diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md index 04ab504783..08b9be1fb7 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md @@ -91,7 +91,7 @@ steps: ### Abhängigkeiten „cachen“ (zwischenspeichern) -Du kannst Deine Abhängigkeiten zwischenspeichern, um die Workflow-Ausführungen zu beschleunigen. Nach einem erfolgreichen Lauf wird Dein lokaler Paket-Cache von Gradle in der Aktions-Infrastruktur auf GitHub gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Paket-Repositories heruntergeladen werden müssen. Weitere Informationen findest Du unter „[Caching-Abhängigkeiten zur Beschleunigung von Workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Nach einem erfolgreichen Lauf wird Dein lokaler Paket-Cache von Gradle in der Aktions-Infrastruktur auf GitHub gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Paket-Repositories heruntergeladen werden müssen. Weitere Informationen findest Du unter „Caching-Abhängigkeiten zur Beschleunigung von Workflows“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md index 039becb6c2..2314effa60 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md @@ -30,7 +30,7 @@ Du solltest ein grundlegendes Verständnis von Java und dem Framework Maven habe ### Einstieg mit einer Maven-Workflow-Vorlage -{% data variables.product.prodname_dotcom %} bietet eine Maven-Workflow-Vorlage, die für die meisten Maven-basierten Java-Projekte funktionieren wird. For more information, see the [Maven workflow template](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml). +{% data variables.product.prodname_dotcom %} bietet eine Maven-Workflow-Vorlage, die für die meisten Maven-basierten Java-Projekte funktionieren wird. Weitere Informationen findest Du im [Workflow-Template für Maven](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml). Um schnell loszulegen, kannst Du beim Erstellen eines neuen Workflows die vorkonfigurierte Maven-Vorlage auswählen. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)." @@ -91,7 +91,7 @@ steps: ### Abhängigkeiten „cachen“ (zwischenspeichern) -Du kannst Deine Abhängigkeiten zwischenspeichern, um die Workflow-Ausführungen zu beschleunigen. Nach einem erfolgreichen Lauf wird Dein lokales Maven-Repository in der Aktions-Infrastruktur auf GitHub gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Maven-Repositories heruntergeladen werden müssen. Weitere Informationen findest Du unter „[Caching-Abhängigkeiten zur Beschleunigung von Workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Nach einem erfolgreichen Lauf wird Dein lokales Maven-Repository in der Aktions-Infrastruktur auf GitHub gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Maven-Repositories heruntergeladen werden müssen. Weitere Informationen findest Du unter „Caching-Abhängigkeiten zur Beschleunigung von Workflows“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml diff --git a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md index 30ecea56d0..c9258acfb2 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md @@ -129,7 +129,7 @@ Wenn Du keine Node.js Version festlegst, verwendet {% data variables.product.pro Auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern sind die Abhängigkeitsmanager npm und Yarn installiert. Du kannst npm und Yarn verwenden, um in Ihrem Workflow Abhängigkeiten zu installieren, bevor Du Deinen Code baust und testest. Die auf {% data variables.product.prodname_dotcom %} gehosteten Windows- und Linux-Runner haben auch Grunt, Gulp und Bower installiert. -Du kannst Abhängigkeiten auch im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen. Weitere Informationen findest Du unter „[Abhängigkeiten im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“. +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. #### Beispiel mit npm @@ -227,7 +227,7 @@ always-auth=true #### Beispiel zum Zwischenspeichern von Abhängigkeiten im Cache -Du kannst Abhängigkeiten mit einem eindeutigen Schlüssel im Cache zwischenspeichern und sie später wiederherstellen, wenn Du zukünftige Workflows mit der Aktion `-cache-` ausführst. Weitere Informationen findest Du unter „[Caching-Abhängigkeiten zur Beschleunigung von Workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. Weitere Informationen findest Du unter „Caching-Abhängigkeiten zur Beschleunigung von Workflows“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml @@ -241,7 +241,7 @@ steps: uses: actions/cache@v2 with: # npm cache files are stored in `~/.npm` on Linux/macOS - path: ~/.npm + path: ~/.npm key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }} restore-keys: | ${{ runner.OS }}-node- diff --git a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md index f546e9f5e1..9f0b0eb43d 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md @@ -91,7 +91,7 @@ The table below describes the locations for various PowerShell modules in each { {% endnote %} -Du kannst Abhängigkeiten auch im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen. Weitere Informationen findest Du unter „[Abhängigkeiten im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“. +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules: @@ -119,7 +119,7 @@ jobs: #### Abhängigkeiten „cachen“ (zwischenspeichern) -You can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system. diff --git a/translations/de-DE/content/actions/guides/building-and-testing-python.md b/translations/de-DE/content/actions/guides/building-and-testing-python.md index 5f0e1d404a..6154cac5b2 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-python.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-python.md @@ -141,9 +141,9 @@ jobs: uses: actions/setup-python@v2 with: # Semantic version range syntax or exact version of a Python version - python-version: '3.x' + python-version: '3.x' # Optional - x64 or x86 architecture, defaults to x64 - architecture: 'x64' + architecture: 'x64' # You can test your matrix by printing the current Python version - name: Display Python version run: python -c "import sys; print(sys.version)" @@ -192,7 +192,7 @@ Wir empfehlen, `setup-python` zu verwenden, um die Version von Python zu konfigu Auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ist der Paketmanager pip installiert. Du kannst pip verwenden, um Abhängigkeiten von der PyPI-Paket-Registry zu installieren, bevor Du Deinen Code baust und testest. Zum Beispiel installiert oder aktualisiert der folgende YAML den Paket-Installierer `pip` sowie die Pakete `setuptools` und `wheel`. -Du kannst Abhängigkeiten auch im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen. Weitere Informationen findest Du unter „[Abhängigkeiten im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“. +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. {% raw %} ```yaml @@ -228,7 +228,7 @@ steps: #### Abhängigkeiten im Cache zwischenspeichern -You can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example below depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip). diff --git a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md index 7d2ef55078..9a4f590d67 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md @@ -148,7 +148,7 @@ steps: #### Abhängigkeiten „cachen“ (zwischenspeichern) -The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. To enable caching, set the following. @@ -165,7 +165,7 @@ This will configure bundler to install your gems to `vendor/cache`. For each suc **Caching without setup-ruby** -For greater control over caching, you can use the `actions/cache` Action directly. Weitere Informationen findest Du unter „[Abhängigkeiten im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“. +For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. {% raw %} ```yaml diff --git a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md index eb8e2e7626..e1d0067de3 100644 --- a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -131,7 +131,7 @@ The `retention-days` value cannot exceed the retention limit set by the reposito During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact)action to download artifacts that were previously uploaded in the same workflow run. -After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/v3/actions/artifacts/)." +After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." #### Herunterladen von Artefakten während einer Workflowausführung diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 42a6fc5357..30fe4c80a3 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -48,7 +48,9 @@ When creating a group, you must choose a policy that defines which repositories {% warning %} **Warnung** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. {% endwarning %} @@ -78,7 +80,9 @@ When creating a group, you must choose a policy that defines which organizations {% warning %} **Warnung** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. {% endwarning %} diff --git a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md index e9cd85487b..2941fc8a7a 100644 --- a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md @@ -57,7 +57,7 @@ jobs: needs: build runs-on: ubuntu-latest steps: - - run: ./test_server.sh + - run: ./test_server.sh ``` For more information, see [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). @@ -106,7 +106,7 @@ jobs: ``` {% endraw %} -Weitere Informationen findest Du unter „[Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)“. +Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. ### Datenbanken und Service-Container verwenden diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 10a49d4a78..3c3851b9fa 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions -Weitere Informationen findest Du unter „[Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)“. +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. {% data variables.product.prodname_actions %} hat kein Äquivalent zum „Docker Layer Caching“ („DLC“, im Cache auf Docker-Ebene zwischenspeichern). diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 99de179d99..683f5152ed 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -262,7 +262,7 @@ jobs: runs-on: ubuntu-latest steps: - run: echo "This job will be run first, in parallel with build_a" - + test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] @@ -346,7 +346,7 @@ jobs: -Weitere Informationen findest Du unter „[Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern](/actions/guides/caching-dependencies-to-speed-up-workflows)“. +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. ### Artifacts @@ -367,7 +367,7 @@ GitLab CI/CD {% raw %} ```yaml -script: +script: artifacts: paths: - math-homework.txt @@ -414,7 +414,7 @@ GitLab CI/CD container-job: variables: POSTGRES_PASSWORD: postgres - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port @@ -423,10 +423,10 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - npm ci - # Runs a script that creates a PostgreSQL client, + # Runs a script that creates a PostgreSQL client, # populates the client with data, and retrieves data - node client.js tags: @@ -452,7 +452,7 @@ jobs: - name: Check out repository code uses: actions/checkout@v2 - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - name: Install dependencies run: npm ci @@ -462,7 +462,7 @@ jobs: # populates the client with data, and retrieves data run: node client.js env: - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port @@ -473,4 +473,4 @@ jobs: -For more information, see "[About service containers](/actions/guides/about-service-containers)." +Weitere Informationen findest Du unter "[Über Service-Container](/actions/guides/about-service-containers)." diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 521bc8c255..d53607e411 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -163,6 +163,12 @@ git: +#### Using environment variables in a matrix + +Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. + +In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} + ### Key features in {% data variables.product.prodname_actions %} When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}: @@ -281,7 +287,7 @@ jobs: ### Abhängigkeiten „cachen“ (zwischenspeichern) -Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. +Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. @@ -316,7 +322,7 @@ cache: npm
-Weitere Informationen findest Du unter „[Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern](/actions/guides/caching-dependencies-to-speed-up-workflows)“. +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. ### Beispiele für häufige Aufgaben diff --git a/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 93a46763d3..3395a68711 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -14,7 +14,7 @@ Auf der Workflow-Lauf-Seite können sie sehen, ob ein Workflow-Lauf ausgeführt Wenn der Lauf abgeschlossen ist, können Sie sehen, ob das Ergebnis erfolgreich, fehlerhaft, abgebrochen oder neutral war. Wenn der Lauf fehlgeschlagen ist, können Sie die Build-Protokolle anzeigen und durchsuchen, um den Fehler zu diagnostizieren und den Workflow erneut auszuführen. Sie können auch fakturierbare Auftragsausführungsminuten anzeigen oder Protokolle herunterladen und Artefakte erstellen. -{% data variables.product.prodname_actions %} verwenden die Checks API, um Status, Ergebnisse und Protokolle für einen Workflow auszugeben. {% data variables.product.prodname_dotcom %} erstellt eine neue Prüfsuite für jeden Workflow-Lauf. Die Prüfsuite enthält einen Prüflauf für jeden Auftrag im Workflow, und jeder Auftrag enthält Schritte. {% data variables.product.prodname_actions %} werden als Schritt in einem Workflow ausgeführt. Weitere Informationen zur Prüf-API finden Sie unter "[](/v3/checks/)". +{% data variables.product.prodname_actions %} verwenden die Checks API, um Status, Ergebnisse und Protokolle für einen Workflow auszugeben. {% data variables.product.prodname_dotcom %} erstellt eine neue Prüfsuite für jeden Workflow-Lauf. Die Prüfsuite enthält einen Prüflauf für jeden Auftrag im Workflow, und jeder Auftrag enthält Schritte. {% data variables.product.prodname_actions %} werden als Schritt in einem Workflow ausgeführt. For more information about the Checks API, see "[Checks](/rest/reference/checks)." {% data reusables.github-actions.invalid-workflow-files %} diff --git a/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md b/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md index c177ed9772..63560a39a7 100644 --- a/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md @@ -79,7 +79,7 @@ Du kannst das `GITHUB_TOKEN` verwenden, um authentifizierte API-Aufrufe durchzuf ### Berechtigungen für das `GITHUB_TOKEN` -For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/v3/apps/permissions/)." +For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)." | Berechtigung | Zugriffstyp | Zugriff durch geforktes Repository | | ------------------------ | --------------- | ---------------------------------- | diff --git a/translations/de-DE/content/actions/reference/encrypted-secrets.md b/translations/de-DE/content/actions/reference/encrypted-secrets.md index f0eb9a3131..295322e2cb 100644 --- a/translations/de-DE/content/actions/reference/encrypted-secrets.md +++ b/translations/de-DE/content/actions/reference/encrypted-secrets.md @@ -43,11 +43,11 @@ Du kannst verschlüsselte Geheimnisse in einer Workflow-Datei verwenden und lese {% endwarning %} -Sie können Geheimnisse auch mit der REST-API verwalten. Weitere Informationen finden Sie unter "[Secrets](/v3/actions/secrets/)". +Sie können Geheimnisse auch mit der REST-API verwalten. For more information, see "[Secrets](/rest/reference/actions#secrets)." #### Einschränken von Anmeldeinformationsberechtigungen -Beim Generieren von Anmeldeinformationen wird empfohlen, möglichst geringe Berechtigungen zu erteilen. Anstatt z.B. persönliche Anmeldeinformationen zu verwenden, solltest Du [Bereitstellen von Schlüsseln](/v3/guides/managing-deploy-keys/#deploy-keys) oder einen „Service-Account“ (Dienstkonto) benuzen. Ziehe in Erwägung, Nur-Lese-Berechtigungen zu gewähren, wenn dies ausreicht, und schränke den Zugriff so weit wie möglich ein. Wähle beim Generieren eines persönlichen Zugriffstokens („personal access token“, PAT) die geringsmöglichen Anwendungsbereiche („scopes“) aus. +Beim Generieren von Anmeldeinformationen wird empfohlen, möglichst geringe Berechtigungen zu erteilen. Anstatt z.B. persönliche Anmeldeinformationen zu verwenden, solltest Du [Bereitstellen von Schlüsseln](/developers/overview/managing-deploy-keys#deploy-keys) oder einen „Service-Account“ (Dienstkonto) benuzen. Ziehe in Erwägung, Nur-Lese-Berechtigungen zu gewähren, wenn dies ausreicht, und schränke den Zugriff so weit wie möglich ein. Wähle beim Generieren eines persönlichen Zugriffstokens („personal access token“, PAT) die geringsmöglichen Anwendungsbereiche („scopes“) aus. ### Erstellen verschlüsselter Geheimnisse für ein Repository diff --git a/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md b/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md index 4f6a7b156a..043d41a583 100644 --- a/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md @@ -143,7 +143,7 @@ jobs: {% data reusables.github-actions.branch-requirement %} -Mit der {% data variables.product.product_name %}-API können Sie das Webhook-Ereignis [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) auslösen, wenn ein Workflow für eine Aktivität ausgelöst werden soll, die außerhalb von {% data variables.product.prodname_dotcom %} abläuft. Weitere Informationen finden Sie unter "[Erstellen eines Repository-Dispatchereignisses](/v3/repos/#create-a-repository-dispatch-event)." +Mit der {% data variables.product.product_name %}-API können Sie das Webhook-Ereignis [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) auslösen, wenn ein Workflow für eine Aktivität ausgelöst werden soll, die außerhalb von {% data variables.product.prodname_dotcom %} abläuft. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)." Soll das benutzerdefinierte Webhook-Ereignis `repository_dispatch` ausgelöst werden, senden Sie eine `POST`-Anfrage an einen {% data variables.product.product_name %}-API-Endpunkt, und geben Sie den Namen für einen `event_type` als Beschreibung für den Aktivitätstyp an. Soll ein Workflow-Lauf ausgelöst werden, konfigurieren Sie außerdem den Workflow für die Verwendung des Ereignisses `repository_dispatch`. @@ -163,7 +163,7 @@ Du kannst Deinen Workflow so konfigurieren, dass er ausgeführt wird, sobald Web #### `check_run` -Führt den Workflow aus, wenn das Ereignis `check_run` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/v3/checks/runs/)." +Führt den Workflow aus, wenn das Ereignis `check_run` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/rest/reference/checks#runs)." {% data reusables.github-actions.branch-requirement %} @@ -183,7 +183,7 @@ on: #### `check_suite` -Führt den Workflow aus, wenn das Ereignis `check_suite` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/v3/checks/suites/)." +Führt den Workflow aus, wenn das Ereignis `check_suite` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/rest/reference/checks#suites)." {% data reusables.github-actions.branch-requirement %} @@ -209,7 +209,7 @@ on: #### `create` -Führt den Workflow aus, wenn ein Benutzer einen Branch oder ein Tag erstellt, wodurch das Ereignis `create` ausgelöst wird. For information about the REST API, see "[Create a reference](/v3/git/refs/#create-a-reference)." +Führt den Workflow aus, wenn ein Benutzer einen Branch oder ein Tag erstellt, wodurch das Ereignis `create` ausgelöst wird. For information about the REST API, see "[Create a reference](/rest/reference/git#create-a-reference)." | Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------- | --------------- | -------------------------------------------- | -------------------------- | @@ -224,7 +224,7 @@ on: #### `delete` -Führt den Workflow aus, wenn ein Benutzer einen Branch oder ein Tag löscht, wodurch das Ereignis `delete` ausgelöst wird. For information about the REST API, see "[Delete a reference](/v3/git/refs/#delete-a-reference)." +Führt den Workflow aus, wenn ein Benutzer einen Branch oder ein Tag löscht, wodurch das Ereignis `delete` ausgelöst wird. For information about the REST API, see "[Delete a reference](/rest/reference/git#delete-a-reference)." {% data reusables.github-actions.branch-requirement %} @@ -271,7 +271,7 @@ on: #### `Fork` -Führt den Workflow aus, wenn ein Benutzer ein Repository forkt, wodurch das Ereignis `fork` ausgelöst wird. For information about the REST API, see "[Create a fork](/v3/repos/forks/#create-a-fork)." +Führt den Workflow aus, wenn ein Benutzer ein Repository forkt, wodurch das Ereignis `fork` ausgelöst wird. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)." {% data reusables.github-actions.branch-requirement %} @@ -354,7 +354,7 @@ jobs: #### `Issues (Lieferungen)` -Führt den Workflow aus, wenn das Ereignis `issues` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/v3/issues)." +Führt den Workflow aus, wenn das Ereignis `issues` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/rest/reference/issues)." {% data reusables.github-actions.branch-requirement %} @@ -374,7 +374,7 @@ on: #### `Kennzeichnung` -Führt den Workflow aus, wenn das Ereignis `label` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Labels](/v3/issues/labels/)." +Führt den Workflow aus, wenn das Ereignis `label` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Labels](/rest/reference/issues#labels)." {% data reusables.github-actions.branch-requirement %} @@ -394,7 +394,7 @@ on: #### `Meilensteine` -Führt Deinen Workflow aus, wenn das Ereignis `milestone` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/v3/issues/milestones/)." +Führt Deinen Workflow aus, wenn das Ereignis `milestone` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)." {% data reusables.github-actions.branch-requirement %} @@ -431,7 +431,7 @@ on: #### `project (Projekt)` -Führt den Workflow aus, wenn das Ereignis `project` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/v3/projects/)." +Führt den Workflow aus, wenn das Ereignis `project` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/rest/reference/projects)." {% data reusables.github-actions.branch-requirement %} @@ -451,7 +451,7 @@ on: #### `project_card` -Führt den Workflow aus, wenn das Ereignis `project_card` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/v3/projects/cards)." +Führt den Workflow aus, wenn das Ereignis `project_card` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)." {% data reusables.github-actions.branch-requirement %} @@ -471,7 +471,7 @@ on: #### `project_column` -Führt Deinen Workflow aus, wenn das Ereignis `project_column` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/v3/projects/columns)." +Führt Deinen Workflow aus, wenn das Ereignis `project_column` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)." {% data reusables.github-actions.branch-requirement %} @@ -491,7 +491,7 @@ on: #### `public` -Führt Deinen Workflow aus, wenn ein Benutzer ein privates Repository öffentlich macht, wodurch das Ereignis `public` ausgelöst wird. For information about the REST API, see "[Edit repositories](/v3/repos/#edit)." +Führt Deinen Workflow aus, wenn ein Benutzer ein privates Repository öffentlich macht, wodurch das Ereignis `public` ausgelöst wird. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)." {% data reusables.github-actions.branch-requirement %} @@ -508,7 +508,7 @@ on: #### `pull_request` -Führt Deinen Workflow aus, wenn das Ereignis `pull_request` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/v3/pulls)." +Führt Deinen Workflow aus, wenn das Ereignis `pull_request` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)." {% note %} @@ -534,7 +534,7 @@ on: #### `pull_request_review` -Führt Deinen Workflow aus, wenn das Ereignis `pull_request_review` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/v3/pulls/reviews)." +Führt Deinen Workflow aus, wenn das Ereignis `pull_request_review` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)." | Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | @@ -554,7 +554,7 @@ on: #### `pull_request_review_comment` -Führt den Workflow aus, wenn ein Kommentar zum vereinheitlichten Diff für einen Pull Request geändert wird, wodurch das Ereignis `pull_request_review_comment` ausgelöst wird. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/v3/pulls/comments). +Führt den Workflow aus, wenn ein Kommentar zum vereinheitlichten Diff für einen Pull Request geändert wird, wodurch das Ereignis `pull_request_review_comment` ausgelöst wird. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/rest/reference/pulls#comments). | Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------- | ------------------------------------------- | @@ -597,7 +597,7 @@ on: pull_request_target {% note %} -**Hinweis:** Die Webhook-Nutzlast, die Für GitHub-Aktionen verfügbar ist, enthält im Objekt `commit` nicht die Attribute `added`, `removed` und `modified`. Du kannst das vollständige Commit-Objekt mit der REST-API abrufen. For more information, see "[Get a single commit](/v3/repos/commits/#get-a-single-commit)"". +**Hinweis:** Die Webhook-Nutzlast, die Für GitHub-Aktionen verfügbar ist, enthält im Objekt `commit` nicht die Attribute `added`, `removed` und `modified`. Du kannst das vollständige Commit-Objekt mit der REST-API abrufen. For more information, see "[Get a single commit](/rest/reference/repos#get-a-single-commit)"". {% endnote %} @@ -640,7 +640,7 @@ on: {% endnote %} -Führt den Workflow aus, wenn das Ereignis `release` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/v3/repos/releases/)." +Führt den Workflow aus, wenn das Ereignis `release` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/rest/reference/repos#releases)." | Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | --------------------- | @@ -658,7 +658,7 @@ on: #### `Status` -Führt den Workflow aus, wenn sich der Status eines Git-Commit ändert, wodurch das Ereignis `status` ausgelöst wird. For information about the REST API, see [Statuses](/v3/repos/statuses/). +Führt den Workflow aus, wenn sich der Status eines Git-Commit ändert, wodurch das Ereignis `status` ausgelöst wird. For information about the REST API, see [Statuses](/rest/reference/repos#statuses). {% data reusables.github-actions.branch-requirement %} @@ -675,7 +675,7 @@ on: #### `beobachten` -Führt den Workflow aus, wenn das Ereignis `watch` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/v3/activity/starring/)." +Führt den Workflow aus, wenn das Ereignis `watch` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/rest/reference/activity#starring)." {% data reusables.github-actions.branch-requirement %} diff --git a/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md b/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md index 8918e6a898..0f91250af9 100644 --- a/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md @@ -79,6 +79,7 @@ Weitere Informationen findest Du unter: - "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" for {% data variables.product.prodname_ghe_cloud %}{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Disabling and enabling workflows You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}. @@ -86,3 +87,4 @@ You can enable and disable individual workflows in your repository on {% data va {% data reusables.actions.scheduled-workflows-disabled %} For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)." +{% endif %} diff --git a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md index d80a5e2114..4a9cb976a0 100644 --- a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md @@ -227,7 +227,7 @@ Jeder Job läuft in einer Umgebung, die mit `runs-on` angegeben wird. Innerhalb der Nutzungsbeschränkungen des Workflows kannst Du unbegrenzt viele Jobs ausführen. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. -Wenn Du den eindeutigen Bezeichner eines Jobs finden musst, der in einem Workflowlauf ausgeführt wird, kannst Du die API von {% data variables.product.prodname_dotcom %} verwenden. For more information, see "[Workflow Jobs](/v3/actions/workflow-jobs)." +Wenn Du den eindeutigen Bezeichner eines Jobs finden musst, der in einem Workflowlauf ausgeführt wird, kannst Du die API von {% data variables.product.prodname_dotcom %} verwenden. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." ### **`jobs.`** @@ -878,34 +878,9 @@ strategy: ##### Using environment variables in a matrix -You can add custom environment variables for each test combination by using `include` with `env`. You can then refer to the custom environment variables in a later step. +You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. -In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: - -{% raw %} -```yaml -name: Node.js CI -on: [push] -jobs: - build: - runs-on: ubuntu-latest - strategy: - matrix: - include: - - node-version: 10.x - site: "prod" - datacenter: "site-a" - - node-version: 12.x - site: "dev" - datacenter: "site-b" - steps: - - name: Echo site details - env: - SITE: ${{ matrix.site }} - DATACENTER: ${{ matrix.datacenter }} - run: echo $SITE $DATACENTER -``` -{% endraw %} +{% data reusables.github-actions.matrix-variable-example %} ### **`jobs..strategy.fail-fast`** diff --git a/translations/de-DE/content/admin/authentication/changing-authentication-methods.md b/translations/de-DE/content/admin/authentication/changing-authentication-methods.md index 4c96577803..5d1bdc7363 100644 --- a/translations/de-DE/content/admin/authentication/changing-authentication-methods.md +++ b/translations/de-DE/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: Wenn Sie die Authentifizierungsmethode ändern, werden die Benutzerkonten auf {% data variables.product.product_location %} beibehalten, und Benutzer melden sich weiterhin beim selben Konto an, sofern ihr Benutzername nicht geändert wird. -Wenn bei der neuen Authentifizierungsmethode Benutzernamen geändert werden, werden neue Konten erstellt. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user). +Wenn bei der neuen Authentifizierungsmethode Benutzernamen geändert werden, werden neue Konten erstellt. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). Zudem sollten Sie die folgenden Issues in Betracht ziehen: diff --git a/translations/de-DE/content/admin/configuration/command-line-utilities.md b/translations/de-DE/content/admin/configuration/command-line-utilities.md index f7b0b18850..13f73e1976 100644 --- a/translations/de-DE/content/admin/configuration/command-line-utilities.md +++ b/translations/de-DE/content/admin/configuration/command-line-utilities.md @@ -159,7 +159,7 @@ $ ghe-es-index-status -do | column -ts, #### ghe-legacy-github-services-report -Dieses Dienstprogramm listet Repositorys auf Ihrer Appliance auf, die {% data variables.product.prodname_dotcom %} Services verwenden. Hierbei handelt es sich um eine Integrationsmethode, die am 1. Oktober 2018 eingestellt wird. Benutzer auf Ihrer Appliance haben {% data variables.product.prodname_dotcom %} Services möglicherweise so eingerichtet, dass für Push-Vorgänge an bestimmte Repositorys Benachrichtigungen erstellt werden. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/v3/guides/replacing-github-services/)." Verwenden Sie das Flag `-h`, um weitere Informationen zu diesem Befehl oder zusätzliche Informationen anzuzeigen. +Dieses Dienstprogramm listet Repositorys auf Ihrer Appliance auf, die {% data variables.product.prodname_dotcom %} Services verwenden. Hierbei handelt es sich um eine Integrationsmethode, die am 1. Oktober 2018 eingestellt wird. Benutzer auf Ihrer Appliance haben {% data variables.product.prodname_dotcom %} Services möglicherweise so eingerichtet, dass für Push-Vorgänge an bestimmte Repositorys Benachrichtigungen erstellt werden. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)." Verwenden Sie das Flag `-h`, um weitere Informationen zu diesem Befehl oder zusätzliche Informationen anzuzeigen. ```shell ghe-legacy-github-services-report diff --git a/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md index cc7e405fcc..577f33fe88 100644 --- a/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md +++ b/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md @@ -37,7 +37,7 @@ Wenn Du {% data variables.product.prodname_github_connect %} aktivierst, wird zu Wenn {% data variables.product.prodname_github_connect %} aktiviert wird, können {% data variables.product.prodname_dotcom_the_website %}-Benutzer keine Änderungen an {% data variables.product.prodname_ghe_server %} vornehmen. -For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." ### {% data variables.product.prodname_github_connect %} aktivieren 1. Sign in to diff --git a/translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md b/translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md index afe5e34bc8..f39bd1d288 100644 --- a/translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md +++ b/translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md @@ -19,6 +19,6 @@ With the APIs, you can automate many administrative tasks. Darunter beispielswei - Änderungen in der {% data variables.enterprise.management_console %} durchführen. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)." - Die LDAP-Synchronisierung konfigurieren. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %} - Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)." -- Verwalte Dein Unternehmenskonto. Weitere Informationen findest Du unter „[Unternehmenskonten](/v4/guides/managing-enterprise-accounts).“ +- Verwalte Dein Unternehmenskonto. Weitere Informationen findest Du unter „[Unternehmenskonten](/graphql/guides/managing-enterprise-accounts).“ -For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). \ No newline at end of file +For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). diff --git a/translations/de-DE/content/admin/user-management/audited-actions.md b/translations/de-DE/content/admin/user-management/audited-actions.md index 245261643b..a0af914b5f 100644 --- a/translations/de-DE/content/admin/user-management/audited-actions.md +++ b/translations/de-DE/content/admin/user-management/audited-actions.md @@ -138,7 +138,7 @@ versions: [Deployment-Schlüssel]: /guides/managing-deploy-keys/#deploy-keys [deploy key]: /guides/managing-deploy-keys/#deploy-keys [generate token]: /articles/creating-an-access-token-for-command-line-use - [OAuth-Zugriffstoken]: /v3/oauth/ + [OAuth-Zugriffstoken]: /developers/apps/authorizing-oauth-apps [OAuth-Anwendung]: /guides/basics-of-authentication/#registering-your-app [2fa]: /articles/about-two-factor-authentication [2fa]: /articles/about-two-factor-authentication diff --git a/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md index a184404e40..b2dfa36708 100644 --- a/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md +++ b/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md @@ -27,7 +27,7 @@ versions: Verwenden Sie die API für Migrationen, um Repository-Daten von {% data variables.product.prodname_dotcom_the_website %} zu exportieren. -Die API für Migrationen befindet sich derzeit in einer Vorschauphase, weshalb sich die Endpunkte und Parameter künftig ändern können. Um auf die API für Migrationen zuzugreifen, müssen Sie einen benutzerdefinierten [Medientyp](/v3/media) im Header `Accept` angeben: `application/vnd.github.wyandotte-preview+json`. Die folgenden Beispiele enthalten den benutzerdefinierten Medientyp. +Die API für Migrationen befindet sich derzeit in einer Vorschauphase, weshalb sich die Endpunkte und Parameter künftig ändern können. Um auf die API für Migrationen zuzugreifen, müssen Sie einen benutzerdefinierten [Medientyp](/rest/overview/media-types) im Header `Accept` angeben: `application/vnd.github.wyandotte-preview+json`. Die folgenden Beispiele enthalten den benutzerdefinierten Medientyp. ### Migrationsarchiv generieren @@ -37,7 +37,7 @@ Die API für Migrationen befindet sich derzeit in einer Vorschauphase, weshalb s 2. Starten Sie eine Migration. Senden Sie dazu eine `POST`-Anforderung an den Migrationsendpunkt. Sie benötigen Folgendes: * Ihr Zugriffstoken für die Authentifizierung. - * Eine [Liste der Repositorys](/v3/repos/#list-organization-repositories), die migriert werden sollen: + * Eine [Liste der Repositorys](/rest/reference/repos#list-organization-repositories), die migriert werden sollen: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md index 4fd08e063c..3c57790e46 100644 --- a/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %} -After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository). Sie benötigen Ihr Zugriffstoken für die Authentifizierung: +After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). Sie benötigen Ihr Zugriffstoken für die Authentifizierung: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md index 09bc4116d6..1d816f1b00 100644 --- a/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ Sie können eine benutzerdefinierte Meldung erstellen, die gesperrten Benutzern ``` ### Weiterführende Informationen -- "[Suspend a user](/enterprise/{{ currentVersion }}/v3/enterprise-admin/users/#suspend-a-user)" +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/de-DE/content/developers/apps/about-apps.md b/translations/de-DE/content/developers/apps/about-apps.md index 058dff52b4..e04779fde9 100644 --- a/translations/de-DE/content/developers/apps/about-apps.md +++ b/translations/de-DE/content/developers/apps/about-apps.md @@ -67,13 +67,13 @@ Keep these ideas in mind when creating {% data variables.product.prodname_oauth_ * Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_app %}s authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/v3/guides/basics-of-authentication/#registering-your-app)." +For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." ### Persönliche Zugriffsstokens A [personal access token](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A personal access token is also similar to a password, but you can have many of them and you can revoke access to each one at any time. -As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/v3/issues/#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it. +As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it. Keep these ideas in mind when using personal access tokens: diff --git a/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md b/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md index 750e4ff36a..ec679b8d8c 100644 --- a/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md @@ -118,13 +118,13 @@ You'll need to create a new JWT after the time expires. ### Accessing API endpoints as a {% data variables.product.prodname_github_app %} -For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/v3/apps/)." +For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)." ### Authenticating as an installation Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. These installation access tokens are used by {% data variables.product.prodname_github_app %}s to authenticate. -By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour. +By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour. To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request: @@ -144,7 +144,7 @@ $ curl -i -X POST \ ``` {% endif %} -The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint. +The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint. To authenticate with an installation access token, include it in the Authorization header in the API request: @@ -168,9 +168,9 @@ $ curl -i \ ### Accessing API endpoints as an installation -For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_app %}s using an installation access token, see "[Available Endpoints](/v3/apps/available-endpoints/)." +For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_app %}s using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)." -For a list of endpoints related to installations, see "[Installations](/v3/apps/installations/)." +For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)." ### HTTP-based Git access by an installation diff --git a/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md b/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md index 375d0be585..79cc6b49eb 100644 --- a/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md @@ -235,12 +235,12 @@ For more information, see the "[OAuth 2.0 Device Authorization Grant](https://to ### Non-Web application flow -Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/v3/auth#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. +Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with two-factor authentication](/v3/auth/#working-with-two-factor-authentication) if you or your users have two-factor authentication enabled. +**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if you or your users have two-factor authentication enabled. {% endnote %} {% endif %} @@ -289,7 +289,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% tip %} -**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/v3/guides/discovering-resources-for-a-user/)." +**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." {% endtip %} diff --git a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md index 9f93d2d434..e19b3edd2e 100644 --- a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -52,16 +52,16 @@ The person creating the app will be redirected to a GitHub page with an input fi ##### GitHub App Manifest parameters - | Name | Typ | Beschreibung | - | --------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `string` | The name of the GitHub App. | - | `url` | `string` | **Required.** The homepage of your GitHub App. | - | `hook_attributes` | `Objekt` | The configuration of the GitHub App's webhook. | - | `redirect_url` | `string` | The full URL to redirect to after the person installs the GitHub App. | - | `Beschreibung` | `string` | A description of the GitHub App. | - | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | - | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | - | `default_permissions` | `Objekt` | The set of [permissions](/v3/apps/permissions/) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | + | Name | Typ | Beschreibung | + | --------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `string` | The name of the GitHub App. | + | `url` | `string` | **Required.** The homepage of your GitHub App. | + | `hook_attributes` | `Objekt` | The configuration of the GitHub App's webhook. | + | `redirect_url` | `string` | The full URL to redirect to after the person installs the GitHub App. | + | `Beschreibung` | `string` | A description of the GitHub App. | + | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | + | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | + | `default_permissions` | `Objekt` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | The `hook_attributes` object has the following key: @@ -153,13 +153,13 @@ If you provided a `state` parameter, you will also see that parameter in the `re #### 3. You exchange the temporary code to retrieve the app configuration -To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. +To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. You must complete this step of the GitHub App Manifest flow within one hour. {% note %} -**Note:** This endpoint is rate limited. See [Rate limits](/v3/rate_limit/) to learn how to get your current rate limit status. +**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status. {% endnote %} @@ -170,7 +170,7 @@ You must complete this step of the GitHub App Manifest flow within one hour. POST /app-manifests/:code/conversions -For more information about the endpoint's response, see [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest). +For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest). When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time. @@ -191,4 +191,4 @@ Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file #### Hosting your app with Glitch -You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/v3/checks/) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. +You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. diff --git a/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md index 03eed961d8..1da31833df 100644 --- a/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -49,37 +49,37 @@ The complete list of available query parameters, permissions, and events is list You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission. -| Berechtigung | Beschreibung | -| -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Berechtigung | Beschreibung | +| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/v3/users/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`checks (Prüfungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/v3/checks/). Can be one of: `none`, `read`, or `write`. | -| `content_references` | Grants access to the "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. | -| [`contents (Inhalte)`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. | +| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`checks (Prüfungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`. | +| `content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. | +| [`contents (Inhalte)`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. | | [`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/v3/repos/deployments/). Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/v3/users/emails/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`follower`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/v3/users/followers/). Can be one of: `none`, `read`, or `write`. | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/v3/users/gpg_keys/). Can be one of: `none`, `read`, or `write`. | -| [`Issues (Lieferungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/v3/issues/). Can be one of: `none`, `read`, or `write`. | -| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/v3/users/keys/). Can be one of: `none`, `read`, or `write`. | +| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`follower`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`. | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`. | +| [`Issues (Lieferungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`. | +| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`. | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`Metadaten`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. | -| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/v3/orgs/#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/v3/orgs/hooks/). Can be one of: `none`, `read`, or `write`. | -| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/v3/orgs/#get-an-organization)" endpoint. Can be one of: `none` or `read`. | -| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} -| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/v3/orgs/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`Seiten`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/v3/repos/pages/). Can be one of: `none`, `read`, or `write`. | -| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/v3/users/#get-a-user)" endpoint. Can be one of: `none` or `read`. | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/v3/repos/hooks/). Can be one of: `none`, `read`, or `write`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`. | -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/v3/repos/contents/). Can be one of: `none`, `read`, or `write`. | -| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/v3/activity/starring/). Can be one of: `none`, `read`, or `write`. | -| [`statuses (Statusangaben)`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/v3/repos/statuses/). Can be one of: `none`, `read`, or `write`. | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/v3/teams/discussions/) and the [Team Discussion Comments API](/v3/teams/discussion_comments/). Can be one of: `none`, `read`, or `write`. | -| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. | -| `beobachten` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. | +| [`Metadaten`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. | +| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/v3/orgs/hooks/). Can be one of: `none`, `read`, or `write`. | +| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`. | +| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} +| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`Seiten`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/v3/repos/pages/). Can be one of: `none`, `read`, or `write`. | +| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`. | +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. | +| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. | +| [`statuses (Statusangaben)`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`. | +| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. | +| `beobachten` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. | ### {% data variables.product.prodname_github_app %} webhook events diff --git a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md index ad7bf69047..9bbbd7e6f0 100644 --- a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Einführung -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/v3/checks/), which you'll use to build a continuous integration (CI) server that runs tests. +This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Durch häufige Code-Aktualisierungen lassen sich zudem Änderungen von verschiedenen Mitgliedern eines Software-Entwicklungsteams leichter zusammenführen. Dies bedeutet einen erheblichen Vorteil für die Entwickler, die sich damit stärker auf das Schreiben des Codes konzentrieren können, statt Fehler debuggen oder Mergekonflikte beheben zu müssen. 🙌 @@ -22,15 +22,15 @@ A CI server hosts code that runs CI tests such as code linters (which check styl #### Checks API overview -The [Checks API](/v3/checks/) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. +The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. -A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/v3/repos/branches/) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. +A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. -The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: +The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: 1. Whenever someone pushes code to the repository, GitHub sends the `check_suite` event with an action of `requested` to all GitHub Apps installed on the repository that have the `checks:write` permission. This event lets the apps know that code was pushed and that GitHub has automatically created a new check suite. -1. When your app receives this event, it can [add check runs](/v3/checks/runs/#create-a-check-run) to that suite. -1. Your check runs can include [annotations](/v3/checks/runs/#annotations-object) that are displayed on specific lines of code. +1. When your app receives this event, it can [add check runs](/rest/reference/checks#create-a-check-run) to that suite. +1. Your check runs can include [annotations](/rest/reference/checks#annotations-object) that are displayed on specific lines of code. **In this guide, you’ll learn how to:** @@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t ### Vorrausetzungen -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/v3/checks/), if you're not already. You'll find more APIs in the [REST API docs](/v3/). The Checks API is also available to use in [GraphQL](/v4/), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/v4/object/checksuite/) and [Check Run](/v4/object/checkrun/) objects for more details. +Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app. @@ -140,7 +140,7 @@ You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sina def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -159,7 +159,7 @@ end def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -175,7 +175,7 @@ end ``` {% endif %} -This code calls the "[Create a check run](/v3/checks/runs/#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method. +This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method. To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [Rubocop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo Rubocop" is used here, but you can choose any name you'd like for the check run. @@ -240,7 +240,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -276,7 +276,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -305,11 +305,11 @@ end ``` {% endif %} -The code above calls the "[Update a check run](/v3/checks/runs/#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. +The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. Here's what this code is doing. First, it updates the check run's status to `in_progress` and sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`. -You'll notice in the "[Update a check run](/v3/checks/runs/#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`. +You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`. You could also provide more details about what your check is doing, but you'll get to that in the next section. Let's test this code again by re-running `template_server.rb`: @@ -435,7 +435,7 @@ The code above gets the full repository name and the head SHA of the commit from ### Schritt 2.3. Running RuboCop -Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/v3/checks/runs/#create-a-check-run). +Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. @@ -523,11 +523,11 @@ You should see the linting errors in the debug output, although they aren't prin The `@output` variable contains the parsed JSON results of the RuboCop report. As shown above, the results contain a `summary` section that your code can use to quickly determine if there are any errors. The following code will set the check run conclusion to `success` when there are no reported errors. RuboCop reports errors for each file in the `files` array, so if there are errors, you'll need to extract some data from the file object. -The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/v3/checks/runs/#update-a-check-run) with annotations. +The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/rest/reference/checks#update-a-check-run) with annotations. -The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. +The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. -A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/v3/checks/runs/#annotations-object-1) reference documentation for details. +A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/rest/reference/checks#annotations-object-1) reference documentation for details. You'll extract the required information from RuboCop needed to create each annotation. Append the following code to the code you added in the [previous section](#step-23-running-rubocop): @@ -536,7 +536,7 @@ annotations = [] # You can create a maximum of 50 annotations per request to the Checks # API. To add more than 50 annotations, use the "Update a check run" API # endpoint. This example code limits the number of annotations to 50. -# See /v3/checks/runs/#update-a-check-run +# See /rest/reference/checks#update-a-check-run # for details. max_annotations = 50 @@ -869,4 +869,4 @@ After walking through this guide, you've learned the basics of using the Checks Here are some ideas for what you can do next: * Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors. -* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/v3/pulls/#create-a-pull-request) with a new branch based on the head branch. +* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch. diff --git a/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 1f43ad34b2..ad3c3830ad 100644 --- a/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -90,10 +90,10 @@ Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to requ ### Git access -| GitHub Apps | OAuth Apps | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | -| The token is used as the HTTP password. | The token is used as the HTTP username. | +| GitHub Apps | OAuth Apps | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/repos#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | +| The token is used as the HTTP password. | The token is used as the HTTP username. | ### Machine vs. bot accounts diff --git a/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 734c3965de..193fe293ec 100644 --- a/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -67,7 +67,7 @@ If the user accepts your request, GitHub redirects back to your site with a temp {% endnote %} -Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." +Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)." Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} @@ -154,7 +154,7 @@ You can also check which repositories are accessible to a user for an installati Authorization: token OAUTH-TOKEN GET /user/installations/:installation_id/repositories -More details can be found in: [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token). +More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). ### Handling a revoked GitHub App authorization @@ -162,7 +162,7 @@ If a user revokes their authorization of a GitHub App, the app will receive the ### User-level permissions -You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/v3/apps/permissions/), which are granted at the time of installation on an organization or user account. +You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account. You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." @@ -172,75 +172,75 @@ Because user-level permissions are granted on an individual user basis, you can ### User-to-server requests -While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/v4/) or [REST v3](/v3/) endpoints. +While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/graphql) or [REST v3](/rest) endpoints. #### Supported endpoints {% if currentVersion == "free-pro-team@latest" %} ##### Actions Runners -* [List runner applications for a repository](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) -* [List self-hosted runners for a repository](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) -* [Get a self-hosted runner for a repository](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) -* [Delete a self-hosted runner from a repository](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) -* [Create a registration token for a repository](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) -* [Create a remove token for a repository](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) -* [List runner applications for an organization](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) -* [List self-hosted runners for an organization](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) -* [Get a self-hosted runner for an organization](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) -* [Delete a self-hosted runner from an organization](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) -* [Create a registration token for an organization](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) -* [Create a remove token for an organization](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) +* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository) +* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization) +* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization) ##### Actions Secrets -* [Get a repository public key](/v3/actions/secrets/#get-a-repository-public-key) -* [List repository secrets](/v3/actions/secrets/#list-repository-secrets) -* [Get a repository secret](/v3/actions/secrets/#get-a-repository-secret) -* [Create or update a repository secret](/v3/actions/secrets/#create-or-update-a-repository-secret) -* [Delete a repository secret](/v3/actions/secrets/#delete-a-repository-secret) -* [Get an organization public key](/v3/actions/secrets/#get-an-organization-public-key) -* [List organization secrets](/v3/actions/secrets/#list-organization-secrets) -* [Get an organization secret](/v3/actions/secrets/#get-an-organization-secret) -* [Create or update an organization secret](/v3/actions/secrets/#create-or-update-an-organization-secret) -* [List selected repositories for an organization secret](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) -* [Set selected repositories for an organization secret](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) -* [Add selected repository to an organization secret](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) -* [Remove selected repository from an organization secret](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) -* [Delete an organization secret](/v3/actions/secrets/#delete-an-organization-secret) +* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key) +* [List repository secrets](/rest/reference/actions#list-repository-secrets) +* [Get a repository secret](/rest/reference/actions#get-a-repository-secret) +* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret) +* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret) +* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key) +* [List organization secrets](/rest/reference/actions#list-organization-secrets) +* [Get an organization secret](/rest/reference/actions#get-an-organization-secret) +* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret) +* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Artifacts -* [List artifacts for a repository](/v3/actions/artifacts/#list-artifacts-for-a-repository) -* [List workflow run artifacts](/v3/actions/artifacts/#list-workflow-run-artifacts) -* [Get an artifact](/v3/actions/artifacts/#get-an-artifact) -* [Delete an artifact](/v3/actions/artifacts/#delete-an-artifact) -* [Download an artifact](/v3/actions/artifacts/#download-an-artifact) +* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository) +* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts) +* [Get an artifact](/rest/reference/actions#get-an-artifact) +* [Delete an artifact](/rest/reference/actions#delete-an-artifact) +* [Download an artifact](/rest/reference/actions#download-an-artifact) {% endif %} ##### Check Runs -* [Create a check run](/v3/checks/runs/#create-a-check-run) -* [Get a check run](/v3/checks/runs/#get-a-check-run) -* [Update a check run](/v3/checks/runs/#update-a-check-run) -* [List check run annotations](/v3/checks/runs/#list-check-run-annotations) -* [List check runs in a check suite](/v3/checks/runs/#list-check-runs-in-a-check-suite) -* [List check runs for a Git reference](/v3/checks/runs/#list-check-runs-for-a-git-reference) +* [Create a check run](/rest/reference/checks#create-a-check-run) +* [Get a check run](/rest/reference/checks#get-a-check-run) +* [Update a check run](/rest/reference/checks#update-a-check-run) +* [List check run annotations](/rest/reference/checks#list-check-run-annotations) +* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference) ##### Prüfsuiten -* [Create a check suite](/v3/checks/suites/#create-a-check-suite) -* [Get a check suite](/v3/checks/suites/#get-a-check-suite) -* [Rerequest a check suite](/v3/checks/suites/#rerequest-a-check-suite) -* [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) -* [List check suites for a Git reference](/v3/checks/suites/#list-check-suites-for-a-git-reference) +* [Create a check suite](/rest/reference/checks#create-a-check-suite) +* [Get a check suite](/rest/reference/checks#get-a-check-suite) +* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite) +* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference) ##### Codes Of Conduct -* [Get all codes of conduct](/v3/codes_of_conduct/#get-all-codes-of-conduct) -* [Get a code of conduct](/v3/codes_of_conduct/#get-a-code-of-conduct) +* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct) ##### Deployment Statuses @@ -266,128 +266,128 @@ While most of your API interaction should occur using your server-to-server inst ##### Git Blobs -* [Create a blob](/v3/git/blobs/#create-a-blob) -* [Get a blob](/v3/git/blobs/#get-a-blob) +* [Create a blob](/rest/reference/git#create-a-blob) +* [Get a blob](/rest/reference/git#get-a-blob) ##### Git Commits -* [Create a commit](/v3/git/commits/#create-a-commit) -* [Get a commit](/v3/git/commits/#get-a-commit) +* [Create a commit](/rest/reference/git#create-a-commit) +* [Get a commit](/rest/reference/git#get-a-commit) ##### Git Refs -* [Create a reference](/v3/git/refs/#create-a-reference)* [Get a reference](/v3/git/refs/#get-a-reference) -* [List matching references](/v3/git/refs/#list-matching-references) -* [Update a reference](/v3/git/refs/#update-a-reference) -* [Delete a reference](/v3/git/refs/#delete-a-reference) +* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference) +* [List matching references](/rest/reference/git#list-matching-references) +* [Update a reference](/rest/reference/git#update-a-reference) +* [Delete a reference](/rest/reference/git#delete-a-reference) ##### Git Tags -* [Create a tag object](/v3/git/tags/#create-a-tag-object) -* [Get a tag](/v3/git/tags/#get-a-tag) +* [Create a tag object](/rest/reference/git#create-a-tag-object) +* [Get a tag](/rest/reference/git#get-a-tag) ##### Git Trees -* [Create a tree](/v3/git/trees/#create-a-tree) -* [Get a tree](/v3/git/trees/#get-a-tree) +* [Create a tree](/rest/reference/git#create-a-tree) +* [Get a tree](/rest/reference/git#get-a-tree) ##### Gitignore Templates -* [Get all gitignore templates](/v3/gitignore/#get-all-gitignore-templates) -* [Get a gitignore template](/v3/gitignore/#get-a-gitignore-template) +* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates) +* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template) ##### Installations -* [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token) +* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} ##### Interaction Limits -* [Get interaction restrictions for an organization](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) -* [Set interaction restrictions for an organization](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) -* [Remove interaction restrictions for an organization](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) -* [Get interaction restrictions for a repository](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) -* [Set interaction restrictions for a repository](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) -* [Remove interaction restrictions for a repository](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) +* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) {% endif %} ##### Issue Assignees -* [Add assignees to an issue](/v3/issues/assignees/#add-assignees-to-an-issue) -* [Remove assignees from an issue](/v3/issues/assignees/#remove-assignees-from-an-issue) +* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue) +* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue) ##### Issue Comments -* [List issue comments](/v3/issues/comments/#list-issue-comments) -* [Create an issue comment](/v3/issues/comments/#create-an-issue-comment) -* [List issue comments for a repository](/v3/issues/comments/#list-issue-comments-for-a-repository) -* [Get an issue comment](/v3/issues/comments/#get-an-issue-comment) -* [Update an issue comment](/v3/issues/comments/#update-an-issue-comment) -* [Delete an issue comment](/v3/issues/comments/#delete-an-issue-comment) +* [List issue comments](/rest/reference/issues#list-issue-comments) +* [Create an issue comment](/rest/reference/issues#create-an-issue-comment) +* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository) +* [Get an issue comment](/rest/reference/issues#get-an-issue-comment) +* [Update an issue comment](/rest/reference/issues#update-an-issue-comment) +* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment) ##### Issue Events -* [List issue events](/v3/issues/events/#list-issue-events) +* [List issue events](/rest/reference/issues#list-issue-events) ##### Issue Timeline -* [List timeline events for an issue](/v3/issues/timeline/#list-timeline-events-for-an-issue) +* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue) ##### Issues -* [List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user) -* [List assignees](/v3/issues/assignees/#list-assignees) -* [Check if a user can be assigned](/v3/issues/assignees/#check-if-a-user-can-be-assigned) -* [List repository issues](/v3/issues/#list-repository-issues) -* [Hiermit wird ein Issue erstellt.](/v3/issues/#create-an-issue) -* [Get an issue](/v3/issues/#get-an-issue) -* [Update an issue](/v3/issues/#update-an-issue) -* [Lock an issue](/v3/issues/#lock-an-issue) -* [Unlock an issue](/v3/issues/#unlock-an-issue) +* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [List assignees](/rest/reference/issues#list-assignees) +* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [List repository issues](/rest/reference/issues#list-repository-issues) +* [Hiermit wird ein Issue erstellt.](/rest/reference/issues#create-an-issue) +* [Get an issue](/rest/reference/issues#get-an-issue) +* [Update an issue](/rest/reference/issues#update-an-issue) +* [Lock an issue](/rest/reference/issues#lock-an-issue) +* [Unlock an issue](/rest/reference/issues#unlock-an-issue) {% if currentVersion == "free-pro-team@latest" %} ##### Jobs -* [Get a job for a workflow run](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) -* [Download job logs for a workflow run](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) -* [List jobs for a workflow run](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) +* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run) {% endif %} ##### Kennzeichnungen -* [List labels for an issue](/v3/issues/labels/#list-labels-for-an-issue) -* [Add labels to an issue](/v3/issues/labels/#add-labels-to-an-issue) -* [Set labels for an issue](/v3/issues/labels/#set-labels-for-an-issue) -* [Remove all labels from an issue](/v3/issues/labels/#remove-all-labels-from-an-issue) -* [Remove a label from an issue](/v3/issues/labels/#remove-a-label-from-an-issue) -* [List labels for a repository](/v3/issues/labels/#list-labels-for-a-repository) -* [Create a label](/v3/issues/labels/#create-a-label) -* [Get a label](/v3/issues/labels/#get-a-label) -* [Update a label](/v3/issues/labels/#update-a-label) -* [Delete a label](/v3/issues/labels/#delete-a-label) -* [Get labels for every issue in a milestone](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) +* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue) +* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue) +* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue) +* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue) +* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue) +* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository) +* [Create a label](/rest/reference/issues#create-a-label) +* [Get a label](/rest/reference/issues#get-a-label) +* [Update a label](/rest/reference/issues#update-a-label) +* [Delete a label](/rest/reference/issues#delete-a-label) +* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone) ##### Licenses -* [Get all commonly used licenses](/v3/licenses/#get-all-commonly-used-licenses) -* [Get a license](/v3/licenses/#get-a-license) +* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses) +* [Get a license](/rest/reference/licenses#get-a-license) ##### Markdown -* [Render a Markdown document](/v3/markdown/#render-a-markdown-document) -* [Render a markdown document in raw mode](/v3/markdown/#render-a-markdown-document-in-raw-mode) +* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document) +* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) ##### Meta -* [Meta](/v3/meta/#meta) +* [Meta](/rest/reference/meta#meta) ##### Meilensteine -* [List milestones](/v3/issues/milestones/#list-milestones) -* [Create a milestone](/v3/issues/milestones/#create-a-milestone) -* [Get a milestone](/v3/issues/milestones/#get-a-milestone) -* [Update a milestone](/v3/issues/milestones/#update-a-milestone) -* [Delete a milestone](/v3/issues/milestones/#delete-a-milestone) +* [List milestones](/rest/reference/issues#list-milestones) +* [Create a milestone](/rest/reference/issues#create-a-milestone) +* [Get a milestone](/rest/reference/issues#get-a-milestone) +* [Update a milestone](/rest/reference/issues#update-a-milestone) +* [Delete a milestone](/rest/reference/issues#delete-a-milestone) ##### Organization Hooks @@ -401,29 +401,29 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Organization Invitations -* [List pending organization invitations](/v3/orgs/members/#list-pending-organization-invitations) -* [Create an organization invitation](/v3/orgs/members/#create-an-organization-invitation) -* [List organization invitation teams](/v3/orgs/members/#list-organization-invitation-teams) +* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations) +* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation) +* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams) {% endif %} ##### Organization Members -* [List organization members](/v3/orgs/members/#list-organization-members) -* [Check organization membership for a user](/v3/orgs/members/#check-organization-membership-for-a-user) -* [Remove an organization member](/v3/orgs/members/#remove-an-organization-member) -* [Get organization membership for a user](/v3/orgs/members/#get-organization-membership-for-a-user) -* [Set organization membership for a user](/v3/orgs/members/#set-organization-membership-for-a-user) -* [Remove organization membership for a user](/v3/orgs/members/#remove-organization-membership-for-a-user) -* [List public organization members](/v3/orgs/members/#list-public-organization-members) -* [Check public organization membership for a user](/v3/orgs/members/#check-public-organization-membership-for-a-user) -* [Set public organization membership for the authenticated user](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) -* [Remove public organization membership for the authenticated user](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) +* [List organization members](/rest/reference/orgs#list-organization-members) +* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user) +* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member) +* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user) +* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user) +* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [List public organization members](/rest/reference/orgs#list-public-organization-members) +* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) ##### Organization Outside Collaborators -* [List outside collaborators for an organization](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) -* [Convert an organization member to outside collaborator](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) -* [Remove outside collaborator from an organization](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) +* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) {% if enterpriseServerVersions contains currentVersion %} ##### Organization Pre Receive Hooks @@ -437,198 +437,198 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Organization Team Projects -* [List team projects](/v3/teams/#list-team-projects) -* [Check team permissions for a project](/v3/teams/#check-team-permissions-for-a-project) -* [Add or update team project permissions](/v3/teams/#add-or-update-team-project-permissions) -* [Remove a project from a team](/v3/teams/#remove-a-project-from-a-team) +* [List team projects](/rest/reference/teams#list-team-projects) +* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project) +* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions) +* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team) {% endif %} ##### Organization Team Repositories -* [List team repositories](/v3/teams/#list-team-repositories) -* [Check team permissions for a repository](/v3/teams/#check-team-permissions-for-a-repository) -* [Add or update team repository permissions](/v3/teams/#add-or-update-team-repository-permissions) -* [Remove a repository from a team](/v3/teams/#remove-a-repository-from-a-team) +* [List team repositories](/rest/reference/teams#list-team-repositories) +* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository) +* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions) +* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team) {% if currentVersion == "free-pro-team@latest" %} ##### Organization Team Sync -* [List idp groups for a team](/v3/teams/team_sync/#list-idp-groups-for-a-team) -* [Create or update idp group connections](/v3/teams/team_sync/#create-or-update-idp-group-connections) -* [List IdP groups for an organization](/v3/teams/team_sync/#list-idp-groups-for-an-organization) +* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team) +* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections) +* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} ##### Organization Teams -* [List teams](/v3/teams/#list-teams) -* [Create a team](/v3/teams/#create-a-team) -* [Get a team by name](/v3/teams/#get-a-team-by-name) +* [List teams](/rest/reference/teams#list-teams) +* [Create a team](/rest/reference/teams#create-a-team) +* [Get a team by name](/rest/reference/teams#get-a-team-by-name) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -* [Get a team](/v3/teams/#get-a-team) +* [Get a team](/rest/reference/teams#get-a-team) {% endif %} -* [Update a team](/v3/teams/#update-a-team) -* [Delete a team](/v3/teams/#delete-a-team) +* [Update a team](/rest/reference/teams#update-a-team) +* [Delete a team](/rest/reference/teams#delete-a-team) {% if currentVersion == "free-pro-team@latest" %} -* [List pending team invitations](/v3/teams/members/#list-pending-team-invitations) +* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations) {% endif %} -* [List team members](/v3/teams/members/#list-team-members) -* [Get team membership for a user](/v3/teams/members/#get-team-membership-for-a-user) -* [Add or update team membership for a user](/v3/teams/members/#add-or-update-team-membership-for-a-user) -* [Remove team membership for a user](/v3/teams/members/#remove-team-membership-for-a-user) -* [List child teams](/v3/teams/#list-child-teams) -* [List teams for the authenticated user](/v3/teams/#list-teams-for-the-authenticated-user) +* [List team members](/rest/reference/teams#list-team-members) +* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user) +* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) +* [List child teams](/rest/reference/teams#list-child-teams) +* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user) ##### Organisationen -* [List organizations](/v3/orgs/#list-organizations) -* [Get an organization](/v3/orgs/#get-an-organization) -* [Update an organization](/v3/orgs/#update-an-organization) -* [List organization memberships for the authenticated user](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) -* [Get an organization membership for the authenticated user](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) -* [Update an organization membership for the authenticated user](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) -* [List organizations for the authenticated user](/v3/orgs/#list-organizations-for-the-authenticated-user) -* [List organizations for a user](/v3/orgs/#list-organizations-for-a-user) +* [List organizations](/rest/reference/orgs#list-organizations) +* [Get an organization](/rest/reference/orgs#get-an-organization) +* [Update an organization](/rest/reference/orgs#update-an-organization) +* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Credential Authorizations -* [List SAML SSO authorizations for an organization](/v3/orgs/#list-saml-sso-authorizations-for-an-organization) -* [Remove a SAML SSO authorization for an organization](/v3/orgs/#remove-a-saml-sso-authorization-for-an-organization) +* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Scim -* [List SCIM provisioned identities](/v3/scim/#list-scim-provisioned-identities) -* [Provision and invite a SCIM user](/v3/scim/#provision-and-invite-a-scim-user) -* [Get SCIM provisioning information for a user](/v3/scim/#get-scim-provisioning-information-for-a-user) -* [Set SCIM information for a provisioned user](/v3/scim/#set-scim-information-for-a-provisioned-user) -* [Update an attribute for a SCIM user](/v3/scim/#update-an-attribute-for-a-scim-user) -* [Delete a SCIM user from an organization](/v3/scim/#delete-a-scim-user-from-an-organization) +* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities) +* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user) +* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Source Imports -* [Get an import status](/v3/migrations/source_imports/#get-an-import-status) -* [Start an import](/v3/migrations/source_imports/#start-an-import) -* [Update an import](/v3/migrations/source_imports/#update-an-import) -* [Cancel an import](/v3/migrations/source_imports/#cancel-an-import) -* [Get commit authors](/v3/migrations/source_imports/#get-commit-authors) -* [Map a commit author](/v3/migrations/source_imports/#map-a-commit-author) -* [Get large files](/v3/migrations/source_imports/#get-large-files) -* [Update Git LFS preference](/v3/migrations/source_imports/#update-git-lfs-preference) +* [Get an import status](/rest/reference/migrations#get-an-import-status) +* [Start an import](/rest/reference/migrations#start-an-import) +* [Update an import](/rest/reference/migrations#update-an-import) +* [Cancel an import](/rest/reference/migrations#cancel-an-import) +* [Get commit authors](/rest/reference/migrations#get-commit-authors) +* [Map a commit author](/rest/reference/migrations#map-a-commit-author) +* [Get large files](/rest/reference/migrations#get-large-files) +* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference) {% endif %} ##### Project Collaborators -* [List project collaborators](/v3/projects/collaborators/#list-project-collaborators) -* [Add project collaborator](/v3/projects/collaborators/#add-project-collaborator) -* [Remove project collaborator](/v3/projects/collaborators/#remove-project-collaborator) -* [Get project permission for a user](/v3/projects/collaborators/#get-project-permission-for-a-user) +* [List project collaborators](/rest/reference/projects#list-project-collaborators) +* [Add project collaborator](/rest/reference/projects#add-project-collaborator) +* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator) +* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user) ##### Projekte -* [List organization projects](/v3/projects/#list-organization-projects) -* [Create an organization project](/v3/projects/#create-an-organization-project) -* [Get a project](/v3/projects/#get-a-project) -* [Update a project](/v3/projects/#update-a-project) -* [Delete a project](/v3/projects/#delete-a-project) -* [List project columns](/v3/projects/columns/#list-project-columns) -* [Create a project column](/v3/projects/columns/#create-a-project-column) -* [Get a project column](/v3/projects/columns/#get-a-project-column) -* [Update a project column](/v3/projects/columns/#update-a-project-column) -* [Delete a project column](/v3/projects/columns/#delete-a-project-column) -* [List project cards](/v3/projects/cards/#list-project-cards) -* [Create a project card](/v3/projects/cards/#create-a-project-card) -* [Move a project column](/v3/projects/columns/#move-a-project-column) -* [Get a project card](/v3/projects/cards/#get-a-project-card) -* [Update a project card](/v3/projects/cards/#update-a-project-card) -* [Delete a project card](/v3/projects/cards/#delete-a-project-card) -* [Move a project card](/v3/projects/cards/#move-a-project-card) -* [List repository projects](/v3/projects/#list-repository-projects) -* [Create a repository project](/v3/projects/#create-a-repository-project) +* [List organization projects](/rest/reference/projects#list-organization-projects) +* [Create an organization project](/rest/reference/projects#create-an-organization-project) +* [Get a project](/rest/reference/projects#get-a-project) +* [Update a project](/rest/reference/projects#update-a-project) +* [Delete a project](/rest/reference/projects#delete-a-project) +* [List project columns](/rest/reference/projects#list-project-columns) +* [Create a project column](/rest/reference/projects#create-a-project-column) +* [Get a project column](/rest/reference/projects#get-a-project-column) +* [Update a project column](/rest/reference/projects#update-a-project-column) +* [Delete a project column](/rest/reference/projects#delete-a-project-column) +* [List project cards](/rest/reference/projects#list-project-cards) +* [Create a project card](/rest/reference/projects#create-a-project-card) +* [Move a project column](/rest/reference/projects#move-a-project-column) +* [Get a project card](/rest/reference/projects#get-a-project-card) +* [Update a project card](/rest/reference/projects#update-a-project-card) +* [Delete a project card](/rest/reference/projects#delete-a-project-card) +* [Move a project card](/rest/reference/projects#move-a-project-card) +* [List repository projects](/rest/reference/projects#list-repository-projects) +* [Create a repository project](/rest/reference/projects#create-a-repository-project) ##### Pull Comments -* [List review comments on a pull request](/v3/pulls/comments/#list-review-comments-on-a-pull-request) -* [Create a review comment for a pull request](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) -* [List review comments in a repository](/v3/pulls/comments/#list-review-comments-in-a-repository) -* [Get a review comment for a pull request](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) -* [Update a review comment for a pull request](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) -* [Delete a review comment for a pull request](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) +* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository) +* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) ##### Pull Request Review Events -* [Dismiss a review for a pull request](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) -* [Submit a review for a pull request](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) +* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request) ##### Pull Request Review Requests -* [List requested reviewers for a pull request](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) -* [Request reviewers for a pull request](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) -* [Remove requested reviewers from a pull request](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) +* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) ##### Pull Request Reviews -* [List reviews for a pull request](/v3/pulls/reviews/#list-reviews-for-a-pull-request) -* [Create a review for a pull request](/v3/pulls/reviews/#create-a-review-for-a-pull-request) -* [Get a review for a pull request](/v3/pulls/reviews/#get-a-review-for-a-pull-request) -* [Update a review for a pull request](/v3/pulls/reviews/#update-a-review-for-a-pull-request) -* [List comments for a pull request review](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) +* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review) ##### Pulls -* [List pull requests](/v3/pulls/#list-pull-requests) -* [Create a pull request](/v3/pulls/#create-a-pull-request) -* [Get a pull request](/v3/pulls/#get-a-pull-request) -* [Update a pull request](/v3/pulls/#update-a-pull-request) -* [List commits on a pull request](/v3/pulls/#list-commits-on-a-pull-request) -* [List pull requests files](/v3/pulls/#list-pull-requests-files) -* [Check if a pull request has been merged](/v3/pulls/#check-if-a-pull-request-has-been-merged) -* [Merge a pull request (Merge Button)](/v3/pulls/#merge-a-pull-request) +* [List pull requests](/rest/reference/pulls#list-pull-requests) +* [Create a pull request](/rest/reference/pulls#create-a-pull-request) +* [Get a pull request](/rest/reference/pulls#get-a-pull-request) +* [Update a pull request](/rest/reference/pulls#update-a-pull-request) +* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request) +* [List pull requests files](/rest/reference/pulls#list-pull-requests-files) +* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request) ##### Reactions -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/v3/reactions/#delete-a-reaction-legacy){% else %}* [Delete a reaction](/v3/reactions/#delete-a-reaction){% endif %} -* [List reactions for a commit comment](/v3/reactions/#list-reactions-for-a-commit-comment) -* [Create reaction for a commit comment](/v3/reactions/#create-reaction-for-a-commit-comment) -* [List reactions for an issue](/v3/reactions/#list-reactions-for-an-issue) -* [Create reaction for an issue](/v3/reactions/#create-reaction-for-an-issue) -* [List reactions for an issue comment](/v3/reactions/#list-reactions-for-an-issue-comment) -* [Create reaction for an issue comment](/v3/reactions/#create-reaction-for-an-issue-comment) -* [List reactions for a pull request review comment](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) -* [Create reaction for a pull request review comment](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) -* [List reactions for a team discussion comment](/v3/reactions/#list-reactions-for-a-team-discussion-comment) -* [Create reaction for a team discussion comment](/v3/reactions/#create-reaction-for-a-team-discussion-comment) -* [List reactions for a team discussion](/v3/reactions/#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/v3/reactions/#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a commit comment reaction](/v3/reactions/#delete-a-commit-comment-reaction) -* [Delete an issue reaction](/v3/reactions/#delete-an-issue-reaction) -* [Delete a reaction to a commit comment](/v3/reactions/#delete-an-issue-comment-reaction) -* [Delete a pull request comment reaction](/v3/reactions/#delete-a-pull-request-comment-reaction) -* [Delete team discussion reaction](/v3/reactions/#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/v3/reactions/#delete-team-discussion-comment-reaction){% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %} +* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue) +* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue) +* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction) +* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction) +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} ##### Repositorys -* [Repositorys einer Organisation auflisten](/v3/repos/#list-organization-repositories) -* [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) -* [Get a repository](/v3/repos/#get-a-repository) -* [Update a repository](/v3/repos/#update-a-repository) -* [Delete a repository](/v3/repos/#delete-a-repository) -* [Compare two commits](/v3/repos/commits/#compare-two-commits) -* [List repository contributors](/v3/repos/#list-repository-contributors) +* [Repositorys einer Organisation auflisten](/rest/reference/repos#list-organization-repositories) +* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [Get a repository](/rest/reference/repos#get-a-repository) +* [Update a repository](/rest/reference/repos#update-a-repository) +* [Delete a repository](/rest/reference/repos#delete-a-repository) +* [Compare two commits](/rest/reference/repos#compare-two-commits) +* [List repository contributors](/rest/reference/repos#list-repository-contributors) * [List forks](/rest/reference/repos#list-forks) -* [Create a fork](/v3/repos/forks/#create-a-fork) -* [List repository languages](/v3/repos/#list-repository-languages) -* [List repository tags](/v3/repos/#list-repository-tags) -* [List repository teams](/v3/repos/#list-repository-teams) -* [Transfer a repository](/v3/repos/#transfer-a-repository) -* [List public repositories](/v3/repos/#list-public-repositories) -* [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) -* [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -* [Create repository using a repository template](/v3/repos/#create-repository-using-a-repository-template) +* [Create a fork](/rest/reference/repos#create-a-fork) +* [List repository languages](/rest/reference/repos#list-repository-languages) +* [List repository tags](/rest/reference/repos#list-repository-tags) +* [List repository teams](/rest/reference/repos#list-repository-teams) +* [Transfer a repository](/rest/reference/repos#transfer-a-repository) +* [List public repositories](/rest/reference/repos#list-public-repositories) +* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user) +* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template) ##### Repository Activity @@ -643,116 +643,116 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Repository Automated Security Fixes -* [Enable automated security fixes](/v3/repos/#enable-automated-security-fixes) -* [Disable automated security fixes](/v3/repos/#disable-automated-security-fixes) +* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes) +* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes) {% endif %} ##### Repository Branches -* [List branches](/v3/repos/branches/#list-branches) -* [Get a branch](/v3/repos/branches/#get-a-branch) -* [Get branch protection](/v3/repos/branches/#get-branch-protection) -* [Update branch protection](/v3/repos/branches/#update-branch-protection) -* [Delete branch protection](/v3/repos/branches/#delete-branch-protection) -* [Get admin branch protection](/v3/repos/branches/#get-admin-branch-protection) -* [Set admin branch protection](/v3/repos/branches/#set-admin-branch-protection) -* [Delete admin branch protection](/v3/repos/branches/#delete-admin-branch-protection) -* [Get pull request review protection](/v3/repos/branches/#get-pull-request-review-protection) -* [Update pull request review protection](/v3/repos/branches/#update-pull-request-review-protection) -* [Delete pull request review protection](/v3/repos/branches/#delete-pull-request-review-protection) -* [Get commit signature protection](/v3/repos/branches/#get-commit-signature-protection) -* [Create commit signature protection](/v3/repos/branches/#create-commit-signature-protection) -* [Delete commit signature protection](/v3/repos/branches/#delete-commit-signature-protection) -* [Get status checks protection](/v3/repos/branches/#get-status-checks-protection) -* [Update status check protection](/v3/repos/branches/#update-status-check-protection) -* [Remove status check protection](/v3/repos/branches/#remove-status-check-protection) -* [Get all status check contexts](/v3/repos/branches/#get-all-status-check-contexts) -* [Add status check contexts](/v3/repos/branches/#add-status-check-contexts) -* [Set status check contexts](/v3/repos/branches/#set-status-check-contexts) -* [Remove status check contexts](/v3/repos/branches/#remove-status-check-contexts) -* [Get access restrictions](/v3/repos/branches/#get-access-restrictions) -* [Delete access restrictions](/v3/repos/branches/#delete-access-restrictions) -* [List teams with access to the protected branch](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) -* [Add team access restrictions](/v3/repos/branches/#add-team-access-restrictions) -* [Set team access restrictions](/v3/repos/branches/#set-team-access-restrictions) -* [Remove team access restriction](/v3/repos/branches/#remove-team-access-restrictions) -* [List user restrictions of protected branch](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) -* [Add user access restrictions](/v3/repos/branches/#add-user-access-restrictions) -* [Set user access restrictions](/v3/repos/branches/#set-user-access-restrictions) -* [Remove user access restrictions](/v3/repos/branches/#remove-user-access-restrictions) -* [Merge a branch](/v3/repos/merging/#merge-a-branch) +* [List branches](/rest/reference/repos#list-branches) +* [Get a branch](/rest/reference/repos#get-a-branch) +* [Get branch protection](/rest/reference/repos#get-branch-protection) +* [Update branch protection](/rest/reference/repos#update-branch-protection) +* [Delete branch protection](/rest/reference/repos#delete-branch-protection) +* [Get admin branch protection](/rest/reference/repos#get-admin-branch-protection) +* [Set admin branch protection](/rest/reference/repos#set-admin-branch-protection) +* [Delete admin branch protection](/rest/reference/repos#delete-admin-branch-protection) +* [Get pull request review protection](/rest/reference/repos#get-pull-request-review-protection) +* [Update pull request review protection](/rest/reference/repos#update-pull-request-review-protection) +* [Delete pull request review protection](/rest/reference/repos#delete-pull-request-review-protection) +* [Get commit signature protection](/rest/reference/repos#get-commit-signature-protection) +* [Create commit signature protection](/rest/reference/repos#create-commit-signature-protection) +* [Delete commit signature protection](/rest/reference/repos#delete-commit-signature-protection) +* [Get status checks protection](/rest/reference/repos#get-status-checks-protection) +* [Update status check protection](/rest/reference/repos#update-status-check-protection) +* [Remove status check protection](/rest/reference/repos#remove-status-check-protection) +* [Get all status check contexts](/rest/reference/repos#get-all-status-check-contexts) +* [Add status check contexts](/rest/reference/repos#add-status-check-contexts) +* [Set status check contexts](/rest/reference/repos#set-status-check-contexts) +* [Remove status check contexts](/rest/reference/repos#remove-status-check-contexts) +* [Get access restrictions](/rest/reference/repos#get-access-restrictions) +* [Delete access restrictions](/rest/reference/repos#delete-access-restrictions) +* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [Add team access restrictions](/rest/reference/repos#add-team-access-restrictions) +* [Set team access restrictions](/rest/reference/repos#set-team-access-restrictions) +* [Remove team access restriction](/rest/reference/repos#remove-team-access-restrictions) +* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [Add user access restrictions](/rest/reference/repos#add-user-access-restrictions) +* [Set user access restrictions](/rest/reference/repos#set-user-access-restrictions) +* [Remove user access restrictions](/rest/reference/repos#remove-user-access-restrictions) +* [Merge a branch](/rest/reference/repos#merge-a-branch) ##### Repository Collaborators -* [List repository collaborators](/v3/repos/collaborators/#list-repository-collaborators) -* [Check if a user is a repository collaborator](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) -* [Add a repository collaborator](/v3/repos/collaborators/#add-a-repository-collaborator) -* [Remove a repository collaborator](/v3/repos/collaborators/#remove-a-repository-collaborator) -* [Get repository permissions for a user](/v3/repos/collaborators/#get-repository-permissions-for-a-user) +* [List repository collaborators](/rest/reference/repos#list-repository-collaborators) +* [Check if a user is a repository collaborator](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator) +* [Remove a repository collaborator](/rest/reference/repos#remove-a-repository-collaborator) +* [Get repository permissions for a user](/rest/reference/repos#get-repository-permissions-for-a-user) ##### Repository Commit Comments -* [List commit comments for a repository](/v3/repos/comments/#list-commit-comments-for-a-repository) -* [Get a commit comment](/v3/repos/comments/#get-a-commit-comment) -* [Update a commit comment](/v3/repos/comments/#update-a-commit-comment) -* [Delete a commit comment](/v3/repos/comments/#delete-a-commit-comment) -* [List commit comments](/v3/repos/comments/#list-commit-comments) -* [Create a commit comment](/v3/repos/comments/#create-a-commit-comment) +* [List commit comments for a repository](/rest/reference/repos#list-commit-comments-for-a-repository) +* [Get a commit comment](/rest/reference/repos#get-a-commit-comment) +* [Update a commit comment](/rest/reference/repos#update-a-commit-comment) +* [Delete a commit comment](/rest/reference/repos#delete-a-commit-comment) +* [List commit comments](/rest/reference/repos#list-commit-comments) +* [Create a commit comment](/rest/reference/repos#create-a-commit-comment) ##### Repository Commits -* [List commits](/v3/repos/commits/#list-commits) -* [Get a commit](/v3/repos/commits/#get-a-commit) -* [List branches for head commit](/v3/repos/commits/#list-branches-for-head-commit) -* [List pull requests associated with commit](/v3/repos/commits/#list-pull-requests-associated-with-commit) +* [List commits](/rest/reference/repos#list-commits) +* [Get a commit](/rest/reference/repos#get-a-commit) +* [List branches for head commit](/rest/reference/repos#list-branches-for-head-commit) +* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit) ##### Repository Community -* [Get the code of conduct for a repository](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) +* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% if currentVersion == "free-pro-team@latest" %} -* [Get community profile metrics](/v3/repos/community/#get-community-profile-metrics) +* [Get community profile metrics](/rest/reference/repos#get-community-profile-metrics) {% endif %} ##### Repository Contents -* [Download a repository archive](/v3/repos/contents/#download-a-repository-archive) -* [Get repository content](/v3/repos/contents/#get-repository-content) -* [Create or update file contents](/v3/repos/contents/#create-or-update-file-contents) -* [Delete a file](/v3/repos/contents/#delete-a-file) -* [Get a repository README](/v3/repos/contents/#get-a-repository-readme) -* [Get the license for a repository](/v3/licenses/#get-the-license-for-a-repository) +* [Download a repository archive](/rest/reference/repos#download-a-repository-archive) +* [Get repository content](/rest/reference/repos#get-repository-content) +* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents) +* [Delete a file](/rest/reference/repos#delete-a-file) +* [Get a repository README](/rest/reference/repos#get-a-repository-readme) +* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Repository Event Dispatches -* [Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event) +* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event) {% endif %} ##### Repository Hooks -* [List repository webhooks](/v3/repos/hooks/#list-repository-webhooks) -* [Create a repository webhook](/v3/repos/hooks/#create-a-repository-webhook) -* [Get a repository webhook](/v3/repos/hooks/#get-a-repository-webhook) -* [Update a repository webhook](/v3/repos/hooks/#update-a-repository-webhook) -* [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) -* [Ping a repository webhook](/v3/repos/hooks/#ping-a-repository-webhook) -* [Test the push repository webhook](/v3/repos/hooks/#test-the-push-repository-webhook) +* [List repository webhooks](/rest/reference/repos#list-repository-webhooks) +* [Create a repository webhook](/rest/reference/repos#create-a-repository-webhook) +* [Get a repository webhook](/rest/reference/repos#get-a-repository-webhook) +* [Update a repository webhook](/rest/reference/repos#update-a-repository-webhook) +* [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) +* [Ping a repository webhook](/rest/reference/repos#ping-a-repository-webhook) +* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook) ##### Repository Invitations -* [List repository invitations](/v3/repos/invitations/#list-repository-invitations) -* [Update a repository invitation](/v3/repos/invitations/#update-a-repository-invitation) -* [Delete a repository invitation](/v3/repos/invitations/#delete-a-repository-invitation) -* [List repository invitations for the authenticated user](/v3/repos/invitations/#list-repository-invitations-for-the-authenticated-user) -* [Accept a repository invitation](/v3/repos/invitations/#accept-a-repository-invitation) -* [Decline a repository invitation](/v3/repos/invitations/#decline-a-repository-invitation) +* [List repository invitations](/rest/reference/repos#list-repository-invitations) +* [Update a repository invitation](/rest/reference/repos#update-a-repository-invitation) +* [Delete a repository invitation](/rest/reference/repos#delete-a-repository-invitation) +* [List repository invitations for the authenticated user](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [Accept a repository invitation](/rest/reference/repos#accept-a-repository-invitation) +* [Decline a repository invitation](/rest/reference/repos#decline-a-repository-invitation) ##### Repository Keys -* [List deploy keys](/v3/repos/keys/#list-deploy-keys) -* [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) -* [Get a deploy key](/v3/repos/keys/#get-a-deploy-key) -* [Delete a deploy key](/v3/repos/keys/#delete-a-deploy-key) +* [List deploy keys](/rest/reference/repos#list-deploy-keys) +* [Create a deploy key](/rest/reference/repos#create-a-deploy-key) +* [Get a deploy key](/rest/reference/repos#get-a-deploy-key) +* [Delete a deploy key](/rest/reference/repos#delete-a-deploy-key) ##### Repository Pages @@ -790,144 +790,144 @@ While most of your API interaction should occur using your server-to-server inst ##### Repository Stats -* [Get the weekly commit activity](/v3/repos/statistics/#get-the-weekly-commit-activity) -* [Get the last year of commit activity](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -* [Get all contributor commit activity](/v3/repos/statistics/#get-all-contributor-commit-activity) -* [Get the weekly commit count](/v3/repos/statistics/#get-the-weekly-commit-count) -* [Get the hourly commit count for each day](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +* [Get the weekly commit activity](/rest/reference/repos#get-the-weekly-commit-activity) +* [Get the last year of commit activity](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [Get all contributor commit activity](/rest/reference/repos#get-all-contributor-commit-activity) +* [Get the weekly commit count](/rest/reference/repos#get-the-weekly-commit-count) +* [Get the hourly commit count for each day](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) {% if currentVersion == "free-pro-team@latest" %} ##### Repository Vulnerability Alerts -* [Enable vulnerability alerts](/v3/repos/#enable-vulnerability-alerts) -* [Disable vulnerability alerts](/v3/repos/#disable-vulnerability-alerts) +* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts) +* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts) {% endif %} ##### Root -* [Root endpoint](/v3/#root-endpoint) -* [Emojis](/v3/emojis/#emojis) -* [Get rate limit status for the authenticated user](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) +* [Root endpoint](/rest#root-endpoint) +* [Emojis](/rest/reference/emojis#emojis) +* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) ##### Suche -* [Search code](/v3/search/#search-code) -* [Search commits](/v3/search/#search-commits) -* [Search labels](/v3/search/#search-labels) -* [Repositorys suchen](/v3/search/#search-repositories) -* [Search topics](/v3/search/#search-topics) -* [Search users](/v3/search/#search-users) +* [Search code](/rest/reference/search#search-code) +* [Search commits](/rest/reference/search#search-commits) +* [Search labels](/rest/reference/search#search-labels) +* [Repositorys suchen](/rest/reference/search#search-repositories) +* [Search topics](/rest/reference/search#search-topics) +* [Search users](/rest/reference/search#search-users) ##### Status -* [Get the combined status for a specific reference](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) -* [List commit statuses for a reference](/v3/repos/statuses/#list-commit-statuses-for-a-reference) -* [Create a commit status](/v3/repos/statuses/#create-a-commit-status) +* [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [List commit statuses for a reference](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [Create a commit status](/rest/reference/repos#create-a-commit-status) ##### Team Discussions -* [List discussions](/v3/teams/discussions/#list-discussions) -* [Create a discussion](/v3/teams/discussions/#create-a-discussion) -* [Get a discussion](/v3/teams/discussions/#get-a-discussion) -* [Update a discussion](/v3/teams/discussions/#update-a-discussion) -* [Delete a discussion](/v3/teams/discussions/#delete-a-discussion) -* [List discussion comments](/v3/teams/discussion_comments/#list-discussion-comments) -* [Create a discussion comment](/v3/teams/discussion_comments/#create-a-discussion-comment) -* [Get a discussion comment](/v3/teams/discussion_comments/#get-a-discussion-comment) -* [Update a discussion comment](/v3/teams/discussion_comments/#update-a-discussion-comment) -* [Delete a discussion comment](/v3/teams/discussion_comments/#delete-a-discussion-comment) +* [List discussions](/rest/reference/teams#list-discussions) +* [Create a discussion](/rest/reference/teams#create-a-discussion) +* [Get a discussion](/rest/reference/teams#get-a-discussion) +* [Update a discussion](/rest/reference/teams#update-a-discussion) +* [Delete a discussion](/rest/reference/teams#delete-a-discussion) +* [List discussion comments](/rest/reference/teams#list-discussion-comments) +* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment) +* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment) +* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment) +* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment) ##### Themen -* [Get all repository topics](/v3/repos#get-all-repository-topics) -* [Replace all repository topics](/v3/repos/#replace-all-repository-topics) +* [Get all repository topics](/rest/reference/repos#get-all-repository-topics) +* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics) {% if currentVersion == "free-pro-team@latest" %} ##### Traffic -* [Get repository clones](/v3/repos/traffic/#get-repository-clones) -* [Get top referral paths](/v3/repos/traffic/#get-top-referral-paths) -* [Get top referral sources](/v3/repos/traffic/#get-top-referral-sources) -* [Get page views](/v3/repos/traffic/#get-page-views) +* [Get repository clones](/rest/reference/repos#get-repository-clones) +* [Get top referral paths](/rest/reference/repos#get-top-referral-paths) +* [Get top referral sources](/rest/reference/repos#get-top-referral-sources) +* [Get page views](/rest/reference/repos#get-page-views) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### User Blocking -* [List users blocked by the authenticated user](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) -* [Check if a user is blocked by the authenticated user](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) -* [List users blocked by an organization](/v3/orgs/blocking/#list-users-blocked-by-an-organization) -* [Check if a user is blocked by an organization](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) -* [Block a user from an organization](/v3/orgs/blocking/#block-a-user-from-an-organization) -* [Unblock a user from an organization](/v3/orgs/blocking/#unblock-a-user-from-an-organization) -* [Block a user](/v3/users/blocking/#block-a-user) -* [Unblock a user](/v3/users/blocking/#unblock-a-user) +* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization) +* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [Block a user](/rest/reference/users#block-a-user) +* [Unblock a user](/rest/reference/users#unblock-a-user) {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ##### User Emails {% if currentVersion == "free-pro-team@latest" %} -* [Set primary email visibility for the authenticated user](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) +* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %} -* [List email addresses for the authenticated user](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) -* [Add email address(es)](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) -* [Delete email address(es)](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) -* [List public email addresses for the authenticated user](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) +* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) {% endif %} ##### User Followers -* [List followers of a user](/v3/users/followers/#list-followers-of-a-user) -* [List the people a user follows](/v3/users/followers/#list-the-people-a-user-follows) -* [Check if a person is followed by the authenticated user](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) -* [Follow a user](/v3/users/followers/#follow-a-user) -* [Unfollow a user](/v3/users/followers/#unfollow-a-user) -* [Check if a user follows another user](/v3/users/followers/#check-if-a-user-follows-another-user) +* [List followers of a user](/rest/reference/users#list-followers-of-a-user) +* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows) +* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [Follow a user](/rest/reference/users#follow-a-user) +* [Unfollow a user](/rest/reference/users#unfollow-a-user) +* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user) ##### User Gpg Keys -* [List GPG keys for the authenticated user](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) -* [Create a GPG key for the authenticated user](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) -* [Get a GPG key for the authenticated user](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) -* [Delete a GPG key for the authenticated user](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) -* [List gpg keys for a user](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) +* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user) ##### User Public Keys -* [List public SSH keys for the authenticated user](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) -* [Create a public SSH key for the authenticated user](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) -* [Get a public SSH key for the authenticated user](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) -* [Delete a public SSH key for the authenticated user](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) -* [List public keys for a user](/v3/users/keys/#list-public-keys-for-a-user) +* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user) ##### Benutzer -* [Get the authenticated user](/v3/users/#get-the-authenticated-user) -* [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) +* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) +* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% endif %} -* [List users](/v3/users/#list-users) -* [Get a user](/v3/users/#get-a-user) +* [List users](/rest/reference/users#list-users) +* [Get a user](/rest/reference/users#get-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Workflow Runs -* [List workflow runs for a repository](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) -* [Get a workflow run](/v3/actions/workflow-runs/#get-a-workflow-run) -* [Cancel a workflow run](/v3/actions/workflow-runs/#cancel-a-workflow-run) -* [Download workflow run logs](/v3/actions/workflow-runs/#download-workflow-run-logs) -* [Delete workflow run logs](/v3/actions/workflow-runs/#delete-workflow-run-logs) -* [Re run a workflow](/v3/actions/workflow-runs/#re-run-a-workflow) -* [List workflow runs](/v3/actions/workflow-runs/#list-workflow-runs) -* [Get workflow run usage](/v3/actions/workflow-runs/#get-workflow-run-usage) +* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [Get a workflow run](/rest/reference/actions#get-a-workflow-run) +* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run) +* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs) +* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs) +* [Re run a workflow](/rest/reference/actions#re-run-a-workflow) +* [List workflow runs](/rest/reference/actions#list-workflow-runs) +* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Workflows -* [List repository workflows](/v3/actions/workflows/#list-repository-workflows) -* [Get a workflow](/v3/actions/workflows/#get-a-workflow) -* [Get workflow usage](/v3/actions/workflows/#get-workflow-usage) +* [List repository workflows](/rest/reference/actions#list-repository-workflows) +* [Get a workflow](/rest/reference/actions#get-a-workflow) +* [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} diff --git a/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 0706b40b6e..2c83c9cdbe 100644 --- a/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -23,7 +23,7 @@ This article provides guidelines for existing integrators who are considering mi - Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). - Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration. - Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation. -- Open Source community support is available through [Octokit libraries](/v3/libraries/) and other frameworks such as [Probot](https://probot.github.io/). +- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/). - Integrators building GitHub Apps have opportunities to adopt earlier access to APIs. ### Converting an OAuth App to a GitHub App @@ -42,13 +42,13 @@ These guidelines assume that you have a registered OAuth App{% if currentVersion #### Review the available API endpoints for GitHub Apps -While the majority of [REST API](/v3) endpoints and [GraphQL](/v4) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/v3/apps/available-endpoints/) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. +While the majority of [REST API](/rest) endpoints and [GraphQL](/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_app %}s. #### Design to stay within API rate limits -GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/v3/#conditional-requests) or consolidate requests by using the [GraphQL API V4](/v4/). +GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest#conditional-requests) or consolidate requests by using the [GraphQL API V4](/graphql). #### Register a new GitHub App @@ -56,7 +56,7 @@ Once you've decided to make the switch to Github Apps, you'll need to [create a #### Determine the permissions your app requires -When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/v3/apps/permissions/)" for a list of the permissions needed for each endpoint available to GitHub Apps. +When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps. In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality. @@ -90,11 +90,11 @@ Once you've made the transition from an OAuth App to a GitHub App, you will need https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) and [List organization repositories](/v3/repos/#list-organization-repositories) endpoints. +You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints. #### Remove any unnecessary repository hooks -Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) on those repositories that were created by your OAuth App. +Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) on those repositories that were created by your OAuth App. #### Encourage users to revoke access to your OAuth app diff --git a/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md index 8ec5ae084d..3fb1433214 100644 --- a/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -25,7 +25,7 @@ To renew an expiring user-to-server access token, you can exchange the `refresh_ `POST https://github.com/login/oauth/access_token` -This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/v3/guides/basics-of-authentication/#providing-a-callback)." +This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." #### Parameters diff --git a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md index b54804d435..2902008e0d 100644 --- a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md @@ -41,13 +41,13 @@ X-Accepted-OAuth-Scopes: user | Name | Beschreibung | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/v3/enterprise-admin).{% endif %} +| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} | **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/v3/repos/deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/v3/code-scanning).{% endif %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | |  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | diff --git a/translations/de-DE/content/developers/apps/setting-permissions-for-github-apps.md b/translations/de-DE/content/developers/apps/setting-permissions-for-github-apps.md index f63d641cdb..c7b9470177 100644 --- a/translations/de-DE/content/developers/apps/setting-permissions-for-github-apps.md +++ b/translations/de-DE/content/developers/apps/setting-permissions-for-github-apps.md @@ -17,4 +17,4 @@ When you create a GitHub App, you can select the permissions it needs to access By default, GitHub Apps have `Read-only` access to metadata endpoints. Metadata is a collection of read-only endpoints that provide general information about resources that the authorized installation can access. -{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/v3/apps/permissions/#metadata-permissions)." +{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/rest/reference/permissions-required-for-github-apps#metadata-permissions)." diff --git a/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index 47531d7ba0..b0afd855de 100644 --- a/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -37,7 +37,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [Webhooks](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -220,7 +220,7 @@ end #### Define a route handler -An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You'll won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. ``` ruby post '/event_handler' do diff --git a/translations/de-DE/content/developers/apps/using-content-attachments.md b/translations/de-DE/content/developers/apps/using-content-attachments.md index 852f7fc873..296e36840c 100644 --- a/translations/de-DE/content/developers/apps/using-content-attachments.md +++ b/translations/de-DE/content/developers/apps/using-content-attachments.md @@ -55,7 +55,7 @@ The content attachment flow shows you the relationship between the URL in the is } ``` -**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/v3/apps/installations/#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -116,7 +116,7 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -For more information on `node_id`, see "[Using Global Node IDs](/v4/guides/using-global-node-ids/)." +For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ### Example using Probot and GitHub App Manifests diff --git a/translations/de-DE/content/developers/apps/using-the-github-api-in-your-app.md b/translations/de-DE/content/developers/apps/using-the-github-api-in-your-app.md index 7064fb3606..91a2677db0 100644 --- a/translations/de-DE/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/de-DE/content/developers/apps/using-the-github-api-in-your-app.md @@ -31,7 +31,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [Webhooks](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -143,11 +143,11 @@ Before the label can be _added_ anywhere, you'll need to _create_ the custom lab {% tip %} -**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/v3/issues/labels/#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. +**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. {% endtip %} -Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/v3/issues/labels/#add-labels-to-an-issue). +Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue). ### Schritt 4. Add label handling diff --git a/translations/de-DE/content/developers/github-marketplace/billing-customers.md b/translations/de-DE/content/developers/github-marketplace/billing-customers.md index a98af4e408..301f6bab3d 100644 --- a/translations/de-DE/content/developers/github-marketplace/billing-customers.md +++ b/translations/de-DE/content/developers/github-marketplace/billing-customers.md @@ -25,7 +25,7 @@ Customers must be able to perform the following actions from your app's website: Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." -You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). +You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). #### Upgrades diff --git a/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 5ec08cc03b..5cfbcccaff 100644 --- a/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -68,7 +68,7 @@ After the customer completes the authorization, your app receives an OAuth acces ### Schritt 4. Provisioning customer accounts -Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. +Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. {% data reusables.marketplace.marketplace-double-purchases %} @@ -76,6 +76,6 @@ If the purchase is for an organization and per-user, you can prompt the customer You can customize the way that organization members receive access to your app. Here are a few suggestions: -**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/v3/orgs/members/#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. +**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/rest/reference/orgs#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. **Per-unit pricing:** One method of provisioning per-unit seats is to allow users to occupy a seat as they log in to the app. Once the customer hits the seat count threshold, your app can alert the user that they need to upgrade through {% data variables.product.prodname_marketplace %}. diff --git a/translations/de-DE/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/de-DE/content/developers/github-marketplace/handling-plan-cancellations.md index 47d8c8b654..0714aa0529 100644 --- a/translations/de-DE/content/developers/github-marketplace/handling-plan-cancellations.md +++ b/translations/de-DE/content/developers/github-marketplace/handling-plan-cancellations.md @@ -28,6 +28,6 @@ When a customer cancels a free or paid plan, your app must perform these steps t {% note %} -**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." {% endnote %} diff --git a/translations/de-DE/content/developers/github-marketplace/handling-plan-changes.md b/translations/de-DE/content/developers/github-marketplace/handling-plan-changes.md index 9987c8c62f..a472324684 100644 --- a/translations/de-DE/content/developers/github-marketplace/handling-plan-changes.md +++ b/translations/de-DE/content/developers/github-marketplace/handling-plan-changes.md @@ -54,7 +54,7 @@ https://www.github.com/marketplace//upgrade// For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page. -Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/v3/apps/marketplace/#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. +Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. {% note %} diff --git a/translations/de-DE/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md b/translations/de-DE/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md index 5ad1d2f177..db3482b992 100644 --- a/translations/de-DE/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md +++ b/translations/de-DE/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md @@ -13,10 +13,10 @@ versions: Here are some useful endpoints available for Marketplace listings: -* [List plans](/v3/apps/marketplace/#list-plans) -* [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan) -* [Get a subscription plan for an account](/v3/apps/marketplace/#get-a-subscription-plan-for-an-account) -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [List plans](/rest/reference/apps#list-plans) +* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan) +* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API: @@ -25,6 +25,6 @@ See these pages for details on how to authenticate when using the {% data variab {% note %} -**Note:** [Rate limits for the REST API](/v3/#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. +**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. {% endnote %} diff --git a/translations/de-DE/content/developers/github-marketplace/testing-your-app.md b/translations/de-DE/content/developers/github-marketplace/testing-your-app.md index 352aaf9c5e..09e79b1a7a 100644 --- a/translations/de-DE/content/developers/github-marketplace/testing-your-app.md +++ b/translations/de-DE/content/developers/github-marketplace/testing-your-app.md @@ -37,7 +37,7 @@ Your testing scenarios may require setting up listing plans that offer free tria ### Testing APIs -For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/v3/apps/marketplace/#github-marketplace). +For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace). ### Testing webhooks diff --git a/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 4cda848ec1..49d83c1c6b 100644 --- a/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -31,15 +31,15 @@ Each `marketplace_purchase` webhook payload will have the following information: The `marketplace_purchase` object has the following keys: -| Schlüssel | Typ | Beschreibung | -| -------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Konto` | `Objekt` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/v3/users/#get-the-authenticated-user) endpoint. | -| `billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. | -| `unit_count` | `integer` | Number of units purchased. | -| `on_free_trial` | `boolean` | `true` when the `account` is on a free trial. | -| `free_trial_ends_on` | `string` | The date the free trial will expire. | -| `next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. | -| `plan` | `Objekt` | The plan purchased by the `user` or `organization`. | +| Schlüssel | Typ | Beschreibung | +| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Konto` | `Objekt` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint. | +| `billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. | +| `unit_count` | `integer` | Number of units purchased. | +| `on_free_trial` | `boolean` | `true` when the `account` is on a free trial. | +| `free_trial_ends_on` | `string` | The date the free trial will expire. | +| `next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. | +| `plan` | `Objekt` | The plan purchased by the `user` or `organization`. | The `plan` object has the following keys: diff --git a/translations/de-DE/content/developers/overview/about-githubs-apis.md b/translations/de-DE/content/developers/overview/about-githubs-apis.md index 39e74b19f1..0d647b78cb 100644 --- a/translations/de-DE/content/developers/overview/about-githubs-apis.md +++ b/translations/de-DE/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/v3/) and the [GraphQL API](/v4/). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). -When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). +When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). -For information on using the GraphQL API, see the [v4 docs](/v4/). +For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/de-DE/content/developers/webhooks-and-events/about-webhooks.md b/translations/de-DE/content/developers/webhooks-and-events/about-webhooks.md index 869ef91377..2bdc23e09b 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/de-DE/content/developers/webhooks-and-events/about-webhooks.md @@ -31,4 +31,4 @@ See "[Webhook event payloads](/webhooks/event-payloads)" for the list of availab For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. [org-hooks]: /rest/reference/orgs#webhooks/ -[repo-hooks]: /v3/repos/hooks/ +[repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/de-DE/content/developers/webhooks-and-events/creating-webhooks.md b/translations/de-DE/content/developers/webhooks-and-events/creating-webhooks.md index f88b2ad740..f49e68d039 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/creating-webhooks.md +++ b/translations/de-DE/content/developers/webhooks-and-events/creating-webhooks.md @@ -65,5 +65,5 @@ When you're finished, click **Add webhook**. Puh! Now that you created the webho To configure a webhook for all events, use the wildcard (`*`) character to specify the webhook events. When you add the wildcard event, we'll replace any existing events you have configured with the wildcard event and send you payloads for all supported events. You'll also automatically get any new events we might add in the future. [webhooks-overview]: /webhooks/ -[webhook-api]: /v3/repos/hooks/ +[webhook-api]: /rest/reference/repos#hooks [hooks-api]: /webhooks/#events diff --git a/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md b/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md index 45087e2bf8..8144b798da 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md @@ -40,7 +40,7 @@ The event objects returned from the Events API endpoints have the same structure #### Example WatchEvent event object -This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/v3/activity/events). +This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events). ``` Status: 200 OK @@ -198,22 +198,22 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -| Schlüssel | Typ | Beschreibung | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `push_id` | `integer` | Unique identifier for the push. | -| `size` | `integer` | The number of commits in the push. | -| `distinct_size` | `integer` | The number of distinct commits in the push. | -| `ref` | `string` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/main`. | -| `Head` | `string` | The SHA of the most recent commit on `ref` after the push. | -| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][sha]` | `string` | The SHA of the commit. | -| `commits[][message]` | `string` | The commit message. | -| `commits[][author]` | `Objekt` | The git author of the commit. | -| `commits[][author][name]` | `string` | The git author's name. | -| `commits[][author][email]` | `string` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| Schlüssel | Typ | Beschreibung | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `push_id` | `integer` | Unique identifier for the push. | +| `size` | `integer` | The number of commits in the push. | +| `distinct_size` | `integer` | The number of distinct commits in the push. | +| `ref` | `string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `Head` | `string` | The SHA of the most recent commit on `ref` after the push. | +| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][sha]` | `string` | The SHA of the commit. | +| `commits[][message]` | `string` | The commit message. | +| `commits[][author]` | `Objekt` | The git author of the commit. | +| `commits[][author][name]` | `string` | The git author's name. | +| `commits[][author][email]` | `string` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | ### ReleaseEvent diff --git a/translations/de-DE/content/developers/webhooks-and-events/issue-event-types.md b/translations/de-DE/content/developers/webhooks-and-events/issue-event-types.md index 82ea0715ce..3a0487ec74 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/de-DE/content/developers/webhooks-and-events/issue-event-types.md @@ -10,7 +10,7 @@ versions: --- -Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/v3/issues/events) and the [Timeline Events API](/v3/issues/timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. +Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. @@ -129,7 +129,7 @@ A comment was added to the issue or pull request. | `html_url` | `string` | The HTML URL of the issue comment. | | `issue_url` | `string` | The HTML URL of the issue. | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `Benutzer` | `Objekt` | The person who commented on the issue. | | `created_at` | `string` | The timestamp indicating when the comment was added. | | `updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated. | @@ -152,19 +152,19 @@ A commit was added to the pull request's `HEAD` branch. {% data reusables.issue-events.timeline_events_object_properties %} -| Name | Typ | Beschreibung | -| -------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `sha` | `string` | The SHA of the commit in the pull request. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `string` | The REST API URL to retrieve the commit. | -| `html_url` | `string` | The HTML URL of the commit. | -| `Autor` | `Objekt` | The person who authored the commit. | -| `Beitragender` | `Objekt` | The person who committed the commit on behalf of the author. | -| `Struktur` | `Objekt` | The Git tree of the commit. | -| `message` | `string` | The commit message. | -| `parents` | `array of objects` | A list of parent commits. | -| `verfication` | `Objekt` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/v3/git/commits/#signature-verification-object)." | -| `event` | `string` | The event value is `"committed"`. | +| Name | Typ | Beschreibung | +| -------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sha` | `string` | The SHA of the commit in the pull request. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `string` | The REST API URL to retrieve the commit. | +| `html_url` | `string` | The HTML URL of the commit. | +| `Autor` | `Objekt` | The person who authored the commit. | +| `Beitragender` | `Objekt` | The person who committed the commit on behalf of the author. | +| `Struktur` | `Objekt` | The Git tree of the commit. | +| `message` | `string` | The commit message. | +| `parents` | `array of objects` | A list of parent commits. | +| `verfication` | `Objekt` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#signature-verification-object)." | +| `event` | `string` | The event value is `"committed"`. | ### connected @@ -583,7 +583,7 @@ The pull request was reviewed. | Name | Typ | Beschreibung | | -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `Benutzer` | `Objekt` | The person who commented on the issue. | | `Text` | `string` | The review summary text. | | `commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review. | diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md index a69238f4bd..983d1ee06a 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -33,7 +33,7 @@ Each webhook event payload also contains properties unique to the event. You can {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)." -The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/v3/activity/events/). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. +The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. {% tip %} @@ -45,14 +45,14 @@ The unique properties for a webhook event are the same properties you'll find in HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: -| Header | Beschreibung | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | Name of the event that triggered the delivery. | +| Header | Beschreibung | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-GitHub-Event` | Name of the event that triggered the delivery. | | `X-GitHub-Delivery` | A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | +| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | | `X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} -| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} +| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. @@ -195,7 +195,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.content_reference_short_desc %} -Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" to create a new content attachment. +Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event. @@ -715,7 +715,7 @@ The webhook this event is configured on was deleted. This event will only listen ### paketieren -Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. +Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. #### Availability @@ -775,7 +775,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus | -------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `zen` | `string` | Random string of GitHub zen. | | `hook_id` | `integer` | The ID of the webhook that triggered the ping. | -| `Hook` | `Objekt` | The [webhook configuration](/v3/repos/hooks/#get-a-repository-webhook). | +| `Hook` | `Objekt` | The [webhook configuration](/rest/reference/repos#get-a-repository-webhook). | | `hook[app_id]` | `integer` | When you register a new {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} sends a ping event to the **webhook URL** you specified during registration. The event contains the `app_id`, which is required for [authenticating](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) an app. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} @@ -969,24 +969,24 @@ Deliveries for `review_requested` and `review_request_removed` events will have #### Webhook payload object -| Schlüssel | Typ | Beschreibung | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/main`. | -| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | -| `after` | `string` | The SHA of the most recent commit on `ref` after the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `string` | The SHA of the commit. | -| `commits[][timestamp]` | `string` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `string` | The commit message. | -| `commits[][author]` | `Objekt` | The git author of the commit. | -| `commits[][author][name]` | `string` | The git author's name. | -| `commits[][author][email]` | `string` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | -| `commits[][added]` | `array` | An array of files added in the commit. | -| `commits[][modified]` | `array` | An array of files modified by the commit. | -| `commits[][removed]` | `array` | An array of files removed in the commit. | -| `pusher` | `Objekt` | The user who pushed the commits. | +| Schlüssel | Typ | Beschreibung | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ref` | `string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | +| `after` | `string` | The SHA of the most recent commit on `ref` after the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][id]` | `string` | The SHA of the commit. | +| `commits[][timestamp]` | `string` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `string` | The commit message. | +| `commits[][author]` | `Objekt` | The git author of the commit. | +| `commits[][author][name]` | `string` | The git author's name. | +| `commits[][author][email]` | `string` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| `commits[][added]` | `array` | An array of files added in the commit. | +| `commits[][modified]` | `array` | An array of files modified by the commit. | +| `commits[][removed]` | `array` | An array of files removed in the commit. | +| `pusher` | `Objekt` | The user who pushed the commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1022,7 +1022,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### repository_dispatch -This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event)" endpoint. +This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. #### Availability @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | Schlüssel | Typ | Beschreibung | | --------- | -------- | -------------------------------------------------------------------------------- | -| `action` | `string` | die Aktion, die durchgeführt wurde. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| +| `action` | `string` | die Aktion, die durchgeführt wurde. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1060,7 +1060,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% if currentVersion == "free-pro-team@latest"%} ### repository_import -{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/v3/migrations/source_imports/). +{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports). #### Availability @@ -1237,9 +1237,9 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ #### Webhook payload object -| Schlüssel | Typ | Beschreibung | -| --------- | -------- | ------------------------------------------------------------------------------------------------------ | -| `Team` | `Objekt` | The [team](/v3/teams/) that was modified. **Note:** Older events may not include this in the payload. | +| Schlüssel | Typ | Beschreibung | +| --------- | -------- | ----------------------------------------------------------------------------------------------------------------- | +| `Team` | `Objekt` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1268,7 +1268,7 @@ When a user is `created` or `deleted`. {% data reusables.webhooks.watch_short_desc %} -The event’s actor is the [user](/v3/users/) who starred a repository, and the event’s repository is the [repository](/v3/repos/) that was starred. +The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. #### Availability diff --git a/translations/de-DE/content/github/administering-a-repository/about-releases.md b/translations/de-DE/content/github/administering-a-repository/about-releases.md index 859f67c001..3484d2fdaa 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-releases.md +++ b/translations/de-DE/content/github/administering-a-repository/about-releases.md @@ -37,7 +37,7 @@ If a release fixes a security vulnerability, you should publish a security advis You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -Du kannst auch das Release-API verwenden, um Informationen zu sammeln, wie zum Beispiel die Anzahl der Downloads eines Release-Objekts. For more information, see "[Releases](/v3/repos/releases/)." +Du kannst auch das Release-API verwenden, um Informationen zu sammeln, wie zum Beispiel die Anzahl der Downloads eines Release-Objekts. For more information, see "[Releases](/rest/reference/repos#releases)." {% if currentVersion == "free-pro-team@latest" %} ### Speicher- und Bandbreiten-Kontingente diff --git a/translations/de-DE/content/github/administering-a-repository/about-required-status-checks.md b/translations/de-DE/content/github/administering-a-repository/about-required-status-checks.md index 71174adf3d..0f62876cf3 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-required-status-checks.md +++ b/translations/de-DE/content/github/administering-a-repository/about-required-status-checks.md @@ -36,7 +36,7 @@ Du kannst entweder lose oder strenge Statuschecks einrichten, je nachdem, ob Du ### Fehlerbehebung von erforderlichen Statuschecks -Wenn Du eine Prüfung und einen Status mit dem gleichen Namen hast, und Du selektierst diesen Namen als erforderlichen Statuscheck, dann sind sowohl die Prüfung wie auch der Status erforderlich. For more information, see "[Checks](/v3/checks/)." +Wenn Du eine Prüfung und einen Status mit dem gleichen Namen hast, und Du selektierst diesen Namen als erforderlichen Statuscheck, dann sind sowohl die Prüfung wie auch der Status erforderlich. For more information, see "[Checks](/rest/reference/checks)." Nachdem Du die erforderlichen Statuschecks eingerichtet hast, muss Dein Branch vor dem Zusammenführen auf dem neuesten Stand des Basisbranches sein. Dadurch wird sichergestellt, dass Dein Branch mit dem neuesten Code aus dem Basisbranch getestet wurde. Wenn Dein Branch veraltet ist, musst Du den Basisbranch in Deinen Branch zusammenführen. @@ -62,7 +62,7 @@ remote: error: Required status check "ci-build" is failing {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Manchmal werden sich die Ergebnisse der Statuschecks für den Test-Merge-Commit und Head-Commit widersprechen. Wenn der Test-Merge-Commit einen Status hat, muss dieser bestanden werden. Anderenfalls muss der Status des Head-Commit bestanden sein, bevor Du den Branch zusammenführen kannst. For more information about test merge commits, see "[Pull Requests](/v3/pulls/#response-1)." +Manchmal werden sich die Ergebnisse der Statuschecks für den Test-Merge-Commit und Head-Commit widersprechen. Wenn der Test-Merge-Commit einen Status hat, muss dieser bestanden werden. Anderenfalls muss der Status des Head-Commit bestanden sein, bevor Du den Branch zusammenführen kannst. For more information about test merge commits, see "[Pull Requests](/rest/reference/pulls#response-1)." ![Branch mit widersprüchlichen Merge-Commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md index 1d03ae0baf..4ccc4a820c 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,12 +15,15 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} + ### About release management +{% if currentVersion == "free-pro-team@latest" %} You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "Publishing an action in the {% data variables.product.prodname_marketplace %}." - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% endif %} You can choose whether + {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/de-DE/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/de-DE/content/github/authenticating-to-github/about-githubs-ip-addresses.md index 0353527257..b1a25e4246 100644 --- a/translations/de-DE/content/github/authenticating-to-github/about-githubs-ip-addresses.md +++ b/translations/de-DE/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -12,7 +12,7 @@ versions: free-pro-team: '*' --- -Sie können eine Liste der IP-Adressen von {% data variables.product.prodname_dotcom %} über den [meta](https://api.github.com/meta)-API-Endpunkt abrufen. For more information, see "[Meta](/v3/meta/)." +Sie können eine Liste der IP-Adressen von {% data variables.product.prodname_dotcom %} über den [meta](https://api.github.com/meta)-API-Endpunkt abrufen. For more information, see "[Meta](/rest/reference/meta)." Diese Bereiche sind in [CIDR-Notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). Mit einem Online-Konvertierungstool wie zum Beispiel [CIDR/VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) kannst Du eine Konvertierung von CIDR-Notation in IP-Adressbereiche durchführen. diff --git a/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md index 4659fa1f53..2127526711 100644 --- a/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -12,7 +12,7 @@ versions: github-ae: '*' --- -Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/v3/auth/#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). +Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). {% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. Weitere Informationen findest Du unter[„Authentifizierung mit SAML Single Sign-On](/articles/about-authentication-with-saml-single-sign-on)" und[„Autorisieren eines persönlichen Zugriffstokens für die Verwendung mit SAML Single Sign-On](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %} diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md index 9b5f455d4c..2df0309f87 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md @@ -29,7 +29,7 @@ Es gibt zwei Arten von Statuschecks auf {% data variables.product.product_name % _Prüfungen_ unterscheiden sich von _Status_ dadurch, dass sie Zeilenanmerkungen und detailliertere Meldungen enthalten und nur für die Verwendung mit {% data variables.product.prodname_github_app %}s verfügbar sind. -Organisationsinhaber und Benutzer mit Push-Zugriff auf ein Repository können mit der API von {% data variables.product.product_name %} Prüfungen und Status erstellen. For more information, see "[Checks](/v3/checks/)" and "[Statuses](/v3/repos/statuses/)." +Organisationsinhaber und Benutzer mit Push-Zugriff auf ein Repository können mit der API von {% data variables.product.product_name %} Prüfungen und Status erstellen. For more information, see "[Checks](/rest/reference/checks)" and "[Statuses](/rest/reference/repos#statuses)." ### Prüfungen diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index 91e7e3cfa1..3897dd6561 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -11,7 +11,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -Um ein Archiv Deines Repositorys herunterzuladen, kannst du die API für die Migration von Benutzern oder Organisationen verwenden. For more information, see "[Migrations](/v3/migrations/)." +Um ein Archiv Deines Repositorys herunterzuladen, kannst du die API für die Migration von Benutzern oder Organisationen verwenden. For more information, see "[Migrations](/rest/reference/migrations)." {% else %} Du kannst Deine Repositorys manuell herunterladen und sichern: @@ -21,15 +21,15 @@ Du kannst Deine Repositorys manuell herunterladen und sichern: Wenn Du ein Repository oder Wiki klonst, werden nur Git-Daten wie Projektdateien und der Commit-Verlauf heruntergeladen. Mithilfe unserer API kannst Du andere Elemente Deines {% data variables.product.product_name %}-Repositorys auf Deinen lokalen Computer herunterladen: -- [Issues](/v3/issues/#list-issues-for-a-repository) -- [Pull Requests](/v3/pulls/#list-pull-requests) +- [Issues](/rest/reference/issues#list-issues-for-a-repository) +- [Pull Requests](/rest/reference/pulls#list-pull-requests) - [Forks](/rest/reference/repos#list-forks) - [Kommentare](/rest/reference/issues#list-issue-comments-for-a-repository) - [Meilensteine](/rest/reference/issues#list-milestones) - [Kennzeichnungen](/rest/reference/issues#list-labels-for-a-repository) - [Watcher](/rest/reference/activity#list-watchers) - [Stargazers](/rest/reference/activity#list-stargazers) -- [Projekte](/v3/projects/#list-repository-projects) +- [Projekte](/rest/reference/projects#list-repository-projects) {% endif %} Once you have {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 4466fa0632..94d8995a0c 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ Wenn Du nach einer Lizenz einer Familie suchst, enthalten die Suchergebnisse all ### Eine Lizenz erkennen -[Das Open-Source-Ruby-Gem Licensee](https://github.com/benbalter/licensee) vergleicht die *LICENSE*-Datei des Repositorys mit einer kurzen Liste bekannter Lizenzen. Licensee stellt außerdem die [Licenses-API](/v3/licenses/) bereit und [bietet Einblicke in die Lizenzierung von Repositorys auf {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Wenn Dein Repository eine Lizenz verwendet, die nicht auf der [Website „Choose a License“](http://choosealicense.com/appendix/) (eine Lizenz auswählen) aufgeführt ist, kannst Du [das Hinzufügen einer Lizenz fordern](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[Das Open-Source-Ruby-Gem Licensee](https://github.com/benbalter/licensee) vergleicht die *LICENSE*-Datei des Repositorys mit einer kurzen Liste bekannter Lizenzen. Licensee stellt außerdem die [Licenses-API](/rest/reference/licenses) bereit und [bietet Einblicke in die Lizenzierung von Repositorys auf {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Wenn Dein Repository eine Lizenz verwendet, die nicht auf der [Website „Choose a License“](http://choosealicense.com/appendix/) (eine Lizenz auswählen) aufgeführt ist, kannst Du [das Hinzufügen einer Lizenz fordern](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). Wenn Dein Repository eine Lizenz verwendet, die auf der Website „Choose a License“ (Wähle eine Lizenz) aufgeführt ist, und die Lizenz nicht deutlich sichtbar oben auf der Repository-Seite angezeigt wird, enthält das Repository möglicherweise mehrere Lizenzen oder es liegt eine andere Komplexität vor. Damit Deine Lizenz erkannt wird, vereinfache Deine *LICENSE*-Datei und notiere die Komplexität an anderer Stelle, beispielsweise in der *README*-Datei Deines Repositorys. diff --git a/translations/de-DE/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/de-DE/content/github/extending-github/git-automation-with-oauth-tokens.md index 074edb9a1a..584af3716d 100644 --- a/translations/de-DE/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/de-DE/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -43,4 +43,4 @@ Um diese Aufforderungen zu vermeiden, kannst Du die Passwort-Zwischenspeicherung ### Weiterführende Informationen -- "[Authorizing OAuth Apps](/v3/oauth/)" +- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)" diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index cc2db49628..c492e3a3a9 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ You can use {% data variables.product.prodname_code_scanning %} to find, triage, If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. +You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)." diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 0cc08d5b3c..878369e4a0 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -52,6 +52,32 @@ The default {% data variables.product.prodname_codeql_workflow %} uses the `pull For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +#### Avoiding unnecessary scans of pull requests + +You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. + +``` yaml +on: + push: + branches: [main, protected] + pull_request: + branches: [main] + paths-ignore: + - '**/*.md' + - '**/*.txt' +``` + +{% note %} + +**Notes** + +* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." +* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. + +{% endnote %} + +For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." + #### Scanning on a schedule If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." @@ -235,13 +261,13 @@ If you only want to run custom queries, you can disable the default security que #### Specifying directories to scan -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from scans by adding a `paths-ignore` array. +For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. ``` yaml -paths: +paths: - src paths-ignore: - - node_modules + - src/node_modules - '**/*.test.js' ``` @@ -254,7 +280,7 @@ paths-ignore: {% endnote %} -For C/C++, C#, and Java, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index e5087e87aa..7cb345a9f6 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -41,7 +41,7 @@ Eine Übersicht Deiner Repository-Abonnements findest Du unter „[Repositorys {% endtip %} {% endif %} -Viele Personen vergessen Repositorys, die sie in der Vergangenheit beobachtet haben. Über die Seite „Watched repositories" (beobachtete Repositorys) kannst Du die Beobachtung von Repositorys schnell deaktivieren. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage worflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +Viele Personen vergessen Repositorys, die sie in der Vergangenheit beobachtet haben. Über die Seite „Watched repositories" (beobachtete Repositorys) kannst Du die Beobachtung von Repositorys schnell deaktivieren. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### Alle Deine Abonnements überprüfen diff --git a/translations/de-DE/content/github/managing-your-work-on-github/index.md b/translations/de-DE/content/github/managing-your-work-on-github/index.md index 067a080885..17156e7774 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/index.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/index.md @@ -14,7 +14,7 @@ versions: ### Inhaltsverzeichnis -{% topic_link_in_list /managing-your-work-with-issues %} +{% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} @@ -27,6 +27,7 @@ versions: {% link_in_list /pinning-an-issue-to-your-repository %} {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} + {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} {% link_in_list /about-automation-for-issues-and-pull-requests-with-query-parameters %} {% link_in_list /file-attachments-on-issues-and-pull-requests %} @@ -35,12 +36,6 @@ versions: {% link_in_list /disabling-issues %} {% link_in_list /linking-a-pull-request-to-an-issue %} {% link_in_list /about-duplicate-issues-and-pull-requests %} -{% topic_link_in_list /labeling-issues-and-pull-requests %} - {% link_in_list /about-labels %} - {% link_in_list /creating-a-label %} - {% link_in_list /applying-labels-to-issues-and-pull-requests %} - {% link_in_list /editing-a-label %} - {% link_in_list /deleting-a-label %} {% topic_link_in_list /managing-project-boards %} {% link_in_list /about-project-boards %} {% link_in_list /creating-a-project-board %} diff --git a/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md b/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md new file mode 100644 index 0000000000..3b2956f832 --- /dev/null +++ b/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md @@ -0,0 +1,97 @@ +--- +title: Managing labels +intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +redirect_from: + - /articles/managing-Labels + - /articles/labeling-issues-and-pull-requests + - /github/managing-your-work-on-github/labeling-issues-and-pull-requests + - /articles/about-labels + - /github/managing-your-work-on-github/about-labels + - /articles/creating-and-editing-labels-for-issues-and-pull-requests + - /articles/creating-a-label + - /github/managing-your-work-on-github/creating-a-label + - /articles/customizing-issue-labels/ + - /articles/applying-labels-to-issues-and-pull-requests + - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests + - /articles/editing-a-label + - /github/managing-your-work-on-github/editing-a-label + - /articles/deleting-a-label + - /github/managing-your-work-on-github/deleting-a-label +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Informationen zu Kennzeichnungen + +Sie können Ihre Arbeit auf {% data variables.product.product_name %} verwalten, indem Sie Kennzeichnungen für die Kategorisierung von Issues und Pull Requests erstellen. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. + +Alle Benutzer mit Lesezugriff auf ein Repository können die Kennzeichnungen des Repositorys einsehen und durchsuchen. Um eine Kennzeichnung zu erstellen, zu bearbeiten, anzuwenden oder zu löschen, benötigst Du Schreibzugriff auf das Repository. + +### About default labels + +{% data variables.product.product_name %} bietet in jedem neuen Repository Standardkennzeichnungen. Mithilfe dieser Standardkennzeichnungen kannst Du einen Standardworkflow in einem Repository erstellen. + +| Kennzeichnung | Beschreibung | +| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `documentation` | Kennzeichnet die Notwendigkeit für Verbesserungen oder Ergänzungen der Dokumentation{% endif %} +| `duplicate` | Kennzeichnet ähnliche Issues oder Pull Requests | +| `enhancement` | Kennzeichnet neue Funktionsanfragen | +| `good first issue` | Kennzeichnet einen geeigneten Issue für erstmalig Mitwirkende | +| `help wanted` | Kennzeichnet, dass ein Betreuer Hilfe bei einem Issue oder Pull Request benötigt | +| `invalid` | Kennzeichnet, dass ein Issue oder Pull Request nicht mehr relevant ist | +| `question` | Kennzeichnet, dass ein Issue oder Pull Request weitere Informationen benötigt | +| `wontfix` | Kennzeichnet, dass die Arbeit an einem Issue oder Pull Request nicht fortgesetzt wird | + +Standardkennzeichnungen sind in jedem neuen Repository beinhaltet, wenn das Repository erstellt wird, aber Du kannst die Kennzeichnungen später bearbeiten oder löschen. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +Organisationsinhaber können die Standardkennzeichnungen für Repositories in ihrer Organisation anpassen. Weitere Informationen findest Du unter „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)." +{% endif %} + +### Eine Kennzeichnung erstellen + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. Klicke rechts neben dem Suchfeld auf **New label** (Neue Kennzeichnung). +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### Kennzeichnungen auf Issues und Pull Requests anwenden + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. Klicke in der oberen rechten Ecke auf **Label** (Kennzeichnung), und gib den Namen einer vorhandenen Kennzeichnung ein. Klicke auf den Namen der Kennzeichnung, um sie mit den ausgewählten Elementen zu verknüpfen. ![Dropdownmenü „Issues Milestone assignment" (Issue-Meilenstein-Zuordnung)](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### Eine Kennzeichnung bearbeiten + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### Eine Kennzeichnung löschen +Deleting a label will remove the label from issues and pull requests. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.delete-label %} + +### Weiterführende Informationen +- „[Informationen zu Kennzeichnungen](/articles/about-labels)“ +- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/de-DE/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md new file mode 100644 index 0000000000..7430e03d28 --- /dev/null +++ b/translations/de-DE/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Managing your work with issues and pull requests +intro: 'Sie können Ihre Arbeit auf {% data variables.product.product_name %} verwalten, indem Sie Issues zur Nachverfolgung von Ideen, Verbesserungen, Aufgaben oder Bugs erstellen.' +mapTopic: true +redirect_from: + - /github/managing-your-work-on-github/managing-your-work-with-issues + - /articles/managing-your-work-with-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 9ef710d922..f7afc70ea8 100644 --- a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -163,7 +163,7 @@ Mit dem Kennzeichner `project` können Sie Issues suchen, die innerhalb eines Re ### Suche nach Commit-Status -Sie können Pull Requests nach dem Status ihrer Commits filtern. Dieser Filter ist besonders nützlich, wenn Sie die [Status-API](/v3/repos/statuses/) oder einen CI-Dienst verwenden. +Sie können Pull Requests nach dem Status ihrer Commits filtern. Dieser Filter ist besonders nützlich, wenn Sie die [Status-API](/rest/reference/repos#statuses) oder einen CI-Dienst verwenden. | Qualifizierer | Beispiel | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 3394c9d9b7..c8bbc96a6f 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -40,7 +40,7 @@ Einige IdPs unterstützen die Bereitstellung von Zugriffen auf eine {% data var ### Mitglieder zu einer Organisation mit SAML SSO hinzufügen -Nachdem Sie SAML SSO aktiviert haben, gibt es mehrere Möglichkeiten, wie Sie neue Mitglieder zu Ihrer Organisation hinzufügen können. Organisationsinhaber können neue Mitglieder manuell auf {% data variables.product.product_name %} oder über die API einladen. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/v3/orgs/members/#add-or-update-organization-membership)." +Nachdem Sie SAML SSO aktiviert haben, gibt es mehrere Möglichkeiten, wie Sie neue Mitglieder zu Ihrer Organisation hinzufügen können. Organisationsinhaber können neue Mitglieder manuell auf {% data variables.product.product_name %} oder über die API einladen. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." {% data reusables.organizations.team-synchronization %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index bbeb598746..cd5d13669c 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -12,7 +12,7 @@ Wenn Sie in Ihrer Organisation [SAML SSO](/articles/about-identity-and-access-ma Wenn Du SAML SSO verwendest, ohne SCIM zu implementieren, ist die Aufhebung der Bereitstellung nicht automatisiert. Wenn die Sitzungen der Organisationsmitglieder ablaufen, nachdem ihr Zugriff vom IdP entfernt wurde, werden sie nicht automatisch aus der Organisation entfernt. Autorisierte Token gewähren auch nach Ablauf ihrer Sitzungen Zugriff auf die Organisation. Um den Zugriff zu entfernen, können Administratoren entweder manuell das autorisierte Token aus der Organisation entfernen oder seine Entfernung mit SCIM automatisieren. -These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. Weitere Informationen findest Du unter [SCIM](/v3/scim/) in der {% data variables.product.product_name %}-API-Dokumentation. +These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. Weitere Informationen findest Du unter [SCIM](/rest/reference/scim) in der {% data variables.product.product_name %}-API-Dokumentation. - Azure AD - Okta - OneLogin diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index a2839954c1..46fe98c8f3 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -59,6 +59,7 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben | Bearbeiten von Wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} | [Melden von Missbrauch oder Spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} | Anwenden von Kennzeichnungen | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | | Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** | | Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** | | Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index f3d271f711..13993ae64b 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -23,7 +23,7 @@ Alle über den IdP vorgenommenen Änderungen an der Teammitgliedschaft werden im Um den Repository-Zugriff für jedes {% data variables.product.prodname_dotcom %}-Team zu verwalten, einschließlich Teams, die mit einer IdP-Gruppe verbunden sind, musst Du Änderungen mit {% data variables.product.product_name %} vornehmen. Weitere Informationen findest Du unter „[Informationen zu Teams](/articles/about-teams)“ und „[Teamzugriff auf ein Organisations-Repository verwalten](/articles/managing-team-access-to-an-organization-repository).“ -Du kannst die Teamsynchronisierung auch mit dem API verwalten. For more information, see "[Team synchronization](/v3/teams/team_sync/)." +Du kannst die Teamsynchronisierung auch mit dem API verwalten. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)." ### Anforderungen an Mitglieder synchronisierter Teams diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md index bc675d9927..540f923057 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -26,7 +26,7 @@ Weitere Informationen über die Unterschiede zwischen {% data variables.product. For more information about member access and management, see "{% if currentVersion == "free-pro-team@latest" %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}." -For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 3ab660a814..86b686d9ae 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -10,7 +10,7 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} -3. Klicke auf der linken Seitenleiste auf **{% data variables.product.prodname_oauth_app %}**. ![Registerkarte von { site.data.variables.product.prodname_oauth_app } in der linken Seitenleiste](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. Klicke auf der linken Seitenleiste auf **{% data variables.product.prodname_oauth_app %}**. ![{% data variables.product.prodname_oauth_app %}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) 3. Klicke auf **Register a new application** (Eine neue Anwendung registrieren). 4. Gib unter **Application name** (Anwendungsname) „Jira“ ein. 5. Gib unter **Homepage URL** (URL für Startseite) die vollständige URL Deiner Jira-Instanz ein. diff --git a/translations/de-DE/content/github/site-policy/github-privacy-statement.md b/translations/de-DE/content/github/site-policy/github-privacy-statement.md index 5d4fd4b8c2..b254f2f5a0 100644 --- a/translations/de-DE/content/github/site-policy/github-privacy-statement.md +++ b/translations/de-DE/content/github/site-policy/github-privacy-statement.md @@ -201,7 +201,7 @@ Bitte wenden Sie sich an die Kontoinhaber, um weitere Informationen darüber zu #### Anwendungen Dritter -Sie haben die Möglichkeit, Ihrem Konto Drittanbieter-Anwendungen, die als "Entwicklerprodukte" bezeichnet werden, hinzuzufügen bzw. diese zu aktivieren. Diese Entwicklerprodukte sind für Ihre Nutzung von GitHub nicht erforderlich. Wir geben Ihre personenbezogenen Benutzerdaten an Dritte weiter, wenn Sie uns darum bitten, z. B. durch den Kauf eines Entwicklerprodukts über den Marketplace; Sie sind jedoch für Ihre Nutzung des Entwicklerprodukts von Drittanbietern sowie für die Menge der personenbezogenen Benutzerinformationen, die Sie mit diesem Produkt teilen möchten, selber verantwortlich. Sie können unsere [API-Dokumentation](/v3/users/) einsehen um zu erfahren, welche Informationen bereitgestellt werden, wenn Sie sich mit Ihrem GitHub-Profil bei einem Entwicklerprodukt authentifizieren. +Sie haben die Möglichkeit, Ihrem Konto Drittanbieter-Anwendungen, die als "Entwicklerprodukte" bezeichnet werden, hinzuzufügen bzw. diese zu aktivieren. Diese Entwicklerprodukte sind für Ihre Nutzung von GitHub nicht erforderlich. Wir geben Ihre personenbezogenen Benutzerdaten an Dritte weiter, wenn Sie uns darum bitten, z. B. durch den Kauf eines Entwicklerprodukts über den Marketplace; Sie sind jedoch für Ihre Nutzung des Entwicklerprodukts von Drittanbietern sowie für die Menge der personenbezogenen Benutzerinformationen, die Sie mit diesem Produkt teilen möchten, selber verantwortlich. Sie können unsere [API-Dokumentation](/rest/reference/users) einsehen um zu erfahren, welche Informationen bereitgestellt werden, wenn Sie sich mit Ihrem GitHub-Profil bei einem Entwicklerprodukt authentifizieren. #### GitHub Pages diff --git a/translations/de-DE/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/de-DE/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index da711cfdc7..1d223209ec 100644 --- a/translations/de-DE/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/de-DE/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -28,7 +28,7 @@ In Bezug auf ihre personenbezogenen Daten können Einwohner Kaliforniens die unt In Kalifornien ansässige Personen haben das Recht, von einem Unternehmen die Offenlegung der Kategorien und spezifischen Teile der personenbezogenen Daten zu verlangen, die es in den vorangegangenen 12 Monaten von ihnen erhoben hat, die Kategorien der Quellen, aus denen diese personenbezogenen Daten erhoben werden, den geschäftlichen oder kommerziellen Zweck der Erhebung oder des Verkaufs dieser personenbezogenen Daten und die Kategorien von Dritten, mit denen das Unternehmen personenbezogene Daten teilt. -Wenn Sie ein Unternehmen auffordern, Kategorien und bestimmte über Sie erfasste personenbezogene Daten offenzulegen, haben Sie das Recht, diese Informationen zweimal im Jahr kostenlos zu erhalten. Die Informationen können per Post oder elektronisch übermittelt werden und müssen, wenn sie elektronisch bereitgestellt werden, in einem portablen und, soweit technisch machbar, leicht verwendbaren Format erfolgen, das es dem in Kalifornien ansässigen Einwohner ermöglicht, diese Informationen relativ einfach an eine andere Stelle zu übermitteln. Sie können GitHubs [Benutzer-Migrations-API](/v3/migrations/users/) verwenden, um auf Ihre Daten zuzugreifen und sie herunterzuladen. Weitere Informationen finden Sie [hier](https://github.blog/2018-12-19-download-your-data/). +Wenn Sie ein Unternehmen auffordern, Kategorien und bestimmte über Sie erfasste personenbezogene Daten offenzulegen, haben Sie das Recht, diese Informationen zweimal im Jahr kostenlos zu erhalten. Die Informationen können per Post oder elektronisch übermittelt werden und müssen, wenn sie elektronisch bereitgestellt werden, in einem portablen und, soweit technisch machbar, leicht verwendbaren Format erfolgen, das es dem in Kalifornien ansässigen Einwohner ermöglicht, diese Informationen relativ einfach an eine andere Stelle zu übermitteln. You can use GitHub’s [User Migration API](/rest/reference/migrations#users) to access and download your data. Weitere Informationen finden Sie [hier](https://github.blog/2018-12-19-download-your-data/). ### 2. Recht zu erfahren, ob Ihre personenbezogenen Daten für einen geschäftlichen Zweck verkauft oder offengelegt werden und an wen diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index 7961659dc2..86a9bfe0ef 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -54,8 +54,6 @@ Wenn Du in einer unterstützen Region lebst, kannst Du diesen Anweisungen folgen {% data reusables.sponsors.double-check-stripe-info %} -Wenn Du nicht in einer unterstützten Region lebst und für die Beta-Phase von {% data variables.product.prodname_sponsors %} akzeptiert wurdest, wirst Du eine E-Mail erhalten mit Anweisungen, wie Du Deine Bankdaten zur Verfügung stellen musst, damit Du Auszahlungen via ACH-Übermittlung oder Banküberweisung erhalten kannst. - {% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} diff --git a/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md index 768251aabc..1299353adc 100644 --- a/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md +++ b/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md @@ -10,7 +10,7 @@ versions: {% data variables.product.product_name %} speichert Repository- und Profil-Metadaten aus den Aktivitäten Ihres persönlichen Kontos. Die Daten Ihres persönlichen Kontos können Sie über die Einstellungen auf der {% data variables.product.prodname_dotcom_the_website %} oder mit der API für die Benutzermigration exportieren. -For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see "[Download a user migration archive](/v3/migrations/users/#download-a-user-migration-archive)" and "[About {% data variables.product.product_name %}'s use of your data](/articles/about-github-s-use-of-your-data). +For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see "[Download a user migration archive](/rest/reference/migrations#download-a-user-migration-archive)" and "[About {% data variables.product.product_name %}'s use of your data](/articles/about-github-s-use-of-your-data). Wenn Sie einen Export Ihrer persönlichen Daten über die Einstellungen auf {% data variables.product.prodname_dotcom_the_website %} anfordern, verpackt {% data variables.product.product_name %} Ihre persönlichen Daten in einer `tar.gz`-Datei. Diese können Sie über einen Download-Link herunterladen, der Ihnen in einer E-Mail an Ihre primäre E-Mail-Adresse gesendet wird. diff --git a/translations/de-DE/content/github/using-git/which-remote-url-should-i-use.md b/translations/de-DE/content/github/using-git/which-remote-url-should-i-use.md index fb5eff82e8..f8cd8fa696 100644 --- a/translations/de-DE/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/de-DE/content/github/using-git/which-remote-url-should-i-use.md @@ -44,7 +44,7 @@ Wenn Du mittels SSH-URLs `git clone`-, `git fetch`-, `git pull`- oder `git push` {% tip %} -**Tipp**: Du kannst eine SSH-URL verwenden, um ein Repository auf Deinem Computer zu klonen oder als sichere Möglichkeit, Deinen Code auf Produktionsserver zu verteilen. Du kannst auch SSH-Agent-Weiterleitung mit Deinem Verteil-Skript verwenden, um das Verwalten von Schlüsseln auf dem Server zu vermeiden. For more information, see "[Using SSH Agent Forwarding](/v3/guides/using-ssh-agent-forwarding/)." +**Tipp**: Du kannst eine SSH-URL verwenden, um ein Repository auf Deinem Computer zu klonen oder als sichere Möglichkeit, Deinen Code auf Produktionsserver zu verteilen. Du kannst auch SSH-Agent-Weiterleitung mit Deinem Verteil-Skript verwenden, um das Verwalten von Schlüsseln auf dem Server zu vermeiden. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index a346fddef3..dcbd8b78fd 100644 --- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -36,7 +36,7 @@ Aus den folgenden Gründen wirst Du möglicherweise im Mitarbeiterdiagramm eines {% tip %} -**Tip:** To list all commit contributors in a repository, see "[Repositories](/v3/repos/#list-contributors)." +**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)." {% endtip %} diff --git a/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md b/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md index 3fb6f1beba..2549348cdb 100644 --- a/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md @@ -150,4 +150,4 @@ Zwar können Sie keine benutzerdefinierten MIME-Typen für einzelne Dateien oder ### Weiterführende Informationen - [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) auf {% data variables.product.prodname_learning %} -- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)" +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index e6d8bd2e4a..f33edb1ec8 100644 --- a/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -16,7 +16,7 @@ versions: Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} - Der Benutzer, der die Änderungen gepusht hat, hat seine E-Mail-Adresse nicht verifiziert. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/articles/verifying-your-email-address)“.{% endif %} -- Du führst den Push mit einem Deployment-Schlüssel durch. Wenn Du Übertragungen zum Repository Deiner Website automatisieren möchtest, kannst du stattdessen einen Maschinenbenutzer einrichten. For more information, see "[Managing deploy keys](/v3/guides/managing-deploy-keys/#machine-users)." +- Du führst den Push mit einem Deployment-Schlüssel durch. Wenn Du Übertragungen zum Repository Deiner Website automatisieren möchtest, kannst du stattdessen einen Maschinenbenutzer einrichten. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)." - Du verwendest einen Dienst für die fortlaufende Integration, der nicht zum Erstellen Deiner Veröffentlichungsquelle konfiguriert ist. Travis CI erstellt beispielsweise nicht den Branch `gh-pages`, es sei denn, Du fügst den Branch zu einer Liste mit sicheren Branches hinzu. Weitere Informationen findest Du unter „[Build anpassen](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)“ auf Travis CI oder in der Dokumentation Deines Dienstes für die fortlaufende Integration. {% note %} diff --git a/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md b/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md index f7cd481789..a385f03800 100644 --- a/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md @@ -18,7 +18,7 @@ Follow the steps in "[Creating a personal access token](/github/authenticating-t {% if currentVersion == "free-pro-team@latest" %} -To match the behavior of the [GraphQL Explorer](/v4/guides/using-the-explorer), request the following scopes: +To match the behavior of the [GraphQL Explorer](/graphql/guides/using-the-explorer), request the following scopes: {% else %} @@ -50,9 +50,9 @@ The endpoint remains constant no matter what operation you perform. ### Communicating with GraphQL -Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/v4/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. +Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/graphql/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. -In REST, [HTTP verbs](/v3/#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/v4/guides/intro-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest)." +In REST, [HTTP verbs](/rest#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." To query GraphQL using cURL, make a `POST` request with a JSON payload. The payload must contain a string called `query`: @@ -72,15 +72,15 @@ curl -H "Authorization: bearer token" -X POST -d " \ #### About query and mutation operations -The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/v4/mutation/) determines which modification is executed. +The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/graphql/reference/mutations) determines which modification is executed. -For information about rate limiting, see "[GraphQL resource limitations](/v4/guides/resource-limitations/)." +For information about rate limiting, see "[GraphQL resource limitations](/graphql/overview/resource-limitations)." Queries and mutations share similar forms, with some important differences. #### About queries -GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/v4/guides/intro-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/v4/scalar/). +GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/graphql/guides/introduction-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/graphql/reference/scalars). Queries are structured like this: @@ -107,7 +107,7 @@ Mutations are structured like this: The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. -In the [mutations](/v4/mutation/) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. +In the [mutations](/graphql/reference/mutations) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. For a real-world example, see "[Example mutation](#example-mutation)." @@ -117,7 +117,7 @@ For a real-world example, see "[Example mutation](#example-mutation)." {% note %} -**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/v4/guides/using-the-explorer/#using-the-variable-pane), and do not include the word `variables` before the JSON object. +**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object. {% endnote %} @@ -207,7 +207,7 @@ Looking at the composition line by line: * `repository(owner:"octocat", name:"Hello-World") {` - To begin the query, we want to find a [`repository`](/v4/object/repository/) object. The schema validation indicates this object requires an `owner` and a `name` argument. + To begin the query, we want to find a [`repository`](/graphql/reference/objects#repository) object. The schema validation indicates this object requires an `owner` and a `name` argument. * `issues(last:20, states:CLOSED) {` @@ -215,9 +215,9 @@ Looking at the composition line by line: Some details about the `issues` object: - - The [docs](/v4/object/repository/) tell us this object has the type `IssueConnection`. + - The [docs](/graphql/reference/objects#repository) tell us this object has the type `IssueConnection`. - Schema validation indicates this object requires a `last` or `first` number of results as an argument, so we provide `20`. - - The [docs](/v4/object/repository/) also tell us this object accepts a `states` argument, which is an [`IssueState`](/v4/enum/issuestate/) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. + - The [docs](/graphql/reference/objects#repository) also tell us this object accepts a `states` argument, which is an [`IssueState`](/graphql/reference/enums#issuestate) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. * `edges {` @@ -225,9 +225,9 @@ Looking at the composition line by line: * `node {` - Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/v4/object/issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. + Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/graphql/reference/objects#issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. -* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/v4/object/issue) and specify the fields we want to return: +* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/graphql/reference/objects#issue) and specify the fields we want to return: ```graphql title @@ -243,7 +243,7 @@ Looking at the composition line by line: Here we specify the `title`, `url`, and `labels` fields of the `Issue` object. - The `labels` field has the type [`LabelConnection`](/v4/object/labelconnection/). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. + The `labels` field has the type [`LabelConnection`](/graphql/reference/objects#labelconnection). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. You may notice that running this query on the Octocat's public `Hello-World` repository won't return many labels. Try running it on one of your own repositories that does use labels, and you'll likely see a difference. @@ -285,7 +285,7 @@ Let's walk through the example. The task sounds simple: add an emoji reaction to So how do we know to begin with a query? We don't, yet. -Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/v4/mutation/addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! +Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/graphql/reference/mutations#addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! The docs for the mutation list three input fields: @@ -337,13 +337,13 @@ With the ID known, we can proceed with the mutation: - `addReaction` is the name of the mutation. - `input` is the required argument key. This will always be `input` for a mutation. - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/v4/input_object/) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/graphql/reference/input-objects) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. - How do we know which value to use for the content? The [`addReaction` docs](/v4/mutation/addreaction/) tell us the `content` field has the type [`ReactionContent`](/v4/enum/reactioncontent/), which is an [enum](/v4/enum) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): + How do we know which value to use for the content? The [`addReaction` docs](/graphql/reference/mutations#addreaction) tell us the `content` field has the type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an [enum](/graphql/reference/enums) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): {% data reusables.repositories.reaction_list %} -* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/v4/mutation/addreaction), which three possible return fields: +* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/graphql/reference/mutations#addreaction), which three possible return fields: - `clientMutationId` (`String`) - `reaction` (`Reaction!`) @@ -394,7 +394,7 @@ variables { {% note %} You may notice that the `content` field value in the earlier example (where it's used directly in the mutation) does not have quotes around `HOORAY`, but it does have quotes when used in the variable. There's a reason for this: -* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/v4/enum/reactioncontent/), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. +* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. * When you use `content` in a variable, the variables section must be valid JSON, so the quotes are required. Schema validation correctly interprets the `ReactionContent` type when the variable is passed into the mutation during execution. For more information on the difference between enums and strings, see the [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). diff --git a/translations/de-DE/content/graphql/guides/introduction-to-graphql.md b/translations/de-DE/content/graphql/guides/introduction-to-graphql.md index f4d05b5bee..017b674775 100644 --- a/translations/de-DE/content/graphql/guides/introduction-to-graphql.md +++ b/translations/de-DE/content/graphql/guides/introduction-to-graphql.md @@ -12,7 +12,7 @@ versions: ### GraphQL terminology -The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/v4/). +The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/graphql). ### Schema @@ -30,11 +30,11 @@ This means that if you try to return a field that is not a scalar, schema valida ### Argument -An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/v4/guides/forming-calls#about-mutations) require an input object as an argument. +An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/graphql/guides/forming-calls-with-graphql#about-mutations) require an input object as an argument. ### Implementation -A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/v4/interface). +A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/graphql/reference/interfaces). Here's a contrived example of a schema that defines interface `X` and object `Y`: @@ -55,13 +55,13 @@ This means object `Y` requires the same fields/arguments/return types that inter In the reference docs, you'll find that: -* Each [object](/v4/object) lists the interface(s) _from which it inherits_ under **Implements**. +* Each [object](/graphql/reference/objects) lists the interface(s) _from which it inherits_ under **Implements**. -* Each [interface](/v4/interface) lists the objects _that inherit from it_ under **Implementations**. +* Each [interface](/graphql/reference/interfaces) lists the objects _that inherit from it_ under **Implementations**. ### Connection -Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest)." +Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." It's helpful to picture a graph: dots connected by lines. The dots are nodes, the lines are edges. A connection defines a relationship between nodes. @@ -71,7 +71,7 @@ Edges represent connections between nodes. When you query a connection, you trav ### Node -_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/v4/scalar), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/v4/guides/using-global-node-ids)." +_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/graphql/reference/scalars), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ## Discovering the GraphQL API @@ -130,4 +130,4 @@ query { {% endnote %} - For more information about performing queries, see "[Forming calls with GraphQL](/v4/guides/forming-calls)." + For more information about performing queries, see "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." diff --git a/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md b/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md index 8398740df1..b7070a9f2a 100644 --- a/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md @@ -33,7 +33,7 @@ With the Enterprise Accounts API, you can: - Invite administrators to your enterprise account. - Create new organizations in your enterprise account. -For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/v4/guides/managing-enterprise-accounts/#graphql-fields-and-types-for-the-enterprise-accounts-api)." +For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)." ### Getting started using GraphQL for enterprise accounts @@ -197,12 +197,12 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio } ``` -For more information about getting started with GraphQL, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql/)" and "[Forming Calls with GraphQL](/v4/guides/forming-calls/)." +For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." ### GraphQL fields and types for the Enterprise Accounts API Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API. -For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/v4/). +For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql). -You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)." For other information, such as authentication and rate limit details, check out the [guides](/v4/guides). +You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)." For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). diff --git a/translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md index 3741cf1779..57ffdca998 100644 --- a/translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: Migrating from REST to GraphQL represents a significant shift in API logic. The differences between REST as a style and GraphQL as a specification make it difficult—and often undesirable—to replace REST API calls with GraphQL API queries on a one-to-one basis. We've included specific examples of migration below. -To migrate your code from the [REST API](/v3) to the GraphQL API: +To migrate your code from the [REST API](/rest) to the GraphQL API: - Review the [GraphQL spec](https://graphql.github.io/graphql-spec/June2018/) -- Review GitHub's [GraphQL schema](/v4/reference/) +- Review GitHub's [GraphQL schema](/graphql/reference) - Consider how any existing code you have currently interacts with the GitHub REST API -- Use [Global Node IDs](/v4/guides/using-global-node-ids) to reference objects between API versions +- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions Significant advantages of GraphQL include: @@ -53,12 +53,12 @@ query { } ``` -Consider another example: retrieving a list of pull requests and checking if each one is mergeable. A call to the REST API retrieves a list of pull requests and their [summary representations](/v3/#summary-representations): +Consider another example: retrieving a list of pull requests and checking if each one is mergeable. A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/v3/#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: +Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ Using the **GraphQL API**, you can retrieve the data with a single query using n } ``` -You can also extend the power of this query by [substituting a variable](/v4/guides/forming-calls/#working-with-variables) for the pull request number. +You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. ## Example: Strong typing GraphQL schemas are strongly typed, making data handling safer. -Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/v4/mutation), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/v4/mutation/addcomment/): +Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): ```graphql mutation { diff --git a/translations/de-DE/content/graphql/guides/using-global-node-ids.md b/translations/de-DE/content/graphql/guides/using-global-node-ids.md index 77307ca9eb..0fb33e4920 100644 --- a/translations/de-DE/content/graphql/guides/using-global-node-ids.md +++ b/translations/de-DE/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ You can access most objects in GitHub (users, issues, pull requests, etc.) using {% note %} -**Note:** In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql/#node)." +**Note:** In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." {% endnote %} @@ -29,7 +29,7 @@ Let's walk through an example. ### 1. Call a REST endpoint that returns an object's node ID -If you [request the authenticated user](/v3/users/#get-the-authenticated-user): +If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { This type of query—that is, finding the node by ID—is known as a "direct node lookup." -When you run this query, you'll see that the `__typename` is [`User`](/v4/object/user/). +When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). ### 3. Do a direct node lookup in GraphQL @@ -122,4 +122,4 @@ This type of query is the standard approach for looking up an object by its glob ### Using global node IDs in migrations -When building integrations that use either the REST API or the GraphQL API, it's best practice to persist the global node ID so you can easily reference objects across API versions. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest/)." +When building integrations that use either the REST API or the GraphQL API, it's best practice to persist the global node ID so you can easily reference objects across API versions. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." diff --git a/translations/de-DE/content/graphql/guides/using-the-explorer.md b/translations/de-DE/content/graphql/guides/using-the-explorer.md index f9b1c02f3e..50ced501bf 100644 --- a/translations/de-DE/content/graphql/guides/using-the-explorer.md +++ b/translations/de-DE/content/graphql/guides/using-the-explorer.md @@ -13,11 +13,11 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -[GraphQL Explorer](/v4/explorer) is an instance of [GraphiQL](https://github.com/graphql/graphiql), which is a "graphical interactive in-browser GraphQL IDE." +[GraphQL Explorer](/graphql/overview/explorer) is an instance of [GraphiQL](https://github.com/graphql/graphiql), which is a "graphical interactive in-browser GraphQL IDE." {% note %} -**Note**: {% data variables.product.prodname_dotcom %} has disabled [mutations](/v4/mutation/) in the Explorer, but you can use them in your own GraphiQL instance. +**Note**: {% data variables.product.prodname_dotcom %} has disabled [mutations](/graphql/reference/mutations) in the Explorer, but you can use them in your own GraphiQL instance. {% endnote %} @@ -33,7 +33,7 @@ To use the GraphiQL app, download and install it from https://github.com/skevy/g #### Configuring GraphiQL -1. Get an [OAuth token](/v4/guides/forming-calls#authenticating-with-graphql). +1. Get an [OAuth token](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql). 1. Launch GraphiQL. 1. In the upper-right corner of GraphiQL, click **Edit HTTP Headers**. 1. In the **Key** field, enter `Authorization`. In the **Value** field, enter `Bearer `, where `` is your generated OAuth token. ![graphiql headers](/assets/images/developer/graphiql-headers.png) @@ -44,7 +44,7 @@ To use the GraphiQL app, download and install it from https://github.com/skevy/g {% note %} -**Note**: For more information about why `POST` is the method, see "[Communicating with GraphQL](/v4/guides/forming-calls#communicating-with-graphql)." +**Note**: For more information about why `POST` is the method, see "[Communicating with GraphQL](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)." {% endnote %} @@ -66,13 +66,13 @@ All types in a GraphQL schema include a `description` field compiled into docume {% note %} -The **Docs** sidebar contains the same content that is automatically generated from the schema under "[Reference](/v4/)," though it is formatted differently in places. +The **Docs** sidebar contains the same content that is automatically generated from the schema under "[Reference](/graphql)," though it is formatted differently in places. {% endnote %} ### Using the variable pane -Some example calls include [variables](/v4/guides/forming-calls#working-with-variables) written like this: +Some example calls include [variables](/graphql/guides/forming-calls-with-graphql#working-with-variables) written like this: ```graphql query($number_of_repos:Int!){ @@ -90,7 +90,7 @@ variables { } ``` -This is the correct format to submit the call via a cURL `POST` (as long as you [escape newlines](/v4/guides/forming-calls#communicating-with-graphql)). +This is the correct format to submit the call via a cURL `POST` (as long as you [escape newlines](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)). If you want to run the call in the Explorer, enter the `query` segment in the main pane and the variables in the **Query Variables** pane below it. Omit the word `variables` from the Explorer: @@ -106,12 +106,12 @@ If you want to run the call in the Explorer, enter the `query` segment in the ma ### Troubleshooting errors -Because GraphQL is [introspective](/v4/guides/intro-to-graphql#discovering-the-graphql-api), the Explorer supports: +Because GraphQL is [introspective](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), the Explorer supports: * Intelligent typeaheads aware of the current schema * Validation error previews as you type -If you enter a query that is not well-formed or does not pass [schema validation](/v4/guides/intro-to-graphql#schema), a popup warns you of an error. If you run the query, the error returns in the response pane. +If you enter a query that is not well-formed or does not pass [schema validation](/graphql/guides/introduction-to-graphql#schema), a popup warns you of an error. If you run the query, the error returns in the response pane. A GraphQL response contains several keys: a `data` hash and an `errors` array. diff --git a/translations/de-DE/content/graphql/overview/about-the-graphql-api.md b/translations/de-DE/content/graphql/overview/about-the-graphql-api.md index b641194fde..9050397ec6 100644 --- a/translations/de-DE/content/graphql/overview/about-the-graphql-api.md +++ b/translations/de-DE/content/graphql/overview/about-the-graphql-api.md @@ -11,25 +11,25 @@ versions: Here are some quick links to get you up and running with the GraphQL API v4: -* [Authentifizierung](/v4/guides/forming-calls/#authenticating-with-graphql) -* [Root endpoint](/v4/guides/forming-calls/#the-graphql-endpoint) -* [Schema introspection](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) -* [Rate limits](/v4/guides/resource-limitations/) -* [Migrating from REST](/v4/guides/migrating-from-rest) +* [Authentifizierung](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) +* [Root endpoint](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) +* [Schema introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) +* [Rate limits](/graphql/overview/resource-limitations) +* [Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql) ### About GraphQL The [GraphQL](https://graphql.github.io/) data query language is: -* **A [specification](https://graphql.github.io/graphql-spec/June2018/).** The spec determines the validity of the [schema](/v4/guides/intro-to-graphql#schema) on the API server. The schema determines the validity of client calls. +* **A [specification](https://graphql.github.io/graphql-spec/June2018/).** The spec determines the validity of the [schema](/graphql/guides/introduction-to-graphql#schema) on the API server. The schema determines the validity of client calls. * **[Strongly typed](#about-the-graphql-schema-reference).** The schema defines an API's type system and all object relationships. -* **[Introspective](/v4/guides/intro-to-graphql#discovering-the-graphql-api).** A client can query the schema for details about the schema. +* **[Introspective](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api).** A client can query the schema for details about the schema. -* **[Hierarchical](/v4/guides/forming-calls).** The shape of a GraphQL call mirrors the shape of the JSON data it returns. [Nested fields](/v4/guides/migrating-from-rest/#example-nesting) let you query for and receive only the data you specify in a single round trip. +* **[Hierarchical](/graphql/guides/forming-calls-with-graphql).** The shape of a GraphQL call mirrors the shape of the JSON data it returns. [Nested fields](/graphql/guides/migrating-from-rest-to-graphql#example-nesting) let you query for and receive only the data you specify in a single round trip. -* **An application layer.** GraphQL is not a storage model or a database query language. The _graph_ refers to graph structures defined in the schema, where [nodes](/v4/guides/intro-to-graphql#node) define objects and [edges](/v4/guides/intro-to-graphql#edge) define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored. +* **An application layer.** GraphQL is not a storage model or a database query language. The _graph_ refers to graph structures defined in the schema, where [nodes](/graphql/guides/introduction-to-graphql#node) define objects and [edges](/graphql/guides/introduction-to-graphql#edge) define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored. ### Why GitHub is using GraphQL @@ -39,15 +39,15 @@ For more details about why GitHub has moved to GraphQL, see the original [announ ### About the GraphQL schema reference -The docs in the sidebar are generated from the {% data variables.product.prodname_dotcom %} GraphQL [schema](/v4/guides/intro-to-graphql/#discovering-the-graphql-api). All calls are validated and executed against the schema. Use these docs to find out what data you can call: +The docs in the sidebar are generated from the {% data variables.product.prodname_dotcom %} GraphQL [schema](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api). All calls are validated and executed against the schema. Use these docs to find out what data you can call: -* Allowed operations: [queries](/v4/query) and [mutations](/v4/mutation). +* Allowed operations: [queries](/graphql/reference/queries) and [mutations](/graphql/reference/mutations). -* Schema-defined types: [scalars](/v4/scalar), [objects](/v4/object), [enums](/v4/enum), [interfaces](/v4/interface), [unions](/v4/union), and [input objects](/v4/input_object). +* Schema-defined types: [scalars](/graphql/reference/scalars), [objects](/graphql/reference/objects), [enums](/graphql/reference/enums), [interfaces](/graphql/reference/interfaces), [unions](/graphql/reference/unions), and [input objects](/graphql/reference/input-objects). -You can access this same content via the [Explorer Docs sidebar](/v4/guides/using-the-explorer#accessing-the-sidebar-docs). Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API. +You can access this same content via the [Explorer Docs sidebar](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API. -For other information, such as authentication and rate limit details, check out the [guides](/v4/guides). +For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). ### Requesting support diff --git a/translations/de-DE/content/graphql/overview/breaking-changes.md b/translations/de-DE/content/graphql/overview/breaking-changes.md index f9fde6b0f6..ba29ae3c09 100644 --- a/translations/de-DE/content/graphql/overview/breaking-changes.md +++ b/translations/de-DE/content/graphql/overview/breaking-changes.md @@ -16,7 +16,7 @@ Breaking changes are any changes that might require action from our integrators. - **Breaking:** Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change. - **Dangerous:** Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change. -We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a [schema preview](/v4/previews/). +We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a [schema preview](/graphql/overview/schema-previews). We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st. diff --git a/translations/de-DE/content/graphql/overview/changelog.md b/translations/de-DE/content/graphql/overview/changelog.md index dbb8876a2b..6c051b659f 100644 --- a/translations/de-DE/content/graphql/overview/changelog.md +++ b/translations/de-DE/content/graphql/overview/changelog.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -Breaking changes include changes that will break existing queries or could affect the runtime behavior of clients. For a list of breaking changes and when they will occur, see our [breaking changes log](/v4/breaking_changes). +Breaking changes include changes that will break existing queries or could affect the runtime behavior of clients. For a list of breaking changes and when they will occur, see our [breaking changes log](/graphql/overview/breaking-changes). {% for entry in graphql.changelog %} ### Schema Changes for {{ entry.date }} diff --git a/translations/de-DE/content/graphql/overview/public-schema.md b/translations/de-DE/content/graphql/overview/public-schema.md index 0df87e7653..d2a8c7309b 100644 --- a/translations/de-DE/content/graphql/overview/public-schema.md +++ b/translations/de-DE/content/graphql/overview/public-schema.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -You can [perform introspection](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) against the GraphQL API directly. +You can [perform introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) against the GraphQL API directly. Alternatively, you can download the latest version of the public schema here: diff --git a/translations/de-DE/content/graphql/overview/resource-limitations.md b/translations/de-DE/content/graphql/overview/resource-limitations.md index bd5cdb791c..d0714a5d93 100644 --- a/translations/de-DE/content/graphql/overview/resource-limitations.md +++ b/translations/de-DE/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## Node limit -To pass [schema](/v4/guides/intro-to-graphql#schema) validation, all GraphQL API v4 [calls](/v4/guides/forming-calls) must meet these standards: +To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: -* Clients must supply a `first` or `last` argument on any [connection](/v4/guides/intro-to-graphql#connection). +* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). * Values of `first` and `last` must be within 1-100. -* Individual calls cannot request more than 500,000 total [nodes](/v4/guides/intro-to-graphql#node). +* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). #### Calculating nodes in a call @@ -121,7 +121,7 @@ These two examples show how to calculate the total nodes in a call. The GraphQL API v4 limit is different from the REST API v3's [rate limits](/rest/overview/resources-in-the-rest-api#rate-limiting). -Why are the API rate limits different? With [GraphQL](/v4/), one GraphQL call can replace [multiple REST calls](/v4/guides/migrating-from-rest/). A single complex GraphQL call could be the equivalent of thousands of REST requests. While a single GraphQL call would fall well below the REST API rate limit, the query might be just as expensive for GitHub's servers to compute. +Why are the API rate limits different? With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). A single complex GraphQL call could be the equivalent of thousands of REST requests. While a single GraphQL call would fall well below the REST API rate limit, the query might be just as expensive for GitHub's servers to compute. To accurately represent the server cost of a query, the GraphQL API v4 calculates a call's **rate limit score** based on a normalized scale of points. A query's score factors in first and last arguments on a parent connection and its children. diff --git a/translations/de-DE/content/graphql/overview/schema-previews.md b/translations/de-DE/content/graphql/overview/schema-previews.md index b0b3a5e30f..6272f17066 100644 --- a/translations/de-DE/content/graphql/overview/schema-previews.md +++ b/translations/de-DE/content/graphql/overview/schema-previews.md @@ -13,7 +13,7 @@ versions: During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -To access a schema preview, you'll need to provide a custom [media type](/v3/media) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. +To access a schema preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% note %} diff --git a/translations/de-DE/content/graphql/reference/enums.md b/translations/de-DE/content/graphql/reference/enums.md index 3cec114335..f87cc2e4cc 100644 --- a/translations/de-DE/content/graphql/reference/enums.md +++ b/translations/de-DE/content/graphql/reference/enums.md @@ -12,9 +12,9 @@ versions: [Enums](https://graphql.github.io/graphql-spec/June2018/#sec-Enums) represent possible sets of values for a field. -For example, the [`Issue`](/v4/object/issue) object has a field called `state`. The state is an enum (specifically, of type [`IssueState`](/v4/enum/issuestate/)) because it may be `OPEN` or `CLOSED`. +For example, the [`Issue`](/graphql/reference/objects#issue) object has a field called `state`. The state is an enum (specifically, of type [`IssueState`](/graphql/reference/enums#issuestate)) because it may be `OPEN` or `CLOSED`. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." {% for item in graphql.schemaForCurrentVersion.enums %} {% include graphql-enum %} diff --git a/translations/de-DE/content/graphql/reference/input-objects.md b/translations/de-DE/content/graphql/reference/input-objects.md index 6726cfaf2c..423c6511c8 100644 --- a/translations/de-DE/content/graphql/reference/input-objects.md +++ b/translations/de-DE/content/graphql/reference/input-objects.md @@ -12,9 +12,9 @@ versions: [Input objects](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects) can be described as "composable objects" because they include a set of input fields that define the object. -For example, [`CommitAuthor`](/v4/input_object/commitauthor/) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/v4/object) **may** have input objects, whereas [mutations](/v4/mutation) **require** input objects. +For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/graphql/reference/objects) **may** have input objects, whereas [mutations](/graphql/reference/mutations) **require** input objects. -For more information, see "[About mutations](/v4/guides/forming-calls#about-mutations)." +For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)." {% for item in graphql.schemaForCurrentVersion.inputObjects %} {% include graphql-input-object %} diff --git a/translations/de-DE/content/graphql/reference/interfaces.md b/translations/de-DE/content/graphql/reference/interfaces.md index 0baee2c467..bfc411d796 100644 --- a/translations/de-DE/content/graphql/reference/interfaces.md +++ b/translations/de-DE/content/graphql/reference/interfaces.md @@ -12,9 +12,9 @@ versions: [Interfaces](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces) serve as parent objects from which other objects can inherit. -For example, [`Lockable`](/v4/interface/lockable/) is an interface because both [`Issue`](/v4/object/issue/) and [`PullRequest`](/v4/object/pullrequest/) objects can be locked. An interface has its own list of named fields that are shared by implementing objects. +For example, [`Lockable`](/graphql/reference/interfaces#lockable) is an interface because both [`Issue`](/graphql/reference/objects#issue) and [`PullRequest`](/graphql/reference/objects#pullrequest) objects can be locked. An interface has its own list of named fields that are shared by implementing objects. -For more information, see "[Implementation](/v4/guides/intro-to-graphql#implementation)." +For more information, see "[Implementation](/graphql/guides/introduction-to-graphql#implementation)." {% for item in graphql.schemaForCurrentVersion.interfaces %} {% include graphql-interface %} diff --git a/translations/de-DE/content/graphql/reference/mutations.md b/translations/de-DE/content/graphql/reference/mutations.md index 9f6542ab79..e42955c3d3 100644 --- a/translations/de-DE/content/graphql/reference/mutations.md +++ b/translations/de-DE/content/graphql/reference/mutations.md @@ -12,7 +12,7 @@ versions: Every GraphQL schema has a root type for both queries and mutations. The [mutation type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that change data on the server. It is analogous to performing HTTP verbs such as `POST`, `PATCH`, and `DELETE`. -For more information, see "[About mutations](/v4/guides/forming-calls#about-mutations)." +For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)." {% for item in graphql.schemaForCurrentVersion.mutations %} {% include graphql-mutation %} diff --git a/translations/de-DE/content/graphql/reference/objects.md b/translations/de-DE/content/graphql/reference/objects.md index 84cbbabfdf..345786d5e1 100644 --- a/translations/de-DE/content/graphql/reference/objects.md +++ b/translations/de-DE/content/graphql/reference/objects.md @@ -14,7 +14,7 @@ versions: For example, the [`Repository`](/graphql/reference/objects#repository) object has a field called `name`, which is a `String`. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." diff --git a/translations/de-DE/content/graphql/reference/queries.md b/translations/de-DE/content/graphql/reference/queries.md index 4d87cd2e25..a2cc6af7b1 100644 --- a/translations/de-DE/content/graphql/reference/queries.md +++ b/translations/de-DE/content/graphql/reference/queries.md @@ -13,7 +13,7 @@ versions: Every GraphQL schema has a root type for both queries and mutations. The [query type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that retrieve data from the server. -For more information, see "[About queries](/v4/guides/forming-calls#about-queries)." +For more information, see "[About queries](/graphql/guides/forming-calls-with-graphql#about-queries)." {% note %} diff --git a/translations/de-DE/content/graphql/reference/scalars.md b/translations/de-DE/content/graphql/reference/scalars.md index 0a37135d2c..338b4f42c7 100644 --- a/translations/de-DE/content/graphql/reference/scalars.md +++ b/translations/de-DE/content/graphql/reference/scalars.md @@ -14,7 +14,7 @@ versions: When calling the GraphQL API, you must specify nested subfields until you return only scalars. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql#field)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#field)." {% for item in graphql.schemaForCurrentVersion.scalars %} {% include graphql-scalar %} diff --git a/translations/de-DE/content/graphql/reference/unions.md b/translations/de-DE/content/graphql/reference/unions.md index 95f5a9f633..5a87c63fc0 100644 --- a/translations/de-DE/content/graphql/reference/unions.md +++ b/translations/de-DE/content/graphql/reference/unions.md @@ -12,9 +12,9 @@ versions: A [union](https://graphql.github.io/graphql-spec/June2018/#sec-Unions) is a type of object representing many objects. -For example, a field marked as an [`ProjectCardItem`](/v4/union/projectcarditem/) could be an [`Issue`](/v4/object/issue/) or a [`PullRequest`](/v4/object/pullrequest/) because each of those objects can be inside a project card. Using a union instead of an object gives you flexibility. +For example, a field marked as an [`ProjectCardItem`](/graphql/reference/unions#projectcarditem) could be an [`Issue`](/graphql/reference/objects#issue) or a [`PullRequest`](/graphql/reference/objects#pullrequest) because each of those objects can be inside a project card. Using a union instead of an object gives you flexibility. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." {% for item in graphql.schemaForCurrentVersion.unions %} {% include graphql-union %} diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index a63e40967e..20b33760bb 100644 --- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: Enabling a link between GitHub Insights and GitHub Enterprise -intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {{ site.data.variables.product.prodname_insights }}.' +intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.' redirect_from: diff --git a/translations/de-DE/content/packages/publishing-and-managing-packages/about-github-packages.md b/translations/de-DE/content/packages/publishing-and-managing-packages/about-github-packages.md index a011723672..a513c7c5eb 100644 --- a/translations/de-DE/content/packages/publishing-and-managing-packages/about-github-packages.md +++ b/translations/de-DE/content/packages/publishing-and-managing-packages/about-github-packages.md @@ -182,7 +182,7 @@ Weitere Informationen findest Du unter: ### Managing packages -You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package)" and "[Forming calls with GraphQL](/v4/guides/forming-calls/)." +You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." diff --git a/translations/de-DE/content/rest/guides/basics-of-authentication.md b/translations/de-DE/content/rest/guides/basics-of-authentication.md index b8805432ed..beffcede81 100644 --- a/translations/de-DE/content/rest/guides/basics-of-authentication.md +++ b/translations/de-DE/content/rest/guides/basics-of-authentication.md @@ -130,7 +130,7 @@ Also, since there's a hierarchical relationship between scopes, you should check Checking for scopes only before making requests is not enough since it's possible that users will change the scopes in between your check and the actual request. In case that happens, API calls you expected to succeed might fail with a `404` or `401` status, or return a different subset of information. -To help you gracefully handle these situations, all API responses for requests made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes]. This header contains the list of scopes of the token that was used to make the request. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/v3/apps/oauth_applications/#check-an-authorization\]{% endif %}. Use this information to detect changes in token scopes, and inform your users of changes in available application functionality. +To help you gracefully handle these situations, all API responses for requests made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes]. This header contains the list of scopes of the token that was used to make the request. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. Use this information to detect changes in token scopes, and inform your users of changes in available application functionality. #### Making authenticated requests diff --git a/translations/de-DE/content/rest/guides/best-practices-for-integrators.md b/translations/de-DE/content/rest/guides/best-practices-for-integrators.md index a391e94b22..a376d64466 100644 --- a/translations/de-DE/content/rest/guides/best-practices-for-integrators.md +++ b/translations/de-DE/content/rest/guides/best-practices-for-integrators.md @@ -20,7 +20,7 @@ It's very important that you secure [the payloads sent from GitHub][event-types] There are several steps you can take to secure receipt of payloads delivered by GitHub: 1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% if currentVersion == "free-pro-team@latest" %} -1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/v3/meta/#meta) to find the address we use.{% endif %} +1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %} 1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected. ### Favor asynchronous work over synchronous @@ -49,7 +49,7 @@ Users can dig into the server responses you send back to GitHub. Ensure that you GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove. -We've provided [a list of HTTP status codes](/v3/#http-redirects) to watch out for when designing your app to follow redirects. +We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects. ### Don't manually parse URLs diff --git a/translations/de-DE/content/rest/guides/building-a-ci-server.md b/translations/de-DE/content/rest/guides/building-a-ci-server.md index 592ca8ba71..b9e39de44c 100644 --- a/translations/de-DE/content/rest/guides/building-a-ci-server.md +++ b/translations/de-DE/content/rest/guides/building-a-ci-server.md @@ -129,7 +129,7 @@ At GitHub, we've used a version of [Janky][janky] to manage our CI for years. Th All of this communication is funneled back to our chat rooms. You don't need to build your own CI setup to use this example. You can always rely on [GitHub integrations][integrations]. -[status API]: /v3/repos/statuses/ +[status API]: /rest/reference/repos#statuses [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server diff --git a/translations/de-DE/content/rest/guides/delivering-deployments.md b/translations/de-DE/content/rest/guides/delivering-deployments.md index 76ac7fb5cd..a5b82c37f3 100644 --- a/translations/de-DE/content/rest/guides/delivering-deployments.md +++ b/translations/de-DE/content/rest/guides/delivering-deployments.md @@ -145,7 +145,7 @@ At GitHub, we've used a version of [Heaven][heaven] to manage our deployments fo Das war alles. You don't need to build your own deployment setup to use this example. You can always rely on [GitHub integrations][integrations]. -[deploy API]: /v3/repos/deployments/ +[deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok diff --git a/translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md b/translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md index 2f7cfa0e05..b8842420aa 100644 --- a/translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md @@ -93,19 +93,19 @@ If you've read the docs from cover to cover, you may have noticed an [API method As an application, you typically want all of the user's organizations (public and private) that your app is authorized to access. The workflow above will give you exactly that. -[basics-of-authentication]: /v3/guides/basics-of-authentication/ -[list-public-orgs]: /v3/orgs/#list-organizations-for-a-user -[list-repositories-for-current-user]: /v3/repos/#list-repositories-for-the-authenticated-user -[list-orgs-for-current-user]: /v3/orgs/#list-organizations-for-the-authenticated-user -[list-teams]: /v3/teams/#list-teams -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests +[basics-of-authentication]: /rest/guides/basics-of-authentication +[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user +[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user +[list-teams]: /rest/reference/teams#list-teams +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ [octokit.rb]: https://github.com/octokit/octokit.rb [octokit.rb]: https://github.com/octokit/octokit.rb -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user -[publicize-membership]: /v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user -[register-oauth-app]: /v3/guides/basics-of-authentication/#registering-your-app +[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user +[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md index ee3e7673dd..5af009b4fc 100644 --- a/translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md +++ b/translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md @@ -11,7 +11,7 @@ versions: This basically allows you to reimplement a lot of Git functionality over our API - by creating raw objects directly into the database and updating branch references you could technically do just about anything that Git can do without having Git installed. -Git Database API functions will return a `409 Conflict` if the Git repository is empty or unavailable. An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the "[Create or update file contents](/v3/repos/contents/#create-or-update-file-contents)" endpoint to create content and initialize the repository so you can use the Git Database API. Contact {% data variables.contact.contact_support %} if this response status persists. +Git Database API functions will return a `409 Conflict` if the Git repository is empty or unavailable. An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" endpoint to create content and initialize the repository so you can use the Git Database API. Contact {% data variables.contact.contact_support %} if this response status persists. ![git database overview](/assets/images/git-database-overview.png) @@ -33,14 +33,14 @@ It might seem complex, but it's actually pretty simple when you understand the m {% warning %} -**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. +**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. {% endwarning %} -A consuming API needs to explicitly request a pull request to create a _test_ merge commit. A _test_ merge commit is created when you view the pull request in the UI and the "Merge" button is displayed, or when you [get](/v3/pulls/#get-a-pull-request), [create](/v3/pulls/#create-a-pull-request), or [edit](/v3/pulls/#update-a-pull-request) a pull request using the REST API. Without this request, the `merge` Git refs will fall out of date until the next time someone views the pull request. +A consuming API needs to explicitly request a pull request to create a _test_ merge commit. A _test_ merge commit is created when you view the pull request in the UI and the "Merge" button is displayed, or when you [get](/rest/reference/pulls#get-a-pull-request), [create](/rest/reference/pulls#create-a-pull-request), or [edit](/rest/reference/pulls#update-a-pull-request) a pull request using the REST API. Without this request, the `merge` Git refs will fall out of date until the next time someone views the pull request. If you are currently using polling methods that produce outdated `merge` Git refs, then GitHub recommends using the following steps to get the latest changes from the base branch (usually `master`): 1. Receive the pull request webhook. -2. Call [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) to start a background job for creating the merge commit candidate. -3. Poll your repository using [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) to see if the `mergeable` attribute is `true` or `false`. You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. +2. Call [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) to start a background job for creating the merge commit candidate. +3. Poll your repository using [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) to see if the `mergeable` attribute is `true` or `false`. You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md index 6578212b39..4934a7d00c 100644 --- a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md @@ -367,33 +367,33 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]! [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[repos-api]: /v3/repos/ -[repos-api]: /v3/repos/ +[repos-api]: /rest/reference/repos +[repos-api]: /rest/reference/repos [pages]: http://pages.github.com [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore -[issues-api]: /v3/issues/ +[issues-api]: /rest/reference/issues [link-header]: http://www.w3.org/wiki/LinkHeader/ -[conditional-requests]: /v3/#conditional-requests -[rate-limiting]: /v3/#rate-limiting -[rate-limiting]: /v3/#rate-limiting -[users api]: /v3/users/#get-a-user +[conditional-requests]: /rest#conditional-requests +[rate-limiting]: /rest#rate-limiting +[rate-limiting]: /rest#rate-limiting +[users api]: /rest/reference/users#get-a-user [defunkt github]: https://github.com/defunkt [defunkt github]: https://github.com/defunkt [json]: http://en.wikipedia.org/wiki/JSON -[authentication]: /v3/#authentication +[authentication]: /rest#authentication [personal token]: /articles/creating-an-access-token-for-command-line-use [personal token]: /articles/creating-an-access-token-for-command-line-use [tokens settings]: https://github.com/settings/tokens -[pagination]: /v3/#pagination -[get repo]: /v3/repos/#get-a-repository -[create repo]: /v3/repos/#create-a-repository-for-the-authenticated-user -[create issue]: /v3/issues/#create-an-issue +[pagination]: /rest#pagination +[get repo]: /rest/reference/repos#get-a-repository +[create repo]: /rest/reference/repos#create-a-repository-for-the-authenticated-user +[create issue]: /rest/reference/issues#create-an-issue [auth guide]: /guides/basics-of-authentication -[user repos api]: /v3/repos/#list-repositories-for-the-authenticated-user -[other user repos api]: /v3/repos/#list-repositories-for-a-user -[org repos api]: /v3/repos/#list-organization-repositories -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[repo issues api]: /v3/issues/#list-repository-issues +[user repos api]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[other user repos api]: /rest/reference/repos#list-repositories-for-a-user +[org repos api]: /rest/reference/repos#list-organization-repositories +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[repo issues api]: /rest/reference/issues#list-repository-issues [etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/de-DE/content/rest/guides/rendering-data-as-graphs.md b/translations/de-DE/content/rest/guides/rendering-data-as-graphs.md index 6dd3ac0e9b..db04598e36 100644 --- a/translations/de-DE/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/de-DE/content/rest/guides/rendering-data-as-graphs.md @@ -333,7 +333,7 @@ Et voila! Beautiful rectangles containing your repo languages, with relative pro [Octokit]: https://github.com/octokit/octokit.rb [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ [D3 treemap]: http://bl.ocks.org/mbostock/4063582 -[language API]: /v3/repos/#list-repository-languages -[language API]: /v3/repos/#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs [new oauth application]: https://github.com/settings/applications/new diff --git a/translations/de-DE/content/rest/guides/traversing-with-pagination.md b/translations/de-DE/content/rest/guides/traversing-with-pagination.md index e3171400f0..7783f89877 100644 --- a/translations/de-DE/content/rest/guides/traversing-with-pagination.md +++ b/translations/de-DE/content/rest/guides/traversing-with-pagination.md @@ -20,9 +20,9 @@ In this guide, we'll make some calls to the {% data variables.product.product_na To start with, it's important to know a few facts about receiving paginated items: -1. Different API calls respond with different defaults. For example, a call to [List public repositories](/v3/repos/#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API provides items in sets of 100 +1. Different API calls respond with different defaults. For example, a call to [List public repositories](/rest/reference/repos#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API provides items in sets of 100 2. You can specify how many items to receive (up to a maximum of 100); but, -3. For technical reasons, not every endpoint behaves the same. For example, [events](/v3/activity/events/) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. +3. For technical reasons, not every endpoint behaves the same. For example, [events](/rest/reference/activity#events) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. Information about pagination is provided in [the Link header](http://tools.ietf.org/html/rfc5988) of an API call. For example, let's make a curl request to the search API, to find out how many times Mozilla projects use the phrase `addClass`: @@ -201,7 +201,7 @@ puts "The prev page link is #{prev_page_href}" puts "The next page link is #{next_page_href}" ``` -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination [octokit.rb]: https://github.com/octokit/octokit.rb [personal token]: /articles/creating-an-access-token-for-command-line-use diff --git a/translations/de-DE/content/rest/guides/working-with-comments.md b/translations/de-DE/content/rest/guides/working-with-comments.md index eb56a1f30e..4b48576560 100644 --- a/translations/de-DE/content/rest/guides/working-with-comments.md +++ b/translations/de-DE/content/rest/guides/working-with-comments.md @@ -97,8 +97,8 @@ Note that this API call will retrieve single line comments, as well as comments [commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 [sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 [platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments -[issues]: /v3/issues/comments/ +[issues]: /rest/reference/issues#comments [personal token]: /articles/creating-an-access-token-for-command-line-use [octokit.rb]: https://github.com/octokit/octokit.rb -[PR Review API]: /v3/pulls/comments/ -[commit comment API]: /v3/repos/comments/#get-a-commit-comment +[PR Review API]: /rest/reference/pulls#comments +[commit comment API]: /rest/reference/repos#get-a-commit-comment diff --git a/translations/de-DE/content/rest/overview/api-previews.md b/translations/de-DE/content/rest/overview/api-previews.md index 24757eff31..892472c4de 100644 --- a/translations/de-DE/content/rest/overview/api-previews.md +++ b/translations/de-DE/content/rest/overview/api-previews.md @@ -15,12 +15,12 @@ API previews let you try out new APIs and changes to existing API methods before During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -To access an API preview, you'll need to provide a custom [media type](/v3/media) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. +To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% if currentVersion == "free-pro-team@latest" %} ### Migrations -Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/v3/migrations/) data to {% data variables.product.prodname_ghe_server %}. +Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/rest/reference/migrations) data to {% data variables.product.prodname_ghe_server %}. **Custom media type:** `wyandotte-preview` **Announced:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) {% endif %} @@ -33,13 +33,13 @@ Exercise greater control over [deployments](/rest/reference/repos#deployments) w ### Reactions -Manage [reactions](/v3/reactions/) for commits, issues, and comments. +Manage [reactions](/rest/reference/reactions) for commits, issues, and comments. **Custom media type:** `squirrel-girl-preview` **Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) ### Timeline -Get a [list of events](/v3/issues/timeline/) for an issue or pull request. +Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request. **Custom media type:** `mockingbird-preview` **Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) @@ -61,40 +61,40 @@ Manage [integrations](/early-access/integrations/) through the API. ### Projekte -Manage [projects](/v3/projects/). +Manage [projects](/rest/reference/projects). **Custom media type:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) ### Commit search -[Search commits](/v3/search/). +[Search commits](/rest/reference/search). **Custom media type:** `cloak-preview` **Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% if currentVersion == "free-pro-team@latest" %} ### User blocking -Users can [block other users](/v3/users/blocking/). Organizations can [block users](/v3/orgs/blocking/), too. +Users can [block other users](/rest/reference/users#blocking). Organizations can [block users](/rest/reference/orgs#blocking), too. **Custom media type:** `giant-sentry-fist-preview` **Announced:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Update 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Update 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) {% endif %} ### Repository topics -View a list of [repository topics](/articles/about-topics/) in [calls](/v3/repos/) that return repository results. +View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results. **Custom media type:** `mercy-preview` **Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics) ### Codes of conduct -View all [codes of conduct](/v3/codes_of_conduct) or get which code of conduct a repository has currently. +View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently. **Custom media type:** `scarlet-witch-preview` {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### Verschachtelte Teams -Include nested team content in [team](/v3/teams/) payloads. +Include nested team content in [team](/rest/reference/teams) payloads. **Custom media type:** `hellcat-preview` **Announced:** [2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) @@ -113,7 +113,7 @@ Enables [global webhooks](/rest/reference/enterprise-admin#global-webhooks/) for {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### Repository transfer -Transfer a [repository](/v3/repos/) to an organization or user. +Transfer a [repository](/rest/reference/repos) to an organization or user. **Custom media type:** `nightshade-preview` **Announced:** [2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) {% endif %} @@ -121,27 +121,27 @@ Transfer a [repository](/v3/repos/) to an organization or user. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### Add lock reason -You can now add a reason when you [lock an issue](/v3/issues/#lock-an-issue). +You can now add a reason when you [lock an issue](/rest/reference/issues#lock-an-issue). **Custom media type:** `sailor-v-preview` **Announced:** [2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) {% endif %} ### Require signed commits -You can now use the API to manage the setting for [requiring signed commits on protected branches](/v3/repos/branches). +You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches). **Custom media type:** `zzzax-preview` **Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) ### Require multiple approving reviews -You can now [require multiple approving reviews](/v3/repos/branches) for a pull request using the API. +You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API. **Custom media type:** `luke-cage-preview` **Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.19" %} ### Retrieve hovercard information -Retrieve information from [someone's hovercard](/v3/users/#get-contextual-information-for-a-user). +Retrieve information from [someone's hovercard](/rest/reference/users#get-contextual-information-for-a-user). **Custom media type:** `hagar-preview` **Announced:** [2018-03-21](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) @@ -150,7 +150,7 @@ Retrieve information from [someone's hovercard](/v3/users/#get-contextual-inform {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} ### Check runs and check suites API -Allows a GitHub App to run external checks on a repository's code. See the [Check runs](/v3/checks/runs/) and [Check suites](/v3/checks/suites/) APIs for more details. +Allows a GitHub App to run external checks on a repository's code. See the [Check runs](/rest/reference/checks#runs) and [Check suites](/rest/reference/checks#suites) APIs for more details. **Custom media type:** `antiope-preview` **Announced:** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) {% endif %} @@ -167,7 +167,7 @@ When a {% data variables.product.prodname_ghe_server %} instance is in private m ### Project card details -The REST API responses for [issue events](/v3/issues/events/) and [issue timeline events](/v3/issues/timeline/) now return the `project_card` field for project-related events. +The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events. **Custom media type:** `starfox-preview` **Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) @@ -189,7 +189,7 @@ You can now update the `environment` of a [deployment status](/rest/reference/re ### Repository creation permissions -You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/v3/orgs/#update-an-organization)" for more details. +You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details. **Custom media types:** `surtur-preview` **Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) @@ -202,7 +202,7 @@ You can now provide more information in GitHub for URLs that link to registered {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### Entwürfe für Pull Requests -You can use the Draft Pull Requests API and its [pull request](/v3/pulls/) endpoints to see whether a pull request is in draft state. To learn more about draft pull requests, see "[About pull requests](/articles/about-pull-requests/)". +You can use the Draft Pull Requests API and its [pull request](/rest/reference/pulls) endpoints to see whether a pull request is in draft state. To learn more about draft pull requests, see "[About pull requests](/articles/about-pull-requests/)". **Custom media types:** `shadow-cat-preview` **Announced:** [2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) @@ -216,48 +216,48 @@ You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to ### List branches or pull requests for a commit -You can use two new endpoints in the [Commits API](/v3/repos/commits/) to list branches or pull requests for a commit. +You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit. **Custom media types:** `groot-preview` **Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### Uninstall a GitHub App -Owners of GitHub Apps can now uninstall an app using the [Apps API](/v3/apps/#delete-an-installation-for-the-authenticated-app). +Owners of GitHub Apps can now uninstall an app using the [Apps API](/rest/reference/apps#delete-an-installation-for-the-authenticated-app). **Custom media types:** `gambit-preview` {% endif %} ### Enable or disable vulnerability alerts for a repository -You can use two new endpoints in the [Repos API](/v3/repos/) to enable or disable vulnerability alerts. +You can use two new endpoints in the [Repos API](/rest/reference/repos) to enable or disable vulnerability alerts. **Custom media types:** `dorian-preview` **Announced:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) ### Update a pull request branch -You can use a new endpoint to [update a pull request branch](/v3/pulls/#update-a-pull-request-branch) with changes from the HEAD of the upstream branch. +You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch. **Custom media types:** `lydian-preview` **Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) {% if currentVersion == "free-pro-team@latest" %} ### Enable or disable automated security fixes -You can use a new set of endpoints to [enable and disable automated security fixes](/v3/repos/#enable-automated-security-fixes). +You can use a new set of endpoints to [enable and disable automated security fixes](/rest/reference/repos#enable-automated-security-fixes). **Custom media types:** `london-preview` **Announced:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ### Create and use repository templates -You can use a new endpoint to [Create a repository using a template](/v3/repos/#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/v3/repos/#get-a-repository) to check whether it's set as a template repository using the `is_template` key. +You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key. **Custom media types:** `baptiste-preview` **Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% if currentVersion == "enterprise-server@2.20" %} ### New OAuth Applications API endpoints -You can more securely manage tokens for OAuth Apps by using OAuth tokens as input parameters instead of path parameters with the new [OAuth Applications API](/v3/apps/oauth_applications/) endpoints. +You can more securely manage tokens for OAuth Apps by using OAuth tokens as input parameters instead of path parameters with the new [OAuth Applications API](/rest/reference/apps#oauth-applications) endpoints. **Custom media types:** `doctor-strange-preview` **Announced:** [2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) {% endif %} @@ -265,7 +265,7 @@ You can more securely manage tokens for OAuth Apps by using OAuth tokens as inpu {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ### New visibility parameter for the Repositories API -You can set and retrieve the visibility of a repository in the [Repositories API](/v3/repos/). +You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos). **Custom media types:** `nebula-preview` **Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/de-DE/content/rest/overview/media-types.md b/translations/de-DE/content/rest/overview/media-types.md index 3be3277dfa..d8db60a892 100644 --- a/translations/de-DE/content/rest/overview/media-types.md +++ b/translations/de-DE/content/rest/overview/media-types.md @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### Comment body properties -The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/v3/issues/), [issue comments](/v3/issues/comments/), [pull request comments](/v3/pulls/comments/), and the [gist comments](/v3/gists/comments/) APIs all accept these same media types: +The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: #### Raw @@ -85,7 +85,7 @@ Return raw, text and HTML representations. Response will include `body`, `body_t ### Git blob properties -The following media types are allowed when [getting a blob](/v3/git/blobs/#get-a-blob): +The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): #### JSON @@ -102,7 +102,7 @@ Return the raw blob data. ### Commits, commit comparison, and pull requests -The [commits API](/v3/repos/commits/) and [pull requests API](/v3/pulls/) support [diff][git-diff] and [patch][git-patch] formats: +The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: #### Diff @@ -147,4 +147,4 @@ The gist contents are base64-encoded before being sent out. This can be useful i [gfm]: http://github.github.com/github-flavored-markdown/ [git-diff]: http://git-scm.com/docs/git-diff [git-patch]: http://git-scm.com/docs/git-format-patch -[versions]: /v3/versions +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/de-DE/content/rest/overview/other-authentication-methods.md b/translations/de-DE/content/rest/overview/other-authentication-methods.md index abfdebe4a2..96c3312c67 100644 --- a/translations/de-DE/content/rest/overview/other-authentication-methods.md +++ b/translations/de-DE/content/rest/overview/other-authentication-methods.md @@ -59,7 +59,7 @@ For example, if you're accessing the API via [cURL][curl], the following command ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/v3/auth/#working-with-two-factor-authentication). +If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). {% endif %} @@ -124,8 +124,8 @@ $ curl --request POST \ {% endif %} [curl]: http://curl.haxx.se/ -[oauth-auth]: /v3/#authentication +[oauth-auth]: /rest#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -[user-issues]: /v3/issues/#list-issues-assigned-to-the-authenticated-user +[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md index 0810b401dc..accaa33077 100644 --- a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md @@ -14,13 +14,13 @@ This describes the resources that make up the official {% data variables.product ### Current version -By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/v3/versions) of the REST API. We encourage you to [explicitly request this version via the `Accept` header](/v3/media/#request-specific-version). +By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API. We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version). Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -For information about GitHub's GraphQL API, see the [v4 documentation](/v4). For information about migrating to GraphQL, see "[Migrating from REST](/v4/guides/migrating-from-rest/)." +For information about GitHub's GraphQL API, see the [v4 documentation](/graphql). For information about migrating to GraphQL, see "[Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql)." {% endif %} @@ -171,7 +171,7 @@ $ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "gith ### GraphQL global node IDs -See the guide on "[Using Global Node IDs](/v4/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. +See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. ### Client errors @@ -262,7 +262,7 @@ You can then expand these templates using something like the [uri_template][uri] ### Pagination -Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/v3/activity/events/) for example. +Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' @@ -287,7 +287,7 @@ The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination inform _The example includes a line break for readability._ -This `Link` response header contains one or more [Hypermedia](/v3/#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). +This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). The possible `rel` values are: @@ -312,7 +312,7 @@ For unauthenticated requests, the rate limit allows for up to 60 requests per ho {% data reusables.enterprise.rate_limit %} -Note that [the Search API has custom rate limit rules](/v3/search/#rate-limit). +Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). The returned HTTP headers of any API request show your current rate limit status: @@ -355,7 +355,7 @@ If you exceed the rate limit, an error response returns: > } ``` -You can [check your rate limit status](/v3/rate_limit) without incurring an API hit. +You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. #### Increasing the unauthenticated rate limit for OAuth applications @@ -586,9 +586,9 @@ Some requests that create new data, such as creating a new commit, allow you to #### Explicitly providing an ISO 8601 timestamp with timezone information -For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/v3/git/commits). +For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits). -These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/v3/git/commits/#example-input) for how these timestamps can be specified. +These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. #### Using the `Time-Zone` header @@ -598,7 +598,7 @@ It is possible to supply a `Time-Zone` header which defines a timezone according $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/v3/repos/contents/) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. +This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. #### Using the last known timezone for the user diff --git a/translations/de-DE/content/rest/overview/troubleshooting.md b/translations/de-DE/content/rest/overview/troubleshooting.md index 2e9e3993b8..2f20648606 100644 --- a/translations/de-DE/content/rest/overview/troubleshooting.md +++ b/translations/de-DE/content/rest/overview/troubleshooting.md @@ -23,7 +23,7 @@ To troubleshoot, ensure [you're authenticating correctly](/guides/getting-starte Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support pagination. If you're making requests and receiving an incomplete set of results, you're probably only seeing the first page. You'll need to request the remaining pages in order to get more results. -It's important to *not* try and guess the format of the pagination URL. Not every API call uses the same structure. Instead, extract the pagination information from [the Link Header](/v3/#pagination), which is sent with every request. +It's important to *not* try and guess the format of the pagination URL. Not every API call uses the same structure. Instead, extract the pagination information from [the Link Header](/rest#pagination), which is sent with every request. {% if currentVersion == "free-pro-team@latest" %} ### Basic authentication errors diff --git a/translations/de-DE/content/rest/reference/apps.md b/translations/de-DE/content/rest/reference/apps.md index 990731db4f..84878d9041 100644 --- a/translations/de-DE/content/rest/reference/apps.md +++ b/translations/de-DE/content/rest/reference/apps.md @@ -18,7 +18,7 @@ When authenticated as a GitHub App, the GitHub Apps API enables you to get high- 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](/v3/apps/installations/) for a list of these endpoints. +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 %} @@ -36,7 +36,7 @@ You can use this API to manage the OAuth tokens an OAuth application uses to acc 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](/v3/orgs/#list-app-installations-for-an-organization)." +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 %} @@ -70,4 +70,4 @@ Be sure to replace stubbed endpoints with production endpoints before deploying {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/de-DE/content/rest/reference/codes-of-conduct.md b/translations/de-DE/content/rest/reference/codes-of-conduct.md index 16d7e8bda3..50cb78757e 100644 --- a/translations/de-DE/content/rest/reference/codes-of-conduct.md +++ b/translations/de-DE/content/rest/reference/codes-of-conduct.md @@ -9,6 +9,6 @@ versions: github-ae: '*' --- -You can use the Codes of Conduct API to retrieve information about a repository's code of conduct. To get a repository's code of conduct, use the "[Get a repository](/v3/repos/#get-a-repository)" endpoint. +You can use the Codes of Conduct API to retrieve information about a repository's code of conduct. To get a repository's code of conduct, use the "[Get a repository](/rest/reference/repos#get-a-repository)" endpoint. {% include rest_operations_at_current_path %} diff --git a/translations/de-DE/content/rest/reference/enterprise-admin.md b/translations/de-DE/content/rest/reference/enterprise-admin.md index 3838ab445d..2a653ff069 100644 --- a/translations/de-DE/content/rest/reference/enterprise-admin.md +++ b/translations/de-DE/content/rest/reference/enterprise-admin.md @@ -86,7 +86,7 @@ The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/v3/auth/#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim).“ +**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim).“ {% endnote %} diff --git a/translations/de-DE/content/rest/reference/git.md b/translations/de-DE/content/rest/reference/git.md index ef43832bc6..4d3d088ee8 100644 --- a/translations/de-DE/content/rest/reference/git.md +++ b/translations/de-DE/content/rest/reference/git.md @@ -34,7 +34,7 @@ For more information, see "[Media types](/rest/overview/media-types)." ## Commits -A Git commit is a snapshot of the hierarchy ([Git tree](/v3/git/trees)) and the contents of the files ([Git blob](/v3/git/blobs)) in a Git repository. These endpoints allow you to read and write [commit objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) to your Git database on {% data variables.product.product_name %}. +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. These endpoints allow you to read and write [commit objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) to your Git database on {% data variables.product.product_name %}. {% for operation in currentRestOperations %} {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} @@ -50,7 +50,7 @@ A Git reference (`git ref`) is just a file that contains a Git commit SHA-1 hash ## Tags -A Git tag is similar to a [Git reference](/v3/git/refs), but the Git commit that it points to never changes. Git tags are helpful when you want to point to specific releases. These endpoints allow you to read and write [tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) to your Git database on {% data variables.product.product_name %}. The Git tags API only supports [annotated tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), not lightweight tags. +A Git tag is similar to a [Git reference](/rest/reference/git#refs), but the Git commit that it points to never changes. Git tags are helpful when you want to point to specific releases. These endpoints allow you to read and write [tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) to your Git database on {% data variables.product.product_name %}. The Git tags API only supports [annotated tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), not lightweight tags. {% for operation in currentRestOperations %} {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %} diff --git a/translations/de-DE/content/rest/reference/issues.md b/translations/de-DE/content/rest/reference/issues.md index 62a919e526..19d98dfb0a 100644 --- a/translations/de-DE/content/rest/reference/issues.md +++ b/translations/de-DE/content/rest/reference/issues.md @@ -33,7 +33,7 @@ For more information about media types, see "[Custom media types](/rest/overview The Issue Comments API supports listing, viewing, editing, and creating comments on issues and pull requests. -Issue Comments use [these custom media types](#custom-media-types). You can read more about the use of media types in the API [here](/v3/media/). +Issue Comments use [these custom media types](#custom-media-types). 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 == 'comments' %}{% include rest_operation %}{% endif %} diff --git a/translations/de-DE/content/rest/reference/licenses.md b/translations/de-DE/content/rest/reference/licenses.md index 547bf45860..ae9673c83b 100644 --- a/translations/de-DE/content/rest/reference/licenses.md +++ b/translations/de-DE/content/rest/reference/licenses.md @@ -16,12 +16,12 @@ If a license is matched, the license key and name returned conforms to the [SPDX **Note:** These endpoints will also return a repository's license information: -- [Get a repository](/v3/repos/#get-a-repository) -- [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -- [Repositorys einer Organisation auflisten](/v3/repos/#list-organization-repositories) +- [Get a repository](/rest/reference/repos#get-a-repository) +- [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user) +- [Repositorys einer Organisation auflisten](/rest/reference/repos#list-organization-repositories) - [List forks](/rest/reference/repos#list-forks) - [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user) -- [List team repositories](/v3/teams/#list-team-repositories) +- [List team repositories](/rest/reference/teams#list-team-repositories) {% warning %} diff --git a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md index 6400690980..f0d51a1304 100644 --- a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md @@ -19,63 +19,63 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe {% data reusables.apps.metadata-permissions %} -- [`GET /`](/v3/#root-endpoint) -- [`GET /codes_of_conduct`](/v3/codes_of_conduct/#get-all-codes-of-conduct) -- [`GET /codes_of_conduct/:key`](/v3/codes_of_conduct/#get-a-code-of-conduct) -- [`GET /emojis`](/v3/emojis/#emojis) +- [`GET /`](/rest#root-endpoint) +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +- [`GET /emojis`](/rest/reference/emojis#emojis) - [`GET /feeds`](/rest/reference/activity#get-feeds) -- [`GET /licenses`](/v3/licenses/#get-all-commonly-used-licenses) -- [`GET /licenses/:key`](/v3/licenses/#get-a-license) -- [`POST /markdown`](/v3/markdown/#render-a-markdown-document) -- [`POST /markdown/raw`](/v3/markdown/#render-a-markdown-document-in-raw-mode) -- [`GET /meta`](/v3/meta/#meta) -- [`GET /organizations`](/v3/orgs/#list-organizations) -- [`GET /orgs/:org`](/v3/orgs/#get-an-organization) -- [`GET /orgs/:org/projects`](/v3/projects/#list-organization-projects) -- [`GET /orgs/:org/repos`](/v3/repos/#list-organization-repositories) -- [`GET /rate_limit`](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) -- [`GET /repos/:owner/:repo`](/v3/repos/#get-a-repository) +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license) +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +- [`GET /meta`](/rest/reference/meta#meta) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization) +- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects) +- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories) +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/community/profile`](/v3/repos/community/#get-community-profile-metrics) +- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics) {% endif %} -- [`GET /repos/:owner/:repo/contributors`](/v3/repos/#list-repository-contributors) +- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors) - [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks) -- [`GET /repos/:owner/:repo/languages`](/v3/repos/#list-repository-languages) -- [`GET /repos/:owner/:repo/license`](/v3/licenses/#get-the-license-for-a-repository) +- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository) - [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers) -- [`GET /repos/:owner/:repo/stats/code_frequency`](/v3/repos/statistics/#get-the-weekly-commit-activity) -- [`GET /repos/:owner/:repo/stats/commit_activity`](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -- [`GET /repos/:owner/:repo/stats/contributors`](/v3/repos/statistics/#get-all-contributor-commit-activity) -- [`GET /repos/:owner/:repo/stats/participation`](/v3/repos/statistics/#get-the-weekly-commit-count) -- [`GET /repos/:owner/:repo/stats/punch_card`](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity) +- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity) +- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity) +- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count) +- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) - [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers) -- [`GET /repos/:owner/:repo/tags`](/v3/repos/#list-repository-tags) -- [`GET /repos/:owner/:repo/topics`](/v3/repos#get-all-repository-topics) -- [`GET /repositories`](/v3/repos/#list-public-repositories) -- [`GET /user/repos`](/v3/repos/#list-repositories-for-the-authenticated-user) +- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) - [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) - [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) -- [`GET /users`](/v3/users/#list-users) -- [`GET /users/:username`](/v3/users/#get-a-user) -- [`GET /users/:username/followers`](/v3/users/followers/#list-followers-of-a-user) -- [`GET /users/:username/following`](/v3/users/followers/#list-the-people-a-user-follows) -- [`GET /users/:username/following/:target_user`](/v3/users/followers/#check-if-a-user-follows-another-user) -- [`GET /users/:username/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) -- [`GET /users/:username/orgs`](/v3/orgs/#list-organizations-for-a-user) +- [`GET /users`](/rest/reference/users#list-users) +- [`GET /users/:username`](/rest/reference/users#get-a-user) +- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user) - [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) - [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) -- [`GET /users/:username/repos`](/v3/repos/#list-repositories-for-a-user) +- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) _Mitarbeiter_ -- [`GET /repos/:owner/:repo/collaborators`](/v3/repos/collaborators/#list-repository-collaborators) -- [`GET /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) +- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) +- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) _Commit-Kommentare_ -- [`GET /repos/:owner/:repo/comments`](/v3/repos/comments/#list-commit-comments-for-a-repository) -- [`GET /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#get-a-commit-comment) -- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-commit-comment) -- [`GET /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#list-commit-comments) +- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) +- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) +- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) _Ereignisse_ - [`GET /events`](/rest/reference/activity#list-public-events) @@ -86,311 +86,311 @@ _Ereignisse_ - [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user) _Git_ -- [`GET /gitignore/templates`](/v3/gitignore/#get-all-gitignore-templates) -- [`GET /gitignore/templates/:key`](/v3/gitignore/#get-a-gitignore-template) +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) +- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) _Keys_ -- [`GET /users/:username/keys`](/v3/users/keys/#list-public-keys-for-a-user) +- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) _Organization members_ -- [`GET /orgs/:org/members`](/v3/orgs/members/#list-organization-members) -- [`GET /orgs/:org/members/:username`](/v3/orgs/members/#check-organization-membership-for-a-user) -- [`GET /orgs/:org/public_members`](/v3/orgs/members/#list-public-organization-members) -- [`GET /orgs/:org/public_members/:username`](/v3/orgs/members/#check-public-organization-membership-for-a-user) +- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`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) _Suche_ -- [`GET /search/code`](/v3/search/#search-code) -- [`GET /search/commits`](/v3/search/#search-commits) -- [`GET /search/issues`](/v3/search/#search-issues-and-pull-requests) -- [`GET /search/labels`](/v3/search/#search-labels) -- [`GET /search/repositories`](/v3/search/#search-repositories) -- [`GET /search/topics`](/v3/search/#search-topics) -- [`GET /search/users`](/v3/search/#search-users) +- [`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) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "actions" -- [`GET /repos/:owner/:repo/actions/artifacts`](/v3/actions/artifacts/#list-artifacts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} ### Permission on "administration" -- [`POST /orgs/:org/repos`](/v3/repos/#create-an-organization-repository) (:write) -- [`PATCH /repos/:owner/:repo`](/v3/repos/#update-a-repository) (:write) -- [`DELETE /repos/:owner/:repo`](/v3/repos/#delete-a-repository) (:write) +- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) +- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) +- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) (:read) -- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) (:write)git +- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write)git {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#enable-automated-security-fixes) (:write) +- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#disable-automated-security-fixes) (:write) +- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:write) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write) {% endif %} -- [`PUT /repos/:owner/:repo/topics`](/v3/repos/#replace-all-repository-topics) (:write) -- [`POST /repos/:owner/:repo/transfer`](/v3/repos/#transfer-a-repository) (:write) +- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write) +- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#disable-vulnerability-alerts) (:write) +- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write) {% endif %} -- [`PATCH /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#accept-a-repository-invitation) (:write) -- [`DELETE /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#decline-a-repository-invitation) (:write) +- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write) +- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write) _Branches_ -- [`GET /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#get-branch-protection) (:read) -- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#update-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#delete-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#get-admin-branch-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#set-admin-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#delete-admin-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#get-pull-request-review-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#update-pull-request-review-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#delete-pull-request-review-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#get-commit-signature-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#create-commit-signature-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#delete-commit-signature-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#get-status-checks-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#update-status-check-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#remove-status-check-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#get-all-status-check-contexts) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#add-status-check-contexts) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#set-status-check-contexts) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#remove-status-check-contexts) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#get-access-restrictions) (:read) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#delete-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#add-team-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#set-team-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#remove-team-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#add-user-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#set-user-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read) +- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Mitarbeiter_ -- [`PUT /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#add-a-repository-collaborator) (:write) -- [`DELETE /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#remove-a-repository-collaborator) (:write) +- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) +- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) _Invitations_ -- [`GET /repos/:owner/:repo/invitations`](/v3/repos/invitations/#list-repository-invitations) (:read) -- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#update-a-repository-invitation) (:write) -- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#delete-a-repository-invitation) (:write) +- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) +- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) +- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) _Keys_ -- [`GET /repos/:owner/:repo/keys`](/v3/repos/keys/#list-deploy-keys) (:read) -- [`POST /repos/:owner/:repo/keys`](/v3/repos/keys/#create-a-deploy-key) (:write) -- [`GET /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#get-a-deploy-key) (:read) -- [`DELETE /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#delete-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) +- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) +- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) _Teams_ -- [`GET /repos/:owner/:repo/teams`](/v3/repos/#list-repository-teams) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:write) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) +- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) {% if currentVersion == "free-pro-team@latest" %} _Traffic_ -- [`GET /repos/:owner/:repo/traffic/clones`](/v3/repos/traffic/#get-repository-clones) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/paths`](/v3/repos/traffic/#get-top-referral-paths) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/v3/repos/traffic/#get-top-referral-sources) (:read) -- [`GET /repos/:owner/:repo/traffic/views`](/v3/repos/traffic/#get-page-views) (:read) +- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) +- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "blocking" -- [`GET /user/blocks`](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) (:read) -- [`GET /user/blocks/:username`](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) -- [`PUT /user/blocks/:username`](/v3/users/blocking/#block-a-user) (:write) -- [`DELETE /user/blocks/:username`](/v3/users/blocking/#unblock-a-user) (:write) +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) +- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) +- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (:write) +- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) {% endif %} ### Permission on "checks" -- [`POST /repos/:owner/:repo/check-runs`](/v3/checks/runs/#create-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#update-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`POST /repos/:owner/:repo/check-suites`](/v3/checks/suites/#create-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/v3/checks/suites/#update-repository-preferences-for-check-suites) (:write) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) +- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (:write) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) ### Permission on "contents" -- [`GET /repos/:owner/:repo/:archive_format/:ref`](/v3/repos/contents/#download-a-repository-archive) (:read) +- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:write) +- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#get-a-repository-secret) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) +- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) +- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/commits`](/v3/repos/commits/#list-commits) (:read) -- [`GET /repos/:owner/:repo/commits/:sha`](/v3/repos/commits/#get-a-commit) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/community/code_of_conduct`](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/compare/:base...:head`](/v3/repos/commits/#compare-two-commits) (:read) -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read) +- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`POST /repos/:owner/:repo/dispatches`](/v3/repos/#create-a-repository-dispatch-event) (:write) +- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:read) -- [`POST /repos/:owner/:repo/merges`](/v3/repos/merging/#merge-a-branch) (:write) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#merge-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/v3/repos/contents/#get-a-repository-readme) (:read) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read) +- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read) _Branches_ -- [`GET /repos/:owner/:repo/branches`](/v3/repos/branches/#list-branches) (:read) -- [`GET /repos/:owner/:repo/branches/:branch`](/v3/repos/branches/#get-a-branch) (:read) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#list-apps-with-access-to-the-protected-branch) (:write) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#add-app-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#set-app-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read) +- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Commit-Kommentare_ -- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#update-a-commit-comment) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#delete-a-commit-comment) (:write) -- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-commit-comment) (:read) -- [`POST /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#create-a-commit-comment) (:read) +- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) +- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) +- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read) _Git_ -- [`POST /repos/:owner/:repo/git/blobs`](/v3/git/blobs/#create-a-blob) (:write) -- [`GET /repos/:owner/:repo/git/blobs/:sha`](/v3/git/blobs/#get-a-blob) (:read) -- [`POST /repos/:owner/:repo/git/commits`](/v3/git/commits/#create-a-commit) (:write) -- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/v3/git/commits/#get-a-commit) (:read) -- [`POST /repos/:owner/:repo/git/refs`](/v3/git/refs/#create-a-reference) (:write) -- [`GET /repos/:owner/:repo/git/ref/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/v3/git/refs/#list-matching-references) (:read) -- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#update-a-reference) (:write) -- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#delete-a-reference) (:write) -- [`POST /repos/:owner/:repo/git/tags`](/v3/git/tags/#create-a-tag-object) (:write) -- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/v3/git/tags/#get-a-tag) (:read) -- [`POST /repos/:owner/:repo/git/trees`](/v3/git/trees/#create-a-tree) (:write) -- [`GET /repos/:owner/:repo/git/trees/:sha`](/v3/git/trees/#get-a-tree) (:read) +- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write) +- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (:read) +- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (:write) +- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (:read) +- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (:write) +- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (:read) +- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (:read) +- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (:write) +- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (:write) +- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (:write) +- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (:read) +- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (:write) +- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) {% if currentVersion == "free-pro-team@latest" %} _importieren_ -- [`GET /repos/:owner/:repo/import`](/v3/migrations/source_imports/#get-an-import-status) (:read) -- [`PUT /repos/:owner/:repo/import`](/v3/migrations/source_imports/#start-an-import) (:write) -- [`PATCH /repos/:owner/:repo/import`](/v3/migrations/source_imports/#update-an-import) (:write) -- [`DELETE /repos/:owner/:repo/import`](/v3/migrations/source_imports/#cancel-an-import) (:write) -- [`GET /repos/:owner/:repo/import/authors`](/v3/migrations/source_imports/#get-commit-authors) (:read) -- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/v3/migrations/source_imports/#map-a-commit-author) (:write) -- [`GET /repos/:owner/:repo/import/large_files`](/v3/migrations/source_imports/#get-large-files) (:read) -- [`PATCH /repos/:owner/:repo/import/lfs`](/v3/migrations/source_imports/#update-git-lfs-preference) (:write) +- [`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) +- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (:write) +- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (:read) +- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (:write) +- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (:read) +- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) {% endif %} _Reactions_ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% endif %} _Veröffentlichungen_ - [`GET /repos/:owner/:repo/releases`](/v3/repos/releases/#list-releases) (:read) @@ -419,195 +419,195 @@ _Veröffentlichungen_ ### Permission on "emails" {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /user/email/visibility`](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) (:write) +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) {% endif %} -- [`GET /user/emails`](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) (:read) -- [`POST /user/emails`](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) (:write) -- [`DELETE /user/emails`](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) (:write) -- [`GET /user/public_emails`](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) (:read) +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (:write) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (:write) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) {% endif %} ### Permission on "followers" -- [`GET /user/followers`](/v3/users/followers/#list-followers-of-a-user) (:read) -- [`GET /user/following`](/v3/users/followers/#list-the-people-a-user-follows) (:read) -- [`GET /user/following/:username`](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) (:read) -- [`PUT /user/following/:username`](/v3/users/followers/#follow-a-user) (:write) -- [`DELETE /user/following/:username`](/v3/users/followers/#unfollow-a-user) (:write) +- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) +- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) +- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (:read) +- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) +- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) ### Permission on "gpg keys" -- [`GET /user/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) (:read) -- [`POST /user/gpg_keys`](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) (:write) -- [`GET /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) (:read) -- [`DELETE /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (:read) +- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) ### Permission on "issues" -Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues. +Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues. -- [`GET /repos/:owner/:repo/issues`](/v3/issues/#list-repository-issues) (:read) -- [`POST /repos/:owner/:repo/issues`](/v3/issues/#create-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#get-an-issue) (:read) -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) +- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (:read) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) _Bearbeiter_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _Ereignisse_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [Get an issue event](/v3/issues/events/#get-an-issue-event) (:read) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [Get an issue event](/rest/reference/issues#get-an-issue-event) (:read) _Kennzeichnungen_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Meilensteine_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reactions_ -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} ### Permission on "keys" _Keys_ -- [`GET /user/keys`](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) (:read) -- [`POST /user/keys`](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) (:write) -- [`GET /user/keys/:key_id`](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) (:read) -- [`DELETE /user/keys/:key_id`](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) +- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) ### Permission on "members" {% if currentVersion == "free-pro-team@latest" %} -- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#list-idp-groups-for-a-team) (:write) +- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#create-or-update-idp-group-connections) (:write) +- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write) {% endif %} -- [`GET /orgs/:org/outside_collaborators`](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) (:read) -- [`PUT /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) (:write) -- [`DELETE /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) (:write) +- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read) +- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write) +- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/team-sync/groups`](/v3/teams/team_sync/#list-idp-groups-for-an-organization) (:write) +- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write) {% endif %} -- [`GET /orgs/:org/team/:team_id`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users`](/v3/scim/#list-scim-provisioned-identities) (:read) +- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /scim/v2/orgs/:org/Users`](/v3/scim/#provision-and-invite-a-scim-user) (:write) +- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#get-scim-provisioning-information-for-a-user) (:read) +- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#set-scim-information-for-a-provisioned-user) (:write) +- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#update-an-attribute-for-a-scim-user) (:write) +- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#delete-a-scim-user-from-an-organization) (:write) +- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} _Invitations_ -- [`GET /orgs/:org/invitations`](/v3/orgs/members/#list-pending-organization-invitations) (:read) -- [`POST /orgs/:org/invitations`](/v3/orgs/members/#create-an-organization-invitation) (:write) -- [`GET /orgs/:org/invitations/:invitation_id/teams`](/v3/orgs/members/#list-organization-invitation-teams) (:read) -- [`GET /teams/:team_id/invitations`](/v3/teams/members/#list-pending-team-invitations) (:read) +- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) +- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) +- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) +- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) {% endif %} _Organization members_ -- [`DELETE /orgs/:org/members/:username`](/v3/orgs/members/#remove-an-organization-member) (:write) -- [`GET /orgs/:org/memberships/:username`](/v3/orgs/members/#get-organization-membership-for-a-user) (:read) -- [`PUT /orgs/:org/memberships/:username`](/v3/orgs/members/#set-organization-membership-for-a-user) (:write) -- [`DELETE /orgs/:org/memberships/:username`](/v3/orgs/members/#remove-organization-membership-for-a-user) (:write) -- [`PUT /orgs/:org/public_members/:username`](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) (:write) -- [`DELETE /orgs/:org/public_members/:username`](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) (:write) -- [`GET /user/memberships/orgs`](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) (:read) -- [`GET /user/memberships/orgs/:org`](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) (:read) -- [`PATCH /user/memberships/orgs/:org`](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) +- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) +- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) +- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (:write) +- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (:write) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (:read) +- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) +- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) _Team members_ -- [`GET /teams/:team_id/members`](/v3/teams/members/#list-team-members) (:read) -- [`GET /teams/:team_id/memberships/:username`](/v3/teams/members/#get-team-membership-for-a-user) (:read) -- [`PUT /teams/:team_id/memberships/:username`](/v3/teams/members/#add-or-update-team-membership-for-a-user) (:write) -- [`DELETE /teams/:team_id/memberships/:username`](/v3/teams/members/#remove-team-membership-for-a-user) (:write) +- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) +- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) +- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) +- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) _Teams_ -- [`GET /orgs/:org/teams`](/v3/teams/#list-teams) (:read) -- [`POST /orgs/:org/teams`](/v3/teams/#create-a-team) (:write) -- [`GET /orgs/:org/teams/:team_slug`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) +- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) +- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -- [`GET /teams/:team_id`](/v3/teams/#get-a-team) (:read) +- [`GET /teams/:team_id`](/rest/reference/teams#get-a-team) (:read) {% endif %} -- [`PATCH /teams/:team_id`](/v3/teams/#update-a-team) (:write) -- [`DELETE /teams/:team_id`](/v3/teams/#delete-a-team) (:write) +- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write) +- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`GET /teams/:team_id/projects`](/v3/teams/#list-team-projects) (:read) -- [`GET /teams/:team_id/projects/:project_id`](/v3/teams/#check-team-permissions-for-a-project) (:read) -- [`PUT /teams/:team_id/projects/:project_id`](/v3/teams/#add-or-update-team-project-permissions) (:read) -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read) +- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read) +- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% endif %} -- [`GET /teams/:team_id/repos`](/v3/teams/#list-team-repositories) (:read) -- [`GET /teams/:team_id/repos/:owner/:repo`](/v3/teams/#check-team-permissions-for-a-repository) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:read) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) -- [`GET /teams/:team_id/teams`](/v3/teams/#list-child-teams) (:read) +- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read) +- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) +- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) ### Permission on "organization administration" -- [`PATCH /orgs/:org`](/v3/orgs/#update-an-organization) (:write) +- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/interaction-limits`](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) (:read) +- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /orgs/:org/interaction-limits`](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) (:write) +- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /orgs/:org/interaction-limits`](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) (:write) +- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) {% endif %} ### Permission on "organization hooks" @@ -620,7 +620,7 @@ _Teams_ - [`POST /orgs/:org/hooks/:hook_id/pings`](/v3/orgs/hooks/#ping-an-organization-webhook) (:write) _Teams_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permission on "organization pre receive hooks" @@ -633,31 +633,31 @@ _Teams_ ### Permission on "organization projects" -- [`POST /orgs/:org/projects`](/v3/projects/#create-an-organization-project) (:write) -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) +- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "organization user blocking" -- [`GET /orgs/:org/blocks`](/v3/orgs/blocking/#list-users-blocked-by-an-organization) (:read) -- [`GET /orgs/:org/blocks/:username`](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) (:read) -- [`PUT /orgs/:org/blocks/:username`](/v3/orgs/blocking/#block-a-user-from-an-organization) (:write) -- [`DELETE /orgs/:org/blocks/:username`](/v3/orgs/blocking/#unblock-a-user-from-an-organization) (:write) +- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) +- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) +- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (:write) +- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) {% endif %} ### Permission on "pages" @@ -675,99 +675,99 @@ _Teams_ Pull requests and issues are closely related.. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests. -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls`](/v3/pulls/#list-pull-requests) (:read) -- [`POST /repos/:owner/:repo/pulls`](/v3/pulls/#create-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#get-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#update-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#list-review-comments-on-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/v3/pulls/#list-commits-on-a-pull-request) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/v3/pulls/#list-pull-requests-files) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#check-if-a-pull-request-has-been-merged) (:read) -- [`GET /repos/:owner/:repo/pulls/comments`](/v3/pulls/comments/#list-review-comments-in-a-repository) (:read) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) (:write) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (:read) +- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (:read) +- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (:read) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) _Bearbeiter_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _Ereignisse_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [`GET /repos/:owner/:repo/issues/events/:event_id`](/v3/issues/events/#get-an-issue-event) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) _Kennzeichnungen_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Meilensteine_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reactions_ -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) (:read) -- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) (:write) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read) +- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} _Requested reviewers_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) _Reviews_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#list-reviews-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#create-a-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#get-a-review-for-a-pull-request) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#update-a-review-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#delete-a-pending-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) ### Permission on "repository hooks" -- [`GET /repos/:owner/:repo/hooks`](/v3/repos/hooks/#list-repository-webhooks) (:read) -- [`POST /repos/:owner/:repo/hooks`](/v3/repos/hooks/#create-a-repository-webhook) (:write) -- [`GET /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#get-a-repository-webhook) (:read) -- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#update-a-repository-webhook) (:write) -- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#delete-a-repository-webhook) (:write) -- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/v3/repos/hooks/#ping-a-repository-webhook) (:read) -- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/v3/repos/hooks/#test-the-push-repository-webhook) (:read) +- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) +- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) +- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read) +- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write) +- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write) +- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read) +- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permission on "repository pre receive hooks" @@ -780,70 +780,70 @@ _Reviews_ ### Permission on "repository projects" -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) -- [`GET /repos/:owner/:repo/projects`](/v3/projects/#list-repository-projects) (:read) -- [`POST /repos/:owner/:repo/projects`](/v3/projects/#create-a-repository-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) +- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) +- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) _Teams_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "secrets" -* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:read) -* [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:read) -* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#get-a-repository-secret) (:read) -* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -* [`GET /orgs/:org/actions/secrets/public-key`](/v3/actions/secrets/#get-an-organization-public-key) (:read) -* [`GET /orgs/:org/actions/secrets`](/v3/actions/secrets/#list-organization-secrets) (:read) -* [`GET /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#get-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-an-organization-secret) (:write) -* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) (:write) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-an-organization-secret) (:write) +* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) +* [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) +* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (:read) +* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (:write) +* [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (:read) +* [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (:read) +* [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (:write) +* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (:write) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "security events" -- [`GET /repos/:owner/:repo/code-scanning/alerts`](/v3/code-scanning/#list-code-scanning-alerts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/v3/code-scanning/#get-a-code-scanning-alert) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "self-hosted runners" -- [`GET /orgs/:org/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) (:write) -- [`GET /orgs/:org/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) (:read) -- [`GET /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) (:write) -- [`DELETE /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) +- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) +- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) {% endif %} ### Permission on "single file" -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -- [`PUT /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#create-or-update-file-contents) (:write) -- [`DELETE /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#delete-a-file) (:write) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) +- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) ### Permission on "starring" @@ -853,23 +853,23 @@ _Teams_ ### Permission on "statuses" -- [`GET /repos/:owner/:repo/commits/:ref/status`](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/v3/repos/statuses/#list-commit-statuses-for-a-reference) (:read) -- [`POST /repos/:owner/:repo/statuses/:sha`](/v3/repos/statuses/#create-a-commit-status) (:write) +- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) +- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) ### Permission on "team discussions" -- [`GET /teams/:team_id/discussions`](/v3/teams/discussions/#list-discussions) (:read) -- [`POST /teams/:team_id/discussions`](/v3/teams/discussions/#create-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#get-a-discussion) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#update-a-discussion) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#delete-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#list-discussion-comments) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#create-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#get-a-discussion-comment) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#update-a-discussion-comment) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#delete-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion-comment) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion) (:write) +- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) +- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/de-DE/content/rest/reference/pulls.md b/translations/de-DE/content/rest/reference/pulls.md index f1d7a568bc..5f4c70fea2 100644 --- a/translations/de-DE/content/rest/reference/pulls.md +++ b/translations/de-DE/content/rest/reference/pulls.md @@ -10,7 +10,7 @@ versions: 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](/v3/issues). +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 @@ -33,16 +33,16 @@ If a diff is corrupt, contact {% data variables.contact.contact_support %}. Incl Pull Requests have these possible link relations: -| Name | Beschreibung | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -| `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](/v3/issues/). | -| `kommentare` | The API location of this Pull Request's [Issue comments](/v3/issues/comments/). | -| `review_comments` | The API location of this Pull Request's [Review comments](/v3/pulls/comments/). | -| `review_comment` | The [URL template](/v3/#hypermedia) to construct the API location for a [Review comment](/v3/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 (Statusangaben)` | The API location of this Pull Request's [commit statuses](/v3/repos/statuses/), which are the statuses of its `head` branch. | +| Name | Beschreibung | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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). | +| `kommentare` | 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 (Statusangaben)` | The API location of this Pull Request's [commit statuses](/rest/reference/repos#statuses), which are the statuses of its `head` branch. | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/de-DE/content/rest/reference/rate-limit.md b/translations/de-DE/content/rest/reference/rate-limit.md index b81dff0260..7c33a37028 100644 --- a/translations/de-DE/content/rest/reference/rate-limit.md +++ b/translations/de-DE/content/rest/reference/rate-limit.md @@ -13,18 +13,18 @@ The REST API overview documentation describes the [rate limit rules](/rest/overv ### Understanding your rate limit status -The Search API has a [custom rate limit](/v3/search/#rate-limit), separate from the rate limit governing the rest of the REST API. The GraphQL API also has a [custom rate limit](/v4/guides/resource-limitations/#rate-limit) that is separate from and calculated differently than rate limits in the REST API. +The Search API has a [custom rate limit](/rest/reference/search#rate-limit), separate from the rate limit governing the rest of the REST API. The GraphQL API also has a [custom rate limit](/graphql/overview/resource-limitations#rate-limit) that is separate from and calculated differently than rate limits in the REST API. For these reasons, the Rate Limit API response categorizes your rate limit. Under `resources`, you'll see four objects: * The `core` object provides your rate limit status for all non-search-related resources in the REST API. -* The `search` object provides your rate limit status for the [Search API](/v3/search/). +* The `search` object provides your rate limit status for the [Search API](/rest/reference/search). -* The `graphql` object provides your rate limit status for the [GraphQL API](/v4/). +* The `graphql` object provides your rate limit status for the [GraphQL API](/graphql). * The `integration_manifest` object provides your rate limit status for the [GitHub App Manifest code conversion](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration) endpoint. -For more information on the headers and values in the rate limit response, see "[Rate limiting](/v3/#rate-limiting)." +For more information on the headers and values in the rate limit response, see "[Rate limiting](/rest#rate-limiting)." {% include rest_operations_at_current_path %} diff --git a/translations/de-DE/content/rest/reference/repos.md b/translations/de-DE/content/rest/reference/repos.md index f70a2e88ab..f87011fdb5 100644 --- a/translations/de-DE/content/rest/reference/repos.md +++ b/translations/de-DE/content/rest/reference/repos.md @@ -29,7 +29,7 @@ versions: ### Custom media types for commit comments -These are the supported media types for commit comments. You can read more about the use of media types in the API [here](/v3/media/). +These are the supported media types for commit comments. You can read more about the use of media types in the API [here](/rest/overview/media-types). application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json @@ -65,7 +65,7 @@ These API endpoints let you create, modify, and delete Base64 encoded content in ### Custom media types for repository contents -[READMEs](/v3/repos/contents/#get-a-repository-readme), [files](/v3/repos/contents/#get-repository-content), and [symlinks](/v3/repos/contents/#get-repository-content) support the following custom media types: +[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 @@ -74,13 +74,13 @@ 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](/v3/repos/contents/#get-repository-content) support the following custom media type: +[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](/v3/media/). +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 %} diff --git a/translations/de-DE/content/rest/reference/scim.md b/translations/de-DE/content/rest/reference/scim.md index ca6a0b7ce6..8fccd14a37 100644 --- a/translations/de-DE/content/rest/reference/scim.md +++ b/translations/de-DE/content/rest/reference/scim.md @@ -12,7 +12,7 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/v3/auth/#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim).“ +**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim).“ {% endnote %} diff --git a/translations/de-DE/content/rest/reference/search.md b/translations/de-DE/content/rest/reference/search.md index 4425c5879d..d506d2f2a1 100644 --- a/translations/de-DE/content/rest/reference/search.md +++ b/translations/de-DE/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**. -You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/v3/search/#constructing-a-search-query)." +You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." ### Ranking search results @@ -18,7 +18,7 @@ Unless another sort option is provided as a query parameter, results are sorted ### Rate limit -The Search API has a custom rate limit. For requests using [Basic Authentication](/v3/#authentication), [OAuth](/v3/#authentication), or [client ID and secret](/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute. +The Search API has a custom rate limit. For requests using [Basic Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute. {% data reusables.enterprise.rate_limit %} diff --git a/translations/de-DE/content/rest/reference/teams.md b/translations/de-DE/content/rest/reference/teams.md index de4aee7e9c..50d5fb8fec 100644 --- a/translations/de-DE/content/rest/reference/teams.md +++ b/translations/de-DE/content/rest/reference/teams.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -This API is only available to authenticated members of the team's [organization](/v3/orgs). OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} generates the team's `slug` from the team `name`. +This API is only available to authenticated members of the team's [organization](/rest/reference/orgs). OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} generates the team's `slug` from the team `name`. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -16,7 +16,7 @@ This API is only available to authenticated members of the team's [organization] ## Discussions -The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/v3/orgs) can create and read public discussion posts. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. This API is only available to authenticated members of the team's organization. +The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -24,7 +24,7 @@ The team discussions API allows you to get, create, edit, and delete discussion ## Discussion comments -The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/v3/teams/discussions) post. Any member of the team's [organization](/v3/orgs) can create and read comments on a public discussion. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. This API is only available to authenticated members of the team's organization. +The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -58,4 +58,4 @@ You can manage GitHub team members through your IdP with team synchronization. T {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/de-DE/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/de-DE/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 10f9989a12..3d4deaabeb 100644 --- a/translations/de-DE/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/de-DE/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.' reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/de-DE/data/graphql/graphql_upcoming_changes.public.yml b/translations/de-DE/data/graphql/graphql_upcoming_changes.public.yml index f12ecd0331..2b5e3ec561 100644 --- a/translations/de-DE/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/de-DE/data/graphql/graphql_upcoming_changes.public.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.' reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/de-DE/data/reusables/apps/app-ruby-guides.md b/translations/de-DE/data/reusables/apps/app-ruby-guides.md index fe649b0de5..19a860b9e9 100644 --- a/translations/de-DE/data/reusables/apps/app-ruby-guides.md +++ b/translations/de-DE/data/reusables/apps/app-ruby-guides.md @@ -1,5 +1,5 @@ {% note %} -**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/v3/libraries/). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. +**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/rest/overview/libraries). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. {% endnote %} diff --git a/translations/de-DE/data/reusables/apps/checks-availability.md b/translations/de-DE/data/reusables/apps/checks-availability.md index 7360c3112d..441b6cc35b 100644 --- a/translations/de-DE/data/reusables/apps/checks-availability.md +++ b/translations/de-DE/data/reusables/apps/checks-availability.md @@ -1 +1 @@ -Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/v3/repos/statuses/). +Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/rest/reference/repos#statuses). diff --git a/translations/de-DE/data/reusables/apps/deletes_ssh_keys.md b/translations/de-DE/data/reusables/apps/deletes_ssh_keys.md index 6b5e91b011..c1a3e41f10 100644 --- a/translations/de-DE/data/reusables/apps/deletes_ssh_keys.md +++ b/translations/de-DE/data/reusables/apps/deletes_ssh_keys.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/v3/guides/managing-deploy-keys/#deploy-keys). +**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys). {% endwarning %} diff --git a/translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md index 07fd7f5941..26ea19355f 100644 --- a/translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/v3/auth/#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). +**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} diff --git a/translations/de-DE/data/reusables/apps/deprecating_github_services_ghe.md b/translations/de-DE/data/reusables/apps/deprecating_github_services_ghe.md index 72e5d399fb..b44e17370a 100644 --- a/translations/de-DE/data/reusables/apps/deprecating_github_services_ghe.md +++ b/translations/de-DE/data/reusables/apps/deprecating_github_services_ghe.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} {% note %} -**Note:** GitHub Enterprise release 2.17 and higher no longer allows admins to install new GitHub Services, and existing services will stop working in GitHub Enterprise release 2.20 and higher. You can use the [Replacing GitHub Services guide](/v3/guides/replacing-github-services) to help you update your services to webhooks. +**Note:** GitHub Enterprise release 2.17 and higher no longer allows admins to install new GitHub Services, and existing services will stop working in GitHub Enterprise release 2.20 and higher. You can use the [Replacing GitHub Services guide](/developers/overview/replacing-github-services) to help you update your services to webhooks. {% endnote %} {% endif %} diff --git a/translations/de-DE/data/reusables/code-scanning/example-configuration-files.md b/translations/de-DE/data/reusables/code-scanning/example-configuration-files.md index 940d94e8d4..f429bb12cf 100644 --- a/translations/de-DE/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/de-DE/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), and to exclude the _node_modules_ directory (also relative to the root), as well as any file whose name ends in _.test.js_. +The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. ``` yaml name: "My {% data variables.product.prodname_codeql %} config" @@ -24,9 +24,9 @@ queries: - name: Use a query suite file (run queries from a query suite in this repo) uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls -paths-ignore: - - node_modules - - '**/*.test.js' paths: - src +paths-ignore: + - src/node_modules + - '**/*.test.js' ``` diff --git a/translations/de-DE/data/reusables/github-actions/matrix-variable-example.md b/translations/de-DE/data/reusables/github-actions/matrix-variable-example.md new file mode 100644 index 0000000000..ce6e9d6d24 --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/matrix-variable-example.md @@ -0,0 +1,26 @@ +In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: + +{% raw %} +```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - node-version: 10.x + site: "prod" + datacenter: "site-a" + - node-version: 12.x + site: "dev" + datacenter: "site-b" + steps: + - name: Echo site details + env: + SITE: ${{ matrix.site }} + DATACENTER: ${{ matrix.datacenter }} + run: echo $SITE $DATACENTER +``` +{% endraw %} diff --git a/translations/de-DE/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/de-DE/data/reusables/github-actions/permissions-statement-secrets-api.md index 0e62bb6498..53142b325e 100644 --- a/translations/de-DE/data/reusables/github-actions/permissions-statement-secrets-api.md +++ b/translations/de-DE/data/reusables/github-actions/permissions-statement-secrets-api.md @@ -1 +1 @@ -To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/v3/actions/secrets/)." +To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)." diff --git a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 9ac93498fa..b645d2a5ac 100644 --- a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,12 +1,12 @@ -1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. - ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Repository-Berechtigungen verwalten](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. {% warning %} - **Warning** + **Warnung** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." + + Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. {% endwarning %} - diff --git a/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 844ef0a42c..28ccd39cce 100644 --- a/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -Nachdem Du die Teamsynchronisierung aktiviert hast, können Team-Betreuer und Organisationsinhaber ein Team auf {% data variables.product.prodname_dotcom %} oder mit dem API zu einer IdP-Gruppe verbinden. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/v3/teams/team_sync/)." +Nachdem Du die Teamsynchronisierung aktiviert hast, können Team-Betreuer und Organisationsinhaber ein Team auf {% data variables.product.prodname_dotcom %} oder mit dem API zu einer IdP-Gruppe verbinden. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md b/translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md index db14856890..053533f692 100644 --- a/translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md @@ -1,10 +1,10 @@ -| Name | Typ | Beschreibung | -| ------------ | --------- | -------------------------------------------------------------------- | -| `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `string` | The REST API URL for fetching the event. | -| `actor` | `Objekt` | The person who generated the event. | -| `event` | `string` | Identifies the actual type of event that occurred. | -| `commit_id` | `string` | The SHA of the commit that referenced this issue. | -| `commit_url` | `string` | The GitHub REST API link to the commit that referenced this issue. | -| `created_at` | `string` | The timestamp indicating when the event occurred. | +| Name | Typ | Beschreibung | +| ------------ | --------- | ------------------------------------------------------------------------- | +| `id` | `integer` | The unique identifier of the event. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `string` | The REST API URL for fetching the event. | +| `actor` | `Objekt` | The person who generated the event. | +| `event` | `string` | Identifies the actual type of event that occurred. | +| `commit_id` | `string` | The SHA of the commit that referenced this issue. | +| `commit_url` | `string` | The GitHub REST API link to the commit that referenced this issue. | +| `created_at` | `string` | The timestamp indicating when the event occurred. | diff --git a/translations/de-DE/data/reusables/pre-release-program/corsair-preview.md b/translations/de-DE/data/reusables/pre-release-program/corsair-preview.md index d5131c62d3..7724c1caaf 100644 --- a/translations/de-DE/data/reusables/pre-release-program/corsair-preview.md +++ b/translations/de-DE/data/reusables/pre-release-program/corsair-preview.md @@ -1,6 +1,6 @@ {% note %} -**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.corsair-preview+json diff --git a/translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md index 6bf0fb2ed4..7bed2bb577 100644 --- a/translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md +++ b/translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Note:** Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)." For more information, see "[Expiring user-to-server access tokens for GitHub Apps](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)." diff --git a/translations/de-DE/data/reusables/pre-release-program/fury-pre-release.md b/translations/de-DE/data/reusables/pre-release-program/fury-pre-release.md index 25b74a97ea..adf434c97e 100644 --- a/translations/de-DE/data/reusables/pre-release-program/fury-pre-release.md +++ b/translations/de-DE/data/reusables/pre-release-program/fury-pre-release.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} {% note %} -**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.fury-preview+json diff --git a/translations/de-DE/data/reusables/pre-release-program/machine-man-preview.md b/translations/de-DE/data/reusables/pre-release-program/machine-man-preview.md index d18399b663..82549b4331 100644 --- a/translations/de-DE/data/reusables/pre-release-program/machine-man-preview.md +++ b/translations/de-DE/data/reusables/pre-release-program/machine-man-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** To access the API with your GitHub App, you must provide a custom [media type](/v3/media) in the `Accept` Header for your requests. +**Note:** To access the API with your GitHub App, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` Header for your requests. `application/vnd.github.machine-man-preview+json` diff --git a/translations/de-DE/data/reusables/pre-release-program/sailor-v-preview.md b/translations/de-DE/data/reusables/pre-release-program/sailor-v-preview.md index fcf2e98e68..ac0d210355 100644 --- a/translations/de-DE/data/reusables/pre-release-program/sailor-v-preview.md +++ b/translations/de-DE/data/reusables/pre-release-program/sailor-v-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.sailor-v-preview+json diff --git a/translations/de-DE/data/reusables/pre-release-program/starfox-preview.md b/translations/de-DE/data/reusables/pre-release-program/starfox-preview.md index 5de305adb6..138455a9eb 100644 --- a/translations/de-DE/data/reusables/pre-release-program/starfox-preview.md +++ b/translations/de-DE/data/reusables/pre-release-program/starfox-preview.md @@ -2,7 +2,7 @@ **Note:** Project card details are now shown in REST API responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events). -To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/v3/media) in the `Accept` header: +To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.starfox-preview+json diff --git a/translations/de-DE/data/reusables/repositories/deploy-keys.md b/translations/de-DE/data/reusables/repositories/deploy-keys.md index ae039b459e..3f3948dc84 100644 --- a/translations/de-DE/data/reusables/repositories/deploy-keys.md +++ b/translations/de-DE/data/reusables/repositories/deploy-keys.md @@ -1 +1 @@ -You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/v3/guides/delivering-deployments/)." +You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)." diff --git a/translations/de-DE/data/reusables/webhooks/check_run_properties.md b/translations/de-DE/data/reusables/webhooks/check_run_properties.md index bc5761715e..40526716e4 100644 --- a/translations/de-DE/data/reusables/webhooks/check_run_properties.md +++ b/translations/de-DE/data/reusables/webhooks/check_run_properties.md @@ -1,7 +1,7 @@ | Schlüssel | Typ | Beschreibung | | --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | The action performed. Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/v3/checks/runs/#check-runs-and-requested-actions)."
| -| `check_run` | `Objekt` | The [check_run](/v3/checks/runs/#get-a-check-run). | +| `action` | `string` | The action performed. Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `check_run` | `Objekt` | The [check_run](/rest/reference/checks#get-a-check-run). | | `check_run[status]` | `string` | The current status of the check run. Can be `queued`, `in_progress`, or `completed`. | | `check_run[conclusion]` | `string` | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. | | `check_run[name]` | `string` | The name of the check run. | diff --git a/translations/de-DE/data/reusables/webhooks/check_run_short_desc.md b/translations/de-DE/data/reusables/webhooks/check_run_short_desc.md index 19fd0846b8..15cbbb7936 100644 --- a/translations/de-DE/data/reusables/webhooks/check_run_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/check_run_short_desc.md @@ -1 +1 @@ -Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/v3/checks/runs/)" REST API. +Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/rest/reference/checks#runs)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/check_suite_properties.md b/translations/de-DE/data/reusables/webhooks/check_suite_properties.md index d9359724f6..0aa800e9eb 100644 --- a/translations/de-DE/data/reusables/webhooks/check_suite_properties.md +++ b/translations/de-DE/data/reusables/webhooks/check_suite_properties.md @@ -1,7 +1,7 @@ | Schlüssel | Typ | Beschreibung | | ---------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | The action performed. Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| -| `check_suite` | `Objekt` | The [check_suite](/v3/checks/suites/). | +| `action` | `string` | The action performed. Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| +| `check_suite` | `Objekt` | The [check_suite](/rest/reference/checks#suites). | | `check_suite[head_branch]` | `string` | The head branch name the changes are on. | | `check_suite[head_sha]` | `string` | The SHA of the most recent commit for this check suite. | | `check_suite[status]` | `string` | The summary status for all check runs that are part of the check suite. Can be `requested`, `in_progress`, or `completed`. | diff --git a/translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md b/translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md index 00c4c00937..94ed6dc937 100644 --- a/translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md @@ -1 +1 @@ -Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/v3/checks/suites/)" REST API. +Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/rest/reference/checks#suites)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/commit_comment_properties.md b/translations/de-DE/data/reusables/webhooks/commit_comment_properties.md index 0081aa6645..4b37d7acdd 100644 --- a/translations/de-DE/data/reusables/webhooks/commit_comment_properties.md +++ b/translations/de-DE/data/reusables/webhooks/commit_comment_properties.md @@ -1,4 +1,4 @@ -| Schlüssel | Typ | Beschreibung | -| -------------- | -------- | ------------------------------------------------------------------------ | -| `action` | `string` | The action performed. Can be `created`. | -| `kommentieren` | `Objekt` | The [commit comment](/v3/repos/comments/#get-a-commit-comment) resource. | +| Schlüssel | Typ | Beschreibung | +| -------------- | -------- | -------------------------------------------------------------------------- | +| `action` | `string` | The action performed. Can be `created`. | +| `kommentieren` | `Objekt` | The [commit comment](/rest/reference/repos#get-a-commit-comment) resource. | diff --git a/translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md b/translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md index 20e258a1ea..7329b1ed61 100644 --- a/translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md @@ -1 +1 @@ -A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/v3/repos/comments/)" REST API. +A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/rest/reference/repos#comments)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/create_properties.md b/translations/de-DE/data/reusables/webhooks/create_properties.md index 089d431944..8944395120 100644 --- a/translations/de-DE/data/reusables/webhooks/create_properties.md +++ b/translations/de-DE/data/reusables/webhooks/create_properties.md @@ -1,6 +1,6 @@ | Schlüssel | Typ | Beschreibung | | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | +| `ref` | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | | `ref_type` | `string` | The type of Git ref object created in the repository. Can be either `branch` or `tag`. | | `master_branch` | `string` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" %}`main`{% else %}`master`{% endif %}). | | `Beschreibung` | `string` | The repository's current description. | diff --git a/translations/de-DE/data/reusables/webhooks/create_short_desc.md b/translations/de-DE/data/reusables/webhooks/create_short_desc.md index a43ab39943..5cf906a338 100644 --- a/translations/de-DE/data/reusables/webhooks/create_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/create_short_desc.md @@ -1 +1 @@ -A Git branch or tag is created. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is created. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/delete_properties.md b/translations/de-DE/data/reusables/webhooks/delete_properties.md index 6bc323fd1e..e238c860fb 100644 --- a/translations/de-DE/data/reusables/webhooks/delete_properties.md +++ b/translations/de-DE/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ | Schlüssel | Typ | Beschreibung | | ---------- | -------- | ------------------------------------------------------------------------------ | -| `ref` | `string` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | +| `ref` | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | | `ref_type` | `string` | The type of Git ref oject deleted in the repository. Can be `branch` or `tag`. | diff --git a/translations/de-DE/data/reusables/webhooks/delete_short_desc.md b/translations/de-DE/data/reusables/webhooks/delete_short_desc.md index 7557d8e4ed..726e68df82 100644 --- a/translations/de-DE/data/reusables/webhooks/delete_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/delete_short_desc.md @@ -1 +1 @@ -A Git branch or tag is deleted. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is deleted. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/deploy_key_properties.md b/translations/de-DE/data/reusables/webhooks/deploy_key_properties.md index 0fa70fac71..86d1f816da 100644 --- a/translations/de-DE/data/reusables/webhooks/deploy_key_properties.md +++ b/translations/de-DE/data/reusables/webhooks/deploy_key_properties.md @@ -1,4 +1,4 @@ -| Schlüssel | Typ | Beschreibung | -| ----------- | -------- | -------------------------------------------------------------- | -| `action` | `string` | The action performed. Can be either `created` or `deleted`. | -| `Schlüssel` | `Objekt` | The [`deploy key`](/v3/repos/keys/#get-a-deploy-key) resource. | +| Schlüssel | Typ | Beschreibung | +| ----------- | -------- | -------------------------------------------------------------------- | +| `action` | `string` | The action performed. Can be either `created` or `deleted`. | +| `Schlüssel` | `Objekt` | The [`deploy key`](/rest/reference/repos#get-a-deploy-key) resource. | diff --git a/translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md b/translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md index c83fe68579..1d4565e788 100644 --- a/translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md @@ -1 +1 @@ -A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/v3/repos/keys/)" REST API. +A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/rest/reference/repos#keys)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/fork_properties.md b/translations/de-DE/data/reusables/webhooks/fork_properties.md index 2a6514c1aa..209a4ab22e 100644 --- a/translations/de-DE/data/reusables/webhooks/fork_properties.md +++ b/translations/de-DE/data/reusables/webhooks/fork_properties.md @@ -1,3 +1,3 @@ -| Schlüssel | Typ | Beschreibung | -| --------- | -------- | ----------------------------------------------------------------- | -| `forkee` | `Objekt` | The created [`repository`](/v3/repos/#get-a-repository) resource. | +| Schlüssel | Typ | Beschreibung | +| --------- | -------- | ---------------------------------------------------------------------------- | +| `forkee` | `Objekt` | The created [`repository`](/rest/reference/repos#get-a-repository) resource. | diff --git a/translations/de-DE/data/reusables/webhooks/fork_short_desc.md b/translations/de-DE/data/reusables/webhooks/fork_short_desc.md index 60f88625b0..23b9eff136 100644 --- a/translations/de-DE/data/reusables/webhooks/fork_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/fork_short_desc.md @@ -1 +1 @@ -A user forks a repository. For more information, see the "[forks](/v3/repos/forks/)" REST API. +A user forks a repository. For more information, see the "[forks](/rest/reference/repos#forks)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md index 63166ba6e2..f1debb10f2 100644 --- a/translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md @@ -1 +1 @@ -Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/installation_short_desc.md b/translations/de-DE/data/reusables/webhooks/installation_short_desc.md index 4abc1de643..21cffb5f50 100644 --- a/translations/de-DE/data/reusables/webhooks/installation_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/installation_short_desc.md @@ -1 +1 @@ -Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/issue_comment_properties.md b/translations/de-DE/data/reusables/webhooks/issue_comment_properties.md index b983deb16f..5a93e1a350 100644 --- a/translations/de-DE/data/reusables/webhooks/issue_comment_properties.md +++ b/translations/de-DE/data/reusables/webhooks/issue_comment_properties.md @@ -1 +1 @@ -`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | The previous version of the body if the action was `edited`. `issue`|`object` | The [issue](/v3/issues/) the comment belongs to. `comment`|`object` | The [comment](/v3/issues/comments/) itself. +`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | The previous version of the body if the action was `edited`. `issue`|`object` | The [issue](/rest/reference/issues) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/issues#comments) itself. diff --git a/translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md b/translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md index cc07764d19..dd67c3de2d 100644 --- a/translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md @@ -1 +1 @@ -Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/v3/issues/comments/)" REST API. +Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/rest/reference/issues#comments)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/issue_properties.md b/translations/de-DE/data/reusables/webhooks/issue_properties.md index c146faa968..bff204fc72 100644 --- a/translations/de-DE/data/reusables/webhooks/issue_properties.md +++ b/translations/de-DE/data/reusables/webhooks/issue_properties.md @@ -1 +1 @@ -`issue`|`object` | The [issue](/v3/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. +`issue`|`object` | The [issue](/rest/reference/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. diff --git a/translations/de-DE/data/reusables/webhooks/issues_short_desc.md b/translations/de-DE/data/reusables/webhooks/issues_short_desc.md index 7dadec073b..3edc02859f 100644 --- a/translations/de-DE/data/reusables/webhooks/issues_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/issues_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/v3/issues/comments/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/rest/reference/issues#comments)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/label_short_desc.md b/translations/de-DE/data/reusables/webhooks/label_short_desc.md index c5f7178d8a..a634b7faa7 100644 --- a/translations/de-DE/data/reusables/webhooks/label_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/label_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/v3/issues/labels/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/rest/reference/issues#labels)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/member_properties.md b/translations/de-DE/data/reusables/webhooks/member_properties.md index d9e1757f40..add035dc19 100644 --- a/translations/de-DE/data/reusables/webhooks/member_properties.md +++ b/translations/de-DE/data/reusables/webhooks/member_properties.md @@ -1 +1 @@ -`member`|`object` | The [user](/v3/users/) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. +`member`|`object` | The [user](/rest/reference/users) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. diff --git a/translations/de-DE/data/reusables/webhooks/member_short_desc.md b/translations/de-DE/data/reusables/webhooks/member_short_desc.md index 2e82896773..b664392fdf 100644 --- a/translations/de-DE/data/reusables/webhooks/member_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/member_short_desc.md @@ -1 +1 @@ -Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/v3/repos/collaborators/)" REST API. +Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/rest/reference/repos#collaborators)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/membership_properties.md b/translations/de-DE/data/reusables/webhooks/membership_properties.md index 59c0a79b4e..fb9fec8ac3 100644 --- a/translations/de-DE/data/reusables/webhooks/membership_properties.md +++ b/translations/de-DE/data/reusables/webhooks/membership_properties.md @@ -2,5 +2,5 @@ | ---------- | -------- | ---------------------------------------------------------------- | | `action` | `string` | die Aktion, die durchgeführt wurde. Can be `added` or `removed`. | | `Umfang` | `string` | The scope of the membership. Currently, can only be `team`. | -| `Mitglied` | `Objekt` | The [user](/v3/users/) that was added or removed. | -| `Team` | `Objekt` | The [team](/v3/teams/) for the membership. | +| `Mitglied` | `Objekt` | The [user](/rest/reference/users) that was added or removed. | +| `Team` | `Objekt` | The [team](/rest/reference/teams) for the membership. | diff --git a/translations/de-DE/data/reusables/webhooks/membership_short_desc.md b/translations/de-DE/data/reusables/webhooks/membership_short_desc.md index e557eea902..f7867d25a9 100644 --- a/translations/de-DE/data/reusables/webhooks/membership_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/membership_short_desc.md @@ -1 +1 @@ -Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/v3/teams/members/)" REST API. +Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/rest/reference/teams#members)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/milestone_short_desc.md b/translations/de-DE/data/reusables/webhooks/milestone_short_desc.md index 6b6bd073ce..c9edf73236 100644 --- a/translations/de-DE/data/reusables/webhooks/milestone_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/milestone_short_desc.md @@ -1 +1 @@ -Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/v3/issues/milestones/)" REST API. +Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/rest/reference/issues#milestones)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/org_block_short_desc.md b/translations/de-DE/data/reusables/webhooks/org_block_short_desc.md index 7c3896f63c..f75660fcdb 100644 --- a/translations/de-DE/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. +Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/org_desc.md b/translations/de-DE/data/reusables/webhooks/org_desc.md index 8b344e764c..90d218b876 100644 --- a/translations/de-DE/data/reusables/webhooks/org_desc.md +++ b/translations/de-DE/data/reusables/webhooks/org_desc.md @@ -1 +1 @@ -`organization` | `object` | Webhook payloads contain the [`organization`](/v3/orgs/#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. +`organization` | `object` | Webhook payloads contain the [`organization`](/rest/reference/orgs#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. diff --git a/translations/de-DE/data/reusables/webhooks/organization_short_desc.md b/translations/de-DE/data/reusables/webhooks/organization_short_desc.md index 895b584aaf..0b539ee364 100644 --- a/translations/de-DE/data/reusables/webhooks/organization_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/organization_short_desc.md @@ -1 +1 @@ -Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/v3/orgs/)" REST API. +Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/rest/reference/orgs)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/project_card_properties.md b/translations/de-DE/data/reusables/webhooks/project_card_properties.md index 0b2049c391..5a7a55de3a 100644 --- a/translations/de-DE/data/reusables/webhooks/project_card_properties.md +++ b/translations/de-DE/data/reusables/webhooks/project_card_properties.md @@ -4,4 +4,4 @@ | `changes` | `Objekt` | The changes to the project card if the action was `edited` or `converted`. | | `changes[note][from]` | `string` | The previous version of the note if the action was `edited` or `converted`. | | `after_id` | `integer` | The id of the card that this card now follows if the action was "moved". Will be `null` if it is the first card in a column. | -| `project_card` | `Objekt` | The [project card](/v3/projects/cards) itself. | +| `project_card` | `Objekt` | The [project card](/rest/reference/projects#cards) itself. | diff --git a/translations/de-DE/data/reusables/webhooks/project_card_short_desc.md b/translations/de-DE/data/reusables/webhooks/project_card_short_desc.md index bbea9ea6c4..6fe2904d9e 100644 --- a/translations/de-DE/data/reusables/webhooks/project_card_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/project_card_short_desc.md @@ -1 +1 @@ -Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/v3/projects/cards)" REST API. +Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/project_column_properties.md b/translations/de-DE/data/reusables/webhooks/project_column_properties.md index a10af792eb..92719b2f8a 100644 --- a/translations/de-DE/data/reusables/webhooks/project_column_properties.md +++ b/translations/de-DE/data/reusables/webhooks/project_column_properties.md @@ -4,4 +4,4 @@ | `changes` | `Objekt` | The changes to the project column if the action was `edited`. | | `changes[name][from]` | `string` | The previous version of the name if the action was `edited`. | | `after_id` | `integer` | The id of the column that this column now follows if the action was "moved". Will be `null` if it is the first column in a project. | -| `project_column` | `Objekt` | The [project column](/v3/projects/columns) itself. | +| `project_column` | `Objekt` | The [project column](/rest/reference/projects#columns) itself. | diff --git a/translations/de-DE/data/reusables/webhooks/project_column_short_desc.md b/translations/de-DE/data/reusables/webhooks/project_column_short_desc.md index 19ac3f6412..35d38e4101 100644 --- a/translations/de-DE/data/reusables/webhooks/project_column_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/project_column_short_desc.md @@ -1 +1 @@ -Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/v3/projects/columns)" REST API. +Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/project_properties.md b/translations/de-DE/data/reusables/webhooks/project_properties.md index fe1ff8fa6d..68ac26830a 100644 --- a/translations/de-DE/data/reusables/webhooks/project_properties.md +++ b/translations/de-DE/data/reusables/webhooks/project_properties.md @@ -4,4 +4,4 @@ | `changes` | `Objekt` | The changes to the project if the action was `edited`. | | `changes[name][from]` | `string` | The previous version of the name if the action was `edited`. | | `changes[body][from]` | `string` | The previous version of the body if the action was `edited`. | -| `project (Projekt)` | `Objekt` | The [project](/v3/projects/) itself. | +| `project (Projekt)` | `Objekt` | The [project](/rest/reference/projects) itself. | diff --git a/translations/de-DE/data/reusables/webhooks/project_short_desc.md b/translations/de-DE/data/reusables/webhooks/project_short_desc.md index 6f18da5d69..2ae5d8be21 100644 --- a/translations/de-DE/data/reusables/webhooks/project_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/project_short_desc.md @@ -1 +1 @@ -Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/v3/projects)" REST API. +Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_properties.md index 21544ccd9e..948f78e0b0 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_properties.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_properties.md @@ -1 +1 @@ -`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls) itself. +`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) itself. diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md index a38df37d8c..1b854809c7 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md @@ -1 +1 @@ -`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls/) the comment belongs to. `comment`|`object` | The [comment](/v3/pulls/comments) itself. +`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/pulls#comments) itself. diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md index 7b05ee9a9a..e002a3be49 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md @@ -1 +1 @@ -Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/v3/pulls/comments/)" REST API. +Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/rest/reference/pulls#comments)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md index 0d570bafdd..fa43eaa9b1 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ | Schlüssel | Typ | Beschreibung | | --------------------- | -------- | --------------------------------------------------------------------------- | | `action` | `string` | die Aktion, die durchgeführt wurde. Can be one of:
  • `submitted` - A pull request review is submitted into a non-pending state.
  • `edited` - The body of a review has been edited.
  • `dismissed` - A review has been dismissed.
| -| `pull_request` | `Objekt` | The [pull request](/v3/pulls/) the review pertains to. | +| `pull_request` | `Objekt` | The [pull request](/rest/reference/pulls) the review pertains to. | | `Review` | `Objekt` | The review that was affected. | | `changes[body][from]` | `string` | The previous version of the body if the action was `edited`. | diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md index 07b263364d..3329d4b62e 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md @@ -1 +1 @@ -Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/v3/pulls/reviews/)" REST API. +Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/rest/reference/pulls#reviews)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md b/translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md index ea9e435d03..45bc1b5789 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md @@ -1 +1 @@ -Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/v3/pulls/)" REST API. +Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/rest/reference/pulls)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/release_short_desc.md b/translations/de-DE/data/reusables/webhooks/release_short_desc.md index e3a9a3bb3a..a8d506f409 100644 --- a/translations/de-DE/data/reusables/webhooks/release_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/release_short_desc.md @@ -1 +1 @@ -Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/v3/repos/releases/)" REST API. +Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/rest/reference/repos#releases)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/repo_desc.md b/translations/de-DE/data/reusables/webhooks/repo_desc.md index df26fb3e7a..e0eca4218d 100644 --- a/translations/de-DE/data/reusables/webhooks/repo_desc.md +++ b/translations/de-DE/data/reusables/webhooks/repo_desc.md @@ -1 +1 @@ -`repository` | `object` | The [`repository`](/v3/repos/#get-a-repository) where the event occurred. +`repository` | `object` | The [`repository`](/rest/reference/repos#get-a-repository) where the event occurred. diff --git a/translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md b/translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md index 056531b019..d4b6cf9aa0 100644 --- a/translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md @@ -1 +1 @@ -Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/v3/migrations/source_imports/)" REST API. +Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/rest/reference/migrations#source-imports)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/repository_short_desc.md b/translations/de-DE/data/reusables/webhooks/repository_short_desc.md index df290ac0ea..b3e90e8d64 100644 --- a/translations/de-DE/data/reusables/webhooks/repository_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/repository_short_desc.md @@ -1 +1 @@ -Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/v3/repos/)" REST API. +Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/rest/reference/repos)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/star_short_desc.md b/translations/de-DE/data/reusables/webhooks/star_short_desc.md index f4fb663419..9569c6958e 100644 --- a/translations/de-DE/data/reusables/webhooks/star_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/star_short_desc.md @@ -1 +1 @@ -Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/status_short_desc.md b/translations/de-DE/data/reusables/webhooks/status_short_desc.md index 754f871add..6d835788c9 100644 --- a/translations/de-DE/data/reusables/webhooks/status_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/status_short_desc.md @@ -1 +1 @@ -When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/v3/repos/statuses/)" REST API. +When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/rest/reference/repos#statuses)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/team_add_short_desc.md b/translations/de-DE/data/reusables/webhooks/team_add_short_desc.md index 914535a212..ff260fc3cb 100644 --- a/translations/de-DE/data/reusables/webhooks/team_add_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/team_add_short_desc.md @@ -1 +1 @@ -When a [repository is added to a team](/v3/teams/#add-or-update-team-repository-permissions). +When a [repository is added to a team](/rest/reference/teams#add-or-update-team-repository-permissions). diff --git a/translations/de-DE/data/reusables/webhooks/team_short_desc.md b/translations/de-DE/data/reusables/webhooks/team_short_desc.md index fdcf742789..ff27913e21 100644 --- a/translations/de-DE/data/reusables/webhooks/team_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/team_short_desc.md @@ -1 +1 @@ -Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/v3/teams/)" REST API. +Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/rest/reference/teams)" REST API. diff --git a/translations/de-DE/data/reusables/webhooks/watch_short_desc.md b/translations/de-DE/data/reusables/webhooks/watch_short_desc.md index a853027b12..1b250fb019 100644 --- a/translations/de-DE/data/reusables/webhooks/watch_short_desc.md +++ b/translations/de-DE/data/reusables/webhooks/watch_short_desc.md @@ -1 +1 @@ -When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md index db14443ac9..29ed37dea2 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md @@ -91,7 +91,7 @@ steps: ### 依存関係のキャッシング -ワークフローの実行速度を上げるために、依存関係をキャッシュすることもできます。 実行に成功した後、ローカルのGradleパッケージキャッシュがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのパッケージリポジトリからダウンロードする必要がなくなります。 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 実行に成功した後、ローカルのGradleパッケージキャッシュがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのパッケージリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} ```yaml diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md index e79f37fcd6..9f5b4290f4 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md @@ -91,7 +91,7 @@ steps: ### 依存関係のキャッシング -ワークフローの実行速度を上げるために、依存関係をキャッシュすることもできます。 実行に成功した後、ローカルのMavenリポジトリがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 実行に成功した後、ローカルのMavenリポジトリがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} ```yaml diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md index 4b55c1a9e3..61f97ffc5b 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md @@ -129,7 +129,7 @@ Node.jsのバージョンを指定しなかった場合、{% data variables.prod {% data variables.product.prodname_dotcom %}ホストランナーには、依存関係マネージャーのnpmとYarnがインストールされています。 コードのビルドとテストに先立って、npmやYarnを使ってワークフロー中で依存関係をインストールできます。 Windows及びLinuxの{% data variables.product.prodname_dotcom %}ホストランナーには、Grunt、Gulp、Bowerもインストールされています。 -ワークフローの速度を上げるために、依存関係をキャッシュすることもできます。 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」を参照してください。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 #### npmの利用例 @@ -227,7 +227,7 @@ always-auth=true #### 依存関係のキャッシングの例 -`cache`アクションを使って、ユニークキーを使って依存関係をキャッシュし、将来のワークフローの実行で依存関係をリストアできます。 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} ```yaml @@ -240,8 +240,8 @@ steps: - name: Cache Node.js modules uses: actions/cache@v2 with: - # npm キャッシュファイルは Linux/macOS の「~/.npm」に保存される - path: ~/.npm + # npm cache files are stored in `~/.npm` on Linux/macOS + path: ~/.npm key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }} restore-keys: | ${{ runner.OS }}-node- diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md b/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md index a6f61f2184..546480993e 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md @@ -91,7 +91,7 @@ The table below describes the locations for various PowerShell modules in each { {% endnote %} -ワークフローの速度を上げるために、依存関係をキャッシュすることもできます。 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」を参照してください。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules: @@ -119,7 +119,7 @@ jobs: #### 依存関係のキャッシング -You can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」を参照してください。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system. diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-python.md b/translations/ja-JP/content/actions/guides/building-and-testing-python.md index 3596418b18..a661d34436 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-python.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-python.md @@ -140,11 +140,11 @@ jobs: - name: Set up Python 3.x uses: actions/setup-python@v2 with: - # セマンティックバージョン範囲の構文または Python バージョンの正確なバージョン - python-version: '3.x' - # オプション - x64 または x86 アーキテクチャ、デフォルトは x64 - architecture: 'x64' - # 現在の Python バージョンを印刷して、マトリックスをテストできます + # Semantic version range syntax or exact version of a Python version + python-version: '3.x' + # Optional - x64 or x86 architecture, defaults to x64 + architecture: 'x64' + # You can test your matrix by printing the current Python version - name: Display Python version run: python -c "import sys; print(sys.version)" ``` @@ -192,7 +192,7 @@ jobs: {% data variables.product.prodname_dotcom %}ホストランナーには、パッケージマネージャーのpipがインストールされています。 コードのビルドとテストに先立って、pipを使ってパッケージレジストリのPyPIから依存関係をインストールできます。 たとえば以下のYAMLは`pip`パッケージインストーラーと`setuptools`及び`wheel`パッケージのインストールやアップグレードを行います。 -ワークフローの速度を上げるために、依存関係をキャッシュすることもできます。 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」を参照してください。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 {% raw %} ```yaml @@ -228,13 +228,11 @@ steps: #### 依存関係のキャッシング -`cache`アクションを使って、ユニークキーを使ってpipの依存関係をキャッシュし、将来のワークフローの実行で依存関係をリストアできます。 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」を参照してください。

+When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 ランナーのオペレーティングシステムによって、pipは依存関係を様々な場所にキャッシュします。 キャッシュする必要があるパスは、使用するオペレーティングシステムによって以下のUbuntuの例とは異なるかもしれません。 詳しい情報については[Pythonのキャッシングの例](https://github.com/actions/cache/blob/main/examples.md#python---pip)を参照してください。 {% raw %} - - ```yaml steps: - uses: actions/checkout@v2 @@ -255,8 +253,6 @@ steps: - name: Install dependencies run: pip install -r requirements.txt ``` - - {% endraw %} {% note %} @@ -265,21 +261,15 @@ steps: {% endnote %} - - ### コードのテスト ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 - - #### pytest及びpytest-covでのテスト 以下の例では、`pytest`及び`pytest-cov`をインストールあるいはアップグレードします。 そしてテストが実行され、JUnit形式で出力が行われ、一方でコードカバレッジの結果がCoberturaに出力されます。 詳しい情報については[JUnit](https://junit.org/junit5/)及び[Cobertura](https://cobertura.github.io/cobertura/)を参照してください。 {% raw %} - - ```yaml steps: - uses: actions/checkout@v2 @@ -297,19 +287,13 @@ steps: pip install pytest-cov pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html ``` - - {% endraw %} - - #### Flake8を使ったコードのlint 以下の例は、`flake8`をインストールもしくはアップグレードし、それを使ってすべてのファイルをlintします。 詳しい情報については[Flake8](http://flake8.pycqa.org/en/latest/)を参照してください。 {% raw %} - - ```yaml steps: - uses: actions/checkout@v2 @@ -326,19 +310,13 @@ steps: pip install flake8 flake8 . ``` - - {% endraw %} - - #### toxでのテストの実行 {% data variables.product.prodname_actions %}では、toxでテストを実行し、その処理を複数のジョブに分散できます。 toxを起動する際には、特定のバージョンを指定するのではなく、`-e py`オプションを使って`PATH`中のPythonのバージョンを選択しなければなりません。 詳しい情報については [tox](https://tox.readthedocs.io/en/latest/)を参照してください。 {% raw %} - - ```yaml name: Python package @@ -364,12 +342,8 @@ jobs: # 「PATH」で Python のバージョンを使用して tox を実行する run: tox -e py ``` - - {% endraw %} - - ### 成果物としてのワークフローのデータのパッケージ化 ワークフローの完了後に、成果物をアップロードして見ることができます。 たとえば、ログファイル、コアダンプ、テスト結果、スクリーンショットを保存する必要があるかもしれません。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 @@ -377,8 +351,6 @@ jobs: 以下の例は、`upload-artifact`アクションを使って`pytest`の実行によるテスト結果をアーカイブする方法を示しています。 詳しい情報については[`upload-artifact`アクション](https://github.com/actions/upload-artifact)を参照してください。 {% raw %} - - ```yaml name: Python package @@ -413,12 +385,8 @@ jobs: # テスト失敗時にテスト結果を公開するには、always() を使用して常にこのステップを実行する if: ${{ always() }} ``` - - {% endraw %} - - ### パッケージレジストリへの公開 CIテストにパスしたなら、Pythonパッケージを任意のパッケージレジストリに公開するようにワークフローを設定できます。 @@ -426,8 +394,6 @@ CIテストにパスしたなら、Pythonパッケージを任意のパッケー パッケージを公開するのに必要なアクセストークンやクレデンシャルは、リポジトリシークレットを使って保存できます。 以下の例では、`twine`と`dist`を使ってパッケージを作成してPyPIに公開しています。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 {% raw %} - - ```yaml name: Upload Python Package @@ -456,8 +422,6 @@ jobs: python setup.py sdist bdist_wheel twine upload dist/* ``` - - {% endraw %} テンプレートワークフローに関する詳しい情報については[`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml)を参照してください。 diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md index 6412735291..f8d8cc1d4e 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md @@ -148,7 +148,7 @@ steps: #### 依存関係のキャッシング -The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. To enable caching, set the following. @@ -165,7 +165,7 @@ This will configure bundler to install your gems to `vendor/cache`. For each suc **Caching without setup-ruby** -For greater control over caching, you can use the `actions/cache` Action directly. 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」を参照してください。 +For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 {% raw %} ```yaml diff --git a/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md index a244634506..b617b0a5d6 100644 --- a/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -131,7 +131,7 @@ versions: ワークフローの実行中に、[`download-artifactaction`](https://github.com/actions/download-artifact) を使用して、同じワークフローの実行で以前にアップロードされたアーティファクトをダウンロードできます。 -ワークフローの実行が完了したら、{% data variables.product.prodname_dotcom %} または REST API を使用してアーティファクトをダウンロードまたは削除できます。 詳しい情報については、「[ワークフローアーティファクトをダウンロードする](/actions/managing-workflow-runs/downloading-workflow-artifacts)」、「[ワークフローアーティファクトを削除する](/actions/managing-workflow-runs/removing-workflow-artifacts)」、および「[アーティファクト REST API](/v3/actions/artifacts/)」を参照してください。 +ワークフローの実行が完了したら、{% data variables.product.prodname_dotcom %} または REST API を使用してアーティファクトをダウンロードまたは削除できます。 詳しい情報については、「[ワークフローアーティファクトをダウンロードする](/actions/managing-workflow-runs/downloading-workflow-artifacts)」、「[ワークフローアーティファクトを削除する](/actions/managing-workflow-runs/removing-workflow-artifacts)」、および「[アーティファクト REST API](/rest/reference/actions#artifacts)」を参照してください。 #### ワークフロー実行中の成果物のダウンロード 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 d164185855..ce58d29bd4 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 @@ -1,6 +1,6 @@ --- -title: Managing access to self-hosted runners using groups -intro: You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise. +title: グループを使用してセルフホストランナーへのアクセスを管理する +intro: ポリシーを使用して、Organization または Enterprise に追加されたセルフホストランナーへのアクセスを制限できます。 redirect_from: - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners versions: @@ -8,105 +8,108 @@ versions: enterprise-server: '>=2.22' --- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} +{% data variables.product.prodname_actions %} の支払いを管理する +{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 -### About self-hosted runner groups +### セルフホストランナーのグループについて {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** All organizations have a single default self-hosted runner group. Creating and managing additional self-hosted runner groups is only available to enterprise accounts, and for organizations owned by an enterprise account. +**注釈:** すべての Organization には、単一のデフォルトのセルフホストランナーグループがあります。 追加のセルフホストランナーグループの作成と管理は、Enterprise アカウント、および Enterprise アカウントが所有する Organization でのみ使用できます。 {% endnote %} {% endif %} -Self-hosted runner groups are used to control access to self-hosted runners at the organization and enterprise level. Enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group. Organization admins can configure access policies that control which repositories in an organization have access to the runner group. +セルフホストランナーグループは、Organization レベルおよび Enterprise レベルでセルフホストランナーへのアクセスを制御するために使用されます。 Enterprise の管理者は、Enterprise 内のどの Organization がランナーグループにアクセスできるかを制御するアクセスポリシーを設定できます。 Organization の管理者は、Organization 内のどのリポジトリがランナーグループにアクセスできるかを制御するアクセスポリシーを設定できます。 -When an enterprise admin grants an organization access to a runner group, organization admins can see the runner group listed in the organization's self-hosted runner settings. The organizations admins can then assign additional granular repository access policies to the enterprise runner group. +Enterprise の管理者が Organization にランナーグループへのアクセスを許可すると、Organization の管理者は、Organization のセルフホストランナー設定にリストされたランナーグループを表示できます。 Organization の管理者は、追加の詳細なリポジトリアクセスポリシーを Enterprise ランナーグループに割り当てることができます。 -When new runners are created, they are automatically assigned to the default group. Runners can only be in one group at a time. You can move runners from the default group to another group. For more information, see "[Moving a self-hosted runner to a group](#moving-a-self-hosted-runner-to-a-group)." +新しいランナーが作成されると、それらは自動的にデフォルトグループに割り当てられます。 ランナーは一度に1つのグループにのみ参加できます。 ランナーはデフォルトグループから別のグループに移動できます。 詳しい情報については、「[セルフホストランナーをグループに移動する](#moving-a-self-hosted-runner-to-a-group)」を参照してください。 -### Creating a self-hosted runner group for an organization +### Organization のセルフホストランナーグループを作成する -All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. +すべての Organization には、単一のデフォルトのセルフホストランナーグループがあります。 Enterprise アカウント内の Organization は、追加のセルフホストグループを作成できます。 Organization の管理者は、個々のリポジトリにランナーグループへのアクセスを許可できます。 -Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create. +セルフホストランナーは、作成時にデフォルトグループに自動的に割り当てられ、一度に 1 つのグループのメンバーになることができます。 ランナーはデフォルトグループから作成した任意のグループに移動できます。 -When creating a group, you must choose a policy that defines which repositories have access to the runner group. +グループを作成する場合、ランナーグループにアクセスできるリポジトリを定義するポリシーを選択する必要があります。 {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. In the **Self-hosted runners** section, click **Add new**, and then **New group**. +1. [**Self-hosted runners**] セクションで、[**Add new**] をクリックし、次に [**New group**] をクリックします。 - ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png) + ![新しいランナーを追加](/assets/images/help/settings/actions-org-add-runner-group.png) 1. Enter a name for your runner group, and assign a policy for repository access. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to a specific list of repositories, all private repositories, or all repositories in the organization.{% endif %} {% warning %} - **Warnung** + **Warning** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. + + 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。 {% endwarning %} - ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png) -1. Click **Save group** to create the group and apply the policy. + ![ランナーグループのオプションを追加](/assets/images/help/settings/actions-org-add-runner-group-options.png) +1. [**Save group**] をクリックしてグループを作成し、ポリシーを適用します。 -### Creating a self-hosted runner group for an enterprise +### Enterprise のセルフホストランナーグループを作成する -Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. +Enterprise は、セルフホストランナーをグループに追加して、アクセス管理を行うことができます。 Enterprise は、Enterprise アカウント内の特定の Organization がアクセスできるセルフホストランナーのグループを作成できます。 Organization の管理者は、追加の詳細なリポジトリアクセスポリシーを Enterprise ランナーグループに割り当てることができます。 -Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group. +セルフホストランナーは、作成時にデフォルトグループに自動的に割り当てられ、一度に 1 つのグループのメンバーになることができます。 登録処理中にランナーを特定のグループに割り当てることも、後でランナーをデフォルトグループからカスタムグループに移動することもできます。 When creating a group, you must choose a policy that defines which organizations have access to the runner group. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Click the **Self-hosted runners** tab. -1. Click **Add new**, and then **New group**. +1. [**Self-hosted runners**] タブをクリックします。 +1. [**Add new**] をクリックしてから、[**New group**] をクリックします。 - ![Add runner group](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) + ![新しいランナーを追加](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) 1. Enter a name for your runner group, and assign a policy for organization access. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to all organizations in the enterprise or choose specific organizations.{% endif %} {% warning %} - **Warnung** + **Warning** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. + + 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。 {% endwarning %} - ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png) -1. Click **Save group** to create the group and apply the policy. + ![ランナーグループのオプションを追加](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png) +1. [**Save group**] をクリックしてグループを作成し、ポリシーを適用します。 -### Changing the access policy of a self-hosted runner group +### セルフホストランナーグループのアクセスポリシーを変更する -You can update the access policy of a runner group, or rename a runner group. +ランナーグループのアクセスポリシーを更新したり、ランナーグループの名前を変更したりすることができます。 {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} -### Moving a self-hosted runner to a group +### セルフホストランナーをグループに移動する -New self-hosted runners are automatically assigned to the default group, and can then be moved to another group. +新しいセルフホストランナーは自動的にデフォルトグループに割り当てられ、その後、別のグループに移動できます。 -1. In the **Self-hosted runners** section of the settings page, locate the current group of the runner you want to move group and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) -1. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png) -1. To move the runner, click on the destination group. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) +1. 設定ページの [**Self-hosted runners**] セクションで、グループを移動するランナーの現在のグループを見つけ、グループメンバーのリストを展開します。 ![ランナーグループのメンバーを表示](/assets/images/help/settings/actions-org-runner-group-members.png) +1. セルフホストランナーの横にあるチェックボックスを選択し、[**Move to group**] をクリックして、利用可能な移動先を確認します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move.png) +1. 移動先のグループをクリックして、ランナーを移動します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) -### Removing a self-hosted runner group +### セルフホストランナーグループを削除する -Self-hosted runners are automatically returned to the default group when their group is removed. +セルフホストランナーは、グループが削除されると自動的にデフォルトグループに戻ります。 -1. In the **Self-hosted runners** section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) +1. 設定ページの [**Self-hosted runners**] セクションで、削除するグループを見つけて、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} ボタンをクリックします。 ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-kebab.png) -1. To remove the group, click **Remove group**. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png) - -1. Review the confirmation prompts, and click **Remove this runner group**. +1. グループを削除するには、[**Remove group**] をクリックします。 ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-remove.png) +1. 確認プロンプトを確認し、[**Remove this runner group**] をクリックします。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md index b66924e2c8..edb77e5c97 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md @@ -57,7 +57,7 @@ jobs: needs: build runs-on: ubuntu-latest steps: - - run: ./test_server.sh + - run: ./test_server.sh ``` 詳しい情報については、[`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) を参照してください。 @@ -106,7 +106,7 @@ jobs: ``` {% endraw %} -詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)」を参照してください。 +詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 ### データベースとサービスコンテナの利用 diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 9f409220da..b1c71453ca 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions -詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)」を参照してください。 +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 {% data variables.product.prodname_actions %}は、CircleCIのDocker Layer Caching（DLC）に相当する機能を持っていません。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index f01c4fa7b8..08077dad2f 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -262,7 +262,7 @@ jobs: runs-on: ubuntu-latest steps: - run: echo "This job will be run first, in parallel with build_a" - + test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] @@ -346,7 +346,7 @@ jobs: -詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/guides/caching-dependencies-to-speed-up-workflows)」を参照してください。 +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 ### 成果物 @@ -367,7 +367,7 @@ GitLab CI/CD {% raw %} ```yaml -script: +script: artifacts: paths: - math-homework.txt @@ -414,20 +414,20 @@ GitLab CI/CD container-job: variables: POSTGRES_PASSWORD: postgres - # PostgreSQL サービスコンテナとの通信に - # 使用されるホスト名 + # The hostname used to communicate with the + # PostgreSQL service container POSTGRES_HOST: postgres - # デフォルトの PostgreSQL ポート + # The default PostgreSQL port POSTGRES_PORT: 5432 image: node:10.18-jessie services: - postgres script: - # 「package.json」ファイル内のすべての依存関係の - # クリーンインストールを実行する + # Performs a clean installation of all dependencies + # in the `package.json` file - npm ci - # PostgreSQL クライアントを作成してクライアントにデータを入力し - # データを取得するスクリプトを実行する + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data - node client.js tags: - docker @@ -452,20 +452,20 @@ jobs: - name: Check out repository code uses: actions/checkout@v2 - # 「package.json」ファイル内のすべての依存関係の - # クリーンインストールを実行する + # Performs a clean installation of all dependencies + # in the `package.json` file - name: Install dependencies run: npm ci - name: Connect to PostgreSQL - # PostgreSQL クライアントを作成してクライアントにデータを入力し - # データを取得するスクリプトを実行する + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data run: node client.js env: - # PostgreSQL サービスコンテナとの通信に - # 使用されるホスト名 + # The hostname used to communicate with the + # PostgreSQL service container POSTGRES_HOST: postgres - # デフォルトの PostgreSQL ポート + # The default PostgreSQL port POSTGRES_PORT: 5432 ``` {% endraw %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 241ff16b29..129c23238c 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -163,6 +163,12 @@ git: +#### Using environment variables in a matrix + +Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. + +In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} + ### Key features in {% data variables.product.prodname_actions %} When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}: @@ -281,7 +287,7 @@ jobs: ### 依存関係のキャッシング -Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. +Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. @@ -316,7 +322,7 @@ cache: npm
-詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/guides/caching-dependencies-to-speed-up-workflows)」を参照してください。 +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 ### 一般的なタスクの例 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 7663b434be..4a1293271a 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -14,7 +14,7 @@ versions: 実行が完了している場合には、結果が成功か失敗か、キャンセルされたか、またはニュートラルかを確認できます。 実行が失敗した場合には、ビルドログを表示して検索し、失敗の原因を診断してワークフローを再実行することもできます。 また、課金対象のジョブ実行時間を表示したり、ログをダウンロードして成果物をビルドすることもできます。 -{% data variables.product.prodname_actions %}は、Checks APIを使用してワークフローのステータス、結果、ログを出力します。 {% data variables.product.prodname_dotcom %} は、ワークフローの実行に対してそれぞれ新しいチェックスイートを作成します。 チェックスイートには、ワークフロー内の各ジョブに対するチェック実行が含まれ、各ジョブにはステップが含まれています。 {% data variables.product.prodname_actions %}は、ワークフローのステップとして実行されます。 チェック API の詳細については、「[チェック](/v3/checks/)」を参照してください。 +{% data variables.product.prodname_actions %}は、Checks APIを使用してワークフローのステータス、結果、ログを出力します。 {% data variables.product.prodname_dotcom %} は、ワークフローの実行に対してそれぞれ新しいチェックスイートを作成します。 チェックスイートには、ワークフロー内の各ジョブに対するチェック実行が含まれ、各ジョブにはステップが含まれています。 {% data variables.product.prodname_actions %}は、ワークフローのステップとして実行されます。 For more information about the Checks API, see "[Checks](/rest/reference/checks)." {% data reusables.github-actions.invalid-workflow-files %} diff --git a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md index 3d44f57e2c..898f939e43 100644 --- a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md @@ -79,7 +79,7 @@ versions: ### `GITHUB_TOKEN`の権限 -{% data variables.product.prodname_github_apps %} が各権限でアクセできる API エンドポイントについては、「[{% data variables.product.prodname_github_app %} の権限](/v3/apps/permissions/)」を参照してください。 +{% data variables.product.prodname_github_apps %} が各権限でアクセできる API エンドポイントについては、「[{% data variables.product.prodname_github_app %} の権限](/rest/reference/permissions-required-for-github-apps)」を参照してください。 | 権限 | アクセスタイプ | フォークしたリポジトリからのアクセス | | ----------- | --------- | ------------------ | diff --git a/translations/ja-JP/content/actions/reference/encrypted-secrets.md b/translations/ja-JP/content/actions/reference/encrypted-secrets.md index 3d267f91f6..e14a78e759 100644 --- a/translations/ja-JP/content/actions/reference/encrypted-secrets.md +++ b/translations/ja-JP/content/actions/reference/encrypted-secrets.md @@ -43,11 +43,11 @@ versions: {% endwarning %} -REST API を使用してシークレットを管理することもできます。 詳しい情報については、「[シークレット](/v3/actions/secrets/)」を参照してください。 +REST API を使用してシークレットを管理することもできます。 詳しい情報については、「[シークレット](/rest/reference/actions#secrets)」を参照してください。 #### 認証情報のアクセス許可を制限する -クレデンシャルを生成する際には、可能な限り最小限の権限だけを許可することをおすすめします。 たとえば、個人のクレデンシャルを使う代わりに、[デプロイキー](/v3/guides/managing-deploy-keys/#deploy-keys)あるいはサービスアカウントを使ってください。 必要なのが読み取りだけであれば、読み取りのみの権限を許可すること、そしてアクセスをできるかぎり限定することを考慮してください。 個人アクセストークン（PAT）を生成する際には、必要最小限のスコープを選択してください。 +クレデンシャルを生成する際には、可能な限り最小限の権限だけを許可することをおすすめします。 たとえば、個人のクレデンシャルを使う代わりに、[デプロイキー](/developers/overview/managing-deploy-keys#deploy-keys)あるいはサービスアカウントを使ってください。 必要なのが読み取りだけであれば、読み取りのみの権限を許可すること、そしてアクセスをできるかぎり限定することを考慮してください。 個人アクセストークン（PAT）を生成する際には、必要最小限のスコープを選択してください。 ### リポジトリの暗号化されたシークレットの作成 diff --git a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md index 56f38cc17c..76307822e2 100644 --- a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md @@ -143,38 +143,27 @@ jobs: {% data reusables.github-actions.branch-requirement %} -{% data variables.product.product_name %} の外部で生じるアクティビティのためにワークフローをトリガーしたい場合、{% data variables.product.prodname_dotcom %} API を使って、[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) と呼ばれる webhook イベントをトリガーできます。 詳細については、「リポジトリディスパッチ イベントを作成 - -」を参照してください。

+{% data variables.product.product_name %} の外部で生じるアクティビティのためにワークフローをトリガーしたい場合、{% data variables.product.prodname_dotcom %} API を使って、[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) と呼ばれる webhook イベントをトリガーできます。 詳しい情報については、「[リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」を参照してください。 カスタム `repository_dispatch` webhook イベントをトリガーするには、{% data variables.product.product_name %} API エンドポイントに `POST` リクエストを送信して、アクティビティのタイプを説明する `event_type` 名を提供する必要があります。 ワークフローの実行をトリガーするには、`repository_dispatch` イベントを使用するようワークフローを設定する必要もあります。 - - ##### サンプル デフォルトでは、すべての`event_types`がワークフローの実行をトリガーします。 特定の`event_type`の値が`repository_dispatch` webhookのペイロード内で送信された時にのみワークフローが実行されるように制限できます。 リポジトリのディスパッチイベントを生成する際に、`repository_dispatch`ペイロード内で送信されるイベントの種類を定義します。 - - ```yaml on: repository_dispatch: types: [opened, deleted] ``` - - - ### webhook イベント -GitHub で webhook イベントが作成された際にワークフローを実行するよう設定できます。 イベントによっては、そのイベントをトリガーするアクティビティタイプが 複数あります。 イベントをトリガーするアクティビティタイプが複数ある場合は、ワークフローの実行をトリガーするアクティビティタイプを指定できます。 詳しい情報については、「[webhook](/webhooks)」を参照してください。 - - +GitHub で webhook イベントが作成された際にワークフローを実行するよう設定できます。 イベントによっては、そのイベントをトリガーするアクティビティタイプが 複数あります。 イベントをトリガーするアクティビティタイプが複数ある場合は、ワークフローの実行をトリガーするアクティビティタイプを指定できます。 詳しい情報については、「[webhook](/webhooks)」を参照してください。 #### `check_run` -`check_run` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[チェック実行](/v3/checks/runs/)」を参照してください。 +`check_run` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[チェック実行](/rest/reference/checks#runs)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -182,25 +171,19 @@ GitHub で webhook イベントが作成された際にワークフローを実 | -------------------------------------------------- | -------------------------------------------------------------------------------------------- | ----------------- | ------------ | | [`check_run`](/webhooks/event-payloads/#check_run) | - `created`
- `rerequested`
- `completed`
- `requested_action` | デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、チェック実行が `rerequested` または `requested_action` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: check_run: types: [rerequested, requested_action] ``` - - - #### `check_suite` -`check_suite` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[チェックスイート](/v3/checks/suites/)」を参照してください。 +`check_suite` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[チェックスイート](/rest/reference/checks#suites)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -214,46 +197,34 @@ on: | ------------------------------------------------------ | -------------------------------------------------------------------------- | ----------------- | ------------ | | [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`
- `requested`
- `rerequested`
| デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、チェック実行が `rerequested` または `completed` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: check_suite: types: [rerequested, completed] ``` - - - #### `create` -誰かがブランチまたはタグを作成し、それによって `create` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの作成](/v3/git/refs/#create-a-reference)」を参照してください。 +誰かがブランチまたはタグを作成し、それによって `create` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの作成](/rest/reference/git#create-a-reference)」を参照してください。 | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------- | ---------- | ---------------------- | -------------- | | [`create`](/webhooks/event-payloads/#create) | n/a | 直近でブランチまたはタグが作成されたコミット | 作成されたブランチまたはタグ | - たとえば、`create` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: create ``` - - - #### `delete` -誰かがブランチまたはタグを作成し、それによって `create` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの削除](/v3/git/refs/#delete-a-reference)」を参照してください。 +誰かがブランチまたはタグを作成し、それによって `create` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの削除](/rest/reference/git#delete-a-reference)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -261,19 +232,13 @@ on: | -------------------------------------------- | ---------- | ----------------- | ------------ | | [`delete`](/webhooks/event-payloads/#delete) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ | - たとえば、`delete` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: delete ``` - - - #### `deployment` 誰かがデプロイメントを作成し、それによって `deploymen` イベントがトリガーされるときにワークフローを実行します。 コミット SHA 付きで作成されたデプロイメントには Git ref がない場合があります。 REST API の詳細については、「[デプロイメント](/rest/reference/repos#deployments)」を参照してください。 @@ -282,19 +247,13 @@ on: | ---------------------------------------------------- | ---------- | ------------ | ---------------------------- | | [`deployment`](/webhooks/event-payloads/#deployment) | n/a | デプロイされるコミット | デプロイされるブランチまたはタグ (コミットの場合は空) | - たとえば、`deployment` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: deployment ``` - - - #### `deployment_status` サードパーティプロバイダーがデプロイメントステータスを提供し、それによって `deployment_status` イベントがトリガーされるときにワークフローを実行します。 コミット SHA 付きで作成されたデプロイメントには Git ref がない場合があります。 REST API の詳細については、「[デプロイメントステータスの作成](/rest/reference/repos#create-a-deployment-status)」を参照してください。 @@ -303,22 +262,16 @@ on: | ------------------------------------------------------------------ | ---------- | ------------ | ---------------------------- | | [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | デプロイされるコミット | デプロイされるブランチまたはタグ (コミットの場合は空) | - たとえば、`deployment_status` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: deployment_status ``` - - - #### `fork` -誰かがリポジトリをフォークし、それによって `deployment_status` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[フォークの作成](/v3/repos/forks/#create-a-fork)」を参照してください。 +誰かがリポジトリをフォークし、それによって `deployment_status` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[フォークの作成](/rest/reference/repos#create-a-fork)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -326,19 +279,13 @@ on: | ---------------------------------------- | ---------- | ----------------- | ------------ | | [`fork`](/webhooks/event-payloads/#fork) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ | - たとえば、`fork` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: fork ``` - - - #### `gollum` 誰かが Wiki ページを作成または更新し、それによって `gollum` イベントがトリガーされるときにワークフローを実行します。 @@ -349,19 +296,13 @@ on: | -------------------------------------------- | ---------- | ----------------- | ------------ | | [`gollum`](/webhooks/event-payloads/#gollum) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ | - たとえば、`gollum` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: gollum ``` - - - #### `issue_comment` `issue_comment` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Issue コメント](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)」を参照してください。 @@ -372,27 +313,21 @@ on: | --------------------------------------------------------- | ----------------------------------------------------------------- | ----------------- | ------------ | | [`issue_comment`](/rest/reference/activity#issue_comment) | - `created`
- `edited`
- `deleted`
| デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、Issue コメントが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: issue_comment: types: [created, deleted] ``` - The `issue_comment` event occurs for comments on both issues and pull requests. To determine whether the `issue_comment` event was triggered from an issue or pull request, you can check the event payload for the `issue.pull_request` property and use it as a condition to skip a job. For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue. {% raw %} - - ```yaml on: issue_comment @@ -415,15 +350,11 @@ jobs: - run: | echo "Comment on issue #${{ github.event.issue.number }}" ``` - - {% endraw %} - - #### `issues` -`Issue` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Issue](/v3/issues)」を参照してください。 +`Issue` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Issue](/rest/reference/issues)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -431,25 +362,19 @@ jobs: | -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------ | | [`issues`](/webhooks/event-payloads/#issues) | - `opened`
- `edited`
- `deleted`
- `transferred`
- `pinned`
- `unpinned`
- `closed`
- `reopened`
- `assigned`
- `unassigned`
- `labeled`
- `unlabeled`
- `locked`
- `unlocked`
- `milestoned`
- `demilestoned` | デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、Issue が `opened`、`edited`、または `milestoned` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: issues: types: [opened, edited, milestoned] ``` - - - #### `label` -`label` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[ラベル](/v3/issues/labels/)」を参照してください。 +`label` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[ラベル](/rest/reference/issues#labels)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -457,25 +382,19 @@ on: | ------------------------------------------ | ----------------------------------------------------------------- | ----------------- | ------------ | | [`label`](/webhooks/event-payloads/#label) | - `created`
- `edited`
- `deleted`
| デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、ラベルが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: label: types: [created, deleted] ``` - - - #### `milestone` -`milestone` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[マイルストーン](/v3/issues/milestones/)」を参照してください。 +`milestone` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[マイルストーン](/rest/reference/issues#milestones)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -483,22 +402,16 @@ on: | -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ----------------- | ------------ | | [`milestone`](/webhooks/event-payloads/#milestone) | - `created`
- `closed`
- `opened`
- `edited`
- `deleted`
| デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえばマイルストーンが`opened`あるいは`deleted`になったときにワークフローを実行できます。 - - ```yaml on: milestone: types: [opened, deleted] ``` - - - #### `page_build` 誰かが {% data variables.product.product_name %} ページ対応のブランチを作成し、それによって `page_build` イベントがトリガーされるときにワークフローを実行します。 For information about the REST API, see "[Pages](/rest/reference/repos#pages)." @@ -509,22 +422,16 @@ on: | ---------------------------------------------------- | ---------- | ----------------- | ------------ | | [`page_build`](/webhooks/event-payloads/#page_build) | n/a | デフォルトブランチの直近のコミット | n/a | - たとえば、`page_build` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: page_build ``` - - - #### `project` -`project` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクト](/v3/projects/)」を参照してください。 +`project` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクト](/rest/reference/projects)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -532,25 +439,19 @@ on: | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------ | | [`project`](/webhooks/event-payloads/#project) | - `created`
- `updated`
- `closed`
- `reopened`
- `edited`
- `deleted`
| デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、プロジェクトが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: project: types: [created, deleted] ``` - - - #### `project_card` -`project_card` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクトカード](/v3/projects/cards)」を参照してください。 +`project_card` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクトカード](/rest/reference/projects#cards)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -558,25 +459,19 @@ on: | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ----------------- | ------------ | | [`project_card`](/webhooks/event-payloads/#project_card) | - `created`
- `moved`
- `converted` to an issue
- `edited`
- `deleted` | デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、プロジェクトカードが `opened` または `deleted` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: project_card: types: [opened, deleted] ``` - - - #### `project_column` -`project_column` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクト列](/v3/projects/columns)」を参照してください。 +`project_column` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクト列](/rest/reference/projects#columns)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -584,25 +479,19 @@ on: | ------------------------------------------------------------ | --------------------------------------------------------------------------- | ----------------- | ------------ | | [`project_column`](/webhooks/event-payloads/#project_column) | - `created`
- `updated`
- `moved`
- `deleted` | デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、プロジェクト列が `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: project_column: types: [created, deleted] ``` - - - #### `public` -誰かがプライベートリポジトリをパブリックにし、それによって `public` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リポジトリの編集](/v3/repos/#edit)」を参照してください。 +誰かがプライベートリポジトリをパブリックにし、それによって `public` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リポジトリの編集](/rest/reference/repos#edit)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -610,22 +499,16 @@ on: | -------------------------------------------- | ---------- | ----------------- | ------------ | | [`public`](/webhooks/event-payloads/#public) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ | - たとえば、`public` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: public ``` - - - #### `pull_request` -`pull_request` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プルリクエスト](/v3/pulls)」を参照してください。 +`pull_request` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プルリクエスト](/rest/reference/pulls)」を参照してください。 {% note %} @@ -637,108 +520,84 @@ on: | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------------------------------------- | | [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`
- `unassigned`
- `labeled`
- `unlabeled`
- `opened`
- `edited`
- `closed`
- `reopened`
- `synchronize`
- `ready_for_review`
- `locked`
- `unlocked`
- `review_requested`
- `review_request_removed` | `GITHUB_REF` ブランチ上の直近のマージコミット | PR マージブランチ `refs/pull/:prNumber/merge` | - デフォルトのアクティビティタイプを拡大または制限するには、`types` キーワードを使用します。 詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/articles/workflow-syntax-for-github-actions#onevent_nametypes)」を参照してください。 たとえば、プルリクエストが `assigned`、`opened`、`synchronize`、または `reopened` だったときにワークフローを実行できます。 - - ```yaml on: pull_request: types: [assigned, opened, synchronize, reopened] ``` - {% data reusables.developer-site.pull_request_forked_repos_link %} - - #### `pull_request_review` -`pull_request_review` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プルリクエストレビュー](/v3/pulls/reviews)」を参照してください。 +`pull_request_review` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プルリクエストレビュー](/rest/reference/pulls#reviews)」を参照してください。 | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------------------------------- | ---------------------------------------------------------- | ----------------------------- | -------------------------------------- | | [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`
- `edited`
- `dismissed` | `GITHUB_REF` ブランチ上の直近のマージコミット | PR マージブランチ `refs/pull/:prNumber/merge` | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、プルリクエストレビューが `eidted` または `dismissed` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: pull_request_review: types: [edited, dismissed] ``` - {% data reusables.developer-site.pull_request_forked_repos_link %} - - #### `pull_request_review_comment` -プルリクエストの統合 diff へのコメントが変更され、それによって `pull_request_review_comment` イベントがトリガーされるときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[レビューコメント](/v3/pulls/comments)」を参照してください。 +プルリクエストの統合 diff へのコメントが変更され、それによって `pull_request_review_comment` イベントがトリガーされるときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[レビューコメント](/rest/reference/pulls#comments)」を参照してください。 | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------------------------------------- | ------------------------------------------------------ | ----------------------------- | -------------------------------------- | | [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`
- `edited`
- `deleted` | `GITHUB_REF` ブランチ上の直近のマージコミット | PR マージブランチ `refs/pull/:prNumber/merge` | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、プルリクエストレビューコメントが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: pull_request_review_comment: types: [created, deleted] ``` - {% data reusables.developer-site.pull_request_forked_repos_link %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - - #### `pull_request_target` -このイベントは `pull_request` に似ていますが、マージコミットではなく、プルリクエストのベースリポジトリのコンテキストで実行される点で異なります。 つまり、ベースリポジトリのコミットで定義されたワークフローのみが実行されるため、プルリクエストによってトリガーされたワークフローでシークレットをより安全に使用できるようになります。 たとえば、このイベントでは、イベントペイロードの内容に基づいて、プルリクエストにラベルを付けてコメントを付けるワークフローを作成できます。 +このイベントは `pull_request` に似ていますが、マージコミットではなく、プルリクエストのベースリポジトリのコンテキストで実行される点で異なります。 つまり、ベースリポジトリのコミットで定義されたワークフローのみが実行されるため、プルリクエストによってトリガーされたワークフローでシークレットをより安全に使用できるようになります。 たとえば、このイベントでは、イベントペイロードの内容に基づいて、プルリクエストにラベルを付けてコメントを付けるワークフローを作成できます。 | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ------------ | | [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`
- `unassigned`
- `labeled`
- `unlabeled`
- `opened`
- `edited`
- `closed`
- `reopened`
- `synchronize`
- `ready_for_review`
- `locked`
- `unlocked`
- `review_requested`
- `review_request_removed` | PR ベースブランチの直近のコミット | PR ベースブランチ | - デフォルトでは、ワークフローは、`pull_request_target` のアクティビティタイプが `opened`、`synchronize`、または `reopened` のときにのみ実行されます。 他のアクティビティタイプについてもワークフローをトリガーするには、`types` キーワードを使用してください。 詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/articles/workflow-syntax-for-github-actions#onevent_nametypes)」を参照してください。 たとえば、プルリクエストが `assigned`、`opened`、`synchronize`、または `reopened` だったときにワークフローを実行できます。 - - ```yaml on: pull_request_target types: [assigned, opened, synchronize, reopened] ``` - {% endif %} - - #### `push` {% note %} -**ノート：** GitHub Actionsが利用できるwebhookのペイロードには、`commit`オブジェクト中の`added`、`removed`、`modified`属性は含まれません。 完全なcommitオブジェクトは、REST APIを使って取得できます。 詳しい情報については、「[1つのコミットの取得](/v3/repos/commits/#get-a-single-commit)」を参照してください。 +**ノート：** GitHub Actionsが利用できるwebhookのペイロードには、`commit`オブジェクト中の`added`、`removed`、`modified`属性は含まれません。 完全なcommitオブジェクトは、REST APIを使って取得できます。 詳しい情報については、「[1つのコミットの取得](/rest/reference/repos#get-a-single-commit)」を参照してください。 {% endnote %} @@ -748,19 +607,13 @@ on: pull_request_target | ---------------------------------------- | ---------- | --------------------------------------------- | ------------ | | [`push`](/webhooks/event-payloads/#push) | n/a | プッシュされたコミット、ただし (デフォルトブランチの際に) ブランチを削除する場合を除く | 更新された ref | - たとえば、`push` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: push ``` - - - #### `registry_package` パッケージが`published`もしくは`updated`されるとワークフローを実行します。 詳しい情報については「[{% data variables.product.prodname_registry %}でのパッケージ管理](/github/managing-packages-with-github-packages)」を参照してください。 @@ -769,22 +622,16 @@ on: | ------------------------------------------------------- | ----------------------------------- | --------------- | --------------------- | | [`registry_package`](/webhooks/event-payloads/#package) | - `published`
- `updated` | 公開されたパッケージのコミット | 公開されたパッケージのブランチもしくはタグ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、パッケージが`published`されたときにワークフローを実行できます。 - - ```yaml on: registry_package: types: [published] ``` - - - #### `release` {% note %} @@ -793,31 +640,25 @@ on: {% endnote %} -`release` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[リリース](/v3/repos/releases/)」を参照してください。 +`release` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[リリース](/rest/reference/repos#releases)」を参照してください。 | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ------------ | | [`release`](/webhooks/event-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | リリースのタグが付いた直近のコミット | リリースのタグ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、リリースが `published` だったときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: release: types: [published] ``` - - - #### `status` -Git コミットのステータスが変更された、それによって `status` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[ステータス](/v3/repos/statuses/)」を参照してください。 +Git コミットのステータスが変更された、それによって `status` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[ステータス](/rest/reference/repos#statuses)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -825,22 +666,16 @@ Git コミットのステータスが変更された、それによって `statu | -------------------------------------------- | ---------- | ----------------- | ------------ | | [`status`](/webhooks/event-payloads/#status) | n/a | デフォルトブランチの直近のコミット | n/a | - たとえば、`status` イベントが発生したときにワークフローを実行する例は、次のとおりです。 - - ```yaml on: status ``` - - - #### `Watch` -`watch` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Star を付ける](/v3/activity/starring/)」を参照してください。 +`watch` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Star を付ける](/rest/reference/activity#starring)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -848,24 +683,18 @@ on: | ------------------------------------------ | ----------- | ----------------- | ------------ | | [`Watch`](/webhooks/event-payloads/#watch) | - `started` | デフォルトブランチの直近のコミット | デフォルトブランチ | - {% data reusables.developer-site.limit_workflow_to_activity_types %} たとえば、誰かがリポジトリに Star を付け、それが Watch イベントをトリガーする `started` アクティブタイプである場合にワークフローを実行する例は、次のとおりです。 - - ```yaml on: watch: types: [started] ``` - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - - #### `workflow_run` {% data reusables.webhooks.workflow_run_desc %} @@ -874,13 +703,10 @@ on: | -------------------------------------------------------- | ---------- | ----------------- | ------------ | | [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | デフォルトブランチの直近のコミット | デフォルトブランチ | - このイベントからブランチをフィルタする必要がある場合は、`branches` または `branches-ignore` を使用できます。 この例では、ワークフローは別の「Run Tests」ワークフローの完了後に実行されるように設定されています。 - - ```yaml on: workflow_run: @@ -891,11 +717,8 @@ on: - requested ``` - {% endif %} - - ### 個人アクセストークンを使った新しいワークフローのトリガー {% data reusables.github-actions.actions-do-not-trigger-workflows %} 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。 diff --git a/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md index fff4da1276..7792779086 100644 --- a/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md @@ -79,6 +79,7 @@ GitHub アクションの使用は、 - 「[Organization の {% data variables.product.prodname_actions %} を無効化または制限する](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)」{% if currentVersion == "free-pro-team@latest" %} - {% data variables.product.prodname_ghe_cloud %} の「[Enterprise アカウントでの {% data variables.product.prodname_actions %} ポリシーを適用する](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)」{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### ワークフローの無効化と有効化 {% data variables.product.prodname_dotcom %} のリポジトリで個々のワークフローを有効化または無効化できます。 @@ -86,3 +87,4 @@ GitHub アクションの使用は、 {% data reusables.actions.scheduled-workflows-disabled %} 詳しい情報については、「[ワークフローの無効化と有効化](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)」を参照してください。 +{% endif %} diff --git a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md index 5c1a003c3f..cfee0dd76f 100644 --- a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md @@ -227,7 +227,7 @@ defaults: ワークフローの利用限度内であれば、実行するジョブ数に限度はありません。 詳細については、{% data variables.product.prodname_dotcom %} ホストランナーの「[使用制限と支払い](/actions/reference/usage-limits-billing-and-administration)」、およびセルフホストランナーの使用制限については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。 -ワークフローの実行中で動作しているジョブのユニークな識別子が必要な場合は、{% data variables.product.prodname_dotcom %} APIが利用できます。 詳しい情報については、「[ワークフロージョブ](/v3/actions/workflow-jobs)」を参照してください。 +ワークフローの実行中で動作しているジョブのユニークな識別子が必要な場合は、{% data variables.product.prodname_dotcom %} APIが利用できます。 詳しい情報については、「[ワークフロージョブ](/rest/reference/actions#workflow-jobs)」を参照してください。 ### **`jobs.`** @@ -878,34 +878,9 @@ strategy: ##### Using environment variables in a matrix -You can add custom environment variables for each test combination by using `include` with `env`. You can then refer to the custom environment variables in a later step. +You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. -In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: - -{% raw %} -```yaml -name: Node.js CI -on: [push] -jobs: - build: - runs-on: ubuntu-latest - strategy: - matrix: - include: - - node-version: 10.x - site: "prod" - datacenter: "site-a" - - node-version: 12.x - site: "dev" - datacenter: "site-b" - steps: - - name: Echo site details - env: - SITE: ${{ matrix.site }} - DATACENTER: ${{ matrix.datacenter }} - run: echo $SITE $DATACENTER -``` -{% endraw %} +{% data reusables.github-actions.matrix-variable-example %} ### **`jobs..strategy.fail-fast`** diff --git a/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md b/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md index 504def4c49..4c5bfae5dd 100644 --- a/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md +++ b/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: {% data variables.product.product_location %}のユーザアカウントは、認証方式を変更しても保存され、ユーザはユーザ名が変更されない限り、同じアカウントにログインし続けることができます。 -新しい認証方式でユーザ名が変更される場合、新しいアカウントが作成されます。 管理者は、サイト管理者設定または[ユーザ管理 API](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user) を使用してユーザ名を変更できます。 +新しい認証方式でユーザ名が変更される場合、新しいアカウントが作成されます。 As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). 他に考慮しなければならない問題には以下があります。 diff --git a/translations/ja-JP/content/admin/configuration/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/command-line-utilities.md index 12267d4b63..8e16bbdc6c 100644 --- a/translations/ja-JP/content/admin/configuration/command-line-utilities.md +++ b/translations/ja-JP/content/admin/configuration/command-line-utilities.md @@ -159,7 +159,7 @@ $ ghe-es-index-status -do | column -ts, #### ghe-legacy-github-services-report -このユーティリティは、2018 年 10 月 1 日に廃止予定の統合方式である {% data variables.product.prodname_dotcom %} サービスを使用しているアプライアンス上のリポジトリを一覧表示します。 アプライアンス上のユーザーは、特定のリポジトリへのプッシュに対する通知を作成するために、{% data variables.product.prodname_dotcom %} サービスを設定している場合があります。 詳しい情報については、{% data variables.product.prodname_blog %} で「[{% data variables.product.prodname_dotcom %} サービスの非推奨をアナウンスする](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)」、または「[{% data variables.product.prodname_dotcom %} サービスを置き換える](/v3/guides/replacing-github-services/)」を参照してください。 このコマンドの詳細や追加のオプションについては、`-h` フラグを使用してください。 +このユーティリティは、2018 年 10 月 1 日に廃止予定の統合方式である {% data variables.product.prodname_dotcom %} サービスを使用しているアプライアンス上のリポジトリを一覧表示します。 アプライアンス上のユーザーは、特定のリポジトリへのプッシュに対する通知を作成するために、{% data variables.product.prodname_dotcom %} サービスを設定している場合があります。 詳しい情報については、{% data variables.product.prodname_blog %} で「[{% data variables.product.prodname_dotcom %} サービスの非推奨をアナウンスする](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)」、または「[{% data variables.product.prodname_dotcom %} サービスを置き換える](/developers/overview/replacing-github-services)」を参照してください。 このコマンドの詳細や追加のオプションについては、`-h` フラグを使用してください。 ```shell ghe-legacy-github-services-report diff --git a/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md index 9735573778..5c428b8ae5 100644 --- a/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md +++ b/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md @@ -37,7 +37,7 @@ versions: {% data variables.product.prodname_github_connect %} を有効化しても、{% data variables.product.prodname_dotcom_the_website %} のユーザは {% data variables.product.prodname_ghe_server %} を変更できるようになりません。 -GraphQL APIを利用したEnterpriseアカウントの管理に関する詳しい情報については、「[Enterprise アカウント](/v4/guides/managing-enterprise-accounts)」を参照してください。 +GraphQL APIを利用したEnterpriseアカウントの管理に関する詳しい情報については、「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。 ### {% data variables.product.prodname_github_connect %} の有効化 1. まず、 diff --git a/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md b/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md index 2c16f3506a..923bed085a 100644 --- a/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md +++ b/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md @@ -19,6 +19,6 @@ With the APIs, you can automate many administrative tasks. 例えば、 - {% data variables.enterprise.management_console %} に変更を加える。 詳しい情報については、「[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)」を参照してください。 - LDAP 同期を設定する。 詳しい情報については、「[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)」を参照してください。{% endif %} - Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)." -- Enterpriseアカウントの管理。 詳しい情報については「[Enterprise アカウント](/v4/guides/managing-enterprise-accounts)」を参照してください。 +- Enterpriseアカウントの管理。 詳しい情報については「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。 -For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). \ No newline at end of file +For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). diff --git a/translations/ja-JP/content/admin/user-management/audited-actions.md b/translations/ja-JP/content/admin/user-management/audited-actions.md index 4de3710f1a..f21212f704 100644 --- a/translations/ja-JP/content/admin/user-management/audited-actions.md +++ b/translations/ja-JP/content/admin/user-management/audited-actions.md @@ -138,7 +138,7 @@ versions: [デプロイキー]: /guides/managing-deploy-keys/#deploy-keys [deploy key]: /guides/managing-deploy-keys/#deploy-keys [generate token]: /articles/creating-an-access-token-for-command-line-use - [OAuth アクセストークン]: /v3/oauth/ + [OAuth アクセストークン]: /developers/apps/authorizing-oauth-apps [OAuth application]: /guides/basics-of-authentication/#registering-your-app [OAuth アプリケーション]: /guides/basics-of-authentication/#registering-your-app [2fa]: /articles/about-two-factor-authentication diff --git a/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md index 0031546919..cc09f5930a 100644 --- a/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md +++ b/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md @@ -27,7 +27,7 @@ versions: {% data variables.product.prodname_dotcom_the_website %} からリポジトリデータをエクスポートするには、移行 API を使います。 -移行APIは現在プレビュー期間です。すなわち、エンドポイントとパラメータは将来変更されることがあります。 移行APIにアクセスするには、カスタムの[メディアタイプ](/v3/media)として`application/vnd.github.wyandotte-preview+json`を`Accept`ヘッダで渡さなければなりません。 以下の例にはカスタムのメディアタイプが含まれています。 +移行APIは現在プレビュー期間です。すなわち、エンドポイントとパラメータは将来変更されることがあります。 移行APIにアクセスするには、カスタムの[メディアタイプ](/rest/overview/media-types)として`application/vnd.github.wyandotte-preview+json`を`Accept`ヘッダで渡さなければなりません。 以下の例にはカスタムのメディアタイプが含まれています。 ### 移行アーカイブの生成 @@ -37,7 +37,7 @@ versions: 2. 移行エンドポイントに `POST` することで移行を開始します。 以下が必要です: * 認証のためのアクセストークン。 - * 移行する[リポジトリのリスト](/v3/repos/#list-organization-repositories)。 + * 移行する[リポジトリのリスト](/rest/reference/repos#list-organization-repositories)。 ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md index 453ba11236..eb2a7bf1fb 100644 --- a/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### {% data variables.product.prodname_dotcom_the_website %} で Organization からリポジトリを削除する -{% data variables.product.prodname_dotcom_the_website %} Organization のリポジトリをロック解除した後、[リポジトリ削除エンドポイント](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository)を使用して以前に移行したすべてのリポジトリを削除する必要があります。 認証のためのアクセストークンが必要になります。 +After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). 認証のためのアクセストークンが必要になります。 ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md index fac744063a..4e5547718b 100644 --- a/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ fatal: The remote end hung up unexpectedly ``` ### 参考リンク -- 「[ユーザーをサスペンドする](/enterprise/{{ currentVersion }}/v3/enterprise-admin/users/#suspend-a-user)」 +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop.md index d0a2f3527a..9211348bb4 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop.md @@ -17,7 +17,7 @@ versions: 1. まず、 -{% data variables.product.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone. +クローンする前に、{% data variables.product.product_location %} と {% data variables.product.prodname_desktop %} にサインインします。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} 5. [**Choose...**]をクリックし、Finderウインドウを使用してリポジトリをクローンするローカルパスに移動します。 ![URLタブにあるchooseボタン](/assets/images/help/desktop/clone-choose-button-url-mac.png) @@ -36,7 +36,7 @@ versions: 1. まず、 -{% data variables.product.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone. +クローンする前に、{% data variables.product.product_location %} と {% data variables.product.prodname_desktop %} にサインインします。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} 5. **Choose...**をクリックし、Windows Explorerを使用してリポジトリをクローンするローカルパスに移動します。 ![Chooseボタン](/assets/images/help/desktop/clone-choose-button-url-win.png) diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md index e88fe761da..ff75d94a9e 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -36,23 +36,23 @@ versions: #### 部分的なコミットの作成方法 -If one file contains multiple changes, but you only want some of those changes to be included in a commit, you can create a partial commit. 追加変更やコミットできるように、他の変更はそのまま残ります。 これにより、改行の変更をコードや構文の変更から区別するなど、個別で有意義なコミットの作成が可能になります。 +1 つのファイルに複数の変更があり、それらの変更の一部のみをコミットに含める場合は、部分的なコミットを作成できます。 追加変更やコミットできるように、他の変更はそのまま残ります。 これにより、改行の変更をコードや構文の変更から区別するなど、個別で有意義なコミットの作成が可能になります。 {% note %} -**Note:** Split diff displays are currently in beta and subject to change. +**注釈:** split diff 表示は現在ベータで、変更される可能性があります。 {% endnote %} -1. To choose how your changes are displayed, in the top-right corner of the changed file, use {% octicon "gear" aria-label="The Gear icon" %} to select **Unified** or **Split**. ![Gear icon with unified and split diffs](/assets/images/help/desktop/gear-diff-select.png) -2. To exclude changed lines from your commit, click one or more changed lines so the blue disappears. The lines that are still highlighted in blue will be included in the commit. ![ファイルで選択解除された行](/assets/images/help/desktop/partial-commit.png) +1. 変更の表示方法を選択するには、変更したファイルの右上隅で、{% octicon "gear" aria-label="The Gear icon" %} を使用して [**Unified**] または [**Split**] を選択します。 ![統合および split diff のギアアイコン](/assets/images/help/desktop/gear-diff-select.png) +2. 変更した行をコミットから除外するには、変更した行を複数クリックして、青色が消えるようにします。 青色で強調表示されている行は、コミットに含まれます。 ![ファイルで選択解除された行](/assets/images/help/desktop/partial-commit.png) ### 3. 変更の廃棄 -If you have uncommitted changes that you don't want to keep, you can discard the changes. This will remove the changes from the files on your computer. You can discard all uncommitted changes in one or more files, or you can discard specific lines you added. +保持する必要がない未コミットの変更がある場合は、変更を破棄できます。 これにより、コンピュータ上のファイルから変更が削除されます。 複数のファイル内の未コミットの変更をすべて破棄することも、追加した特定の行を破棄することもできます。 -Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied. +破棄した変更は、ゴミ箱内の日付つきのファイルに保存されます。 ゴミ箱を空にするまでは、破棄した変更を復元できます。 -#### Discarding changes in one or more files +#### 複数のファイルの変更を破棄する {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -60,22 +60,22 @@ Discarded changes are saved in a dated file in the Trash. You can recover discar {% data reusables.desktop.confirm-discard-files %} ![確定ダイアログ内の [Discard Changes] ボタン](/assets/images/help/desktop/discard-changes-confirm-mac.png) -#### Discarding changes in one or more lines -You can discard one or more changed lines that are uncommitted. +#### 複数の行の変更を破棄する +未コミットの変更した複数の行を破棄できます。 {% note %} -**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. +**注釈:** 行を追加および削除する変更グループでは、単一行の破棄は無効になっています。 {% endnote %} -To discard one added line, in the list of changed lines, right click on the line you want to discard and select **Discard added line**. +追加した単一行を破棄するには、変更した行のリストで、破棄する行を右クリックし、[**Discard added line**] を選択します。 - ![Discard single line in the confirmation dialog](/assets/images/help/desktop/discard-single-line.png) + ![確認ダイアログ内の [Discard single line]](/assets/images/help/desktop/discard-single-line.png) -To discard a group of changed lines, right click the vertical bar to the right of the line numbers for the lines you want to discard, then select **Discard added lines**. +変更した行のグループを破棄するには、破棄する行の行番号の右側にある垂直バーを右クリックして、[**Discard added lines**] を選択します。 - ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) + ![確認ダイアログ内の [Discard a group of added lines]](/assets/images/help/desktop/discard-multiple-lines.png) ### 4. コミットメッセージの入力と変更のプッシュ diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md index f5004443eb..743eb57b9d 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md @@ -51,7 +51,7 @@ Issue を使用して、プロジェクトにとって重要なアイデア、 1. プルリクエストを作成するブランチに切り替えます。 詳しい情報については、「[ブランチの切り替え](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)」を参照してください。 2. **Create Pull Request**をクリックします {% data variables.product.prodname_desktop %} はデフォルトのブラウザを開いて {% data variables.product.prodname_dotcom %} に移動します。 ![[Create Pull Request] ボタン](/assets/images/help/desktop/mac-create-pull-request.png) 4. On -{% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. **compare:** ドロップダウンメニューのブランチが、変更を加えたトピックブランチであることを確認します。 +{% data variables.product.prodname_dotcom %} で、**base:** ドロップダウンメニューのブランチが変更をマージするブランチであることを確認します。 **compare:** ドロップダウンメニューのブランチが、変更を加えたトピックブランチであることを確認します。 ![ベースを選択し、ブランチを比較するドロップダウンメニュー](/assets/images/help/desktop/base-and-compare-branches.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %} @@ -63,7 +63,7 @@ Issue を使用して、プロジェクトにとって重要なアイデア、 1. プルリクエストを作成するブランチに切り替えます。 詳しい情報については、「[ブランチの切り替え](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)」を参照してください。 2. **Create Pull Request**をクリックします {% data variables.product.prodname_desktop %} はデフォルトのブラウザを開いて {% data variables.product.prodname_dotcom %} に移動します。 ![[Create Pull Request] ボタン](/assets/images/help/desktop/windows-create-pull-request.png) 3. On -{% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. **compare:** ドロップダウンメニューのブランチが、変更を加えたトピックブランチであることを確認します。 +{% data variables.product.prodname_dotcom %} で、**base:** ドロップダウンメニューのブランチが変更をマージするブランチであることを確認します。 **compare:** ドロップダウンメニューのブランチが、変更を加えたトピックブランチであることを確認します。 ![ベースを選択し、ブランチを比較するドロップダウンメニュー](/assets/images/help/desktop/base-and-compare-branches.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %} diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md index 4cb2ac5de4..edc4af0c75 100644 --- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md +++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md @@ -16,80 +16,80 @@ versions: チュートリアルを最後まで完了することをお勧めしますが、新しいリポジトリを作成することで {% data variables.product.prodname_desktop %} を学ぶ場合は、このガイドで {% data variables.product.prodname_desktop %} を使用して Git で作業する方法を説明します。 ### パート 1: {% data variables.product.prodname_desktop %} をインストールしてアカウントを認証する -You can install {% data variables.product.prodname_desktop %} on any supported operating system. After you install the app, you will need to sign in and authenticate your account on {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %} before you can create and clone a tutorial repository. +{% data variables.product.prodname_desktop %} は、サポートされている任意のオペレーティングシステムにインストールできます。 アプリをインストールした後、チュートリアルリポジトリを作成して複製する前に、{% data variables.product.prodname_dotcom %} または {% data variables.product.prodname_enterprise %} でアカウントにサインインして認証する必要があります。 -For more information on installing and authenticating, see "[Setting up {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop)." +インストールと認証の詳細については、「[{% data variables.product.prodname_desktop %} の設定](/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop)」を参照してください。 -### Part 2: Creating a new repository -If you do not have any repositories associated with {% data variables.product.prodname_desktop %}, you will see a "Let's get started!" view, where you can choose to create and clone a tutorial repository, clone an existing repository from the Internet, create a new repository, or add an existing repository from your hard drive. ![The Let's get started! screen](/assets/images/help/desktop/lets-get-started.png) +### パート 2: 新しいリポジトリを作成する +{% data variables.product.prodname_desktop %} に関連付けられたリポジトリがない場合は、「Let's get started!」ビューが表示されます。ここでは、チュートリアルリポジトリの作成と複製、インターネットからの既存のリポジトリの複製、新しいリポジトリの作成、またはハードドライブからの既存のリポジトリの追加を選択できます。 ![The Let's get started! screen](/assets/images/help/desktop/lets-get-started.png) -#### Creating and cloning a tutorial repository -We recommend that you create and clone a tutorial repository as your first project to practice using {% data variables.product.prodname_desktop %}. +#### チュートリアルリポジトリの作成とクローン +{% data variables.product.prodname_desktop %} を使用して練習する最初のプロジェクトとして、チュートリアルリポジトリを作成してクローンすることをお勧めします。 1. [**Create a tutorial repository and clone it**] をクリックします。 ![[Create and clone a tutorial repository] ボタン](/assets/images/help/desktop/getting-started-guide/create-and-clone-a-tutorial-repository.png) -2. Follow the prompts in the tutorial to install a text editor, create a branch, edit a file, make a commit, publish to {% data variables.product.prodname_dotcom %}, and open a pull request. +2. チュートリアルのプロンプトに従って、テキストエディタのインストール、ブランチの作成、ファイルの編集、コミットの作成、{% data variables.product.prodname_dotcom %} への公開、プルリクエストのオープンを行います。 #### 新しいリポジトリの作成 -If you do not wish to create and clone a tutorial repository, you can create a new repository. +チュートリアルリポジトリを作成してクローンしない場合は、新しいリポジトリを作成できます。 1. [**Create a New Repository on your Hard Drive...**] をクリックします。 ![新しいリポジトリの作成](/assets/images/help/desktop/getting-started-guide/creating-a-repository.png) -2. Fill in the fields and select your preferred options. ![リポジトリの作成オプション](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png) +2. フィールドに入力し、希望するオプションを選択します。 ![リポジトリの作成オプション](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png) - [Name] は、ローカルと {% data variables.product.product_name %} の両方で使う、リポジトリの名前を定義します。 - [Description] はオプションのフィールドで、リポジトリの目的に関する情報を提供するために使うことができます。 - [Local path] は、お手元のコンピューターにおけるリポジトリの場所を設定します。 デフォルトでは、{% data variables.product.prodname_desktop %} は _Documents_ フォルダの中に_GitHub_ フォルダを作成して、そこにリポジトリを保存しますが、保存するフォルダは任意の場所に設定可能です。 新しいリポジトリは、選択した場所の中のフォルダになります。 たとえば、リポジトリに `Tutorial` と名付けた場合、選択したローカルパスのフォルダの中に _Tutorial_ という名前のフォルダが作成されます。 {% data variables.product.prodname_desktop %} は、次に新しいリポジトリをクローンするか作成するときに、選択した場所を記憶します。 - [**Initialize this repository with a README**] は、最初のコミットを _README.md_ ファイル付きで作成します。 README は、人々がプロジェクトの目的を理解するために役立つので、これを選択して、README に役立つ情報を記載することをおすすめします。 {% data variables.product.product_name %} でリポジトリにアクセスした人は、まず README を読んで、そのプロジェクトについて知ります。 詳細は「[README について](/articles/about-readmes)」を参照してください。 - - [**Git ignore**] ドロップダウンメニューは、バージョン管理で保存したくない、ローカルリポジトリ内で無視するファイルを指定するためのカスタムファイルを追加します。 If there's a specific language or framework that you'll be using, you can select an option from the available list. まだ始めたばかりの場合は、この選択について無視して構いません。 詳細は「[ファイルを無視する](/articles/ignoring-files)」を参照してください。 + - [**Git ignore**] ドロップダウンメニューは、バージョン管理で保存したくない、ローカルリポジトリ内で無視するファイルを指定するためのカスタムファイルを追加します。 特定の言語またはフレームワークを使用する場合、利用できるリストからオプションを選択できます。 まだ始めたばかりの場合は、この選択について無視して構いません。 詳細は「[ファイルを無視する](/articles/ignoring-files)」を参照してください。 - [**License**] ドロップダウンメニューは、リポジトリの _LICENSE_ ファイルにオープンソースライセンスを追加します。 ライセンスをすぐに追加する必要はありません。 利用可能なオープンソースライセンスと、それらをリポジトリに追加する方法についての詳細は「[リポジトリのライセンス](/articles/licensing-a-repository)」を参照してください。 3. [**Create repository**] をクリックします。 -### Part 3: Exploring {% data variables.product.prodname_desktop %} -In the file menu at the top of the screen, you can access settings and actions that you can perform in {% data variables.product.prodname_desktop %}. 作業の効率化のため、ほとんどのアクションにはキーボードショートカットも設定されています。 For a full list of keyboard shortcuts, see "[Keyboard shortcuts](/desktop/getting-started-with-github-desktop/keyboard-shortcuts)." +### パート 3: {% data variables.product.prodname_desktop %} に触れる +画面上部のファイルメニューから、{% data variables.product.prodname_desktop %} で実行可能な設定や操作にアクセスできます。 作業の効率化のため、ほとんどのアクションにはキーボードショートカットも設定されています。 キーボードショートカットの一覧は「[キーボードショートカット](/desktop/getting-started-with-github-desktop/keyboard-shortcuts)」を参照してください。 -#### The {% data variables.product.prodname_desktop %} menu bar -At the top of the {% data variables.product.prodname_desktop %} app, you will see a bar that shows the current state of your repository. +#### {% data variables.product.prodname_desktop %} メニューバー +{% data variables.product.prodname_desktop %} アプリケーションの上部に、リポジトリの現在の状態を示すバーが表示されます。 - [**Current repository**] では、現在作業中のリポジトリ名が表示されます。 [**Current repository**] をクリックすると、{% data variables.product.prodname_desktop %} の別のリポジトリに切り替えることができます。 - [**Current branch**] では、作業中のブランチ名が表示されます。 [**Current branch**] をクリックすると、リポジトリ内のすべてのブランチの表示、別のブランチへの切り替え、新しいブランチの作成ができます。 リポジトリにプルリクエストを作成すると、[**Current branch**] をクリックしてプルリクエストを表示することもできます。 - - [**Publish repository**] が表示されるのは、まだリポジトリを {% data variables.product.product_name %} に公開していないためです。これについては、次のステップで扱います。 This section of the bar will change based on the status of your current branch and repository. Different context dependent actions will be available that let you exchange data between your local and remote repositories. + - [**Publish repository**] が表示されるのは、まだリポジトリを {% data variables.product.product_name %} に公開していないためです。これについては、次のステップで扱います。 バーのこのセクションは、現在のブランチとリポジトリのステータスに基づいて変更されます。 ローカルリポジトリとリモートリポジトリの間でデータを交換できるようにする、さまざまなコンテキスト依存のアクションが利用可能になります。 ![GitHub Desktop を探索する](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png) -#### Changes and History +#### 変更と履歴 左サイドバーには、[**Changes**] ビューと [**History**] ビューが表示されています。 ![The Changes and History tabs](/assets/images/help/desktop/changes-and-history.png) - - [**Changes**] ビューは、現在のブランチで変更を行い、まだローカルリポジトリにコミットしていないファイルが表示されます。 At the bottom, there is a box with "Summary" and "Description" text boxes and a **Commit to BRANCH** button. これが、新しい変更をコミットする場所です。 The **Commit to BRANCH** button is dynamic and will display which branch you're committing your changes to. ![コミットエリア](/assets/images/help/desktop/getting-started-guide/commit-area.png) + - [**Changes**] ビューは、現在のブランチで変更を行い、まだローカルリポジトリにコミットしていないファイルが表示されます。 ビューの下部には、[Summary] および [Description] テキストボックスのあるボックスと [**Commit to BRANCH**] ボタンがあります。 これが、新しい変更をコミットする場所です。 [**Commit to BRANCH**] ボタンは動的で、変更をコミットするブランチが表示されます。 ![コミットエリア](/assets/images/help/desktop/getting-started-guide/commit-area.png) - [**History**] ビューには、リポジトリの現在のブランチにおける以前のコミットが表示されます。 リポジトリを作成したときに、{% data variables.product.prodname_desktop %} によって作成された「最初のコミット」が表示されているはずです。 そのコミットの右側に、リポジトリを作成したときのオプションによっては、_.gitattributes_、_.gitignore_、_LICENSE_、_README_ ファイルが表示されているかもしれません。 各ファイルをクリックすると、そのファイルの diff が表示できます。これは、コミットでファイルに行った変更を示すものです。 diff には、ファイル全体の内容ではなく、変更を行った部分のみが表示されます。 ![[History] ビュー](/assets/images/help/desktop/getting-started-guide/history-view.png) -### Part 4: Publishing your repository to {% data variables.product.product_name %} -When you create a new repository, it only exists on your computer and you are the only one who can access the repository. You can publish your repository to {% data variables.product.product_name %} to keep it synchronized across multiple computers and allow other people to access it. To publish your repository, push your local changes to {% data variables.product.product_name %}. +### パート4: リポジトリを {% data variables.product.product_name %} に公開する +新しいリポジトリを作成する場合、そのリポジトリはコンピュータ上にのみ存在し、自分だけがアクセスできます。 リポジトリを {% data variables.product.product_name %} に公開して、複数のコンピュータ間で同期を維持し、他のユーザがアクセスできるようにすることができます。 リポジトリを公開するには、ローカルの変更を {% data variables.product.product_name %} にプッシュします。 -1. Click **Publish repository** in the menu bar. ![[Publish repository]](/assets/images/help/desktop/getting-started-guide/publish-repository.png) - - {% data variables.product.prodname_desktop %} automatically fills the "Name" and "Description" fields with the information you entered when you created the repository. - - **Keep this code private** lets you control who can view your project. If you leave this option unselected, other users on {% data variables.product.product_name %} will be able to view your code. If you select this option, your code will not be publicly available. - - The **Organization** drop-down menu, if present, lets you publish your repository to a specific organization that you belong to on {% data variables.product.product_name %}. +1. メニューバーの [**Publish repository**] をクリックします。 ![[Publish repository]](/assets/images/help/desktop/getting-started-guide/publish-repository.png) + - {% data variables.product.prodname_desktop %} は、リポジトリの作成時に入力した情報を [Name] フィールドと [Description] フィールドに自動的に入力します。 + - [**Keep this code private**] を使用すると、プロジェクトを表示できるユーザを制御できます。 このオプションを選択していない場合、{% data variables.product.product_name %} の他のユーザがあなたのコードを表示できるようになります。 このオプションを選択すると、コードは公開されなくなります。 + - [**Organization**] ドロップダウンメニューがある場合は、{% data variables.product.product_name %} で所属している特定の Organization にリポジトリを公開できます。 ![[Publish repository] のステップ](/assets/images/help/desktop/getting-started-guide/publish-repository-steps.png) 2. **Publish Repository**ボタンをクリックします。 3. {% data variables.product.prodname_desktop %} から {% data variables.product.prodname_dotcom_the_website %} のリポジトリにアクセスできます。 ファイルメニューで、[**Repository**] をクリックしてから [**View on GitHub**] をクリックしてください。 デフォルトブラウザで、リポジトリに直接移動します。 -### Part 5: Making, committing, and pushing changes -Now that you've created and published your repository, you're ready to make changes to your project and start crafting your first commit to your repository. +### パート 5: 変更の作成、コミット、プッシュ +これまでの手順でリポジトリを作成して公開したら、プロジェクトに変更を加えて、リポジトリへの最初のコミットを作成することができます。 -1. To launch your external editor from within {% data variables.product.prodname_desktop %}, click **Repository**, then click **Open in EDITOR**. For more information, see "[Configuring a default editor](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)." ![[Open in editor]](/assets/images/help/desktop/getting-started-guide/open-in-editor.png) +1. {% data variables.product.prodname_desktop %} 内から外部エディタを起動するには、[**Repository**] をクリックしてから [**Open in EDITOR**] をクリックします。 詳しい情報については、「[デフォルトエディタを設定する](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)」を参照してください。 ![[Open in editor]](/assets/images/help/desktop/getting-started-guide/open-in-editor.png) -2. Make some changes to the _README.md_ file that you previously created. You can add information that describes your project, like what it does and why it is useful. When you are satisfied with your changes, save them in your text editor. -3. In {% data variables.product.prodname_desktop %}, navigate to the **Changes** view. ファイルのリストに、_README.md_ が表示されているはずです。 The checkmark to the left of the _README.md_ file indicates that the changes you've made to the file will be part of the commit you make. 今後、複数のファイルに変更を行って、そのうちの一部のファイルのみの変更をコミットしたい場合があるかもしれません。 If you click the checkmark next to a file, that file will not be included in the commit. ![変更を表示する](/assets/images/help/desktop/getting-started-guide/viewing-changes.png) +2. 以前作成した _README.md_ ファイルにいくつかの変更を加えます。 何を行うのか、なぜ役立つのかなど、プロジェクトを説明する情報を追加できます。 変更が完了したら、テキストエディタに保存します。 +3. {% data variables.product.prodname_desktop %} で、[**Changes**] ビューに移動します。 ファイルのリストに、_README.md_ が表示されているはずです。 _README.md_ ファイルの左側にあるチェックマークは、ファイルに加えた変更がコミットの一部になることを示しています。 今後、複数のファイルに変更を行って、そのうちの一部のファイルのみの変更をコミットしたい場合があるかもしれません。 ファイルの横にあるチェックマークをクリックすると、そのファイルはコミットに含まれません。 ![変更を表示する](/assets/images/help/desktop/getting-started-guide/viewing-changes.png) -4. [**Changes**] リストの下に、コミットメッセージを入力します。 プロフィール画像の右側で、コミットについて簡潔な説明を入力します。 ここでは _README.md_ ファイルを変更するので、「プロジェクトの目的について情報を追加する」などがコミットの要約として良いかもしれません。 Below the summary, you'll see a "Description" text field where you can type a longer description of the changes in the commit, which is helpful when looking back at the history of a project and understanding why changes were made. 今は _README.md_ ファイルの基本的な更新を行っているところなので、この内容は飛ばしてもかまいません。 ![コミットメッセージ](/assets/images/help/desktop/getting-started-guide/commit-message.png) -5. Click **Commit to BRANCH NAME**. The commit button shows your current branch so you can be sure to commit to the branch you want. ![Commit to branch](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) +4. [**Changes**] リストの下に、コミットメッセージを入力します。 プロフィール画像の右側で、コミットについて簡潔な説明を入力します。 ここでは _README.md_ ファイルを変更するので、「プロジェクトの目的について情報を追加する」などがコミットの要約として良いかもしれません。 概要の下に、コミットの変更詳しい説明を入力できる [Description] テキストフィールドが表示されます。これは、プロジェクトの履歴を振り返ったり、変更理由を確認するときに役立ちます。 今は _README.md_ ファイルの基本的な更新を行っているところなので、この内容は飛ばしてもかまいません。 ![コミットメッセージ](/assets/images/help/desktop/getting-started-guide/commit-message.png) +5. [**Commit to BRANCH NAME**] をクリックします。 コミットボタンには現在のブランチが表示されるので、必要なブランチに確実にコミットできます。 ![Commit to branch](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) 6. 変更を {% data variables.product.product_name %} のリモートリポジトリにプッシュするには、[**Push origin**] をクリックします。 ![[Push origin]](/assets/images/help/desktop/getting-started-guide/push-to-origin.png) - - The **Push origin** button is the same one that you clicked to publish your repository to {% data variables.product.product_name %}. This button changes contextually based on where you are at in the Git workflow. It should now say `Push origin` with a `1` next to it, indicating that there is one commit that has not been pushed up to {% data variables.product.product_name %}. - - The "origin" in **Push origin** means that you are pushing changes to the remote called `origin`, which in this case is your project's repository on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.product_name %} に何か新しいコミットをプッシュするまで、お手元のコンピューターにあるプロジェクトのリポジトリと、{% data variables.product.prodname_dotcom_the_website %} にあるプロジェクトのリポジトリには違いがあります。 This allows you to work locally and only push your changes to {% data variables.product.prodname_dotcom_the_website %} when you're ready. -7. In the window to the right of the **Changes** view, you'll see suggestions for actions you can do next. To open the repository on {% data variables.product.product_name %} in your browser, click **View on {% data variables.product.product_name %}**. ![Available actions](/assets/images/help/desktop/available-actions.png) -8. ブラウザで、[**2 commits**] をクリックします。 {% data variables.product.product_name %} にあるリポジトリの、コミットのリストが表示されます。 The first commit should be the commit you just made in {% data variables.product.prodname_desktop %}. ![2 つのコミットをクリック](/assets/images/help/desktop/getting-started-guide/click-two-commits.png) + - [**Push origin**] ボタンは、リポジトリを {% data variables.product.product_name %} に公開する際にクリックしたボタンと同じです。 このボタンは、Git ワークフローの現在の場所に基づいてコンテキストが変わります。 ボタンが `Push origin` に変わり、横に `1` と表示されます。これは、{% data variables.product.product_name %} にプッシュされていないコミットが 1 つあることを示しています。 + - **Push origin** の「origin」は、`origin` というリモートに変更をプッシュしていることを示しています。この場合は、{% data variables.product.prodname_dotcom_the_website %} 上のプロジェクトのリポジトリです。 {% data variables.product.product_name %} に何か新しいコミットをプッシュするまで、お手元のコンピューターにあるプロジェクトのリポジトリと、{% data variables.product.prodname_dotcom_the_website %} にあるプロジェクトのリポジトリには違いがあります。 これにより、ローカルで作業し、準備ができたときにのみ変更を {% data variables.product.prodname_dotcom_the_website %} にプッシュできます。 +7. [**Changes**] ビューの右側のウィンドウに、次に実行可能なアクションの提案が表示されます。 ブラウザで {% data variables.product.product_name %} のリポジトリを開くには、[**View on {% data variables.product.product_name %}**] をクリックします。 ![Available actions](/assets/images/help/desktop/available-actions.png) +8. ブラウザで、[**2 commits**] をクリックします。 {% data variables.product.product_name %} にあるリポジトリの、コミットのリストが表示されます。 最初のコミットは、{% data variables.product.prodname_desktop %} で行ったコミットである必要があります。 ![2 つのコミットをクリック](/assets/images/help/desktop/getting-started-guide/click-two-commits.png) ### おわりに -You've now created a repository, published the repository to {% data variables.product.product_name %}, made a commit, and pushed your changes to {% data variables.product.product_name %}. You can follow this same workflow when contributing to other projects that you create or collaborate on. +これで、リポジトリの作成、{% data variables.product.product_name %} へのリポジトリの公開、コミットの実行、{% data variables.product.product_name %} への変更のプッシュが完了しました。 作成やコラボレーションを行う他のプロジェクトに貢献するときに、これと同じワークフローを使用することができます。 ### 参考リンク - "[Learning about Git](/github/using-git/learning-about-git)" diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md index 159e4febbb..1f2433e347 100644 --- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md +++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md @@ -1,17 +1,17 @@ --- title: GitHub Desktop を使ってみる -intro: 'Learn how to set up, authenticate, and configure {% data variables.product.prodname_desktop %} to allow you to contribute to projects directly from your machine.' +intro: '{% data variables.product.prodname_desktop %} のセットアップ、認証、構成して、自分のマシンから直接プロジェクトに貢献できるようにする方法を学びます。' miniTocMaxHeadingLevel: 4 versions: free-pro-team: '*' --- ### はじめに -{% data variables.product.prodname_desktop %} is an application that enables you to interact with {% data variables.product.prodname_dotcom %} using a GUI instead of the command line or a web browser. {% data variables.product.prodname_desktop %} は、あなたとあなたの Team が Git および {% data variables.product.prodname_dotcom %} とベストプラクティスを使用して共同開発することを推奨します。 You can use {% data variables.product.prodname_desktop %} to complete most Git commands from your desktop with visual confirmation of changes. You can push to, pull from, and clone remote repositories with {% data variables.product.prodname_desktop %}, and use collaborative tools such as attributing commits and creating pull requests. +{% data variables.product.prodname_desktop %} は、コマンドラインや Web ブラウザの代わりに GUI を使用して {% data variables.product.prodname_dotcom %} とやり取りできるようにするアプリケーションです。 {% data variables.product.prodname_desktop %} は、あなたとあなたの Team が Git および {% data variables.product.prodname_dotcom %} とベストプラクティスを使用して共同開発することを推奨します。 {% data variables.product.prodname_desktop %} を使用すると、変更を視覚的に確認して、デスクトップからほとんどの Git コマンドを完了できます。 {% data variables.product.prodname_desktop %} を使用してリモートリポジトリにプッシュ、プル、およびクローンを作成し、コミットの関連付けやプルリクエストの作成などのコラボレーションツールを使用できます。 -This guide will help you get started with {% data variables.product.prodname_desktop %} by setting up the application, authenticating your account, configuring basic settings, and introducing the fundamentals of managing projects with {% data variables.product.prodname_desktop %}. You will be able to use {% data variables.product.prodname_desktop %} to collaborate on projects and connect to remote repositories after working through this guide. +このガイドは、アプリケーションのセットアップ、アカウントの認証、基本設定の構成、および {% data variables.product.prodname_desktop %} を使用したプロジェクト管理の基本を紹介しており、{% data variables.product.prodname_desktop %} の使用開始の際に役立ちます。 このガイドを実行すると、{% data variables.product.prodname_desktop %} を使用してプロジェクトでコラボレーションを行い、リモートリポジトリに接続できるようになります。 -You might find it helpful to have a basic understanding of Git and {% data variables.product.prodname_dotcom %} before getting started with {% data variables.product.prodname_desktop %}. For more information, see the following articles. +{% data variables.product.prodname_desktop %} を始める前に、Git と {% data variables.product.prodname_dotcom %} の基本を理解しておくと便利です。 詳しい情報については、次の記事を参照してください。 - "[Learning about Git](/github/using-git/learning-about-git)" - "[Learning about {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" @@ -20,7 +20,7 @@ You might find it helpful to have a basic understanding of Git and {% data varia {% data variables.product.prodname_desktop %} is an open source project. You can see the roadmap, contribute to the project, or open an issue to provide feedback or feature requests. For more information, see the [`desktop/desktop`](https://github.com/desktop/desktop) repository. ### Part 1: Installing and authenticating -You can install {% data variables.product.prodname_desktop %} on any supported operating system. For more information, see "[Supported operating systems](/desktop/getting-started-with-github-desktop/supported-operating-systems)." +{% data variables.product.prodname_desktop %} は、サポートされている任意のオペレーティングシステムにインストールできます。 For more information, see "[Supported operating systems](/desktop/getting-started-with-github-desktop/supported-operating-systems)." To install {% data variables.product.prodname_desktop %}, visit the download page for [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). 詳しい情報については「[{% data variables.product.prodname_desktop %}のインストール](/desktop/installing-and-configuring-github-desktop/installing-github-desktop)」を参照してください。 diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-github-desktop.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-github-desktop.md index 70701385e8..c8374bc1dc 100644 --- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-github-desktop.md +++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-github-desktop.md @@ -14,11 +14,11 @@ versions: {% windows %} -If you are a network administrator, you can deploy {% data variables.product.prodname_desktop %} to computers running Windows on an Active Directory-managed network by using the Windows Installer package file (`.msi`) with Group Policy or another remote installation system. +ネットワーク管理者は、グループポリシーまたは別のリモートインストールシステムで Windows インストーラーパッケージファイル (`.msi`) を使用して、Active Directory 管理のネットワーク上でWindowsを実行しているコンピューターに {% data variables.product.prodname_desktop %} を展開できます。 -The Windows Installer package extracts the standalone installer (`.exe`) and configures Windows to install {% data variables.product.prodname_desktop %} the next time a user signs in to their workstation. ユーザがユーザディレクトリに{% data variables.product.prodname_desktop %}をインストールするには、権限が必要です。 +Windows インストーラーパッケージは、単独のインストーラー (`.exe`) を抽出し、ユーザが次にワークステーションにサインインしたときに {% data variables.product.prodname_desktop %} をインストールされるように Windows を設定します。 ユーザがユーザディレクトリに{% data variables.product.prodname_desktop %}をインストールするには、権限が必要です。 -If a user runs the Windows Installer package for {% data variables.product.prodname_desktop %} directly, to complete the installation, the user must sign out of their workstation and then sign back in. +ユーザが {% data variables.product.prodname_desktop %} の Windows インストーラーパッケージを直接実行する場合、インストールを完了するには、ワークステーションからサインアウトし再度サインインする必要があります。 {% endwindows %} @@ -29,10 +29,10 @@ If a user runs the Windows Installer package for {% data variables.product.prodn {% data variables.product.prodname_desktop %}は、{% data variables.desktop.mac-osx-versions %}にインストールできます。 {% data reusables.desktop.download-desktop-page %} -2. Click **Download for macOS**. ![The Download for macOS button](/assets/images/help/desktop/download-for-mac.png) -3. お使いのコンピュータの`Downloads`フォルダで、**{% data variables.product.prodname_desktop %}** zipファイルをダブルクリックします。 ![The GitHubDesktop.zip file](/assets/images/help/desktop/mac-zipfile.png) +2. [**Download for macOS**] をクリックします。 ![[Download for macOS] ボタン](/assets/images/help/desktop/download-for-mac.png) +3. お使いのコンピュータの`Downloads`フォルダで、**{% data variables.product.prodname_desktop %}** zipファイルをダブルクリックします。 ![[GitHubDesktop.zip] ファイル](/assets/images/help/desktop/mac-zipfile.png) 4. ファイルが解凍された後、**{% data variables.product.prodname_desktop %}**をダブルクリックします。 -5. {% data variables.product.prodname_desktop %} will launch after installation is complete. +5. インストールが完了すると、{% data variables.product.prodname_desktop %} が起動します。 {% endmac %} @@ -47,8 +47,8 @@ If a user runs the Windows Installer package for {% data variables.product.prodn {% endwarning %} {% data reusables.desktop.download-desktop-page %} -2. Click **Download for Windows**. ![The Download for Windows button](/assets/images/help/desktop/download-for-windows.png) -3. In your computer's `Downloads` folder, double-click the **{% data variables.product.prodname_desktop %}** setup file. ![The GitHubDesktopSetup file](/assets/images/help/desktop/windows-githubdesktopsetup.png) -4. {% data variables.product.prodname_desktop %} will launch after installation is complete. +2. [**Download for Windows**] をクリックします。 ![[Download for Windows] ボタン](/assets/images/help/desktop/download-for-windows.png) +3. コンピューターの [`Downloads`] フォルダで、[**{% data variables.product.prodname_desktop %}**] セットアップファイルをダブルクリックします。 ![[GitHubDesktopSetup] ファイル](/assets/images/help/desktop/windows-githubdesktopsetup.png) +4. インストールが完了すると、{% data variables.product.prodname_desktop %} が起動します。 {% endwindows %} diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop.md index 6477368678..3936f63eaf 100644 --- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop.md +++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop.md @@ -10,7 +10,7 @@ versions: ### パート 1: {% data variables.product.prodname_desktop %} のインストール方法 -You can install {% data variables.product.prodname_desktop %} on any supported operating system. 詳しい情報については、「[サポートされているオペレーティングシステム](/desktop/getting-started-with-github-desktop/supported-operating-systems)」を参照してください。 +{% data variables.product.prodname_desktop %} は、サポートされている任意のオペレーティングシステムにインストールできます。 詳しい情報については、「[サポートされているオペレーティングシステム](/desktop/getting-started-with-github-desktop/supported-operating-systems)」を参照してください。 {% data variables.product.prodname_desktop %} をインストールするには、[https://desktop.github.com/](https://desktop.github.com/) に移動し、オペレーティングシステムに適したバージョンの {% data variables.product.prodname_desktop %} をダウンロードします。 プロンプトに従って、インストールを完了します。 詳しい情報については「[{% data variables.product.prodname_desktop %}のインストール](/desktop/getting-started-with-github-desktop/installing-github-desktop)」を参照してください。 @@ -37,7 +37,7 @@ Git をインストールしたら、{% data variables.product.prodname_desktop デフォルトや設定を変更して、{% data variables.product.prodname_desktop %} をニーズに合わせて調整できます。 #### デフォルトのテキストエディタを選択する -{% data variables.product.prodname_desktop %} からテキストエディタを開いて、ファイルとリポジトリを操作できます。 {% data variables.product.prodname_desktop %} は、Windows および macOS 用のさまざまなテキストエディタと統合開発環境 (IDE) をサポートしています。 {% data variables.product.prodname_desktop %} 設定でデフォルトのエディタを選択できます。 For more information, see "[Configuring a default editor](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)." +{% data variables.product.prodname_desktop %} からテキストエディタを開いて、ファイルとリポジトリを操作できます。 {% data variables.product.prodname_desktop %} は、Windows および macOS 用のさまざまなテキストエディタと統合開発環境 (IDE) をサポートしています。 {% data variables.product.prodname_desktop %} 設定でデフォルトのエディタを選択できます。 詳しい情報については、「[デフォルトエディタを設定する](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)」を参照してください。 #### テーマを選択する {% data variables.product.prodname_desktop %} には、アプリの見た目をカスタマイズする際に利用できる複数のテーマがあります。 {% data variables.product.prodname_desktop %} 設定でテーマを選択できます。 詳しい情報については、「[{% data variables.product.prodname_desktop %} のテーマを設定する](/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)」を参照してください。 diff --git a/translations/ja-JP/content/developers/apps/about-apps.md b/translations/ja-JP/content/developers/apps/about-apps.md index a99bedb059..e2c2773316 100644 --- a/translations/ja-JP/content/developers/apps/about-apps.md +++ b/translations/ja-JP/content/developers/apps/about-apps.md @@ -67,13 +67,13 @@ OAuth2 は、外部アプリケーションがパスワードにアクセスす * Team や企業を代理するアプリケーションとして {% data variables.product.prodname_oauth_app %} を構築しないでください。 {% data variables.product.prodname_oauth_app %} は単一のユーザとして認証を行うので、ある人が {% data variables.product.prodname_oauth_app %} を会社が使用するものとして作成し、その人が会社を辞めた場合は、他の人がアクセスできなくなります。{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -{% data variables.product.prodname_oauth_app %} の詳細については、「[{% data variables.product.prodname_oauth_app %} を作成する](/apps/building-oauth-apps/creating-an-oauth-app/)」および「[アプリケーションを登録する](/v3/guides/basics-of-authentication/#registering-your-app)」を参照してください。 +{% data variables.product.prodname_oauth_app %} の詳細については、「[{% data variables.product.prodname_oauth_app %} を作成する](/apps/building-oauth-apps/creating-an-oauth-app/)」および「[アプリケーションを登録する](/rest/guides/basics-of-authentication#registering-your-app)」を参照してください。 ### 個人アクセストークン [個人アクセストークン](/articles/creating-a-personal-access-token-for-the-command-line/)は、権限を[スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)で特定できる点において、[OAuth トークン](/apps/building-oauth-apps/authorizing-oauth-apps/)と機能が似ている文字列です。 また、個人アクセストークンはパスワードとも似ています。ただし、個人アクセストークンは複数所有でき、それぞれのアクセス権をいつでも取り消すことができます。 -たとえば、個人アクセストークンにリポジトリへの書き込みをできるように設定できます。 そして、リポジトリで[Issue を作成する](/v3/issues/#create-an-issue) cURL コマンドを実行するかスクリプトを記述する場合、個人アクセストークンを渡して認証します。 個人アクセストークンを環境変数として保存することで、使用のたびに入力することを避けることができます。 +たとえば、個人アクセストークンにリポジトリへの書き込みをできるように設定できます。 そして、リポジトリで[Issue を作成する](/rest/reference/issues#create-an-issue) cURL コマンドを実行するかスクリプトを記述する場合、個人アクセストークンを渡して認証します。 個人アクセストークンを環境変数として保存することで、使用のたびに入力することを避けることができます。 個人アクセストークンを使用する際は、以下に気を付けてください。 diff --git a/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md b/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md index c2a934072c..9bbb50091a 100644 --- a/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md @@ -118,13 +118,13 @@ $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github ### {% data variables.product.prodname_github_app %} として API エンドポイントにアクセスする -{% data variables.product.prodname_github_app %} の概要を取得するために使用できる REST API エンドポイントの一覧については、「[GitHub App](/v3/apps/)」を参照してください。 +{% data variables.product.prodname_github_app %} の概要を取得するために使用できる REST API エンドポイントの一覧については、「[GitHub App](/rest/reference/apps)」を参照してください。 ### インストールとして認証を行う インストールとして認証を行うと、そのインストールの API でアクションを実行できます。 インストールとして認証を行う前に、インストールアクセストークンを作成する必要があります。 インストールアクセストークンは、認証を行うため {% data variables.product.prodname_github_app %} により使用されます。 -デフォルトでは、インストールトークンのスコープは、インストールがアクセスできるすべてのリポジトリにアクセスできるよう設定されています。 `repository_ids` パラメータを使用すると、インストールアクセストークンのスコープを特定のリポジトリに限定できます。 詳細については、[アプリケーション (エンドポイント) に対するアクセストークンの作成](/v3/apps/#create-an-installation-access-token-for-an-app)を参照してください。 インストールアクセストークンは {% data variables.product.prodname_github_app %} によって設定された権限を持ち、1 時間後に期限切れになります。 +デフォルトでは、インストールトークンのスコープは、インストールがアクセスできるすべてのリポジトリにアクセスできるよう設定されています。 `repository_ids` パラメータを使用すると、インストールアクセストークンのスコープを特定のリポジトリに限定できます。 詳細については、[アプリケーション (エンドポイント) に対するアクセストークンの作成](/rest/reference/apps#create-an-installation-access-token-for-an-app)を参照してください。 インストールアクセストークンは {% data variables.product.prodname_github_app %} によって設定された権限を持ち、1 時間後に期限切れになります。 インストールアクセストークンを作成するには、[上記で生成した](#jwt-payload) JWT を API リクエストの Authorization ヘッダに含めます。 @@ -144,7 +144,7 @@ $ curl -i -X POST \ ``` {% endif %} -レスポンスには、インストールアクセストークン、有効期限、トークンの権限、およびトークンがアクセスできるリポジトリが含まれます。 レスポンスのフォーマットに関する詳しい情報については、[アプリケーション (エンドポイント) に対するアクセストークンの作成](/v3/apps/#create-an-installation-access-token-for-an-app)を参照してください。 +レスポンスには、インストールアクセストークン、有効期限、トークンの権限、およびトークンがアクセスできるリポジトリが含まれます。 レスポンスのフォーマットに関する詳しい情報については、[アプリケーション (エンドポイント) に対するアクセストークンの作成](/rest/reference/apps#create-an-installation-access-token-for-an-app)を参照してください。 インストールアクセストークンで認証を行うには、インストールアクセストークンを API リクエストの Authorization ヘッダに含めます。 @@ -168,9 +168,9 @@ $ curl -i \ ### インストールとして API エンドポイントにアクセスする -インストールアクセストークンを使用して {% data variables.product.prodname_github_app %} の概要を取得するために利用できる REST API エンドポイントの一覧については、「[利用可能なエンドポイント](/v3/apps/available-endpoints/)」を参照してください。 +インストールアクセストークンを使用して {% data variables.product.prodname_github_app %} の概要を取得するために利用できる REST API エンドポイントの一覧については、「[利用可能なエンドポイント](/rest/overview/endpoints-available-for-github-apps)」を参照してください。 -インストールに関連するエンドポイントの一覧については、「[インストール](/v3/apps/installations/)」を参照してください。 +インストールに関連するエンドポイントの一覧については、「[インストール](/rest/reference/apps#installations)」を参照してください。 ### インストールによる HTTP ベースの Git アクセス diff --git a/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md b/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md index a6447d2aac..31c9ff647b 100644 --- a/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md @@ -235,12 +235,12 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre ### 非Webアプリケーションフロー -テストのような限定的な状況では、非Web認証が利用できます。 必要な場合は、[個人アクセストークン設定ページ](/articles/creating-an-access-token-for-command-line-use)を使い、[Basic認証](/v3/auth#basic-authentication)を利用して個人アクセストークンを作成できます。 この手法を使えば、ユーザはいつでもアクセスを取り消せます。 +テストのような限定的な状況では、非Web認証が利用できます。 必要な場合は、[個人アクセストークン設定ページ](/articles/creating-an-access-token-for-command-line-use)を使い、[Basic認証](/rest/overview/other-authentication-methods#basic-authentication)を利用して個人アクセストークンを作成できます。 この手法を使えば、ユーザはいつでもアクセスを取り消せます。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**ノート:** 非Webアプリケーションフローを使ってOAuth2トークンを作成する場合で、ユーザが2要素認証を有効化しているなら[2要素認証の利用](/v3/auth/#working-with-two-factor-authentication)方法を必ず理解しておいてください。 +**ノート:** 非Webアプリケーションフローを使ってOAuth2トークンを作成する場合で、ユーザが2要素認証を有効化しているなら[2要素認証の利用](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)方法を必ず理解しておいてください。 {% endnote %} {% endif %} @@ -289,7 +289,7 @@ OAuthアプリケーションへの認可情報へリンクし、ユーザがア {% tip %} -**Tip:** OAuthアプリケーションがユーザのためにアクセスできるリソースについてさらに学ぶには、「[ユーザのためにリソースを見つける](/v3/guides/discovering-resources-for-a-user/)」を参照してください。 +**Tip:** OAuthアプリケーションがユーザのためにアクセスできるリソースについてさらに学ぶには、「[ユーザのためにリソースを見つける](/rest/guides/discovering-resources-for-a-user)」を参照してください。 {% endtip %} diff --git a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md index 67e0deca63..64d569c591 100644 --- a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -52,16 +52,16 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ ##### GitHub App Manifest のパラメータ - | 名前 | 種類 | 説明 | - | --------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------- | - | `name` | `string` | GitHub App の名前。 | - | `url` | `string` | **必須。**GitHub App のホームページ。 | - | `hook_attributes` | `オブジェクト` | GitHub App の webhook の構成。 | - | `redirect_url` | `string` | GitHub App をインストール後にユーザをリダイレクトする完全な URL。 | - | `説明` | `string` | GitHub App の説明。 | - | `public` | `boolean` | GitHub App を公開する場合には `true` に、アプリケーションの所有者のみがアクセスできるようにするには `false` を設定。 | - | `default_events` | `array` | GitHub App がサブスクライブする[イベント](/webhooks/event-payloads)のリスト。 | - | `default_permissions` | `オブジェクト` | GitHub App が必要とする[権限](/v3/apps/permissions/)のセット。 オブジェクトのフォーマットでは、キーの権限名 (`issues` など) と、値のアクセスタイプ (`write` など) を使用します。 | + | 名前 | 種類 | 説明 | + | --------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | + | `name` | `string` | GitHub App の名前。 | + | `url` | `string` | **必須。**GitHub App のホームページ。 | + | `hook_attributes` | `オブジェクト` | GitHub App の webhook の構成。 | + | `redirect_url` | `string` | GitHub App をインストール後にユーザをリダイレクトする完全な URL。 | + | `説明` | `string` | GitHub App の説明。 | + | `public` | `boolean` | GitHub App を公開する場合には `true` に、アプリケーションの所有者のみがアクセスできるようにするには `false` を設定。 | + | `default_events` | `array` | GitHub App がサブスクライブする[イベント](/webhooks/event-payloads)のリスト。 | + | `default_permissions` | `オブジェクト` | GitHub App が必要とする[権限](/rest/reference/permissions-required-for-github-apps)のセット。 オブジェクトのフォーマットでは、キーの権限名 (`issues` など) と、値のアクセスタイプ (`write` など) を使用します。 | `hook_attributes` オブジェクトは、以下のキーを持っています。 @@ -153,13 +153,13 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ #### 3. 一時コードをやり取りして、アプリケーションの構成を取得する -ハンドシェイクを完了するため、`POST` リクエストにある一時的 `code` を [GitHub App をマニフェストから作成する](/v3/apps/#create-a-github-app-from-a-manifest)エンドポイントに送信します。 このレスポンスには `id` (GitHub App ID)、`pem` (秘密鍵)、`webhook_secret` が含まれます。 GitHub はアプリケーションに対する webhook シークレットを自動的に作成します。 これらの値は、アプリケーションのサーバーの環境変数に格納できます。 たとえば、アプリケーションが [dotenv](https://github.com/bkeepers/dotenv) を使用して環境変数を格納する場合、変数をアプリケーションの `.env` ファイルに格納することになるでしょう。 +ハンドシェイクを完了するため、`POST` リクエストにある一時的 `code` を [GitHub App をマニフェストから作成する](/rest/reference/apps#create-a-github-app-from-a-manifest)エンドポイントに送信します。 このレスポンスには `id` (GitHub App ID)、`pem` (秘密鍵)、`webhook_secret` が含まれます。 GitHub はアプリケーションに対する webhook シークレットを自動的に作成します。 これらの値は、アプリケーションのサーバーの環境変数に格納できます。 たとえば、アプリケーションが [dotenv](https://github.com/bkeepers/dotenv) を使用して環境変数を格納する場合、変数をアプリケーションの `.env` ファイルに格納することになるでしょう。 GitHub App Manifest フローのこのステップを、1 時間以内に完了する必要があります。 {% note %} -**注釈:** このエンドポイントはレート制限されます。 現在のレート制限状態を確認する方法については、[レート制限](/v3/rate_limit/)を参照してください。 +**注釈:** このエンドポイントはレート制限されます。 現在のレート制限状態を確認する方法については、[レート制限](/rest/reference/rate-limit)を参照してください。 {% endnote %} @@ -170,7 +170,7 @@ GitHub App Manifest フローのこのステップを、1 時間以内に完了 POST /app-manifests/:code/conversions -エンドポイントのレスポンスに関する詳しい情報については、[マニフェストから GitHub App を作成する](/v3/apps/#create-a-github-app-from-a-manifest)を参照してください。 +エンドポイントのレスポンスに関する詳しい情報については、[マニフェストから GitHub App を作成する](/rest/reference/apps#create-a-github-app-from-a-manifest)を参照してください。 マニフェストフローの最後のステップをフローからアプリケーションを作成するユーザは、登録した GitHub App の所有者となり、そのユーザの任意の個人用リポジトリにその GitHub App をインストールできます。 所有者は、GitHub API を使用してアプリケーションを拡張したり、所有権を他のユーザに移譲したり、任意の時に削除したりできます。 @@ -191,4 +191,4 @@ GitHub App Manifest フローのこのステップを、1 時間以内に完了 #### Glitch でアプリケーションをホストする -[Probot アプリケーションのサンプル](https://glitch.com/~auspicious-aardwolf)で、[Glitch](https://glitch.com/) でアプリケーションをホストして共有する例を見ることができます。 この例では、[Checks API](/v3/checks/) を使用し、`app.yml` ファイルで、必要な Checks API イベントと権限を選択しています。 Glitch は、既存のアプリケーションを流用して独自のアプリケーションを作成 (リミックス) できるツールです。 アプリケーションをリミックスすると、アプリケーションのコピーが作成され、Glitch はそれをホストしてデプロイします。 Glitch アプリケーションのリミックスについては、「[Glitch について](https://glitch.com/about/)」を参照してください。 +[Probot アプリケーションのサンプル](https://glitch.com/~auspicious-aardwolf)で、[Glitch](https://glitch.com/) でアプリケーションをホストして共有する例を見ることができます。 この例では、[Checks API](/rest/reference/checks) を使用し、`app.yml` ファイルで、必要な Checks API イベントと権限を選択しています。 Glitch は、既存のアプリケーションを流用して独自のアプリケーションを作成 (リミックス) できるツールです。 アプリケーションをリミックスすると、アプリケーションのコピーが作成され、Glitch はそれをホストしてデプロイします。 Glitch アプリケーションのリミックスについては、「[Glitch について](https://glitch.com/about/)」を参照してください。 diff --git a/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md index b9d3d93097..99b290bb34 100644 --- a/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -49,37 +49,37 @@ versions: 以下の表にある権限名をクエリパラメータ名として、権限タイプをクエリの値として使用することで、クエリ文字列で権限を設定できます。 たとえば、`contents` のユーザインターフェースに `Read & write` 権限を設定するには、クエリ文字列に `&contents=write` を含めます。 `blocking` のユーザインターフェースに `Read-only` 権限を設定するには、クエリ文字列に `&blocking=read` を含めます。 `checks` のユーザインターフェースに `no-access` を設定するには、クエリ文字列に `checks` 権限を含めないようにします。 -| 権限 | 説明 | -| -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 権限 | 説明 | +| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Organization およびリポジトリ管理のためのさまざまなエンドポイントにアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% if currentVersion == "free-pro-team@latest" %} -| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | [Blocking Users API](/v3/users/blocking/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} -| [`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | [Checks API](/v3/checks/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| `content_references` | 「[コンテンツ添付の作成](/v3/apps/installations/#create-a-content-attachment)」エンドポイントへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | さまざまなエンドポイントにアクセス権を付与し、リポジトリのコンテンツを変更できるようにします。 `none`、`read`、`write` のいずれかです。 | +| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | [Blocking Users API](/rest/reference/users#blocking) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} +| [`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | [Checks API](/rest/reference/checks) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| `content_references` | 「[コンテンツ添付の作成](/rest/reference/apps#create-a-content-attachment)」エンドポイントへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | さまざまなエンドポイントにアクセス権を付与し、リポジトリのコンテンツを変更できるようにします。 `none`、`read`、`write` のいずれかです。 | | [`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | [Deployments API](/rest/reference/repos#deployments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | [Emails API](/v3/users/emails/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} -| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | [Followers API](/v3/users/followers/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | [GPG Keys API](/v3/users/gpg_keys/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | [Issues API](/v3/issues/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | [Public Keys API](/v3/users/keys/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | [Emails API](/rest/reference/users#emails) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} +| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | [Followers API](/rest/reference/users#followers) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | [GPG Keys API](/rest/reference/users#gpg-keys) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | [Issues API](/rest/reference/issues) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | [Public Keys API](/rest/reference/users#keys) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Organization のメンバーへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% if currentVersion == "free-pro-team@latest" %} -| [`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | 機密データを漏洩しない、読み取り専用のエンドポイントへのアクセス権を付与します。 `read`、`none` のいずれかです。 {% data variables.product.prodname_github_app %} に何らかの権限を設定した場合、デフォルトは `read` となり、権限を指定しなかった場合、デフォルトは `none` となります。 | -| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | 「[Organization の更新](/v3/orgs/#update-an-organization)」エンドポイントと、[Organization Interaction Restrictions API](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | [Organization Webhooks API](/rest/reference/orgs#webhooks/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| `organization_plan` | 「[Organization の取得](/v3/orgs/#get-an-organization)」エンドポイントを使用して Organization のプランについての情報を取得するためのアクセス権を付与します。 `none`、`read` のいずれかです。 | -| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | [Projects API](/v3/projects/) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。{% if currentVersion == "free-pro-team@latest" %} -| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | [Blocking Organization Users API](/v3/orgs/blocking/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} -| [`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | [Pages API](/rest/reference/repos#pages) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| `plan` | 「[ユーザの取得](/v3/users/#get-a-user)」エンドポイントを使用してユーザの GitHub プランについての情報を取得するためのアクセス権を付与します。 `none`、`read` のいずれかです。 | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | さまざまなプルリクエストエンドポイントへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | [Repository Webhooks API](/v3/repos/hooks/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | [Projects API](/v3/projects/) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。 | -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | [Contents API](/v3/repos/contents/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | [Starring API](/v3/activity/starring/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | [Statuses API](/v3/repos/statuses/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | [Team Discussions API](/v3/teams/discussions/) および [Team Discussion Comments API](/v3/teams/discussion_comments/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| `vulnerability_alerts` | リポジトリ内の脆弱性のある依存関係に対するセキュリティアラートを受信するためのアクセス権を付与します。 詳細は「[脆弱性のある依存関係に対するセキュリティアラートについて](/articles/about-security-alerts-for-vulnerable-dependencies)」を参照。 `none`、`read` のいずれかです。 | -| `Watch` | リストへのアクセス権を付与し、ユーザがサブスクライブするリポジトリの変更を許可します。 `none`、`read`、`write` のいずれかです。 | +| [`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | 機密データを漏洩しない、読み取り専用のエンドポイントへのアクセス権を付与します。 `read`、`none` のいずれかです。 {% data variables.product.prodname_github_app %} に何らかの権限を設定した場合、デフォルトは `read` となり、権限を指定しなかった場合、デフォルトは `none` となります。 | +| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | 「[Organization の更新](/rest/reference/orgs#update-an-organization)」エンドポイントと、[Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | [Organization Webhooks API](/rest/reference/orgs#webhooks/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| `organization_plan` | 「[Organization の取得](/rest/reference/orgs#get-an-organization)」エンドポイントを使用して Organization のプランについての情報を取得するためのアクセス権を付与します。 `none`、`read` のいずれかです。 | +| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | [Projects API](/rest/reference/projects) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。{% if currentVersion == "free-pro-team@latest" %} +| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | [Blocking Organization Users API](/rest/reference/orgs#blocking) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} +| [`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | [Pages API](/rest/reference/repos#pages) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| `plan` | 「[ユーザの取得](/rest/reference/users#get-a-user)」エンドポイントを使用してユーザの GitHub プランについての情報を取得するためのアクセス権を付与します。 `none`、`read` のいずれかです。 | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | さまざまなプルリクエストエンドポイントへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | [Repository Webhooks API](/rest/reference/repos#hooks) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | [Projects API](/rest/reference/projects) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。 | +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | [Contents API](/rest/reference/repos#contents) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | [Starring API](/rest/reference/activity#starring) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | [Statuses API](/rest/reference/repos#statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | [Team Discussions API](/rest/reference/teams#discussions) および [Team Discussion Comments API](/rest/reference/teams#discussion-comments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| `vulnerability_alerts` | リポジトリ内の脆弱性のある依存関係に対するセキュリティアラートを受信するためのアクセス権を付与します。 詳細は「[脆弱性のある依存関係に対するセキュリティアラートについて](/articles/about-security-alerts-for-vulnerable-dependencies)」を参照。 `none`、`read` のいずれかです。 | +| `Watch` | リストへのアクセス権を付与し、ユーザがサブスクライブするリポジトリの変更を許可します。 `none`、`read`、`write` のいずれかです。 | ### {% data variables.product.prodname_github_app %} webhook イベント diff --git a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 6a9386ff94..0f0f89156e 100644 --- a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### はじめに -このガイドでは、[Github App](/apps/) と [Checks API](/v3/checks/) について紹介します。Checks API は、テストを実行する継続的インテグレーション (CI) サーバーを構築するために使用します。 +このガイドでは、[Github App](/apps/) と [Checks API](/rest/reference/checks) について紹介します。Checks API は、テストを実行する継続的インテグレーション (CI) サーバーを構築するために使用します。 CI とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの発生が早くなり、開発者がエラーの原因を見つけようとしてデバッグする必要性も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 開発者がコードの記述にばかり時間をとられ、エラーのデバッグやマージコンフリクトの解決にかける時間が少ないときに威力を発揮します。 🙌 @@ -22,21 +22,21 @@ CI サーバーは、コードの文法チェッカー (スタイルフォーマ #### Checks API の概要 -[Checks API](/v3/checks/) を使用すると、リポジトリでコミットされている各コードに対して自動的に実行される CI テストを設定できます。 Checks API は、プルリクエストの [**Checks**] タブにおいて、各チェックについての詳細情報をレポートします。 Checks API を使用すると、コードの特定の行に対して追加的な情報を含むアノテーションを作成できます。 アノテーションは [**Checks**] タブに表示されます。 プルリクエストの一部であるファイルに対してアノテーションを作成すると、そのアノテーションは [**Files changed**] タブにも表示されます。 +[Checks API](/rest/reference/checks) を使用すると、リポジトリでコミットされている各コードに対して自動的に実行される CI テストを設定できます。 Checks API は、プルリクエストの [**Checks**] タブにおいて、各チェックについての詳細情報をレポートします。 Checks API を使用すると、コードの特定の行に対して追加的な情報を含むアノテーションを作成できます。 アノテーションは [**Checks**] タブに表示されます。 プルリクエストの一部であるファイルに対してアノテーションを作成すると、そのアノテーションは [**Files changed**] タブにも表示されます。 -_チェックスイート_とは、 _チェック実行_ (個々の CI テスト) をグループ化したものです。 チェックスイートにもチェック実行にも_ステータス_が含まれており、GitHub のプルリクエストで表示できます。 ステータスを使用して、コードコミットがエラーを発生させるタイミングを決定できます。 これらのステータスを[保護されたブランチ](/v3/repos/branches/)で使用すると、プルリクエストを早まってマージすることを防げます。 詳細は「[ステータスチェック必須の有効化](/articles/enabling-required-status-checks/)」を参照してください。 +_チェックスイート_とは、 _チェック実行_ (個々の CI テスト) をグループ化したものです。 チェックスイートにもチェック実行にも_ステータス_が含まれており、GitHub のプルリクエストで表示できます。 ステータスを使用して、コードコミットがエラーを発生させるタイミングを決定できます。 これらのステータスを[保護されたブランチ](/rest/reference/repos#branches)で使用すると、プルリクエストを早まってマージすることを防げます。 詳細は「[ステータスチェック必須の有効化](/articles/enabling-required-status-checks/)」を参照してください。 -Checks API は、新しいコードがリポジトリにプッシュされるたびに、リポジトリにインストールされている全ての GitHub App に [`check_suite` webhook イベント](/webhooks/event-payloads/#check_suite)を送信します。 Checks API イベントの全てのアクションを受信するには、アプリケーションに `checks:write` 権限が必要です。 GitHub はデフォルトのフローを使ってリポジトリの新しいコードのコミットに `check_suite` イベントを自動的に作成しますが、[チェックスイートのためのリポジトリプリファレンスの更新](/v3/checks/suites/#update-repository-preferences-for-check-suites)を行っても構いません。 デフォルトのフローは以下の通りです。 +Checks API は、新しいコードがリポジトリにプッシュされるたびに、リポジトリにインストールされている全ての GitHub App に [`check_suite` webhook イベント](/webhooks/event-payloads/#check_suite)を送信します。 Checks API イベントの全てのアクションを受信するには、アプリケーションに `checks:write` 権限が必要です。 GitHub はデフォルトのフローを使ってリポジトリの新しいコードのコミットに `check_suite` イベントを自動的に作成しますが、[チェックスイートのためのリポジトリプリファレンスの更新](/rest/reference/checks#update-repository-preferences-for-check-suites)を行っても構いません。 デフォルトのフローは以下の通りです。 1. 誰かがリポジトリにコードをプッシュすると、GitHubは、`checks:write` 権限を持つ、リポジトリにインストールされている全ての GitHub Apps に `requested` のアクションと共に `check_suite` イベントを送信します。 このイベントにより、コードがプッシュされたことと、GitHub が新しいチェックスイートを自動的に作成したことがアプリケーションに通知されます。 -1. アプリケーションがこのイベントを受信すると、アプリケーションはスイートに[チェック実行を追加](/v3/checks/runs/#create-a-check-run)できます。 -1. チェック実行には、コードの特定の行で表示される[アノテーション](/v3/checks/runs/#annotations-object)を含めることができます。 +1. アプリケーションがこのイベントを受信すると、アプリケーションはスイートに[チェック実行を追加](/rest/reference/checks#create-a-check-run)できます。 +1. チェック実行には、コードの特定の行で表示される[アノテーション](/rest/reference/checks#annotations-object)を含めることができます。 **このガイドでは、次のこと行う方法について学びます。** * パート 1: Checks API を使用して CI サーバー用のフレームワークをセットアップする。 * Checks API イベントを受信するサーバーとして GitHub App を構成します。 - * Create new check runs for CI tests when a repository receives newly pushed commits. + * 新たにプッシュされたコミットをリポジトリが受信した時に、CI テスト用の新しいチェック実行を作成します。 * Re-run check runs when a user requests that action on GitHub. * パート 2: 文法チェッカー CI テストを追加して、作成した CI サーバーフレームワークを基に構築する。 * Update a check run with a `status`, `conclusion`, and `output` details. @@ -49,7 +49,7 @@ Checks API は、新しいコードがリポジトリにプッシュされるた ### 必要な環境 -以下の作業に取りかかる前に、[Github Apps](/apps/)、[webhook](/webhooks)、[Checks API](/v3/checks/) を使い慣れていない場合は、ある程度慣れておくとよいでしょう。 [REST API ドキュメント](/v3/)には、さらに API が掲載されています。 Checks API は [GraphQL](/v4/) でも使用できますが、このクイックスタートでは REST に焦点を当てます。 詳細については、GraphQL [Checks Suite](/v4/object/checksuite/) および [Check Run](/v4/object/checkrun/) オブジェクトを参照してください。 +以下の作業に取りかかる前に、[Github Apps](/apps/)、[webhook](/webhooks)、[Checks API](/rest/reference/checks) を使い慣れていない場合は、ある程度慣れておくとよいでしょう。 [REST API ドキュメント](/rest)には、さらに多くの API が掲載されています。 Checks API は [GraphQL](/graphql) でも使用できますが、このクイックスタートでは REST に焦点を当てます。 詳細については、GraphQL [Checks Suite](/graphql/reference/objects#checksuite) および [Check Run](/graphql/reference/objects#checkrun) オブジェクトを参照してください。 [Ruby プログラミング言語](https://www.ruby-lang.org/en/)、[Smee](https://smee.io/) webhook ペイロード配信サービス、GitHub REST API 用の [Octokit.rb Ruby ライブラリ](http://octokit.github.io/octokit.rb/)、および [Sinatra ウェブフレームワーク](http://sinatrarb.com/) を使用して、Checks API CI サーバーアプリケーションを作成します。 @@ -140,7 +140,7 @@ GitHub が送信する全てのイベントには、`HTTP_X_GITHUB_EVENT` とい def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -159,7 +159,7 @@ end def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -175,7 +175,7 @@ end ``` {% endif %} -このコードは [HTTP `POST` メソッド](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method)を使用して、「[チェック実行の作成](/v3/checks/runs/#create-a-check-run)」エンドポイントを呼び出します。 このメソッドは、エンドポイントの URL とメソッドの入力パラメータという 2 つのパラメータを取ります。 +このコードは [HTTP `POST` メソッド](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method)を使用して、「[チェック実行の作成](/rest/reference/checks#create-a-check-run)」エンドポイントを呼び出します。 このメソッドは、エンドポイントの URL とメソッドの入力パラメータという 2 つのパラメータを取ります。 チェック実行を作成するために必要なのは、`name` と `head_sha` の 2 つの入力パラメータのみです。 このクイックスタートでは、後で [Rubocop](https://rubocop.readthedocs.io/en/latest/) を使用して CI テストを実装します。そのため、ここでは「Octo Rubocop」という名前を使っていますが、チェック実行には任意の名前を選ぶことができます。 @@ -240,7 +240,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -276,7 +276,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -305,11 +305,11 @@ end ``` {% endif %} -上記のコードは、ジェネリックな [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method)メソッドを使用して「[チェック実行を更新する](/v3/checks/runs/#update-a-check-run)」API エンドポイントを呼び出し、既に作成したチェック実行を更新します。 +上記のコードは、ジェネリックな [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method)メソッドを使用して「[チェック実行を更新する](/rest/reference/checks#update-a-check-run)」API エンドポイントを呼び出し、既に作成したチェック実行を更新します。 このコードがしていることを説明しましょう。 まず、チェック実行のステータスを `in_progress` に更新し、`started_at` の時刻を現在の時刻に設定します。 このクイックスタートの[パート 2](#part-2-creating-the-octo-rubocop-ci-test)では、実際の CI テストを開始するコードを `***** RUN A CI TEST *****` の下に追加します。 今はこのセクションをプレースホルダーとして残しておきましょう。そうすると、続くコードが CI のプロセスを成功させ、すべてのテストに合格したことをシミュレートすることになります。 最後に、コードはチェック実行のステータスを再び `completed` に更新します。 -「[チェック実行を更新する](/v3/checks/runs/#update-a-check-run)」 ドキュメントに、`completed` のステータスを指定すると、`conclusion` と `completed_at` のパラメータが必須となることが書かれています。 `conclusion` はチェック実行の結果を要約するもので、`success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` のいずれかになります。 この結果 (conclusion) は `success` に、`completed_at` の時刻は現在の時刻に、ステータスは `completed` に設定します。 +You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. `conclusion` はチェック実行の結果を要約するもので、`success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` のいずれかになります。 この結果 (conclusion) は `success` に、`completed_at` の時刻は現在の時刻に、ステータスは `completed` に設定します。 チェックが行っていることについてより詳しく指定することもできますが、それは次のセクションで行うことにします。 では、`template_server.rb` を実行して、このコードを再びテストしましょう。 @@ -435,7 +435,7 @@ clone_repository(full_repo_name, repository, head_sha) ### ステップ 2.3. RuboCop を実行する -これでうまくいきました。 You're cloning the repository and creating check runs using your CI server. それではいよいよ [RuboCop 文法チェッカー](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) と [Checks API アノテーション](/v3/checks/runs/#create-a-check-run)の核心に迫ります。 +これでうまくいきました。 You're cloning the repository and creating check runs using your CI server. それではいよいよ [RuboCop 文法チェッカー](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) と [Checks API アノテーション](/rest/reference/checks#create-a-check-run)の核心に迫ります。 次のコードは、RuboCop を実行し、スタイル コード エラーを JSON フォーマットで保存します。 Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. @@ -523,11 +523,11 @@ $ ruby template_server.rb `@output` 変数には、RuboCop レポートの解析済み JSON の結果が含まれています。 上記で示す通り、結果には `summary` セクションが含まれており、コードでエラーがあるかどうかを迅速に判断するために使用できます。 以下のコードは、報告されたエラーがない場合に、チェック実行の結果を `success` に設定します。 RuboCop は、`files` 配列内にある各ファイルについてエラーを報告します。エラーがある場合、ファイル オブジェクトからデータを抽出する必要があります。 -Checks API により、コードの特定の行に対してアノテーションを作成することができます。 チェック実行を作成または更新する際に、アノテーションを追加できます。 このクイックスタートでは、アノテーションを付けて[チェック実行を更新](/v3/checks/runs/#update-a-check-run)します。 +Checks API により、コードの特定の行に対してアノテーションを作成することができます。 チェック実行を作成または更新する際に、アノテーションを追加できます。 このクイックスタートでは、アノテーションを付けて[チェック実行を更新](/rest/reference/checks#update-a-check-run)します。 -Checks API では、アノテーションの数は API の 1 リクエストあたり最大 50 に制限されています。 51 以上のアノテーションを作成するには、[チェック実行を更新する](/v3/checks/runs/#update-a-check-run)エンドポイントに複数回のリクエストを行う必要があります。 たとえば、105 のアノテーションを作成するには、[チェック実行を更新する](/v3/checks/runs/#update-a-check-run)エンドポイントを 3 回呼び出す必要があります。 始めの 2 回のリクエストでそれぞれ 50 個のアノテーションが作成され、3 回目のリクエストで残り 5 つのアノテーションが作成されます。 チェック実行を更新するたびに、アノテーションは既存のチェック実行にあるアノテーションのリストに追加されます。 +Checks API では、アノテーションの数は API の 1 リクエストあたり最大 50 に制限されています。 51 以上のアノテーションを作成するには、[チェック実行を更新する](/rest/reference/checks#update-a-check-run)エンドポイントに複数回のリクエストを行う必要があります。 たとえば、105 のアノテーションを作成するには、[チェック実行を更新する](/rest/reference/checks#update-a-check-run)エンドポイントを 3 回呼び出す必要があります。 始めの 2 回のリクエストでそれぞれ 50 個のアノテーションが作成され、3 回目のリクエストで残り 5 つのアノテーションが作成されます。 チェック実行を更新するたびに、アノテーションは既存のチェック実行にあるアノテーションのリストに追加されます。 -チェック実行は、アノテーションをオブジェクトの配列として受け取ります。 アノテーションの各オブジェクトには、`path`、`start_line`、 `end_line`、`annotation_level`、`message` を含める必要があります。 RuboCop では `start_column` および `end_column` も提供しており、これらのオプションのパラメータをアノテーションに含めることもできます。 Annotations only support `start_column` and `end_column` on the same line. 詳細については [`annotations` オブジェクト](/v3/checks/runs/#annotations-object-1)のリファレンスドキュメントを参照してください。 +チェック実行は、アノテーションをオブジェクトの配列として受け取ります。 アノテーションの各オブジェクトには、`path`、`start_line`、 `end_line`、`annotation_level`、`message` を含める必要があります。 RuboCop では `start_column` および `end_column` も提供しており、これらのオプションのパラメータをアノテーションに含めることもできます。 アノテーションは、`start_column` と `end_column` を同一の行においてのみサポートしています。 詳細については [`annotations` オブジェクト](/rest/reference/checks#annotations-object-1)のリファレンスドキュメントを参照してください。 各アノテーションを作成するために必要な RuboCop から、必須の情報を抽出します。 [前のセクション](#step-23-running-rubocop)で追加したコードに、次のコードを追加します。 @@ -536,7 +536,7 @@ annotations = [] # You can create a maximum of 50 annotations per request to the Checks # API. To add more than 50 annotations, use the "Update a check run" API # endpoint. This example code limits the number of annotations to 50. -# See /v3/checks/runs/#update-a-check-run +# See /rest/reference/checks#update-a-check-run # for details. max_annotations = 50 @@ -590,7 +590,7 @@ end エラーが報告されると、上記のコードは ReboCop レポートの `files` 配列を反復処理します。 コードは各ファイルにおいてファイルパスを抽出し、アノテーションレベルを `notice` に設定します。 さらに細かく、[RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/) の各タイプに特定の警告レベルを設定することもできますが、このクイックスタートでは簡単さを優先し、すべてのエラーを `notice` のレベルに設定します。 -このコードはまた、`offenses` 配列の各エラーを反復処理し、違反の場所とエラー メッセージを収集します。 必要な情報を抽出後、コードは各エラーに対してアノテーションを作成し、それを `annotations` 配列に格納します。 Because annotations only support start and end columns on the same line, `start_column` and `end_column` are only added to the `annotation` object if the start and end line values are the same. +このコードはまた、`offenses` 配列の各エラーを反復処理し、違反の場所とエラー メッセージを収集します。 必要な情報を抽出後、コードは各エラーに対してアノテーションを作成し、それを `annotations` 配列に格納します。 アノテーションは同一行の開始列と終了列のみをサポートしているため、開始行と終了行の値が同じである場合にのみ `annotation` オブジェクトに `start_column` と `end_column` が追加されます。 このコードはまだチェック実行のアノテーションを作成しません。 それを作成するコードは、次のセクションで追加します。 @@ -694,7 +694,7 @@ updated_check_run = @installation_client.patch( さて、これで CI テストのステータスに基づいて結論を設定し、RuboCop の結果からの出力を追加しました。あなたは CI テストを作成したのです。 おめでとうございます。 🙌 -また、上記のコードは、`actions` オブジェクトを介して CI サーバーに[リクエストされたアクション](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/)という機能も追加しています。 {% if currentVersion == "free-pro-team@latest" %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}Requested actions add a button in the **Checks** tab on GitHub that allows someone to request the check run to take additional action. The additional action is completely configurable by your app. For example, because RuboCop has a feature to automatically fix the errors it finds in Ruby code, your CI server can use a requested actions button to allow people to request automatic error fixes. When someone clicks the button, the app receives the `check_run` event with a `requested_action` action. Each requested action has an `identifier` that the app uses to determine which button was clicked. +また、上記のコードは、`actions` オブジェクトを介して CI サーバーに[リクエストされたアクション](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/)という機能も追加しています。 {% if currentVersion == "free-pro-team@latest" %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}リクエストされたアクションは、追加のアクションを実行するためにチェック実行をリクエストできるボタンを GitHub の [**Checks**] タブに追加します。 The additional action is completely configurable by your app. For example, because RuboCop has a feature to automatically fix the errors it finds in Ruby code, your CI server can use a requested actions button to allow people to request automatic error fixes. When someone clicks the button, the app receives the `check_run` event with a `requested_action` action. Each requested action has an `identifier` that the app uses to determine which button was clicked. The code above doesn't have RuboCop automatically fix errors yet. You'll add that in the next section. But first, take a look at the CI test that you just created by starting up the `template_server.rb` server again and creating a new pull request: @@ -836,7 +836,7 @@ Here are a few common problems and some suggested solutions. If you run into any * **Q:** アプリケーションが GitHub にコードをプッシュしません。 I don't see the fixes that RuboCop automatically makes! - **A:** Make sure you have **Read & write** permissions for "Repository contents," and that you are cloning the repository with your installation token. See [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) for details. + **A:** Make sure you have **Read & write** permissions for "Repository contents," and that you are cloning the repository with your installation token. [ステップ 2.2. Cloning the repository](#step-22-cloning-the-repository) for details. * **Q:** I see an error in the `template_server.rb` debug output related to cloning my repository. @@ -869,4 +869,4 @@ After walking through this guide, you've learned the basics of using the Checks Here are some ideas for what you can do next: * Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors. -* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/v3/pulls/#create-a-pull-request) with a new branch based on the head branch. +* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch. diff --git a/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 7cb1f10a2b..90a725ed17 100644 --- a/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -90,10 +90,10 @@ Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to requ ### Git access -| GitHub Apps | OAuth Apps | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | -| The token is used as the HTTP password. | The token is used as the HTTP username. | +| GitHub Apps | OAuth Apps | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/repos#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | +| The token is used as the HTTP password. | The token is used as the HTTP username. | ### Machine vs. bot accounts diff --git a/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 94e9798727..12d946734b 100644 --- a/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -67,7 +67,7 @@ If the user accepts your request, GitHub redirects back to your site with a temp {% endnote %} -Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." +Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)." Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} @@ -154,7 +154,7 @@ You can also check which repositories are accessible to a user for an installati Authorization: token OAUTH-TOKEN GET /user/installations/:installation_id/repositories -More details can be found in: [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token). +More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). ### Handling a revoked GitHub App authorization @@ -162,7 +162,7 @@ If a user revokes their authorization of a GitHub App, the app will receive the ### User-level permissions -You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/v3/apps/permissions/), which are granted at the time of installation on an organization or user account. +You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account. You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." @@ -172,75 +172,75 @@ Because user-level permissions are granted on an individual user basis, you can ### User-to-server requests -While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/v4/) or [REST v3](/v3/) endpoints. +While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/graphql) or [REST v3](/rest) endpoints. #### Supported endpoints {% if currentVersion == "free-pro-team@latest" %} ##### Actions Runners -* [List runner applications for a repository](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) -* [List self-hosted runners for a repository](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) -* [Get a self-hosted runner for a repository](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) -* [Delete a self-hosted runner from a repository](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) -* [Create a registration token for a repository](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) -* [Create a remove token for a repository](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) -* [List runner applications for an organization](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) -* [List self-hosted runners for an organization](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) -* [Get a self-hosted runner for an organization](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) -* [Delete a self-hosted runner from an organization](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) -* [Create a registration token for an organization](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) -* [Create a remove token for an organization](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) +* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository) +* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization) +* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization) ##### Actions Secrets -* [Get a repository public key](/v3/actions/secrets/#get-a-repository-public-key) -* [List repository secrets](/v3/actions/secrets/#list-repository-secrets) -* [Get a repository secret](/v3/actions/secrets/#get-a-repository-secret) -* [Create or update a repository secret](/v3/actions/secrets/#create-or-update-a-repository-secret) -* [Delete a repository secret](/v3/actions/secrets/#delete-a-repository-secret) -* [Get an organization public key](/v3/actions/secrets/#get-an-organization-public-key) -* [List organization secrets](/v3/actions/secrets/#list-organization-secrets) -* [Get an organization secret](/v3/actions/secrets/#get-an-organization-secret) -* [Create or update an organization secret](/v3/actions/secrets/#create-or-update-an-organization-secret) -* [List selected repositories for an organization secret](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) -* [Set selected repositories for an organization secret](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) -* [Add selected repository to an organization secret](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) -* [Remove selected repository from an organization secret](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) -* [Delete an organization secret](/v3/actions/secrets/#delete-an-organization-secret) +* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key) +* [List repository secrets](/rest/reference/actions#list-repository-secrets) +* [Get a repository secret](/rest/reference/actions#get-a-repository-secret) +* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret) +* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret) +* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key) +* [List organization secrets](/rest/reference/actions#list-organization-secrets) +* [Get an organization secret](/rest/reference/actions#get-an-organization-secret) +* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret) +* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### 成果物 -* [List artifacts for a repository](/v3/actions/artifacts/#list-artifacts-for-a-repository) -* [List workflow run artifacts](/v3/actions/artifacts/#list-workflow-run-artifacts) -* [Get an artifact](/v3/actions/artifacts/#get-an-artifact) -* [Delete an artifact](/v3/actions/artifacts/#delete-an-artifact) -* [Download an artifact](/v3/actions/artifacts/#download-an-artifact) +* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository) +* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts) +* [Get an artifact](/rest/reference/actions#get-an-artifact) +* [Delete an artifact](/rest/reference/actions#delete-an-artifact) +* [Download an artifact](/rest/reference/actions#download-an-artifact) {% endif %} ##### チェックラン -* [Create a check run](/v3/checks/runs/#create-a-check-run) -* [Get a check run](/v3/checks/runs/#get-a-check-run) -* [Update a check run](/v3/checks/runs/#update-a-check-run) -* [List check run annotations](/v3/checks/runs/#list-check-run-annotations) -* [List check runs in a check suite](/v3/checks/runs/#list-check-runs-in-a-check-suite) -* [List check runs for a Git reference](/v3/checks/runs/#list-check-runs-for-a-git-reference) +* [Create a check run](/rest/reference/checks#create-a-check-run) +* [Get a check run](/rest/reference/checks#get-a-check-run) +* [Update a check run](/rest/reference/checks#update-a-check-run) +* [List check run annotations](/rest/reference/checks#list-check-run-annotations) +* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference) ##### チェックスイート -* [Create a check suite](/v3/checks/suites/#create-a-check-suite) -* [Get a check suite](/v3/checks/suites/#get-a-check-suite) -* [Rerequest a check suite](/v3/checks/suites/#rerequest-a-check-suite) -* [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) -* [List check suites for a Git reference](/v3/checks/suites/#list-check-suites-for-a-git-reference) +* [Create a check suite](/rest/reference/checks#create-a-check-suite) +* [Get a check suite](/rest/reference/checks#get-a-check-suite) +* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite) +* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference) ##### Codes Of Conduct -* [Get all codes of conduct](/v3/codes_of_conduct/#get-all-codes-of-conduct) -* [Get a code of conduct](/v3/codes_of_conduct/#get-a-code-of-conduct) +* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct) ##### Deployment Statuses @@ -266,128 +266,128 @@ While most of your API interaction should occur using your server-to-server inst ##### Git Blobs -* [Create a blob](/v3/git/blobs/#create-a-blob) -* [Get a blob](/v3/git/blobs/#get-a-blob) +* [Create a blob](/rest/reference/git#create-a-blob) +* [Get a blob](/rest/reference/git#get-a-blob) ##### Git Commits -* [Create a commit](/v3/git/commits/#create-a-commit) -* [Get a commit](/v3/git/commits/#get-a-commit) +* [Create a commit](/rest/reference/git#create-a-commit) +* [Get a commit](/rest/reference/git#get-a-commit) ##### Git Refs -* [Create a reference](/v3/git/refs/#create-a-reference)* [Get a reference](/v3/git/refs/#get-a-reference) -* [List matching references](/v3/git/refs/#list-matching-references) -* [Update a reference](/v3/git/refs/#update-a-reference) -* [Delete a reference](/v3/git/refs/#delete-a-reference) +* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference) +* [List matching references](/rest/reference/git#list-matching-references) +* [Update a reference](/rest/reference/git#update-a-reference) +* [Delete a reference](/rest/reference/git#delete-a-reference) ##### Git Tags -* [Create a tag object](/v3/git/tags/#create-a-tag-object) -* [Get a tag](/v3/git/tags/#get-a-tag) +* [Create a tag object](/rest/reference/git#create-a-tag-object) +* [Get a tag](/rest/reference/git#get-a-tag) ##### Git Trees -* [Create a tree](/v3/git/trees/#create-a-tree) -* [Get a tree](/v3/git/trees/#get-a-tree) +* [Create a tree](/rest/reference/git#create-a-tree) +* [Get a tree](/rest/reference/git#get-a-tree) ##### Gitignore Templates -* [Get all gitignore templates](/v3/gitignore/#get-all-gitignore-templates) -* [Get a gitignore template](/v3/gitignore/#get-a-gitignore-template) +* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates) +* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template) ##### Installations -* [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token) +* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} ##### Interaction Limits -* [Get interaction restrictions for an organization](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) -* [Set interaction restrictions for an organization](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) -* [Remove interaction restrictions for an organization](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) -* [Get interaction restrictions for a repository](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) -* [Set interaction restrictions for a repository](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) -* [Remove interaction restrictions for a repository](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) +* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) {% endif %} ##### Issue Assignees -* [Add assignees to an issue](/v3/issues/assignees/#add-assignees-to-an-issue) -* [Remove assignees from an issue](/v3/issues/assignees/#remove-assignees-from-an-issue) +* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue) +* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue) ##### Issue Comments -* [List issue comments](/v3/issues/comments/#list-issue-comments) -* [Create an issue comment](/v3/issues/comments/#create-an-issue-comment) -* [List issue comments for a repository](/v3/issues/comments/#list-issue-comments-for-a-repository) -* [Get an issue comment](/v3/issues/comments/#get-an-issue-comment) -* [Update an issue comment](/v3/issues/comments/#update-an-issue-comment) -* [Delete an issue comment](/v3/issues/comments/#delete-an-issue-comment) +* [List issue comments](/rest/reference/issues#list-issue-comments) +* [Create an issue comment](/rest/reference/issues#create-an-issue-comment) +* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository) +* [Get an issue comment](/rest/reference/issues#get-an-issue-comment) +* [Update an issue comment](/rest/reference/issues#update-an-issue-comment) +* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment) ##### Issue Events -* [List issue events](/v3/issues/events/#list-issue-events) +* [List issue events](/rest/reference/issues#list-issue-events) ##### Issue Timeline -* [List timeline events for an issue](/v3/issues/timeline/#list-timeline-events-for-an-issue) +* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue) ##### 問題 -* [List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user) -* [List assignees](/v3/issues/assignees/#list-assignees) -* [Check if a user can be assigned](/v3/issues/assignees/#check-if-a-user-can-be-assigned) -* [List repository issues](/v3/issues/#list-repository-issues) -* [Issue を作成します](/v3/issues/#create-an-issue) -* [Get an issue](/v3/issues/#get-an-issue) -* [Update an issue](/v3/issues/#update-an-issue) -* [Lock an issue](/v3/issues/#lock-an-issue) -* [Unlock an issue](/v3/issues/#unlock-an-issue) +* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [List assignees](/rest/reference/issues#list-assignees) +* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [List repository issues](/rest/reference/issues#list-repository-issues) +* [Issue を作成します](/rest/reference/issues#create-an-issue) +* [Get an issue](/rest/reference/issues#get-an-issue) +* [Update an issue](/rest/reference/issues#update-an-issue) +* [Lock an issue](/rest/reference/issues#lock-an-issue) +* [Unlock an issue](/rest/reference/issues#unlock-an-issue) {% if currentVersion == "free-pro-team@latest" %} ##### Jobs -* [Get a job for a workflow run](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) -* [Download job logs for a workflow run](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) -* [List jobs for a workflow run](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) +* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run) {% endif %} ##### ラベル -* [List labels for an issue](/v3/issues/labels/#list-labels-for-an-issue) -* [Add labels to an issue](/v3/issues/labels/#add-labels-to-an-issue) -* [Set labels for an issue](/v3/issues/labels/#set-labels-for-an-issue) -* [Remove all labels from an issue](/v3/issues/labels/#remove-all-labels-from-an-issue) -* [Remove a label from an issue](/v3/issues/labels/#remove-a-label-from-an-issue) -* [List labels for a repository](/v3/issues/labels/#list-labels-for-a-repository) -* [Create a label](/v3/issues/labels/#create-a-label) -* [Get a label](/v3/issues/labels/#get-a-label) -* [Update a label](/v3/issues/labels/#update-a-label) -* [Delete a label](/v3/issues/labels/#delete-a-label) -* [Get labels for every issue in a milestone](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) +* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue) +* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue) +* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue) +* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue) +* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue) +* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository) +* [Create a label](/rest/reference/issues#create-a-label) +* [Get a label](/rest/reference/issues#get-a-label) +* [Update a label](/rest/reference/issues#update-a-label) +* [Delete a label](/rest/reference/issues#delete-a-label) +* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone) ##### ライセンス -* [Get all commonly used licenses](/v3/licenses/#get-all-commonly-used-licenses) -* [Get a license](/v3/licenses/#get-a-license) +* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses) +* [Get a license](/rest/reference/licenses#get-a-license) ##### Markdown -* [Render a Markdown document](/v3/markdown/#render-a-markdown-document) -* [Render a markdown document in raw mode](/v3/markdown/#render-a-markdown-document-in-raw-mode) +* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document) +* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) ##### メタ情報 -* [メタ情報](/v3/meta/#meta) +* [メタ情報](/rest/reference/meta#meta) ##### マイルストーン -* [List milestones](/v3/issues/milestones/#list-milestones) -* [Create a milestone](/v3/issues/milestones/#create-a-milestone) -* [Get a milestone](/v3/issues/milestones/#get-a-milestone) -* [Update a milestone](/v3/issues/milestones/#update-a-milestone) -* [Delete a milestone](/v3/issues/milestones/#delete-a-milestone) +* [List milestones](/rest/reference/issues#list-milestones) +* [Create a milestone](/rest/reference/issues#create-a-milestone) +* [Get a milestone](/rest/reference/issues#get-a-milestone) +* [Update a milestone](/rest/reference/issues#update-a-milestone) +* [Delete a milestone](/rest/reference/issues#delete-a-milestone) ##### Organization Hooks @@ -401,29 +401,29 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Organization Invitations -* [List pending organization invitations](/v3/orgs/members/#list-pending-organization-invitations) -* [Create an organization invitation](/v3/orgs/members/#create-an-organization-invitation) -* [List organization invitation teams](/v3/orgs/members/#list-organization-invitation-teams) +* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations) +* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation) +* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams) {% endif %} ##### Organization Members -* [List organization members](/v3/orgs/members/#list-organization-members) -* [Check organization membership for a user](/v3/orgs/members/#check-organization-membership-for-a-user) -* [Remove an organization member](/v3/orgs/members/#remove-an-organization-member) -* [Get organization membership for a user](/v3/orgs/members/#get-organization-membership-for-a-user) -* [Set organization membership for a user](/v3/orgs/members/#set-organization-membership-for-a-user) -* [Remove organization membership for a user](/v3/orgs/members/#remove-organization-membership-for-a-user) -* [List public organization members](/v3/orgs/members/#list-public-organization-members) -* [Check public organization membership for a user](/v3/orgs/members/#check-public-organization-membership-for-a-user) -* [Set public organization membership for the authenticated user](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) -* [Remove public organization membership for the authenticated user](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) +* [List organization members](/rest/reference/orgs#list-organization-members) +* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user) +* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member) +* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user) +* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user) +* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [List public organization members](/rest/reference/orgs#list-public-organization-members) +* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) ##### Organization Outside Collaborators -* [List outside collaborators for an organization](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) -* [Convert an organization member to outside collaborator](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) -* [Remove outside collaborator from an organization](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) +* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) {% if enterpriseServerVersions contains currentVersion %} ##### Organization Pre Receive Hooks @@ -437,198 +437,198 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Organization Team Projects -* [List team projects](/v3/teams/#list-team-projects) -* [Check team permissions for a project](/v3/teams/#check-team-permissions-for-a-project) -* [Add or update team project permissions](/v3/teams/#add-or-update-team-project-permissions) -* [Remove a project from a team](/v3/teams/#remove-a-project-from-a-team) +* [List team projects](/rest/reference/teams#list-team-projects) +* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project) +* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions) +* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team) {% endif %} ##### Organization Team Repositories -* [Team リポジトリの一覧表示](/v3/teams/#list-team-repositories) -* [Check team permissions for a repository](/v3/teams/#check-team-permissions-for-a-repository) -* [Add or update team repository permissions](/v3/teams/#add-or-update-team-repository-permissions) -* [Remove a repository from a team](/v3/teams/#remove-a-repository-from-a-team) +* [Team リポジトリの一覧表示](/rest/reference/teams#list-team-repositories) +* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository) +* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions) +* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team) {% if currentVersion == "free-pro-team@latest" %} ##### Organization Team Sync -* [List idp groups for a team](/v3/teams/team_sync/#list-idp-groups-for-a-team) -* [Create or update idp group connections](/v3/teams/team_sync/#create-or-update-idp-group-connections) -* [List IdP groups for an organization](/v3/teams/team_sync/#list-idp-groups-for-an-organization) +* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team) +* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections) +* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} ##### Organization Teams -* [List teams](/v3/teams/#list-teams) -* [Create a team](/v3/teams/#create-a-team) -* [Get a team by name](/v3/teams/#get-a-team-by-name) +* [List teams](/rest/reference/teams#list-teams) +* [Create a team](/rest/reference/teams#create-a-team) +* [Get a team by name](/rest/reference/teams#get-a-team-by-name) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -* [Get a team](/v3/teams/#get-a-team) +* [Get a team](/rest/reference/teams#get-a-team) {% endif %} -* [Update a team](/v3/teams/#update-a-team) -* [Delete a team](/v3/teams/#delete-a-team) +* [Update a team](/rest/reference/teams#update-a-team) +* [Delete a team](/rest/reference/teams#delete-a-team) {% if currentVersion == "free-pro-team@latest" %} -* [List pending team invitations](/v3/teams/members/#list-pending-team-invitations) +* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations) {% endif %} -* [List team members](/v3/teams/members/#list-team-members) -* [Get team membership for a user](/v3/teams/members/#get-team-membership-for-a-user) -* [Add or update team membership for a user](/v3/teams/members/#add-or-update-team-membership-for-a-user) -* [Remove team membership for a user](/v3/teams/members/#remove-team-membership-for-a-user) -* [List child teams](/v3/teams/#list-child-teams) -* [List teams for the authenticated user](/v3/teams/#list-teams-for-the-authenticated-user) +* [List team members](/rest/reference/teams#list-team-members) +* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user) +* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) +* [List child teams](/rest/reference/teams#list-child-teams) +* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user) ##### Organization -* [List organizations](/v3/orgs/#list-organizations) -* [Get an organization](/v3/orgs/#get-an-organization) -* [Update an organization](/v3/orgs/#update-an-organization) -* [List organization memberships for the authenticated user](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) -* [Get an organization membership for the authenticated user](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) -* [Update an organization membership for the authenticated user](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) -* [List organizations for the authenticated user](/v3/orgs/#list-organizations-for-the-authenticated-user) -* [List organizations for a user](/v3/orgs/#list-organizations-for-a-user) +* [List organizations](/rest/reference/orgs#list-organizations) +* [Get an organization](/rest/reference/orgs#get-an-organization) +* [Update an organization](/rest/reference/orgs#update-an-organization) +* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Credential Authorizations -* [List SAML SSO authorizations for an organization](/v3/orgs/#list-saml-sso-authorizations-for-an-organization) -* [Remove a SAML SSO authorization for an organization](/v3/orgs/#remove-a-saml-sso-authorization-for-an-organization) +* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Scim -* [List SCIM provisioned identities](/v3/scim/#list-scim-provisioned-identities) -* [Provision and invite a SCIM user](/v3/scim/#provision-and-invite-a-scim-user) -* [Get SCIM provisioning information for a user](/v3/scim/#get-scim-provisioning-information-for-a-user) -* [Set SCIM information for a provisioned user](/v3/scim/#set-scim-information-for-a-provisioned-user) -* [Update an attribute for a SCIM user](/v3/scim/#update-an-attribute-for-a-scim-user) -* [Delete a SCIM user from an organization](/v3/scim/#delete-a-scim-user-from-an-organization) +* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities) +* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user) +* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Source Imports -* [Get an import status](/v3/migrations/source_imports/#get-an-import-status) -* [Start an import](/v3/migrations/source_imports/#start-an-import) -* [Update an import](/v3/migrations/source_imports/#update-an-import) -* [Cancel an import](/v3/migrations/source_imports/#cancel-an-import) -* [Get commit authors](/v3/migrations/source_imports/#get-commit-authors) -* [Map a commit author](/v3/migrations/source_imports/#map-a-commit-author) -* [Get large files](/v3/migrations/source_imports/#get-large-files) -* [Update Git LFS preference](/v3/migrations/source_imports/#update-git-lfs-preference) +* [Get an import status](/rest/reference/migrations#get-an-import-status) +* [Start an import](/rest/reference/migrations#start-an-import) +* [Update an import](/rest/reference/migrations#update-an-import) +* [Cancel an import](/rest/reference/migrations#cancel-an-import) +* [Get commit authors](/rest/reference/migrations#get-commit-authors) +* [Map a commit author](/rest/reference/migrations#map-a-commit-author) +* [Get large files](/rest/reference/migrations#get-large-files) +* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference) {% endif %} ##### Project Collaborators -* [List project collaborators](/v3/projects/collaborators/#list-project-collaborators) -* [Add project collaborator](/v3/projects/collaborators/#add-project-collaborator) -* [Remove project collaborator](/v3/projects/collaborators/#remove-project-collaborator) -* [Get project permission for a user](/v3/projects/collaborators/#get-project-permission-for-a-user) +* [List project collaborators](/rest/reference/projects#list-project-collaborators) +* [Add project collaborator](/rest/reference/projects#add-project-collaborator) +* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator) +* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user) ##### プロジェクト -* [List organization projects](/v3/projects/#list-organization-projects) -* [Create an organization project](/v3/projects/#create-an-organization-project) -* [Get a project](/v3/projects/#get-a-project) -* [Update a project](/v3/projects/#update-a-project) -* [Delete a project](/v3/projects/#delete-a-project) -* [List project columns](/v3/projects/columns/#list-project-columns) -* [Create a project column](/v3/projects/columns/#create-a-project-column) -* [Get a project column](/v3/projects/columns/#get-a-project-column) -* [Update a project column](/v3/projects/columns/#update-a-project-column) -* [Delete a project column](/v3/projects/columns/#delete-a-project-column) -* [List project cards](/v3/projects/cards/#list-project-cards) -* [Create a project card](/v3/projects/cards/#create-a-project-card) -* [Move a project column](/v3/projects/columns/#move-a-project-column) -* [Get a project card](/v3/projects/cards/#get-a-project-card) -* [Update a project card](/v3/projects/cards/#update-a-project-card) -* [Delete a project card](/v3/projects/cards/#delete-a-project-card) -* [Move a project card](/v3/projects/cards/#move-a-project-card) -* [List repository projects](/v3/projects/#list-repository-projects) -* [Create a repository project](/v3/projects/#create-a-repository-project) +* [List organization projects](/rest/reference/projects#list-organization-projects) +* [Create an organization project](/rest/reference/projects#create-an-organization-project) +* [Get a project](/rest/reference/projects#get-a-project) +* [Update a project](/rest/reference/projects#update-a-project) +* [Delete a project](/rest/reference/projects#delete-a-project) +* [List project columns](/rest/reference/projects#list-project-columns) +* [Create a project column](/rest/reference/projects#create-a-project-column) +* [Get a project column](/rest/reference/projects#get-a-project-column) +* [Update a project column](/rest/reference/projects#update-a-project-column) +* [Delete a project column](/rest/reference/projects#delete-a-project-column) +* [List project cards](/rest/reference/projects#list-project-cards) +* [Create a project card](/rest/reference/projects#create-a-project-card) +* [Move a project column](/rest/reference/projects#move-a-project-column) +* [Get a project card](/rest/reference/projects#get-a-project-card) +* [Update a project card](/rest/reference/projects#update-a-project-card) +* [Delete a project card](/rest/reference/projects#delete-a-project-card) +* [Move a project card](/rest/reference/projects#move-a-project-card) +* [List repository projects](/rest/reference/projects#list-repository-projects) +* [Create a repository project](/rest/reference/projects#create-a-repository-project) ##### Pull Comments -* [List review comments on a pull request](/v3/pulls/comments/#list-review-comments-on-a-pull-request) -* [Create a review comment for a pull request](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) -* [List review comments in a repository](/v3/pulls/comments/#list-review-comments-in-a-repository) -* [Get a review comment for a pull request](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) -* [Update a review comment for a pull request](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) -* [Delete a review comment for a pull request](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) +* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository) +* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) ##### Pull Request Review Events -* [Dismiss a review for a pull request](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) -* [Submit a review for a pull request](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) +* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request) ##### Pull Request Review Requests -* [List requested reviewers for a pull request](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) -* [Request reviewers for a pull request](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) -* [Remove requested reviewers from a pull request](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) +* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) ##### Pull Request Reviews -* [List reviews for a pull request](/v3/pulls/reviews/#list-reviews-for-a-pull-request) -* [Create a review for a pull request](/v3/pulls/reviews/#create-a-review-for-a-pull-request) -* [Get a review for a pull request](/v3/pulls/reviews/#get-a-review-for-a-pull-request) -* [Update a review for a pull request](/v3/pulls/reviews/#update-a-review-for-a-pull-request) -* [List comments for a pull request review](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) +* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review) ##### Pulls -* [List pull requests](/v3/pulls/#list-pull-requests) -* [Create a pull request](/v3/pulls/#create-a-pull-request) -* [Get a pull request](/v3/pulls/#get-a-pull-request) -* [Update a pull request](/v3/pulls/#update-a-pull-request) -* [List commits on a pull request](/v3/pulls/#list-commits-on-a-pull-request) -* [List pull requests files](/v3/pulls/#list-pull-requests-files) -* [Check if a pull request has been merged](/v3/pulls/#check-if-a-pull-request-has-been-merged) -* [Merge a pull request (Merge Button)](/v3/pulls/#merge-a-pull-request) +* [List pull requests](/rest/reference/pulls#list-pull-requests) +* [Create a pull request](/rest/reference/pulls#create-a-pull-request) +* [Get a pull request](/rest/reference/pulls#get-a-pull-request) +* [Update a pull request](/rest/reference/pulls#update-a-pull-request) +* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request) +* [List pull requests files](/rest/reference/pulls#list-pull-requests-files) +* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request) ##### リアクション -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/v3/reactions/#delete-a-reaction-legacy){% else %}* [Delete a reaction](/v3/reactions/#delete-a-reaction){% endif %} -* [List reactions for a commit comment](/v3/reactions/#list-reactions-for-a-commit-comment) -* [Create reaction for a commit comment](/v3/reactions/#create-reaction-for-a-commit-comment) -* [List reactions for an issue](/v3/reactions/#list-reactions-for-an-issue) -* [Create reaction for an issue](/v3/reactions/#create-reaction-for-an-issue) -* [List reactions for an issue comment](/v3/reactions/#list-reactions-for-an-issue-comment) -* [Create reaction for an issue comment](/v3/reactions/#create-reaction-for-an-issue-comment) -* [List reactions for a pull request review comment](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) -* [Create reaction for a pull request review comment](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) -* [List reactions for a team discussion comment](/v3/reactions/#list-reactions-for-a-team-discussion-comment) -* [Create reaction for a team discussion comment](/v3/reactions/#create-reaction-for-a-team-discussion-comment) -* [List reactions for a team discussion](/v3/reactions/#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/v3/reactions/#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a commit comment reaction](/v3/reactions/#delete-a-commit-comment-reaction) -* [Delete an issue reaction](/v3/reactions/#delete-an-issue-reaction) -* [Delete a reaction to a commit comment](/v3/reactions/#delete-an-issue-comment-reaction) -* [Delete a pull request comment reaction](/v3/reactions/#delete-a-pull-request-comment-reaction) -* [Delete team discussion reaction](/v3/reactions/#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/v3/reactions/#delete-team-discussion-comment-reaction){% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %} +* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue) +* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue) +* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction) +* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction) +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} ##### リポジトリ -* [Organization リポジトリの一覧表示](/v3/repos/#list-organization-repositories) -* [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) -* [リポジトリの Get](/v3/repos/#get-a-repository) -* [Update a repository](/v3/repos/#update-a-repository) -* [Delete a repository](/v3/repos/#delete-a-repository) -* [Compare two commits](/v3/repos/commits/#compare-two-commits) -* [List repository contributors](/v3/repos/#list-repository-contributors) +* [Organization リポジトリの一覧表示](/rest/reference/repos#list-organization-repositories) +* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [リポジトリの Get](/rest/reference/repos#get-a-repository) +* [Update a repository](/rest/reference/repos#update-a-repository) +* [Delete a repository](/rest/reference/repos#delete-a-repository) +* [Compare two commits](/rest/reference/repos#compare-two-commits) +* [List repository contributors](/rest/reference/repos#list-repository-contributors) * [一覧表示のフォーク](/rest/reference/repos#list-forks) -* [Create a fork](/v3/repos/forks/#create-a-fork) -* [List repository languages](/v3/repos/#list-repository-languages) -* [List repository tags](/v3/repos/#list-repository-tags) -* [List repository teams](/v3/repos/#list-repository-teams) -* [Transfer a repository](/v3/repos/#transfer-a-repository) -* [List public repositories](/v3/repos/#list-public-repositories) -* [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) -* [ユーザのリポジトリの一覧表示](/v3/repos/#list-repositories-for-a-user) -* [Create repository using a repository template](/v3/repos/#create-repository-using-a-repository-template) +* [Create a fork](/rest/reference/repos#create-a-fork) +* [List repository languages](/rest/reference/repos#list-repository-languages) +* [List repository tags](/rest/reference/repos#list-repository-tags) +* [List repository teams](/rest/reference/repos#list-repository-teams) +* [Transfer a repository](/rest/reference/repos#transfer-a-repository) +* [List public repositories](/rest/reference/repos#list-public-repositories) +* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [ユーザのリポジトリの一覧表示](/rest/reference/repos#list-repositories-for-a-user) +* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template) ##### Repository Activity @@ -643,116 +643,116 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Repository Automated Security Fixes -* [Enable automated security fixes](/v3/repos/#enable-automated-security-fixes) -* [Disable automated security fixes](/v3/repos/#disable-automated-security-fixes) +* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes) +* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes) {% endif %} ##### Repository Branches -* [List branches](/v3/repos/branches/#list-branches) -* [Get a branch](/v3/repos/branches/#get-a-branch) -* [Get branch protection](/v3/repos/branches/#get-branch-protection) -* [Update branch protection](/v3/repos/branches/#update-branch-protection) -* [Delete branch protection](/v3/repos/branches/#delete-branch-protection) -* [Get admin branch protection](/v3/repos/branches/#get-admin-branch-protection) -* [Set admin branch protection](/v3/repos/branches/#set-admin-branch-protection) -* [Delete admin branch protection](/v3/repos/branches/#delete-admin-branch-protection) -* [Get pull request review protection](/v3/repos/branches/#get-pull-request-review-protection) -* [Update pull request review protection](/v3/repos/branches/#update-pull-request-review-protection) -* [Delete pull request review protection](/v3/repos/branches/#delete-pull-request-review-protection) -* [Get commit signature protection](/v3/repos/branches/#get-commit-signature-protection) -* [Create commit signature protection](/v3/repos/branches/#create-commit-signature-protection) -* [Delete commit signature protection](/v3/repos/branches/#delete-commit-signature-protection) -* [Get status checks protection](/v3/repos/branches/#get-status-checks-protection) -* [Update status check protection](/v3/repos/branches/#update-status-check-protection) -* [Remove status check protection](/v3/repos/branches/#remove-status-check-protection) -* [Get all status check contexts](/v3/repos/branches/#get-all-status-check-contexts) -* [Add status check contexts](/v3/repos/branches/#add-status-check-contexts) -* [Set status check contexts](/v3/repos/branches/#set-status-check-contexts) -* [Remove status check contexts](/v3/repos/branches/#remove-status-check-contexts) -* [Get access restrictions](/v3/repos/branches/#get-access-restrictions) -* [Delete access restrictions](/v3/repos/branches/#delete-access-restrictions) -* [List teams with access to the protected branch](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) -* [Add team access restrictions](/v3/repos/branches/#add-team-access-restrictions) -* [Set team access restrictions](/v3/repos/branches/#set-team-access-restrictions) -* [Remove team access restriction](/v3/repos/branches/#remove-team-access-restrictions) -* [List user restrictions of protected branch](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) -* [Add user access restrictions](/v3/repos/branches/#add-user-access-restrictions) -* [Set user access restrictions](/v3/repos/branches/#set-user-access-restrictions) -* [Remove user access restrictions](/v3/repos/branches/#remove-user-access-restrictions) -* [Merge a branch](/v3/repos/merging/#merge-a-branch) +* [List branches](/rest/reference/repos#list-branches) +* [Get a branch](/rest/reference/repos#get-a-branch) +* [Get branch protection](/rest/reference/repos#get-branch-protection) +* [Update branch protection](/rest/reference/repos#update-branch-protection) +* [Delete branch protection](/rest/reference/repos#delete-branch-protection) +* [Get admin branch protection](/rest/reference/repos#get-admin-branch-protection) +* [Set admin branch protection](/rest/reference/repos#set-admin-branch-protection) +* [Delete admin branch protection](/rest/reference/repos#delete-admin-branch-protection) +* [Get pull request review protection](/rest/reference/repos#get-pull-request-review-protection) +* [Update pull request review protection](/rest/reference/repos#update-pull-request-review-protection) +* [Delete pull request review protection](/rest/reference/repos#delete-pull-request-review-protection) +* [Get commit signature protection](/rest/reference/repos#get-commit-signature-protection) +* [Create commit signature protection](/rest/reference/repos#create-commit-signature-protection) +* [Delete commit signature protection](/rest/reference/repos#delete-commit-signature-protection) +* [Get status checks protection](/rest/reference/repos#get-status-checks-protection) +* [Update status check protection](/rest/reference/repos#update-status-check-protection) +* [Remove status check protection](/rest/reference/repos#remove-status-check-protection) +* [Get all status check contexts](/rest/reference/repos#get-all-status-check-contexts) +* [Add status check contexts](/rest/reference/repos#add-status-check-contexts) +* [Set status check contexts](/rest/reference/repos#set-status-check-contexts) +* [Remove status check contexts](/rest/reference/repos#remove-status-check-contexts) +* [Get access restrictions](/rest/reference/repos#get-access-restrictions) +* [Delete access restrictions](/rest/reference/repos#delete-access-restrictions) +* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [Add team access restrictions](/rest/reference/repos#add-team-access-restrictions) +* [Set team access restrictions](/rest/reference/repos#set-team-access-restrictions) +* [Remove team access restriction](/rest/reference/repos#remove-team-access-restrictions) +* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [Add user access restrictions](/rest/reference/repos#add-user-access-restrictions) +* [Set user access restrictions](/rest/reference/repos#set-user-access-restrictions) +* [Remove user access restrictions](/rest/reference/repos#remove-user-access-restrictions) +* [Merge a branch](/rest/reference/repos#merge-a-branch) ##### Repository Collaborators -* [List repository collaborators](/v3/repos/collaborators/#list-repository-collaborators) -* [Check if a user is a repository collaborator](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) -* [Add a repository collaborator](/v3/repos/collaborators/#add-a-repository-collaborator) -* [Remove a repository collaborator](/v3/repos/collaborators/#remove-a-repository-collaborator) -* [Get repository permissions for a user](/v3/repos/collaborators/#get-repository-permissions-for-a-user) +* [List repository collaborators](/rest/reference/repos#list-repository-collaborators) +* [Check if a user is a repository collaborator](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator) +* [Remove a repository collaborator](/rest/reference/repos#remove-a-repository-collaborator) +* [Get repository permissions for a user](/rest/reference/repos#get-repository-permissions-for-a-user) ##### Repository Commit Comments -* [List commit comments for a repository](/v3/repos/comments/#list-commit-comments-for-a-repository) -* [Get a commit comment](/v3/repos/comments/#get-a-commit-comment) -* [Update a commit comment](/v3/repos/comments/#update-a-commit-comment) -* [Delete a commit comment](/v3/repos/comments/#delete-a-commit-comment) -* [List commit comments](/v3/repos/comments/#list-commit-comments) -* [Create a commit comment](/v3/repos/comments/#create-a-commit-comment) +* [List commit comments for a repository](/rest/reference/repos#list-commit-comments-for-a-repository) +* [Get a commit comment](/rest/reference/repos#get-a-commit-comment) +* [Update a commit comment](/rest/reference/repos#update-a-commit-comment) +* [Delete a commit comment](/rest/reference/repos#delete-a-commit-comment) +* [List commit comments](/rest/reference/repos#list-commit-comments) +* [Create a commit comment](/rest/reference/repos#create-a-commit-comment) ##### Repository Commits -* [List commits](/v3/repos/commits/#list-commits) -* [Get a commit](/v3/repos/commits/#get-a-commit) -* [List branches for head commit](/v3/repos/commits/#list-branches-for-head-commit) -* [List pull requests associated with commit](/v3/repos/commits/#list-pull-requests-associated-with-commit) +* [List commits](/rest/reference/repos#list-commits) +* [Get a commit](/rest/reference/repos#get-a-commit) +* [List branches for head commit](/rest/reference/repos#list-branches-for-head-commit) +* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit) ##### Repository Community -* [Get the code of conduct for a repository](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) +* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% if currentVersion == "free-pro-team@latest" %} -* [Get community profile metrics](/v3/repos/community/#get-community-profile-metrics) +* [Get community profile metrics](/rest/reference/repos#get-community-profile-metrics) {% endif %} ##### Repository Contents -* [Download a repository archive](/v3/repos/contents/#download-a-repository-archive) -* [Get repository content](/v3/repos/contents/#get-repository-content) -* [Create or update file contents](/v3/repos/contents/#create-or-update-file-contents) -* [Delete a file](/v3/repos/contents/#delete-a-file) -* [Get a repository README](/v3/repos/contents/#get-a-repository-readme) -* [Get the license for a repository](/v3/licenses/#get-the-license-for-a-repository) +* [Download a repository archive](/rest/reference/repos#download-a-repository-archive) +* [Get repository content](/rest/reference/repos#get-repository-content) +* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents) +* [Delete a file](/rest/reference/repos#delete-a-file) +* [Get a repository README](/rest/reference/repos#get-a-repository-readme) +* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Repository Event Dispatches -* [Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event) +* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event) {% endif %} ##### Repository Hooks -* [List repository webhooks](/v3/repos/hooks/#list-repository-webhooks) -* [Create a repository webhook](/v3/repos/hooks/#create-a-repository-webhook) -* [Get a repository webhook](/v3/repos/hooks/#get-a-repository-webhook) -* [Update a repository webhook](/v3/repos/hooks/#update-a-repository-webhook) -* [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) -* [Ping a repository webhook](/v3/repos/hooks/#ping-a-repository-webhook) -* [Test the push repository webhook](/v3/repos/hooks/#test-the-push-repository-webhook) +* [List repository webhooks](/rest/reference/repos#list-repository-webhooks) +* [Create a repository webhook](/rest/reference/repos#create-a-repository-webhook) +* [Get a repository webhook](/rest/reference/repos#get-a-repository-webhook) +* [Update a repository webhook](/rest/reference/repos#update-a-repository-webhook) +* [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) +* [Ping a repository webhook](/rest/reference/repos#ping-a-repository-webhook) +* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook) ##### Repository Invitations -* [List repository invitations](/v3/repos/invitations/#list-repository-invitations) -* [Update a repository invitation](/v3/repos/invitations/#update-a-repository-invitation) -* [Delete a repository invitation](/v3/repos/invitations/#delete-a-repository-invitation) -* [List repository invitations for the authenticated user](/v3/repos/invitations/#list-repository-invitations-for-the-authenticated-user) -* [Accept a repository invitation](/v3/repos/invitations/#accept-a-repository-invitation) -* [Decline a repository invitation](/v3/repos/invitations/#decline-a-repository-invitation) +* [List repository invitations](/rest/reference/repos#list-repository-invitations) +* [Update a repository invitation](/rest/reference/repos#update-a-repository-invitation) +* [Delete a repository invitation](/rest/reference/repos#delete-a-repository-invitation) +* [List repository invitations for the authenticated user](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [Accept a repository invitation](/rest/reference/repos#accept-a-repository-invitation) +* [Decline a repository invitation](/rest/reference/repos#decline-a-repository-invitation) ##### Repository Keys -* [List deploy keys](/v3/repos/keys/#list-deploy-keys) -* [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) -* [Get a deploy key](/v3/repos/keys/#get-a-deploy-key) -* [Delete a deploy key](/v3/repos/keys/#delete-a-deploy-key) +* [List deploy keys](/rest/reference/repos#list-deploy-keys) +* [Create a deploy key](/rest/reference/repos#create-a-deploy-key) +* [Get a deploy key](/rest/reference/repos#get-a-deploy-key) +* [Delete a deploy key](/rest/reference/repos#delete-a-deploy-key) ##### Repository Pages @@ -790,144 +790,144 @@ While most of your API interaction should occur using your server-to-server inst ##### Repository Stats -* [Get the weekly commit activity](/v3/repos/statistics/#get-the-weekly-commit-activity) -* [Get the last year of commit activity](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -* [Get all contributor commit activity](/v3/repos/statistics/#get-all-contributor-commit-activity) -* [Get the weekly commit count](/v3/repos/statistics/#get-the-weekly-commit-count) -* [Get the hourly commit count for each day](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +* [Get the weekly commit activity](/rest/reference/repos#get-the-weekly-commit-activity) +* [Get the last year of commit activity](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [Get all contributor commit activity](/rest/reference/repos#get-all-contributor-commit-activity) +* [Get the weekly commit count](/rest/reference/repos#get-the-weekly-commit-count) +* [Get the hourly commit count for each day](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) {% if currentVersion == "free-pro-team@latest" %} ##### リポジトリ脆弱性アラート -* [Enable vulnerability alerts](/v3/repos/#enable-vulnerability-alerts) -* [Disable vulnerability alerts](/v3/repos/#disable-vulnerability-alerts) +* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts) +* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts) {% endif %} ##### ルート -* [ルートエンドポイント](/v3/#root-endpoint) -* [絵文字](/v3/emojis/#emojis) -* [Get rate limit status for the authenticated user](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) +* [ルートエンドポイント](/rest#root-endpoint) +* [絵文字](/rest/reference/emojis#emojis) +* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) ##### 検索 -* [Search code](/v3/search/#search-code) -* [Search commits](/v3/search/#search-commits) -* [Search labels](/v3/search/#search-labels) -* [リポジトリを検索](/v3/search/#search-repositories) -* [Search topics](/v3/search/#search-topics) -* [Search users](/v3/search/#search-users) +* [Search code](/rest/reference/search#search-code) +* [Search commits](/rest/reference/search#search-commits) +* [Search labels](/rest/reference/search#search-labels) +* [リポジトリを検索](/rest/reference/search#search-repositories) +* [Search topics](/rest/reference/search#search-topics) +* [Search users](/rest/reference/search#search-users) ##### ステータス -* [Get the combined status for a specific reference](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) -* [List commit statuses for a reference](/v3/repos/statuses/#list-commit-statuses-for-a-reference) -* [Create a commit status](/v3/repos/statuses/#create-a-commit-status) +* [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [List commit statuses for a reference](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [Create a commit status](/rest/reference/repos#create-a-commit-status) ##### Team Discussions -* [List discussions](/v3/teams/discussions/#list-discussions) -* [Create a discussion](/v3/teams/discussions/#create-a-discussion) -* [Get a discussion](/v3/teams/discussions/#get-a-discussion) -* [Update a discussion](/v3/teams/discussions/#update-a-discussion) -* [Delete a discussion](/v3/teams/discussions/#delete-a-discussion) -* [List discussion comments](/v3/teams/discussion_comments/#list-discussion-comments) -* [Create a discussion comment](/v3/teams/discussion_comments/#create-a-discussion-comment) -* [Get a discussion comment](/v3/teams/discussion_comments/#get-a-discussion-comment) -* [Update a discussion comment](/v3/teams/discussion_comments/#update-a-discussion-comment) -* [Delete a discussion comment](/v3/teams/discussion_comments/#delete-a-discussion-comment) +* [List discussions](/rest/reference/teams#list-discussions) +* [Create a discussion](/rest/reference/teams#create-a-discussion) +* [Get a discussion](/rest/reference/teams#get-a-discussion) +* [Update a discussion](/rest/reference/teams#update-a-discussion) +* [Delete a discussion](/rest/reference/teams#delete-a-discussion) +* [List discussion comments](/rest/reference/teams#list-discussion-comments) +* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment) +* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment) +* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment) +* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment) ##### Topics -* [Get all repository topics](/v3/repos#get-all-repository-topics) -* [Replace all repository topics](/v3/repos/#replace-all-repository-topics) +* [Get all repository topics](/rest/reference/repos#get-all-repository-topics) +* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics) {% if currentVersion == "free-pro-team@latest" %} ##### トラフィック -* [Get repository clones](/v3/repos/traffic/#get-repository-clones) -* [Get top referral paths](/v3/repos/traffic/#get-top-referral-paths) -* [Get top referral sources](/v3/repos/traffic/#get-top-referral-sources) -* [Get page views](/v3/repos/traffic/#get-page-views) +* [Get repository clones](/rest/reference/repos#get-repository-clones) +* [Get top referral paths](/rest/reference/repos#get-top-referral-paths) +* [Get top referral sources](/rest/reference/repos#get-top-referral-sources) +* [Get page views](/rest/reference/repos#get-page-views) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### User Blocking -* [List users blocked by the authenticated user](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) -* [Check if a user is blocked by the authenticated user](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) -* [List users blocked by an organization](/v3/orgs/blocking/#list-users-blocked-by-an-organization) -* [Check if a user is blocked by an organization](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) -* [Block a user from an organization](/v3/orgs/blocking/#block-a-user-from-an-organization) -* [Unblock a user from an organization](/v3/orgs/blocking/#unblock-a-user-from-an-organization) -* [Block a user](/v3/users/blocking/#block-a-user) -* [Unblock a user](/v3/users/blocking/#unblock-a-user) +* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization) +* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [Block a user](/rest/reference/users#block-a-user) +* [Unblock a user](/rest/reference/users#unblock-a-user) {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ##### User Emails {% if currentVersion == "free-pro-team@latest" %} -* [Set primary email visibility for the authenticated user](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) +* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %} -* [List email addresses for the authenticated user](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) -* [Add email address(es)](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) -* [Delete email address(es)](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) -* [List public email addresses for the authenticated user](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) +* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) {% endif %} ##### User Followers -* [List followers of a user](/v3/users/followers/#list-followers-of-a-user) -* [List the people a user follows](/v3/users/followers/#list-the-people-a-user-follows) -* [Check if a person is followed by the authenticated user](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) -* [Follow a user](/v3/users/followers/#follow-a-user) -* [Unfollow a user](/v3/users/followers/#unfollow-a-user) -* [Check if a user follows another user](/v3/users/followers/#check-if-a-user-follows-another-user) +* [List followers of a user](/rest/reference/users#list-followers-of-a-user) +* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows) +* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [Follow a user](/rest/reference/users#follow-a-user) +* [Unfollow a user](/rest/reference/users#unfollow-a-user) +* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user) ##### User Gpg Keys -* [List GPG keys for the authenticated user](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) -* [Create a GPG key for the authenticated user](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) -* [Get a GPG key for the authenticated user](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) -* [Delete a GPG key for the authenticated user](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) -* [List gpg keys for a user](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) +* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user) ##### User Public Keys -* [List public SSH keys for the authenticated user](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) -* [Create a public SSH key for the authenticated user](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) -* [Get a public SSH key for the authenticated user](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) -* [Delete a public SSH key for the authenticated user](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) -* [List public keys for a user](/v3/users/keys/#list-public-keys-for-a-user) +* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user) ##### ユーザ -* [Get the authenticated user](/v3/users/#get-the-authenticated-user) -* [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) +* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) +* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -* [認証されたユーザのサブスクリプションのリスト](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [認証されたユーザのサブスクリプションのリスト](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% endif %} -* [List users](/v3/users/#list-users) -* [Get a user](/v3/users/#get-a-user) +* [List users](/rest/reference/users#list-users) +* [Get a user](/rest/reference/users#get-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Workflow Runs -* [List workflow runs for a repository](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) -* [Get a workflow run](/v3/actions/workflow-runs/#get-a-workflow-run) -* [Cancel a workflow run](/v3/actions/workflow-runs/#cancel-a-workflow-run) -* [Download workflow run logs](/v3/actions/workflow-runs/#download-workflow-run-logs) -* [Delete workflow run logs](/v3/actions/workflow-runs/#delete-workflow-run-logs) -* [Re run a workflow](/v3/actions/workflow-runs/#re-run-a-workflow) -* [List workflow runs](/v3/actions/workflow-runs/#list-workflow-runs) -* [Get workflow run usage](/v3/actions/workflow-runs/#get-workflow-run-usage) +* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [Get a workflow run](/rest/reference/actions#get-a-workflow-run) +* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run) +* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs) +* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs) +* [Re run a workflow](/rest/reference/actions#re-run-a-workflow) +* [List workflow runs](/rest/reference/actions#list-workflow-runs) +* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### ワークフロー -* [List repository workflows](/v3/actions/workflows/#list-repository-workflows) -* [Get a workflow](/v3/actions/workflows/#get-a-workflow) -* [Get workflow usage](/v3/actions/workflows/#get-workflow-usage) +* [List repository workflows](/rest/reference/actions#list-repository-workflows) +* [Get a workflow](/rest/reference/actions#get-a-workflow) +* [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} diff --git a/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 1062f2c09b..0c3349fd79 100644 --- a/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -23,7 +23,7 @@ This article provides guidelines for existing integrators who are considering mi - Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). - Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration. - Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation. -- Open Source community support is available through [Octokit libraries](/v3/libraries/) and other frameworks such as [Probot](https://probot.github.io/). +- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/). - Integrators building GitHub Apps have opportunities to adopt earlier access to APIs. ### Converting an OAuth App to a GitHub App @@ -42,13 +42,13 @@ These guidelines assume that you have a registered OAuth App{% if currentVersion #### Review the available API endpoints for GitHub Apps -While the majority of [REST API](/v3) endpoints and [GraphQL](/v4) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/v3/apps/available-endpoints/) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. +While the majority of [REST API](/rest) endpoints and [GraphQL](/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_app %}s. #### Design to stay within API rate limits -GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/v3/#conditional-requests) or consolidate requests by using the [GraphQL API V4](/v4/). +GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest#conditional-requests) or consolidate requests by using the [GraphQL API V4](/graphql). #### Register a new GitHub App @@ -56,7 +56,7 @@ Once you've decided to make the switch to Github Apps, you'll need to [create a #### Determine the permissions your app requires -When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/v3/apps/permissions/)" for a list of the permissions needed for each endpoint available to GitHub Apps. +When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps. In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality. @@ -90,11 +90,11 @@ Once you've made the transition from an OAuth App to a GitHub App, you will need https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) and [List organization repositories](/v3/repos/#list-organization-repositories) endpoints. +You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints. #### Remove any unnecessary repository hooks -Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) on those repositories that were created by your OAuth App. +Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) on those repositories that were created by your OAuth App. #### Encourage users to revoke access to your OAuth app diff --git a/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md index 0d4b1ec75d..8d6e4c0d5d 100644 --- a/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -25,7 +25,7 @@ To renew an expiring user-to-server access token, you can exchange the `refresh_ `POST https://github.com/login/oauth/access_token` -This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/v3/guides/basics-of-authentication/#providing-a-callback)." +This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." #### パラメータ diff --git a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md index 9cda3c6f09..1080d22f14 100644 --- a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md @@ -41,13 +41,13 @@ X-Accepted-OAuth-Scopes: user | 名前 | 説明 | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/v3/enterprise-admin).{% endif %} +| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} | **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/v3/repos/deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/v3/code-scanning).{% endif %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | |  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | diff --git a/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md b/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md index 6a8d799202..222dfb1728 100644 --- a/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md @@ -17,4 +17,4 @@ When you create a GitHub App, you can select the permissions it needs to access By default, GitHub Apps have `Read-only` access to metadata endpoints. Metadata is a collection of read-only endpoints that provide general information about resources that the authorized installation can access. -{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/v3/apps/permissions/#metadata-permissions)." +{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/rest/reference/permissions-required-for-github-apps#metadata-permissions)." diff --git a/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index c2d8321ed8..568bf41543 100644 --- a/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -37,7 +37,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [webhook](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -220,7 +220,7 @@ end #### Define a route handler -An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You'll won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. ``` ruby post '/event_handler' do diff --git a/translations/ja-JP/content/developers/apps/using-content-attachments.md b/translations/ja-JP/content/developers/apps/using-content-attachments.md index 5cdf8e130c..61a61a2d39 100644 --- a/translations/ja-JP/content/developers/apps/using-content-attachments.md +++ b/translations/ja-JP/content/developers/apps/using-content-attachments.md @@ -55,7 +55,7 @@ The content attachment flow shows you the relationship between the URL in the is } ``` -**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/v3/apps/installations/#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -116,7 +116,7 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -For more information on `node_id`, see "[Using Global Node IDs](/v4/guides/using-global-node-ids/)." +For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ### Example using Probot and GitHub App Manifests diff --git a/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md b/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md index 5d8116f1ff..3b206f1718 100644 --- a/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md @@ -31,7 +31,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [webhook](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -74,7 +74,7 @@ These are the steps you'll complete to create your first GitHub App: ### ステップ 1. Update app permissions -When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels. +[最初にアプリケーションを登録](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)した際は、デフォルトの権限を受け入れています。これは、アプリケーションがほとんどのリソースにアクセスできないことを意味します。 For this example, your app will need permission to read issues and write labels. アプリケーションの権限を更新するには、以下の手順に従います。 @@ -143,11 +143,11 @@ Before the label can be _added_ anywhere, you'll need to _create_ the custom lab {% tip %} -**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/v3/issues/labels/#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. +**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. {% endtip %} -Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/v3/issues/labels/#add-labels-to-an-issue). +Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue). ### ステップ 4. Add label handling diff --git a/translations/ja-JP/content/developers/github-marketplace/billing-customers.md b/translations/ja-JP/content/developers/github-marketplace/billing-customers.md index 270b7aa97a..925d2cb0db 100644 --- a/translations/ja-JP/content/developers/github-marketplace/billing-customers.md +++ b/translations/ja-JP/content/developers/github-marketplace/billing-customers.md @@ -25,7 +25,7 @@ versions: 明確で一貫性のある支払いプロセスを保つために、アップグレード、ダウングレード、キャンセルについて以下のガイドラインに従ってください。 {% data variables.product.prodname_marketplace %}の購入イベントに関する詳細な手順については「[支払いのフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)」を参照してください。 -`marketplace_purchase` webhookの`effective_date`キーを使えば、プランの変更がいつ生じるのかを確認し、定期的に[プランのアカウントのリスト](/v3/apps/marketplace/#list-accounts-for-a-plan)を同期できます。 +`marketplace_purchase` webhookの`effective_date`キーを使えば、プランの変更がいつ生じるのかを確認し、定期的に[プランのアカウントのリスト](/rest/reference/apps#list-accounts-for-a-plan)を同期できます。 #### アップグレード diff --git a/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index c5456ec756..5166af9deb 100644 --- a/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -68,7 +68,7 @@ versions: ### ステップ 4. 顧客アカウントのプロビジョニング -アプリケーションは、すべての新規購入に対して顧客アカウントをプロビジョニングしなければなりません。 [ステップ3 認可](#step-3-authorization)で受け取った顧客のアクセストークンを使い、 「[認証されたユーザのサブスクリプションのリスト](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user)」エンドポイントを呼び出してください。 レスポンスには顧客の`account`情報が含まれ、その顧客が無料トライアルを利用しているかが示されます（`on_free_trial`）。 この情報を使って、セットアップとプロビジョニングを完了させてください。 +アプリケーションは、すべての新規購入に対して顧客アカウントをプロビジョニングしなければなりません。 [ステップ3 認可](#step-3-authorization)で受け取った顧客のアクセストークンを使い、 「[認証されたユーザのサブスクリプションのリスト](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)」エンドポイントを呼び出してください。 レスポンスには顧客の`account`情報が含まれ、その顧客が無料トライアルを利用しているかが示されます（`on_free_trial`）。 この情報を使って、セットアップとプロビジョニングを完了させてください。 {% data reusables.marketplace.marketplace-double-purchases %} @@ -76,6 +76,6 @@ versions: Organizationのメンバーがアプリケーションへのアクセスを受け取る方法は、カスタマイズできます。 いくつかの例を挙げましょう。 -**定額料金:** Organizationに対して定額料金での購入が行われたなら、アプリケーションはAPI経由で[Organizationの全メンバーを取得](/v3/orgs/members/#list-organization-members)して、Organizationの管理者に対してどのメンバーがインテグレーター側で有料ユーザとなるかの選択を求めることができます。 +**定額料金:** Organizationに対して定額料金での購入が行われたなら、アプリケーションはAPI経由で[Organizationの全メンバーを取得](/rest/reference/orgs#list-organization-members)して、Organizationの管理者に対してどのメンバーがインテグレーター側で有料ユーザとなるかの選択を求めることができます。 **ユニット単位の料金:** ユニットシートごとにプロビジョニングする方法の1つは、ユーザがアプリケーションにログインしたときにシートを使用できるようにすることです。 顧客がシートカウントの閾値に達した場合、アプリケーションはユーザに対して{% data variables.product.prodname_marketplace %}を通じてアップグレードする必要があることを警告できます。 diff --git a/translations/ja-JP/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/ja-JP/content/developers/github-marketplace/handling-plan-cancellations.md index 3d7dc3242d..7b74900171 100644 --- a/translations/ja-JP/content/developers/github-marketplace/handling-plan-cancellations.md +++ b/translations/ja-JP/content/developers/github-marketplace/handling-plan-cancellations.md @@ -28,6 +28,6 @@ versions: {% note %} -**ノート:** プランの変更がいつ生じるのかを知るために[`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhookの`effective_date`を利用し、定期的に[プランのリストアカウント](/v3/apps/marketplace/#list-accounts-for-a-plan)を同期することをおすすめします。 webhookに関する詳しい情報については「[{% data variables.product.prodname_marketplace %}のwebhookイベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。 +**ノート:** プランの変更がいつ生じるのかを知るために[`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhookの`effective_date`を利用し、定期的に[プランのリストアカウント](/rest/reference/apps#list-accounts-for-a-plan)を同期することをおすすめします。 webhookに関する詳しい情報については「[{% data variables.product.prodname_marketplace %}のwebhookイベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/developers/github-marketplace/handling-plan-changes.md b/translations/ja-JP/content/developers/github-marketplace/handling-plan-changes.md index 8b20394f2f..f6c7d78f79 100644 --- a/translations/ja-JP/content/developers/github-marketplace/handling-plan-changes.md +++ b/translations/ja-JP/content/developers/github-marketplace/handling-plan-changes.md @@ -54,7 +54,7 @@ https://www.github.com/marketplace//upgrade// たとえば、顧客が5人のプランを使っていて、10人のプランに移行する必要があることに気づいた場合、アプリケーションのUIに「アップグレードの方法はこちら」というボタンを表示したり、アップグレードURLへのリンクを持つバナーを表示したりできます。 アップグレードURLは顧客をリストされたプランのアップグレードの確認ページへ移動させます。 -顧客が購入したいであろうプランの`LISTING_PLAN_NUMBER`を使ってください。 新しい価格プランを作成すると、それらにはリスト内で各プランに対してユニークな`LISTING_PLAN_NUMBER`と、{% data variables.product.prodname_marketplace %}内で各プランに対してユニークな`LISTING_PLAN_ID`が与えられます。 [プランをリスト](/v3/apps/marketplace/#list-plans)する際にはこれらの番号があり、リストの価格プランを特定できます。 `LISTING_PLAN_ID`と「[プランに対するアカウントのリスト](/v3/apps/marketplace/#list-accounts-for-a-plan)」エンドポイントを使って、`CUSTOMER_ACCOUNT_ID`を取得してください。 +顧客が購入したいであろうプランの`LISTING_PLAN_NUMBER`を使ってください。 新しい価格プランを作成すると、それらにはリスト内で各プランに対してユニークな`LISTING_PLAN_NUMBER`と、{% data variables.product.prodname_marketplace %}内で各プランに対してユニークな`LISTING_PLAN_ID`が与えられます。 [プランをリスト](/rest/reference/apps#list-plans)する際にはこれらの番号があり、リストの価格プランを特定できます。 `LISTING_PLAN_ID`と「[プランに対するアカウントのリスト](/rest/reference/apps#list-accounts-for-a-plan)」エンドポイントを使って、`CUSTOMER_ACCOUNT_ID`を取得してください。 {% note %} diff --git a/translations/ja-JP/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md b/translations/ja-JP/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md index ca90f5d346..bfadbfe3ef 100644 --- a/translations/ja-JP/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md +++ b/translations/ja-JP/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md @@ -13,10 +13,10 @@ versions: 以下は、Marketplaceのリストで利用できる便利なエンドポイントです。 -* [プランのリスト](/v3/apps/marketplace/#list-plans) -* [プランのアカウントのリスト](/v3/apps/marketplace/#list-accounts-for-a-plan) -* [アカウントのサブスクリプションプランの取得](/v3/apps/marketplace/#get-a-subscription-plan-for-an-account) -* [認証されたユーザのサブスクリプションのリスト](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [プランのリスト](/rest/reference/apps#list-plans) +* [プランのアカウントのリスト](/rest/reference/apps#list-accounts-for-a-plan) +* [アカウントのサブスクリプションプランの取得](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [認証されたユーザのサブスクリプションのリスト](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% data variables.product.prodname_marketplace %} APIを使用する際の認証の受け方の詳細については、以下のページを参照してください。 @@ -25,6 +25,6 @@ versions: {% note %} -**ノート:** [REST APIのためのレート制限](/v3/#rate-limiting)は、{% data variables.product.prodname_marketplace %} APIのすべてのエンドポイントに適用されます。 +**ノート:** [REST APIのためのレート制限](/rest#rate-limiting)は、{% data variables.product.prodname_marketplace %} APIのすべてのエンドポイントに適用されます。 {% endnote %} diff --git a/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md b/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md index d798e1145d..03cc9014c1 100644 --- a/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md @@ -37,7 +37,7 @@ versions: ### APIのテスト -ほとんどの{% data variables.product.prodname_marketplace %} APIエンドポイントに対しては、テストに利用できるハードコーディングされた偽のデータを返すスタブのAPIエンドポイントも提供されています。 スタブのデータを受信するには、ルートに`/stubbed`を含むスタブURL（たとえば`/user/marketplace_purchases/stubbed`）を指定してください。 スタブデータのアプローチをサポートしているエンドポイントのリストは、[{% data variables.product.prodname_marketplace %}エンドポイント](/v3/apps/marketplace/#github-marketplace)を参照してください。 +ほとんどの{% data variables.product.prodname_marketplace %} APIエンドポイントに対しては、テストに利用できるハードコーディングされた偽のデータを返すスタブのAPIエンドポイントも提供されています。 スタブのデータを受信するには、ルートに`/stubbed`を含むスタブURL（たとえば`/user/marketplace_purchases/stubbed`）を指定してください。 スタブデータのアプローチをサポートしているエンドポイントのリストは、[{% data variables.product.prodname_marketplace %}エンドポイント](/rest/reference/apps#github-marketplace)を参照してください。 ### webhookのテスト diff --git a/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 775b4a70e5..8fb4e33a30 100644 --- a/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -31,15 +31,15 @@ webhookの`POST`リクエストには、特別なヘッダがあります。 詳 `marketplace_purchase`オブジェクトは、以下のキーを持ちます。 -| キー | 種類 | 説明 | -| -------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `account` | `object` | サブスクリプションに関連づけられた`organization`もしくあは`user`アカウント。 Organizationアカウントは、そのOrganizationの管理者のメールアドレスである`organization_billing_email`を含みます。 個人アカウントのメールアドレスを知るには、[認証されたユーザの取得](/v3/users/#get-the-authenticated-user)エンドポイントが利用できます。 | -| `billing_cycle` | `string` | `yearly`もしくは`monthly`のいずれかになります。 `account`の所有者が無料のGitHubのプランを使っており、無料の{% data variables.product.prodname_marketplace %}プランを購入した場合、`billing_cycle`は`nil`になります。 | -| `unit_count` | `integer` | 購入したユーザ数。 | -| `on_free_trial` | `boolean` | `account`が無料トライアル中の場合`true`になります。 | -| `free_trial_ends_on` | `string` | 無料トライアルが期限切れになる日付。 | -| `next_billing_date` | `string` | 次の支払いサイクルが始まる日付。 `account`の所有者が無料のGitHub.comのプランを使っており、無料の{% data variables.product.prodname_marketplace %}プランを購入した場合、`next_billing_date`は`nil`になります。 | -| `plan` | `オブジェクト` | `user`または`organization`が購入したプラン。 | +| キー | 種類 | 説明 | +| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `account` | `object` | サブスクリプションに関連づけられた`organization`もしくあは`user`アカウント。 Organizationアカウントは、そのOrganizationの管理者のメールアドレスである`organization_billing_email`を含みます。 個人アカウントのメールアドレスを知るには、[認証されたユーザの取得](/rest/reference/users#get-the-authenticated-user)エンドポイントが利用できます。 | +| `billing_cycle` | `string` | `yearly`もしくは`monthly`のいずれかになります。 `account`の所有者が無料のGitHubのプランを使っており、無料の{% data variables.product.prodname_marketplace %}プランを購入した場合、`billing_cycle`は`nil`になります。 | +| `unit_count` | `integer` | 購入したユーザ数。 | +| `on_free_trial` | `boolean` | `account`が無料トライアル中の場合`true`になります。 | +| `free_trial_ends_on` | `string` | 無料トライアルが期限切れになる日付。 | +| `next_billing_date` | `string` | 次の支払いサイクルが始まる日付。 `account`の所有者が無料のGitHub.comのプランを使っており、無料の{% data variables.product.prodname_marketplace %}プランを購入した場合、`next_billing_date`は`nil`になります。 | +| `plan` | `オブジェクト` | `user`または`organization`が購入したプラン。 | `plan`オブジェクトには以下のキーがあります。 diff --git a/translations/ja-JP/content/developers/overview/about-githubs-apis.md b/translations/ja-JP/content/developers/overview/about-githubs-apis.md index b6b267148b..ed6731b247 100644 --- a/translations/ja-JP/content/developers/overview/about-githubs-apis.md +++ b/translations/ja-JP/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -GitHub APIには、[REST API](/v3/)と[GraphQL API](/v4/)という2つの安定バージョンがあります。 +GitHub APIには、[REST API](/rest)と[GraphQL API](/graphql)という2つの安定バージョンがあります。 -REST APIを使う際には、[`Accept`ヘッダを介してv3をリクエスト](/v3/media/#request-specific-version)することをおすすめします。 +REST APIを使う際には、[`Accept`ヘッダを介してv3をリクエスト](/rest/overview/media-types#request-specific-version)することをおすすめします。 -GraphQL APIの利用に関する情報については[v4のドキュメント](/v4/)を参照してください。 +GraphQL APIの利用に関する情報については[v4のドキュメント](/graphql)を参照してください。 ## 非推奨のバージョン diff --git a/translations/ja-JP/content/developers/overview/secret-scanning.md b/translations/ja-JP/content/developers/overview/secret-scanning.md index 66751d7e41..a03b9bb190 100644 --- a/translations/ja-JP/content/developers/overview/secret-scanning.md +++ b/translations/ja-JP/content/developers/overview/secret-scanning.md @@ -29,7 +29,7 @@ versions: 以下の図は、パブリックリポジトリに対するシークレットスキャンニングのプロセスをまとめたもので、一致があった場合にサービスプロバイダへの検証エンドポイントに送信されています。 -![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "Secret scanning flow") +![シークレットのスキャンニングと、サービスプロバイダーの検証エンドポイントへの一致の送信のプロセスのフロー図。](/assets/images/secret-scanning-flow.png "シークレットスキャンニングのフロー") ### {% data variables.product.prodname_dotcom %}上のシークレットスキャンニングプログラムへの参加 @@ -43,23 +43,23 @@ versions: 登録のプロセスを開始するために、secret-scanning@github.comにメールしてください。 -You will receive details on the secret scanning program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. +シークレットスキャンニングプログラムの詳細が送られてくるので、先へ進む前に{% data variables.product.prodname_dotcom %}の参加規約に同意しなければなりません。 -#### Identify your secrets and create regular expressions +#### シークレットの特定と正規表現の作成 -To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the secret scanning program: +シークレットをスキャンするために、{% data variables.product.prodname_dotcom %}はシークレットスキャンニングプログラムに含めたいそれぞれのシークレットについて以下の情報を必要とします。 -* A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later. -* A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives. -* The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type. +* シークレットの種類に対する、ユニークで人が読める名前。 後にこれを使って、メッセージペイロード中の`Type`値が生成されます。 +* このシークレットの種類を見つける正規表現。 できるかぎり正確にしてください。そうすることで、誤検知の数を減らすことができます。 +* {% data variables.product.prodname_dotcom %}からのメッセージを受信するエンドポイントのURL。 これは各シークレットの種類ごとにユニークである必要はありません。 -Send this information to secret-scanning@github.com. +この情報をsecret-scanning@github.comに送信してください。 -#### Create a secret alert service +#### シークレットアラートサービスの作成 -Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send a HTTP `POST` message to your endpoint. +提供したURLに、パブリックでインターネットからアクセスできるHTTPエンドポイントを作成してください。 パブリックリポジトリで正規表現への一致が見つかった場合、{% data variables.product.prodname_dotcom %}はHTTPの`POST`メッセージをエンドポイントに送信します。 -##### Example POST sent to your endpoint +##### エンドポイントに送信されるPOSTの例 ``` POST / HTTP/1.1 @@ -79,21 +79,21 @@ Content-Length: 0123 ] ``` -The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %} may send a single message with more than one secret match. Your endpoint should be able to handle requests with a large number of matches without timing out. +メッセージのボディはJSONの配列で、以下の内容を持つ1つ以上のオブジェクトを含みます。 複数の一致が見つかった場合には、{% data variables.product.prodname_dotcom %}は複数のシークレットの一致を含む1つのメッセージを送信することがあります。 エンドポイントは、タイムアウトすることなく大量の一致を含むリクエストを処理できなければなりません。 -* **Token**: The value of the secret match. -* **Type**: The unique name you provided to identify your regular expression. -* **URL**: The public commit URL where the match was found. +* **Token**: シークレットの一致の値。 +* **Type**: 正規表現を特定するために渡されたユニークな名前。 +* **URL**: マッチが見つかったパブリックなコミットURL。 -#### Implement signature verification in your secret alert service +#### シークレットアラートサービスへの署名検証の実装 -We strongly recommend you implement signature validation in your secret alert service to ensure that the messages you receive are genuinely from {% data variables.product.prodname_dotcom %} and not malicious. +シークレットサービスには署名検証サービスを実装して、受信したメッセージが本当に{% data variables.product.prodname_dotcom %}からのものであり、悪意がないことを保証することを強くおすすめします。 -You can retrieve the {% data variables.product.prodname_dotcom %} secret scanning public key from https://api.github.com/meta/public_keys/secret_scanning and validate the message using the `ECDSA-NIST-P256V1-SHA256` algorithm. +{% data variables.product.prodname_dotcom %}のシークレットスキャンニング公開鍵はhttps://api.github.com/meta/public_keys/secret_scanningから取得でき、`ECDSA-NIST-P256V1-SHA256`アルゴリズムを使ってメッセージを検証できます。 -Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set. +次のメッセージを受信したとして、以下のコードは署名検証の方法を示しています。 このコードはまた、`GITHUB_PRODUCTION_TOKEN`という環境変数に生成されたPATが設定されているものとしています(https://github.com/settings/tokens)。 このトークンには権限が設定されている必要はありません。 -**Sample message sent to verify endpoint** +**検証エンドポイントに送信されたサンプルのメッセージ** ``` POST / HTTP/1.1 Host: HOST @@ -106,7 +106,7 @@ Content-Length: 0000 [{"token": "some_token", "type": "some_type", "url": "some_url"}] ``` -**Validation sample in Go** +**Goでの検証のサンプル** ```golang package main @@ -132,7 +132,7 @@ func main() { kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=" - // Fetch the list of GitHub Public Keys + // GitHub公開鍵のリストをフェッチ req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil) if err != nil { fmt.Printf("Error preparing request: %s\n", err) @@ -159,7 +159,7 @@ func main() { os.Exit(3) } - // Find the Key used to sign our webhook + // webhookの署名に使われた鍵を見つける pubKey, err := func() (string, error) { for _, v := range keys.PublicKeys { if v.KeyIdentifier == kID { @@ -175,33 +175,25 @@ func main() { os.Exit(4) } - // Decode the Public Key + // 公開鍵のデコード block, _ := pem.Decode([]byte(pubKey)) if block == nil { fmt.Println("Error parsing PEM block with GitHub public key") os.Exit(5) } - // Create our ECDSA Public Key + // ECDSA公開鍵の生成 key, err := x509.ParsePKIXPublicKey(block.Bytes) if err != nil { fmt.Printf("Error parsing DER encoded public key: %s\n", err) os.Exit(6) } - // Because of documentation, we know it's a *ecdsa.PublicKey + // ドキュメントから、これが*ecdsa.PublicKeyであることは分かっている ecdsaKey, ok := key.(*ecdsa.PublicKey) if !ok { fmt.Println("GitHub key was not ECDSA, what are they doing?!") - os.Exit(7) - } - - // Parse the Webhook Signature - parsedSig := asn1Signature{} - asnSig, err := base64.StdEncoding.DecodeString(kSig) - if err != nil { - fmt.Printf("unable to base64 decode signature: %s\n", err) - os.Exit(8) + os.Exit(8) } rest, err := asn1.Unmarshal(asnSig, &parsedSig) if err != nil || len(rest) != 0 { @@ -209,7 +201,7 @@ func main() { os.Exit(9) } - // Verify the SHA256 encoded payload against the signature with GitHub's Key + // SHA256エンコードされたペイロードをGitHubの鍵での署名に対して検証する digest := sha256.Sum256([]byte(payload)) keyOk := ecdsa.Verify(ecdsaKey, digest[:], parsedSig.R, parsedSig.S) @@ -229,14 +221,14 @@ type GitHubSigningKeys struct { } `json:"public_keys"` } -// asn1Signature is a struct for ASN.1 serializing/parsing signatures. +// asn1Signatureは ASN.1 シリアライズ/パース署名に対する構造体 type asn1Signature struct { R *big.Int S *big.Int } ``` -**Validation sample in Ruby** +**Rubyでの検証サンプル** ```ruby require 'openssl' require 'net/http' @@ -276,6 +268,6 @@ openssl_key = OpenSSL::PKey::EC.new(current_key) puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), payload.chomp) ``` -#### Implement secret revocation and user notification in your secret alert service +#### シークレットアラートサービスへのシークレットの破棄とユーザ通知の実装 -For secret scanning in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. +パブリックリポジトリでのシークレットスキャンニングでは、シークレットアラートサービスを拡張して、公開されたシークレットを取り除き、影響されたユーザに通知できます。 これをシークレットアラートサービスへどのように実装するかは実装者に任されていますが、{% data variables.product.prodname_dotcom %}がメッセージを送信したすべてのシークレットは、公開され、侵害されたものと考えることをおすすめします。 diff --git a/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md b/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md index 951c3ca09e..04973f146a 100644 --- a/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md +++ b/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md @@ -1,6 +1,6 @@ --- -title: Using SSH agent forwarding -intro: 'To simplify deploying to a server, you can set up SSH agent forwarding to securely use local SSH keys.' +title: SSHエージェント転送の利用 +intro: 'サーバーへのデプロイを簡単にするために、SSHエージェント転送をセットアップして、安全にローカルのSSHキーを使うことができます。' redirect_from: - /guides/using-ssh-agent-forwarding/ - /v3/guides/using-ssh-agent-forwarding @@ -12,45 +12,45 @@ versions: -SSH agent forwarding can be used to make deploying to a server simple. It allows you to use your local SSH keys instead of leaving keys (without passphrases!) sitting on your server. +SSHエージェント転送を使って、サーバーへのデプロイをシンプルにすることができます。 そうすることで、キー（パスフレーズなしの！）をサーバー上に残さずに、ローカルのSSHキーを使用できます。 -If you've already set up an SSH key to interact with {% data variables.product.product_name %}, you're probably familiar with `ssh-agent`. It's a program that runs in the background and keeps your key loaded into memory, so that you don't need to enter your passphrase every time you need to use the key. The nifty thing is, you can choose to let servers access your local `ssh-agent` as if they were already running on the server. This is sort of like asking a friend to enter their password so that you can use their computer. +{% data variables.product.product_name %}とやりとりするためのSSHキーをセットアップ済みなら、`ssh-agent`には慣れていることでしょう。 これは、バックグラウンドで実行され、キーをメモリにロードした状態にし続けるので、キーを使うたびにパスフレーズを入力する必要がなくなります。 便利なのは、ローカルの`ssh-agent`がサーバー上で動作しているかのように、サーバーからローカルの`ssh-agent`にアクセスさせられることです。 これは、友人のコンピュータをあなたが使えるように、友人のパスワードを友人に入力してもらうように頼むようなものです。 -Check out [Steve Friedl's Tech Tips guide][tech-tips] for a more detailed explanation of SSH agent forwarding. +SSHエージェント転送に関するさらに詳細な説明については、[Steve Friedl's Tech Tips guide][tech-tips]をご覧ください。 -### Setting up SSH agent forwarding +### SSHエージェント転送のセットアップ -Ensure that your own SSH key is set up and working. You can use [our guide on generating SSH keys][generating-keys] if you've not done this yet. +SSHキーがセットアップされており、動作していることを確認してください。 まだ確認ができていないなら、[SSHキーの生成ガイド][generating-keys]を利用できます。 -You can test that your local key works by entering `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` in the terminal: +ローカルのキーが動作しているかは、ターミナルで`ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}`と入力すればテストできます。 ```shell $ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %} -# Attempt to SSH in to github +# SSHでgithubに入る > Hi username! You've successfully authenticated, but GitHub does not provide > shell access. ``` -We're off to a great start. Let's set up SSH to allow agent forwarding to your server. +いいスタートを切ることができました。 サーバーへのエージェント転送ができるよう、SSHをセットアップしましょう。 -1. Using your favorite text editor, open up the file at `~/.ssh/config`. If this file doesn't exist, you can create it by entering `touch ~/.ssh/config` in the terminal. +1. 好きなテキストエディタで`~/.ssh/config`にあるファイルを開いてください。 もしこのファイルがなかったなら、ターミナルで`touch ~/.ssh/config`と入力すれば作成できます。 -2. Enter the following text into the file, replacing `example.com` with your server's domain name or IP: +2. `example.com`のところを使用するサーバーのドメイン名もしくはIPで置き換えて、以下のテキストをこのファイルに入力してください。 Host example.com ForwardAgent yes {% warning %} -**Warning:** You may be tempted to use a wildcard like `Host *` to just apply this setting to all SSH connections. That's not really a good idea, as you'd be sharing your local SSH keys with *every* server you SSH into. They won't have direct access to the keys, but they will be able to use them *as you* while the connection is established. **You should only add servers you trust and that you intend to use with agent forwarding.** +**警告:** すべてのSSH接続のこの設定を適用するために、`Host *`のようなワイルドカードを使いたくなるかもしれません。 これはローカルのSSHキーをSSHで入る*すべての*サーバーと共有することになるので、実際には良い考えではありません。 キーに直接アクセスされることはないかもしれませんが、接続が確立されている間はそれらのキーが*あなたのかわりに*使われるかもしれません。 **追加するサーバーは、信用でき、エージェント転送で使おうとしているサーバーのみにすべきです。** {% endwarning %} -### Testing SSH agent forwarding +### SSHエージェント転送のテスト -To test that agent forwarding is working with your server, you can SSH into your server and run `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` once more. If all is well, you'll get back the same prompt as you did locally. +エージェント転送がサーバーで動作しているかをテストするには、サーバーにSSHで入ってもう一度`ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}`と実行してみてください。 すべてうまくいっているなら、ローカルでやった場合と同じプロンプトが返ってくるでしょう。 -If you're unsure if your local key is being used, you can also inspect the `SSH_AUTH_SOCK` variable on your server: +ローカルのキーが使われているか確信が持てない場合は、サーバー上で`SSH_AUTH_SOCK`変数を調べてみることもできます。 ```shell $ echo "$SSH_AUTH_SOCK" @@ -58,24 +58,24 @@ $ echo "$SSH_AUTH_SOCK" > /tmp/ssh-4hNGMk8AZX/agent.79453 ``` -If the variable is not set, it means that agent forwarding is not working: +この変数が設定されていないなら、エージェント転送は動作していないということです。 ```shell $ echo "$SSH_AUTH_SOCK" -# Print out the SSH_AUTH_SOCK variable +# SSH_AUTH_SOCK変数の出力 > [No output] $ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %} -# Try to SSH to github +# SSHでgithubに入る > Permission denied (publickey). ``` -### Troubleshooting SSH agent forwarding +### SSHエージェント転送のトラブルシューティング -Here are some things to look out for when troubleshooting SSH agent forwarding. +以下は、SSHエージェント転送のトラブルシューティングの際に注意すべきことです。 -#### You must be using an SSH URL to check out code +#### コードをのチェックアウトにはSSH URLを使わなければならない -SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/config* file on your server and ensure the URL is an SSH-style URL like below: +SSH転送はHTTP(s) URLでは動作せず、SSH URLでのみ動作します。 サーバー上の*.git/config*ファイルを調べて、URLが以下のようなSSHスタイルのURLになっていることを確認してください。 ```shell [remote "origin"] @@ -83,13 +83,13 @@ SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/confi fetch = +refs/heads/*:refs/remotes/origin/* ``` -#### Your SSH keys must work locally +#### SSHキーはローカルで動作していなければならない -Before you can make your keys work through agent forwarding, they must work locally first. [Our guide on generating SSH keys][generating-keys] can help you set up your SSH keys locally. +エージェント転送を通じてキーを動作させるには、まずキーがローカルで動作していなければなりません。 SSHキーをローカルでセットアップするには、[SSHキーの生成ガイド][generating-keys]が役に立つでしょう。 -#### Your system must allow SSH agent forwarding +#### システムがSSHエージェント転送を許可していなければならない -Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal: +システム設定でSSHエージェント転送が許可されていないことがあります。 システム設定ファイルが使われているかは、ターミナルで以下のコマンドを入力してみればチェックできます。 ```shell $ ssh -v example.com @@ -103,7 +103,7 @@ $ exit # Returns to your local command prompt ``` -In the example above, the file *~/.ssh/config* is loaded first, then */etc/ssh_config* is read. We can inspect that file to see if it's overriding our options by running the following commands: +上の例では、*~/.ssh/config*というファイルがまずロードされ、それから*/etc/ssh_config*が読まれます。 以下のコマンドを実行すれば、そのファイルが設定を上書きしているかを調べることができます。 ```shell $ cat /etc/ssh_config @@ -113,17 +113,17 @@ $ cat /etc/ssh_config > ForwardAgent no ``` -In this example, our */etc/ssh_config* file specifically says `ForwardAgent no`, which is a way to block agent forwarding. Deleting this line from the file should get agent forwarding working once more. +この例では、*/etc/ssh_config*ファイルが`ForwardAgent no`と具体的に指定しており、これはエージェント転送をブロックするやり方です。 この行をファイルから削除すれば、エージェント転送は改めて動作するようになります。 -#### Your server must allow SSH agent forwarding on inbound connections +#### サーバーはインバウンド接続でSSHエージェント転送を許可していなければならない -Agent forwarding may also be blocked on your server. You can check that agent forwarding is permitted by SSHing into the server and running `sshd_config`. The output from this command should indicate that `AllowAgentForwarding` is set. +エージェント転送は、サーバーでブロックされているかもしれません。 エージェント転送が許可されているかは、サーバーにSSHで入り、`sshd_config`を実行してみれば確認できます。 このコマンドからの出力で、`AllowAgentForwarding`が設定されていることが示されていなければなりません。 -#### Your local `ssh-agent` must be running +#### ローカルの`ssh-agent`が動作していなければならない -On most computers, the operating system automatically launches `ssh-agent` for you. On Windows, however, you need to do this manually. We have [a guide on how to start `ssh-agent` whenever you open Git Bash][autolaunch-ssh-agent]. +ほとんどのコンピュータでは、オペレーティングシステムは自動的に`ssh-agent`を起動してくれます。 しかし、Windowsではこれを手動で行わなければなりません。 [Git Bashを開いたときに`ssh-agent`を起動する方法のガイド][autolaunch-ssh-agent]があります。 -To verify that `ssh-agent` is running on your computer, type the following command in the terminal: +コンピュータで`ssh-agent`が動作しているかを確認するには、ターミナルで以下のコマンドを入力してください。 ```shell $ echo "$SSH_AUTH_SOCK" @@ -131,15 +131,15 @@ $ echo "$SSH_AUTH_SOCK" > /tmp/launch-kNSlgU/Listeners ``` -#### Your key must be available to `ssh-agent` +#### キーが`ssh-agent`から利用可能でなければならない -You can check that your key is visible to `ssh-agent` by running the following command: +`ssh-agent`からキーが見えるかは、以下のコマンドを実行すれば確認できます。 ```shell ssh-add -L ``` -If the command says that no identity is available, you'll need to add your key: +このコマンドが識別情報が利用できないと言ってきたなら、キーを追加しなければなりません。 ```shell $ ssh-add yourkey @@ -147,7 +147,7 @@ $ ssh-add yourkey {% tip %} -On Mac OS X, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command: +Mac OS Xでは、再起動時に`ssh-agent`が起動し直されると、キーは「忘れられて」しまいます。 ただし、以下のコマンドでキーチェーンにSSHキーをインポートできます。 ```shell $ ssh-add -K yourkey @@ -157,5 +157,4 @@ $ ssh-add -K yourkey [tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html [generating-keys]: /articles/generating-ssh-keys -[generating-keys]: /articles/generating-ssh-keys [autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows diff --git a/translations/ja-JP/content/developers/webhooks-and-events/about-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/about-webhooks.md index b97f903371..78cbc68fd8 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/about-webhooks.md @@ -1,6 +1,6 @@ --- title: webhook について -intro: Learn the basics of how webhooks work to help you build and set up integrations. +intro: インテグレーションの構築とセットアップに役立つwebhookの動作の基本を学んでください。 redirect_from: - /webhooks versions: @@ -10,25 +10,25 @@ versions: --- -Webhooks allow you to build or set up integrations, such as [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), which subscribe to certain events on GitHub.com. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. You're only limited by your imagination. +webhookを使うと、[{% data variables.product.prodname_github_app %}](/apps/building-github-apps/)や[{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/)のような、GitHub.com上の特定のイベントをサブスクライブするインテグレーションを構築し、セットアップできます。 それらのイベントのいずれかがトリガーされると、webhookに設定されたURLにHTTP POSTペイロードが送信されます。 webhookは、外部のIssueトラッカーを更新したり、CIビルドをトリガーしたり、バックアップミラーを更新したり、さらにはプロダクションサーバーへのデプロイをしたりするのに利用できます。 想像力が及ぶかぎりのことが可能です。 -Webhooks can be installed on{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} an [organization][org-hooks], a specific [repository][repo-hooks], or a {% data variables.product.prodname_github_app %}. Once installed, the webhook will be sent each time one or more subscribed events occurs. +webhookは、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/)、{% endif %}[Organization][org-hooks]、特定の[リポジトリ][repo-hooks]、{% data variables.product.prodname_github_app %}にインストールできます。 インストールされると、1つ以上のサブスクライブされたイベントが発生するたびに、webhookが送信されます。 -You can create up to {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %} webhooks for each event on each installation target {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}({% data variables.product.prodname_ghe_server %} instance, specific organization, or specific repository).{% else %}(specific organization or specific repository).{% endif %} +作成できるwebhookは、それぞれのインストールターゲット{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}({% data variables.product.prodname_ghe_server %} のインスタンス、特定のOrganization、あるいは特定のリポジトリ){% else %}(特定のOrganizationもしくは特定のリポジトリ){% endif %}上の各イベントに対して最大{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %}です。 ### イベント {% data reusables.webhooks.webhooks_intro %} -Each event corresponds to a certain set of actions that can happen to your organization and/or repository. For example, if you subscribe to the `issues` event you'll receive detailed payloads every time an issue is opened, closed, labeled, etc. +それぞれのイベントは、Organizationやリポジトリに生じうる一連のアクションに対応します。 たとえば、`issues`イベントにサブスクライブしているなら、Issueのオープン、クローズ、ラベル付けなどが生じるたびに詳細なペイロードを受信することになります。 -See "[Webhook event payloads](/webhooks/event-payloads)" for the list of available webhook events and their payloads. +利用できるwebhookのイベントとそれらのペイロードのリストについては「[webhookイベントのペイロード](/webhooks/event-payloads)」を参照してください。 -### Ping event +### Pingイベント {% data reusables.webhooks.ping_short_desc %} -For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. +`ping`イベントのwebhookのペイロードに関する詳細な情報については[`ping`](/webhooks/event-payloads/#ping)イベントを参照してください。 [org-hooks]: /rest/reference/orgs#webhooks/ -[repo-hooks]: /v3/repos/hooks/ +[repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/ja-JP/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md index 0d5384fc43..bf6b953cba 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md @@ -1,6 +1,6 @@ --- -title: Configuring your server to receive payloads -intro: Learn to set up a server to manage incoming webhook payloads. +title: ペイロードを受信するようサーバーを設定する +intro: 受信するwebhookのペイロードを管理するためのサーバー設定を学んでください。 redirect_from: - /webhooks/configuring versions: @@ -11,31 +11,31 @@ versions: -Now that our webhook is ready to deliver messages, we'll set up a basic Sinatra server to handle incoming payloads. +webhookがメッセージを配信する準備ができたので、受信するペイロードを処理するための基本的なSinatraサーバーをセットアップしましょう。 -Recall that we specifically set our webhook URL to `http://localhost:4567/payload`. Since we're developing locally, we'll need to expose our local development environment to the Internet, so that GitHub can send out messages, and our local server can process them. +webhookのURLは`http://localhost:4567/payload`に設定したことを思い出してください。 開発をローカルで行っているので、ローカルの開発環境をインターネットに公開し、GitHubがメッセージを送信して、ローカルサーバーでそれを処理できるようにしてやらなければなりません。 注釈: このプロジェクトの完全なソースコードは、[platform-samplesリポジトリ][platform samples]からダウンロードできます。 -### Using ngrok +### ngrokの利用 -First, we'll install a program to expose our local host to the Internet. We'll use ngrok to do this. [ngrok is a free download](https://ngrok.com/download) available for all major operating systems. +最初に、ローカルホストをインターネットに公開するプログラムをインストールします。 そのためにngrokを使用します。 すべての主要なオペレーティングシステムについて、[ngrokは無料でダウンロード](https://ngrok.com/download)できます。 -When you're done with that, you can expose your localhost by running `./ngrok http 4567` on the command line. You should see a line that looks something like this: +ダウンロードができたら、コマンドラインで`./ngrok http 4567`と実行すればローカルホストを公開できます。 以下のような行が表示されるはずです。 ```shell $ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567 ``` -Copy that funky `*.ngrok.io` URL! We're now going to go *back* to the Payload URL and pasting this server into that field. It should look something like `http://7e9ea9dc.ngrok.io/payload`. +この格好いい`*.ngrok.io` というURLをコピーしてください! ここでペイロードのURLに*もどり*、このサーバーをそのフィールドに貼り付けます。 `http://7e9ea9dc.ngrok.io/payload`のようになるはずです。 -By doing this, we've set ourselves up to expose our localhost at path `/payload` to the Internet. +こうすることで、ローカルホストを`/payload`というパスでインターネットに公開するようセットアップできました。 -### Writing the server +### サーバーの作成 -Now comes the fun part! We want our server to listen to `POST` requests, at `/payload`, because that's where we told GitHub our webhook URL was. Since ngrok is exposing our local environment, we don't need to set up a real server somewhere online, and can happily test out our code locally. +ここからが面白いところです! サーバーを`/payload`で`POST`リクエストに対して待ち受けさせたいですが、これはGitHubにそこがwebhookのURLだと伝えたからです。 ngrokはローカル環境を公開しているので、オンラインでどこかに本物のサーバーをセットアップする必要はなく、ローカルでコードをうまくテストできます。 -Let's set up a little Sinatra app to do something with the information. Our initial setup might look something like this: +小さなSinatraのアプリケーションをセットアップして、この情報で何かをさせてみましょう。 初期のセットアップは以下のようになるでしょう。 ``` ruby require 'sinatra' @@ -47,11 +47,11 @@ post '/payload' do end ``` -(シナトラの仕組みに詳しくない方は、[Sinatraのガイド][Sinatra]を読むことをお勧めします。) +(Sinatraの仕組みに詳しくない方は、[Sinatraのガイド][Sinatra]を読むことをお勧めします。) このサーバーを起動してください。 -Since we set up our webhook to listen to events dealing with `Issues`, go ahead and create a new Issue on the repository you're testing with. Once you create it, switch back to your terminal. You should see something like this in your output: +webhookは`Issues`と関連するイベントを待ち受けるようにセットアップしたので、先へ進んで新しいIssueをテストしているリポジトリで作成してください。 作成できたら、ターミナルに戻ってください。 以下のような出力があるでしょう。 ```shell $ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server.rb @@ -62,9 +62,9 @@ $ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server. > I got some JSON: {"action"=>"opened", "issue"=>{"url"=>"... ``` -Success! You've successfully configured your server to listen to webhooks. Your server can now process this information any way you see fit. For example, if you were setting up a "real" web application, you might want to log some of the JSON output to a database. +成功です! webhookを待ち受けるようにサーバーを設定することに成功しました。 これでサーバーは、適切だと考えられる方法でこの情報を処理できるようになりました。 たとえば、「本物の」Webアプリケーションをセットアップしているなら、JSONの出力をデータベースに記録したいかもしれません。 -For additional information on working with webhooks for fun and profit, head on over to the [Testing Webhooks](/webhooks/testing) guide. +楽しみと利益のためにwebhookを扱うための追加情報については、[webhookのテスト](/webhooks/testing)ガイドを参照してください。 [platform samples]: https://github.com/github/platform-samples/tree/master/hooks/ruby/configuring-your-server [Sinatra]: http://www.sinatrarb.com/ diff --git a/translations/ja-JP/content/developers/webhooks-and-events/creating-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/creating-webhooks.md index 0f926096ff..12f1866359 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/creating-webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/creating-webhooks.md @@ -1,6 +1,6 @@ --- -title: Creating webhooks -intro: 'Learn to build a webhook, choosing the events your webhook will listen for on {% data variables.product.prodname_dotcom %} and how to set up a server to receive and manage the webhook payload.' +title: webhookの作成 +intro: 'webhookの構築、webhookが{% data variables.product.prodname_dotcom %}上で待ち受けるイベントの選択、webhookのペイロードを受信して管理するサーバーのセットアップ方法を学んでください。' redirect_from: - /webhooks/creating versions: @@ -11,59 +11,59 @@ versions: -Now that we understand [the basics of webhooks][webhooks-overview], let's go through the process of building out our own webhook powered integration. In this tutorial, we'll create a repository webhook that will be responsible for listing out how popular our repository is, based on the number of Issues it receives per day. +[webhookの基礎][webhooks-overview]を理解したので、webhookで動作する独自のインテグレーションオン構築プロセスを見ていきましょう。 このチュートリアルでは、1日あたりに受け取るIssueのの数に基づいて、リポジトリの人気の度合いをリストする役目を持つリポジトリwebhookを作成します。 -Creating a webhook is a two-step process. You'll first need to set up how you want your webhook to behave through {% data variables.product.product_name %}--what events should it listen to. After that, you'll set up your server to receive and manage the payload. +webhookの作成は、2ステップのプロセスです。 まず、webhookを{% data variables.product.product_name %}を通じてどのように動作させたいのかをセットアップする必要があります。これはすなわち、どのイベントを待ち受けるのかということです。 その後、ペイロードを受信して管理するようにサーバーをセットアップします。 {% data reusables.webhooks.webhooks-rest-api-links %} -### Setting up a Webhook +### webhookのセットアップ -You can install webhooks on an organization or on a specific repository. +webhookは、Organizationもしくは特定のリポジトリにインストールできます。 -To set up a webhook, go to the settings page of your repository or organization. From there, click **Webhooks**, then **Add webhook**. +webhookをセットアップするには、リポジトリもしくはOrganizationのsettings（設定）ページにアクセスしてください。 そこから**Webhooks**をクリックし、続いて**Add webhook（webhookの追加）**をクリックしてください。 -Alternatively, you can choose to build and manage a webhook [through the Webhooks API][webhook-api]. +あるいは、[Webhooks APIを通じて][webhook-api]webhookの構築と管理を行うこともできます。 -Webhooks require a few configuration options before you can make use of them. We'll go through each of these settings below. +webhookには、利用を開始する前にいくつかの設定オプションが必要です。 以下、それぞれの設定について見ていきます。 -### Payload URL +### ペイロードURL {% data reusables.webhooks.payload_url %} -Since we're developing locally for our tutorial, let's set it to `http://localhost:4567/payload`. We'll explain why in the [Configuring Your Server](/webhooks/configuring/) docs. +チュートリアルではローカルで開発をしているので、`http://localhost:4567/payload`に設定しましょう。 その理由は[サーバーの設定](/webhooks/configuring/)ドキュメントで説明します。 -### Content Type +### コンテントタイプ -{% data reusables.webhooks.content_type %} For this tutorial, the default content type of `application/json` is fine. +{% data reusables.webhooks.content_type %} このチュートリアルでは、デフォルトのコンテントタイプを`application/json`にしておけば問題ありません。 -### Secret +### シークレット {% data reusables.webhooks.secret %} -### SSL Verification +### SSLの検証 {% data reusables.webhooks.webhooks_ssl %} ### Active -デフォルトでは、webhookの配信は「Active」です。 You can choose to disable the delivery of webhook payloads by deselecting "Active." +デフォルトでは、webhookの配信は「Active」です。 「Active」の選択を解除することで、webhookのペイロードの配信を無効化できます。 ### イベント -Events are at the core of webhooks. These webhooks fire whenever a certain action is taken on the repository, which your server's payload URL intercepts and acts upon. +イベントは、webhookの中核です。 これらのwebhookは、リポジトリで特定のアクションが行われたときに動作し、それがサーバーのペイロードURLで受信され、処理が行われます。 -A full list of webhook events, and when they execute, can be found in [the webhooks API][hooks-api] reference. +webhookイベントと、それらのイベントがいつ動作するのかの完全なリストは[webhook API][hooks-api]リファレンスにあります。 -Since our webhook is dealing with Issues in a repository, we'll click **Let me select individual events** and then **Issues**. Make sure you select **Active** to receive issue events for triggered webhooks. You can also select all events using the default option. +ここでのwebhookはリポジトリ内のIssueを扱うので、**Let me select individual events（個別のイベントを選択する）**をクリックし、そして**Issue**をクリックしてください。 トリガーされたwebhookに対するIssueイベントを受信できるよう、必ず**Active**を選択してください。 また、デフォルトオプションを使ってすべてのイベントを選択することもできます。 -When you're finished, click **Add webhook**. いかがですか。 Now that you created the webhook, it's time to set up our local server to test the webhook. Head on over to [Configuring Your Server](/webhooks/configuring/) to learn how to do that. +完了したら、**Add webhook（webhookの追加）**をクリックしてください。 ふう！ これでwebhookができたので、ローカルサーバーをセットアップしてwebhookをテストしましょう。 その方法は[サーバーの設定](/webhooks/configuring/)を見てください。 -#### Wildcard Event +#### ワイルドカードイベント -To configure a webhook for all events, use the wildcard (`*`) character to specify the webhook events. When you add the wildcard event, we'll replace any existing events you have configured with the wildcard event and send you payloads for all supported events. You'll also automatically get any new events we might add in the future. +すべてのイベントに対してwebhookを設定するには、ワイルドカード（`*`）文字を使ってwebhookイベントを指定してください。 ワイルドカードイベントを追加すると、設定されたすべての既存のイベントはワイルドカードイベントで置き換えられ、サポートされるすべてのイベントについてペイロードが送信されます。 また、将来追加される可能性のある新しいイベントも自動的に受信されるようになります。 [webhooks-overview]: /webhooks/ -[webhook-api]: /v3/repos/hooks/ +[webhook-api]: /rest/reference/repos#hooks [hooks-api]: /webhooks/#events diff --git a/translations/ja-JP/content/developers/webhooks-and-events/events.md b/translations/ja-JP/content/developers/webhooks-and-events/events.md index 65642f4d31..fade0f96d4 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/events.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/events.md @@ -1,6 +1,6 @@ --- title: イベント -intro: 'Your integrations can subscribe and react to events on {% data variables.product.prodname_dotcom %}.' +intro: 'インテグレーションは、{% data variables.product.prodname_dotcom %}上のイベントをサブスクライブし、反応できます。' mapTopic: true versions: free-pro-team: '*' diff --git a/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md b/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md index 7d024ff641..5a84bc623b 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md @@ -1,6 +1,6 @@ --- -title: GitHub event types -intro: 'For the {% data variables.product.prodname_dotcom %} Events API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.' +title: GitHubイベントの種類 +intro: '{% data variables.product.prodname_dotcom %} Event APIについて、各イベントの種類、{% data variables.product.prodname_dotcom %}上でのトリガーするアクション、各イベント固有のプロパティについて学んでください。' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /v3/activity/event_types @@ -11,7 +11,7 @@ versions: --- -The Events API can return different types of events triggered by activity on GitHub. Each event response contains shared properties, but has a unique `payload` object determined by its event type. The [Event object common properties](#event-object-common-properties) describes the properties shared by all events, and each event type describes the `payload` properties that are unique to the specific event. +Events APIは、GitHub上のアクティビティによってトリガーされる様々な種類のイベントを返します。 Each event response contains shared properties, but has a unique `payload` object determined by its event type. The [Event object common properties](#event-object-common-properties) describes the properties shared by all events, and each event type describes the `payload` properties that are unique to the specific event. {% if currentVersion == "free-pro-team@latest" %} @@ -40,7 +40,7 @@ The event objects returned from the Events API endpoints have the same structure #### Example WatchEvent event object -This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/v3/activity/events). +This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events). ``` Status: 200 OK @@ -198,22 +198,22 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -| キー | 種類 | 説明 | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `push_id` | `integer` | Unique identifier for the push. | -| `size` | `integer` | The number of commits in the push. | -| `distinct_size` | `integer` | The number of distinct commits in the push. | -| `ref` | `string` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/main`. | -| `head` | `string` | The SHA of the most recent commit on `ref` after the push. | -| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][sha]` | `string` | コミットのSHA。 | -| `commits[][message]` | `string` | コミットメッセージ。 | -| `commits[][author]` | `オブジェクト` | The git author of the commit. | -| `commits[][author][name]` | `string` | The git author's name. | -| `commits[][author][email]` | `string` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| キー | 種類 | 説明 | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `push_id` | `integer` | Unique identifier for the push. | +| `size` | `integer` | The number of commits in the push. | +| `distinct_size` | `integer` | The number of distinct commits in the push. | +| `ref` | `string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `head` | `string` | The SHA of the most recent commit on `ref` after the push. | +| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][sha]` | `string` | コミットのSHA。 | +| `commits[][message]` | `string` | コミットメッセージ。 | +| `commits[][author]` | `オブジェクト` | The git author of the commit. | +| `commits[][author][name]` | `string` | The git author's name. | +| `commits[][author][email]` | `string` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | ### ReleaseEvent diff --git a/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md b/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md index f172a97da0..7a7a452b62 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md @@ -10,7 +10,7 @@ versions: --- -Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/v3/issues/events) and the [Timeline Events API](/v3/issues/timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. +Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. @@ -129,7 +129,7 @@ A comment was added to the issue or pull request. | `html_url` | `string` | The HTML URL of the issue comment. | | `issue_url` | `string` | The HTML URL of the issue. | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `ユーザ` | `オブジェクト` | The person who commented on the issue. | | `created_at` | `string` | The timestamp indicating when the comment was added. | | `updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated. | @@ -152,19 +152,19 @@ A commit was added to the pull request's `HEAD` branch. {% data reusables.issue-events.timeline_events_object_properties %} -| 名前 | 種類 | 説明 | -| ------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `sha` | `string` | The SHA of the commit in the pull request. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `string` | The REST API URL to retrieve the commit. | -| `html_url` | `string` | The HTML URL of the commit. | -| `作者` | `オブジェクト` | The person who authored the commit. | -| `コミッター` | `オブジェクト` | The person who committed the commit on behalf of the author. | -| `ツリー` | `オブジェクト` | The Git tree of the commit. | -| `message` | `string` | コミットメッセージ。 | -| `親` | `array of objects` | A list of parent commits. | -| `verfication` | `オブジェクト` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/v3/git/commits/#signature-verification-object)." | -| `event` | `string` | The event value is `"committed"`. | +| 名前 | 種類 | 説明 | +| ------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sha` | `string` | The SHA of the commit in the pull request. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `string` | The REST API URL to retrieve the commit. | +| `html_url` | `string` | The HTML URL of the commit. | +| `作者` | `オブジェクト` | The person who authored the commit. | +| `コミッター` | `オブジェクト` | The person who committed the commit on behalf of the author. | +| `ツリー` | `オブジェクト` | The Git tree of the commit. | +| `message` | `string` | コミットメッセージ。 | +| `親` | `array of objects` | A list of parent commits. | +| `verfication` | `オブジェクト` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#signature-verification-object)." | +| `event` | `string` | The event value is `"committed"`. | ### connected @@ -583,7 +583,7 @@ The pull request was reviewed. | 名前 | 種類 | 説明 | | -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `ユーザ` | `オブジェクト` | The person who commented on the issue. | | `body` | `string` | The review summary text. | | `commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review. | diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md index c37e469883..77798fb53d 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -33,7 +33,7 @@ Each webhook event payload also contains properties unique to the event. You can {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)." -The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/v3/activity/events/). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. +The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. {% tip %} @@ -45,14 +45,14 @@ The unique properties for a webhook event are the same properties you'll find in HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: -| ヘッダ | 説明 | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | Name of the event that triggered the delivery. | +| ヘッダ | 説明 | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-GitHub-Event` | Name of the event that triggered the delivery. | | `X-GitHub-Delivery` | A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | +| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | | `X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} -| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} +| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. @@ -195,7 +195,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.content_reference_short_desc %} -Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" to create a new content attachment. +Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event. @@ -715,7 +715,7 @@ The webhook this event is configured on was deleted. This event will only listen ### package -Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. +Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. #### Availability @@ -775,7 +775,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus | -------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `zen` | `string` | Random string of GitHub zen. | | `hook_id` | `integer` | The ID of the webhook that triggered the ping. | -| `フック` | `オブジェクト` | The [webhook configuration](/v3/repos/hooks/#get-a-repository-webhook). | +| `フック` | `オブジェクト` | The [webhook configuration](/rest/reference/repos#get-a-repository-webhook). | | `hook[app_id]` | `integer` | When you register a new {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} sends a ping event to the **webhook URL** you specified during registration. The event contains the `app_id`, which is required for [authenticating](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) an app. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} @@ -969,24 +969,24 @@ Deliveries for `review_requested` and `review_request_removed` events will have #### Webhook payload object -| キー | 種類 | 説明 | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/main`. | -| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | -| `after` | `string` | The SHA of the most recent commit on `ref` after the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `string` | コミットのSHA。 | -| `commits[][timestamp]` | `string` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `string` | コミットメッセージ。 | -| `commits[][author]` | `オブジェクト` | The git author of the commit. | -| `commits[][author][name]` | `string` | The git author's name. | -| `commits[][author][email]` | `string` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | -| `commits[][added]` | `array` | An array of files added in the commit. | -| `commits[][modified]` | `array` | An array of files modified by the commit. | -| `commits[][removed]` | `array` | An array of files removed in the commit. | -| `pusher` | `オブジェクト` | The user who pushed the commits. | +| キー | 種類 | 説明 | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ref` | `string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | +| `after` | `string` | The SHA of the most recent commit on `ref` after the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][id]` | `string` | コミットのSHA。 | +| `commits[][timestamp]` | `string` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `string` | コミットメッセージ。 | +| `commits[][author]` | `オブジェクト` | The git author of the commit. | +| `commits[][author][name]` | `string` | The git author's name. | +| `commits[][author][email]` | `string` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| `commits[][added]` | `array` | An array of files added in the commit. | +| `commits[][modified]` | `array` | An array of files modified by the commit. | +| `commits[][removed]` | `array` | An array of files removed in the commit. | +| `pusher` | `オブジェクト` | The user who pushed the commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1022,7 +1022,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### repository_dispatch -This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event)" endpoint. +This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. #### Availability @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | キー | 種類 | 説明 | | -------- | -------- | -------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| +| `action` | `string` | 実行されたアクション. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1060,7 +1060,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% if currentVersion == "free-pro-team@latest"%} ### repository_import -{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/v3/migrations/source_imports/). +{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports). #### Availability @@ -1237,9 +1237,9 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ #### Webhook payload object -| キー | 種類 | 説明 | -| ------ | -------- | ------------------------------------------------------------------------------------------------------ | -| `Team` | `オブジェクト` | The [team](/v3/teams/) that was modified. **Note:** Older events may not include this in the payload. | +| キー | 種類 | 説明 | +| ------ | -------- | ----------------------------------------------------------------------------------------------------------------- | +| `Team` | `オブジェクト` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1268,7 +1268,7 @@ When a user is `created` or `deleted`. {% data reusables.webhooks.watch_short_desc %} -The event’s actor is the [user](/v3/users/) who starred a repository, and the event’s repository is the [repository](/v3/repos/) that was starred. +The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. #### Availability diff --git a/translations/ja-JP/content/github/administering-a-repository/about-releases.md b/translations/ja-JP/content/github/administering-a-repository/about-releases.md index 628e57ad37..3fdcd4b83f 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-releases.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-releases.md @@ -37,7 +37,7 @@ People with admin permissions to a repository can choose whether リポジトリ内のコードに依存しているリポジトリとパッケージを確認するために、依存関係グラフの [**依存関係**] タブを表示することができますが、それによって、新しいリリースの影響を受ける可能性があります。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 {% endif %} -リリースAPIを使用して、リリースアセットがダウンロードされた回数などの情報を収集することもできます。 詳しい情報については、「[リリース](/v3/repos/releases/)」を参照してください。 +リリースAPIを使用して、リリースアセットがダウンロードされた回数などの情報を収集することもできます。 詳しい情報については、「[リリース](/rest/reference/repos#releases)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} ### ストレージと帯域幅の容量 diff --git a/translations/ja-JP/content/github/administering-a-repository/about-required-status-checks.md b/translations/ja-JP/content/github/administering-a-repository/about-required-status-checks.md index fa947c0735..2cd46af3bd 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-required-status-checks.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-required-status-checks.md @@ -36,7 +36,7 @@ versions: ### 必須ステータスチェックのトラブルシューティング -同じ名前の Check と Status を持っており、その名前をステータスチェック必須とするようにした場合、Check と Status はどちらも必須です。 詳しい情報については、「[チェック](/v3/checks/)」を参照してください。 +同じ名前の Check と Status を持っており、その名前をステータスチェック必須とするようにした場合、Check と Status はどちらも必須です。 詳しい情報については、「[チェック](/rest/reference/checks)」を参照してください。 必須ステータスチェックをセットアップした場合、ブランチはマージする前にベースブランチに対して最新になっていなければなりません。 これによって、ブランチがベースブランチからの最新のコードでテストされたことが保証されます。 ブランチが古い場合、ベースブランチをブランチにマージする必要があります。 @@ -62,7 +62,7 @@ remote: error: Required status check "ci-build" is failing {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 テストマージコミットにステータスがある場合、必ずパスする必要があります。 それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 テストマージコミットに関する詳しい情報については、「[プルリクエスト](/v3/pulls/#response-1)」を参照してください。 +テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 テストマージコミットにステータスがある場合、必ずパスする必要があります。 それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 テストマージコミットに関する詳しい情報については、「[プルリクエスト](/rest/reference/pulls#response-1)」を参照してください。 ![マージコミットが競合しているブランチ](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md index 6baf5ff245..dd9e47a6fe 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,12 +15,15 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} + ### リリース管理について -特定のリリースのアクションを {% data variables.product.prodname_marketplace %} で公開することもできます。 詳しい情報については、「アクションを {% data variables.product.prodname_marketplace %} で公開する」を参照してください。 - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} +You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. 詳しい情報については、「アクションを {% data variables.product.prodname_marketplace %} で公開する」を参照してください。 +{% endif %} You can choose whether + {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/ja-JP/content/github/authenticating-to-github/about-githubs-ip-addresses.md index 6c6b43313c..ceeb571b6e 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-githubs-ip-addresses.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -12,7 +12,7 @@ versions: free-pro-team: '*' --- -{% data variables.product.prodname_dotcom %}のIPアドレスのリストは、[メタ](https://api.github.com/meta)APIエンドポイントから取得できます。 詳しい情報については、「[メタ](/v3/meta/)」を参照してください。 +{% data variables.product.prodname_dotcom %}のIPアドレスのリストは、[メタ](https://api.github.com/meta)APIエンドポイントから取得できます。 詳しい情報については、「[メタ](/rest/reference/meta)」を参照してください。 これらの範囲は[CIDR表記](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)になっています。 [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php)のようなツールを使って、CIDR表記をIPアドレスの範囲に変換できます。 diff --git a/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md index dc83100e8d..67d0f22555 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -12,7 +12,7 @@ versions: github-ae: '*' --- -個人アクセストークン（PAT）は、[GitHub API](/v3/auth/#via-oauth-and-personal-access-tokens) または[コマンドライン](#using-a-token-on-the-command-line)を使用するときに {% data variables.product.product_name %} への認証でパスワードの代わりに使用できます。 +個人アクセストークン（PAT）は、[GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) または[コマンドライン](#using-a-token-on-the-command-line)を使用するときに {% data variables.product.product_name %} への認証でパスワードの代わりに使用できます。 {% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. 詳しい情報については「[SAMLシングルサインオンでの認証について](/articles/about-authentication-with-saml-single-sign-on)」及び「[SAMLシングルサインオンで利用する個人アクセストークンの認可](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。{% endif %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md index aa161cf0da..6a22f1be09 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md @@ -29,7 +29,7 @@ versions: _チェック_は、行のアノテーション、より詳細なメッセージを提供するという点で_ステータス_とは異なっており、{% data variables.product.prodname_github_app %} でのみ利用できます。 -Organization オーナー、およびリポジトリにプッシュアクセスを持つユーザは、{% data variables.product.product_name %} の API でチェックおよびステータスを作成できます。 詳しい情報については、「[チェック](/v3/checks/)」および「[ ステータス](/v3/repos/statuses/)」を参照してください。 +Organization オーナー、およびリポジトリにプッシュアクセスを持つユーザは、{% data variables.product.product_name %} の API でチェックおよびステータスを作成できます。 詳しい情報については、「[チェック](/rest/reference/checks)」および「[ ステータス](/rest/reference/repos#statuses)」を参照してください。 ### チェック diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index 8bff3d1496..e8f5d83340 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -11,7 +11,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -リポジトリのアーカイブをダウンロードするには、ユーザあるいは Organization のマイグレーション用の API が利用できます。 詳しい情報については、「[移行](/v3/migrations/)」を参照してください。 +リポジトリのアーカイブをダウンロードするには、ユーザあるいは Organization のマイグレーション用の API が利用できます。 詳しい情報については、「[移行](/rest/reference/migrations)」を参照してください。 {% else %} リポジトリのダウンロードおよびバックアップを手動で実行できます。 @@ -21,15 +21,15 @@ versions: リポジトリもしくは wiki をクローンすると、プロジェクトのファイルやコミット履歴などの Git のデータだけがダウンロードされます。 {% data variables.product.product_name %}リポジトリの他の要素をローカルマシンにエクスポートするには、弊社の API が利用できます。 -- [問題](/v3/issues/#list-issues-for-a-repository) -- [プルリクエスト](/v3/pulls/#list-pull-requests) +- [問題](/rest/reference/issues#list-issues-for-a-repository) +- [プルリクエスト](/rest/reference/pulls#list-pull-requests) - [フォーク](/rest/reference/repos#list-forks) - [コメント](/rest/reference/issues#list-issue-comments-for-a-repository) - [マイルストーン](/rest/reference/issues#list-milestones) - [ラベル](/rest/reference/issues#list-labels-for-a-repository) - [Watcher](/rest/reference/activity#list-watchers) - [Starを付けたユーザ](/rest/reference/activity#list-stargazers) -- [プロジェクト](/v3/projects/#list-repository-projects) +- [プロジェクト](/rest/reference/projects#list-repository-projects) {% endif %} Once you have {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index df64df6c88..1aa03ce681 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ versions: ### ライセンスを見つけてもらう -[オープンソースの Ruby Gem Licensee](https://github.com/benbalter/licensee) は、リポジトリの *LICENSE* ファイルを、既知のライセンスの候補リストと比較します。 Licensee には [ライセンス API](/v3/licenses/) も用意されており、 {% data variables.product.product_name %} のリポジトリがどのようにライセンスされているかを[深く理解できます](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 自分のリポジトリで使用しているライセンスが、[ライセンス選択のウェブサイト](http://choosealicense.com/appendix/)にリストされていない場合は、[ライセンスの追加をリクエストする](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)ことができます。 +[オープンソースの Ruby Gem Licensee](https://github.com/benbalter/licensee) は、リポジトリの *LICENSE* ファイルを、既知のライセンスの候補リストと比較します。 Licensee には [ライセンス API](/rest/reference/licenses) も用意されており、 {% data variables.product.product_name %} のリポジトリがどのようにライセンスされているかを[深く理解できます](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 自分のリポジトリで使用しているライセンスが、[ライセンス選択のウェブサイト](http://choosealicense.com/appendix/)にリストされていない場合は、[ライセンスの追加をリクエストする](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)ことができます。 自分のリポジトリで使用しているライセンスが、ライセンス選択のウェブサイトにはリストされていて、リポジトリ ページのトップに明示的に表示されていない場合には、複数のライセンスが含まれるなど、複雑な状況が考えられます。 ライセンスを見つけてもらうために、*LICENSE* ファイルは単純にし、リポジトリの *README* ファイルなど、どこかでその複雑さに言及してください。 diff --git a/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md index 8347fb0df3..4606a49254 100644 --- a/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -43,4 +43,4 @@ To avoid these prompts, you can use Git password caching. 詳しい情報につ ### 参考リンク -- 「[OAuth App を認証する](/v3/oauth/)」 +- 「[OAuth App を認証する](/developers/apps/authorizing-oauth-apps)」 diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index fa6ce7cdf0..77591e2c59 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ versions: {% data variables.product.prodname_code_scanning %} がコードに潜在的な脆弱性またはエラーを見つけた場合、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。 アラートを引き起こしたコードを修正すると、{% data variables.product.prodname_dotcom %}はそのアラートを閉じます。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -{% data variables.product.prodname_code_scanning_capc %} は {% data variables.product.prodname_actions %} を使用します。 詳細については、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。 +{% data variables.product.prodname_code_scanning_capc %} は {% data variables.product.prodname_actions %} を使用します。 For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." {% data variables.product.prodname_code_scanning %} を始めるには、「[{% data variables.product.prodname_code_scanning %} の有効化](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)」を参照してください。 diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 0cc08d5b3c..878369e4a0 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -52,6 +52,32 @@ The default {% data variables.product.prodname_codeql_workflow %} uses the `pull For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +#### Avoiding unnecessary scans of pull requests + +You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. + +``` yaml +on: + push: + branches: [main, protected] + pull_request: + branches: [main] + paths-ignore: + - '**/*.md' + - '**/*.txt' +``` + +{% note %} + +**Notes** + +* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." +* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. + +{% endnote %} + +For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." + #### Scanning on a schedule If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." @@ -235,13 +261,13 @@ If you only want to run custom queries, you can disable the default security que #### Specifying directories to scan -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from scans by adding a `paths-ignore` array. +For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. ``` yaml -paths: +paths: - src paths-ignore: - - node_modules + - src/node_modules - '**/*.test.js' ``` @@ -254,7 +280,7 @@ paths-ignore: {% endnote %} -For C/C++, C#, and Java, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index b3965a51ab..68b36f9b81 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -41,7 +41,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie {% endtip %} {% endif %} -Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage worflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### サブスクリプションのリストを確認する diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/index.md b/translations/ja-JP/content/github/managing-your-work-on-github/index.md index 5e92264415..5e60b99910 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/index.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/index.md @@ -14,7 +14,7 @@ versions: ### 目次 -{% topic_link_in_list /managing-your-work-with-issues %} +{% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} @@ -27,6 +27,7 @@ versions: {% link_in_list /pinning-an-issue-to-your-repository %} {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} + {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} {% link_in_list /about-automation-for-issues-and-pull-requests-with-query-parameters %} {% link_in_list /file-attachments-on-issues-and-pull-requests %} @@ -35,12 +36,6 @@ versions: {% link_in_list /disabling-issues %} {% link_in_list /linking-a-pull-request-to-an-issue %} {% link_in_list /about-duplicate-issues-and-pull-requests %} -{% topic_link_in_list /labeling-issues-and-pull-requests %} - {% link_in_list /about-labels %} - {% link_in_list /creating-a-label %} - {% link_in_list /applying-labels-to-issues-and-pull-requests %} - {% link_in_list /editing-a-label %} - {% link_in_list /deleting-a-label %} {% topic_link_in_list /managing-project-boards %} {% link_in_list /about-project-boards %} {% link_in_list /creating-a-project-board %} diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md b/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md new file mode 100644 index 0000000000..b30fc95af4 --- /dev/null +++ b/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md @@ -0,0 +1,97 @@ +--- +title: Managing labels +intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +redirect_from: + - /articles/managing-Labels + - /articles/labeling-issues-and-pull-requests + - /github/managing-your-work-on-github/labeling-issues-and-pull-requests + - /articles/about-labels + - /github/managing-your-work-on-github/about-labels + - /articles/creating-and-editing-labels-for-issues-and-pull-requests + - /articles/creating-a-label + - /github/managing-your-work-on-github/creating-a-label + - /articles/customizing-issue-labels/ + - /articles/applying-labels-to-issues-and-pull-requests + - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests + - /articles/editing-a-label + - /github/managing-your-work-on-github/editing-a-label + - /articles/deleting-a-label + - /github/managing-your-work-on-github/deleting-a-label +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### ラベルについて + +作業を管理するとき、{% data variables.product.product_name %} ラベルを作成して Issue とプルリクエストを分類することができます。 You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. + +リポジトリへの読み取りアクセスを持つ人は、誰でもリポジトリのラベルを表示・検索できます。 ラベルの作成、編集、適用、削除をするためには、リポジトリに書き込みアクセスができなければなりません。 + +### About default labels + +{% data variables.product.product_name %} は、すべての新しいリポジトリにデフォルトのラベルを提供します。 You can use these default labels to help create a standard workflow in a repository. + +| ラベル | 説明 | +| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `documentation` | ドキュメンテーションに改善や追加が必要であることを示します{% endif %} +| `duplicate` | 同様の Issue あるいはプルリクエストを示します | +| `enhancement` | 新しい機能のリクエストを示します | +| `good first issue` | 初回のコントリビューターに適した Issue を示します | +| `help wanted` | メンテナーが Issue もしくはプルリクエストに助けを求めていることを示します | +| `invalid` | Issue あるいはプルリクエストに関連性がなくなったことを示します | +| `question` | Issue あるいはプルリクエストにさらなる情報が必要なことを示します | +| `wontfix` | Issue あるいはプルリクエストの作業が継続されないことを示します | + +リポジトリの作成時に、すべての新しいリポジトリにデフォルトのラベルが含められますが、後でそのラベルを編集または削除できます。 + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +Organization のオーナーは、Organization 内のリポジトリのためのデフォルトラベルをカスタマイズできます。 詳しい情報については、「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照してください。 +{% endif %} + +### ラベルの作成 + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. 検索フィールドの右にある、[**New label**] をクリックします。 +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### Issue およびプルリクエストへのラベルの適用 + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. 右上で [**Label**] をクリックし、続けて既存のラベル名を入力してください。 ラベルの名前をクリックして、選択されたアイテムに関連付けてください。 ![Issue のマイルストーン割り当てドロップダウンメニュー](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### ラベルの編集 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### ラベルの削除 +Deleting a label will remove the label from issues and pull requests. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.delete-label %} + +### 参考リンク +- [ラベルについて](/articles/about-labels) +- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/ja-JP/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md new file mode 100644 index 0000000000..1d722ae845 --- /dev/null +++ b/translations/ja-JP/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Managing your work with issues and pull requests +intro: '{% data variables.product.product_name %} で作業を管理するとき、Issue を作成してアイデアや機能強化、タスク、バグを追跡することができます。' +mapTopic: true +redirect_from: + - /github/managing-your-work-on-github/managing-your-work-with-issues + - /articles/managing-your-work-with-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 3bb8984868..4829d23a26 100644 --- a/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -163,7 +163,7 @@ You can filter by the visibility of the repository containing the issues and pul ### コミットステータスで検索 -コミットのステータスでプルリクエストをフィルタリングできます。 [ステータス API](/v3/repos/statuses/) または CI サービスを使っている場合、特に役立ちます。 +コミットのステータスでプルリクエストをフィルタリングできます。 [ステータス API](/rest/reference/repos#statuses) または CI サービスを使っている場合、特に役立ちます。 | 修飾子 | サンプル | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index d3cce27fb3..8d869a5418 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -40,7 +40,7 @@ Organization で SAML SSO を有効化する前に、IdP を Organization に接 ### SAML SSO で Organization にメンバーを追加する -SAML SSO を有効化後、Organization に新しいメンバーを追加する方法はいくつかあります。 Organization のオーナーは、{% data variables.product.product_name %} で手作業または API を使って、新しいメンバーを招待できます。 詳細は {} の「[Organization に参加するようユーザを招待する](/articles/inviting-users-to-join-your-organization)」および「[メンバー](/v3/orgs/members/#add-or-update-organization-membership)」を参照してください。 +SAML SSO を有効化後、Organization に新しいメンバーを追加する方法はいくつかあります。 Organization のオーナーは、{% data variables.product.product_name %} で手作業または API を使って、新しいメンバーを招待できます。 詳細は {} の「[Organization に参加するようユーザを招待する](/articles/inviting-users-to-join-your-organization)」および「[メンバー](/rest/reference/orgs#add-or-update-organization-membership)」を参照してください。 {% data reusables.organizations.team-synchronization %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 3b4e9e627f..e86afea2ef 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -12,7 +12,7 @@ versions: SCIM を実装せずに SAML SSO を使った場合、自動のプロビジョニング解除は行われません。 Organization のメンバーのアクセスが ldP から削除された後、セッションの有効期限が切れても、そのメンバーは Organization から自動的には削除されません。 認証済みのトークンにより、セッションが期限切れになった後も Organization へのアクセスが許可されます。 アクセスを削除するには、Organization の管理者は手動で認証済みのトークンを Organization から削除するか、その削除を SCIM で自動化します。 -Organization の {% data variables.product.product_name %} の SCIM API と連携できるアイデンティティプロバイダとして、以下のものがあります。 詳しい情報については{% data variables.product.product_name %}API ドキュメンテーション中の[SCIM](/v3/scim/) を参照してください。 +Organization の {% data variables.product.product_name %} の SCIM API と連携できるアイデンティティプロバイダとして、以下のものがあります。 詳しい情報については{% data variables.product.product_name %}API ドキュメンテーション中の[SCIM](/rest/reference/scim) を参照してください。 - Azure AD - Okta - OneLogin diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 4912c1f95c..afb5a4f33f 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -59,6 +59,7 @@ Organization レベルの設定を管理することに加え、Organization の | wiki の編集 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} | [悪用あるいはスパムの可能性があるコンテンツのレポート](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} | ラベルの適用 | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | | すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** | | マイルストーンの適用 | | **X** | **X** | **X** | **X** | | [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 4e35569710..d2be055386 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -429,9 +429,9 @@ An overview of some of the most common actions that are recorded as events in th | アクション | 説明 | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | -| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data.variables.product.prodname_dotcom %} for a draft security advisory. | -| `github_broadcast` | Triggered when {% data.variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | -| `github_withdraw` | Triggered when {% data.variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | | `オープン` | Triggered when someone opens a draft security advisory. | | `publish` | Triggered when someone publishes a security advisory. | | `さいお` | Triggered when someone reopens as draft security advisory. | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 3dc24a2810..b2f38c494a 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -23,7 +23,7 @@ IdP を通じた Team メンバーシップ変更はすべて、Team 同期ボ IdP グループに接続された Team を含めて {% data variables.product.prodname_dotcom %} Team のリポジトリに対するアクセスを管理するには、{% data variables.product.product_name %} で変更を行う必要があります。 詳細は「[Team について](/articles/about-teams)」および「[Organization リポジトリへの Team のアクセスを管理する](/articles/managing-team-access-to-an-organization-repository)」を参照してください。 -Team 同期を API で管理することもできます。 詳しい情報については「[Team の同期](/v3/teams/team_sync/)」を参照してください。 +Team 同期を API で管理することもできます。 詳しい情報については「[Team の同期](/rest/reference/teams#team-sync)」を参照してください。 ### 同期される Team のメンバーに関する要件 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md index 51ecaa9ad0..b2f201f7fc 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -26,7 +26,7 @@ Enterprise アカウントでは、複数の {% data variables.product.prodname_ For more information about member access and management, see "{% if currentVersion == "free-pro-team@latest" %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}." -GraphQL APIを利用したEnterpriseアカウントの管理に関する詳しい情報については、「[Enterprise アカウント](/v4/guides/managing-enterprise-accounts)」を参照してください。 +GraphQL APIを利用したEnterpriseアカウントの管理に関する詳しい情報については、「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 13eab7f183..df6206f65d 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -10,7 +10,7 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} -3. 左サイドバーで [**{% data variables.product.prodname_oauth_app %}s**] をクリックします。 ![左サイドバーの [{ site.data.variables.product.prodname_oauth_app }s] タブ](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. 左サイドバーで [**{% data variables.product.prodname_oauth_app %}s**] をクリックします。 ![{% data variables.product.prodname_oauth_app %}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) 3. [**Register a new application**] をクリックします。 4. [**Application name**] に "Jira" と入力します。 5. [**Homepage URL**] に、JIRA インスタンスの完全な URL を入力します。 diff --git a/translations/ja-JP/content/github/site-policy/github-privacy-statement.md b/translations/ja-JP/content/github/site-policy/github-privacy-statement.md index 7f8ee21b28..af5a9e23c1 100644 --- a/translations/ja-JP/content/github/site-policy/github-privacy-statement.md +++ b/translations/ja-JP/content/github/site-policy/github-privacy-statement.md @@ -201,7 +201,7 @@ Organizationでお客様のユーザ個人情報を処理する方法および #### サードパーティアプリケーション -お客様は、アカウントで「Developer Products」として知られるサードパーティアプリケーションを有効化または追加することを選択できます。 このDeveloper Productsは、お客様がGitHubを利用するにあたって、必ずしも必要なものではありません。 当社は、MarketplaceからDeveloper Productを購入する場合などお客様の要望があったとき、ユーザ個人情報を第三者と共有します。しかし、第三者のDeveloper Productの利用およびユーザ個人情報を共有する量の選択については、お客様がその責を負うものとします。 お客様のGitHubプロフィールを利用してDeveloper Productに認証した場合、どの情報が提供されるのか[API documentation](/v3/users/)で確認できます。 +お客様は、アカウントで「Developer Products」として知られるサードパーティアプリケーションを有効化または追加することを選択できます。 このDeveloper Productsは、お客様がGitHubを利用するにあたって、必ずしも必要なものではありません。 当社は、MarketplaceからDeveloper Productを購入する場合などお客様の要望があったとき、ユーザ個人情報を第三者と共有します。しかし、第三者のDeveloper Productの利用およびユーザ個人情報を共有する量の選択については、お客様がその責を負うものとします。 お客様のGitHubプロフィールを利用してDeveloper Productに認証した場合、どの情報が提供されるのか[API documentation](/rest/reference/users)で確認できます。 #### GitHub Pages diff --git a/translations/ja-JP/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/ja-JP/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index d7198c1cac..b88292324e 100644 --- a/translations/ja-JP/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/ja-JP/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -28,7 +28,7 @@ With respect to their personal information, California residents may exercise th California residents have the right to request from a business disclosure of the categories and specific pieces of personal information it has collected from them in the preceding 12 months, the categories of sources from which such personal information is collected, the business or commercial purpose for collecting or selling such personal information, and the categories of third parties with whom the business shares personal information. -If you request that a business disclose categories and specific pieces of personal information collected about you, you have the right to receive that information, free of charge, twice a year. The information may be delivered by mail or electronically and, if provided electronically, shall be in a portable and, to the extent technically feasible, readily usable format that allows the California resident to relatively easily transmit this information to another entity. You can use GitHub’s [User Migration API](/v3/migrations/users/) to access and download your data. Learn more [here](https://github.blog/2018-12-19-download-your-data/). +If you request that a business disclose categories and specific pieces of personal information collected about you, you have the right to receive that information, free of charge, twice a year. The information may be delivered by mail or electronically and, if provided electronically, shall be in a portable and, to the extent technically feasible, readily usable format that allows the California resident to relatively easily transmit this information to another entity. You can use GitHub’s [User Migration API](/rest/reference/migrations#users) to access and download your data. Learn more [here](https://github.blog/2018-12-19-download-your-data/). ### 2. Right to know whether your personal information is sold or disclosed for a business purpose and to whom diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index a0188d8814..d80618e9d8 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -54,8 +54,6 @@ To join {% data variables.product.prodname_sponsors %} as an organization, see " {% data reusables.sponsors.double-check-stripe-info %} -サポートされていない地域にお住まいで、{% data variables.product.prodname_sponsors %} のベータに参加が許可された場合は、ACH 送金または電信で支払いを受けられるように、銀行口座情報を指定する手順が、メールで届きます。 - {% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} diff --git a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md index 1ae92e50e3..43eff12fb0 100644 --- a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md +++ b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md @@ -10,7 +10,7 @@ versions: {% data variables.product.product_name %} は、個人アカウントの活動からリポジトリとプロファイルのメタデータを保存します。 個人アカウントのデータは、{% data variables.product.prodname_dotcom_the_website %} での設定または User Migration API によりエクスポートできます。 -{% data variables.product.product_name %} が保存するエクスポート用に使用できるデータの詳細については、「[ユーザー移行アーカイブをダウンロードする](/v3/migrations/users/#download-a-user-migration-archive)」と「[{% data variables.product.product_name %} のデータの使用について](/articles/about-github-s-use-of-your-data)」を参照してください。 +{% data variables.product.product_name %} が保存するエクスポート用に使用できるデータの詳細については、「[ユーザー移行アーカイブをダウンロードする](/rest/reference/migrations#download-a-user-migration-archive)」と「[{% data variables.product.product_name %} のデータの使用について](/articles/about-github-s-use-of-your-data)」を参照してください。 {% data variables.product.prodname_dotcom_the_website %} での設定により個人データのエクスポートをリクエストする場合、{% data variables.product.product_name %} は個人データを `tar.gz` ファイルにパッケージ化し、ダウンロードリンクを記載したメールをお使いのプライマリ メール アドレスに送信します。 diff --git a/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md b/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md index 9bbc4f1619..d4ab221511 100644 --- a/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md @@ -44,7 +44,7 @@ SSH URL を使用して、`git clone`、`git fetch`、`git pull` または `git {% tip %} -**ヒント**: SSH URL は、お使いのコンピュータにリポジトリを作成する際にも、または本番サーバーにコードをデプロイする安全な方法としても使用できます。 デプロイスクリプトで SSH エージェント転送を使用して、サーバー上のキーの管理を回避することもできます。 詳細は「[SSH エージェント転送を使用する](/v3/guides/using-ssh-agent-forwarding/)」を参照してください。 +**ヒント**: SSH URL は、お使いのコンピュータにリポジトリを作成する際にも、または本番サーバーにコードをデプロイする安全な方法としても使用できます。 デプロイスクリプトで SSH エージェント転送を使用して、サーバー上のキーの管理を回避することもできます。 詳細は「[SSH エージェント転送を使用する](/developers/overview/using-ssh-agent-forwarding)」を参照してください。 {% endtip %} diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index e2eae1e8cb..f09f50cc23 100644 --- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -36,7 +36,7 @@ You can also see a list of people who have contributed to the project's Python d {% tip %} -**ヒント:** リポジトリへのコミットのコントリビューターを一覧表示する方法については、「[リポジトリ](/v3/repos/#list-contributors)」を参照してください。 +**ヒント:** リポジトリへのコミットのコントリビューターを一覧表示する方法については、「[リポジトリ](/rest/reference/repos#list-contributors)」を参照してください。 {% endtip %} diff --git a/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md b/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md index 370fa517e2..8a8af18d9d 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md @@ -150,4 +150,4 @@ MIME タイプとは、ブラウザがリクエストするファイルの性質 ### 参考リンク - {% data variables.product.prodname_learning %} の [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) -- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)" +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index 79882065c7..8fea86d137 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -16,7 +16,7 @@ versions: Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} - 変更をプッシュしたユーザーがメールアドレスを検証していない。 詳しい情報については、「[メールアドレスの検証](/articles/verifying-your-email-address)」を参照してください。{% endif %} -- デプロイキーでプッシュしている。 サイトのリポジトリへのプッシュを自動化する場合は、かわりにマシンユーザーを設定できます。 詳しい情報については、「[デプロイキーを管理する](/v3/guides/managing-deploy-keys/#machine-users)」を参照してください。 +- デプロイキーでプッシュしている。 サイトのリポジトリへのプッシュを自動化する場合は、かわりにマシンユーザーを設定できます。 詳しい情報については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys#machine-users)」を参照してください。 - 公開元をビルドするようにCIサービスを設定していない。 たとえば、Travis CIは`gh-pages`ブランチを、セーフリストに追加しない限りビルドしません。 詳細は、Travis CIまたはCIサービスのドキュメンテーションで、「[ビルドのカスタマイズ](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)」を参照してください。 {% note %} diff --git a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md index 6131fceffd..623c032f8c 100644 --- a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md @@ -18,7 +18,7 @@ GraphQLサーバーと通信するには、適切なスコープを持つOAuth {% if currentVersion == "free-pro-team@latest" %} -[GraphQL Explorer](/v4/guides/using-the-explorer)の動作とマッチさせるためには、以下のスコープをリクエストしてください。 +[GraphQL Explorer](/graphql/guides/using-the-explorer)の動作とマッチさせるためには、以下のスコープをリクエストしてください。 {% else %} @@ -50,9 +50,9 @@ REST APIは多数のエンドポイントを持ちますが、GraphQL APIは単 ### GraphQLでの通信 -GraphQLの操作は複数行のJSONからなるので、GitHubはGraphQLの呼び出しを行うのに[Explorer](/v4/guides/using-the-explorer)を使うことをおすすめします。 cURLや、その他の任意のHTTPを使うライブラリも利用できます。 +GraphQLの操作は複数行のJSONからなるので、GitHubはGraphQLの呼び出しを行うのに[Explorer](/graphql/guides/using-the-explorer)を使うことをおすすめします。 cURLや、その他の任意のHTTPを使うライブラリも利用できます。 -RESTでは、[HTTPの動詞](/v3/#http-verbs)によって行う操作が決まります。 GraphQLでは、クエリを実行しているのかミューテーションを実行しているかにかかわらず、JSONエンコードされたボディを提供するので、HTTPの動詞は`POST`です。 例外は[イントロスペクションクエリ](/v4/guides/intro-to-graphql#discovering-the-graphql-api)で、これはエンドポイントへのシンプルな`GET`です。 GraphQLとRESTの比較に関する詳しい情報については「[RESTからGraphQLへの移行](/v4/guides/migrating-from-rest)」を参照してください。 +RESTでは、[HTTPの動詞](/rest#http-verbs)によって行う操作が決まります。 GraphQLでは、クエリを実行しているのかミューテーションを実行しているかにかかわらず、JSONエンコードされたボディを提供するので、HTTPの動詞は`POST`です。 例外は[イントロスペクションクエリ](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)で、これはエンドポイントへのシンプルな`GET`です。 GraphQLとRESTの比較に関する詳しい情報については「[RESTからGraphQLへの移行](/graphql/guides/migrating-from-rest-to-graphql)」を参照してください。 cURLを使ってGraphQLのクエリを行うには、JSONのペイロードを持つ`POST`リクエストを作成してください。 このペイロードには、`query`という文字列が含まれていなければなりません。 @@ -72,15 +72,15 @@ curl -H "Authorization: bearer token" -X POST -d " \ #### クエリ及びミューテーション操作について -GitHubのGraphQL APIで許されている操作は、_クエリ_と_ミューテーション_の2種類です。 GraphQLをRESTと比較すると、クエリは`GET`リクエストのような操作で、ミューテーションは`POST`/`PATCH`/`DELETE`のような操作です。 [ミューテーション名](/v4/mutation/)が、どの変更が実行されるのかを決定します。 +GitHubのGraphQL APIで許されている操作は、_クエリ_と_ミューテーション_の2種類です。 GraphQLをRESTと比較すると、クエリは`GET`リクエストのような操作で、ミューテーションは`POST`/`PATCH`/`DELETE`のような操作です。 [ミューテーション名](/graphql/reference/mutations)が、どの変更が実行されるのかを決定します。 -レート制限に関する情報については「[GraphQLのリソース制限](/v4/guides/resource-limitations/)」を参照してください。 +レート制限に関する情報については「[GraphQLのリソース制限](/graphql/overview/resource-limitations)」を参照してください。 クエリとミューテーションは似た形式を持っていますが、重要な違いがあります。 #### クエリについて -GraphQLのクエリは、指定したデータのみを返します。 クエリを作成する2は、[フィールド内のフィールド](/v4/guides/intro-to-graphql#field)（_入れ子になったサブフィールド_とも呼ばれます）を、[スカラー](/v4/scalar/)だけを返すまで指定します。 +GraphQLのクエリは、指定したデータのみを返します。 クエリを作成する2は、[フィールド内のフィールド](/graphql/guides/introduction-to-graphql#field)（_入れ子になったサブフィールド_とも呼ばれます）を、[スカラー](/graphql/reference/scalars)だけを返すまで指定します。 クエリは以下のような構造になります。 @@ -107,7 +107,7 @@ GraphQLのクエリは、指定したデータのみを返します。 クエリ この例の入力オブジェクトは`MuitationNameInput`であり、ペイロードオブジェクトは `MuitationNamePayload` です。 -[ミューテーション](/v4/mutation/)の参照では、リストされた_入力フィールド_は、入力オブジェクトとして渡すものです。 リストされている_返値フィールド_は、ペイロードオブジェクトとして渡すものです。 +[ミューテーション](/graphql/reference/mutations)の参照では、リストされた_入力フィールド_は、入力オブジェクトとして渡すものです。 リストされている_返値フィールド_は、ペイロードオブジェクトとして渡すものです。 実際の例については「[ミューテーションの例](#example-mutation)」を参照してください。 @@ -117,7 +117,7 @@ GraphQLのクエリは、指定したデータのみを返します。 クエリ {% note %} -**ノート**: Explorerを使っている場合は、変数を個別の[クエリ変数ペイン](/v4/guides/using-the-explorer/#using-the-variable-pane)に入力するようにして、JSONオブジェクトの前に`variables`という語を含めないようにしてください。 +**ノート**: Explorerを使っている場合は、変数を個別の[クエリ変数ペイン](/graphql/guides/using-the-explorer#using-the-variable-pane)に入力するようにして、JSONオブジェクトの前に`variables`という語を含めないようにしてください。 {% endnote %} @@ -207,7 +207,7 @@ query { * `repository(owner:"octocat", name:"Hello-World") {` - クエリを始めるにあたって、見つけたいのは[`repository`](/v4/object/repository/)オブジェクトです。 スキーマの検証によって、このオブジェクトが引数として`owner` と`name`を必要とすることが示されます。 + クエリを始めるにあたって、見つけたいのは[`repository`](/graphql/reference/objects#repository)オブジェクトです。 スキーマの検証によって、このオブジェクトが引数として`owner` と`name`を必要とすることが示されます。 * `issues(last:20, states:CLOSED) {` @@ -215,9 +215,9 @@ query { 以下は`issues`オブジェクトに関する詳細です。 - - [docs](/v4/object/repository/)は、このオブジェクトが`IssueConnection`という型を持つことを示します。 + - [docs](/graphql/reference/objects#repository)は、このオブジェクトが`IssueConnection`という型を持つことを示します。 - スキーマ検証によって、このオブジェクトが引数として`last`もしくは`first`の結果数を必要とすることが示されるので、`20`を渡します。 - - [docs](/v4/object/repository/)は、このオブジェクトが引数として`states`も取ることを示します。これはenumの[`IssueState`](/v4/enum/issuestate/)で、値として`OPEN`か`CLOSED`を取ります。 クローズされたIssueだけを見つけるために、`states`キーに`CLOSED`という値を渡します。 + - [docs](/graphql/reference/objects#repository)は、このオブジェクトが引数として`states`も取ることを示します。これはenumの[`IssueState`](/graphql/reference/enums#issuestate)で、値として`OPEN`か`CLOSED`を取ります。 クローズされたIssueだけを見つけるために、`states`キーに`CLOSED`という値を渡します。 * `edges {` @@ -225,9 +225,9 @@ query { * `node {` - ここで、エッジの端にあるノードを取り出します。 [`IssueConnection` docs](/v4/object/issueconnection)は、`IssueConnection`型の端にあるノードが`Issue`オブジェクトであることを示しています。 + ここで、エッジの端にあるノードを取り出します。 [`IssueConnection` docs](/graphql/reference/objects#issueconnection)は、`IssueConnection`型の端にあるノードが`Issue`オブジェクトであることを示しています。 -* `Issue`オブジェクトを取り出そうとしていることが分かっているので、[docs](/v4/object/issue)を見て返してほしいフィールドを指定できます。 +* `Issue`オブジェクトを取り出そうとしていることが分かっているので、[docs](/graphql/reference/objects#issue)を見て返してほしいフィールドを指定できます。 ```graphql title @@ -243,7 +243,7 @@ query { ここでは、`Issue`オブジェクトの`title`、`url`、`labels`フィールドを指定しています。 - `labels`フィールドは[`LabelConnection`](/v4/object/labelconnection/)という型を持っています。 `issues`オブジェクトと同じように、`labels`はコネクションなので、そのエッジを経て接続されたノードである`label`オブジェクトに到達しなければなりません。 このノードでは、返してほしい`label`オブジェクトフィールドを指定できます。ここでは`name`です。 + `labels`フィールドは[`LabelConnection`](/graphql/reference/objects#labelconnection)という型を持っています。 `issues`オブジェクトと同じように、`labels`はコネクションなので、そのエッジを経て接続されたノードである`label`オブジェクトに到達しなければなりません。 このノードでは、返してほしい`label`オブジェクトフィールドを指定できます。ここでは`name`です。 Octocatのパブリックな`Hello-World`リポジトリに対してこのクエリを実行しても、多くのラベルは返されないことに気づくかもしれません。 ラベルを使っている自分自身のリポジトリに対してこれを実行してみれば、違いがわかるでしょう。 @@ -285,7 +285,7 @@ mutation AddReactionToIssue { それでは、クエリから始めることはどのように知ることができるのでしょうか？ この時点ではまだわかりません。 -サーバー上のデータを変更したい（絵文字をIssueに添付する）ので、まずは役に立つミューテーションを探してスキーマを検索することから始めます。 リファレンスのドキュメントは、 [`addReaction`](/v4/mutation/addreaction)ミューテーションに`Adds a reaction to a subject.`という説明を付けています。完璧です！ +サーバー上のデータを変更したい（絵文字をIssueに添付する）ので、まずは役に立つミューテーションを探してスキーマを検索することから始めます。 リファレンスのドキュメントは、 [`addReaction`](/graphql/reference/mutations#addreaction)ミューテーションに`Adds a reaction to a subject.`という説明を付けています。完璧です！ このミューテーションのドキュメントには、3つの入力フィールドがリストアップされています。 @@ -337,13 +337,13 @@ IDが分かれば、ミューテーションで先に進むことができます - `addReaction`はミューテーションの名前です。 - `input`は必須の引数のキーです。 ミューテーションではこれは常に`input`になります。 - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}`は必須の引数の値です。 ミューテーションでは、これは常に入力フィールド（このケースでは`subjectId`と`content`）から構成される[入力オブジェクト](/v4/input_object/)（そのため波括弧です）になります。 + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}`は必須の引数の値です。 ミューテーションでは、これは常に入力フィールド（このケースでは`subjectId`と`content`）から構成される[入力オブジェクト](/graphql/reference/input-objects)（そのため波括弧です）になります。 - どの値がcontentとして使われるのかは、どのように分かるのでしょうか？ [`addReaction`のドキュメント](/v4/mutation/addreaction/)は、`content`フィールドが[`ReactionContent`](/v4/enum/reactioncontent/)という型を持っていることを教えてくれます。GitHubのIssueでは特定の絵文字リアクションだけがサポートされているので、これは[enum](/v4/enum)です。 リアクションとして使える値は以下のとおりです（いくつかの値は対応する絵文字の名前とは異なっていることに注意してください）。 + どの値がcontentとして使われるのかは、どのように分かるのでしょうか？ [`addReaction`のドキュメント](/graphql/reference/mutations#addreaction)は、`content`フィールドが[`ReactionContent`](/graphql/reference/enums#reactioncontent)という型を持っていることを教えてくれます。GitHubのIssueでは特定の絵文字リアクションだけがサポートされているので、これは[enum](/graphql/reference/enums)です。 リアクションとして使える値は以下のとおりです（いくつかの値は対応する絵文字の名前とは異なっていることに注意してください）。 {% data reusables.repositories.reaction_list %} -* 呼び出しの残りの部分は、ペイロードオブジェクトから構成されます。 ここでは、ミューテーションを行った後にサーバーから返してほしいデータを指定します。 これらの行は、[`addReaction`のドキュメント](/v4/mutation/addreaction)から来ています。指定できる返値フィールドは3つあります。 +* 呼び出しの残りの部分は、ペイロードオブジェクトから構成されます。 ここでは、ミューテーションを行った後にサーバーから返してほしいデータを指定します。 これらの行は、[`addReaction`のドキュメント](/graphql/reference/mutations#addreaction)から来ています。指定できる返値フィールドは3つあります。 - `clientMutationId` (`String`) - `reaction` (`Reaction!`) @@ -394,7 +394,7 @@ variables { {% note %} 先ほどの例では、`content`のフィールド値（これはミューテーション中で直接使われています）で、`HOORAY`の周りにクオートがありませんが、変数で使われる場合にはクオートがあることに気づいたかもしれません。 これには理由があります。 -* ミューテーション中で`content`を直接使う場合には、スキーマはその値が[`ReactionContent`](/v4/enum/reactioncontent/)型であることを期待しています。これは文字列ではなく_列挙型_です。 スキーマ検証は、列挙値の周りにクオートを加えるとエラーを投げます。これはクオートが文字列のために予約されているからです。 +* ミューテーション中で`content`を直接使う場合には、スキーマはその値が[`ReactionContent`](/graphql/reference/enums#reactioncontent)型であることを期待しています。これは文字列ではなく_列挙型_です。 スキーマ検証は、列挙値の周りにクオートを加えるとエラーを投げます。これはクオートが文字列のために予約されているからです。 * `content`を変数中で使う場合、変数のセクションは適切なJSONでなければならないので、クオートが必要になります。 スキーマ検証は、変数が実行時にミューテーションに渡されるとき、`ReactionContent`型を正しく解釈します。 列挙型と文字列の違いに関する詳しい情報については、[公式のGraphQL仕様](https://graphql.github.io/graphql-spec/June2018/#sec-Enums)を参照してください。 diff --git a/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md b/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md index 6b86eaf251..d2e3589830 100644 --- a/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md +++ b/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md @@ -12,7 +12,7 @@ versions: ### GraphQLの用語 -GitHub GraphQL APIは、GitHub REST APIからのアーキテクチャ及び概念的な移行を表すものです。 GraphQL APIの[リファレンスドキュメント](/v4/)では、いくつかの新しい用語が登場することになるでしょう。 +GitHub GraphQL APIは、GitHub REST APIからのアーキテクチャ及び概念的な移行を表すものです。 GraphQL APIの[リファレンスドキュメント](/graphql)では、いくつかの新しい用語が登場することになるでしょう。 ### スキーマ @@ -30,11 +30,11 @@ GitHub GraphQL APIは、GitHub REST APIからのアーキテクチャ及び概 ### 引数 -引数は、特定のフィールドに添付されるキー/値ペアの集合です。 フィールドの中には、引数を必要とするものがあります。 [ミューテーション](/v4/guides/forming-calls#about-mutations)は引数として入力オブジェクトを必要とします。 +引数は、特定のフィールドに添付されるキー/値ペアの集合です。 フィールドの中には、引数を必要とするものがあります。 [ミューテーション](/graphql/guides/forming-calls-with-graphql#about-mutations)は引数として入力オブジェクトを必要とします。 ### Implementation -GraphQLのスキーマは、_implements_という語を使ってオブジェクトが[インターフェース](/v4/interface)からどのように継承するかを定義することがあります。 +GraphQLのスキーマは、_implements_という語を使ってオブジェクトが[インターフェース](/graphql/reference/interfaces)からどのように継承するかを定義することがあります。 以下は、インターフェース`X`とオブジェクト`Y`の仮想的な例です。 @@ -55,13 +55,13 @@ type Y implements X { リファレンスドキュメントには、以下のような記述があります。 -* 各[オブジェクト](/v4/object)は、**Implements**の下に_継承元の_インターフェースを並べます。 +* 各[オブジェクト](/graphql/reference/objects)は、**Implements**の下に_継承元の_インターフェースを並べます。 -* 各[インターフェース](/v4/interface)は、** Implementations**の下に_継承先_のオブジェクトを並べます。 +* 各[インターフェース](/graphql/reference/interfaces)は、** Implementations**の下に_継承先_のオブジェクトを並べます。 ### コネクション -コネクションを使うと、同じ呼び出しの一部として関連するオブジェクトに対するクエリを実行できます。 コネクションを使うと、REST APIでは複数の呼び出しを使うような場合に、単一のGraphQL呼び出しを使うことができます。 詳しい情報については「[RESTからGraphQLへの移行](/v4/guides/migrating-from-rest)」を参照してください。 +コネクションを使うと、同じ呼び出しの一部として関連するオブジェクトに対するクエリを実行できます。 コネクションを使うと、REST APIでは複数の呼び出しを使うような場合に、単一のGraphQL呼び出しを使うことができます。 詳しい情報については「[RESTからGraphQLへの移行](/graphql/guides/migrating-from-rest-to-graphql)」を参照してください。 点を線でつなぎ、グラフを図示すると役立ちます。 点はノードで、線はエッジです。 コネクションは、ノード間の関係を定義します。 @@ -71,7 +71,7 @@ type Y implements X { ### ノード -_ノード_ はオブジェクトの総称です。 ノードは直接ルックアップすることもできますが、コネクションを通じて関連するノードにアクセスすることもできます。 [スカラー](/v4/scalar)を返さない`node`を指定する場合は、すべてのフィールドがスカラーを返すまでサブフィールドを含めなければなりません。 REST APIを通じてノードIDにアクセスし、それらをGraphQLクエリで利用することに関する情報については、「[グローバルノードIDの利用](/v4/guides/using-global-node-ids)」を参照してください。 +_ノード_ はオブジェクトの総称です。 ノードは直接ルックアップすることもできますが、コネクションを通じて関連するノードにアクセスすることもできます。 [スカラー](/graphql/reference/scalars)を返さない`node`を指定する場合は、すべてのフィールドがスカラーを返すまでサブフィールドを含めなければなりません。 REST APIを通じてノードIDにアクセスし、それらをGraphQLクエリで利用することに関する情報については、「[グローバルノードIDの利用](/graphql/guides/using-global-node-ids)」を参照してください。 ## GraphQL APIの発見 @@ -130,4 +130,4 @@ query { {% endnote %} - クエリの実行に関する詳しい情報については「[GraphQLでの呼び出しの作成](/v4/guides/forming-calls)」を参照してください。 + クエリの実行に関する詳しい情報については「[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。 diff --git a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md index 5ca8c91065..300a4f90b4 100644 --- a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md @@ -33,7 +33,7 @@ Enterprise APIを利用すると、以下のことができます。 - Enterpriseアカウントへの管理者の招待。 - Enterpriseアカウント内での新しいOrganizationの作成。 -Enterprise Accounts APIで利用できるフィールドのリストについては、「[Enterprise Accounts APIのGraphQLフィールドと型](/v4/guides/managing-enterprise-accounts/#graphql-fields-and-types-for-the-enterprise-accounts-api)」を参照してください。 +Enterprise Accounts APIで利用できるフィールドのリストについては、「[Enterprise Accounts APIのGraphQLフィールドと型](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)」を参照してください。 ### EnterpriseアカウントでGraphQLを使い始める @@ -187,12 +187,12 @@ fragment repositories on Organization { } ``` -GraphQLの使い始め方に関する詳しい情報については「[GraphQLの紹介](/v4/guides/intro-to-graphql/)」及び「[GraphQLでの呼び出しの作成](/v4/guides/forming-calls/)」を参照してください。 +GraphQLの使い始め方に関する詳しい情報については「[GraphQLの紹介](/graphql/guides/introduction-to-graphql)」及び「[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。 ### Enterprise Accounts APIでのGraphQLのフィールドと型 Enterprise Accounts APIで利用できる新しいクエリ、ミューテーション、スキーマ定義された型の概要を以下に示します。 -For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/v4/). +For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql). -GitHub上のGraphQL Explorer内からリファレンスドキュメントにアクセスできます。 詳しい情報については「[Explorerの利用](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)」を参照してください。 認証やレート制限の詳細など その他の情報については[ガイド](/v4/guides)を参照してください。 +GitHub上のGraphQL Explorer内からリファレンスドキュメントにアクセスできます。 詳しい情報については「[Explorerの利用](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)」を参照してください。 認証やレート制限の詳細など その他の情報については[ガイド](/graphql/guides)を参照してください。 diff --git a/translations/ja-JP/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/ja-JP/content/graphql/guides/migrating-from-rest-to-graphql.md index a8dd7631db..0e8c057f42 100644 --- a/translations/ja-JP/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/ja-JP/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: RESTからGraphQLへの移行は、APIロジックの大きな変化を示します。 スタイルとしてのRESTと仕様としてのGraphQLとの違いのために、REST APIの呼び出しをGraphQL APIのクエリに1対1で置き換えることは難しく、しばしば望ましくないことになります。 移行の具体的な例を以下に示しました。 -コードを [REST API](/v3) から GraphQL API に移行するには、以下を行います。 +To migrate your code from the [REST API](/rest) to the GraphQL API: - [GraphQL仕様](https://graphql.github.io/graphql-spec/June2018/)のレビュー -- GitHubの[GraphQLスキーマ](/v4/reference/)のレビュー +- Review GitHub's [GraphQL schema](/graphql/reference) - 現在のコードによるGitHub REST APIとのやりとりの考慮 -- [グローバルノードID](/v4/guides/using-global-node-ids)を使ったAPIバージョン間でのオブジェクトの参照 +- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions GraphQLによる重要な利点には以下があります。 @@ -53,12 +53,12 @@ query { } ``` -別の例を考えてみましょう。プルリクエストのリストを取得して、それぞれがマージ可能かをチェックします。 REST APIの呼び出しは、プルリクエストとその[サマリ表現](/v3/#summary-representations)のリストを取得します。 +別の例を考えてみましょう。プルリクエストのリストを取得して、それぞれがマージ可能かをチェックします。 A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -プルリクエストがマージ可能かを判断するためには、個別にそれぞれのプルリクエストの[詳細な表現](/v3/#detailed-representations)（大きなペイロード）を取得し、その`mergeable`属性がtrueかfalse下をチェックしなければなりません。 +Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:numbe } ``` -プルリクエストの番号で[変数を置き換える](/v4/guides/forming-calls/#working-with-variables)ことで、このクエリの力を拡張することもできます。 +You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. ## 例：強力な型付け GraphQLスキーマは強く型付けされており、データの扱いが安全になっています。 -IssueもしくはプルリクエストにGraphQLの[ミューテーション](/v4/mutation)を使ってコメントを追加する例で、間違って[`clientMutationId`](/v4/mutation/addcomment/)の値に文字列ではなく整数値を指定してしまったとしましょう。 +Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): ```graphql mutation { diff --git a/translations/ja-JP/content/graphql/guides/using-global-node-ids.md b/translations/ja-JP/content/graphql/guides/using-global-node-ids.md index e5076208ce..1fa831871e 100644 --- a/translations/ja-JP/content/graphql/guides/using-global-node-ids.md +++ b/translations/ja-JP/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ GitHubのほとんどのオブジェクト（ユーザ、Issue、プルリクエ {% note %} -**ノート:** RESTでは、グローバルノードIDフィールドは`node_id`という名前になっています。 GraphQLでは、`node`インターフェースの`id`フィールドです。 GraphQLで「ノード」が何を意味するかを再確認するため、「[GraphQLの紹介](/v4/guides/intro-to-graphql/#node)」を参照してください。 +**ノート:** RESTでは、グローバルノードIDフィールドは`node_id`という名前になっています。 GraphQLでは、`node`インターフェースの`id`フィールドです。 For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." {% endnote %} @@ -29,7 +29,7 @@ GitHubのほとんどのオブジェクト（ユーザ、Issue、プルリクエ ### 1. オブジェクトのノードIDを返すRESTのエンドポイントの呼び出し -[認証済みのユーザをリクエスト](/v3/users/#get-the-authenticated-user)した場合、 +If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { この種のノードをIDで見つけるクエリは、「ダイレクトノードルックアップ」と呼ばれています。 -このクエリを実行すると、`__typename`が[`User`](/v4/object/user/)であることが分かります。 +When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). ### 3. GraphQLでダイレクトノードルックアップを行う @@ -122,4 +122,4 @@ query { ### 移行におけるグローバルノードIDの利用 -REST API または GraphQL API を使用するインテグレーションを構築する場合、API バージョン間にわたってオブジェクトを簡単に参照できるように、グローバルノード ID を保持すると良いでしょう。 RESTとGraphQL間の移行の扱いに関する詳細な情報については「[RESTからGraphQLへの移行](/v4/guides/migrating-from-rest/)」を参照してください。 +REST API または GraphQL API を使用するインテグレーションを構築する場合、API バージョン間にわたってオブジェクトを簡単に参照できるように、グローバルノード ID を保持すると良いでしょう。 For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." diff --git a/translations/ja-JP/content/graphql/guides/using-the-explorer.md b/translations/ja-JP/content/graphql/guides/using-the-explorer.md index 0169da3ed7..e0ae302e14 100644 --- a/translations/ja-JP/content/graphql/guides/using-the-explorer.md +++ b/translations/ja-JP/content/graphql/guides/using-the-explorer.md @@ -13,11 +13,11 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -[GraphQL Explorer](/v4/explorer)は、「グラフィカルでインタラクティブなブラウザ内のGraphQL IDE」である[ GraphiQL](https://github.com/graphql/graphiql)のインスタンスです。 +[GraphQL Explorer](/graphql/overview/explorer)は、「グラフィカルでインタラクティブなブラウザ内のGraphQL IDE」である[ GraphiQL](https://github.com/graphql/graphiql)のインスタンスです。 {% note %} -**ノート**: {% data variables.product.prodname_dotcom %}はExplorer内での[ミューテーション](/v4/mutation/)を無効化していますが、独自のGraphiQLのインスタンスではミューテーションが利用できます。 +**ノート**: {% data variables.product.prodname_dotcom %}はExplorer内での[ミューテーション](/graphql/reference/mutations)を無効化していますが、独自のGraphiQLのインスタンスではミューテーションが利用できます。 {% endnote %} @@ -33,7 +33,7 @@ GraphiQLアプリケーションを使うには、https://github.com/skevy/graph #### GraphiQLの設定 -1. [OAuthトークン](/v4/guides/forming-calls#authenticating-with-graphql)を取得してください。 +1. [OAuthトークン](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql)を取得してください。 1. GraphiQLを起動してください。 1. GraphiQLの右上で、**Edit HTTP Headers（HTTPヘッダの編集）**をクリックしてください。 1. **Key**フィールドに、`Authorization`と入力してください。 **Value**フィールドには`Bearer `と入力してください。ここで、``は生成したOAuthトークンです。 ![graphiqlのヘッダー](/assets/images/developer/graphiql-headers.png) @@ -44,7 +44,7 @@ GraphiQLアプリケーションを使うには、https://github.com/skevy/graph {% note %} -**ノート**: メソッドが`POST`である理由に関する詳しい情報については「[GraphQLでの通信](/v4/guides/forming-calls#communicating-with-graphql)」を参照してください。 +**ノート**: メソッドが`POST`である理由に関する詳しい情報については「[GraphQLでの通信](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)」を参照してください。 {% endnote %} @@ -66,13 +66,13 @@ GraphQLスキーマ内のすべての型には、ドキュメントに編集さ {% note %} -**Docs**サイドバーには、「[リファレンス](/v4/)」の下にあるスキーマから自動的に生成されるものと同じ内容が含まれていますが、所々形式が異なっています。 +**Docs**サイドバーには、「[リファレンス](/graphql)」の下にあるスキーマから自動的に生成されるものと同じ内容が含まれていますが、所々形式が異なっています。 {% endnote %} ### 変数ペインの利用 -サンプルの呼び出しの中には、以下のように書かれる[変数](/v4/guides/forming-calls#working-with-variables)を含むものがあります。 +サンプルの呼び出しの中には、以下のように書かれる[変数](/graphql/guides/forming-calls-with-graphql#working-with-variables)を含むものがあります。 ```graphql query($number_of_repos:Int!){ @@ -90,7 +90,7 @@ variables { } ``` -これは、cURLの`POST`で呼び出しをサブミットするための正しいフォーマットです（[改行をエスケープ](/v4/guides/forming-calls#communicating-with-graphql)するかぎりにおいて）。 +これは、cURLの`POST`で呼び出しをサブミットするための正しいフォーマットです（[改行をエスケープ](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)するかぎりにおいて）。 この呼び出しをExplorerで実行したい場合は、メインペインに`query`セグメントを入力し、その下の**Query Variables（クエリ変数）**ペインに変数を入力してください。 Explorerからは`variable`という語は省略してください。 @@ -106,12 +106,12 @@ variables { ### エラーのトラブルシューティング -GraphQLは[イントロスペクション](/v4/guides/intro-to-graphql#discovering-the-graphql-api)可能なので、Explorerは以下をサポートしています。 +GraphQLは[イントロスペクション](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)可能なので、Explorerは以下をサポートしています。 * インテリジェントに現在のスキーマを先行して認識 * 入力中の検証エラープレビュー -正しい形式ではない、あるいは[スキーマ検証](/v4/guides/intro-to-graphql#schema)をパスしないクエリを入力すると、ポップアップがエラーを警告します。 そのクエリを実行すると、レスポンスペインにエラーが返されます。 +正しい形式ではない、あるいは[スキーマ検証](/graphql/guides/introduction-to-graphql#schema)をパスしないクエリを入力すると、ポップアップがエラーを警告します。 そのクエリを実行すると、レスポンスペインにエラーが返されます。 GraphQLのレスポンスには、`data`ハッシュや`errors`配列といったいくつかのキーが含まれます。 diff --git a/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md b/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md index 070d5d5ed7..20d5465d02 100644 --- a/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md +++ b/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md @@ -11,25 +11,25 @@ versions: 以下は、GraphQL API v4を使い始めるためのクイックリンクです。 -* [認証](/v4/guides/forming-calls/#authenticating-with-graphql) -* [ルートエンドポイント](/v4/guides/forming-calls/#the-graphql-endpoint) -* [スキーマイントロスペクション](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) -* [レート制限](/v4/guides/resource-limitations/) -* [RESTからの移行](/v4/guides/migrating-from-rest) +* [認証](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) +* [ルートエンドポイント](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) +* [スキーマイントロスペクション](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) +* [レート制限](/graphql/overview/resource-limitations) +* [RESTからの移行](/graphql/guides/migrating-from-rest-to-graphql) ### GraphQLについて [GraphQL](https://graphql.github.io/)データクエリ言語は、 -* **[仕様](https://graphql.github.io/graphql-spec/June2018/)です。**この仕様は、APIサーバー上の[スキーマ](/v4/guides/intro-to-graphql#schema)の正当性を決定します。 スキーマは、クライアントの呼び出しの正当性を決定します。 +* **[仕様](https://graphql.github.io/graphql-spec/June2018/)です。**この仕様は、APIサーバー上の[スキーマ](/graphql/guides/introduction-to-graphql#schema)の正当性を決定します。 スキーマは、クライアントの呼び出しの正当性を決定します。 * **[強く型付けされて](#about-the-graphql-schema-reference)います。**スキーマは、APIの型システムとすべてのオブジェクトの関係を定義します。 -* **[イントロスペクティブ](/v4/guides/intro-to-graphql#discovering-the-graphql-api)です。**クライアントは、スキーマに関する詳細を求めるためにスキーマに対してクエリを行えます。 +* **[イントロスペクティブ](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)です。**クライアントは、スキーマに関する詳細を求めるためにスキーマに対してクエリを行えます。 -* **[階層型](/v4/guides/forming-calls)です。**GraphQLの呼び出しの形は、返されるJSONデータの型を反映します。 [入れ子になったフィールド](/v4/guides/migrating-from-rest/#example-nesting)によって、1回のラウンドトリップで指定したデータだけをクエリで返してもらうことができます。 +* **[階層型](/graphql/guides/forming-calls-with-graphql)です。**GraphQLの呼び出しの形は、返されるJSONデータの型を反映します。 [入れ子になったフィールド](/graphql/guides/migrating-from-rest-to-graphql#example-nesting)によって、1回のラウンドトリップで指定したデータだけをクエリで返してもらうことができます。 -* **アプリケーション層です。**GraphQLはストレージモデルやデータベースクエリ言語ではありません。 _グラフ_はスキーマで定義されたグラフ構造を指し、[ノード](/v4/guides/intro-to-graphql#node)はオブジェクトを、[エッジ](/v4/guides/intro-to-graphql#edge)はオブジェクト間の関係を定義します。 APIは、データがどのように保存されているかに関係なく、スキーマ定義に従ってアプリケーションデータをトラバースして返します。 +* **アプリケーション層です。**GraphQLはストレージモデルやデータベースクエリ言語ではありません。 _グラフ_はスキーマで定義されたグラフ構造を指し、[ノード](/graphql/guides/introduction-to-graphql#node)はオブジェクトを、[エッジ](/graphql/guides/introduction-to-graphql#edge)はオブジェクト間の関係を定義します。 APIは、データがどのように保存されているかに関係なく、スキーマ定義に従ってアプリケーションデータをトラバースして返します。 ### GitHubがGraphQLを使う理由 @@ -39,15 +39,15 @@ GitHubがGraphQLに移行した理由の詳細については、オリジナル ### GraphQLのスキーマ参照について -サイドバー内のドキュメントは、{% data variables.product.prodname_dotcom %}のGraphQL[スキーマ](/v4/guides/intro-to-graphql/#discovering-the-graphql-api)から生成されます。 すべての呼び出しは、このスキーマに対して検証され、実行されます。 以下のドキュメントを使って、呼び出せるデータを見つけてください。 +サイドバー内のドキュメントは、{% data variables.product.prodname_dotcom %}のGraphQL[スキーマ](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)から生成されます。 すべての呼び出しは、このスキーマに対して検証され、実行されます。 以下のドキュメントを使って、呼び出せるデータを見つけてください。 -* 許可された操作：[クエリ](/v4/query)と[ミューテーション](/v4/mutation)。 +* 許可された操作：[クエリ](/graphql/reference/queries)と[ミューテーション](/graphql/reference/mutations)。 -* スキーマ定義型：[スカラー](/v4/scalar)、[オブジェクト](/v4/object)、[列挙](/v4/enum)、[インターフェース](/v4/interface)、[union](/v4/union)、[入力オブジェクト](/v4/input_object)。 +* スキーマ定義型：[スカラー](/graphql/reference/scalars)、[オブジェクト](/graphql/reference/objects)、[列挙](/graphql/reference/enums)、[インターフェース](/graphql/reference/interfaces)、[union](/graphql/reference/unions)、[入力オブジェクト](/graphql/reference/input-objects)。 -同じ内容には、[Explorer Docsサイドバー](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)からもアクセスできます。 GraphQL APIの呼び出しをうまく行うためには、ドキュメントとスキーマ検証の両方に依存しなければならないことがあります。 +同じ内容には、[Explorer Docsサイドバー](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)からもアクセスできます。 GraphQL APIの呼び出しをうまく行うためには、ドキュメントとスキーマ検証の両方に依存しなければならないことがあります。 -認証やレート制限の詳細など その他の情報については[ガイド](/v4/guides)を参照してください。 +認証やレート制限の詳細など その他の情報については[ガイド](/graphql/guides)を参照してください。 ### サポートのリクエスト diff --git a/translations/ja-JP/content/graphql/overview/breaking-changes.md b/translations/ja-JP/content/graphql/overview/breaking-changes.md index ee2e23082b..acb41a929e 100644 --- a/translations/ja-JP/content/graphql/overview/breaking-changes.md +++ b/translations/ja-JP/content/graphql/overview/breaking-changes.md @@ -16,7 +16,7 @@ versions: - **破壊的：** GraphQL APIに対する既存のクエリを損なう変更。 たとえば、フィールドの削除は破壊的変更です。 - **危険：** 既存のクエリを損なうことはないものの、クライアントの実行時の振る舞いに影響するかもしれない変更です。 enum値の追加は危険な変更の例です。 -私たちは、インテグレーターに安定したAPIを提供するよう努めています。 新しい機能が進化を続けている場合、それは[スキーマプレビュー](/v4/previews/)の背後でリリースしています。 +私たちは、インテグレーターに安定したAPIを提供するよう努めています。 新しい機能が進化を続けている場合、それは[スキーマプレビュー](/graphql/overview/schema-previews)の背後でリリースしています。 今後の破壊的変更のアナウンスは、遅くてもGraphQLスキーマに対して変更を行う3ヶ月前にアナウンスを行い、インテグレーターに必要な調整を行う時間を提供します。 変更は、四半期の初日（1月1日、4月1日、7月1日、10月1日）に適用されます。 たとえば、変更を1月115日にアナウンスした場合、その変更は7月1日に行われます。 diff --git a/translations/ja-JP/content/graphql/overview/changelog.md b/translations/ja-JP/content/graphql/overview/changelog.md index 9c9b039289..c5fa89869c 100644 --- a/translations/ja-JP/content/graphql/overview/changelog.md +++ b/translations/ja-JP/content/graphql/overview/changelog.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -破壊的変更には、既存のクエリを損なったり、クライアントの実行時の振る舞いに影響するかもしれない変更が含まれます。 破壊的変更とそれらが行われる時期のリストについては、[破壊的変更の履歴](/v4/breaking_changes)を参照してください。 +破壊的変更には、既存のクエリを損なったり、クライアントの実行時の振る舞いに影響するかもしれない変更が含まれます。 破壊的変更とそれらが行われる時期のリストについては、[破壊的変更の履歴](/graphql/overview/breaking-changes)を参照してください。 {% for entry in graphql.changelog %} ### {{ entry.date }}のスキーマ変更 diff --git a/translations/ja-JP/content/graphql/overview/public-schema.md b/translations/ja-JP/content/graphql/overview/public-schema.md index 61f1d091db..6976c6ef75 100644 --- a/translations/ja-JP/content/graphql/overview/public-schema.md +++ b/translations/ja-JP/content/graphql/overview/public-schema.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -GraphQL APIに対しては、直接[イントロスペクションを行え](/v4/guides/intro-to-graphql/#discovering-the-graphql-api)ます。 +GraphQL APIに対しては、直接[イントロスペクションを行え](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)ます。 あるいは、こちらから最新バージョンのパブリックスキーマをダウンロードすることもできます。 diff --git a/translations/ja-JP/content/graphql/overview/resource-limitations.md b/translations/ja-JP/content/graphql/overview/resource-limitations.md index 68b8a7124a..36db666a9d 100644 --- a/translations/ja-JP/content/graphql/overview/resource-limitations.md +++ b/translations/ja-JP/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## ノードの制限 -[スキーマ](/v4/guides/intro-to-graphql#schema)検証をパスするため、すべてのGraphQL API v4の[呼び出し](/v4/guides/forming-calls)は以下の標準を満たさなければなりません。 +To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: -* クライアントはすべての[コネクション](/v4/guides/intro-to-graphql#connection)で引数として`first`もしくは`last`を渡さなければなりません。 +* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). * `first`及び`last`の値は1から100の間でなければなりません。 -* 個々の呼び出しは合計500,000以上の[ノード](/v4/guides/intro-to-graphql#node)を要求してはなりません。 +* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). #### 呼び出し中のノードの計算 @@ -121,7 +121,7 @@ versions: GraphQL API v4 の制限は、REST API v3 の[レート制限](/rest/overview/resources-in-the-rest-api#rate-limiting)とは異なります。 -APIのレート制限が異なっているのはなぜでしょうか？ [GraphQL](/v4/)では、一つのGraphQLの呼び出しで[複数のRESTの呼び出し](/v4/guides/migrating-from-rest/)を置き換えることができます。 単一の複雑なGraphQLの呼び出しが、数千のRESTリクエストと等価なこともあります。 単一の GraphQL 呼び出しは REST API レート制限を大幅に下回りますが、クエリはGitHub のサーバーが演算するのと同等の負荷になる可能性があります。 +APIのレート制限が異なっているのはなぜでしょうか？ With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). 単一の複雑なGraphQLの呼び出しが、数千のRESTリクエストと等価なこともあります。 単一の GraphQL 呼び出しは REST API レート制限を大幅に下回りますが、クエリはGitHub のサーバーが演算するのと同等の負荷になる可能性があります。 クエリのサーバーにとってのコストを正確に表すために、GraphQL API v4は呼び出しの**レート制限スコア**を正規化されたポイントのスケールに基づいて計算します。 クエリのスコアは、親のコネクションやその子のfirst及びlast引数を計算に入れます。 diff --git a/translations/ja-JP/content/graphql/overview/schema-previews.md b/translations/ja-JP/content/graphql/overview/schema-previews.md index 9e3c316de9..cb4a9d1e53 100644 --- a/translations/ja-JP/content/graphql/overview/schema-previews.md +++ b/translations/ja-JP/content/graphql/overview/schema-previews.md @@ -13,7 +13,7 @@ versions: プレビュー期間中は、開発者からのフィードバックに基づいて機能を変更することがあります。 変更をする際には、事前の通知なく[開発者blog](https://developer.github.com/changes/)でアナウンスします。 -スキーマプレビューにアクセスするには、リクエストの` Accept`ヘッダー内でカスタムの[メディアタイプ](/v3/media)を提供しなければなりません。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。 +スキーマプレビューにアクセスするには、リクエストの` Accept`ヘッダー内でカスタムの[メディアタイプ](/rest/overview/media-types)を提供しなければなりません。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。 {% note %} diff --git a/translations/ja-JP/content/graphql/reference/enums.md b/translations/ja-JP/content/graphql/reference/enums.md index b4baf72864..9017539bcb 100644 --- a/translations/ja-JP/content/graphql/reference/enums.md +++ b/translations/ja-JP/content/graphql/reference/enums.md @@ -12,9 +12,9 @@ versions: [列挙型](https://graphql.github.io/graphql-spec/June2018/#sec-Enums)は、フィールドが取り得る値の集合を表します。 -たとえば、[`Issue`](/v4/object/issue)オブジェクトは、`state`というフィールドを持っています。 stateは、`OPEN`もしくは`CLOSED`なので、列挙型（具体的には[` IssueState`](/v4/enum/issuestate/)という型です）です。 +たとえば、[`Issue`](/graphql/reference/objects#issue)オブジェクトは、`state`というフィールドを持っています。 stateは、`OPEN`もしくは`CLOSED`なので、列挙型（具体的には[` IssueState`](/graphql/reference/enums#issuestate)という型です）です。 -詳しい情報については「[GraphQLの紹介](/v4/guides/intro-to-graphql)」を参照してください。 +詳しい情報については「[GraphQLの紹介](/graphql/guides/introduction-to-graphql)」を参照してください。 {% for item in graphql.schemaForCurrentVersion.enums %} {% include graphql-enum %} diff --git a/translations/ja-JP/content/graphql/reference/input-objects.md b/translations/ja-JP/content/graphql/reference/input-objects.md index 8edeb7bdc4..585f21ba57 100644 --- a/translations/ja-JP/content/graphql/reference/input-objects.md +++ b/translations/ja-JP/content/graphql/reference/input-objects.md @@ -12,9 +12,9 @@ versions: [入力オブジェクト](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects)は、オブジェクトを定義する入力フィールドの集合を含むことから、「構成可能オブジェクト」と呼ぶことができます。 -たとえば、[` CommitAuthor`](/v4/input_object/commitauthor/)は`emails`というフィールドを取ります。 `emails`に値を提供すると、`CommitAuthor`はそのメールアドレスを含む`User`オブジェクトのリストに変換されます。 [オブジェクト](/v4/object)は入力オブジェクトを持つ**こともある**のに対して、[ミューテーション](/v4/mutation)は入力オブジェクトを**必要**とすることに注意してください。 +たとえば、[` CommitAuthor`](/graphql/reference/input-objects#commitauthor)は`emails`というフィールドを取ります。 `emails`に値を提供すると、`CommitAuthor`はそのメールアドレスを含む`User`オブジェクトのリストに変換されます。 [オブジェクト](/graphql/reference/objects)は入力オブジェクトを持つ**こともある**のに対して、[ミューテーション](/graphql/reference/mutations)は入力オブジェクトを**必要**とすることに注意してください。 -詳しい情報については「[ミューテーションについて](/v4/guides/forming-calls#about-mutations)」を参照してください。 +詳しい情報については「[ミューテーションについて](/graphql/guides/forming-calls-with-graphql#about-mutations)」を参照してください。 {% for item in graphql.schemaForCurrentVersion.inputObjects %} {% include graphql-input-object %} diff --git a/translations/ja-JP/content/graphql/reference/interfaces.md b/translations/ja-JP/content/graphql/reference/interfaces.md index 374d1f7676..3b7b697258 100644 --- a/translations/ja-JP/content/graphql/reference/interfaces.md +++ b/translations/ja-JP/content/graphql/reference/interfaces.md @@ -12,9 +12,9 @@ versions: [インターフェース](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces)は、他のオブジェクトが継承できる親オブジェクトとして働きます。 -たとえば[`Lockable`](/v4/interface/lockable/)は、[`Issue`](/v4/object/issue/)及び[`PullRequest`](/v4/object/pullrequest/)オブジェクトがどちらもロックできるので、インターフェースです。 インターフェースは、実装オブジェクトが共有する名前付きフィールドのリストを独自に持ちます。 +たとえば[`Lockable`](/graphql/reference/interfaces#lockable)は、[`Issue`](/graphql/reference/objects#issue)及び[`PullRequest`](/graphql/reference/objects#pullrequest)オブジェクトがどちらもロックできるので、インターフェースです。 インターフェースは、実装オブジェクトが共有する名前付きフィールドのリストを独自に持ちます。 -詳しい情報については「[実装](/v4/guides/intro-to-graphql#implementation)」を参照してください。 +詳しい情報については「[実装](/graphql/guides/introduction-to-graphql#implementation)」を参照してください。 {% for item in graphql.schemaForCurrentVersion.interfaces %} {% include graphql-interface %} diff --git a/translations/ja-JP/content/graphql/reference/mutations.md b/translations/ja-JP/content/graphql/reference/mutations.md index 588e486740..712c8dab11 100644 --- a/translations/ja-JP/content/graphql/reference/mutations.md +++ b/translations/ja-JP/content/graphql/reference/mutations.md @@ -12,7 +12,7 @@ versions: すべてのGraphQLスキーマは、クエリとミューテーションの両方についてルート型を持っています。 [ミューテーション型](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System)は、サーバー上のデータを変更するGraphQLの操作を定義します。 これは、`POST`、`PATCH`、`DELETE`といったHTTPのメソッドを実行するのに似ています。 -詳しい情報については「[ミューテーションについて](/v4/guides/forming-calls#about-mutations)」を参照してください。 +詳しい情報については「[ミューテーションについて](/graphql/guides/forming-calls-with-graphql#about-mutations)」を参照してください。 {% for item in graphql.schemaForCurrentVersion.mutations %} {% include graphql-mutation %} diff --git a/translations/ja-JP/content/graphql/reference/objects.md b/translations/ja-JP/content/graphql/reference/objects.md index 3b199f413c..6024fd36e9 100644 --- a/translations/ja-JP/content/graphql/reference/objects.md +++ b/translations/ja-JP/content/graphql/reference/objects.md @@ -14,7 +14,7 @@ GraphQLにおける[オブジェクト](https://graphql.github.io/graphql-spec/J たとえば[`Repository`](/graphql/reference/objects#repository)オブジェクトは`name`というフィールドを持ち、これは`String`です。 -詳しい情報については「[GraphQLの紹介](/v4/guides/intro-to-graphql)」を参照してください。 +詳しい情報については「[GraphQLの紹介](/graphql/guides/introduction-to-graphql)」を参照してください。 diff --git a/translations/ja-JP/content/graphql/reference/queries.md b/translations/ja-JP/content/graphql/reference/queries.md index 886693554e..0a5c5e58f9 100644 --- a/translations/ja-JP/content/graphql/reference/queries.md +++ b/translations/ja-JP/content/graphql/reference/queries.md @@ -13,7 +13,7 @@ versions: すべてのGraphQLスキーマは、クエリとミューテーションの両方についてルート型を持っています。 [クエリ型](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System)は、サーバーからデータを取り出すGraphQLの操作を定義します。 -詳しい情報については「[クエリについて](/v4/guides/forming-calls#about-queries)」を参照してください。 +詳しい情報については「[クエリについて](/graphql/guides/forming-calls-with-graphql#about-queries)」を参照してください。 {% note %} diff --git a/translations/ja-JP/content/graphql/reference/scalars.md b/translations/ja-JP/content/graphql/reference/scalars.md index f2d7380cbf..51280d6776 100644 --- a/translations/ja-JP/content/graphql/reference/scalars.md +++ b/translations/ja-JP/content/graphql/reference/scalars.md @@ -14,7 +14,7 @@ versions: GraphQL APIを呼ぶ際には、スカラだけが返されるようになるまでネストしたサブフィールドを指定していかなければなりません。 -詳しい情報については「[GraphQLの紹介](/v4/guides/intro-to-graphql#field)」を参照してください。 +詳しい情報については「[GraphQLの紹介](/graphql/guides/introduction-to-graphql#field)」を参照してください。 {% for item in graphql.schemaForCurrentVersion.scalars %} {% include graphql-scalar %} diff --git a/translations/ja-JP/content/graphql/reference/unions.md b/translations/ja-JP/content/graphql/reference/unions.md index fd63fbb903..b66f1e0f3f 100644 --- a/translations/ja-JP/content/graphql/reference/unions.md +++ b/translations/ja-JP/content/graphql/reference/unions.md @@ -12,9 +12,9 @@ versions: [ユニオン](https://graphql.github.io/graphql-spec/June2018/#sec-Unions)は、多くのオブジェクトを表すオブジェクトの型です。 -たとえば、[`ProjectCardItem`](/v4/union/projectcarditem/)としてマークされたフィールドは、[`Issue`](/v4/object/issue/)あるいは[`PullRequest`](/v4/object/pullrequest/)になれます。これは、これらのオブジェクトはどちらもプロジェクトカードの中に置けるためです。 オブジェクトの代わりにユニオンを使うことで柔軟性が得られます。 +たとえば、[`ProjectCardItem`](/graphql/reference/unions#projectcarditem)としてマークされたフィールドは、[`Issue`](/graphql/reference/objects#issue)あるいは[`PullRequest`](/graphql/reference/objects#pullrequest)になれます。これは、これらのオブジェクトはどちらもプロジェクトカードの中に置けるためです。 オブジェクトの代わりにユニオンを使うことで柔軟性が得られます。 -詳しい情報については「[GraphQLの紹介](/v4/guides/intro-to-graphql)」を参照してください。 +詳しい情報については「[GraphQLの紹介](/graphql/guides/introduction-to-graphql)」を参照してください。 {% for item in graphql.schemaForCurrentVersion.unions %} {% include graphql-union %} diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 99ff2d00c5..751d059f02 100644 --- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: GitHub InsightsとGitHub Enterprise間のリンクの有効化 -intro: 'ユーザが{% data variables.product.prodname_ghe_server %}から{{ site.data.variables.product.prodname_insights }}へアクセスできるようにするリンクを有効化できます。' +intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' permissions: '{% data variables.product.prodname_ghe_server %}のサイト管理者は、{% data variables.product.prodname_ghe_server %}と{% data variables.product.prodname_insights %}間のリンクを有効化できます。' redirect_from: diff --git a/translations/ja-JP/content/packages/publishing-and-managing-packages/about-github-packages.md b/translations/ja-JP/content/packages/publishing-and-managing-packages/about-github-packages.md index 9b23fe94cc..8ed543a16f 100644 --- a/translations/ja-JP/content/packages/publishing-and-managing-packages/about-github-packages.md +++ b/translations/ja-JP/content/packages/publishing-and-managing-packages/about-github-packages.md @@ -182,7 +182,7 @@ Subdomain Isolation の詳しい情報については、「[Subdomain Isolation ### パッケージの管理 -You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. GraphQL APIを使ってプライベートパッケージに対するクエリや削除を行う場合、{% data variables.product.prodname_registry %}の認証に使うのと同じトークンを使わなければなりません。 詳しい情報については、「[パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package)」と「[GraphQLでの呼び出しの作成](/v4/guides/forming-calls/)」を参照してください。 +You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. GraphQL APIを使ってプライベートパッケージに対するクエリや削除を行う場合、{% data variables.product.prodname_registry %}の認証に使うのと同じトークンを使わなければなりません。 詳しい情報については、「[パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package)」と「[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。 webhookを設定して、パッケージの公開や更新といったパッケージ関連のイベントにサブスクライブできます。 詳しい情報については、「[`package` webhookイベント](/webhooks/event-payloads/#package)」を参照してください。 diff --git a/translations/ja-JP/content/rest/guides/basics-of-authentication.md b/translations/ja-JP/content/rest/guides/basics-of-authentication.md index 36132c7337..ce92984eea 100644 --- a/translations/ja-JP/content/rest/guides/basics-of-authentication.md +++ b/translations/ja-JP/content/rest/guides/basics-of-authentication.md @@ -130,7 +130,7 @@ end リクエストを行う前にのみスコープを確認するだけでは不十分です。確認時と実際のリクエスト時の間に、ユーザがスコープを変更する可能性があります。 このような場合には、成功すると思っていたAPIの呼び出しが`404`または`401`ステータスになって失敗したり、情報の別のサブセットを返したりします。 -この状況にうまく対応できるように、有効なトークンによるリクエストに対するすべてのAPIレスポンスには、[`X-OAuth-Scopes`ヘッダ][oauth scopes]も含まれています。 このヘッダには、リクエストを行うために使用されたトークンのスコープのリストが含まれています。 In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/v3/apps/oauth_applications/#check-an-authorization\]{% endif %}. この情報を使用してトークンのスコープにおける変更を検出し、利用可能なアプリケーション機能の変更をユーザに通知します。 +この状況にうまく対応できるように、有効なトークンによるリクエストに対するすべてのAPIレスポンスには、[`X-OAuth-Scopes`ヘッダ][oauth scopes]も含まれています。 このヘッダには、リクエストを行うために使用されたトークンのスコープのリストが含まれています。 In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. この情報を使用してトークンのスコープにおける変更を検出し、利用可能なアプリケーション機能の変更をユーザに通知します。 #### 認証リクエストの実施 diff --git a/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md b/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md index f46aeaccab..674dcb6caf 100644 --- a/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md +++ b/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md @@ -20,7 +20,7 @@ GitHubプラットフォームとの統合に興味はありますか。 [同じ いくつかのステップを踏むことで、GitHubから配信されるペイロードを安全に受信できます。 1. 受信サーバーは必ずHTTPS接続にしてください。 By default, GitHub will verify SSL certificates when delivering payloads.{% if currentVersion == "free-pro-team@latest" %} -1. [フック配信時に使用するIPアドレス](/github/authenticating-to-github/about-githubs-ip-addresses)をサーバーの許可リストに追加できます。 正しいIPアドレスを常に確認していることを確かめるため、[`/meta`エンドポイントを使用して](/v3/meta/#meta)GitHubが使用するアドレスを見つけることができます。{% endif %} +1. [フック配信時に使用するIPアドレス](/github/authenticating-to-github/about-githubs-ip-addresses)をサーバーの許可リストに追加できます。 正しいIPアドレスを常に確認していることを確かめるため、[`/meta`エンドポイントを使用して](/rest/reference/meta#meta)GitHubが使用するアドレスを見つけることができます。{% endif %} 1. ペイロードがGitHubから配信されていることを確実に保証するため、[シークレットトークン](/webhooks/securing/)を提供します。 シークレットトークンを強制することにより、サーバーが受信するあらゆるデータが確実にGitHubから来ていることを保証できます。 サービスの*ユーザごと*に異なるシークレットトークンを提供するのが理想的です。 そうすれば、1つのトークンが侵害されても、他のユーザは影響を受けません。 ### 同期作業より非同期作業を優先する @@ -49,7 +49,7 @@ Note that even with a background job running, GitHub still expects your server t GitHubは、リダイレクトのステータスコードを提供することにより、リソースがいつ移動したかを明示します。 このリダイレクトに従ってください。 すべてのリダイレクト応答は、`Location`ヘッダに、移動する新しいURIを設定します。 リダイレクトを受け取ったら、削除する可能性がある非推奨のパスをリクエストしている場合、新しいURIにしたがってコードを更新するようお勧めします。 -アプリケーションをリダイレクトに従うよう設計する際に気をつけるべき[HTTPステータスコードのリスト](/v3/#http-redirects)をご用意しています。 +アプリケーションをリダイレクトに従うよう設計する際に気をつけるべき[HTTPステータスコードのリスト](/rest#http-redirects)をご用意しています。 ### 手動でURLをパースしない diff --git a/translations/ja-JP/content/rest/guides/building-a-ci-server.md b/translations/ja-JP/content/rest/guides/building-a-ci-server.md index 5572696352..e0e08347b8 100644 --- a/translations/ja-JP/content/rest/guides/building-a-ci-server.md +++ b/translations/ja-JP/content/rest/guides/building-a-ci-server.md @@ -129,7 +129,7 @@ GitHubでは長年、CIを管理するため[Janky][janky]の特定のバージ これら全ての通信は、チャットルームに集約されます。 この例を使用するために、独自のCI設定を構築する必要はありません。 いつでも[GitHubインテグレーション][integrations]に頼ることができます。 -[status API]: /v3/repos/statuses/ +[status API]: /rest/reference/repos#statuses [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server diff --git a/translations/ja-JP/content/rest/guides/delivering-deployments.md b/translations/ja-JP/content/rest/guides/delivering-deployments.md index 61568ebb49..8d294cd530 100644 --- a/translations/ja-JP/content/rest/guides/delivering-deployments.md +++ b/translations/ja-JP/content/rest/guides/delivering-deployments.md @@ -13,7 +13,7 @@ versions: -[Deployment API][deploy API]は、{% data variables.product.product_name %}にホストされたプロジェクトが、あなたのサーバーで起動できるようにします。 Combined with [the Status API][status API], you'll be able to coordinate your deployments the moment your code lands on the default branch. +The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with the capability to launch them on a server that you own. Combined with [the Status API][status API], you'll be able to coordinate your deployments the moment your code lands on the default branch. このAPIでは、ステータスAPIを使って、利用できる設定を示します。 このシナリオでは、以下を行います。 @@ -145,7 +145,7 @@ GitHubでは長年、デプロイメントを管理するため[Heaven][heaven] これで完了です。 この例を使用するために、独自のデプロイメントを構築する必要はありません。 いつでも[GitHubインテグレーション][integrations]に頼ることができます。 -[deploy API]: /v3/repos/deployments/ +[deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok diff --git a/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md b/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md index 0278d70690..c999af9fc3 100644 --- a/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md @@ -93,19 +93,19 @@ end 通常、アプリケーションでは、アプリケーションにアクセスする権限が与えられたユーザのOrganization (パブリックおよびプライベート) の全てを必要とします。 上記のワークフローでは、まさにこれを実行しています。 -[basics-of-authentication]: /v3/guides/basics-of-authentication/ -[list-public-orgs]: /v3/orgs/#list-organizations-for-a-user -[list-repositories-for-current-user]: /v3/repos/#list-repositories-for-the-authenticated-user -[list-orgs-for-current-user]: /v3/orgs/#list-organizations-for-the-authenticated-user -[list-teams]: /v3/teams/#list-teams -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests +[basics-of-authentication]: /rest/guides/basics-of-authentication +[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user +[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user +[list-teams]: /rest/reference/teams#list-teams +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ [octokit.rb]: https://github.com/octokit/octokit.rb [octokit.rb]: https://github.com/octokit/octokit.rb -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user -[publicize-membership]: /v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user -[register-oauth-app]: /v3/guides/basics-of-authentication/#registering-your-app +[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user +[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-git-database-api.md index f48957e37f..6a504b1026 100644 --- a/translations/ja-JP/content/rest/guides/getting-started-with-the-git-database-api.md +++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-git-database-api.md @@ -11,7 +11,7 @@ versions: これにより、さまざまなGitの機能を、APIを介して再実装することができます。Raw形式オブジェクトのオブジェクトをデータベースに直接作成し、ブランチリファレンスを更新することにより、Gitをインストールしなくても、Gitができることのほとんどを行えるのです。 -Git Database API関数は、Gitリポジトリが空または利用できない場合、`409 Conflict`を返します。 リポジトリが利用できないということは、通常、{% data variables.product.product_name %}がリポジトリを作成処理中であるということです。 空のリポジトリの場合は、「[ファイルコンテンツの作成または更新](/v3/repos/contents/#create-or-update-file-contents)」エンドポイントを使用してコンテンツを作成し、リポジトリを初期化してGit Database APIを使用できるようにすることができます。 このレスポンスステータスが継続している場合は、{% data variables.contact.contact_support %}までご連絡ください。 +Git Database API関数は、Gitリポジトリが空または利用できない場合、`409 Conflict`を返します。 リポジトリが利用できないということは、通常、{% data variables.product.product_name %}がリポジトリを作成処理中であるということです。 空のリポジトリの場合は、「[ファイルコンテンツの作成または更新](/rest/reference/repos#create-or-update-file-contents)」エンドポイントを使用してコンテンツを作成し、リポジトリを初期化してGit Database APIを使用できるようにすることができます。 このレスポンスステータスが継続している場合は、{% data variables.contact.contact_support %}までご連絡ください。 ![Gitデータベースの概要](/assets/images/git-database-overview.png) @@ -33,14 +33,14 @@ Gitオブジェクトデータベースについての詳細は、Pro Gitブッ {% warning %} -**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. +**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. {% endwarning %} -_test_マージコミットを作成するには、使用するAPIは、明示的にプルリクエストを要求する必要があります。 _test_マージコミットは、UIでプルリクエストを表示して [Merge] ボタンが表示されるか、REST APIを使ってプルリクエストを[取得](/v3/pulls/#get-a-pull-request)、[作成](/v3/pulls/#create-a-pull-request)、または[編集](/v3/pulls/#update-a-pull-request)した際に作成されます。 このリクエストがなければ、`merge` Git refは次に誰かがプルリクエストを表示するまで期限切れになります。 +_test_マージコミットを作成するには、使用するAPIは、明示的にプルリクエストを要求する必要があります。 _test_マージコミットは、UIでプルリクエストを表示して [Merge] ボタンが表示されるか、REST APIを使ってプルリクエストを[取得](/rest/reference/pulls#get-a-pull-request)、[作成](/rest/reference/pulls#create-a-pull-request)、または[編集](/rest/reference/pulls#update-a-pull-request)した際に作成されます。 このリクエストがなければ、`merge` Git refは次に誰かがプルリクエストを表示するまで期限切れになります。 If you are currently using polling methods that produce outdated `merge` Git refs, then GitHub recommends using the following steps to get the latest changes from the default branch: 1. プルリクエストwebhookを受け取ります。 -2. [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request)を呼び出し、マージコミット候補を作成するためのバックグラウンドジョブを開始します。 -3. `mergeable`属性が`true`か`false`かを判断するため、[`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request)を使用してリポジトリをポーリングします。 You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. +2. [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request)を呼び出し、マージコミット候補を作成するためのバックグラウンドジョブを開始します。 +3. `mergeable`属性が`true`か`false`かを判断するため、[`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request)を使用してリポジトリをポーリングします。 You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md index 434cfcc4bc..d58d660cae 100644 --- a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md @@ -367,33 +367,33 @@ $ {% data variables.product.api_url_pre %}/users/defunkt [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[repos-api]: /v3/repos/ -[repos-api]: /v3/repos/ +[repos-api]: /rest/reference/repos +[repos-api]: /rest/reference/repos [pages]: http://pages.github.com [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore -[issues-api]: /v3/issues/ +[issues-api]: /rest/reference/issues [link-header]: http://www.w3.org/wiki/LinkHeader/ -[conditional-requests]: /v3/#conditional-requests -[rate-limiting]: /v3/#rate-limiting -[rate-limiting]: /v3/#rate-limiting -[users api]: /v3/users/#get-a-user +[conditional-requests]: /rest#conditional-requests +[rate-limiting]: /rest#rate-limiting +[rate-limiting]: /rest#rate-limiting +[users api]: /rest/reference/users#get-a-user [defunkt github]: https://github.com/defunkt [defunkt github]: https://github.com/defunkt [json]: http://en.wikipedia.org/wiki/JSON -[authentication]: /v3/#authentication +[authentication]: /rest#authentication [personal token]: /articles/creating-an-access-token-for-command-line-use [personal token]: /articles/creating-an-access-token-for-command-line-use [tokens settings]: https://github.com/settings/tokens -[pagination]: /v3/#pagination -[get repo]: /v3/repos/#get-a-repository -[create repo]: /v3/repos/#create-a-repository-for-the-authenticated-user -[create issue]: /v3/issues/#create-an-issue +[pagination]: /rest#pagination +[get repo]: /rest/reference/repos#get-a-repository +[create repo]: /rest/reference/repos#create-a-repository-for-the-authenticated-user +[create issue]: /rest/reference/issues#create-an-issue [auth guide]: /guides/basics-of-authentication -[user repos api]: /v3/repos/#list-repositories-for-the-authenticated-user -[other user repos api]: /v3/repos/#list-repositories-for-a-user -[org repos api]: /v3/repos/#list-organization-repositories -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[repo issues api]: /v3/issues/#list-repository-issues +[user repos api]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[other user repos api]: /rest/reference/repos#list-repositories-for-a-user +[org repos api]: /rest/reference/repos#list-organization-repositories +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[repo issues api]: /rest/reference/issues#list-repository-issues [etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md b/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md index 7c1061c16b..0d6d983ee3 100644 --- a/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md @@ -232,7 +232,7 @@ erb :lang_freq, :locals => { :languages => languages.to_json} ] ``` -すでに上記でリポジトリのリストを取得しているので、それぞれを調べて、[言語をリスト化するAPIメソッド][language API]を呼びましょう。 +Since we already have a list of repositories above, let's inspect each one, and call [the language listing API method][language API]: ``` ruby repos.each do |repo| @@ -264,7 +264,7 @@ end language_bytes = [ :name => "language_bytes", :elements => language_byte_count] ``` -(D3ツリーマップの魔力をもっと詳しく知りたければ、[この簡単なチュートリアル][language API]を確認しましょう。) +(For more information on D3 tree map magic, check out [this simple tutorial][language API].) 仕上げに、このJSON情報を同じERBテンプレートに渡します。 @@ -333,7 +333,7 @@ erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_cou [Octokit]: https://github.com/octokit/octokit.rb [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ [D3 treemap]: http://bl.ocks.org/mbostock/4063582 -[language API]: /v3/repos/#list-repository-languages -[language API]: /v3/repos/#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs [new oauth application]: https://github.com/settings/applications/new diff --git a/translations/ja-JP/content/rest/guides/traversing-with-pagination.md b/translations/ja-JP/content/rest/guides/traversing-with-pagination.md index 3951eebe0b..6c2b062da8 100644 --- a/translations/ja-JP/content/rest/guides/traversing-with-pagination.md +++ b/translations/ja-JP/content/rest/guides/traversing-with-pagination.md @@ -20,9 +20,9 @@ versions: はじめに、ページネーションされたアイテムの受け取りについて、いくつかの事実を知っておくことが重要です。 -1. 呼び出す API によって、応答するデフォルト値が異なります。 [パブリックリポジトリのリスト化](/v3/repos/#list-public-repositories)を呼び出すと、ページネーションされて提供されるのは 1 セットで 30 アイテムですが、GitHub Search APIを呼び出すと 1 セットで 100 アイテムとなります。 +1. 呼び出す API によって、応答するデフォルト値が異なります。 [パブリックリポジトリのリスト化](/rest/reference/repos#list-public-repositories)を呼び出すと、ページネーションされて提供されるのは 1 セットで 30 アイテムですが、GitHub Search APIを呼び出すと 1 セットで 100 アイテムとなります。 2. 受け取るアイテムの数は指定できます (最大 100 まで)。 -3. ただし、技術的な理由により、すべてのエンドポイントが同じ動作をするわけではありません。 たとえば、[イベント](/v3/activity/events/)では受け取るアイテム数の最大値を設定できません。 特定のエンドポイントにおけるページネーションされた結果の処理方法については、必ずドキュメントをお読みください。 +3. ただし、技術的な理由により、すべてのエンドポイントが同じ動作をするわけではありません。 たとえば、[イベント](/rest/reference/activity#events)では受け取るアイテム数の最大値を設定できません。 特定のエンドポイントにおけるページネーションされた結果の処理方法については、必ずドキュメントをお読みください。 ページネーションに関する情報は、API呼び出しの[リンクヘッダ](http://tools.ietf.org/html/rfc5988)に記載されています。 たとえば、検索APIにcurlでリクエストを行って、Mozilla プロジェクトで `addClass`というフレーズを何回使っているか調べましょう。 @@ -201,7 +201,7 @@ puts "The prev page link is #{prev_page_href}" puts "The next page link is #{next_page_href}" ``` -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination [octokit.rb]: https://github.com/octokit/octokit.rb [personal token]: /articles/creating-an-access-token-for-command-line-use diff --git a/translations/ja-JP/content/rest/guides/working-with-comments.md b/translations/ja-JP/content/rest/guides/working-with-comments.md index f61353b038..900b4d19b8 100644 --- a/translations/ja-JP/content/rest/guides/working-with-comments.md +++ b/translations/ja-JP/content/rest/guides/working-with-comments.md @@ -18,7 +18,7 @@ versions: ### プルリクエストのコメント -プルリクエストのコメントにアクセスするには、[Issues API][issues] を経由します。 最初はこれを意外に思うかもしれません。 しかし、プルリクエストがコード付きの Issue に過ぎないことさえ理解すれば、プルリクエストにコメントを作成するため Issues API を使うこともうなずけるでしょう。 +To access comments on a Pull Request, you'll go through [the Issues API][issues]. 最初はこれを意外に思うかもしれません。 しかし、プルリクエストがコード付きの Issue に過ぎないことさえ理解すれば、プルリクエストにコメントを作成するため Issues API を使うこともうなずけるでしょう。 ここでは [Octokit.rb][octokit.rb] を使って Ruby スクリプトを作成し、プルリクエストのコメントをフェッチする方法を示します。 また、[個人アクセストークン][personal token]の作成もおすすめします。 @@ -44,7 +44,7 @@ end ### 行につけるプルリクエストのコメント -diff ビュー内では、プルリクエスト内の一つの変更について、特定の側面からディスカッションを開始できます。 これらのコメントは、変更されたファイル内の個々の行について書き込まれます。 このディスカッションのエンドポイントURLは、[Pull Request Review API][PR Review API] から取得されます。 +diff ビュー内では、プルリクエスト内の一つの変更について、特定の側面からディスカッションを開始できます。 これらのコメントは、変更されたファイル内の個々の行について書き込まれます。 The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API]. 以下のコードは、指定したプルリクエスト番号のファイルにあるプルリクエストのコメントすべてをフェッチします。 @@ -70,7 +70,7 @@ end ### コミットのコメント -最後のタイプのコメントは、特に個々のコミットで発生します。 このため、[コミットのコメント API][commit comment API] を使用します。 +最後のタイプのコメントは、特に個々のコミットで発生します。 For this reason, they make use of [the commit comment API][commit comment API]. コミットのコメントを取得するには、コミットの SHA1 を使用します。 言い換えれば、プルリクエストに関する識別子は全く使用しません。 次に例を示します。 @@ -97,8 +97,8 @@ end [commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 [sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 [platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments -[issues]: /v3/issues/comments/ +[issues]: /rest/reference/issues#comments [personal token]: /articles/creating-an-access-token-for-command-line-use [octokit.rb]: https://github.com/octokit/octokit.rb -[PR Review API]: /v3/pulls/comments/ -[commit comment API]: /v3/repos/comments/#get-a-commit-comment +[PR Review API]: /rest/reference/pulls#comments +[commit comment API]: /rest/reference/repos#get-a-commit-comment diff --git a/translations/ja-JP/content/rest/overview/api-previews.md b/translations/ja-JP/content/rest/overview/api-previews.md index 5c6385cf0a..a97c3408f9 100644 --- a/translations/ja-JP/content/rest/overview/api-previews.md +++ b/translations/ja-JP/content/rest/overview/api-previews.md @@ -15,12 +15,12 @@ API プレビューを使用すると、正式に GitHub API の一部になる プレビュー期間中は、開発者からのフィードバックに基づいて機能を変更することがあります。 変更をする際には、事前の通知なく[開発者blog](https://developer.github.com/changes/)でアナウンスします。 -API プレビューにアクセスするには、リクエストの ` Accept` ヘッダー内でカスタムの[メディアタイプ](/v3/media)を提供しなければなりません。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。 +API プレビューにアクセスするには、リクエストの ` Accept` ヘッダー内でカスタムの[メディアタイプ](/rest/overview/media-types)を提供しなければなりません。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。 {% if currentVersion == "free-pro-team@latest" %} ### 移行 -GitHub ユーザまたは Organization アカウントからリポジトリをダウンロードして、データの確認、バックアップ、{% data variables.product.prodname_ghe_server %} への[移行](/v3/migrations/)ができます。 +GitHub ユーザまたは Organization アカウントからリポジトリをダウンロードして、データの確認、バックアップ、{% data variables.product.prodname_ghe_server %} への[移行](/rest/reference/migrations)ができます。 **カスタムメディアタイプ:** `wyandotte-preview` **発表日:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) {% endif %} @@ -33,13 +33,13 @@ GitHub ユーザまたは Organization アカウントからリポジトリを ### リアクション -コミット、Issue、コメントに対する[リアクション](/v3/reactions/)を管理します。 +コミット、Issue、コメントに対する[リアクション](/rest/reference/reactions)を管理します。 **カスタムメディアタイプ:** `squirrel-girl-preview` **発表日:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **更新日:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) ### タイムライン -Issue またはプルリクエストの[イベントのリスト](/v3/issues/timeline/)を取得します。 +Issue またはプルリクエストの[イベントのリスト](/rest/reference/issues#timeline)を取得します。 **カスタムメディアタイプ:** `mockingbird-preview` **発表日:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) @@ -61,40 +61,40 @@ API を介して[インテグレーション](/early-access/integrations/)を管 ### プロジェクト -[プロジェクト](/v3/projects/)を管理します。 +[プロジェクト](/rest/reference/projects)を管理します。 **カスタムメディアタイプ:** `inertia-preview` **発表日:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **更新日:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) ### コミット検索 -[コミットの検索](/v3/search/)をします。 +[コミットの検索](/rest/reference/search)をします。 **カスタムメディアタイプ:** `cloak-preview` **発表日:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% if currentVersion == "free-pro-team@latest" %} ### ユーザブロック -ユーザは[他のユーザをブロック](/v3/users/blocking/)できます。 Organization も[ユーザをブロック](/v3/orgs/blocking/)できます。 +ユーザは[他のユーザをブロック](/rest/reference/users#blocking)できます。 Organization も[ユーザをブロック](/rest/reference/orgs#blocking)できます。 **カスタムメディアタイプ:** `giant-sentry-fist-preview` **発表日:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **更新日1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **更新日 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) {% endif %} ### リポジトリトピック -リポジトリの結果を返す[呼び出し](/v3/repos/)で[リポジトリトピック](/articles/about-topics/)のリストを表示します。 +リポジトリの結果を返す[呼び出し](/rest/reference/repos)で[リポジトリトピック](/articles/about-topics/)のリストを表示します。 **カスタムメディアタイプ:** `mercy-preview` **発表日:** [2017-01-31](https://github.com/blog/2309-introducing-topics) ### 行動規範 -すべての[行動規範](/v3/codes_of_conduct)を表示するか、リポジトリに現在ある行動規範を取得します。 +すべての[行動規範](/rest/reference/codes-of-conduct)を表示するか、リポジトリに現在ある行動規範を取得します。 **カスタムメディアタイプ:** `scarlet-witch-preview` {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### 入れ子チーム -入れ子チームコンテンツを [Team](/v3/teams/) ペイロードに含めます。 +入れ子チームコンテンツを [Team](/rest/reference/teams) ペイロードに含めます。 **カスタムメディアタイプ:** `hellcat-preview` **発表日:** [2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) @@ -113,7 +113,7 @@ API を介して[インテグレーション](/early-access/integrations/)を管 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### リポジトリ移譲 -[リポジトリ](/v3/repos/)を Organization またはユーザに移譲します。 +[リポジトリ](/rest/reference/repos)を Organization またはユーザに移譲します。 **カスタムメディアタイプ:** `nightshade-preview` **発表日:** [2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) {% endif %} @@ -121,27 +121,27 @@ API を介して[インテグレーション](/early-access/integrations/)を管 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### ロック理由の追加 -[Issue をロック](/v3/issues/#lock-an-issue)するときに理由を追加できるようになりました。 +[Issue をロック](/rest/reference/issues#lock-an-issue)するときに理由を追加できるようになりました。 **カスタムメディアタイプ:** `sailor-v-preview` **発表日:** [2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) {% endif %} ### 署名済みコミットの必須化 -これで、API を使用して、[保護されたブランチで署名済みコミットを必須にする](/v3/repos/branches)ための設定を管理できます。 +これで、API を使用して、[保護されたブランチで署名済みコミットを必須にする](/rest/reference/repos#branches)ための設定を管理できます。 **カスタムメディアタイプ:** `zzzax-preview` **発表日:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) ### 複数の承認レビューの必須化 -API を使用して、プルリクエストに対して[複数の承認レビューを必須にする](/v3/repos/branches)ことができるようになりました。 +API を使用して、プルリクエストに対して[複数の承認レビューを必須にする](/rest/reference/repos#branches)ことができるようになりました。 **カスタムメディアタイプ:** `luke-cage-preview` **発表日:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.19" %} ### ホバーカード情報の取得 -[ユーザのホバーカード](/v3/users/#get-contextual-information-for-a-user)から情報を取得します。 +[ユーザのホバーカード](/rest/reference/users#get-contextual-information-for-a-user)から情報を取得します。 **カスタムメディアタイプ:** `hagar-preview` **発表日:** [2018-03-21](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) @@ -150,7 +150,7 @@ API を使用して、プルリクエストに対して[複数の承認レビュ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} ### チェック実行とチェックスイート API -GitHub App がリポジトリのコードに対して外部チェックを実行できるようにします。 詳細については、[チェック実行](/v3/checks/runs/)と[チェックスイート](/v3/checks/suites/) API をご覧ください。 +GitHub App がリポジトリのコードに対して外部チェックを実行できるようにします。 詳細については、[チェック実行](/rest/reference/checks#runs)と[チェックスイート](/rest/reference/checks#suites) API をご覧ください。 **カスタムメディアタイプ:** `antiope-preview` **発表日:** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) {% endif %} @@ -167,7 +167,7 @@ GitHub App がリポジトリのコードに対して外部チェックを実行 ### プロジェクトカードの詳細 -[Issue イベント](/v3/issues/events/)および [Issue タイムラインイベント](/v3/issues/timeline/)の REST API 応答は、プロジェクト関連イベントの `project_card` フィールドを返すようになりました。 +[Issue イベント](/rest/reference/issues#events)および [Issue タイムラインイベント](/rest/reference/issues#timeline)の REST API 応答は、プロジェクト関連イベントの `project_card` フィールドを返すようになりました。 **カスタムメディアタイプ:** `starfox-preview` **発表日:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) @@ -189,7 +189,7 @@ GitHub App マニフェストを使用すると、事前設された GitHub App ### リポジトリの作成権限 -Organization メンバーによるリポジトリの作成可否、および作成可能なリポジトリのタイプを設定できるようになりました。 詳細については、「[Organization を更新する](/v3/orgs/#update-an-organization)」を参照してください。 +Organization メンバーによるリポジトリの作成可否、および作成可能なリポジトリのタイプを設定できるようになりました。 詳細については、「[Organization を更新する](/rest/reference/orgs#update-an-organization)」を参照してください。 **カスタムメディアタイプ:** `surtur-preview` **発表日:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) @@ -202,7 +202,7 @@ Organization メンバーによるリポジトリの作成可否、および作 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### ドラフトプルリクエスト -ドラフトプルリクエスト API とその[プルリクエスト](/v3/pulls/)エンドポイントを使用して、プルリクエストがドラフト状態かどうかを確認できます。 ドラフトプルリクエストについての詳細は、「[プルリクエストについて](/articles/about-pull-requests/)」を参照してください。 +ドラフトプルリクエスト API とその[プルリクエスト](/rest/reference/pulls)エンドポイントを使用して、プルリクエストがドラフト状態かどうかを確認できます。 ドラフトプルリクエストについての詳細は、「[プルリクエストについて](/articles/about-pull-requests/)」を参照してください。 **カスタムメディアタイプ:** `shadow-cat-preview` **発表日:** [2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) @@ -216,48 +216,48 @@ Organization メンバーによるリポジトリの作成可否、および作 ### コミットのブランチまたはプルリクエストの一覧表示 -[Commits API](/v3/repos/commits/) で 2 つの新しいエンドポイントを使用して、コミットのブランチまたはプルリクエストを一覧表示できます。 +[Commits API](/rest/reference/repos#commits) で 2 つの新しいエンドポイントを使用して、コミットのブランチまたはプルリクエストを一覧表示できます。 **カスタムメディアタイプ:** `groot-preview` **発表日:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### GitHub App のアンインストール -GitHub App の所有者は、[Apps API](/v3/apps/#delete-an-installation-for-the-authenticated-app) を使用してアプリケーションをアンインストールできるようになりました。 +GitHub App の所有者は、[Apps API](/rest/reference/apps#delete-an-installation-for-the-authenticated-app) を使用してアプリケーションをアンインストールできるようになりました。 **カスタムメディアタイプ:** `gambit-preview` {% endif %} ### リポジトリの脆弱性アラートの有効化または無効化 -[Repos API](/v3/repos/) で 2 つの新しいエンドポイントを使用して、脆弱性アラートを有効化または無効化できます。 +[Repos API](/rest/reference/repos) で 2 つの新しいエンドポイントを使用して、脆弱性アラートを有効化または無効化できます。 **カスタムメディアタイプ:** `dorian-preview` **発表日:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) ### プルリクエストブランチの更新 -新しいエンドポイントを使用して、[プルリクエストブランチ](/v3/pulls/#update-a-pull-request-branch)を上流ブランチの HEAD からの変更で更新できます。 +新しいエンドポイントを使用して、[プルリクエストブランチ](/rest/reference/pulls#update-a-pull-request-branch)を上流ブランチの HEAD からの変更で更新できます。 **カスタムメディアタイプ:** `lydian-preview` **発表日:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) {% if currentVersion == "free-pro-team@latest" %} ### 自動セキュリティ修正の有効化または無効化 -新しいエンドポイントを使用して、[自動セキュリティ修正を有効化または無効化](/v3/repos/#enable-automated-security-fixes)することができます。 +新しいエンドポイントを使用して、[自動セキュリティ修正を有効化または無効化](/rest/reference/repos#enable-automated-security-fixes)することができます。 **カスタムメディアタイプ:** `london-preview` **発表日:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ### リポジトリテンプレートの作成および使用 -新しいエンドポイントで、[テンプレートを使用してリポジトリを作成](/v3/repos/#create-a-repository-using-a-template)し、`is_template` パラメータを `true` に設定して、テンプレートリポジトリである[認証済みユーザのリポジトリを作成](/v3/repos/#create-a-repository-for-the-authenticated-user)できます。 `is_template` キーを使用して、[リポジトリを取得](/v3/repos/#get-a-repository)し、テンプレートリポジトリとして設定されているかどうかを確認します。 +新しいエンドポイントで、[テンプレートを使用してリポジトリを作成](/rest/reference/repos#create-a-repository-using-a-template)し、`is_template` パラメータを `true` に設定して、テンプレートリポジトリである[認証済みユーザのリポジトリを作成](/rest/reference/repos#create-a-repository-for-the-authenticated-user)できます。 `is_template` キーを使用して、[リポジトリを取得](/rest/reference/repos#get-a-repository)し、テンプレートリポジトリとして設定されているかどうかを確認します。 **カスタムメディアタイプ:** `baptiste-preview` **発表日:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% if currentVersion == "enterprise-server@2.20" %} ### 新しい OAuth アプリケーション API エンドポイント -新しい [OAuth アプリケーション API](/v3/apps/oauth_applications/) エンドポイントでパスパラメータの代わりに OAuth トークンを入力パラメータとして使用することにより、OAuth App のトークンをより安全に管理できます。 +新しい [OAuth アプリケーション API](/rest/reference/apps#oauth-applications) エンドポイントでパスパラメータの代わりに OAuth トークンを入力パラメータとして使用することにより、OAuth App のトークンをより安全に管理できます。 **カスタムメディアタイプ:** `doctor-strange-preview` **発表日:** [2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) {% endif %} @@ -265,7 +265,7 @@ GitHub App の所有者は、[Apps API](/v3/apps/#delete-an-installation-for-the {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ### Repositories API の新しい可視性パラメータ -[Repositories API](/v3/repos/) でリポジトリの可視性を設定および取得できます。 +[Repositories API](/rest/reference/repos) でリポジトリの可視性を設定および取得できます。 **カスタムメディアタイプ:** `nebula-preview` **発表日:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/ja-JP/content/rest/overview/media-types.md b/translations/ja-JP/content/rest/overview/media-types.md index 754e94aa71..8574279d93 100644 --- a/translations/ja-JP/content/rest/overview/media-types.md +++ b/translations/ja-JP/content/rest/overview/media-types.md @@ -21,7 +21,7 @@ API がサポートする最も基本的なメディアタイプは次のとお application/json application/vnd.github+json -これらはどちらも[バージョン][versions]を指定しないため、常にリソースの現在のデフォルトの JSON 表現を取得します。 +Neither of these specify a [version][versions], so you will always get the current default JSON representation of resources. {% note %} @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### コメント本文のプロパティ -コメントの本文は、[GitHub Flavored Markdown][gfm]、[Issue](/v3/issues/)、[Issue コメント](/v3/issues/comments/)、[プルリクエストコメント](/v3/pulls/comments/)、および [gist コメント](/v3/gists/comments/) API で記述できます。これらの API はすべて、次の同じメディアタイプを受け入れます。 +The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: #### Raw @@ -85,7 +85,7 @@ Raw 形式のテキストおよび HTML 表現を返します。 レスポンス ### Git blob プロパティ -[blob の取得](/v3/git/blobs/#get-a-blob)時に許可されるメディアタイプは次のとおりです。 +The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): #### JSON @@ -102,7 +102,7 @@ Raw 形式の blob データを返します。 ### コミット、コミット比較、プルリクエスト -[コミット API](/v3/repos/commits/) と[プルリクエスト API](/v3/pulls/) は、[diff][git-diff] および [patch][git-patch] 形式をサポートしています。 +The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: #### diff @@ -147,4 +147,4 @@ Gist の内容は、送信前に base64 でエンコードされます。 これ [gfm]: http://github.github.com/github-flavored-markdown/ [git-diff]: http://git-scm.com/docs/git-diff [git-patch]: http://git-scm.com/docs/git-format-patch -[versions]: /v3/versions +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/ja-JP/content/rest/overview/other-authentication-methods.md b/translations/ja-JP/content/rest/overview/other-authentication-methods.md index 6bb455bb12..444b0b3f00 100644 --- a/translations/ja-JP/content/rest/overview/other-authentication-methods.md +++ b/translations/ja-JP/content/rest/overview/other-authentication-methods.md @@ -59,7 +59,7 @@ password associated with the account. ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -2 要素認証を有効にしている場合は、[2 要素認証の使用方法](/v3/auth/#working-with-two-factor-authentication)を理解した上で行ってください。 +2 要素認証を有効にしている場合は、[2 要素認証の使用方法](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)を理解した上で行ってください。 {% endif %} @@ -124,8 +124,8 @@ $ curl --request POST \ {% endif %} [curl]: http://curl.haxx.se/ -[oauth-auth]: /v3/#authentication +[oauth-auth]: /rest#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -[user-issues]: /v3/issues/#list-issues-assigned-to-the-authenticated-user +[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md index 8876a806c8..7081b7c8c1 100644 --- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md @@ -14,13 +14,13 @@ versions: ### 最新バージョン -デフォルトでは、`{% data variables.product.api_url_code %}` へのすべてのリクエストが REST API の **v3** [バージョン](/v3/versions)を受け取ります。 [`Accept` ヘッダを介してこのバージョンを明示的にリクエストする](/v3/media/#request-specific-version)ことをお勧めします。 +デフォルトでは、`{% data variables.product.api_url_code %}` へのすべてのリクエストが REST API の **v3** [バージョン](/developers/overview/about-githubs-apis)を受け取ります。 [`Accept` ヘッダを介してこのバージョンを明示的にリクエストする](/rest/overview/media-types#request-specific-version)ことをお勧めします。 Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -GitHub の GraphQL API についての情報は、[v4 ドキュメント](/v4)を参照してください。 GraphQL への移行についての情報は、「[REST から移行する](/v4/guides/migrating-from-rest/)」を参照してください。 +GitHub の GraphQL API についての情報は、[v4 ドキュメント](/graphql)を参照してください。 GraphQL への移行についての情報は、「[REST から移行する](/graphql/guides/migrating-from-rest-to-graphql)」を参照してください。 {% endif %} @@ -171,7 +171,7 @@ $ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "gith ### GraphQL グローバルノード ID -REST API を介して `node_id` を検索し、それらを GraphQL 操作で使用する方法について詳しくは、「[グローバルノード ID を使用する](/v4/guides/using-global-node-ids)」のガイドを参照してください。 +REST API を介して `node_id` を検索し、それらを GraphQL 操作で使用する方法について詳しくは、「[グローバルノード ID を使用する](/graphql/guides/using-global-node-ids)」のガイドを参照してください。 ### クライアントエラー @@ -261,7 +261,7 @@ API v3 は、可能な限り各アクションに適切な HTTPメソッドを ### ページネーション -複数のアイテムを返すリクエストは、デフォルトで 30 件ごとにページ分けされます。 `?page` パラメータを使用すると、さらにページを指定できます。 一部のリソースでは、`?per_page` パラメータを使用してカスタムページサイズを最大 100 に設定することもできます。 技術的な理由により、すべてのエンドポイントが `?per_page` パラメータを尊重するわけではないことに注意してください。例については、[イベント](/v3/activity/events/)を参照してください。 +複数のアイテムを返すリクエストは、デフォルトで 30 件ごとにページ分けされます。 `?page` パラメータを使用すると、さらにページを指定できます。 一部のリソースでは、`?per_page` パラメータを使用してカスタムページサイズを最大 100 に設定することもできます。 技術的な理由により、すべてのエンドポイントが `?per_page` パラメータを尊重するわけではないことに注意してください。例については、[イベント](/rest/reference/activity#events)を参照してください。 ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' @@ -286,7 +286,7 @@ $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' _この例は、読みやすいように改行されています。_ -この `Link` レスポンスヘッダには、1 つ以上の[ハイパーメディア](/v3/#hypermedia)リンク関係が含まれています。その一部には、[URI テンプレート](http://tools.ietf.org/html/rfc6570)としての拡張が必要な場合があります。 +この `Link` レスポンスヘッダには、1 つ以上の[ハイパーメディア](/rest#hypermedia)リンク関係が含まれています。その一部には、[URI テンプレート](http://tools.ietf.org/html/rfc6570)としての拡張が必要な場合があります。 使用可能な `rel` の値は以下のとおりです。 @@ -311,7 +311,7 @@ Basic 認証または OAuth を使用する API リクエストの場合、1 時 {% data reusables.enterprise.rate_limit %} -[Search API にはカスタムのレート制限ルール](/v3/search/#rate-limit)があることに注意してください。 +[Search API にはカスタムのレート制限ルール](/rest/reference/search#rate-limit)があることに注意してください。 API リクエストの返された HTTP ヘッダは、現在のレート制限ステータスを示しています。 @@ -354,7 +354,7 @@ new Date(1372700873 * 1000) > } ``` -API ヒットを発生させることなく、[レート制限ステータスを確認](/v3/rate_limit)できます。 +API ヒットを発生させることなく、[レート制限ステータスを確認](/rest/reference/rate-limit)できます。 #### OAuth アプリケーションの認証されていないレート制限を増やす @@ -585,9 +585,9 @@ JavaScript ハンドラを記述して、コールバックを処理できます #### ISO 8601 タイムスタンプにタイムゾーン情報を明示的に提供する -タイムスタンプを指定できる API 呼び出しの場合、その正確なタイムスタンプを使用します。 これは[コミット API](/v3/git/commits) の例です。 +タイムスタンプを指定できる API 呼び出しの場合、その正確なタイムスタンプを使用します。 これは[コミット API](/rest/reference/git#commits) の例です。 -これらのタイムスタンプは、`2014-02-27T15:05:06+01:00` のようになります。 これらのタイムスタンプを指定する方法については、[こちらの例](/v3/git/commits/#example-input)も参照してください。 +これらのタイムスタンプは、`2014-02-27T15:05:06+01:00` のようになります。 これらのタイムスタンプを指定する方法については、[こちらの例](/rest/reference/git#example-input)も参照してください。 #### `Time-Zone` ヘッダを使用する @@ -597,7 +597,7 @@ JavaScript ハンドラを記述して、コールバックを処理できます $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -つまり、このヘッダが定義するタイムゾーンで API 呼び出しが行われた時のタイムスタンプが生成されます。 たとえば、[コンテンツ API](/v3/repos/contents/) は追加または変更ごとに git コミットを生成し、タイムスタンプとして現在の時刻を使用します。 このヘッダは、現在のタイムスタンプの生成に使用されたタイムゾーンを決定します。 +つまり、このヘッダが定義するタイムゾーンで API 呼び出しが行われた時のタイムスタンプが生成されます。 たとえば、[コンテンツ API](/rest/reference/repos#contents) は追加または変更ごとに git コミットを生成し、タイムスタンプとして現在の時刻を使用します。 このヘッダは、現在のタイムスタンプの生成に使用されたタイムゾーンを決定します。 #### ユーザが最後に認識されたタイムゾーンを使用する diff --git a/translations/ja-JP/content/rest/overview/troubleshooting.md b/translations/ja-JP/content/rest/overview/troubleshooting.md index 8661577e8e..63a188ab00 100644 --- a/translations/ja-JP/content/rest/overview/troubleshooting.md +++ b/translations/ja-JP/content/rest/overview/troubleshooting.md @@ -23,7 +23,7 @@ API で不可解な問題が発生した場合、発生したと思われる問 リソース（_例:_ ユーザ、Issue _など_）のリストにアクセスするほとんどの API 呼び出しは、ページネーションをサポートしています。 リクエストをして、すべての結果を受け取っていない場合は、おそらく最初のページしか表示されていません。 より多くの結果を受け取るには、残りのページをリクエストする必要があります。 -ページネーション URL のフォーマットを推測*しない*ことが重要です。 すべての API 呼び出しで同じ構造が使用されるわけではありません。 代わりに、すべてのリクエストで送信される [Link Header](/v3/#pagination) からページネーション情報を抽出します。 +ページネーション URL のフォーマットを推測*しない*ことが重要です。 すべての API 呼び出しで同じ構造が使用されるわけではありません。 代わりに、すべてのリクエストで送信される [Link Header](/rest#pagination) からページネーション情報を抽出します。 {% if currentVersion == "free-pro-team@latest" %} ### Basic authentication errors diff --git a/translations/ja-JP/content/rest/reference/apps.md b/translations/ja-JP/content/rest/reference/apps.md index 598ada4c2b..db750025db 100644 --- a/translations/ja-JP/content/rest/reference/apps.md +++ b/translations/ja-JP/content/rest/reference/apps.md @@ -18,7 +18,7 @@ GitHub App として認証されると、GitHub Apps API を使用して、GitHu GitHub App として認証されている場合、REST API v3 エンドポイントにアクセスできます。 これらのエンドポイントには、「Works with GitHub Apps」という箇条書きを含む「注釈」セクションがあります。 ユーザとして認証されている場合、これらのエンドポイントにアクセスすることもできます。 -REST API v3 エンドポイントのサブセットでは、GitHub App のインストールとして認証する必要があります。 これらのエンドポイントの一覧については、[Installations](/v3/apps/installations/) を参照してください。 +REST API v3 エンドポイントのサブセットでは、GitHub App のインストールとして認証する必要があります。 これらのエンドポイントの一覧については、[Installations](/rest/reference/apps#installations) を参照してください。 {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -36,7 +36,7 @@ REST API v3 エンドポイントのサブセットでは、GitHub App のイン Installations API を使用すると、GitHub App のインストールに関する情報を取得して、それらのインストール内でアクションを実行できます。 _インストレーション_とは、アプリケーションをインストールしたユーザまたは Organization のアカウントを指します。 インストレーションとして認証し、特定のリポジトリへのアクセスを制限する方法については、「[インストレーションとして認証する](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)」を参照してください。 -Organization のすべての GitHub App インストレーションを一覧表示するには、「[Organization のアプリケーションインストールの一覧表示](/v3/orgs/#list-app-installations-for-an-organization)」を参照してください。 +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 %} @@ -70,4 +70,4 @@ Organization のすべての GitHub App インストレーションを一覧表 {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} 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 93c96f702d..d13e59de8d 100644 --- a/translations/ja-JP/content/rest/reference/codes-of-conduct.md +++ b/translations/ja-JP/content/rest/reference/codes-of-conduct.md @@ -9,6 +9,6 @@ versions: github-ae: '*' --- -Codes of Conduct API を使用して、リポジトリの行動規範に関する情報を取得できます。 リポジトリの行動規範を取得するには、「[Get a repository](/v3/repos/#get-a-repository)」エンドポイントを使用します。 +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/enterprise-admin.md b/translations/ja-JP/content/rest/reference/enterprise-admin.md index de5cc1a321..a448ae41b2 100644 --- a/translations/ja-JP/content/rest/reference/enterprise-admin.md +++ b/translations/ja-JP/content/rest/reference/enterprise-admin.md @@ -86,7 +86,7 @@ IdP は、SCIM エンドポイントとして `{% data variables.product.api_url {% note %} -**注釈:** Enterprise SCIM API は、[SAML SSO](/v3/auth/#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Enterprise でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 +**注釈:** Enterprise SCIM API は、[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Enterprise でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/rest/reference/git.md b/translations/ja-JP/content/rest/reference/git.md index 2d169a7483..ed8c8b03ed 100644 --- a/translations/ja-JP/content/rest/reference/git.md +++ b/translations/ja-JP/content/rest/reference/git.md @@ -34,7 +34,7 @@ Git blob (バイナリラージオブジェクト) は、各ファイルのコ ## コミット -Git コミットは、Git リポジトリ内の階層（[Git ツリー](/v3/git/trees)）とファイルのコンテンツ（[Git blob](/v3/git/blobs)）のスナップショットです。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [コミットオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects)の読み書きができます。 +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 %} @@ -50,7 +50,7 @@ Git リファレンス（`git ref`）は、Git コミット SHA-1 ハッシュ ## タグ -Git タグは [Git リファレンス](/v3/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)のみをサポートし、軽量タグはサポートしません。 +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 %} diff --git a/translations/ja-JP/content/rest/reference/issues.md b/translations/ja-JP/content/rest/reference/issues.md index db57f7d6a2..05060448b1 100644 --- a/translations/ja-JP/content/rest/reference/issues.md +++ b/translations/ja-JP/content/rest/reference/issues.md @@ -33,7 +33,7 @@ Issue についてサポートされているメディアタイプは次のと Issue コメント API は、Issue およびプルリクエストに関するリスト、表示、編集、コメントの作成に対応しています。 -Issue コメントは、[3 つのカスタムメディアタイプ](#custom-media-types)を使用します。 API におけるメディアタイプの使用に関する詳細は、[こちら](/v3/media/)を参照してください。 +Issue コメントは、[3 つのカスタムメディアタイプ](#custom-media-types)を使用します。 API におけるメディアタイプの使用に関する詳細は、[こちら](/rest/overview/media-types)を参照してください。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} diff --git a/translations/ja-JP/content/rest/reference/licenses.md b/translations/ja-JP/content/rest/reference/licenses.md index d6abb10645..089ba047de 100644 --- a/translations/ja-JP/content/rest/reference/licenses.md +++ b/translations/ja-JP/content/rest/reference/licenses.md @@ -16,12 +16,12 @@ versions: **注釈:** 以下のエンドポイントも、リポジトリのライセンス情報を返します。 -- [リポジトリの Get](/v3/repos/#get-a-repository) -- [ユーザのリポジトリの一覧表示](/v3/repos/#list-repositories-for-a-user) -- [Organization リポジトリの一覧表示](/v3/repos/#list-organization-repositories) +- [リポジトリの Get](/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 リポジトリの一覧表示](/v3/teams/#list-team-repositories) +- [Team リポジトリの一覧表示](/rest/reference/teams#list-team-repositories) {% warning %} diff --git a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md index 05341be0ad..1e6eecdbe9 100644 --- a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md @@ -19,63 +19,63 @@ GitHub Appは、デフォルトで`Read-only`メタデータ権限を持ちま {% data reusables.apps.metadata-permissions %} -- [`GET /`](/v3/#root-endpoint) -- [`GET /codes_of_conduct`](/v3/codes_of_conduct/#get-all-codes-of-conduct) -- [`GET /codes_of_conduct/:key`](/v3/codes_of_conduct/#get-a-code-of-conduct) -- [`GET /emojis`](/v3/emojis/#emojis) +- [`GET /`](/rest#root-endpoint) +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +- [`GET /emojis`](/rest/reference/emojis#emojis) - [`GET /feeds`](/rest/reference/activity#get-feeds) -- [`GET /licenses`](/v3/licenses/#get-all-commonly-used-licenses) -- [`GET /licenses/:key`](/v3/licenses/#get-a-license) -- [`POST /markdown`](/v3/markdown/#render-a-markdown-document) -- [`POST /markdown/raw`](/v3/markdown/#render-a-markdown-document-in-raw-mode) -- [`GET /meta`](/v3/meta/#meta) -- [`GET /organizations`](/v3/orgs/#list-organizations) -- [`GET /orgs/:org`](/v3/orgs/#get-an-organization) -- [`GET /orgs/:org/projects`](/v3/projects/#list-organization-projects) -- [`GET /orgs/:org/repos`](/v3/repos/#list-organization-repositories) -- [`GET /rate_limit`](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) -- [`GET /repos/:owner/:repo`](/v3/repos/#get-a-repository) +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license) +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +- [`GET /meta`](/rest/reference/meta#meta) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization) +- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects) +- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories) +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/community/profile`](/v3/repos/community/#get-community-profile-metrics) +- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics) {% endif %} -- [`GET /repos/:owner/:repo/contributors`](/v3/repos/#list-repository-contributors) +- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors) - [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks) -- [`GET /repos/:owner/:repo/languages`](/v3/repos/#list-repository-languages) -- [`GET /repos/:owner/:repo/license`](/v3/licenses/#get-the-license-for-a-repository) +- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository) - [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers) -- [`GET /repos/:owner/:repo/stats/code_frequency`](/v3/repos/statistics/#get-the-weekly-commit-activity) -- [`GET /repos/:owner/:repo/stats/commit_activity`](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -- [`GET /repos/:owner/:repo/stats/contributors`](/v3/repos/statistics/#get-all-contributor-commit-activity) -- [`GET /repos/:owner/:repo/stats/participation`](/v3/repos/statistics/#get-the-weekly-commit-count) -- [`GET /repos/:owner/:repo/stats/punch_card`](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity) +- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity) +- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity) +- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count) +- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) - [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers) -- [`GET /repos/:owner/:repo/tags`](/v3/repos/#list-repository-tags) -- [`GET /repos/:owner/:repo/topics`](/v3/repos#get-all-repository-topics) -- [`GET /repositories`](/v3/repos/#list-public-repositories) -- [`GET /user/repos`](/v3/repos/#list-repositories-for-the-authenticated-user) +- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) - [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) - [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) -- [`GET /users`](/v3/users/#list-users) -- [`GET /users/:username`](/v3/users/#get-a-user) -- [`GET /users/:username/followers`](/v3/users/followers/#list-followers-of-a-user) -- [`GET /users/:username/following`](/v3/users/followers/#list-the-people-a-user-follows) -- [`GET /users/:username/following/:target_user`](/v3/users/followers/#check-if-a-user-follows-another-user) -- [`GET /users/:username/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) -- [`GET /users/:username/orgs`](/v3/orgs/#list-organizations-for-a-user) +- [`GET /users`](/rest/reference/users#list-users) +- [`GET /users/:username`](/rest/reference/users#get-a-user) +- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user) - [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) - [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) -- [`GET /users/:username/repos`](/v3/repos/#list-repositories-for-a-user) +- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) _コラボレータ_ -- [`GET /repos/:owner/:repo/collaborators`](/v3/repos/collaborators/#list-repository-collaborators) -- [`GET /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) +- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) +- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) _コミットのコメント_ -- [`GET /repos/:owner/:repo/comments`](/v3/repos/comments/#list-commit-comments-for-a-repository) -- [`GET /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#get-a-commit-comment) -- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-commit-comment) -- [`GET /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#list-commit-comments) +- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) +- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) +- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) _イベント_ - [`GET /events`](/rest/reference/activity#list-public-events) @@ -86,311 +86,311 @@ _イベント_ - [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user) _Git_ -- [`GET /gitignore/templates`](/v3/gitignore/#get-all-gitignore-templates) -- [`GET /gitignore/templates/:key`](/v3/gitignore/#get-a-gitignore-template) +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) +- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) _キー_ -- [`GET /users/:username/keys`](/v3/users/keys/#list-public-keys-for-a-user) +- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) _Organizationメンバー_ -- [`GET /orgs/:org/members`](/v3/orgs/members/#list-organization-members) -- [`GET /orgs/:org/members/:username`](/v3/orgs/members/#check-organization-membership-for-a-user) -- [`GET /orgs/:org/public_members`](/v3/orgs/members/#list-public-organization-members) -- [`GET /orgs/:org/public_members/:username`](/v3/orgs/members/#check-public-organization-membership-for-a-user) +- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`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) _検索_ -- [`GET /search/code`](/v3/search/#search-code) -- [`GET /search/commits`](/v3/search/#search-commits) -- [`GET /search/issues`](/v3/search/#search-issues-and-pull-requests) -- [`GET /search/labels`](/v3/search/#search-labels) -- [`GET /search/repositories`](/v3/search/#search-repositories) -- [`GET /search/topics`](/v3/search/#search-topics) -- [`GET /search/users`](/v3/search/#search-users) +- [`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) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) {% if currentVersion == "free-pro-team@latest" %} ### "actions"に対する権限 -- [`GET /repos/:owner/:repo/actions/artifacts`](/v3/actions/artifacts/#list-artifacts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} ### "administration"に対する権限 -- [`POST /orgs/:org/repos`](/v3/repos/#create-an-organization-repository) (:write) -- [`PATCH /repos/:owner/:repo`](/v3/repos/#update-a-repository) (:write) -- [`DELETE /repos/:owner/:repo`](/v3/repos/#delete-a-repository) (:write) +- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) +- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) +- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) (:read) -- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) (:write)git +- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write)git {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#enable-automated-security-fixes) (:write) +- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#disable-automated-security-fixes) (:write) +- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:write) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write) {% endif %} -- [`PUT /repos/:owner/:repo/topics`](/v3/repos/#replace-all-repository-topics) (:write) -- [`POST /repos/:owner/:repo/transfer`](/v3/repos/#transfer-a-repository) (:write) +- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write) +- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#disable-vulnerability-alerts) (:write) +- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write) {% endif %} -- [`PATCH /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#accept-a-repository-invitation) (:write) -- [`DELETE /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#decline-a-repository-invitation) (:write) +- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write) +- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write) _ブランチ_ -- [`GET /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#get-branch-protection) (:read) -- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#update-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#delete-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#get-admin-branch-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#set-admin-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#delete-admin-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#get-pull-request-review-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#update-pull-request-review-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#delete-pull-request-review-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#get-commit-signature-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#create-commit-signature-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#delete-commit-signature-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#get-status-checks-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#update-status-check-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#remove-status-check-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#get-all-status-check-contexts) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#add-status-check-contexts) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#set-status-check-contexts) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#remove-status-check-contexts) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#get-access-restrictions) (:read) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#delete-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#add-team-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#set-team-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#remove-team-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#add-user-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#set-user-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read) +- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) _コラボレータ_ -- [`PUT /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#add-a-repository-collaborator) (:write) -- [`DELETE /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#remove-a-repository-collaborator) (:write) +- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) +- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) _招待_ -- [`GET /repos/:owner/:repo/invitations`](/v3/repos/invitations/#list-repository-invitations) (:read) -- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#update-a-repository-invitation) (:write) -- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#delete-a-repository-invitation) (:write) +- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) +- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) +- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) _キー_ -- [`GET /repos/:owner/:repo/keys`](/v3/repos/keys/#list-deploy-keys) (:read) -- [`POST /repos/:owner/:repo/keys`](/v3/repos/keys/#create-a-deploy-key) (:write) -- [`GET /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#get-a-deploy-key) (:read) -- [`DELETE /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#delete-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) +- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) +- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) _Team_ -- [`GET /repos/:owner/:repo/teams`](/v3/repos/#list-repository-teams) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:write) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) +- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) {% if currentVersion == "free-pro-team@latest" %} _トラフィック_ -- [`GET /repos/:owner/:repo/traffic/clones`](/v3/repos/traffic/#get-repository-clones) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/paths`](/v3/repos/traffic/#get-top-referral-paths) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/v3/repos/traffic/#get-top-referral-sources) (:read) -- [`GET /repos/:owner/:repo/traffic/views`](/v3/repos/traffic/#get-page-views) (:read) +- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) +- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### "blocking"に対する権限 -- [`GET /user/blocks`](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) (:read) -- [`GET /user/blocks/:username`](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) -- [`PUT /user/blocks/:username`](/v3/users/blocking/#block-a-user) (:write) -- [`DELETE /user/blocks/:username`](/v3/users/blocking/#unblock-a-user) (:write) +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) +- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) +- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (:write) +- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) {% endif %} ### "checks"に対する権限 -- [`POST /repos/:owner/:repo/check-runs`](/v3/checks/runs/#create-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#update-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`POST /repos/:owner/:repo/check-suites`](/v3/checks/suites/#create-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/v3/checks/suites/#update-repository-preferences-for-check-suites) (:write) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) +- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (:write) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) ### "contents"に対する権限 -- [`GET /repos/:owner/:repo/:archive_format/:ref`](/v3/repos/contents/#download-a-repository-archive) (:read) +- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:write) +- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#get-a-repository-secret) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) +- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) +- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/commits`](/v3/repos/commits/#list-commits) (:read) -- [`GET /repos/:owner/:repo/commits/:sha`](/v3/repos/commits/#get-a-commit) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/community/code_of_conduct`](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/compare/:base...:head`](/v3/repos/commits/#compare-two-commits) (:read) -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read) +- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`POST /repos/:owner/:repo/dispatches`](/v3/repos/#create-a-repository-dispatch-event) (:write) +- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:read) -- [`POST /repos/:owner/:repo/merges`](/v3/repos/merging/#merge-a-branch) (:write) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#merge-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/v3/repos/contents/#get-a-repository-readme) (:read) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read) +- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read) _ブランチ_ -- [`GET /repos/:owner/:repo/branches`](/v3/repos/branches/#list-branches) (:read) -- [`GET /repos/:owner/:repo/branches/:branch`](/v3/repos/branches/#get-a-branch) (:read) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#list-apps-with-access-to-the-protected-branch) (:write) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#add-app-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#set-app-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read) +- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) _コミットのコメント_ -- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#update-a-commit-comment) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#delete-a-commit-comment) (:write) -- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-commit-comment) (:read) -- [`POST /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#create-a-commit-comment) (:read) +- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) +- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) +- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read) _Git_ -- [`POST /repos/:owner/:repo/git/blobs`](/v3/git/blobs/#create-a-blob) (:write) -- [`GET /repos/:owner/:repo/git/blobs/:sha`](/v3/git/blobs/#get-a-blob) (:read) -- [`POST /repos/:owner/:repo/git/commits`](/v3/git/commits/#create-a-commit) (:write) -- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/v3/git/commits/#get-a-commit) (:read) -- [`POST /repos/:owner/:repo/git/refs`](/v3/git/refs/#create-a-reference) (:write) -- [`GET /repos/:owner/:repo/git/ref/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/v3/git/refs/#list-matching-references) (:read) -- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#update-a-reference) (:write) -- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#delete-a-reference) (:write) -- [`POST /repos/:owner/:repo/git/tags`](/v3/git/tags/#create-a-tag-object) (:write) -- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/v3/git/tags/#get-a-tag) (:read) -- [`POST /repos/:owner/:repo/git/trees`](/v3/git/trees/#create-a-tree) (:write) -- [`GET /repos/:owner/:repo/git/trees/:sha`](/v3/git/trees/#get-a-tree) (:read) +- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write) +- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (:read) +- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (:write) +- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (:read) +- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (:write) +- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (:read) +- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (:read) +- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (:write) +- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (:write) +- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (:write) +- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (:read) +- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (:write) +- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) {% if currentVersion == "free-pro-team@latest" %} _インポート_ -- [`GET /repos/:owner/:repo/import`](/v3/migrations/source_imports/#get-an-import-status) (:read) -- [`PUT /repos/:owner/:repo/import`](/v3/migrations/source_imports/#start-an-import) (:write) -- [`PATCH /repos/:owner/:repo/import`](/v3/migrations/source_imports/#update-an-import) (:write) -- [`DELETE /repos/:owner/:repo/import`](/v3/migrations/source_imports/#cancel-an-import) (:write) -- [`GET /repos/:owner/:repo/import/authors`](/v3/migrations/source_imports/#get-commit-authors) (:read) -- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/v3/migrations/source_imports/#map-a-commit-author) (:write) -- [`GET /repos/:owner/:repo/import/large_files`](/v3/migrations/source_imports/#get-large-files) (:read) -- [`PATCH /repos/:owner/:repo/import/lfs`](/v3/migrations/source_imports/#update-git-lfs-preference) (:write) +- [`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) +- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (:write) +- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (:read) +- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (:write) +- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (:read) +- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) {% endif %} _リアクション_ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% endif %} _リリース_ - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read) @@ -419,195 +419,195 @@ _リリース_ ### "emails"に対する権限 {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /user/email/visibility`](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) (:write) +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) {% endif %} -- [`GET /user/emails`](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) (:read) -- [`POST /user/emails`](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) (:write) -- [`DELETE /user/emails`](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) (:write) -- [`GET /user/public_emails`](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) (:read) +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (:write) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (:write) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) {% endif %} ### "followers"に対する権限 -- [`GET /user/followers`](/v3/users/followers/#list-followers-of-a-user) (:read) -- [`GET /user/following`](/v3/users/followers/#list-the-people-a-user-follows) (:read) -- [`GET /user/following/:username`](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) (:read) -- [`PUT /user/following/:username`](/v3/users/followers/#follow-a-user) (:write) -- [`DELETE /user/following/:username`](/v3/users/followers/#unfollow-a-user) (:write) +- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) +- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) +- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (:read) +- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) +- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) ### "gpg keys"に対する権限 -- [`GET /user/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) (:read) -- [`POST /user/gpg_keys`](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) (:write) -- [`GET /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) (:read) -- [`DELETE /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (:read) +- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) ### "issues"に対する権限 -Issueとプルリクエストには密接な関係があります。 詳細は、「[認証済みユーザに割り当てられたIssueのリスト](/v3/issues/#list-issues-assigned-to-the-authenticated-user)」を参照してください。 GitHub Appに、Issueに対する権限があってプルリクエストに対する権限がない場合、そのエンドポイントはIssueに限定されます。 Issueとプルリクエストの両方を返すエンドポイントがフィルターされます。 Issueとプルリクエストの両方に対する操作が可能なエンドポイントは、Issueに限定されます。 +Issueとプルリクエストには密接な関係があります。 詳細は、「[認証済みユーザに割り当てられたIssueのリスト](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)」を参照してください。 GitHub Appに、Issueに対する権限があってプルリクエストに対する権限がない場合、そのエンドポイントはIssueに限定されます。 Issueとプルリクエストの両方を返すエンドポイントがフィルターされます。 Issueとプルリクエストの両方に対する操作が可能なエンドポイントは、Issueに限定されます。 -- [`GET /repos/:owner/:repo/issues`](/v3/issues/#list-repository-issues) (:read) -- [`POST /repos/:owner/:repo/issues`](/v3/issues/#create-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#get-an-issue) (:read) -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) +- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (:read) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) _アサインされた人_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _イベント_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [Get an issue event](/v3/issues/events/#get-an-issue-event) (:read) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [Get an issue event](/rest/reference/issues#get-an-issue-event) (:read) _ラベル_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _マイルストーン_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _リアクション_ -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} ### "keys"に対する権限 _キー_ -- [`GET /user/keys`](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) (:read) -- [`POST /user/keys`](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) (:write) -- [`GET /user/keys/:key_id`](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) (:read) -- [`DELETE /user/keys/:key_id`](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) +- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) ### "members"に対する権限 {% if currentVersion == "free-pro-team@latest" %} -- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#list-idp-groups-for-a-team) (:write) +- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#create-or-update-idp-group-connections) (:write) +- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write) {% endif %} -- [`GET /orgs/:org/outside_collaborators`](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) (:read) -- [`PUT /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) (:write) -- [`DELETE /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) (:write) +- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read) +- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write) +- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/team-sync/groups`](/v3/teams/team_sync/#list-idp-groups-for-an-organization) (:write) +- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write) {% endif %} -- [`GET /orgs/:org/team/:team_id`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users`](/v3/scim/#list-scim-provisioned-identities) (:read) +- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /scim/v2/orgs/:org/Users`](/v3/scim/#provision-and-invite-a-scim-user) (:write) +- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#get-scim-provisioning-information-for-a-user) (:read) +- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#set-scim-information-for-a-provisioned-user) (:write) +- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#update-an-attribute-for-a-scim-user) (:write) +- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#delete-a-scim-user-from-an-organization) (:write) +- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} _招待_ -- [`GET /orgs/:org/invitations`](/v3/orgs/members/#list-pending-organization-invitations) (:read) -- [`POST /orgs/:org/invitations`](/v3/orgs/members/#create-an-organization-invitation) (:write) -- [`GET /orgs/:org/invitations/:invitation_id/teams`](/v3/orgs/members/#list-organization-invitation-teams) (:read) -- [`GET /teams/:team_id/invitations`](/v3/teams/members/#list-pending-team-invitations) (:read) +- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) +- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) +- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) +- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) {% endif %} _Organizationメンバー_ -- [`DELETE /orgs/:org/members/:username`](/v3/orgs/members/#remove-an-organization-member) (:write) -- [`GET /orgs/:org/memberships/:username`](/v3/orgs/members/#get-organization-membership-for-a-user) (:read) -- [`PUT /orgs/:org/memberships/:username`](/v3/orgs/members/#set-organization-membership-for-a-user) (:write) -- [`DELETE /orgs/:org/memberships/:username`](/v3/orgs/members/#remove-organization-membership-for-a-user) (:write) -- [`PUT /orgs/:org/public_members/:username`](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) (:write) -- [`DELETE /orgs/:org/public_members/:username`](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) (:write) -- [`GET /user/memberships/orgs`](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) (:read) -- [`GET /user/memberships/orgs/:org`](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) (:read) -- [`PATCH /user/memberships/orgs/:org`](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) +- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) +- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) +- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (:write) +- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (:write) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (:read) +- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) +- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) _Teamメンバー_ -- [`GET /teams/:team_id/members`](/v3/teams/members/#list-team-members) (:read) -- [`GET /teams/:team_id/memberships/:username`](/v3/teams/members/#get-team-membership-for-a-user) (:read) -- [`PUT /teams/:team_id/memberships/:username`](/v3/teams/members/#add-or-update-team-membership-for-a-user) (:write) -- [`DELETE /teams/:team_id/memberships/:username`](/v3/teams/members/#remove-team-membership-for-a-user) (:write) +- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) +- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) +- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) +- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) _Team_ -- [`GET /orgs/:org/teams`](/v3/teams/#list-teams) (:read) -- [`POST /orgs/:org/teams`](/v3/teams/#create-a-team) (:write) -- [`GET /orgs/:org/teams/:team_slug`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) +- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) +- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -- [`GET /teams/:team_id`](/v3/teams/#get-a-team) (:read) +- [`GET /teams/:team_id`](/rest/reference/teams#get-a-team) (:read) {% endif %} -- [`PATCH /teams/:team_id`](/v3/teams/#update-a-team) (:write) -- [`DELETE /teams/:team_id`](/v3/teams/#delete-a-team) (:write) +- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write) +- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`GET /teams/:team_id/projects`](/v3/teams/#list-team-projects) (:read) -- [`GET /teams/:team_id/projects/:project_id`](/v3/teams/#check-team-permissions-for-a-project) (:read) -- [`PUT /teams/:team_id/projects/:project_id`](/v3/teams/#add-or-update-team-project-permissions) (:read) -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read) +- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read) +- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% endif %} -- [`GET /teams/:team_id/repos`](/v3/teams/#list-team-repositories) (:read) -- [`GET /teams/:team_id/repos/:owner/:repo`](/v3/teams/#check-team-permissions-for-a-repository) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:read) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) -- [`GET /teams/:team_id/teams`](/v3/teams/#list-child-teams) (:read) +- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read) +- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) +- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) ### "organization administration"に対する権限 -- [`PATCH /orgs/:org`](/v3/orgs/#update-an-organization) (:write) +- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/interaction-limits`](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) (:read) +- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /orgs/:org/interaction-limits`](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) (:write) +- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /orgs/:org/interaction-limits`](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) (:write) +- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) {% endif %} ### "organization hooks"に対する権限 @@ -620,7 +620,7 @@ _Team_ - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write) _Team_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if enterpriseServerVersions contains currentVersion %} ### "organization pre receive hooks"に対する権限 @@ -633,31 +633,31 @@ _Team_ ### "organization projects"に対する権限 -- [`POST /orgs/:org/projects`](/v3/projects/#create-an-organization-project) (:write) -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) +- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) {% if currentVersion == "free-pro-team@latest" %} ### "organization user blocking"に対する権限 -- [`GET /orgs/:org/blocks`](/v3/orgs/blocking/#list-users-blocked-by-an-organization) (:read) -- [`GET /orgs/:org/blocks/:username`](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) (:read) -- [`PUT /orgs/:org/blocks/:username`](/v3/orgs/blocking/#block-a-user-from-an-organization) (:write) -- [`DELETE /orgs/:org/blocks/:username`](/v3/orgs/blocking/#unblock-a-user-from-an-organization) (:write) +- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) +- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) +- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (:write) +- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) {% endif %} ### "pages"に対する権限 @@ -675,99 +675,99 @@ _Team_ プルリクエストとIssueには密接な関係があります。 GitHub Appに、プルリクエストに対する権限があってIssueに対する権限がない場合、そのエンドポイントはプルリクエストに限定されます。 プルリクエストとIssueの両方を返すエンドポイントがフィルターされます。 プルリクエストとIssueの両方に対する操作が可能なエンドポイントは、プルリクエストに限定されます。 -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls`](/v3/pulls/#list-pull-requests) (:read) -- [`POST /repos/:owner/:repo/pulls`](/v3/pulls/#create-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#get-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#update-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#list-review-comments-on-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/v3/pulls/#list-commits-on-a-pull-request) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/v3/pulls/#list-pull-requests-files) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#check-if-a-pull-request-has-been-merged) (:read) -- [`GET /repos/:owner/:repo/pulls/comments`](/v3/pulls/comments/#list-review-comments-in-a-repository) (:read) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) (:write) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (:read) +- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (:read) +- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (:read) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) _アサインされた人_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _イベント_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [`GET /repos/:owner/:repo/issues/events/:event_id`](/v3/issues/events/#get-an-issue-event) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) _ラベル_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _マイルストーン_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _リアクション_ -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) (:read) -- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) (:write) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read) +- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} _リクエストされたレビュー担当者_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) _レビュー_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#list-reviews-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#create-a-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#get-a-review-for-a-pull-request) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#update-a-review-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#delete-a-pending-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) ### "repository hooks"に対する権限 -- [`GET /repos/:owner/:repo/hooks`](/v3/repos/hooks/#list-repository-webhooks) (:read) -- [`POST /repos/:owner/:repo/hooks`](/v3/repos/hooks/#create-a-repository-webhook) (:write) -- [`GET /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#get-a-repository-webhook) (:read) -- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#update-a-repository-webhook) (:write) -- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#delete-a-repository-webhook) (:write) -- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/v3/repos/hooks/#ping-a-repository-webhook) (:read) -- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/v3/repos/hooks/#test-the-push-repository-webhook) (:read) +- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) +- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) +- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read) +- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write) +- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write) +- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read) +- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read) {% if enterpriseServerVersions contains currentVersion %} ### "repository pre receive hooks"に対する権限 @@ -780,70 +780,70 @@ _レビュー_ ### "repository projects"に対する権限 -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) -- [`GET /repos/:owner/:repo/projects`](/v3/projects/#list-repository-projects) (:read) -- [`POST /repos/:owner/:repo/projects`](/v3/projects/#create-a-repository-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) +- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) +- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) _Team_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if currentVersion == "free-pro-team@latest" %} ### "secrets"に対する権限 -* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:read) -* [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:read) -* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#get-a-repository-secret) (:read) -* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -* [`GET /orgs/:org/actions/secrets/public-key`](/v3/actions/secrets/#get-an-organization-public-key) (:read) -* [`GET /orgs/:org/actions/secrets`](/v3/actions/secrets/#list-organization-secrets) (:read) -* [`GET /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#get-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-an-organization-secret) (:write) -* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) (:write) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-an-organization-secret) (:write) +* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) +* [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) +* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (:read) +* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (:write) +* [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (:read) +* [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (:read) +* [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (:write) +* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (:write) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### "security events"に対する権限 -- [`GET /repos/:owner/:repo/code-scanning/alerts`](/v3/code-scanning/#list-code-scanning-alerts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/v3/code-scanning/#get-a-code-scanning-alert) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### "self-hosted runners"に対する権限 -- [`GET /orgs/:org/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) (:write) -- [`GET /orgs/:org/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) (:read) -- [`GET /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) (:write) -- [`DELETE /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) +- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) +- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) {% endif %} ### "single file"に対する権限 -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -- [`PUT /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#create-or-update-file-contents) (:write) -- [`DELETE /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#delete-a-file) (:write) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) +- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) ### "starring"に対する権限 @@ -853,23 +853,23 @@ _Team_ ### "statuses"に対する権限 -- [`GET /repos/:owner/:repo/commits/:ref/status`](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/v3/repos/statuses/#list-commit-statuses-for-a-reference) (:read) -- [`POST /repos/:owner/:repo/statuses/:sha`](/v3/repos/statuses/#create-a-commit-status) (:write) +- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) +- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) ### "team discussions"に対する権限 -- [`GET /teams/:team_id/discussions`](/v3/teams/discussions/#list-discussions) (:read) -- [`POST /teams/:team_id/discussions`](/v3/teams/discussions/#create-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#get-a-discussion) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#update-a-discussion) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#delete-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#list-discussion-comments) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#create-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#get-a-discussion-comment) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#update-a-discussion-comment) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#delete-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion-comment) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion) (:write) +- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) +- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/ja-JP/content/rest/reference/pulls.md b/translations/ja-JP/content/rest/reference/pulls.md index d82744b8c2..7e070a9fd1 100644 --- a/translations/ja-JP/content/rest/reference/pulls.md +++ b/translations/ja-JP/content/rest/reference/pulls.md @@ -10,7 +10,7 @@ versions: Pull Request API を使用すると、プルリクエストを一覧表示、編集、作成、マージできます。 プルリクエストのコメントは、[Issue Comments API](/rest/reference/issues#comments) で管理できます。 -すべてのプルリクエストは Issue ですが、すべての Issue がプルリクエストというわけではありません。 このため、アサインされた人、ラベル、マイルストーンなどの操作といった、両方の機能で共通するアクションは、[Issues API](/v3/issues) で提供されます。 +すべてのプルリクエストは Issue ですが、すべての Issue がプルリクエストというわけではありません。 このため、アサインされた人、ラベル、マイルストーンなどの操作といった、両方の機能で共通するアクションは、[Issues API](/rest/reference/issues) で提供されます。 ### プルリクエストのカスタムメディアタイプ @@ -33,16 +33,16 @@ diff が破損している場合は、{% data variables.contact.contact_support プルリクエストには以下のリンク関係が含まれる可能性があります。 -| 名前 | 説明 | -| ----------------- | ------------------------------------------------------------------------------------------------ | -| `self` | プルリクエストの API ロケーション。 | -| `html` | プルリクエストの HTML ロケーション。 | -| `Issue` | プルリクエストの [Issue](/v3/issues/) の API ロケーション。 | -| `コメント` | プルリクエストの [Issue コメント](/v3/issues/comments/) の API ロケーション。 | -| `review_comments` | プルリクエストの [レビューコメント](/v3/pulls/comments/) の API ロケーション。 | -| `review_comment` | プルリクエストのリポジトリで、[レビューコメント](/v3/pulls/comments/)の API ロケーションを構築するための[URL テンプレート](/v3/#hypermedia)。 | -| `commits` | プルリクエストの [コミット](#list-commits-on-a-pull-request) の API ロケーション。 | -| `ステータス` | プルリクエストの[コミットステータス](/v3/repos/statuses/)、すなわち`head` ブランチのステータスの API ロケーション。 | +| 名前 | 説明 | +| ----------------- | ------------------------------------------------------------------------------------------------------------ | +| `self` | プルリクエストの API ロケーション。 | +| `html` | プルリクエストの HTML ロケーション。 | +| `Issue` | プルリクエストの [Issue](/rest/reference/issues) の API ロケーション。 | +| `コメント` | プルリクエストの [Issue コメント](/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/repos#statuses)、すなわち`head` ブランチのステータスの API ロケーション。 | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/ja-JP/content/rest/reference/rate-limit.md b/translations/ja-JP/content/rest/reference/rate-limit.md index 49bbb7b736..284b288e01 100644 --- a/translations/ja-JP/content/rest/reference/rate-limit.md +++ b/translations/ja-JP/content/rest/reference/rate-limit.md @@ -13,18 +13,18 @@ REST API 概要ドキュメンテーションでは、[レート制限のルー ### レート制限のステータスを理解する -Search APIは[カスタムのレート制限](/v3/search/#rate-limit)を持ち、他のREST APIを管理するレート制限とは分離されています。 GraphQL APIも[カスタムのレート制限](/v4/guides/resource-limitations/#rate-limit)を持ち、REST APIのレート制限とは分離されて別に計算されます。 +Search APIは[カスタムのレート制限](/rest/reference/search#rate-limit)を持ち、他のREST APIを管理するレート制限とは分離されています。 GraphQL APIも[カスタムのレート制限](/graphql/overview/resource-limitations#rate-limit)を持ち、REST APIのレート制限とは分離されて別に計算されます。 そのため、Rate Limit APIのレスポンスは、レート制限を分類します。 `resources` の下には、4 つのオブジェクトがあります。 * `core`オブジェクトは、REST API中の検索に関連しないすべてのリソースに関するレート制限のステータスを提供します。 -* `search`オブジェクトは、[Search API](/v3/search/)に対するレート制限のステータスを提供します。 +* `search`オブジェクトは、[Search API](/rest/reference/search)に対するレート制限のステータスを提供します。 -* `graphql`オブジェクトは、[GraphQL API](/v4/)に対するレート制限のステータスを提供します。 +* `graphql`オブジェクトは、[GraphQL API](/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)エンドポイントに対するレート制限のステータスを提供します。 -レート制限レスポンス中のヘッダと値に関する詳しい情報については「[レート制限](/v3/#rate-limiting)」を参照してください。 +レート制限レスポンス中のヘッダと値に関する詳しい情報については「[レート制限](/rest#rate-limiting)」を参照してください。 {% include rest_operations_at_current_path %} diff --git a/translations/ja-JP/content/rest/reference/repos.md b/translations/ja-JP/content/rest/reference/repos.md index 65b924487b..f51ada9f27 100644 --- a/translations/ja-JP/content/rest/reference/repos.md +++ b/translations/ja-JP/content/rest/reference/repos.md @@ -29,7 +29,7 @@ versions: ### コミットコメントのカスタムメディアタイプ -以下がコミットコメントでサポートされているメディアタイプです。 API におけるメディアタイプの使用に関する詳細は、[こちら](/v3/media/)を参照してください。 +以下がコミットコメントでサポートされているメディアタイプです。 API におけるメディアタイプの使用に関する詳細は、[こちら](/rest/overview/media-types)を参照してください。 application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json @@ -65,7 +65,7 @@ Repo Commits API は、リポジトリ内の子コミットのリスティング ### リポジトリコンテンツのカスタムメディアタイプ -[README](/v3/repos/contents/#get-a-repository-readme)、[ファイル](/v3/repos/contents/#get-repository-content)、[シンボリックリンク](/v3/repos/contents/#get-repository-content)は以下のカスタムメディアタイプをサポートしています。 +[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 @@ -74,13 +74,13 @@ Repo Commits API は、リポジトリ内の子コミットのリスティング Markdown や AsciiDoc などのマークアップファイルでは、`.html` メディアタイプを使用して、レンダリングされた HTML を取得できます。 マークアップ言語は、オープンソースの[マークアップライブラリ](https://github.com/github/markup)を使用して HTML にレンダリングされます。 -[すべてのオブジェクト](/v3/repos/contents/#get-repository-content)は、以下のカスタムメディアタイプをサポートしています。 +[すべてのオブジェクト](/rest/reference/repos#get-repository-content)は、以下のカスタムメディアタイプをサポートしています。 application/vnd.github.VERSION.object コンテンツのタイプに関係なく、一貫したオブジェクトフォーマットを取得するには、`object` メディアタイプパラメータを使用します。 たとえば、レスポンスはディレクトリに対するオブジェクトの配列ではなく、オブジェクトの配列を含む `entries` 属性のオブジェクトになります。 -You can read more about the use of media types in the API [here](/v3/media/). +API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %} diff --git a/translations/ja-JP/content/rest/reference/scim.md b/translations/ja-JP/content/rest/reference/scim.md index 4440700707..b77ea5b771 100644 --- a/translations/ja-JP/content/rest/reference/scim.md +++ b/translations/ja-JP/content/rest/reference/scim.md @@ -12,7 +12,7 @@ SCIM API は SCIM を有効にしたアイデンティティプロバイダ (IdP {% note %} -**注釈:** SCIM API は、[SAML SSO](/v3/auth/#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Organization でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 +**注釈:** SCIM API は、[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Organization でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/rest/reference/search.md b/translations/ja-JP/content/rest/reference/search.md index 0313b752ba..dee7e09695 100644 --- a/translations/ja-JP/content/rest/reference/search.md +++ b/translations/ja-JP/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: Search API は、見つけたい特定の項目を検索するために役立ちます。 たとえば、リポジトリ内のユーザや特定のファイルを見つけることができます。 Google で検索を実行するのと同じように考えてください。 Search API は、探している 1 つの結果 (または探しているいくつかの結果) を見つけるために役立つよう設計されています。 Google で検索する場合と同じように、ニーズに最も合う項目を見つけるため、検索結果を数ページ表示したい場合もあるでしょう。 こうしたニーズを満たすため、{% data variables.product.product_name %} Search API では**各検索につき 最大 1,000 件の結果**を提供します。 -クエリを使って、検索を絞り込めます。 検索クエリ構文の詳細については、「[検索クエリの構築](/v3/search/#constructing-a-search-query)」を参照してください。 +クエリを使って、検索を絞り込めます。 To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." ### 検索結果を順番づける @@ -18,7 +18,7 @@ Search API は、見つけたい特定の項目を検索するために役立ち ### レート制限 -Search API にはカスタムレート制限があります。 リクエストに[基本認証](/v3/#authentication)、[OAuth](/v3/#authentication)、または[クライアント ID とシークレット](/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications)を使用する場合は、1 分間に最大 30 件のリクエストが行えます。 認証されていないリクエストでは、レート制限により 1 分間あたり最大 10 件のリクエストが行えます。 +Search API にはカスタムレート制限があります。 For requests using [Basic Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. 認証されていないリクエストでは、レート制限により 1 分間あたり最大 10 件のリクエストが行えます。 {% data reusables.enterprise.rate_limit %} diff --git a/translations/ja-JP/content/rest/reference/teams.md b/translations/ja-JP/content/rest/reference/teams.md index dde837042b..03bbe2cd7b 100644 --- a/translations/ja-JP/content/rest/reference/teams.md +++ b/translations/ja-JP/content/rest/reference/teams.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -この API は、Team の [Organization](/v3/orgs) の、認証済みメンバーのみが利用できます。 OAuth のアクセストークンは、 `read:org` [スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を必要とします。 {% data variables.product.prodname_dotcom %} は、Team の `name` からTeam の `slug` を生成します。 +この 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 %} @@ -16,7 +16,7 @@ versions: ## ディスカッション -Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/v3/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. この API は、Team の Organization の、認証済みメンバーのみが利用できます。 +Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). この API は、Team の Organization の、認証済みメンバーのみが利用できます。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -24,7 +24,7 @@ Team ディスカッション API を使用すると、Team のページに投 ## ディスカッションコメント -Team ディスカッションコメント API を使用すると、[Team ディスカッション](/v3/teams/discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/v3/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. この API は、Team の Organization の、認証済みメンバーのみが利用できます。 +Team ディスカッションコメント API を使用すると、[Team ディスカッション](/rest/reference/teams#discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. この API は、Team の Organization の、認証済みメンバーのみが利用できます。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -58,4 +58,4 @@ Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理で {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} 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 f90a51675b..d9842c4371 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 @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' 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 95775c388b..0d9a08ff06 100644 --- a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/ja-JP/data/reusables/apps/app-ruby-guides.md b/translations/ja-JP/data/reusables/apps/app-ruby-guides.md index fe649b0de5..19a860b9e9 100644 --- a/translations/ja-JP/data/reusables/apps/app-ruby-guides.md +++ b/translations/ja-JP/data/reusables/apps/app-ruby-guides.md @@ -1,5 +1,5 @@ {% note %} -**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/v3/libraries/). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. +**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/rest/overview/libraries). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. {% endnote %} diff --git a/translations/ja-JP/data/reusables/apps/checks-availability.md b/translations/ja-JP/data/reusables/apps/checks-availability.md index 7360c3112d..441b6cc35b 100644 --- a/translations/ja-JP/data/reusables/apps/checks-availability.md +++ b/translations/ja-JP/data/reusables/apps/checks-availability.md @@ -1 +1 @@ -Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/v3/repos/statuses/). +Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/rest/reference/repos#statuses). diff --git a/translations/ja-JP/data/reusables/apps/deletes_ssh_keys.md b/translations/ja-JP/data/reusables/apps/deletes_ssh_keys.md index 6b5e91b011..c1a3e41f10 100644 --- a/translations/ja-JP/data/reusables/apps/deletes_ssh_keys.md +++ b/translations/ja-JP/data/reusables/apps/deletes_ssh_keys.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/v3/guides/managing-deploy-keys/#deploy-keys). +**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys). {% endwarning %} diff --git a/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md index 4ade7302d7..b28bcd97ce 100644 --- a/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**非推奨の注意:** {% data variables.product.prodname_dotcom %}は、クエリパラメータを使ったAPIの認証を廃止します。 Authenticating to the API should be done with [HTTP basic authentication](/v3/auth/#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %}予定された一時停止を含む詳しい情報については[ブログポスト](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)を参照してください。 +**非推奨の注意:** {% data variables.product.prodname_dotcom %}は、クエリパラメータを使ったAPIの認証を廃止します。 Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %}予定された一時停止を含む詳しい情報については[ブログポスト](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)を参照してください。 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. その代わりに、インテグレータはアクセストークン、`client_id`もしくは`client_secret`をヘッダに移すことをおすすめします。 {% data variables.product.prodname_dotcom %}は、クエリパラメータによる認証の削除を、事前に通知します。 {% endif %} diff --git a/translations/ja-JP/data/reusables/apps/deprecating_github_services_ghe.md b/translations/ja-JP/data/reusables/apps/deprecating_github_services_ghe.md index b3c74c5bfd..659a055902 100644 --- a/translations/ja-JP/data/reusables/apps/deprecating_github_services_ghe.md +++ b/translations/ja-JP/data/reusables/apps/deprecating_github_services_ghe.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} {% note %} -**ノート:** GitHub Enterprise リリース2.17以降では、管理者が新しいGitHub Servicesをインストールすることはできなくなっており、既存のサービスはGitHub Enterprise 2.20以降で動作しなくなります。 サービスをwebhookに更新するためには、[GitHub Servicesの置き換えガイド](/v3/guides/replacing-github-services)が利用できます。 +**ノート:** GitHub Enterprise リリース2.17以降では、管理者が新しいGitHub Servicesをインストールすることはできなくなっており、既存のサービスはGitHub Enterprise 2.20以降で動作しなくなります。 サービスをwebhookに更新するためには、[GitHub Servicesの置き換えガイド](/developers/overview/replacing-github-services)が利用できます。 {% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md b/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md index 6286cd3091..f7b0dd209a 100644 --- a/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), and to exclude the _node_modules_ directory (also relative to the root), as well as any file whose name ends in _.test.js_. +The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. ``` yaml name: "My {% data variables.product.prodname_codeql %} config" @@ -24,9 +24,9 @@ queries: - name: Use a query suite file (run queries from a query suite in this repo) uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls -paths-ignore: - - node_modules - - '**/*.test.js' paths: - src +paths-ignore: + - src/node_modules + - '**/*.test.js' ``` diff --git a/translations/ja-JP/data/reusables/github-actions/matrix-variable-example.md b/translations/ja-JP/data/reusables/github-actions/matrix-variable-example.md new file mode 100644 index 0000000000..ce6e9d6d24 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/matrix-variable-example.md @@ -0,0 +1,26 @@ +In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: + +{% raw %} +```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - node-version: 10.x + site: "prod" + datacenter: "site-a" + - node-version: 12.x + site: "dev" + datacenter: "site-b" + steps: + - name: Echo site details + env: + SITE: ${{ matrix.site }} + DATACENTER: ${{ matrix.datacenter }} + run: echo $SITE $DATACENTER +``` +{% endraw %} diff --git a/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-api.md index 0e62bb6498..53142b325e 100644 --- a/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-api.md +++ b/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-api.md @@ -1 +1 @@ -To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/v3/actions/secrets/)." +To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)." diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 9ac93498fa..d7cc948f28 100644 --- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,12 +1,12 @@ -1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. - ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![リポジトリの権限の管理](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. {% warning %} **Warning** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." + + 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。 {% endwarning %} - diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index e73619ec06..8c59247f56 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -Team同期を有効化すると、チームメンテナとOrganizationのオーナーは、{% data variables.product.prodname_dotcom %}上で、あるいはAPIを通じてTeamをIdPグループに接続できます。 For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/v3/teams/team_sync/)." +Team同期を有効化すると、チームメンテナとOrganizationのオーナーは、{% data variables.product.prodname_dotcom %}上で、あるいはAPIを通じてTeamをIdPグループに接続できます。 For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md b/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md index 6872d48d33..0fd49cd43d 100644 --- a/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md @@ -1,10 +1,10 @@ -| 名前 | 種類 | 説明 | -| ------------ | --------- | -------------------------------------------------------------------- | -| `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `string` | The REST API URL for fetching the event. | -| `actor` | `オブジェクト` | The person who generated the event. | -| `event` | `string` | Identifies the actual type of event that occurred. | -| `commit_id` | `string` | The SHA of the commit that referenced this issue. | -| `commit_url` | `string` | The GitHub REST API link to the commit that referenced this issue. | -| `created_at` | `string` | The timestamp indicating when the event occurred. | +| 名前 | 種類 | 説明 | +| ------------ | --------- | ------------------------------------------------------------------------- | +| `id` | `integer` | The unique identifier of the event. | +| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `string` | The REST API URL for fetching the event. | +| `actor` | `オブジェクト` | The person who generated the event. | +| `event` | `string` | Identifies the actual type of event that occurred. | +| `commit_id` | `string` | The SHA of the commit that referenced this issue. | +| `commit_url` | `string` | The GitHub REST API link to the commit that referenced this issue. | +| `created_at` | `string` | The timestamp indicating when the event occurred. | diff --git a/translations/ja-JP/data/reusables/pre-release-program/corsair-preview.md b/translations/ja-JP/data/reusables/pre-release-program/corsair-preview.md index d5131c62d3..7724c1caaf 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/corsair-preview.md +++ b/translations/ja-JP/data/reusables/pre-release-program/corsair-preview.md @@ -1,6 +1,6 @@ {% note %} -**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.corsair-preview+json diff --git a/translations/ja-JP/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/ja-JP/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md index 6bf0fb2ed4..7bed2bb577 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md +++ b/translations/ja-JP/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Note:** Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)." For more information, see "[Expiring user-to-server access tokens for GitHub Apps](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)." diff --git a/translations/ja-JP/data/reusables/pre-release-program/fury-pre-release.md b/translations/ja-JP/data/reusables/pre-release-program/fury-pre-release.md index 25b74a97ea..adf434c97e 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/fury-pre-release.md +++ b/translations/ja-JP/data/reusables/pre-release-program/fury-pre-release.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} {% note %} -**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.fury-preview+json diff --git a/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md b/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md index d18399b663..82549b4331 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md +++ b/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** To access the API with your GitHub App, you must provide a custom [media type](/v3/media) in the `Accept` Header for your requests. +**Note:** To access the API with your GitHub App, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` Header for your requests. `application/vnd.github.machine-man-preview+json` diff --git a/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md b/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md index fcf2e98e68..ac0d210355 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md +++ b/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.sailor-v-preview+json diff --git a/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md b/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md index 5de305adb6..138455a9eb 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md +++ b/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md @@ -2,7 +2,7 @@ **Note:** Project card details are now shown in REST API responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events). -To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/v3/media) in the `Accept` header: +To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.starfox-preview+json diff --git a/translations/ja-JP/data/reusables/repositories/deploy-keys.md b/translations/ja-JP/data/reusables/repositories/deploy-keys.md index ae039b459e..3f3948dc84 100644 --- a/translations/ja-JP/data/reusables/repositories/deploy-keys.md +++ b/translations/ja-JP/data/reusables/repositories/deploy-keys.md @@ -1 +1 @@ -You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/v3/guides/delivering-deployments/)." +You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)." diff --git a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md index 362623ab06..cd08b87360 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md @@ -1,7 +1,7 @@ | キー | 種類 | 説明 | | --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/v3/checks/runs/#check-runs-and-requested-actions)."
| -| `check_run` | `オブジェクト` | The [check_run](/v3/checks/runs/#get-a-check-run). | +| `action` | `string` | 実行されたアクション。 Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `check_run` | `オブジェクト` | The [check_run](/rest/reference/checks#get-a-check-run). | | `check_run[status]` | `string` | The current status of the check run. Can be `queued`, `in_progress`, or `completed`. | | `check_run[conclusion]` | `string` | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. | | `check_run[name]` | `string` | The name of the check run. | diff --git a/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md b/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md index 19fd0846b8..15cbbb7936 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md @@ -1 +1 @@ -Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/v3/checks/runs/)" REST API. +Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/rest/reference/checks#runs)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md index 8b4637d209..abc6ecc54d 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md @@ -1,7 +1,7 @@ | キー | 種類 | 説明 | | ---------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| -| `check_suite` | `オブジェクト` | The [check_suite](/v3/checks/suites/). | +| `action` | `string` | 実行されたアクション。 Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| +| `check_suite` | `オブジェクト` | The [check_suite](/rest/reference/checks#suites). | | `check_suite[head_branch]` | `string` | The head branch name the changes are on. | | `check_suite[head_sha]` | `string` | The SHA of the most recent commit for this check suite. | | `check_suite[status]` | `string` | The summary status for all check runs that are part of the check suite. Can be `requested`, `in_progress`, or `completed`. | diff --git a/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md b/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md index 00c4c00937..94ed6dc937 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md @@ -1 +1 @@ -Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/v3/checks/suites/)" REST API. +Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/rest/reference/checks#suites)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/commit_comment_properties.md b/translations/ja-JP/data/reusables/webhooks/commit_comment_properties.md index e1e1ba4bc1..7f4ce34c43 100644 --- a/translations/ja-JP/data/reusables/webhooks/commit_comment_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/commit_comment_properties.md @@ -1,4 +1,4 @@ -| キー | 種類 | 説明 | -| -------- | -------- | --------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 `created `になりうる。 | -| `コメント` | `オブジェクト` | [commit comment](/v3/repos/comments/#get-a-commit-comment)リソース。 | +| キー | 種類 | 説明 | +| -------- | -------- | ----------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 `created `になりうる。 | +| `コメント` | `オブジェクト` | [commit comment](/rest/reference/repos#get-a-commit-comment)リソース。 | diff --git a/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md b/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md index 20e258a1ea..7329b1ed61 100644 --- a/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md @@ -1 +1 @@ -A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/v3/repos/comments/)" REST API. +A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/rest/reference/repos#comments)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/create_properties.md b/translations/ja-JP/data/reusables/webhooks/create_properties.md index b64d4fb3ef..e220d6e76a 100644 --- a/translations/ja-JP/data/reusables/webhooks/create_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/create_properties.md @@ -1,6 +1,6 @@ | キー | 種類 | 説明 | | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | +| `ref` | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | | `ref_type` | `string` | リポジトリで作成されたGit refオブジェクトの種類。 `branch`もしくは`tag`になる。 | | `master_branch` | `string` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" %}`main`{% else %}`master`{% endif %}). | | `説明` | `string` | リポジトリの現在の説明。 | diff --git a/translations/ja-JP/data/reusables/webhooks/create_short_desc.md b/translations/ja-JP/data/reusables/webhooks/create_short_desc.md index a43ab39943..5cf906a338 100644 --- a/translations/ja-JP/data/reusables/webhooks/create_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/create_short_desc.md @@ -1 +1 @@ -A Git branch or tag is created. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is created. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/delete_properties.md b/translations/ja-JP/data/reusables/webhooks/delete_properties.md index 5febfb46d6..16e33e07f5 100644 --- a/translations/ja-JP/data/reusables/webhooks/delete_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ -| キー | 種類 | 説明 | -| ---------- | -------- | -------------------------------------------------------- | -| `ref` | `string` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | -| `ref_type` | `string` | リポジトリで削除されたGit refオブジェクトの種類。 `branch`もしくは`tag`になる。 | +| キー | 種類 | 説明 | +| ---------- | -------- | -------------------------------------------------------------- | +| `ref` | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | +| `ref_type` | `string` | リポジトリで削除されたGit refオブジェクトの種類。 `branch`もしくは`tag`になる。 | diff --git a/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md b/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md index 7557d8e4ed..726e68df82 100644 --- a/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md @@ -1 +1 @@ -A Git branch or tag is deleted. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is deleted. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md b/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md index 75981d42a1..b51766f731 100644 --- a/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md @@ -1,4 +1,4 @@ -| キー | 種類 | 説明 | -| -------- | -------- | -------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 Can be either `created` or `deleted`. | -| `キー` | `オブジェクト` | The [`deploy key`](/v3/repos/keys/#get-a-deploy-key) resource. | +| キー | 種類 | 説明 | +| -------- | -------- | -------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 Can be either `created` or `deleted`. | +| `キー` | `オブジェクト` | The [`deploy key`](/rest/reference/repos#get-a-deploy-key) resource. | diff --git a/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md b/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md index c83fe68579..1d4565e788 100644 --- a/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md @@ -1 +1 @@ -A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/v3/repos/keys/)" REST API. +A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/rest/reference/repos#keys)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/fork_properties.md b/translations/ja-JP/data/reusables/webhooks/fork_properties.md index 840d5ff8c5..a7c6752e06 100644 --- a/translations/ja-JP/data/reusables/webhooks/fork_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/fork_properties.md @@ -1,3 +1,3 @@ -| キー | 種類 | 説明 | -| -------- | -------- | ----------------------------------------------------------------- | -| `forkee` | `オブジェクト` | The created [`repository`](/v3/repos/#get-a-repository) resource. | +| キー | 種類 | 説明 | +| -------- | -------- | ---------------------------------------------------------------------------- | +| `forkee` | `オブジェクト` | The created [`repository`](/rest/reference/repos#get-a-repository) resource. | diff --git a/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md b/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md index 60f88625b0..23b9eff136 100644 --- a/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md @@ -1 +1 @@ -A user forks a repository. For more information, see the "[forks](/v3/repos/forks/)" REST API. +A user forks a repository. For more information, see the "[forks](/rest/reference/repos#forks)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md index 63166ba6e2..f1debb10f2 100644 --- a/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md @@ -1 +1 @@ -Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md b/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md index 4abc1de643..21cffb5f50 100644 --- a/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md @@ -1 +1 @@ -Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md index a1ae73ab62..159facecf3 100644 --- a/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md @@ -1 +1 @@ -`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | アクションが`edited`だった場合の、以前のバージョンのbody。 `issue`|`object` | The [issue](/v3/issues/) the comment belongs to. `comment`|`object` | The [comment](/v3/issues/comments/) itself. +`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | アクションが`edited`だった場合の、以前のバージョンのbody。 `issue`|`object` | The [issue](/rest/reference/issues) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/issues#comments) itself. diff --git a/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md b/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md index cc07764d19..dd67c3de2d 100644 --- a/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md @@ -1 +1 @@ -Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/v3/issues/comments/)" REST API. +Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/rest/reference/issues#comments)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/issue_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_properties.md index c146faa968..bff204fc72 100644 --- a/translations/ja-JP/data/reusables/webhooks/issue_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/issue_properties.md @@ -1 +1 @@ -`issue`|`object` | The [issue](/v3/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. +`issue`|`object` | The [issue](/rest/reference/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. diff --git a/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md b/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md index 7dadec073b..3edc02859f 100644 --- a/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/v3/issues/comments/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/rest/reference/issues#comments)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/label_short_desc.md b/translations/ja-JP/data/reusables/webhooks/label_short_desc.md index c5f7178d8a..a634b7faa7 100644 --- a/translations/ja-JP/data/reusables/webhooks/label_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/label_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/v3/issues/labels/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/rest/reference/issues#labels)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/member_properties.md b/translations/ja-JP/data/reusables/webhooks/member_properties.md index d9e1757f40..add035dc19 100644 --- a/translations/ja-JP/data/reusables/webhooks/member_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/member_properties.md @@ -1 +1 @@ -`member`|`object` | The [user](/v3/users/) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. +`member`|`object` | The [user](/rest/reference/users) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. diff --git a/translations/ja-JP/data/reusables/webhooks/member_short_desc.md b/translations/ja-JP/data/reusables/webhooks/member_short_desc.md index 2e82896773..b664392fdf 100644 --- a/translations/ja-JP/data/reusables/webhooks/member_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/member_short_desc.md @@ -1 +1 @@ -Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/v3/repos/collaborators/)" REST API. +Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/rest/reference/repos#collaborators)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/membership_properties.md b/translations/ja-JP/data/reusables/webhooks/membership_properties.md index 770442be84..28a16d9b2a 100644 --- a/translations/ja-JP/data/reusables/webhooks/membership_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/membership_properties.md @@ -1,6 +1,6 @@ -| キー | 種類 | 説明 | -| -------- | -------- | ----------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be `added` or `removed`. | -| `スコープ` | `string` | The scope of the membership. Currently, can only be `team`. | -| `member` | `オブジェクト` | The [user](/v3/users/) that was added or removed. | -| `Team` | `オブジェクト` | The [team](/v3/teams/) for the membership. | +| キー | 種類 | 説明 | +| -------- | -------- | ------------------------------------------------------------ | +| `action` | `string` | 実行されたアクション. Can be `added` or `removed`. | +| `スコープ` | `string` | The scope of the membership. Currently, can only be `team`. | +| `member` | `オブジェクト` | The [user](/rest/reference/users) that was added or removed. | +| `Team` | `オブジェクト` | The [team](/rest/reference/teams) for the membership. | diff --git a/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md b/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md index e557eea902..f7867d25a9 100644 --- a/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md @@ -1 +1 @@ -Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/v3/teams/members/)" REST API. +Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/rest/reference/teams#members)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md b/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md index 6b6bd073ce..c9edf73236 100644 --- a/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md @@ -1 +1 @@ -Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/v3/issues/milestones/)" REST API. +Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/rest/reference/issues#milestones)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md b/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md index 7c3896f63c..f75660fcdb 100644 --- a/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. +Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/org_desc.md b/translations/ja-JP/data/reusables/webhooks/org_desc.md index 8b344e764c..90d218b876 100644 --- a/translations/ja-JP/data/reusables/webhooks/org_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/org_desc.md @@ -1 +1 @@ -`organization` | `object` | Webhook payloads contain the [`organization`](/v3/orgs/#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. +`organization` | `object` | Webhook payloads contain the [`organization`](/rest/reference/orgs#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. diff --git a/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md b/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md index 895b584aaf..0b539ee364 100644 --- a/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md @@ -1 +1 @@ -Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/v3/orgs/)" REST API. +Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/rest/reference/orgs)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/project_card_properties.md b/translations/ja-JP/data/reusables/webhooks/project_card_properties.md index acd386a739..0e2304eb52 100644 --- a/translations/ja-JP/data/reusables/webhooks/project_card_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/project_card_properties.md @@ -4,4 +4,4 @@ | `変更` | `オブジェクト` | The changes to the project card if the action was `edited` or `converted`. | | `changes[note][from]` | `string` | The previous version of the note if the action was `edited` or `converted`. | | `after_id` | `integer` | The id of the card that this card now follows if the action was "moved". Will be `null` if it is the first card in a column. | -| `project_card` | `オブジェクト` | The [project card](/v3/projects/cards) itself. | +| `project_card` | `オブジェクト` | The [project card](/rest/reference/projects#cards) itself. | diff --git a/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md b/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md index bbea9ea6c4..6fe2904d9e 100644 --- a/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md @@ -1 +1 @@ -Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/v3/projects/cards)" REST API. +Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/project_column_properties.md b/translations/ja-JP/data/reusables/webhooks/project_column_properties.md index 87f5eed710..fc42b2e783 100644 --- a/translations/ja-JP/data/reusables/webhooks/project_column_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/project_column_properties.md @@ -4,4 +4,4 @@ | `変更` | `オブジェクト` | The changes to the project column if the action was `edited`. | | `changes[name][from]` | `string` | The previous version of the name if the action was `edited`. | | `after_id` | `integer` | The id of the column that this column now follows if the action was "moved". Will be `null` if it is the first column in a project. | -| `project_column` | `オブジェクト` | The [project column](/v3/projects/columns) itself. | +| `project_column` | `オブジェクト` | The [project column](/rest/reference/projects#columns) itself. | diff --git a/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md b/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md index 19ac3f6412..35d38e4101 100644 --- a/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md @@ -1 +1 @@ -Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/v3/projects/columns)" REST API. +Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/project_properties.md b/translations/ja-JP/data/reusables/webhooks/project_properties.md index acd6b65d3d..af4aabb07b 100644 --- a/translations/ja-JP/data/reusables/webhooks/project_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/project_properties.md @@ -4,4 +4,4 @@ | `変更` | `オブジェクト` | The changes to the project if the action was `edited`. | | `changes[name][from]` | `string` | The previous version of the name if the action was `edited`. | | `changes[body][from]` | `string` | The previous version of the body if the action was `edited`. | -| `project` | `オブジェクト` | The [project](/v3/projects/) itself. | +| `project` | `オブジェクト` | The [project](/rest/reference/projects) itself. | diff --git a/translations/ja-JP/data/reusables/webhooks/project_short_desc.md b/translations/ja-JP/data/reusables/webhooks/project_short_desc.md index 6f18da5d69..2ae5d8be21 100644 --- a/translations/ja-JP/data/reusables/webhooks/project_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/project_short_desc.md @@ -1 +1 @@ -Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/v3/projects)" REST API. +Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md index 21544ccd9e..948f78e0b0 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md @@ -1 +1 @@ -`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls) itself. +`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) itself. diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md index a38df37d8c..1b854809c7 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md @@ -1 +1 @@ -`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls/) the comment belongs to. `comment`|`object` | The [comment](/v3/pulls/comments) itself. +`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/pulls#comments) itself. diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md index 7b05ee9a9a..e002a3be49 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md @@ -1 +1 @@ -Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/v3/pulls/comments/)" REST API. +Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/rest/reference/pulls#comments)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md index df38b34ad7..a056cfc763 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ -| キー | 種類 | 説明 | -| --------------------- | -------- | ------------------------------------------------------------ | -| `action` | `string` | 実行されたアクション. Can be one of:
  • `submitted` - A pull request review is submitted into a non-pending state.
  • `edited` - The body of a review has been edited.
  • `dismissed` - A review has been dismissed.
| -| `pull_request` | `オブジェクト` | The [pull request](/v3/pulls/) the review pertains to. | -| `レビュー` | `オブジェクト` | The review that was affected. | -| `changes[body][from]` | `string` | The previous version of the body if the action was `edited`. | +| キー | 種類 | 説明 | +| --------------------- | -------- | ----------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. Can be one of:
  • `submitted` - A pull request review is submitted into a non-pending state.
  • `edited` - The body of a review has been edited.
  • `dismissed` - A review has been dismissed.
| +| `pull_request` | `オブジェクト` | The [pull request](/rest/reference/pulls) the review pertains to. | +| `レビュー` | `オブジェクト` | The review that was affected. | +| `changes[body][from]` | `string` | The previous version of the body if the action was `edited`. | diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md index 07b263364d..3329d4b62e 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md @@ -1 +1 @@ -Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/v3/pulls/reviews/)" REST API. +Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/rest/reference/pulls#reviews)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md b/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md index ea9e435d03..45bc1b5789 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md @@ -1 +1 @@ -Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/v3/pulls/)" REST API. +Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/rest/reference/pulls)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/release_short_desc.md b/translations/ja-JP/data/reusables/webhooks/release_short_desc.md index e3a9a3bb3a..a8d506f409 100644 --- a/translations/ja-JP/data/reusables/webhooks/release_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/release_short_desc.md @@ -1 +1 @@ -Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/v3/repos/releases/)" REST API. +Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/rest/reference/repos#releases)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/repo_desc.md b/translations/ja-JP/data/reusables/webhooks/repo_desc.md index df26fb3e7a..e0eca4218d 100644 --- a/translations/ja-JP/data/reusables/webhooks/repo_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/repo_desc.md @@ -1 +1 @@ -`repository` | `object` | The [`repository`](/v3/repos/#get-a-repository) where the event occurred. +`repository` | `object` | The [`repository`](/rest/reference/repos#get-a-repository) where the event occurred. diff --git a/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md b/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md index 056531b019..d4b6cf9aa0 100644 --- a/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md @@ -1 +1 @@ -Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/v3/migrations/source_imports/)" REST API. +Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/rest/reference/migrations#source-imports)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md b/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md index df290ac0ea..b3e90e8d64 100644 --- a/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md @@ -1 +1 @@ -Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/v3/repos/)" REST API. +Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/rest/reference/repos)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/star_short_desc.md b/translations/ja-JP/data/reusables/webhooks/star_short_desc.md index f4fb663419..9569c6958e 100644 --- a/translations/ja-JP/data/reusables/webhooks/star_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/star_short_desc.md @@ -1 +1 @@ -Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/status_short_desc.md b/translations/ja-JP/data/reusables/webhooks/status_short_desc.md index 754f871add..6d835788c9 100644 --- a/translations/ja-JP/data/reusables/webhooks/status_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/status_short_desc.md @@ -1 +1 @@ -When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/v3/repos/statuses/)" REST API. +When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/rest/reference/repos#statuses)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/team_add_short_desc.md b/translations/ja-JP/data/reusables/webhooks/team_add_short_desc.md index bf33defeed..d8590939da 100644 --- a/translations/ja-JP/data/reusables/webhooks/team_add_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/team_add_short_desc.md @@ -1 +1 @@ -[リポジトリがTeamに追加された](/v3/teams/#add-or-update-team-repository-permissions)。 +[リポジトリがTeamに追加された](/rest/reference/teams#add-or-update-team-repository-permissions)。 diff --git a/translations/ja-JP/data/reusables/webhooks/team_short_desc.md b/translations/ja-JP/data/reusables/webhooks/team_short_desc.md index fdcf742789..ff27913e21 100644 --- a/translations/ja-JP/data/reusables/webhooks/team_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/team_short_desc.md @@ -1 +1 @@ -Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/v3/teams/)" REST API. +Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/rest/reference/teams)" REST API. diff --git a/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md b/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md index a853027b12..1b250fb019 100644 --- a/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md @@ -1 +1 @@ -When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md index f124e1d3dc..00a4c6143f 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md @@ -91,7 +91,7 @@ steps: ### Caching dependencies -You can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" and the [`cache` action](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} ```yaml diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md index 8bda99df17..81e5ae5945 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md @@ -91,7 +91,7 @@ steps: ### Caching dependencies -You can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" and the [`cache` action](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} ```yaml diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md index 69d1a978ad..54b5a8a71f 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md @@ -129,7 +129,7 @@ If you don't specify a Node.js version, {% data variables.product.prodname_dotco {% data variables.product.prodname_dotcom %}-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux {% data variables.product.prodname_dotcom %}-hosted runners also have Grunt, Gulp, and Bower installed. -You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." #### Example using npm @@ -227,7 +227,7 @@ always-auth=true #### Example caching dependencies -You can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" and the [`cache` action](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} ```yaml @@ -241,7 +241,7 @@ steps: uses: actions/cache@v2 with: # npm cache files are stored in `~/.npm` on Linux/macOS - path: ~/.npm + path: ~/.npm key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }} restore-keys: | ${{ runner.OS }}-node- diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md b/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md index 13a946fb38..14717c687d 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md @@ -91,7 +91,7 @@ The table below describes the locations for various PowerShell modules in each { {% endnote %} -You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules: @@ -119,7 +119,7 @@ jobs: #### Caching dependencies -You can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "Caching dependencies to speed up workflows." PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system. diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-python.md b/translations/ko-KR/content/actions/guides/building-and-testing-python.md index 5024f4dac4..dcebfbbeb0 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-python.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-python.md @@ -141,9 +141,9 @@ jobs: uses: actions/setup-python@v2 with: # Semantic version range syntax or exact version of a Python version - python-version: '3.x' + python-version: '3.x' # Optional - x64 or x86 architecture, defaults to x64 - architecture: 'x64' + architecture: 'x64' # You can test your matrix by printing the current Python version - name: Display Python version run: python -c "import sys; print(sys.version)" @@ -192,7 +192,7 @@ We recommend using `setup-python` to configure the version of Python used in you {% data variables.product.prodname_dotcom %}-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. For example, the YAML below installs or upgrades the `pip` package installer and the `setuptools` and `wheel` packages. -You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." {% raw %} ```yaml @@ -228,7 +228,7 @@ steps: #### Caching Dependencies -You can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "Caching dependencies to speed up workflows." Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example below depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip). diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md index 44df05f98f..1a7698f789 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md @@ -148,7 +148,7 @@ steps: #### Caching dependencies -The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. To enable caching, set the following. @@ -165,7 +165,7 @@ This will configure bundler to install your gems to `vendor/cache`. For each suc **Caching without setup-ruby** -For greater control over caching, you can use the `actions/cache` Action directly. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. For more information, see "Caching dependencies to speed up workflows." {% raw %} ```yaml diff --git a/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md index aae79b58b2..633050ef6c 100644 --- a/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -131,7 +131,7 @@ The `retention-days` value cannot exceed the retention limit set by the reposito During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact)action to download artifacts that were previously uploaded in the same workflow run. -After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/v3/actions/artifacts/)." +After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." #### Downloading artifacts during a workflow run diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index b23291c04a..dc2b208d2a 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -48,7 +48,9 @@ When creating a group, you must choose a policy that defines which repositories {% warning %} **경고** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} @@ -78,7 +80,9 @@ When creating a group, you must choose a policy that defines which organizations {% warning %} **경고** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md index 4c4da16850..4a13f941e6 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -57,7 +57,7 @@ jobs: needs: build runs-on: ubuntu-latest steps: - - run: ./test_server.sh + - run: ./test_server.sh ``` For more information, see [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). @@ -106,7 +106,7 @@ jobs: ``` {% endraw %} -For more information, see "[Caching dependencies to speed up workflows](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)." +For more information, see "Caching dependencies to speed up workflows." ### Using databases and service containers diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 17d1431c82..497f6175fc 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions -For more information, see "[Caching dependencies to speed up workflows](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)." +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." {% data variables.product.prodname_actions %} does not have an equivalent of CircleCI’s Docker Layer Caching (or DLC). diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 618503642e..80d2f12511 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -262,7 +262,7 @@ jobs: runs-on: ubuntu-latest steps: - run: echo "This job will be run first, in parallel with build_a" - + test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] @@ -346,7 +346,7 @@ jobs: -For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." ### Artifacts @@ -367,7 +367,7 @@ GitLab CI/CD {% raw %} ```yaml -script: +script: artifacts: paths: - math-homework.txt @@ -414,7 +414,7 @@ GitLab CI/CD container-job: variables: POSTGRES_PASSWORD: postgres - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port @@ -423,10 +423,10 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - npm ci - # Runs a script that creates a PostgreSQL client, + # Runs a script that creates a PostgreSQL client, # populates the client with data, and retrieves data - node client.js tags: @@ -452,7 +452,7 @@ jobs: - name: Check out repository code uses: actions/checkout@v2 - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - name: Install dependencies run: npm ci @@ -462,7 +462,7 @@ jobs: # populates the client with data, and retrieves data run: node client.js env: - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index f2931cc45a..83f15f782d 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -163,6 +163,12 @@ git: +#### Using environment variables in a matrix + +Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. + +In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} + ### Key features in {% data variables.product.prodname_actions %} When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}: @@ -281,7 +287,7 @@ jobs: ### Caching dependencies -Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. +Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. @@ -316,7 +322,7 @@ cache: npm
-For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." ### Examples of common tasks diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 7ba456e003..a6150cf4bf 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -14,7 +14,7 @@ You can see whether a workflow run is in progress or complete from the workflow If the run is complete, you can see whether the result was a success, failure, canceled, or neutral. If the run failed, you can view and search the build logs to diagnose the failure and re-run the workflow. You can also view billable job execution minutes, or download logs and build artifacts. -{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/v3/checks/)." +{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/rest/reference/checks)." {% data reusables.github-actions.invalid-workflow-files %} diff --git a/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md b/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md index 73fd38f3be..04790351aa 100644 --- a/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md @@ -79,7 +79,7 @@ You can use the `GITHUB_TOKEN` to make authenticated API calls. This example wor ### Permissions for the `GITHUB_TOKEN` -For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/v3/apps/permissions/)." +For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)." | Permission | Access type | Access by forked repos | | ------------------- | ----------- | ---------------------- | diff --git a/translations/ko-KR/content/actions/reference/encrypted-secrets.md b/translations/ko-KR/content/actions/reference/encrypted-secrets.md index bd499e0b88..25d65026bf 100644 --- a/translations/ko-KR/content/actions/reference/encrypted-secrets.md +++ b/translations/ko-KR/content/actions/reference/encrypted-secrets.md @@ -43,11 +43,11 @@ You can use and read encrypted secrets in a workflow file if you have access to {% endwarning %} -You can also manage secrets using the REST API. For more information, see "[Secrets](/v3/actions/secrets/)." +You can also manage secrets using the REST API. For more information, see "[Secrets](/rest/reference/actions#secrets)." #### Limiting credential permissions -When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/v3/guides/managing-deploy-keys/#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary. +When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary. ### Creating encrypted secrets for a repository diff --git a/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md b/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md index 067053a5ee..353d02f366 100644 --- a/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md @@ -143,7 +143,7 @@ jobs: {% data reusables.github-actions.branch-requirement %} -You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event)." +You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)." To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% data variables.product.product_name %} API endpoint and provide an `event_type` name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the `repository_dispatch` event. @@ -163,7 +163,7 @@ You can configure your workflow to run when webhook events are created on {% dat #### `check_run` -Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/v3/checks/runs/)." +Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/rest/reference/checks#runs)." {% data reusables.github-actions.branch-requirement %} @@ -183,7 +183,7 @@ on: #### `check_suite` -Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/v3/checks/suites/)." +Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/rest/reference/checks#suites)." {% data reusables.github-actions.branch-requirement %} @@ -209,7 +209,7 @@ on: #### `create` -Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/v3/git/refs/#create-a-reference)." +Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/rest/reference/git#create-a-reference)." | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------- | -------------- | ---------------------------------------- | --------------------- | @@ -224,7 +224,7 @@ on: #### `delete` -Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/v3/git/refs/#delete-a-reference)." +Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/rest/reference/git#delete-a-reference)." {% data reusables.github-actions.branch-requirement %} @@ -271,7 +271,7 @@ on: #### `포크` -Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/v3/repos/forks/#create-a-fork)." +Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)." {% data reusables.github-actions.branch-requirement %} @@ -354,7 +354,7 @@ jobs: #### `issues` -Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/v3/issues)." +Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/rest/reference/issues)." {% data reusables.github-actions.branch-requirement %} @@ -374,7 +374,7 @@ on: #### `레이블` -Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Labels](/v3/issues/labels/)." +Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Labels](/rest/reference/issues#labels)." {% data reusables.github-actions.branch-requirement %} @@ -394,7 +394,7 @@ on: #### `마일스톤` -Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/v3/issues/milestones/)." +Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)." {% data reusables.github-actions.branch-requirement %} @@ -431,7 +431,7 @@ on: #### `프로젝트` -Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/v3/projects/)." +Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/rest/reference/projects)." {% data reusables.github-actions.branch-requirement %} @@ -451,7 +451,7 @@ on: #### `project_card` -Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/v3/projects/cards)." +Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)." {% data reusables.github-actions.branch-requirement %} @@ -471,7 +471,7 @@ on: #### `project_column` -Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/v3/projects/columns)." +Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)." {% data reusables.github-actions.branch-requirement %} @@ -491,7 +491,7 @@ on: #### `public` -Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/v3/repos/#edit)." +Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)." {% data reusables.github-actions.branch-requirement %} @@ -508,7 +508,7 @@ on: #### `pull_request` -Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/v3/pulls)." +Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)." {% note %} @@ -534,7 +534,7 @@ on: #### `pull_request_review` -Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/v3/pulls/reviews)." +Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)." | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------------------------------- | ---------------------------------------------------------- | -------------------------------------------- | ------------------------------------------- | @@ -554,7 +554,7 @@ on: #### `pull_request_review_comment` -Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/v3/pulls/comments). +Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/rest/reference/pulls#comments). | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------------------------------------------- | ------------------------------------------- | @@ -597,7 +597,7 @@ on: pull_request_target {% note %} -**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a single commit](/v3/repos/commits/#get-a-single-commit)"". +**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a single commit](/rest/reference/repos#get-a-single-commit)"". {% endnote %} @@ -640,7 +640,7 @@ on: {% endnote %} -Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/v3/repos/releases/)." +Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/rest/reference/repos#releases)." | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | -------------- | @@ -658,7 +658,7 @@ on: #### `상태` -Runs your workflow anytime the status of a Git commit changes, which triggers the `status` event. For information about the REST API, see [Statuses](/v3/repos/statuses/). +Runs your workflow anytime the status of a Git commit changes, which triggers the `status` event. For information about the REST API, see [Statuses](/rest/reference/repos#statuses). {% data reusables.github-actions.branch-requirement %} @@ -675,7 +675,7 @@ on: #### `보기` -Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/v3/activity/starring/)." +Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/rest/reference/activity#starring)." {% data reusables.github-actions.branch-requirement %} diff --git a/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md b/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md index 71508b0105..947977b041 100644 --- a/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md @@ -79,6 +79,7 @@ For more information, see: - "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" for {% data variables.product.prodname_ghe_cloud %}{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Disabling and enabling workflows You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}. @@ -86,3 +87,4 @@ You can enable and disable individual workflows in your repository on {% data va {% data reusables.actions.scheduled-workflows-disabled %} For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)." +{% endif %} diff --git a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md index 1a163d6569..4f7c77e3ed 100644 --- a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md @@ -227,7 +227,7 @@ Each job runs in an environment specified by `runs-on`. You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. -If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/v3/actions/workflow-jobs)." +If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." ### **`jobs.`** @@ -878,34 +878,9 @@ strategy: ##### Using environment variables in a matrix -You can add custom environment variables for each test combination by using `include` with `env`. You can then refer to the custom environment variables in a later step. +You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. -In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: - -{% raw %} -```yaml -name: Node.js CI -on: [push] -jobs: - build: - runs-on: ubuntu-latest - strategy: - matrix: - include: - - node-version: 10.x - site: "prod" - datacenter: "site-a" - - node-version: 12.x - site: "dev" - datacenter: "site-b" - steps: - - name: Echo site details - env: - SITE: ${{ matrix.site }} - DATACENTER: ${{ matrix.datacenter }} - run: echo $SITE $DATACENTER -``` -{% endraw %} +{% data reusables.github-actions.matrix-variable-example %} ### **`jobs..strategy.fail-fast`** diff --git a/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md b/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md index 25be0883c4..4afe0374d7 100644 --- a/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md +++ b/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: User accounts on {% data variables.product.product_location %} are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change. -If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user). +If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). Other issues you should take into consideration include: diff --git a/translations/ko-KR/content/admin/configuration/command-line-utilities.md b/translations/ko-KR/content/admin/configuration/command-line-utilities.md index c9e22e1bdb..45e8b6fcea 100644 --- a/translations/ko-KR/content/admin/configuration/command-line-utilities.md +++ b/translations/ko-KR/content/admin/configuration/command-line-utilities.md @@ -159,7 +159,7 @@ $ ghe-es-index-status -do | column -ts, #### ghe-legacy-github-services-report -This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/v3/guides/replacing-github-services/)." For more information about this command or for additional options, use the `-h` flag. +This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)." For more information about this command or for additional options, use the `-h` flag. ```shell ghe-legacy-github-services-report diff --git a/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md index 627c419bb1..9cf696baba 100644 --- a/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md +++ b/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md @@ -37,7 +37,7 @@ Enabling {% data variables.product.prodname_github_connect %} also creates a {% Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.prodname_ghe_server %}. -For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." ### Enabling {% data variables.product.prodname_github_connect %} 1. Sign in to diff --git a/translations/ko-KR/content/admin/overview/about-the-github-enterprise-api.md b/translations/ko-KR/content/admin/overview/about-the-github-enterprise-api.md index d2586b8381..8f75a39a07 100644 --- a/translations/ko-KR/content/admin/overview/about-the-github-enterprise-api.md +++ b/translations/ko-KR/content/admin/overview/about-the-github-enterprise-api.md @@ -19,6 +19,6 @@ With the APIs, you can automate many administrative tasks. Some examples include - Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)." - Configure LDAP sync. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %} - Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)." -- Manage your enterprise account. For more information, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +- Manage your enterprise account. For more information, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." -For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). \ No newline at end of file +For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). diff --git a/translations/ko-KR/content/admin/user-management/audited-actions.md b/translations/ko-KR/content/admin/user-management/audited-actions.md index 74a877f3b0..744a09907d 100644 --- a/translations/ko-KR/content/admin/user-management/audited-actions.md +++ b/translations/ko-KR/content/admin/user-management/audited-actions.md @@ -137,6 +137,6 @@ versions: [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [deploy key]: /guides/managing-deploy-keys/#deploy-keys [generate token]: /articles/creating-an-access-token-for-command-line-use - [OAuth access token]: /v3/oauth/ + [OAuth access token]: /developers/apps/authorizing-oauth-apps [OAuth application]: /guides/basics-of-authentication/#registering-your-app [2fa]: /articles/about-two-factor-authentication diff --git a/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md index 5b4046fe37..2b499848ef 100644 --- a/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md +++ b/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md @@ -27,7 +27,7 @@ versions: To export repository data from {% data variables.product.prodname_dotcom_the_website %}, use the Migrations API. -The Migrations API is currently in a preview period, which means that the endpoints and parameters may change in the future. To access the Migrations API, you must provide a custom [media type](/v3/media) in the `Accept` header: `application/vnd.github.wyandotte-preview+json`. The examples below include the custom media type. +The Migrations API is currently in a preview period, which means that the endpoints and parameters may change in the future. To access the Migrations API, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: `application/vnd.github.wyandotte-preview+json`. The examples below include the custom media type. ### Generating a migration archive @@ -37,7 +37,7 @@ The Migrations API is currently in a preview period, which means that the endpoi 2. Start a migration by `POST`ing to the migration endpoint. You'll need: * Your access token for authentication. - * A [list of the repositories](/v3/repos/#list-organization-repositories) you want to migrate: + * A [list of the repositories](/rest/reference/repos#list-organization-repositories) you want to migrate: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ diff --git a/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md index 43fb80aefd..84cd9a5261 100644 --- a/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %} -After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository). You'll need your access token for authentication: +After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). You'll need your access token for authentication: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md index 0c2ccc8150..0d80e0097f 100644 --- a/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ You can create a custom message that suspended users will see when attempting to ``` ### 더 읽을거리 -- "[Suspend a user](/enterprise/{{ currentVersion }}/v3/enterprise-admin/users/#suspend-a-user)" +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/ko-KR/content/developers/apps/about-apps.md b/translations/ko-KR/content/developers/apps/about-apps.md index 010cd5c2e6..fff85efbab 100644 --- a/translations/ko-KR/content/developers/apps/about-apps.md +++ b/translations/ko-KR/content/developers/apps/about-apps.md @@ -67,13 +67,13 @@ Keep these ideas in mind when creating {% data variables.product.prodname_oauth_ * Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_app %}s authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/v3/guides/basics-of-authentication/#registering-your-app)." +For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." ### Personal access tokens A [personal access token](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A personal access token is also similar to a password, but you can have many of them and you can revoke access to each one at any time. -As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/v3/issues/#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it. +As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it. Keep these ideas in mind when using personal access tokens: diff --git a/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md b/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md index 750e4ff36a..ec679b8d8c 100644 --- a/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md @@ -118,13 +118,13 @@ You'll need to create a new JWT after the time expires. ### Accessing API endpoints as a {% data variables.product.prodname_github_app %} -For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/v3/apps/)." +For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)." ### Authenticating as an installation Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. These installation access tokens are used by {% data variables.product.prodname_github_app %}s to authenticate. -By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour. +By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour. To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request: @@ -144,7 +144,7 @@ $ curl -i -X POST \ ``` {% endif %} -The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint. +The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint. To authenticate with an installation access token, include it in the Authorization header in the API request: @@ -168,9 +168,9 @@ $ curl -i \ ### Accessing API endpoints as an installation -For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_app %}s using an installation access token, see "[Available Endpoints](/v3/apps/available-endpoints/)." +For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_app %}s using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)." -For a list of endpoints related to installations, see "[Installations](/v3/apps/installations/)." +For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)." ### HTTP-based Git access by an installation diff --git a/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md b/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md index 04007cdc3e..fb00d5b28a 100644 --- a/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md @@ -235,12 +235,12 @@ For more information, see the "[OAuth 2.0 Device Authorization Grant](https://to ### Non-Web application flow -Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/v3/auth#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. +Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with two-factor authentication](/v3/auth/#working-with-two-factor-authentication) if you or your users have two-factor authentication enabled. +**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if you or your users have two-factor authentication enabled. {% endnote %} {% endif %} @@ -289,7 +289,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% tip %} -**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/v3/guides/discovering-resources-for-a-user/)." +**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." {% endtip %} diff --git a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md index ef9427e2d1..fa38169b67 100644 --- a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -52,16 +52,16 @@ The person creating the app will be redirected to a GitHub page with an input fi ##### GitHub App Manifest parameters - | 이름 | 유형 | 설명 | - | --------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `문자열` | The name of the GitHub App. | - | `url` | `문자열` | **Required.** The homepage of your GitHub App. | - | `hook_attributes` | `개체` | The configuration of the GitHub App's webhook. | - | `redirect_url` | `문자열` | The full URL to redirect to after the person installs the GitHub App. | - | `설명` | `문자열` | A description of the GitHub App. | - | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | - | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | - | `default_permissions` | `개체` | The set of [permissions](/v3/apps/permissions/) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | + | 이름 | 유형 | 설명 | + | --------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `문자열` | The name of the GitHub App. | + | `url` | `문자열` | **Required.** The homepage of your GitHub App. | + | `hook_attributes` | `개체` | The configuration of the GitHub App's webhook. | + | `redirect_url` | `문자열` | The full URL to redirect to after the person installs the GitHub App. | + | `설명` | `문자열` | A description of the GitHub App. | + | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | + | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | + | `default_permissions` | `개체` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | The `hook_attributes` object has the following key: @@ -153,13 +153,13 @@ If you provided a `state` parameter, you will also see that parameter in the `re #### 3. You exchange the temporary code to retrieve the app configuration -To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. +To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. You must complete this step of the GitHub App Manifest flow within one hour. {% note %} -**Note:** This endpoint is rate limited. See [Rate limits](/v3/rate_limit/) to learn how to get your current rate limit status. +**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status. {% endnote %} @@ -170,7 +170,7 @@ You must complete this step of the GitHub App Manifest flow within one hour. POST /app-manifests/:code/conversions -For more information about the endpoint's response, see [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest). +For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest). When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time. @@ -191,4 +191,4 @@ Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file #### Hosting your app with Glitch -You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/v3/checks/) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. +You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. diff --git a/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md index 30e1aec255..45ee46145e 100644 --- a/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -49,37 +49,37 @@ The complete list of available query parameters, permissions, and events is list You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission. -| Permission | 설명 | -| -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Permission | 설명 | +| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/v3/users/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/v3/checks/). Can be one of: `none`, `read`, or `write`. | -| `content_references` | Grants access to the "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. | -| [`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. | +| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`. | +| `content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. | +| [`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. | | [`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/v3/repos/deployments/). Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/v3/users/emails/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/v3/users/followers/). Can be one of: `none`, `read`, or `write`. | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/v3/users/gpg_keys/). Can be one of: `none`, `read`, or `write`. | -| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/v3/issues/). Can be one of: `none`, `read`, or `write`. | -| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/v3/users/keys/). Can be one of: `none`, `read`, or `write`. | +| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`. | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`. | +| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`. | +| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`. | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`메타데이터`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. | -| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/v3/orgs/#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/v3/orgs/hooks/). Can be one of: `none`, `read`, or `write`. | -| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/v3/orgs/#get-an-organization)" endpoint. Can be one of: `none` or `read`. | -| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} -| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/v3/orgs/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/v3/repos/pages/). Can be one of: `none`, `read`, or `write`. | -| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/v3/users/#get-a-user)" endpoint. Can be one of: `none` or `read`. | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/v3/repos/hooks/). Can be one of: `none`, `read`, or `write`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`. | -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/v3/repos/contents/). Can be one of: `none`, `read`, or `write`. | -| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/v3/activity/starring/). Can be one of: `none`, `read`, or `write`. | -| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/v3/repos/statuses/). Can be one of: `none`, `read`, or `write`. | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/v3/teams/discussions/) and the [Team Discussion Comments API](/v3/teams/discussion_comments/). Can be one of: `none`, `read`, or `write`. | -| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. | -| `시청` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. | +| [`메타데이터`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. | +| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/v3/orgs/hooks/). Can be one of: `none`, `read`, or `write`. | +| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`. | +| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} +| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/v3/repos/pages/). Can be one of: `none`, `read`, or `write`. | +| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`. | +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. | +| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. | +| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`. | +| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. | +| `시청` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. | ### {% data variables.product.prodname_github_app %} webhook events diff --git a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md index a74759ea0c..2331b96d76 100644 --- a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introduction -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/v3/checks/), which you'll use to build a continuous integration (CI) server that runs tests. +This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts. 🙌 @@ -22,15 +22,15 @@ A CI server hosts code that runs CI tests such as code linters (which check styl #### Checks API overview -The [Checks API](/v3/checks/) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. +The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. -A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/v3/repos/branches/) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. +A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. -The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: +The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: 1. Whenever someone pushes code to the repository, GitHub sends the `check_suite` event with an action of `requested` to all GitHub Apps installed on the repository that have the `checks:write` permission. This event lets the apps know that code was pushed and that GitHub has automatically created a new check suite. -1. When your app receives this event, it can [add check runs](/v3/checks/runs/#create-a-check-run) to that suite. -1. Your check runs can include [annotations](/v3/checks/runs/#annotations-object) that are displayed on specific lines of code. +1. When your app receives this event, it can [add check runs](/rest/reference/checks#create-a-check-run) to that suite. +1. Your check runs can include [annotations](/rest/reference/checks#annotations-object) that are displayed on specific lines of code. **In this guide, you’ll learn how to:** @@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t ### 빌드전 요구 사양 -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/v3/checks/), if you're not already. You'll find more APIs in the [REST API docs](/v3/). The Checks API is also available to use in [GraphQL](/v4/), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/v4/object/checksuite/) and [Check Run](/v4/object/checkrun/) objects for more details. +Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app. @@ -140,7 +140,7 @@ You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sina def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -159,7 +159,7 @@ end def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -175,7 +175,7 @@ end ``` {% endif %} -This code calls the "[Create a check run](/v3/checks/runs/#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method. +This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method. To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [Rubocop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo Rubocop" is used here, but you can choose any name you'd like for the check run. @@ -240,7 +240,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -276,7 +276,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -305,11 +305,11 @@ end ``` {% endif %} -The code above calls the "[Update a check run](/v3/checks/runs/#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. +The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. Here's what this code is doing. First, it updates the check run's status to `in_progress` and sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`. -You'll notice in the "[Update a check run](/v3/checks/runs/#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`. +You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`. You could also provide more details about what your check is doing, but you'll get to that in the next section. Let's test this code again by re-running `template_server.rb`: @@ -435,7 +435,7 @@ The code above gets the full repository name and the head SHA of the commit from ### Step 2.3. Running RuboCop -Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/v3/checks/runs/#create-a-check-run). +Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. @@ -523,11 +523,11 @@ You should see the linting errors in the debug output, although they aren't prin The `@output` variable contains the parsed JSON results of the RuboCop report. As shown above, the results contain a `summary` section that your code can use to quickly determine if there are any errors. The following code will set the check run conclusion to `success` when there are no reported errors. RuboCop reports errors for each file in the `files` array, so if there are errors, you'll need to extract some data from the file object. -The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/v3/checks/runs/#update-a-check-run) with annotations. +The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/rest/reference/checks#update-a-check-run) with annotations. -The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. +The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. -A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/v3/checks/runs/#annotations-object-1) reference documentation for details. +A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/rest/reference/checks#annotations-object-1) reference documentation for details. You'll extract the required information from RuboCop needed to create each annotation. Append the following code to the code you added in the [previous section](#step-23-running-rubocop): @@ -536,7 +536,7 @@ annotations = [] # You can create a maximum of 50 annotations per request to the Checks # API. To add more than 50 annotations, use the "Update a check run" API # endpoint. This example code limits the number of annotations to 50. -# See /v3/checks/runs/#update-a-check-run +# See /rest/reference/checks#update-a-check-run # for details. max_annotations = 50 @@ -869,4 +869,4 @@ After walking through this guide, you've learned the basics of using the Checks Here are some ideas for what you can do next: * Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors. -* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/v3/pulls/#create-a-pull-request) with a new branch based on the head branch. +* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch. diff --git a/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 1bed7a0807..c16a98f38e 100644 --- a/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -90,10 +90,10 @@ Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to requ ### Git access -| GitHub Apps | OAuth Apps | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | -| The token is used as the HTTP password. | The token is used as the HTTP username. | +| GitHub Apps | OAuth Apps | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/repos#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | +| The token is used as the HTTP password. | The token is used as the HTTP username. | ### Machine vs. bot accounts diff --git a/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 2ca154a001..eac9f713c3 100644 --- a/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -67,7 +67,7 @@ If the user accepts your request, GitHub redirects back to your site with a temp {% endnote %} -Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." +Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)." Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} @@ -154,7 +154,7 @@ You can also check which repositories are accessible to a user for an installati Authorization: token OAUTH-TOKEN GET /user/installations/:installation_id/repositories -More details can be found in: [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token). +More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). ### Handling a revoked GitHub App authorization @@ -162,7 +162,7 @@ If a user revokes their authorization of a GitHub App, the app will receive the ### User-level permissions -You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/v3/apps/permissions/), which are granted at the time of installation on an organization or user account. +You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account. You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." @@ -172,75 +172,75 @@ Because user-level permissions are granted on an individual user basis, you can ### User-to-server requests -While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/v4/) or [REST v3](/v3/) endpoints. +While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/graphql) or [REST v3](/rest) endpoints. #### Supported endpoints {% if currentVersion == "free-pro-team@latest" %} ##### Actions Runners -* [List runner applications for a repository](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) -* [List self-hosted runners for a repository](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) -* [Get a self-hosted runner for a repository](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) -* [Delete a self-hosted runner from a repository](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) -* [Create a registration token for a repository](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) -* [Create a remove token for a repository](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) -* [List runner applications for an organization](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) -* [List self-hosted runners for an organization](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) -* [Get a self-hosted runner for an organization](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) -* [Delete a self-hosted runner from an organization](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) -* [Create a registration token for an organization](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) -* [Create a remove token for an organization](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) +* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository) +* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization) +* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization) ##### Actions Secrets -* [Get a repository public key](/v3/actions/secrets/#get-a-repository-public-key) -* [List repository secrets](/v3/actions/secrets/#list-repository-secrets) -* [Get a repository secret](/v3/actions/secrets/#get-a-repository-secret) -* [Create or update a repository secret](/v3/actions/secrets/#create-or-update-a-repository-secret) -* [Delete a repository secret](/v3/actions/secrets/#delete-a-repository-secret) -* [Get an organization public key](/v3/actions/secrets/#get-an-organization-public-key) -* [List organization secrets](/v3/actions/secrets/#list-organization-secrets) -* [Get an organization secret](/v3/actions/secrets/#get-an-organization-secret) -* [Create or update an organization secret](/v3/actions/secrets/#create-or-update-an-organization-secret) -* [List selected repositories for an organization secret](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) -* [Set selected repositories for an organization secret](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) -* [Add selected repository to an organization secret](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) -* [Remove selected repository from an organization secret](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) -* [Delete an organization secret](/v3/actions/secrets/#delete-an-organization-secret) +* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key) +* [List repository secrets](/rest/reference/actions#list-repository-secrets) +* [Get a repository secret](/rest/reference/actions#get-a-repository-secret) +* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret) +* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret) +* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key) +* [List organization secrets](/rest/reference/actions#list-organization-secrets) +* [Get an organization secret](/rest/reference/actions#get-an-organization-secret) +* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret) +* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Artifacts -* [List artifacts for a repository](/v3/actions/artifacts/#list-artifacts-for-a-repository) -* [List workflow run artifacts](/v3/actions/artifacts/#list-workflow-run-artifacts) -* [Get an artifact](/v3/actions/artifacts/#get-an-artifact) -* [Delete an artifact](/v3/actions/artifacts/#delete-an-artifact) -* [Download an artifact](/v3/actions/artifacts/#download-an-artifact) +* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository) +* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts) +* [Get an artifact](/rest/reference/actions#get-an-artifact) +* [Delete an artifact](/rest/reference/actions#delete-an-artifact) +* [Download an artifact](/rest/reference/actions#download-an-artifact) {% endif %} ##### Check Runs -* [Create a check run](/v3/checks/runs/#create-a-check-run) -* [Get a check run](/v3/checks/runs/#get-a-check-run) -* [Update a check run](/v3/checks/runs/#update-a-check-run) -* [List check run annotations](/v3/checks/runs/#list-check-run-annotations) -* [List check runs in a check suite](/v3/checks/runs/#list-check-runs-in-a-check-suite) -* [List check runs for a Git reference](/v3/checks/runs/#list-check-runs-for-a-git-reference) +* [Create a check run](/rest/reference/checks#create-a-check-run) +* [Get a check run](/rest/reference/checks#get-a-check-run) +* [Update a check run](/rest/reference/checks#update-a-check-run) +* [List check run annotations](/rest/reference/checks#list-check-run-annotations) +* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference) ##### 체크 스위트 -* [Create a check suite](/v3/checks/suites/#create-a-check-suite) -* [Get a check suite](/v3/checks/suites/#get-a-check-suite) -* [Rerequest a check suite](/v3/checks/suites/#rerequest-a-check-suite) -* [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) -* [List check suites for a Git reference](/v3/checks/suites/#list-check-suites-for-a-git-reference) +* [Create a check suite](/rest/reference/checks#create-a-check-suite) +* [Get a check suite](/rest/reference/checks#get-a-check-suite) +* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite) +* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference) ##### Codes Of Conduct -* [Get all codes of conduct](/v3/codes_of_conduct/#get-all-codes-of-conduct) -* [Get a code of conduct](/v3/codes_of_conduct/#get-a-code-of-conduct) +* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct) ##### Deployment Statuses @@ -266,128 +266,128 @@ While most of your API interaction should occur using your server-to-server inst ##### Git Blobs -* [Create a blob](/v3/git/blobs/#create-a-blob) -* [Get a blob](/v3/git/blobs/#get-a-blob) +* [Create a blob](/rest/reference/git#create-a-blob) +* [Get a blob](/rest/reference/git#get-a-blob) ##### Git Commits -* [Create a commit](/v3/git/commits/#create-a-commit) -* [Get a commit](/v3/git/commits/#get-a-commit) +* [Create a commit](/rest/reference/git#create-a-commit) +* [Get a commit](/rest/reference/git#get-a-commit) ##### Git Refs -* [Create a reference](/v3/git/refs/#create-a-reference)* [Get a reference](/v3/git/refs/#get-a-reference) -* [List matching references](/v3/git/refs/#list-matching-references) -* [Update a reference](/v3/git/refs/#update-a-reference) -* [Delete a reference](/v3/git/refs/#delete-a-reference) +* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference) +* [List matching references](/rest/reference/git#list-matching-references) +* [Update a reference](/rest/reference/git#update-a-reference) +* [Delete a reference](/rest/reference/git#delete-a-reference) ##### Git Tags -* [Create a tag object](/v3/git/tags/#create-a-tag-object) -* [Get a tag](/v3/git/tags/#get-a-tag) +* [Create a tag object](/rest/reference/git#create-a-tag-object) +* [Get a tag](/rest/reference/git#get-a-tag) ##### Git Trees -* [Create a tree](/v3/git/trees/#create-a-tree) -* [Get a tree](/v3/git/trees/#get-a-tree) +* [Create a tree](/rest/reference/git#create-a-tree) +* [Get a tree](/rest/reference/git#get-a-tree) ##### Gitignore Templates -* [Get all gitignore templates](/v3/gitignore/#get-all-gitignore-templates) -* [Get a gitignore template](/v3/gitignore/#get-a-gitignore-template) +* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates) +* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template) ##### Installations -* [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token) +* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} ##### Interaction Limits -* [Get interaction restrictions for an organization](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) -* [Set interaction restrictions for an organization](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) -* [Remove interaction restrictions for an organization](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) -* [Get interaction restrictions for a repository](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) -* [Set interaction restrictions for a repository](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) -* [Remove interaction restrictions for a repository](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) +* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) {% endif %} ##### Issue Assignees -* [Add assignees to an issue](/v3/issues/assignees/#add-assignees-to-an-issue) -* [Remove assignees from an issue](/v3/issues/assignees/#remove-assignees-from-an-issue) +* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue) +* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue) ##### Issue Comments -* [List issue comments](/v3/issues/comments/#list-issue-comments) -* [Create an issue comment](/v3/issues/comments/#create-an-issue-comment) -* [List issue comments for a repository](/v3/issues/comments/#list-issue-comments-for-a-repository) -* [Get an issue comment](/v3/issues/comments/#get-an-issue-comment) -* [Update an issue comment](/v3/issues/comments/#update-an-issue-comment) -* [Delete an issue comment](/v3/issues/comments/#delete-an-issue-comment) +* [List issue comments](/rest/reference/issues#list-issue-comments) +* [Create an issue comment](/rest/reference/issues#create-an-issue-comment) +* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository) +* [Get an issue comment](/rest/reference/issues#get-an-issue-comment) +* [Update an issue comment](/rest/reference/issues#update-an-issue-comment) +* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment) ##### Issue Events -* [List issue events](/v3/issues/events/#list-issue-events) +* [List issue events](/rest/reference/issues#list-issue-events) ##### Issue Timeline -* [List timeline events for an issue](/v3/issues/timeline/#list-timeline-events-for-an-issue) +* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue) ##### 문제 -* [List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user) -* [List assignees](/v3/issues/assignees/#list-assignees) -* [Check if a user can be assigned](/v3/issues/assignees/#check-if-a-user-can-be-assigned) -* [List repository issues](/v3/issues/#list-repository-issues) -* [Create an issue](/v3/issues/#create-an-issue) -* [Get an issue](/v3/issues/#get-an-issue) -* [Update an issue](/v3/issues/#update-an-issue) -* [Lock an issue](/v3/issues/#lock-an-issue) -* [Unlock an issue](/v3/issues/#unlock-an-issue) +* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [List assignees](/rest/reference/issues#list-assignees) +* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [List repository issues](/rest/reference/issues#list-repository-issues) +* [Create an issue](/rest/reference/issues#create-an-issue) +* [Get an issue](/rest/reference/issues#get-an-issue) +* [Update an issue](/rest/reference/issues#update-an-issue) +* [Lock an issue](/rest/reference/issues#lock-an-issue) +* [Unlock an issue](/rest/reference/issues#unlock-an-issue) {% if currentVersion == "free-pro-team@latest" %} ##### Jobs -* [Get a job for a workflow run](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) -* [Download job logs for a workflow run](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) -* [List jobs for a workflow run](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) +* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run) {% endif %} ##### Labels -* [List labels for an issue](/v3/issues/labels/#list-labels-for-an-issue) -* [Add labels to an issue](/v3/issues/labels/#add-labels-to-an-issue) -* [Set labels for an issue](/v3/issues/labels/#set-labels-for-an-issue) -* [Remove all labels from an issue](/v3/issues/labels/#remove-all-labels-from-an-issue) -* [Remove a label from an issue](/v3/issues/labels/#remove-a-label-from-an-issue) -* [List labels for a repository](/v3/issues/labels/#list-labels-for-a-repository) -* [Create a label](/v3/issues/labels/#create-a-label) -* [Get a label](/v3/issues/labels/#get-a-label) -* [Update a label](/v3/issues/labels/#update-a-label) -* [Delete a label](/v3/issues/labels/#delete-a-label) -* [Get labels for every issue in a milestone](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) +* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue) +* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue) +* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue) +* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue) +* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue) +* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository) +* [Create a label](/rest/reference/issues#create-a-label) +* [Get a label](/rest/reference/issues#get-a-label) +* [Update a label](/rest/reference/issues#update-a-label) +* [Delete a label](/rest/reference/issues#delete-a-label) +* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone) ##### Licenses -* [Get all commonly used licenses](/v3/licenses/#get-all-commonly-used-licenses) -* [Get a license](/v3/licenses/#get-a-license) +* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses) +* [Get a license](/rest/reference/licenses#get-a-license) ##### Markdown -* [Render a Markdown document](/v3/markdown/#render-a-markdown-document) -* [Render a markdown document in raw mode](/v3/markdown/#render-a-markdown-document-in-raw-mode) +* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document) +* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) ##### Meta -* [Meta](/v3/meta/#meta) +* [Meta](/rest/reference/meta#meta) ##### Milestones -* [List milestones](/v3/issues/milestones/#list-milestones) -* [Create a milestone](/v3/issues/milestones/#create-a-milestone) -* [Get a milestone](/v3/issues/milestones/#get-a-milestone) -* [Update a milestone](/v3/issues/milestones/#update-a-milestone) -* [Delete a milestone](/v3/issues/milestones/#delete-a-milestone) +* [List milestones](/rest/reference/issues#list-milestones) +* [Create a milestone](/rest/reference/issues#create-a-milestone) +* [Get a milestone](/rest/reference/issues#get-a-milestone) +* [Update a milestone](/rest/reference/issues#update-a-milestone) +* [Delete a milestone](/rest/reference/issues#delete-a-milestone) ##### Organization Hooks @@ -401,29 +401,29 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Organization Invitations -* [List pending organization invitations](/v3/orgs/members/#list-pending-organization-invitations) -* [Create an organization invitation](/v3/orgs/members/#create-an-organization-invitation) -* [List organization invitation teams](/v3/orgs/members/#list-organization-invitation-teams) +* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations) +* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation) +* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams) {% endif %} ##### Organization Members -* [List organization members](/v3/orgs/members/#list-organization-members) -* [Check organization membership for a user](/v3/orgs/members/#check-organization-membership-for-a-user) -* [Remove an organization member](/v3/orgs/members/#remove-an-organization-member) -* [Get organization membership for a user](/v3/orgs/members/#get-organization-membership-for-a-user) -* [Set organization membership for a user](/v3/orgs/members/#set-organization-membership-for-a-user) -* [Remove organization membership for a user](/v3/orgs/members/#remove-organization-membership-for-a-user) -* [List public organization members](/v3/orgs/members/#list-public-organization-members) -* [Check public organization membership for a user](/v3/orgs/members/#check-public-organization-membership-for-a-user) -* [Set public organization membership for the authenticated user](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) -* [Remove public organization membership for the authenticated user](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) +* [List organization members](/rest/reference/orgs#list-organization-members) +* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user) +* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member) +* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user) +* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user) +* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [List public organization members](/rest/reference/orgs#list-public-organization-members) +* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) ##### Organization Outside Collaborators -* [List outside collaborators for an organization](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) -* [Convert an organization member to outside collaborator](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) -* [Remove outside collaborator from an organization](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) +* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) {% if enterpriseServerVersions contains currentVersion %} ##### Organization Pre Receive Hooks @@ -437,198 +437,198 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Organization Team Projects -* [List team projects](/v3/teams/#list-team-projects) -* [Check team permissions for a project](/v3/teams/#check-team-permissions-for-a-project) -* [Add or update team project permissions](/v3/teams/#add-or-update-team-project-permissions) -* [Remove a project from a team](/v3/teams/#remove-a-project-from-a-team) +* [List team projects](/rest/reference/teams#list-team-projects) +* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project) +* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions) +* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team) {% endif %} ##### Organization Team Repositories -* [List team repositories](/v3/teams/#list-team-repositories) -* [Check team permissions for a repository](/v3/teams/#check-team-permissions-for-a-repository) -* [Add or update team repository permissions](/v3/teams/#add-or-update-team-repository-permissions) -* [Remove a repository from a team](/v3/teams/#remove-a-repository-from-a-team) +* [List team repositories](/rest/reference/teams#list-team-repositories) +* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository) +* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions) +* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team) {% if currentVersion == "free-pro-team@latest" %} ##### Organization Team Sync -* [List idp groups for a team](/v3/teams/team_sync/#list-idp-groups-for-a-team) -* [Create or update idp group connections](/v3/teams/team_sync/#create-or-update-idp-group-connections) -* [List IdP groups for an organization](/v3/teams/team_sync/#list-idp-groups-for-an-organization) +* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team) +* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections) +* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} ##### Organization Teams -* [List teams](/v3/teams/#list-teams) -* [Create a team](/v3/teams/#create-a-team) -* [Get a team by name](/v3/teams/#get-a-team-by-name) +* [List teams](/rest/reference/teams#list-teams) +* [Create a team](/rest/reference/teams#create-a-team) +* [Get a team by name](/rest/reference/teams#get-a-team-by-name) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -* [Get a team](/v3/teams/#get-a-team) +* [Get a team](/rest/reference/teams#get-a-team) {% endif %} -* [Update a team](/v3/teams/#update-a-team) -* [Delete a team](/v3/teams/#delete-a-team) +* [Update a team](/rest/reference/teams#update-a-team) +* [Delete a team](/rest/reference/teams#delete-a-team) {% if currentVersion == "free-pro-team@latest" %} -* [List pending team invitations](/v3/teams/members/#list-pending-team-invitations) +* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations) {% endif %} -* [List team members](/v3/teams/members/#list-team-members) -* [Get team membership for a user](/v3/teams/members/#get-team-membership-for-a-user) -* [Add or update team membership for a user](/v3/teams/members/#add-or-update-team-membership-for-a-user) -* [Remove team membership for a user](/v3/teams/members/#remove-team-membership-for-a-user) -* [List child teams](/v3/teams/#list-child-teams) -* [List teams for the authenticated user](/v3/teams/#list-teams-for-the-authenticated-user) +* [List team members](/rest/reference/teams#list-team-members) +* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user) +* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) +* [List child teams](/rest/reference/teams#list-child-teams) +* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user) ##### Organizations -* [List organizations](/v3/orgs/#list-organizations) -* [Get an organization](/v3/orgs/#get-an-organization) -* [Update an organization](/v3/orgs/#update-an-organization) -* [List organization memberships for the authenticated user](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) -* [Get an organization membership for the authenticated user](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) -* [Update an organization membership for the authenticated user](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) -* [List organizations for the authenticated user](/v3/orgs/#list-organizations-for-the-authenticated-user) -* [List organizations for a user](/v3/orgs/#list-organizations-for-a-user) +* [List organizations](/rest/reference/orgs#list-organizations) +* [Get an organization](/rest/reference/orgs#get-an-organization) +* [Update an organization](/rest/reference/orgs#update-an-organization) +* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Credential Authorizations -* [List SAML SSO authorizations for an organization](/v3/orgs/#list-saml-sso-authorizations-for-an-organization) -* [Remove a SAML SSO authorization for an organization](/v3/orgs/#remove-a-saml-sso-authorization-for-an-organization) +* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Scim -* [List SCIM provisioned identities](/v3/scim/#list-scim-provisioned-identities) -* [Provision and invite a SCIM user](/v3/scim/#provision-and-invite-a-scim-user) -* [Get SCIM provisioning information for a user](/v3/scim/#get-scim-provisioning-information-for-a-user) -* [Set SCIM information for a provisioned user](/v3/scim/#set-scim-information-for-a-provisioned-user) -* [Update an attribute for a SCIM user](/v3/scim/#update-an-attribute-for-a-scim-user) -* [Delete a SCIM user from an organization](/v3/scim/#delete-a-scim-user-from-an-organization) +* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities) +* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user) +* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Source Imports -* [Get an import status](/v3/migrations/source_imports/#get-an-import-status) -* [Start an import](/v3/migrations/source_imports/#start-an-import) -* [Update an import](/v3/migrations/source_imports/#update-an-import) -* [Cancel an import](/v3/migrations/source_imports/#cancel-an-import) -* [Get commit authors](/v3/migrations/source_imports/#get-commit-authors) -* [Map a commit author](/v3/migrations/source_imports/#map-a-commit-author) -* [Get large files](/v3/migrations/source_imports/#get-large-files) -* [Update Git LFS preference](/v3/migrations/source_imports/#update-git-lfs-preference) +* [Get an import status](/rest/reference/migrations#get-an-import-status) +* [Start an import](/rest/reference/migrations#start-an-import) +* [Update an import](/rest/reference/migrations#update-an-import) +* [Cancel an import](/rest/reference/migrations#cancel-an-import) +* [Get commit authors](/rest/reference/migrations#get-commit-authors) +* [Map a commit author](/rest/reference/migrations#map-a-commit-author) +* [Get large files](/rest/reference/migrations#get-large-files) +* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference) {% endif %} ##### Project Collaborators -* [List project collaborators](/v3/projects/collaborators/#list-project-collaborators) -* [Add project collaborator](/v3/projects/collaborators/#add-project-collaborator) -* [Remove project collaborator](/v3/projects/collaborators/#remove-project-collaborator) -* [Get project permission for a user](/v3/projects/collaborators/#get-project-permission-for-a-user) +* [List project collaborators](/rest/reference/projects#list-project-collaborators) +* [Add project collaborator](/rest/reference/projects#add-project-collaborator) +* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator) +* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user) ##### Projects -* [List organization projects](/v3/projects/#list-organization-projects) -* [Create an organization project](/v3/projects/#create-an-organization-project) -* [Get a project](/v3/projects/#get-a-project) -* [Update a project](/v3/projects/#update-a-project) -* [Delete a project](/v3/projects/#delete-a-project) -* [List project columns](/v3/projects/columns/#list-project-columns) -* [Create a project column](/v3/projects/columns/#create-a-project-column) -* [Get a project column](/v3/projects/columns/#get-a-project-column) -* [Update a project column](/v3/projects/columns/#update-a-project-column) -* [Delete a project column](/v3/projects/columns/#delete-a-project-column) -* [List project cards](/v3/projects/cards/#list-project-cards) -* [Create a project card](/v3/projects/cards/#create-a-project-card) -* [Move a project column](/v3/projects/columns/#move-a-project-column) -* [Get a project card](/v3/projects/cards/#get-a-project-card) -* [Update a project card](/v3/projects/cards/#update-a-project-card) -* [Delete a project card](/v3/projects/cards/#delete-a-project-card) -* [Move a project card](/v3/projects/cards/#move-a-project-card) -* [List repository projects](/v3/projects/#list-repository-projects) -* [Create a repository project](/v3/projects/#create-a-repository-project) +* [List organization projects](/rest/reference/projects#list-organization-projects) +* [Create an organization project](/rest/reference/projects#create-an-organization-project) +* [Get a project](/rest/reference/projects#get-a-project) +* [Update a project](/rest/reference/projects#update-a-project) +* [Delete a project](/rest/reference/projects#delete-a-project) +* [List project columns](/rest/reference/projects#list-project-columns) +* [Create a project column](/rest/reference/projects#create-a-project-column) +* [Get a project column](/rest/reference/projects#get-a-project-column) +* [Update a project column](/rest/reference/projects#update-a-project-column) +* [Delete a project column](/rest/reference/projects#delete-a-project-column) +* [List project cards](/rest/reference/projects#list-project-cards) +* [Create a project card](/rest/reference/projects#create-a-project-card) +* [Move a project column](/rest/reference/projects#move-a-project-column) +* [Get a project card](/rest/reference/projects#get-a-project-card) +* [Update a project card](/rest/reference/projects#update-a-project-card) +* [Delete a project card](/rest/reference/projects#delete-a-project-card) +* [Move a project card](/rest/reference/projects#move-a-project-card) +* [List repository projects](/rest/reference/projects#list-repository-projects) +* [Create a repository project](/rest/reference/projects#create-a-repository-project) ##### Pull Comments -* [List review comments on a pull request](/v3/pulls/comments/#list-review-comments-on-a-pull-request) -* [Create a review comment for a pull request](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) -* [List review comments in a repository](/v3/pulls/comments/#list-review-comments-in-a-repository) -* [Get a review comment for a pull request](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) -* [Update a review comment for a pull request](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) -* [Delete a review comment for a pull request](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) +* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository) +* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) ##### Pull Request Review Events -* [Dismiss a review for a pull request](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) -* [Submit a review for a pull request](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) +* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request) ##### Pull Request Review Requests -* [List requested reviewers for a pull request](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) -* [Request reviewers for a pull request](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) -* [Remove requested reviewers from a pull request](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) +* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) ##### Pull Request Reviews -* [List reviews for a pull request](/v3/pulls/reviews/#list-reviews-for-a-pull-request) -* [Create a review for a pull request](/v3/pulls/reviews/#create-a-review-for-a-pull-request) -* [Get a review for a pull request](/v3/pulls/reviews/#get-a-review-for-a-pull-request) -* [Update a review for a pull request](/v3/pulls/reviews/#update-a-review-for-a-pull-request) -* [List comments for a pull request review](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) +* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review) ##### Pulls -* [List pull requests](/v3/pulls/#list-pull-requests) -* [Create a pull request](/v3/pulls/#create-a-pull-request) -* [Get a pull request](/v3/pulls/#get-a-pull-request) -* [Update a pull request](/v3/pulls/#update-a-pull-request) -* [List commits on a pull request](/v3/pulls/#list-commits-on-a-pull-request) -* [List pull requests files](/v3/pulls/#list-pull-requests-files) -* [Check if a pull request has been merged](/v3/pulls/#check-if-a-pull-request-has-been-merged) -* [Merge a pull request (Merge Button)](/v3/pulls/#merge-a-pull-request) +* [List pull requests](/rest/reference/pulls#list-pull-requests) +* [Create a pull request](/rest/reference/pulls#create-a-pull-request) +* [Get a pull request](/rest/reference/pulls#get-a-pull-request) +* [Update a pull request](/rest/reference/pulls#update-a-pull-request) +* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request) +* [List pull requests files](/rest/reference/pulls#list-pull-requests-files) +* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request) ##### Reactions -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/v3/reactions/#delete-a-reaction-legacy){% else %}* [Delete a reaction](/v3/reactions/#delete-a-reaction){% endif %} -* [List reactions for a commit comment](/v3/reactions/#list-reactions-for-a-commit-comment) -* [Create reaction for a commit comment](/v3/reactions/#create-reaction-for-a-commit-comment) -* [List reactions for an issue](/v3/reactions/#list-reactions-for-an-issue) -* [Create reaction for an issue](/v3/reactions/#create-reaction-for-an-issue) -* [List reactions for an issue comment](/v3/reactions/#list-reactions-for-an-issue-comment) -* [Create reaction for an issue comment](/v3/reactions/#create-reaction-for-an-issue-comment) -* [List reactions for a pull request review comment](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) -* [Create reaction for a pull request review comment](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) -* [List reactions for a team discussion comment](/v3/reactions/#list-reactions-for-a-team-discussion-comment) -* [Create reaction for a team discussion comment](/v3/reactions/#create-reaction-for-a-team-discussion-comment) -* [List reactions for a team discussion](/v3/reactions/#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/v3/reactions/#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a commit comment reaction](/v3/reactions/#delete-a-commit-comment-reaction) -* [Delete an issue reaction](/v3/reactions/#delete-an-issue-reaction) -* [Delete a reaction to a commit comment](/v3/reactions/#delete-an-issue-comment-reaction) -* [Delete a pull request comment reaction](/v3/reactions/#delete-a-pull-request-comment-reaction) -* [Delete team discussion reaction](/v3/reactions/#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/v3/reactions/#delete-team-discussion-comment-reaction){% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %} +* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue) +* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue) +* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction) +* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction) +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} ##### Repositories -* [List organization repositories](/v3/repos/#list-organization-repositories) -* [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) -* [Get a repository](/v3/repos/#get-a-repository) -* [Update a repository](/v3/repos/#update-a-repository) -* [Delete a repository](/v3/repos/#delete-a-repository) -* [Compare two commits](/v3/repos/commits/#compare-two-commits) -* [List repository contributors](/v3/repos/#list-repository-contributors) +* [List organization repositories](/rest/reference/repos#list-organization-repositories) +* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [Get a repository](/rest/reference/repos#get-a-repository) +* [Update a repository](/rest/reference/repos#update-a-repository) +* [Delete a repository](/rest/reference/repos#delete-a-repository) +* [Compare two commits](/rest/reference/repos#compare-two-commits) +* [List repository contributors](/rest/reference/repos#list-repository-contributors) * [List forks](/rest/reference/repos#list-forks) -* [Create a fork](/v3/repos/forks/#create-a-fork) -* [List repository languages](/v3/repos/#list-repository-languages) -* [List repository tags](/v3/repos/#list-repository-tags) -* [List repository teams](/v3/repos/#list-repository-teams) -* [Transfer a repository](/v3/repos/#transfer-a-repository) -* [List public repositories](/v3/repos/#list-public-repositories) -* [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) -* [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -* [Create repository using a repository template](/v3/repos/#create-repository-using-a-repository-template) +* [Create a fork](/rest/reference/repos#create-a-fork) +* [List repository languages](/rest/reference/repos#list-repository-languages) +* [List repository tags](/rest/reference/repos#list-repository-tags) +* [List repository teams](/rest/reference/repos#list-repository-teams) +* [Transfer a repository](/rest/reference/repos#transfer-a-repository) +* [List public repositories](/rest/reference/repos#list-public-repositories) +* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user) +* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template) ##### Repository Activity @@ -643,116 +643,116 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Repository Automated Security Fixes -* [Enable automated security fixes](/v3/repos/#enable-automated-security-fixes) -* [Disable automated security fixes](/v3/repos/#disable-automated-security-fixes) +* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes) +* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes) {% endif %} ##### Repository Branches -* [List branches](/v3/repos/branches/#list-branches) -* [Get a branch](/v3/repos/branches/#get-a-branch) -* [Get branch protection](/v3/repos/branches/#get-branch-protection) -* [Update branch protection](/v3/repos/branches/#update-branch-protection) -* [Delete branch protection](/v3/repos/branches/#delete-branch-protection) -* [Get admin branch protection](/v3/repos/branches/#get-admin-branch-protection) -* [Set admin branch protection](/v3/repos/branches/#set-admin-branch-protection) -* [Delete admin branch protection](/v3/repos/branches/#delete-admin-branch-protection) -* [Get pull request review protection](/v3/repos/branches/#get-pull-request-review-protection) -* [Update pull request review protection](/v3/repos/branches/#update-pull-request-review-protection) -* [Delete pull request review protection](/v3/repos/branches/#delete-pull-request-review-protection) -* [Get commit signature protection](/v3/repos/branches/#get-commit-signature-protection) -* [Create commit signature protection](/v3/repos/branches/#create-commit-signature-protection) -* [Delete commit signature protection](/v3/repos/branches/#delete-commit-signature-protection) -* [Get status checks protection](/v3/repos/branches/#get-status-checks-protection) -* [Update status check protection](/v3/repos/branches/#update-status-check-protection) -* [Remove status check protection](/v3/repos/branches/#remove-status-check-protection) -* [Get all status check contexts](/v3/repos/branches/#get-all-status-check-contexts) -* [Add status check contexts](/v3/repos/branches/#add-status-check-contexts) -* [Set status check contexts](/v3/repos/branches/#set-status-check-contexts) -* [Remove status check contexts](/v3/repos/branches/#remove-status-check-contexts) -* [Get access restrictions](/v3/repos/branches/#get-access-restrictions) -* [Delete access restrictions](/v3/repos/branches/#delete-access-restrictions) -* [List teams with access to the protected branch](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) -* [Add team access restrictions](/v3/repos/branches/#add-team-access-restrictions) -* [Set team access restrictions](/v3/repos/branches/#set-team-access-restrictions) -* [Remove team access restriction](/v3/repos/branches/#remove-team-access-restrictions) -* [List user restrictions of protected branch](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) -* [Add user access restrictions](/v3/repos/branches/#add-user-access-restrictions) -* [Set user access restrictions](/v3/repos/branches/#set-user-access-restrictions) -* [Remove user access restrictions](/v3/repos/branches/#remove-user-access-restrictions) -* [Merge a branch](/v3/repos/merging/#merge-a-branch) +* [List branches](/rest/reference/repos#list-branches) +* [Get a branch](/rest/reference/repos#get-a-branch) +* [Get branch protection](/rest/reference/repos#get-branch-protection) +* [Update branch protection](/rest/reference/repos#update-branch-protection) +* [Delete branch protection](/rest/reference/repos#delete-branch-protection) +* [Get admin branch protection](/rest/reference/repos#get-admin-branch-protection) +* [Set admin branch protection](/rest/reference/repos#set-admin-branch-protection) +* [Delete admin branch protection](/rest/reference/repos#delete-admin-branch-protection) +* [Get pull request review protection](/rest/reference/repos#get-pull-request-review-protection) +* [Update pull request review protection](/rest/reference/repos#update-pull-request-review-protection) +* [Delete pull request review protection](/rest/reference/repos#delete-pull-request-review-protection) +* [Get commit signature protection](/rest/reference/repos#get-commit-signature-protection) +* [Create commit signature protection](/rest/reference/repos#create-commit-signature-protection) +* [Delete commit signature protection](/rest/reference/repos#delete-commit-signature-protection) +* [Get status checks protection](/rest/reference/repos#get-status-checks-protection) +* [Update status check protection](/rest/reference/repos#update-status-check-protection) +* [Remove status check protection](/rest/reference/repos#remove-status-check-protection) +* [Get all status check contexts](/rest/reference/repos#get-all-status-check-contexts) +* [Add status check contexts](/rest/reference/repos#add-status-check-contexts) +* [Set status check contexts](/rest/reference/repos#set-status-check-contexts) +* [Remove status check contexts](/rest/reference/repos#remove-status-check-contexts) +* [Get access restrictions](/rest/reference/repos#get-access-restrictions) +* [Delete access restrictions](/rest/reference/repos#delete-access-restrictions) +* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [Add team access restrictions](/rest/reference/repos#add-team-access-restrictions) +* [Set team access restrictions](/rest/reference/repos#set-team-access-restrictions) +* [Remove team access restriction](/rest/reference/repos#remove-team-access-restrictions) +* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [Add user access restrictions](/rest/reference/repos#add-user-access-restrictions) +* [Set user access restrictions](/rest/reference/repos#set-user-access-restrictions) +* [Remove user access restrictions](/rest/reference/repos#remove-user-access-restrictions) +* [Merge a branch](/rest/reference/repos#merge-a-branch) ##### Repository Collaborators -* [List repository collaborators](/v3/repos/collaborators/#list-repository-collaborators) -* [Check if a user is a repository collaborator](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) -* [Add a repository collaborator](/v3/repos/collaborators/#add-a-repository-collaborator) -* [Remove a repository collaborator](/v3/repos/collaborators/#remove-a-repository-collaborator) -* [Get repository permissions for a user](/v3/repos/collaborators/#get-repository-permissions-for-a-user) +* [List repository collaborators](/rest/reference/repos#list-repository-collaborators) +* [Check if a user is a repository collaborator](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator) +* [Remove a repository collaborator](/rest/reference/repos#remove-a-repository-collaborator) +* [Get repository permissions for a user](/rest/reference/repos#get-repository-permissions-for-a-user) ##### Repository Commit Comments -* [List commit comments for a repository](/v3/repos/comments/#list-commit-comments-for-a-repository) -* [Get a commit comment](/v3/repos/comments/#get-a-commit-comment) -* [Update a commit comment](/v3/repos/comments/#update-a-commit-comment) -* [Delete a commit comment](/v3/repos/comments/#delete-a-commit-comment) -* [List commit comments](/v3/repos/comments/#list-commit-comments) -* [Create a commit comment](/v3/repos/comments/#create-a-commit-comment) +* [List commit comments for a repository](/rest/reference/repos#list-commit-comments-for-a-repository) +* [Get a commit comment](/rest/reference/repos#get-a-commit-comment) +* [Update a commit comment](/rest/reference/repos#update-a-commit-comment) +* [Delete a commit comment](/rest/reference/repos#delete-a-commit-comment) +* [List commit comments](/rest/reference/repos#list-commit-comments) +* [Create a commit comment](/rest/reference/repos#create-a-commit-comment) ##### Repository Commits -* [List commits](/v3/repos/commits/#list-commits) -* [Get a commit](/v3/repos/commits/#get-a-commit) -* [List branches for head commit](/v3/repos/commits/#list-branches-for-head-commit) -* [List pull requests associated with commit](/v3/repos/commits/#list-pull-requests-associated-with-commit) +* [List commits](/rest/reference/repos#list-commits) +* [Get a commit](/rest/reference/repos#get-a-commit) +* [List branches for head commit](/rest/reference/repos#list-branches-for-head-commit) +* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit) ##### Repository Community -* [Get the code of conduct for a repository](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) +* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% if currentVersion == "free-pro-team@latest" %} -* [Get community profile metrics](/v3/repos/community/#get-community-profile-metrics) +* [Get community profile metrics](/rest/reference/repos#get-community-profile-metrics) {% endif %} ##### Repository Contents -* [Download a repository archive](/v3/repos/contents/#download-a-repository-archive) -* [Get repository content](/v3/repos/contents/#get-repository-content) -* [Create or update file contents](/v3/repos/contents/#create-or-update-file-contents) -* [Delete a file](/v3/repos/contents/#delete-a-file) -* [Get a repository README](/v3/repos/contents/#get-a-repository-readme) -* [Get the license for a repository](/v3/licenses/#get-the-license-for-a-repository) +* [Download a repository archive](/rest/reference/repos#download-a-repository-archive) +* [Get repository content](/rest/reference/repos#get-repository-content) +* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents) +* [Delete a file](/rest/reference/repos#delete-a-file) +* [Get a repository README](/rest/reference/repos#get-a-repository-readme) +* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Repository Event Dispatches -* [Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event) +* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event) {% endif %} ##### Repository Hooks -* [List repository webhooks](/v3/repos/hooks/#list-repository-webhooks) -* [Create a repository webhook](/v3/repos/hooks/#create-a-repository-webhook) -* [Get a repository webhook](/v3/repos/hooks/#get-a-repository-webhook) -* [Update a repository webhook](/v3/repos/hooks/#update-a-repository-webhook) -* [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) -* [Ping a repository webhook](/v3/repos/hooks/#ping-a-repository-webhook) -* [Test the push repository webhook](/v3/repos/hooks/#test-the-push-repository-webhook) +* [List repository webhooks](/rest/reference/repos#list-repository-webhooks) +* [Create a repository webhook](/rest/reference/repos#create-a-repository-webhook) +* [Get a repository webhook](/rest/reference/repos#get-a-repository-webhook) +* [Update a repository webhook](/rest/reference/repos#update-a-repository-webhook) +* [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) +* [Ping a repository webhook](/rest/reference/repos#ping-a-repository-webhook) +* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook) ##### Repository Invitations -* [List repository invitations](/v3/repos/invitations/#list-repository-invitations) -* [Update a repository invitation](/v3/repos/invitations/#update-a-repository-invitation) -* [Delete a repository invitation](/v3/repos/invitations/#delete-a-repository-invitation) -* [List repository invitations for the authenticated user](/v3/repos/invitations/#list-repository-invitations-for-the-authenticated-user) -* [Accept a repository invitation](/v3/repos/invitations/#accept-a-repository-invitation) -* [Decline a repository invitation](/v3/repos/invitations/#decline-a-repository-invitation) +* [List repository invitations](/rest/reference/repos#list-repository-invitations) +* [Update a repository invitation](/rest/reference/repos#update-a-repository-invitation) +* [Delete a repository invitation](/rest/reference/repos#delete-a-repository-invitation) +* [List repository invitations for the authenticated user](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [Accept a repository invitation](/rest/reference/repos#accept-a-repository-invitation) +* [Decline a repository invitation](/rest/reference/repos#decline-a-repository-invitation) ##### Repository Keys -* [List deploy keys](/v3/repos/keys/#list-deploy-keys) -* [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) -* [Get a deploy key](/v3/repos/keys/#get-a-deploy-key) -* [Delete a deploy key](/v3/repos/keys/#delete-a-deploy-key) +* [List deploy keys](/rest/reference/repos#list-deploy-keys) +* [Create a deploy key](/rest/reference/repos#create-a-deploy-key) +* [Get a deploy key](/rest/reference/repos#get-a-deploy-key) +* [Delete a deploy key](/rest/reference/repos#delete-a-deploy-key) ##### Repository Pages @@ -790,144 +790,144 @@ While most of your API interaction should occur using your server-to-server inst ##### Repository Stats -* [Get the weekly commit activity](/v3/repos/statistics/#get-the-weekly-commit-activity) -* [Get the last year of commit activity](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -* [Get all contributor commit activity](/v3/repos/statistics/#get-all-contributor-commit-activity) -* [Get the weekly commit count](/v3/repos/statistics/#get-the-weekly-commit-count) -* [Get the hourly commit count for each day](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +* [Get the weekly commit activity](/rest/reference/repos#get-the-weekly-commit-activity) +* [Get the last year of commit activity](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [Get all contributor commit activity](/rest/reference/repos#get-all-contributor-commit-activity) +* [Get the weekly commit count](/rest/reference/repos#get-the-weekly-commit-count) +* [Get the hourly commit count for each day](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) {% if currentVersion == "free-pro-team@latest" %} ##### Repository Vulnerability Alerts -* [Enable vulnerability alerts](/v3/repos/#enable-vulnerability-alerts) -* [Disable vulnerability alerts](/v3/repos/#disable-vulnerability-alerts) +* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts) +* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts) {% endif %} ##### Root -* [Root endpoint](/v3/#root-endpoint) -* [Emojis](/v3/emojis/#emojis) -* [Get rate limit status for the authenticated user](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) +* [Root endpoint](/rest#root-endpoint) +* [Emojis](/rest/reference/emojis#emojis) +* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) ##### 검색 -* [Search code](/v3/search/#search-code) -* [Search commits](/v3/search/#search-commits) -* [Search labels](/v3/search/#search-labels) -* [Search repositories](/v3/search/#search-repositories) -* [Search topics](/v3/search/#search-topics) -* [Search users](/v3/search/#search-users) +* [Search code](/rest/reference/search#search-code) +* [Search commits](/rest/reference/search#search-commits) +* [Search labels](/rest/reference/search#search-labels) +* [Search repositories](/rest/reference/search#search-repositories) +* [Search topics](/rest/reference/search#search-topics) +* [Search users](/rest/reference/search#search-users) ##### Statuses -* [Get the combined status for a specific reference](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) -* [List commit statuses for a reference](/v3/repos/statuses/#list-commit-statuses-for-a-reference) -* [Create a commit status](/v3/repos/statuses/#create-a-commit-status) +* [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [List commit statuses for a reference](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [Create a commit status](/rest/reference/repos#create-a-commit-status) ##### Team Discussions -* [List discussions](/v3/teams/discussions/#list-discussions) -* [Create a discussion](/v3/teams/discussions/#create-a-discussion) -* [Get a discussion](/v3/teams/discussions/#get-a-discussion) -* [Update a discussion](/v3/teams/discussions/#update-a-discussion) -* [Delete a discussion](/v3/teams/discussions/#delete-a-discussion) -* [List discussion comments](/v3/teams/discussion_comments/#list-discussion-comments) -* [Create a discussion comment](/v3/teams/discussion_comments/#create-a-discussion-comment) -* [Get a discussion comment](/v3/teams/discussion_comments/#get-a-discussion-comment) -* [Update a discussion comment](/v3/teams/discussion_comments/#update-a-discussion-comment) -* [Delete a discussion comment](/v3/teams/discussion_comments/#delete-a-discussion-comment) +* [List discussions](/rest/reference/teams#list-discussions) +* [Create a discussion](/rest/reference/teams#create-a-discussion) +* [Get a discussion](/rest/reference/teams#get-a-discussion) +* [Update a discussion](/rest/reference/teams#update-a-discussion) +* [Delete a discussion](/rest/reference/teams#delete-a-discussion) +* [List discussion comments](/rest/reference/teams#list-discussion-comments) +* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment) +* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment) +* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment) +* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment) ##### Topics -* [Get all repository topics](/v3/repos#get-all-repository-topics) -* [Replace all repository topics](/v3/repos/#replace-all-repository-topics) +* [Get all repository topics](/rest/reference/repos#get-all-repository-topics) +* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics) {% if currentVersion == "free-pro-team@latest" %} ##### Traffic -* [Get repository clones](/v3/repos/traffic/#get-repository-clones) -* [Get top referral paths](/v3/repos/traffic/#get-top-referral-paths) -* [Get top referral sources](/v3/repos/traffic/#get-top-referral-sources) -* [Get page views](/v3/repos/traffic/#get-page-views) +* [Get repository clones](/rest/reference/repos#get-repository-clones) +* [Get top referral paths](/rest/reference/repos#get-top-referral-paths) +* [Get top referral sources](/rest/reference/repos#get-top-referral-sources) +* [Get page views](/rest/reference/repos#get-page-views) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### User Blocking -* [List users blocked by the authenticated user](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) -* [Check if a user is blocked by the authenticated user](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) -* [List users blocked by an organization](/v3/orgs/blocking/#list-users-blocked-by-an-organization) -* [Check if a user is blocked by an organization](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) -* [Block a user from an organization](/v3/orgs/blocking/#block-a-user-from-an-organization) -* [Unblock a user from an organization](/v3/orgs/blocking/#unblock-a-user-from-an-organization) -* [Block a user](/v3/users/blocking/#block-a-user) -* [Unblock a user](/v3/users/blocking/#unblock-a-user) +* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization) +* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [Block a user](/rest/reference/users#block-a-user) +* [Unblock a user](/rest/reference/users#unblock-a-user) {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ##### User Emails {% if currentVersion == "free-pro-team@latest" %} -* [Set primary email visibility for the authenticated user](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) +* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %} -* [List email addresses for the authenticated user](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) -* [Add email address(es)](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) -* [Delete email address(es)](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) -* [List public email addresses for the authenticated user](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) +* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) {% endif %} ##### User Followers -* [List followers of a user](/v3/users/followers/#list-followers-of-a-user) -* [List the people a user follows](/v3/users/followers/#list-the-people-a-user-follows) -* [Check if a person is followed by the authenticated user](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) -* [Follow a user](/v3/users/followers/#follow-a-user) -* [Unfollow a user](/v3/users/followers/#unfollow-a-user) -* [Check if a user follows another user](/v3/users/followers/#check-if-a-user-follows-another-user) +* [List followers of a user](/rest/reference/users#list-followers-of-a-user) +* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows) +* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [Follow a user](/rest/reference/users#follow-a-user) +* [Unfollow a user](/rest/reference/users#unfollow-a-user) +* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user) ##### User Gpg Keys -* [List GPG keys for the authenticated user](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) -* [Create a GPG key for the authenticated user](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) -* [Get a GPG key for the authenticated user](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) -* [Delete a GPG key for the authenticated user](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) -* [List gpg keys for a user](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) +* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user) ##### User Public Keys -* [List public SSH keys for the authenticated user](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) -* [Create a public SSH key for the authenticated user](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) -* [Get a public SSH key for the authenticated user](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) -* [Delete a public SSH key for the authenticated user](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) -* [List public keys for a user](/v3/users/keys/#list-public-keys-for-a-user) +* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user) ##### Users -* [Get the authenticated user](/v3/users/#get-the-authenticated-user) -* [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) +* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) +* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% endif %} -* [List users](/v3/users/#list-users) -* [Get a user](/v3/users/#get-a-user) +* [List users](/rest/reference/users#list-users) +* [Get a user](/rest/reference/users#get-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Workflow Runs -* [List workflow runs for a repository](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) -* [Get a workflow run](/v3/actions/workflow-runs/#get-a-workflow-run) -* [Cancel a workflow run](/v3/actions/workflow-runs/#cancel-a-workflow-run) -* [Download workflow run logs](/v3/actions/workflow-runs/#download-workflow-run-logs) -* [Delete workflow run logs](/v3/actions/workflow-runs/#delete-workflow-run-logs) -* [Re run a workflow](/v3/actions/workflow-runs/#re-run-a-workflow) -* [List workflow runs](/v3/actions/workflow-runs/#list-workflow-runs) -* [Get workflow run usage](/v3/actions/workflow-runs/#get-workflow-run-usage) +* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [Get a workflow run](/rest/reference/actions#get-a-workflow-run) +* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run) +* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs) +* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs) +* [Re run a workflow](/rest/reference/actions#re-run-a-workflow) +* [List workflow runs](/rest/reference/actions#list-workflow-runs) +* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Workflows -* [List repository workflows](/v3/actions/workflows/#list-repository-workflows) -* [Get a workflow](/v3/actions/workflows/#get-a-workflow) -* [Get workflow usage](/v3/actions/workflows/#get-workflow-usage) +* [List repository workflows](/rest/reference/actions#list-repository-workflows) +* [Get a workflow](/rest/reference/actions#get-a-workflow) +* [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} diff --git a/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md index f0bcc953ea..b0b4f2866a 100644 --- a/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -23,7 +23,7 @@ This article provides guidelines for existing integrators who are considering mi - Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). - Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration. - Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation. -- Open Source community support is available through [Octokit libraries](/v3/libraries/) and other frameworks such as [Probot](https://probot.github.io/). +- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/). - Integrators building GitHub Apps have opportunities to adopt earlier access to APIs. ### Converting an OAuth App to a GitHub App @@ -42,13 +42,13 @@ These guidelines assume that you have a registered OAuth App{% if currentVersion #### Review the available API endpoints for GitHub Apps -While the majority of [REST API](/v3) endpoints and [GraphQL](/v4) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/v3/apps/available-endpoints/) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. +While the majority of [REST API](/rest) endpoints and [GraphQL](/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_app %}s. #### Design to stay within API rate limits -GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/v3/#conditional-requests) or consolidate requests by using the [GraphQL API V4](/v4/). +GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest#conditional-requests) or consolidate requests by using the [GraphQL API V4](/graphql). #### Register a new GitHub App @@ -56,7 +56,7 @@ Once you've decided to make the switch to Github Apps, you'll need to [create a #### Determine the permissions your app requires -When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/v3/apps/permissions/)" for a list of the permissions needed for each endpoint available to GitHub Apps. +When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps. In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality. @@ -90,11 +90,11 @@ Once you've made the transition from an OAuth App to a GitHub App, you will need https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) and [List organization repositories](/v3/repos/#list-organization-repositories) endpoints. +You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints. #### Remove any unnecessary repository hooks -Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) on those repositories that were created by your OAuth App. +Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) on those repositories that were created by your OAuth App. #### Encourage users to revoke access to your OAuth app diff --git a/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md index d9b78acf7a..3e3b63adf0 100644 --- a/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -25,7 +25,7 @@ To renew an expiring user-to-server access token, you can exchange the `refresh_ `POST https://github.com/login/oauth/access_token` -This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/v3/guides/basics-of-authentication/#providing-a-callback)." +This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." #### 매개변수 diff --git a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md index 26f6c12712..eea880cf33 100644 --- a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md @@ -41,13 +41,13 @@ X-Accepted-OAuth-Scopes: user | 이름 | 설명 | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/v3/enterprise-admin).{% endif %} +| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} | **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/v3/repos/deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/v3/code-scanning).{% endif %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | |  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | diff --git a/translations/ko-KR/content/developers/apps/setting-permissions-for-github-apps.md b/translations/ko-KR/content/developers/apps/setting-permissions-for-github-apps.md index f63d641cdb..c7b9470177 100644 --- a/translations/ko-KR/content/developers/apps/setting-permissions-for-github-apps.md +++ b/translations/ko-KR/content/developers/apps/setting-permissions-for-github-apps.md @@ -17,4 +17,4 @@ When you create a GitHub App, you can select the permissions it needs to access By default, GitHub Apps have `Read-only` access to metadata endpoints. Metadata is a collection of read-only endpoints that provide general information about resources that the authorized installation can access. -{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/v3/apps/permissions/#metadata-permissions)." +{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/rest/reference/permissions-required-for-github-apps#metadata-permissions)." diff --git a/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index 86058820ec..a83272428a 100644 --- a/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -37,7 +37,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [Webhooks](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -220,7 +220,7 @@ end #### Define a route handler -An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You'll won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. ``` ruby post '/event_handler' do diff --git a/translations/ko-KR/content/developers/apps/using-content-attachments.md b/translations/ko-KR/content/developers/apps/using-content-attachments.md index e093b1610c..bcd3a05720 100644 --- a/translations/ko-KR/content/developers/apps/using-content-attachments.md +++ b/translations/ko-KR/content/developers/apps/using-content-attachments.md @@ -55,7 +55,7 @@ The content attachment flow shows you the relationship between the URL in the is } ``` -**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/v3/apps/installations/#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -116,7 +116,7 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -For more information on `node_id`, see "[Using Global Node IDs](/v4/guides/using-global-node-ids/)." +For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ### Example using Probot and GitHub App Manifests diff --git a/translations/ko-KR/content/developers/apps/using-the-github-api-in-your-app.md b/translations/ko-KR/content/developers/apps/using-the-github-api-in-your-app.md index 1ac135eceb..bdccb99154 100644 --- a/translations/ko-KR/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/ko-KR/content/developers/apps/using-the-github-api-in-your-app.md @@ -31,7 +31,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [Webhooks](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -143,11 +143,11 @@ Before the label can be _added_ anywhere, you'll need to _create_ the custom lab {% tip %} -**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/v3/issues/labels/#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. +**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. {% endtip %} -Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/v3/issues/labels/#add-labels-to-an-issue). +Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue). ### Step 4. Add label handling diff --git a/translations/ko-KR/content/developers/github-marketplace/billing-customers.md b/translations/ko-KR/content/developers/github-marketplace/billing-customers.md index 43bb5ab916..ddc8e0716d 100644 --- a/translations/ko-KR/content/developers/github-marketplace/billing-customers.md +++ b/translations/ko-KR/content/developers/github-marketplace/billing-customers.md @@ -25,7 +25,7 @@ Customers must be able to perform the following actions from your app's website: Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." -You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). +You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). #### 업그레이드 diff --git a/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index b047103753..a30f26b72e 100644 --- a/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -68,7 +68,7 @@ After the customer completes the authorization, your app receives an OAuth acces ### Step 4. Provisioning customer accounts -Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. +Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. {% data reusables.marketplace.marketplace-double-purchases %} @@ -76,6 +76,6 @@ If the purchase is for an organization and per-user, you can prompt the customer You can customize the way that organization members receive access to your app. Here are a few suggestions: -**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/v3/orgs/members/#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. +**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/rest/reference/orgs#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. **Per-unit pricing:** One method of provisioning per-unit seats is to allow users to occupy a seat as they log in to the app. Once the customer hits the seat count threshold, your app can alert the user that they need to upgrade through {% data variables.product.prodname_marketplace %}. diff --git a/translations/ko-KR/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/ko-KR/content/developers/github-marketplace/handling-plan-cancellations.md index 17cd1d8b80..ed287efb5e 100644 --- a/translations/ko-KR/content/developers/github-marketplace/handling-plan-cancellations.md +++ b/translations/ko-KR/content/developers/github-marketplace/handling-plan-cancellations.md @@ -28,6 +28,6 @@ When a customer cancels a free or paid plan, your app must perform these steps t {% note %} -**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." {% endnote %} diff --git a/translations/ko-KR/content/developers/github-marketplace/handling-plan-changes.md b/translations/ko-KR/content/developers/github-marketplace/handling-plan-changes.md index 98758c327a..7fb64dd96c 100644 --- a/translations/ko-KR/content/developers/github-marketplace/handling-plan-changes.md +++ b/translations/ko-KR/content/developers/github-marketplace/handling-plan-changes.md @@ -54,7 +54,7 @@ https://www.github.com/marketplace//upgrade// For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page. -Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/v3/apps/marketplace/#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. +Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. {% note %} diff --git a/translations/ko-KR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md b/translations/ko-KR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md index 5ad1d2f177..db3482b992 100644 --- a/translations/ko-KR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md +++ b/translations/ko-KR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md @@ -13,10 +13,10 @@ versions: Here are some useful endpoints available for Marketplace listings: -* [List plans](/v3/apps/marketplace/#list-plans) -* [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan) -* [Get a subscription plan for an account](/v3/apps/marketplace/#get-a-subscription-plan-for-an-account) -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [List plans](/rest/reference/apps#list-plans) +* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan) +* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API: @@ -25,6 +25,6 @@ See these pages for details on how to authenticate when using the {% data variab {% note %} -**Note:** [Rate limits for the REST API](/v3/#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. +**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. {% endnote %} diff --git a/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md b/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md index 352aaf9c5e..09e79b1a7a 100644 --- a/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md +++ b/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md @@ -37,7 +37,7 @@ Your testing scenarios may require setting up listing plans that offer free tria ### Testing APIs -For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/v3/apps/marketplace/#github-marketplace). +For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace). ### Testing webhooks diff --git a/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index eae7e66c49..60d0556bb3 100644 --- a/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -31,15 +31,15 @@ Each `marketplace_purchase` webhook payload will have the following information: The `marketplace_purchase` object has the following keys: -| 키 | 유형 | 설명 | -| -------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `계정` | `개체` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/v3/users/#get-the-authenticated-user) endpoint. | -| `billing_cycle` | `문자열` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. | -| `unit_count` | `integer` | Number of units purchased. | -| `on_free_trial` | `boolean` | `true` when the `account` is on a free trial. | -| `free_trial_ends_on` | `문자열` | The date the free trial will expire. | -| `next_billing_date` | `문자열` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. | -| `plan` | `개체` | The plan purchased by the `user` or `organization`. | +| 키 | 유형 | 설명 | +| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `계정` | `개체` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint. | +| `billing_cycle` | `문자열` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. | +| `unit_count` | `integer` | Number of units purchased. | +| `on_free_trial` | `boolean` | `true` when the `account` is on a free trial. | +| `free_trial_ends_on` | `문자열` | The date the free trial will expire. | +| `next_billing_date` | `문자열` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. | +| `plan` | `개체` | The plan purchased by the `user` or `organization`. | The `plan` object has the following keys: diff --git a/translations/ko-KR/content/developers/overview/about-githubs-apis.md b/translations/ko-KR/content/developers/overview/about-githubs-apis.md index 39e74b19f1..0d647b78cb 100644 --- a/translations/ko-KR/content/developers/overview/about-githubs-apis.md +++ b/translations/ko-KR/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/v3/) and the [GraphQL API](/v4/). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). -When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). +When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). -For information on using the GraphQL API, see the [v4 docs](/v4/). +For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/ko-KR/content/developers/webhooks-and-events/about-webhooks.md b/translations/ko-KR/content/developers/webhooks-and-events/about-webhooks.md index 28831fe1a3..525d45c86c 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/about-webhooks.md @@ -31,4 +31,4 @@ See "[Webhook event payloads](/webhooks/event-payloads)" for the list of availab For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. [org-hooks]: /rest/reference/orgs#webhooks/ -[repo-hooks]: /v3/repos/hooks/ +[repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/ko-KR/content/developers/webhooks-and-events/creating-webhooks.md b/translations/ko-KR/content/developers/webhooks-and-events/creating-webhooks.md index 4146344b29..6543843f3f 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/creating-webhooks.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/creating-webhooks.md @@ -65,5 +65,5 @@ When you're finished, click **Add webhook**. Phew! Now that you created the webh To configure a webhook for all events, use the wildcard (`*`) character to specify the webhook events. When you add the wildcard event, we'll replace any existing events you have configured with the wildcard event and send you payloads for all supported events. You'll also automatically get any new events we might add in the future. [webhooks-overview]: /webhooks/ -[webhook-api]: /v3/repos/hooks/ +[webhook-api]: /rest/reference/repos#hooks [hooks-api]: /webhooks/#events diff --git a/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md b/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md index fa0881c8ba..306862266e 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md @@ -40,7 +40,7 @@ The event objects returned from the Events API endpoints have the same structure #### Example WatchEvent event object -This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/v3/activity/events). +This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events). ``` Status: 200 OK @@ -198,22 +198,22 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -| 키 | 유형 | 설명 | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `push_id` | `integer` | Unique identifier for the push. | -| `크기` | `integer` | The number of commits in the push. | -| `distinct_size` | `integer` | The number of distinct commits in the push. | -| `ref` | `문자열` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/main`. | -| `head` | `문자열` | The SHA of the most recent commit on `ref` after the push. | -| `before` | `문자열` | The SHA of the most recent commit on `ref` before the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][sha]` | `문자열` | The SHA of the commit. | -| `commits[][message]` | `문자열` | The commit message. | -| `commits[][author]` | `개체` | The git author of the commit. | -| `commits[][author][name]` | `문자열` | The git author's name. | -| `commits[][author][email]` | `문자열` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| 키 | 유형 | 설명 | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `push_id` | `integer` | Unique identifier for the push. | +| `크기` | `integer` | The number of commits in the push. | +| `distinct_size` | `integer` | The number of distinct commits in the push. | +| `ref` | `문자열` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `head` | `문자열` | The SHA of the most recent commit on `ref` after the push. | +| `before` | `문자열` | The SHA of the most recent commit on `ref` before the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][sha]` | `문자열` | The SHA of the commit. | +| `commits[][message]` | `문자열` | The commit message. | +| `commits[][author]` | `개체` | The git author of the commit. | +| `commits[][author][name]` | `문자열` | The git author's name. | +| `commits[][author][email]` | `문자열` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | ### ReleaseEvent diff --git a/translations/ko-KR/content/developers/webhooks-and-events/issue-event-types.md b/translations/ko-KR/content/developers/webhooks-and-events/issue-event-types.md index e10a98add6..f07e12d2d7 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/issue-event-types.md @@ -10,7 +10,7 @@ versions: --- -Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/v3/issues/events) and the [Timeline Events API](/v3/issues/timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. +Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. @@ -129,7 +129,7 @@ A comment was added to the issue or pull request. | `html_url` | `문자열` | The HTML URL of the issue comment. | | `issue_url` | `문자열` | The HTML URL of the issue. | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `문자열` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `문자열` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `사용자` | `개체` | The person who commented on the issue. | | `created_at` | `문자열` | The timestamp indicating when the comment was added. | | `updated_at` | `문자열` | The timestamp indicating when the comment was updated or created, if the comment is never updated. | @@ -152,19 +152,19 @@ A commit was added to the pull request's `HEAD` branch. {% data reusables.issue-events.timeline_events_object_properties %} -| 이름 | 유형 | 설명 | -| ------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `sha` | `문자열` | The SHA of the commit in the pull request. | -| `node_id` | `문자열` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `문자열` | The REST API URL to retrieve the commit. | -| `html_url` | `문자열` | The HTML URL of the commit. | -| `저자` | `개체` | The person who authored the commit. | -| `커밋한 사람` | `개체` | The person who committed the commit on behalf of the author. | -| `트리` | `개체` | The Git tree of the commit. | -| `message` | `문자열` | The commit message. | -| `parents` | `array of objects` | A list of parent commits. | -| `verfication` | `개체` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/v3/git/commits/#signature-verification-object)." | -| `event` | `문자열` | The event value is `"committed"`. | +| 이름 | 유형 | 설명 | +| ------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sha` | `문자열` | The SHA of the commit in the pull request. | +| `node_id` | `문자열` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `문자열` | The REST API URL to retrieve the commit. | +| `html_url` | `문자열` | The HTML URL of the commit. | +| `저자` | `개체` | The person who authored the commit. | +| `커밋한 사람` | `개체` | The person who committed the commit on behalf of the author. | +| `트리` | `개체` | The Git tree of the commit. | +| `message` | `문자열` | The commit message. | +| `parents` | `array of objects` | A list of parent commits. | +| `verfication` | `개체` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#signature-verification-object)." | +| `event` | `문자열` | The event value is `"committed"`. | ### connected @@ -583,7 +583,7 @@ The pull request was reviewed. | 이름 | 유형 | 설명 | | -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `문자열` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `문자열` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `사용자` | `개체` | The person who commented on the issue. | | `본문` | `문자열` | The review summary text. | | `commit_id` | `문자열` | The SHA of the latest commit in the pull request at the time of the review. | diff --git a/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md index 9606a2ea27..7c93e78582 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -33,7 +33,7 @@ Each webhook event payload also contains properties unique to the event. You can {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)." -The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/v3/activity/events/). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. +The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. {% tip %} @@ -45,14 +45,14 @@ The unique properties for a webhook event are the same properties you'll find in HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: -| Header | 설명 | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | Name of the event that triggered the delivery. | +| Header | 설명 | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-GitHub-Event` | Name of the event that triggered the delivery. | | `X-GitHub-Delivery` | A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | +| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | | `X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} -| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} +| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. @@ -195,7 +195,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.content_reference_short_desc %} -Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" to create a new content attachment. +Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event. @@ -715,7 +715,7 @@ The webhook this event is configured on was deleted. This event will only listen ### 패키지 -Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. +Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. #### Availability @@ -775,7 +775,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus | -------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `zen` | `문자열` | Random string of GitHub zen. | | `hook_id` | `integer` | The ID of the webhook that triggered the ping. | -| `후크` | `개체` | The [webhook configuration](/v3/repos/hooks/#get-a-repository-webhook). | +| `후크` | `개체` | The [webhook configuration](/rest/reference/repos#get-a-repository-webhook). | | `hook[app_id]` | `integer` | When you register a new {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} sends a ping event to the **webhook URL** you specified during registration. The event contains the `app_id`, which is required for [authenticating](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) an app. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} @@ -969,24 +969,24 @@ Deliveries for `review_requested` and `review_request_removed` events will have #### Webhook payload object -| 키 | 유형 | 설명 | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `문자열` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/main`. | -| `before` | `문자열` | The SHA of the most recent commit on `ref` before the push. | -| `after` | `문자열` | The SHA of the most recent commit on `ref` after the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `문자열` | The SHA of the commit. | -| `commits[][timestamp]` | `문자열` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `문자열` | The commit message. | -| `commits[][author]` | `개체` | The git author of the commit. | -| `commits[][author][name]` | `문자열` | The git author's name. | -| `commits[][author][email]` | `문자열` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | -| `commits[][added]` | `array` | An array of files added in the commit. | -| `commits[][modified]` | `array` | An array of files modified by the commit. | -| `commits[][removed]` | `array` | An array of files removed in the commit. | -| `pusher` | `개체` | The user who pushed the commits. | +| 키 | 유형 | 설명 | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ref` | `문자열` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `before` | `문자열` | The SHA of the most recent commit on `ref` before the push. | +| `after` | `문자열` | The SHA of the most recent commit on `ref` after the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][id]` | `문자열` | The SHA of the commit. | +| `commits[][timestamp]` | `문자열` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `문자열` | The commit message. | +| `commits[][author]` | `개체` | The git author of the commit. | +| `commits[][author][name]` | `문자열` | The git author's name. | +| `commits[][author][email]` | `문자열` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| `commits[][added]` | `array` | An array of files added in the commit. | +| `commits[][modified]` | `array` | An array of files modified by the commit. | +| `commits[][removed]` | `array` | An array of files removed in the commit. | +| `pusher` | `개체` | The user who pushed the commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1022,7 +1022,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### repository_dispatch -This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event)" endpoint. +This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. #### Availability @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | 키 | 유형 | 설명 | | ---- | ----- | --------------------------------------------------------------------------- | -| `동작` | `문자열` | The action that was performed. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| +| `동작` | `문자열` | The action that was performed. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1060,7 +1060,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% if currentVersion == "free-pro-team@latest"%} ### repository_import -{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/v3/migrations/source_imports/). +{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports). #### Availability @@ -1237,9 +1237,9 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ #### Webhook payload object -| 키 | 유형 | 설명 | -| --- | ---- | ------------------------------------------------------------------------------------------------------ | -| `팀` | `개체` | The [team](/v3/teams/) that was modified. **Note:** Older events may not include this in the payload. | +| 키 | 유형 | 설명 | +| --- | ---- | ----------------------------------------------------------------------------------------------------------------- | +| `팀` | `개체` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1268,7 +1268,7 @@ When a user is `created` or `deleted`. {% data reusables.webhooks.watch_short_desc %} -The event’s actor is the [user](/v3/users/) who starred a repository, and the event’s repository is the [repository](/v3/repos/) that was starred. +The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. #### Availability diff --git a/translations/ko-KR/content/github/administering-a-repository/about-releases.md b/translations/ko-KR/content/github/administering-a-repository/about-releases.md index 65fd50ecbb..194786ffab 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-releases.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-releases.md @@ -37,7 +37,7 @@ If a release fixes a security vulnerability, you should publish a security advis You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/v3/repos/releases/)." +You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)." {% if currentVersion == "free-pro-team@latest" %} ### Storage and bandwidth quotas diff --git a/translations/ko-KR/content/github/administering-a-repository/about-required-status-checks.md b/translations/ko-KR/content/github/administering-a-repository/about-required-status-checks.md index 87223e5fe1..63aa64f741 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-required-status-checks.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-required-status-checks.md @@ -36,7 +36,7 @@ You can set up either loose or strict status checks, depending on whether you wa ### Troubleshooting required status checks -If you have a check and a status with the same name and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/v3/checks/)." +If you have a check and a status with the same name and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)." Once you've set up required status checks, your branch must be up to date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. @@ -62,7 +62,7 @@ remote: error: Required status check "ci-build" is failing {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, it must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pull Requests](/v3/pulls/#response-1)." +Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, it must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pull Requests](/rest/reference/pulls#response-1)." ![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md index 3f62ea9444..90b2670783 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,12 +15,15 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} + ### About release management +{% if currentVersion == "free-pro-team@latest" %} You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% endif %} You can choose whether + {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/ko-KR/content/github/authenticating-to-github/about-githubs-ip-addresses.md index 47b7058574..1737356d63 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/about-githubs-ip-addresses.md +++ b/translations/ko-KR/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -12,7 +12,7 @@ versions: free-pro-team: '*' --- -You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/v3/meta/)." +You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)." These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges. diff --git a/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md index 138b970cd4..a76918b12c 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -12,7 +12,7 @@ versions: github-ae: '*' --- -Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/v3/auth/#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). +Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). {% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %} diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md index 7acf9caa10..4723d04971 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md @@ -29,7 +29,7 @@ There are two types of status checks on {% data variables.product.product_name % _Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_app %}s. -Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/v3/checks/)" and "[Statuses](/v3/repos/statuses/)." +Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/rest/reference/checks)" and "[Statuses](/rest/reference/repos#statuses)." ### Checks diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index cbf7e51a56..a74ff9111c 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -11,7 +11,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/v3/migrations/)." +To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/rest/reference/migrations)." {% else %} You can download and back up your repositories manually: @@ -21,15 +21,15 @@ You can download and back up your repositories manually: When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your {% data variables.product.product_name %} repository to your local machine: -- [문제](/v3/issues/#list-issues-for-a-repository) -- [Pull requests](/v3/pulls/#list-pull-requests) +- [문제](/rest/reference/issues#list-issues-for-a-repository) +- [Pull requests](/rest/reference/pulls#list-pull-requests) - [Forks](/rest/reference/repos#list-forks) - [Comments](/rest/reference/issues#list-issue-comments-for-a-repository) - [Milestones](/rest/reference/issues#list-milestones) - [Labels](/rest/reference/issues#list-labels-for-a-repository) - [Watchers](/rest/reference/activity#list-watchers) - [별을 준 사람들](/rest/reference/activity#list-stargazers) -- [Projects](/v3/projects/#list-repository-projects) +- [Projects](/rest/reference/projects#list-repository-projects) {% endif %} Once you have {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 6b51db17f0..45018e2271 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ When you search by a family license, your results will include all licenses in t ### Detecting a license -[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/v3/licenses/) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. diff --git a/translations/ko-KR/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/ko-KR/content/github/extending-github/git-automation-with-oauth-tokens.md index 162fa92202..af90164963 100644 --- a/translations/ko-KR/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/ko-KR/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -43,4 +43,4 @@ To avoid these prompts, you can use Git password caching. For information, see " ### 더 읽을거리 -- "[Authorizing OAuth Apps](/v3/oauth/)" +- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)" diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index cc0e246565..767b7ad311 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ You can use {% data variables.product.prodname_code_scanning %} to find, triage, If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/v3/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index f6a0e3abd4..9e693aff0b 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -50,6 +50,32 @@ The default {% data variables.product.prodname_codeql_workflow %} uses the `pull For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +#### Avoiding unnecessary scans of pull requests + +You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. + +``` yaml +on: + push: + branches: [main, protected] + pull_request: + branches: [main] + paths-ignore: + - '**/*.md' + - '**/*.txt' +``` + +{% note %} + +**참고** + +* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." +* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. + +{% endnote %} + +For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." + #### Scanning on a schedule If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." @@ -233,13 +259,13 @@ If you only want to run custom queries, you can disable the default security que #### Specifying directories to scan -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from scans by adding a `paths-ignore` array. +For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. ``` yaml -paths: +paths: - src paths-ignore: - - node_modules + - src/node_modules - '**/*.test.js' ``` @@ -252,7 +278,7 @@ paths-ignore: {% endnote %} -For C/C++, C#, and Java, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index 85c5c093e6..09453e574d 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -41,7 +41,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie {% endtip %} {% endif %} -Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage worflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### Reviewing all of your subscriptions diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/index.md b/translations/ko-KR/content/github/managing-your-work-on-github/index.md index c6f2a858e0..d882a90b1d 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/index.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/index.md @@ -14,7 +14,7 @@ versions: ### Table of Contents -{% topic_link_in_list /managing-your-work-with-issues %} +{% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} @@ -27,6 +27,7 @@ versions: {% link_in_list /pinning-an-issue-to-your-repository %} {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} + {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} {% link_in_list /about-automation-for-issues-and-pull-requests-with-query-parameters %} {% link_in_list /file-attachments-on-issues-and-pull-requests %} @@ -35,12 +36,6 @@ versions: {% link_in_list /disabling-issues %} {% link_in_list /linking-a-pull-request-to-an-issue %} {% link_in_list /about-duplicate-issues-and-pull-requests %} -{% topic_link_in_list /labeling-issues-and-pull-requests %} - {% link_in_list /about-labels %} - {% link_in_list /creating-a-label %} - {% link_in_list /applying-labels-to-issues-and-pull-requests %} - {% link_in_list /editing-a-label %} - {% link_in_list /deleting-a-label %} {% topic_link_in_list /managing-project-boards %} {% link_in_list /about-project-boards %} {% link_in_list /creating-a-project-board %} diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md b/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md new file mode 100644 index 0000000000..97c332fe04 --- /dev/null +++ b/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md @@ -0,0 +1,97 @@ +--- +title: Managing labels +intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +redirect_from: + - /articles/managing-Labels + - /articles/labeling-issues-and-pull-requests + - /github/managing-your-work-on-github/labeling-issues-and-pull-requests + - /articles/about-labels + - /github/managing-your-work-on-github/about-labels + - /articles/creating-and-editing-labels-for-issues-and-pull-requests + - /articles/creating-a-label + - /github/managing-your-work-on-github/creating-a-label + - /articles/customizing-issue-labels/ + - /articles/applying-labels-to-issues-and-pull-requests + - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests + - /articles/editing-a-label + - /github/managing-your-work-on-github/editing-a-label + - /articles/deleting-a-label + - /github/managing-your-work-on-github/deleting-a-label +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### About labels + +You can manage your work on {% data variables.product.product_name %} by creating labels to categorize issues and pull requests. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. + +Anyone with read access to a repository can view and search the repository’s labels. To create, edit, apply, or delete a label, you must have write access to the repository. + +### About default labels + +{% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository. + +| Label | 설명 | +| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `문서` | Indicates a need for improvements or additions to documentation{% endif %} +| `duplicate` | Indicates similar issues or pull requests | +| `enhancement` | Indicates new feature requests | +| `good first issue` | Indicates a good issue for first-time contributors | +| `help wanted` | Indicates that a maintainer wants help on an issue or pull request | +| `invalid` | Indicates that an issue or pull request is no longer relevant | +| `question` | Indicates that an issue or pull request needs more information | +| `wontfix` | Indicates that work won't continue on an issue or pull request | + +Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +Organization owners can customize the default labels for repositories in their organization. For more information, see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)." +{% endif %} + +### Creating a label + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. To the right of the search field, click **New label**. +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### Applying labels to issues and pull requests + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. In the upper-right corner, click **Label**, then start typing the name of an existing label. Click the label's name to associate it with the selected items. ![Issues Milestone assignment drop-down](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### Editing a label + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### Deleting a label +Deleting a label will remove the label from issues and pull requests. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.delete-label %} + +### 더 읽을거리 +- "[About labels](/articles/about-labels)" +- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/ko-KR/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md new file mode 100644 index 0000000000..7627c87e95 --- /dev/null +++ b/translations/ko-KR/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Managing your work with issues and pull requests +intro: 'You can manage your work on {% data variables.product.product_name %} by creating issues to track ideas, enhancements, tasks, or bugs.' +mapTopic: true +redirect_from: + - /github/managing-your-work-on-github/managing-your-work-with-issues + - /articles/managing-your-work-with-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index b10689f90f..1f2f3910b8 100644 --- a/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -163,7 +163,7 @@ You can use the `project` qualifier to find issues that are associated with a sp ### Search by commit status -You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/v3/repos/statuses/) or a CI service. +You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service. | Qualifier | 예시 | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 538275f538..b1c8f2ef96 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -40,7 +40,7 @@ Some IdPs support provisioning access to a {% data variables.product.prodname_d ### Adding members to an organization using SAML SSO -After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/v3/orgs/members/#add-or-update-organization-membership)." +After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." {% data reusables.organizations.team-synchronization %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 2120f1dba0..3365dae5ab 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -12,7 +12,7 @@ If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-s If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. -These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/v3/scim/) in the {% data variables.product.product_name %} API documentation. +These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% data variables.product.product_name %} API documentation. - Azure AD - Okta - OneLogin diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index bc5cf4609e..3ffd62c502 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -59,6 +59,7 @@ In addition to managing organization-level settings, organization owners have ad | Edit wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} | [Report abusive or spammy content](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} | Apply labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | | Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** | | Apply milestones | | **X** | **X** | **X** | **X** | | Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 7a37fcd35f..f14dbeb656 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -429,9 +429,9 @@ For more information, see "[Restricting publication of {% data variables.product | 동작 | 설명 | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | -| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data.variables.product.prodname_dotcom %} for a draft security advisory. | -| `github_broadcast` | Triggered when {% data.variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | -| `github_withdraw` | Triggered when {% data.variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | | `open` | Triggered when someone opens a draft security advisory. | | `publish` | Triggered when someone publishes a security advisory. | | `reopen` | Triggered when someone reopens as draft security advisory. | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 702d925c1a..e9991559b7 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -23,7 +23,7 @@ Parent teams cannot synchronize with IdP groups. If the team you want to connect To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." -You can also manage team synchronization with the API. For more information, see "[Team synchronization](/v3/teams/team_sync/)." +You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)." ### Requirements for members of synchronized teams diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md index ea38298892..fab3c8a0ca 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -26,7 +26,7 @@ For more information about the differences between {% data variables.product.pro For more information about member access and management, see "{% if currentVersion == "free-pro-team@latest" %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}." -For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 018d39b694..d71085132f 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -10,7 +10,7 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} -3. In the left sidebar, click **{% data variables.product.prodname_oauth_app %}s**. ![{ site.data.variables.product.prodname_oauth_app }}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. In the left sidebar, click **{% data variables.product.prodname_oauth_app %}s**. ![{% data variables.product.prodname_oauth_app %}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) 3. Click **Register a new application**. 4. Under **Application name**, type "Jira". 5. Under **Homepage URL**, type the full URL to your Jira instance. diff --git a/translations/ko-KR/content/github/site-policy/github-privacy-statement.md b/translations/ko-KR/content/github/site-policy/github-privacy-statement.md index d7613d36fd..fdb3688b72 100644 --- a/translations/ko-KR/content/github/site-policy/github-privacy-statement.md +++ b/translations/ko-KR/content/github/site-policy/github-privacy-statement.md @@ -201,7 +201,7 @@ Please contact the Account owners for more information about how they might proc #### Third party applications -You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/v3/users/) to see what information is provided when you authenticate into a Developer Product using your GitHub profile. +You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile. #### GitHub 페이지 diff --git a/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index d7198c1cac..b88292324e 100644 --- a/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -28,7 +28,7 @@ With respect to their personal information, California residents may exercise th California residents have the right to request from a business disclosure of the categories and specific pieces of personal information it has collected from them in the preceding 12 months, the categories of sources from which such personal information is collected, the business or commercial purpose for collecting or selling such personal information, and the categories of third parties with whom the business shares personal information. -If you request that a business disclose categories and specific pieces of personal information collected about you, you have the right to receive that information, free of charge, twice a year. The information may be delivered by mail or electronically and, if provided electronically, shall be in a portable and, to the extent technically feasible, readily usable format that allows the California resident to relatively easily transmit this information to another entity. You can use GitHub’s [User Migration API](/v3/migrations/users/) to access and download your data. Learn more [here](https://github.blog/2018-12-19-download-your-data/). +If you request that a business disclose categories and specific pieces of personal information collected about you, you have the right to receive that information, free of charge, twice a year. The information may be delivered by mail or electronically and, if provided electronically, shall be in a portable and, to the extent technically feasible, readily usable format that allows the California resident to relatively easily transmit this information to another entity. You can use GitHub’s [User Migration API](/rest/reference/migrations#users) to access and download your data. Learn more [here](https://github.blog/2018-12-19-download-your-data/). ### 2. Right to know whether your personal information is sold or disclosed for a business purpose and to whom diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index 83f2ce29f2..f11ff74a9a 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -54,8 +54,6 @@ If you live in a supported region, you can follow these instructions to submit y {% data reusables.sponsors.double-check-stripe-info %} -If you live in an unsupported region and are accepted to the beta of {% data variables.product.prodname_sponsors %}, you will receive an email with instructions to provide your bank information so that you can receive payments via ACH transfer or wire transfer. - {% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} diff --git a/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md index a205866918..67d6ea0ff6 100644 --- a/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md +++ b/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md @@ -10,7 +10,7 @@ versions: {% data variables.product.product_name %} stores repository and profile metadata from your personal account's activity. You can export your personal account's data through settings on {% data variables.product.prodname_dotcom_the_website %} or with the User Migration API. -For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see "[Download a user migration archive](/v3/migrations/users/#download-a-user-migration-archive)" and "[About {% data variables.product.product_name %}'s use of your data](/articles/about-github-s-use-of-your-data). +For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see "[Download a user migration archive](/rest/reference/migrations#download-a-user-migration-archive)" and "[About {% data variables.product.product_name %}'s use of your data](/articles/about-github-s-use-of-your-data). When you request an export of your personal data through settings on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.product_name %} packages your personal data in a `tar.gz` file and sends you an email to your primary email address with a download link. diff --git a/translations/ko-KR/content/github/using-git/which-remote-url-should-i-use.md b/translations/ko-KR/content/github/using-git/which-remote-url-should-i-use.md index 961edb4c57..7de5599e0d 100644 --- a/translations/ko-KR/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/ko-KR/content/github/using-git/which-remote-url-should-i-use.md @@ -44,7 +44,7 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit {% tip %} -**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/v3/guides/using-ssh-agent-forwarding/)." +**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} diff --git a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index bc0f615a44..d3ef7ec30a 100644 --- a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -36,7 +36,7 @@ If you don't appear in a repository's contributors graph, it may be because: {% tip %} -**Tip:** To list all commit contributors in a repository, see "[Repositories](/v3/repos/#list-contributors)." +**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)." {% endtip %} diff --git a/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md b/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md index 3745adbb18..19722761b2 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md @@ -150,4 +150,4 @@ While you can't specify custom MIME types on a per-file or per-repository basis, ### 더 읽을거리 - [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %} -- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)" +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index f3ca97d471..dc00414587 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -16,7 +16,7 @@ versions: Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} - The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} -- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/v3/guides/managing-deploy-keys/#machine-users)." +- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)." - You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safelist. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation. {% note %} diff --git a/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md b/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md index c7a8a62125..5ab7b8a8ed 100644 --- a/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md @@ -18,7 +18,7 @@ Follow the steps in "[Creating a personal access token](/github/authenticating-t {% if currentVersion == "free-pro-team@latest" %} -To match the behavior of the [GraphQL Explorer](/v4/guides/using-the-explorer), request the following scopes: +To match the behavior of the [GraphQL Explorer](/graphql/guides/using-the-explorer), request the following scopes: {% else %} @@ -50,9 +50,9 @@ The endpoint remains constant no matter what operation you perform. ### Communicating with GraphQL -Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/v4/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. +Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/graphql/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. -In REST, [HTTP verbs](/v3/#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/v4/guides/intro-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest)." +In REST, [HTTP verbs](/rest#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." To query GraphQL using cURL, make a `POST` request with a JSON payload. The payload must contain a string called `query`: @@ -72,15 +72,15 @@ curl -H "Authorization: bearer token" -X POST -d " \ #### About query and mutation operations -The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/v4/mutation/) determines which modification is executed. +The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/graphql/reference/mutations) determines which modification is executed. -For information about rate limiting, see "[GraphQL resource limitations](/v4/guides/resource-limitations/)." +For information about rate limiting, see "[GraphQL resource limitations](/graphql/overview/resource-limitations)." Queries and mutations share similar forms, with some important differences. #### About queries -GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/v4/guides/intro-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/v4/scalar/). +GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/graphql/guides/introduction-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/graphql/reference/scalars). Queries are structured like this: @@ -107,7 +107,7 @@ Mutations are structured like this: The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. -In the [mutations](/v4/mutation/) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. +In the [mutations](/graphql/reference/mutations) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. For a real-world example, see "[Example mutation](#example-mutation)." @@ -117,7 +117,7 @@ For a real-world example, see "[Example mutation](#example-mutation)." {% note %} -**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/v4/guides/using-the-explorer/#using-the-variable-pane), and do not include the word `variables` before the JSON object. +**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object. {% endnote %} @@ -207,7 +207,7 @@ Looking at the composition line by line: * `repository(owner:"octocat", name:"Hello-World") {` - To begin the query, we want to find a [`repository`](/v4/object/repository/) object. The schema validation indicates this object requires an `owner` and a `name` argument. + To begin the query, we want to find a [`repository`](/graphql/reference/objects#repository) object. The schema validation indicates this object requires an `owner` and a `name` argument. * `issues(last:20, states:CLOSED) {` @@ -215,9 +215,9 @@ Looking at the composition line by line: Some details about the `issues` object: - - The [docs](/v4/object/repository/) tell us this object has the type `IssueConnection`. + - The [docs](/graphql/reference/objects#repository) tell us this object has the type `IssueConnection`. - Schema validation indicates this object requires a `last` or `first` number of results as an argument, so we provide `20`. - - The [docs](/v4/object/repository/) also tell us this object accepts a `states` argument, which is an [`IssueState`](/v4/enum/issuestate/) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. + - The [docs](/graphql/reference/objects#repository) also tell us this object accepts a `states` argument, which is an [`IssueState`](/graphql/reference/enums#issuestate) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. * `edges {` @@ -225,9 +225,9 @@ Looking at the composition line by line: * `node {` - Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/v4/object/issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. + Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/graphql/reference/objects#issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. -* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/v4/object/issue) and specify the fields we want to return: +* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/graphql/reference/objects#issue) and specify the fields we want to return: ```graphql title @@ -243,7 +243,7 @@ Looking at the composition line by line: Here we specify the `title`, `url`, and `labels` fields of the `Issue` object. - The `labels` field has the type [`LabelConnection`](/v4/object/labelconnection/). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. + The `labels` field has the type [`LabelConnection`](/graphql/reference/objects#labelconnection). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. You may notice that running this query on the Octocat's public `Hello-World` repository won't return many labels. Try running it on one of your own repositories that does use labels, and you'll likely see a difference. @@ -285,7 +285,7 @@ Let's walk through the example. The task sounds simple: add an emoji reaction to So how do we know to begin with a query? We don't, yet. -Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/v4/mutation/addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! +Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/graphql/reference/mutations#addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! The docs for the mutation list three input fields: @@ -337,13 +337,13 @@ With the ID known, we can proceed with the mutation: - `addReaction` is the name of the mutation. - `input` is the required argument key. This will always be `input` for a mutation. - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/v4/input_object/) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/graphql/reference/input-objects) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. - How do we know which value to use for the content? The [`addReaction` docs](/v4/mutation/addreaction/) tell us the `content` field has the type [`ReactionContent`](/v4/enum/reactioncontent/), which is an [enum](/v4/enum) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): + How do we know which value to use for the content? The [`addReaction` docs](/graphql/reference/mutations#addreaction) tell us the `content` field has the type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an [enum](/graphql/reference/enums) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): {% data reusables.repositories.reaction_list %} -* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/v4/mutation/addreaction), which three possible return fields: +* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/graphql/reference/mutations#addreaction), which three possible return fields: - `clientMutationId` (`String`) - `reaction` (`Reaction!`) @@ -394,7 +394,7 @@ variables { {% note %} You may notice that the `content` field value in the earlier example (where it's used directly in the mutation) does not have quotes around `HOORAY`, but it does have quotes when used in the variable. There's a reason for this: -* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/v4/enum/reactioncontent/), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. +* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. * When you use `content` in a variable, the variables section must be valid JSON, so the quotes are required. Schema validation correctly interprets the `ReactionContent` type when the variable is passed into the mutation during execution. For more information on the difference between enums and strings, see the [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). diff --git a/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md b/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md index f4d05b5bee..017b674775 100644 --- a/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md +++ b/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md @@ -12,7 +12,7 @@ versions: ### GraphQL terminology -The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/v4/). +The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/graphql). ### Schema @@ -30,11 +30,11 @@ This means that if you try to return a field that is not a scalar, schema valida ### Argument -An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/v4/guides/forming-calls#about-mutations) require an input object as an argument. +An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/graphql/guides/forming-calls-with-graphql#about-mutations) require an input object as an argument. ### Implementation -A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/v4/interface). +A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/graphql/reference/interfaces). Here's a contrived example of a schema that defines interface `X` and object `Y`: @@ -55,13 +55,13 @@ This means object `Y` requires the same fields/arguments/return types that inter In the reference docs, you'll find that: -* Each [object](/v4/object) lists the interface(s) _from which it inherits_ under **Implements**. +* Each [object](/graphql/reference/objects) lists the interface(s) _from which it inherits_ under **Implements**. -* Each [interface](/v4/interface) lists the objects _that inherit from it_ under **Implementations**. +* Each [interface](/graphql/reference/interfaces) lists the objects _that inherit from it_ under **Implementations**. ### Connection -Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest)." +Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." It's helpful to picture a graph: dots connected by lines. The dots are nodes, the lines are edges. A connection defines a relationship between nodes. @@ -71,7 +71,7 @@ Edges represent connections between nodes. When you query a connection, you trav ### Node -_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/v4/scalar), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/v4/guides/using-global-node-ids)." +_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/graphql/reference/scalars), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ## Discovering the GraphQL API @@ -130,4 +130,4 @@ query { {% endnote %} - For more information about performing queries, see "[Forming calls with GraphQL](/v4/guides/forming-calls)." + For more information about performing queries, see "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." diff --git a/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md b/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md index 4b002a1c85..906de99617 100644 --- a/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md @@ -33,7 +33,7 @@ With the Enterprise Accounts API, you can: - Invite administrators to your enterprise account. - Create new organizations in your enterprise account. -For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/v4/guides/managing-enterprise-accounts/#graphql-fields-and-types-for-the-enterprise-accounts-api)." +For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)." ### Getting started using GraphQL for enterprise accounts @@ -197,12 +197,12 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio } ``` -For more information about getting started with GraphQL, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql/)" and "[Forming Calls with GraphQL](/v4/guides/forming-calls/)." +For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." ### GraphQL fields and types for the Enterprise Accounts API Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API. -For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/v4/). +For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql). -You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)." For other information, such as authentication and rate limit details, check out the [guides](/v4/guides). +You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)." For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). diff --git a/translations/ko-KR/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/ko-KR/content/graphql/guides/migrating-from-rest-to-graphql.md index dbc64338ed..27493df1c5 100644 --- a/translations/ko-KR/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/ko-KR/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: Migrating from REST to GraphQL represents a significant shift in API logic. The differences between REST as a style and GraphQL as a specification make it difficult—and often undesirable—to replace REST API calls with GraphQL API queries on a one-to-one basis. We've included specific examples of migration below. -To migrate your code from the [REST API](/v3) to the GraphQL API: +To migrate your code from the [REST API](/rest) to the GraphQL API: - Review the [GraphQL spec](https://graphql.github.io/graphql-spec/June2018/) -- Review GitHub's [GraphQL schema](/v4/reference/) +- Review GitHub's [GraphQL schema](/graphql/reference) - Consider how any existing code you have currently interacts with the GitHub REST API -- Use [Global Node IDs](/v4/guides/using-global-node-ids) to reference objects between API versions +- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions Significant advantages of GraphQL include: @@ -53,12 +53,12 @@ query { } ``` -Consider another example: retrieving a list of pull requests and checking if each one is mergeable. A call to the REST API retrieves a list of pull requests and their [summary representations](/v3/#summary-representations): +Consider another example: retrieving a list of pull requests and checking if each one is mergeable. A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/v3/#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: +Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ Using the **GraphQL API**, you can retrieve the data with a single query using n } ``` -You can also extend the power of this query by [substituting a variable](/v4/guides/forming-calls/#working-with-variables) for the pull request number. +You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. ## Example: Strong typing GraphQL schemas are strongly typed, making data handling safer. -Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/v4/mutation), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/v4/mutation/addcomment/): +Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): ```graphql mutation { diff --git a/translations/ko-KR/content/graphql/guides/using-global-node-ids.md b/translations/ko-KR/content/graphql/guides/using-global-node-ids.md index 77307ca9eb..0fb33e4920 100644 --- a/translations/ko-KR/content/graphql/guides/using-global-node-ids.md +++ b/translations/ko-KR/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ You can access most objects in GitHub (users, issues, pull requests, etc.) using {% note %} -**Note:** In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql/#node)." +**Note:** In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." {% endnote %} @@ -29,7 +29,7 @@ Let's walk through an example. ### 1. Call a REST endpoint that returns an object's node ID -If you [request the authenticated user](/v3/users/#get-the-authenticated-user): +If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { This type of query—that is, finding the node by ID—is known as a "direct node lookup." -When you run this query, you'll see that the `__typename` is [`User`](/v4/object/user/). +When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). ### 3. Do a direct node lookup in GraphQL @@ -122,4 +122,4 @@ This type of query is the standard approach for looking up an object by its glob ### Using global node IDs in migrations -When building integrations that use either the REST API or the GraphQL API, it's best practice to persist the global node ID so you can easily reference objects across API versions. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest/)." +When building integrations that use either the REST API or the GraphQL API, it's best practice to persist the global node ID so you can easily reference objects across API versions. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." diff --git a/translations/ko-KR/content/graphql/guides/using-the-explorer.md b/translations/ko-KR/content/graphql/guides/using-the-explorer.md index f9b1c02f3e..50ced501bf 100644 --- a/translations/ko-KR/content/graphql/guides/using-the-explorer.md +++ b/translations/ko-KR/content/graphql/guides/using-the-explorer.md @@ -13,11 +13,11 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -[GraphQL Explorer](/v4/explorer) is an instance of [GraphiQL](https://github.com/graphql/graphiql), which is a "graphical interactive in-browser GraphQL IDE." +[GraphQL Explorer](/graphql/overview/explorer) is an instance of [GraphiQL](https://github.com/graphql/graphiql), which is a "graphical interactive in-browser GraphQL IDE." {% note %} -**Note**: {% data variables.product.prodname_dotcom %} has disabled [mutations](/v4/mutation/) in the Explorer, but you can use them in your own GraphiQL instance. +**Note**: {% data variables.product.prodname_dotcom %} has disabled [mutations](/graphql/reference/mutations) in the Explorer, but you can use them in your own GraphiQL instance. {% endnote %} @@ -33,7 +33,7 @@ To use the GraphiQL app, download and install it from https://github.com/skevy/g #### Configuring GraphiQL -1. Get an [OAuth token](/v4/guides/forming-calls#authenticating-with-graphql). +1. Get an [OAuth token](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql). 1. Launch GraphiQL. 1. In the upper-right corner of GraphiQL, click **Edit HTTP Headers**. 1. In the **Key** field, enter `Authorization`. In the **Value** field, enter `Bearer `, where `` is your generated OAuth token. ![graphiql headers](/assets/images/developer/graphiql-headers.png) @@ -44,7 +44,7 @@ To use the GraphiQL app, download and install it from https://github.com/skevy/g {% note %} -**Note**: For more information about why `POST` is the method, see "[Communicating with GraphQL](/v4/guides/forming-calls#communicating-with-graphql)." +**Note**: For more information about why `POST` is the method, see "[Communicating with GraphQL](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)." {% endnote %} @@ -66,13 +66,13 @@ All types in a GraphQL schema include a `description` field compiled into docume {% note %} -The **Docs** sidebar contains the same content that is automatically generated from the schema under "[Reference](/v4/)," though it is formatted differently in places. +The **Docs** sidebar contains the same content that is automatically generated from the schema under "[Reference](/graphql)," though it is formatted differently in places. {% endnote %} ### Using the variable pane -Some example calls include [variables](/v4/guides/forming-calls#working-with-variables) written like this: +Some example calls include [variables](/graphql/guides/forming-calls-with-graphql#working-with-variables) written like this: ```graphql query($number_of_repos:Int!){ @@ -90,7 +90,7 @@ variables { } ``` -This is the correct format to submit the call via a cURL `POST` (as long as you [escape newlines](/v4/guides/forming-calls#communicating-with-graphql)). +This is the correct format to submit the call via a cURL `POST` (as long as you [escape newlines](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)). If you want to run the call in the Explorer, enter the `query` segment in the main pane and the variables in the **Query Variables** pane below it. Omit the word `variables` from the Explorer: @@ -106,12 +106,12 @@ If you want to run the call in the Explorer, enter the `query` segment in the ma ### Troubleshooting errors -Because GraphQL is [introspective](/v4/guides/intro-to-graphql#discovering-the-graphql-api), the Explorer supports: +Because GraphQL is [introspective](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), the Explorer supports: * Intelligent typeaheads aware of the current schema * Validation error previews as you type -If you enter a query that is not well-formed or does not pass [schema validation](/v4/guides/intro-to-graphql#schema), a popup warns you of an error. If you run the query, the error returns in the response pane. +If you enter a query that is not well-formed or does not pass [schema validation](/graphql/guides/introduction-to-graphql#schema), a popup warns you of an error. If you run the query, the error returns in the response pane. A GraphQL response contains several keys: a `data` hash and an `errors` array. diff --git a/translations/ko-KR/content/graphql/overview/about-the-graphql-api.md b/translations/ko-KR/content/graphql/overview/about-the-graphql-api.md index 64bce06cad..dd59f763da 100644 --- a/translations/ko-KR/content/graphql/overview/about-the-graphql-api.md +++ b/translations/ko-KR/content/graphql/overview/about-the-graphql-api.md @@ -11,25 +11,25 @@ versions: Here are some quick links to get you up and running with the GraphQL API v4: -* [Authentication](/v4/guides/forming-calls/#authenticating-with-graphql) -* [Root endpoint](/v4/guides/forming-calls/#the-graphql-endpoint) -* [Schema introspection](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) -* [Rate limits](/v4/guides/resource-limitations/) -* [Migrating from REST](/v4/guides/migrating-from-rest) +* [Authentication](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) +* [Root endpoint](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) +* [Schema introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) +* [Rate limits](/graphql/overview/resource-limitations) +* [Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql) ### About GraphQL The [GraphQL](https://graphql.github.io/) data query language is: -* **A [specification](https://graphql.github.io/graphql-spec/June2018/).** The spec determines the validity of the [schema](/v4/guides/intro-to-graphql#schema) on the API server. The schema determines the validity of client calls. +* **A [specification](https://graphql.github.io/graphql-spec/June2018/).** The spec determines the validity of the [schema](/graphql/guides/introduction-to-graphql#schema) on the API server. The schema determines the validity of client calls. * **[Strongly typed](#about-the-graphql-schema-reference).** The schema defines an API's type system and all object relationships. -* **[Introspective](/v4/guides/intro-to-graphql#discovering-the-graphql-api).** A client can query the schema for details about the schema. +* **[Introspective](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api).** A client can query the schema for details about the schema. -* **[Hierarchical](/v4/guides/forming-calls).** The shape of a GraphQL call mirrors the shape of the JSON data it returns. [Nested fields](/v4/guides/migrating-from-rest/#example-nesting) let you query for and receive only the data you specify in a single round trip. +* **[Hierarchical](/graphql/guides/forming-calls-with-graphql).** The shape of a GraphQL call mirrors the shape of the JSON data it returns. [Nested fields](/graphql/guides/migrating-from-rest-to-graphql#example-nesting) let you query for and receive only the data you specify in a single round trip. -* **An application layer.** GraphQL is not a storage model or a database query language. The _graph_ refers to graph structures defined in the schema, where [nodes](/v4/guides/intro-to-graphql#node) define objects and [edges](/v4/guides/intro-to-graphql#edge) define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored. +* **An application layer.** GraphQL is not a storage model or a database query language. The _graph_ refers to graph structures defined in the schema, where [nodes](/graphql/guides/introduction-to-graphql#node) define objects and [edges](/graphql/guides/introduction-to-graphql#edge) define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored. ### Why GitHub is using GraphQL @@ -39,15 +39,15 @@ For more details about why GitHub has moved to GraphQL, see the original [announ ### About the GraphQL schema reference -The docs in the sidebar are generated from the {% data variables.product.prodname_dotcom %} GraphQL [schema](/v4/guides/intro-to-graphql/#discovering-the-graphql-api). All calls are validated and executed against the schema. Use these docs to find out what data you can call: +The docs in the sidebar are generated from the {% data variables.product.prodname_dotcom %} GraphQL [schema](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api). All calls are validated and executed against the schema. Use these docs to find out what data you can call: -* Allowed operations: [queries](/v4/query) and [mutations](/v4/mutation). +* Allowed operations: [queries](/graphql/reference/queries) and [mutations](/graphql/reference/mutations). -* Schema-defined types: [scalars](/v4/scalar), [objects](/v4/object), [enums](/v4/enum), [interfaces](/v4/interface), [unions](/v4/union), and [input objects](/v4/input_object). +* Schema-defined types: [scalars](/graphql/reference/scalars), [objects](/graphql/reference/objects), [enums](/graphql/reference/enums), [interfaces](/graphql/reference/interfaces), [unions](/graphql/reference/unions), and [input objects](/graphql/reference/input-objects). -You can access this same content via the [Explorer Docs sidebar](/v4/guides/using-the-explorer#accessing-the-sidebar-docs). Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API. +You can access this same content via the [Explorer Docs sidebar](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API. -For other information, such as authentication and rate limit details, check out the [guides](/v4/guides). +For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). ### Requesting support diff --git a/translations/ko-KR/content/graphql/overview/breaking-changes.md b/translations/ko-KR/content/graphql/overview/breaking-changes.md index f9fde6b0f6..ba29ae3c09 100644 --- a/translations/ko-KR/content/graphql/overview/breaking-changes.md +++ b/translations/ko-KR/content/graphql/overview/breaking-changes.md @@ -16,7 +16,7 @@ Breaking changes are any changes that might require action from our integrators. - **Breaking:** Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change. - **Dangerous:** Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change. -We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a [schema preview](/v4/previews/). +We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a [schema preview](/graphql/overview/schema-previews). We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st. diff --git a/translations/ko-KR/content/graphql/overview/changelog.md b/translations/ko-KR/content/graphql/overview/changelog.md index dbb8876a2b..6c051b659f 100644 --- a/translations/ko-KR/content/graphql/overview/changelog.md +++ b/translations/ko-KR/content/graphql/overview/changelog.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -Breaking changes include changes that will break existing queries or could affect the runtime behavior of clients. For a list of breaking changes and when they will occur, see our [breaking changes log](/v4/breaking_changes). +Breaking changes include changes that will break existing queries or could affect the runtime behavior of clients. For a list of breaking changes and when they will occur, see our [breaking changes log](/graphql/overview/breaking-changes). {% for entry in graphql.changelog %} ### Schema Changes for {{ entry.date }} diff --git a/translations/ko-KR/content/graphql/overview/public-schema.md b/translations/ko-KR/content/graphql/overview/public-schema.md index 0df87e7653..d2a8c7309b 100644 --- a/translations/ko-KR/content/graphql/overview/public-schema.md +++ b/translations/ko-KR/content/graphql/overview/public-schema.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -You can [perform introspection](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) against the GraphQL API directly. +You can [perform introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) against the GraphQL API directly. Alternatively, you can download the latest version of the public schema here: diff --git a/translations/ko-KR/content/graphql/overview/resource-limitations.md b/translations/ko-KR/content/graphql/overview/resource-limitations.md index bd5cdb791c..d0714a5d93 100644 --- a/translations/ko-KR/content/graphql/overview/resource-limitations.md +++ b/translations/ko-KR/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## Node limit -To pass [schema](/v4/guides/intro-to-graphql#schema) validation, all GraphQL API v4 [calls](/v4/guides/forming-calls) must meet these standards: +To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: -* Clients must supply a `first` or `last` argument on any [connection](/v4/guides/intro-to-graphql#connection). +* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). * Values of `first` and `last` must be within 1-100. -* Individual calls cannot request more than 500,000 total [nodes](/v4/guides/intro-to-graphql#node). +* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). #### Calculating nodes in a call @@ -121,7 +121,7 @@ These two examples show how to calculate the total nodes in a call. The GraphQL API v4 limit is different from the REST API v3's [rate limits](/rest/overview/resources-in-the-rest-api#rate-limiting). -Why are the API rate limits different? With [GraphQL](/v4/), one GraphQL call can replace [multiple REST calls](/v4/guides/migrating-from-rest/). A single complex GraphQL call could be the equivalent of thousands of REST requests. While a single GraphQL call would fall well below the REST API rate limit, the query might be just as expensive for GitHub's servers to compute. +Why are the API rate limits different? With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). A single complex GraphQL call could be the equivalent of thousands of REST requests. While a single GraphQL call would fall well below the REST API rate limit, the query might be just as expensive for GitHub's servers to compute. To accurately represent the server cost of a query, the GraphQL API v4 calculates a call's **rate limit score** based on a normalized scale of points. A query's score factors in first and last arguments on a parent connection and its children. diff --git a/translations/ko-KR/content/graphql/overview/schema-previews.md b/translations/ko-KR/content/graphql/overview/schema-previews.md index b0b3a5e30f..6272f17066 100644 --- a/translations/ko-KR/content/graphql/overview/schema-previews.md +++ b/translations/ko-KR/content/graphql/overview/schema-previews.md @@ -13,7 +13,7 @@ versions: During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -To access a schema preview, you'll need to provide a custom [media type](/v3/media) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. +To access a schema preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% note %} diff --git a/translations/ko-KR/content/graphql/reference/enums.md b/translations/ko-KR/content/graphql/reference/enums.md index 3cec114335..f87cc2e4cc 100644 --- a/translations/ko-KR/content/graphql/reference/enums.md +++ b/translations/ko-KR/content/graphql/reference/enums.md @@ -12,9 +12,9 @@ versions: [Enums](https://graphql.github.io/graphql-spec/June2018/#sec-Enums) represent possible sets of values for a field. -For example, the [`Issue`](/v4/object/issue) object has a field called `state`. The state is an enum (specifically, of type [`IssueState`](/v4/enum/issuestate/)) because it may be `OPEN` or `CLOSED`. +For example, the [`Issue`](/graphql/reference/objects#issue) object has a field called `state`. The state is an enum (specifically, of type [`IssueState`](/graphql/reference/enums#issuestate)) because it may be `OPEN` or `CLOSED`. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." {% for item in graphql.schemaForCurrentVersion.enums %} {% include graphql-enum %} diff --git a/translations/ko-KR/content/graphql/reference/input-objects.md b/translations/ko-KR/content/graphql/reference/input-objects.md index 6726cfaf2c..423c6511c8 100644 --- a/translations/ko-KR/content/graphql/reference/input-objects.md +++ b/translations/ko-KR/content/graphql/reference/input-objects.md @@ -12,9 +12,9 @@ versions: [Input objects](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects) can be described as "composable objects" because they include a set of input fields that define the object. -For example, [`CommitAuthor`](/v4/input_object/commitauthor/) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/v4/object) **may** have input objects, whereas [mutations](/v4/mutation) **require** input objects. +For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/graphql/reference/objects) **may** have input objects, whereas [mutations](/graphql/reference/mutations) **require** input objects. -For more information, see "[About mutations](/v4/guides/forming-calls#about-mutations)." +For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)." {% for item in graphql.schemaForCurrentVersion.inputObjects %} {% include graphql-input-object %} diff --git a/translations/ko-KR/content/graphql/reference/interfaces.md b/translations/ko-KR/content/graphql/reference/interfaces.md index 0baee2c467..bfc411d796 100644 --- a/translations/ko-KR/content/graphql/reference/interfaces.md +++ b/translations/ko-KR/content/graphql/reference/interfaces.md @@ -12,9 +12,9 @@ versions: [Interfaces](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces) serve as parent objects from which other objects can inherit. -For example, [`Lockable`](/v4/interface/lockable/) is an interface because both [`Issue`](/v4/object/issue/) and [`PullRequest`](/v4/object/pullrequest/) objects can be locked. An interface has its own list of named fields that are shared by implementing objects. +For example, [`Lockable`](/graphql/reference/interfaces#lockable) is an interface because both [`Issue`](/graphql/reference/objects#issue) and [`PullRequest`](/graphql/reference/objects#pullrequest) objects can be locked. An interface has its own list of named fields that are shared by implementing objects. -For more information, see "[Implementation](/v4/guides/intro-to-graphql#implementation)." +For more information, see "[Implementation](/graphql/guides/introduction-to-graphql#implementation)." {% for item in graphql.schemaForCurrentVersion.interfaces %} {% include graphql-interface %} diff --git a/translations/ko-KR/content/graphql/reference/mutations.md b/translations/ko-KR/content/graphql/reference/mutations.md index 9f6542ab79..e42955c3d3 100644 --- a/translations/ko-KR/content/graphql/reference/mutations.md +++ b/translations/ko-KR/content/graphql/reference/mutations.md @@ -12,7 +12,7 @@ versions: Every GraphQL schema has a root type for both queries and mutations. The [mutation type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that change data on the server. It is analogous to performing HTTP verbs such as `POST`, `PATCH`, and `DELETE`. -For more information, see "[About mutations](/v4/guides/forming-calls#about-mutations)." +For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)." {% for item in graphql.schemaForCurrentVersion.mutations %} {% include graphql-mutation %} diff --git a/translations/ko-KR/content/graphql/reference/objects.md b/translations/ko-KR/content/graphql/reference/objects.md index 84cbbabfdf..345786d5e1 100644 --- a/translations/ko-KR/content/graphql/reference/objects.md +++ b/translations/ko-KR/content/graphql/reference/objects.md @@ -14,7 +14,7 @@ versions: For example, the [`Repository`](/graphql/reference/objects#repository) object has a field called `name`, which is a `String`. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." diff --git a/translations/ko-KR/content/graphql/reference/queries.md b/translations/ko-KR/content/graphql/reference/queries.md index b8ed9487c5..e9d3c92baf 100644 --- a/translations/ko-KR/content/graphql/reference/queries.md +++ b/translations/ko-KR/content/graphql/reference/queries.md @@ -13,7 +13,7 @@ versions: Every GraphQL schema has a root type for both queries and mutations. The [query type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that retrieve data from the server. -For more information, see "[About queries](/v4/guides/forming-calls#about-queries)." +For more information, see "[About queries](/graphql/guides/forming-calls-with-graphql#about-queries)." {% note %} diff --git a/translations/ko-KR/content/graphql/reference/scalars.md b/translations/ko-KR/content/graphql/reference/scalars.md index 0a37135d2c..338b4f42c7 100644 --- a/translations/ko-KR/content/graphql/reference/scalars.md +++ b/translations/ko-KR/content/graphql/reference/scalars.md @@ -14,7 +14,7 @@ versions: When calling the GraphQL API, you must specify nested subfields until you return only scalars. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql#field)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#field)." {% for item in graphql.schemaForCurrentVersion.scalars %} {% include graphql-scalar %} diff --git a/translations/ko-KR/content/graphql/reference/unions.md b/translations/ko-KR/content/graphql/reference/unions.md index 95f5a9f633..5a87c63fc0 100644 --- a/translations/ko-KR/content/graphql/reference/unions.md +++ b/translations/ko-KR/content/graphql/reference/unions.md @@ -12,9 +12,9 @@ versions: A [union](https://graphql.github.io/graphql-spec/June2018/#sec-Unions) is a type of object representing many objects. -For example, a field marked as an [`ProjectCardItem`](/v4/union/projectcarditem/) could be an [`Issue`](/v4/object/issue/) or a [`PullRequest`](/v4/object/pullrequest/) because each of those objects can be inside a project card. Using a union instead of an object gives you flexibility. +For example, a field marked as an [`ProjectCardItem`](/graphql/reference/unions#projectcarditem) could be an [`Issue`](/graphql/reference/objects#issue) or a [`PullRequest`](/graphql/reference/objects#pullrequest) because each of those objects can be inside a project card. Using a union instead of an object gives you flexibility. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." {% for item in graphql.schemaForCurrentVersion.unions %} {% include graphql-union %} diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 87f5be536c..a4cfdabbeb 100644 --- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: Enabling a link between GitHub Insights and GitHub Enterprise -intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {{ site.data.variables.product.prodname_insights }}.' +intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.' redirect_from: diff --git a/translations/ko-KR/content/packages/publishing-and-managing-packages/about-github-packages.md b/translations/ko-KR/content/packages/publishing-and-managing-packages/about-github-packages.md index 55a2bc4215..518df9da72 100644 --- a/translations/ko-KR/content/packages/publishing-and-managing-packages/about-github-packages.md +++ b/translations/ko-KR/content/packages/publishing-and-managing-packages/about-github-packages.md @@ -182,7 +182,7 @@ For more information, see: ### Managing packages -You can a delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package)" and "[Forming calls with GraphQL](/v4/guides/forming-calls/)." +You can a delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." diff --git a/translations/ko-KR/content/rest/guides/basics-of-authentication.md b/translations/ko-KR/content/rest/guides/basics-of-authentication.md index b8805432ed..beffcede81 100644 --- a/translations/ko-KR/content/rest/guides/basics-of-authentication.md +++ b/translations/ko-KR/content/rest/guides/basics-of-authentication.md @@ -130,7 +130,7 @@ Also, since there's a hierarchical relationship between scopes, you should check Checking for scopes only before making requests is not enough since it's possible that users will change the scopes in between your check and the actual request. In case that happens, API calls you expected to succeed might fail with a `404` or `401` status, or return a different subset of information. -To help you gracefully handle these situations, all API responses for requests made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes]. This header contains the list of scopes of the token that was used to make the request. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/v3/apps/oauth_applications/#check-an-authorization\]{% endif %}. Use this information to detect changes in token scopes, and inform your users of changes in available application functionality. +To help you gracefully handle these situations, all API responses for requests made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes]. This header contains the list of scopes of the token that was used to make the request. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. Use this information to detect changes in token scopes, and inform your users of changes in available application functionality. #### Making authenticated requests diff --git a/translations/ko-KR/content/rest/guides/best-practices-for-integrators.md b/translations/ko-KR/content/rest/guides/best-practices-for-integrators.md index a391e94b22..a376d64466 100644 --- a/translations/ko-KR/content/rest/guides/best-practices-for-integrators.md +++ b/translations/ko-KR/content/rest/guides/best-practices-for-integrators.md @@ -20,7 +20,7 @@ It's very important that you secure [the payloads sent from GitHub][event-types] There are several steps you can take to secure receipt of payloads delivered by GitHub: 1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% if currentVersion == "free-pro-team@latest" %} -1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/v3/meta/#meta) to find the address we use.{% endif %} +1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %} 1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected. ### Favor asynchronous work over synchronous @@ -49,7 +49,7 @@ Users can dig into the server responses you send back to GitHub. Ensure that you GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove. -We've provided [a list of HTTP status codes](/v3/#http-redirects) to watch out for when designing your app to follow redirects. +We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects. ### Don't manually parse URLs diff --git a/translations/ko-KR/content/rest/guides/building-a-ci-server.md b/translations/ko-KR/content/rest/guides/building-a-ci-server.md index dd6f60636d..16a776fd6e 100644 --- a/translations/ko-KR/content/rest/guides/building-a-ci-server.md +++ b/translations/ko-KR/content/rest/guides/building-a-ci-server.md @@ -129,7 +129,7 @@ At GitHub, we've used a version of [Janky][janky] to manage our CI for years. Th All of this communication is funneled back to our chat rooms. You don't need to build your own CI setup to use this example. You can always rely on [GitHub integrations][integrations]. -[status API]: /v3/repos/statuses/ +[status API]: /rest/reference/repos#statuses [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server diff --git a/translations/ko-KR/content/rest/guides/delivering-deployments.md b/translations/ko-KR/content/rest/guides/delivering-deployments.md index 7ec5a2a34d..00fc5fc581 100644 --- a/translations/ko-KR/content/rest/guides/delivering-deployments.md +++ b/translations/ko-KR/content/rest/guides/delivering-deployments.md @@ -145,7 +145,7 @@ At GitHub, we've used a version of [Heaven][heaven] to manage our deployments fo 간단하죠? You don't need to build your own deployment setup to use this example. You can always rely on [GitHub integrations][integrations]. -[deploy API]: /v3/repos/deployments/ +[deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok diff --git a/translations/ko-KR/content/rest/guides/discovering-resources-for-a-user.md b/translations/ko-KR/content/rest/guides/discovering-resources-for-a-user.md index 61ae4c6e93..bb34110d57 100644 --- a/translations/ko-KR/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/ko-KR/content/rest/guides/discovering-resources-for-a-user.md @@ -93,19 +93,19 @@ If you've read the docs from cover to cover, you may have noticed an [API method As an application, you typically want all of the user's organizations (public and private) that your app is authorized to access. The workflow above will give you exactly that. -[basics-of-authentication]: /v3/guides/basics-of-authentication/ -[list-public-orgs]: /v3/orgs/#list-organizations-for-a-user -[list-repositories-for-current-user]: /v3/repos/#list-repositories-for-the-authenticated-user -[list-orgs-for-current-user]: /v3/orgs/#list-organizations-for-the-authenticated-user -[list-teams]: /v3/teams/#list-teams -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests +[basics-of-authentication]: /rest/guides/basics-of-authentication +[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user +[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user +[list-teams]: /rest/reference/teams#list-teams +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ [octokit.rb]: https://github.com/octokit/octokit.rb [octokit.rb]: https://github.com/octokit/octokit.rb -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user -[publicize-membership]: /v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user -[register-oauth-app]: /v3/guides/basics-of-authentication/#registering-your-app +[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user +[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/ko-KR/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/ko-KR/content/rest/guides/getting-started-with-the-git-database-api.md index 38f5173b71..1c034db9bc 100644 --- a/translations/ko-KR/content/rest/guides/getting-started-with-the-git-database-api.md +++ b/translations/ko-KR/content/rest/guides/getting-started-with-the-git-database-api.md @@ -11,7 +11,7 @@ versions: This basically allows you to reimplement a lot of Git functionality over our API - by creating raw objects directly into the database and updating branch references you could technically do just about anything that Git can do without having Git installed. -Git Database API functions will return a `409 Conflict` if the Git repository is empty or unavailable. An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the "[Create or update file contents](/v3/repos/contents/#create-or-update-file-contents)" endpoint to create content and initialize the repository so you can use the Git Database API. Contact {% data variables.contact.contact_support %} if this response status persists. +Git Database API functions will return a `409 Conflict` if the Git repository is empty or unavailable. An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" endpoint to create content and initialize the repository so you can use the Git Database API. Contact {% data variables.contact.contact_support %} if this response status persists. ![git database overview](/assets/images/git-database-overview.png) @@ -33,14 +33,14 @@ It might seem complex, but it's actually pretty simple when you understand the m {% warning %} -**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. +**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. {% endwarning %} -A consuming API needs to explicitly request a pull request to create a _test_ merge commit. A _test_ merge commit is created when you view the pull request in the UI and the "Merge" button is displayed, or when you [get](/v3/pulls/#get-a-pull-request), [create](/v3/pulls/#create-a-pull-request), or [edit](/v3/pulls/#update-a-pull-request) a pull request using the REST API. Without this request, the `merge` Git refs will fall out of date until the next time someone views the pull request. +A consuming API needs to explicitly request a pull request to create a _test_ merge commit. A _test_ merge commit is created when you view the pull request in the UI and the "Merge" button is displayed, or when you [get](/rest/reference/pulls#get-a-pull-request), [create](/rest/reference/pulls#create-a-pull-request), or [edit](/rest/reference/pulls#update-a-pull-request) a pull request using the REST API. Without this request, the `merge` Git refs will fall out of date until the next time someone views the pull request. If you are currently using polling methods that produce outdated `merge` Git refs, then GitHub recommends using the following steps to get the latest changes from the base branch (usually `master`): 1. Receive the pull request webhook. -2. Call [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) to start a background job for creating the merge commit candidate. -3. Poll your repository using [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) to see if the `mergeable` attribute is `true` or `false`. You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. +2. Call [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) to start a background job for creating the merge commit candidate. +3. Poll your repository using [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) to see if the `mergeable` attribute is `true` or `false`. You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. diff --git a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md index 4812d8a36d..9498083852 100644 --- a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md @@ -367,33 +367,33 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]! [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[repos-api]: /v3/repos/ -[repos-api]: /v3/repos/ +[repos-api]: /rest/reference/repos +[repos-api]: /rest/reference/repos [pages]: http://pages.github.com [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore -[issues-api]: /v3/issues/ +[issues-api]: /rest/reference/issues [link-header]: http://www.w3.org/wiki/LinkHeader/ -[conditional-requests]: /v3/#conditional-requests -[rate-limiting]: /v3/#rate-limiting -[rate-limiting]: /v3/#rate-limiting -[users api]: /v3/users/#get-a-user +[conditional-requests]: /rest#conditional-requests +[rate-limiting]: /rest#rate-limiting +[rate-limiting]: /rest#rate-limiting +[users api]: /rest/reference/users#get-a-user [defunkt github]: https://github.com/defunkt [defunkt github]: https://github.com/defunkt [json]: http://en.wikipedia.org/wiki/JSON -[authentication]: /v3/#authentication +[authentication]: /rest#authentication [personal token]: /articles/creating-an-access-token-for-command-line-use [personal token]: /articles/creating-an-access-token-for-command-line-use [tokens settings]: https://github.com/settings/tokens -[pagination]: /v3/#pagination -[get repo]: /v3/repos/#get-a-repository -[create repo]: /v3/repos/#create-a-repository-for-the-authenticated-user -[create issue]: /v3/issues/#create-an-issue +[pagination]: /rest#pagination +[get repo]: /rest/reference/repos#get-a-repository +[create repo]: /rest/reference/repos#create-a-repository-for-the-authenticated-user +[create issue]: /rest/reference/issues#create-an-issue [auth guide]: /guides/basics-of-authentication -[user repos api]: /v3/repos/#list-repositories-for-the-authenticated-user -[other user repos api]: /v3/repos/#list-repositories-for-a-user -[org repos api]: /v3/repos/#list-organization-repositories -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[repo issues api]: /v3/issues/#list-repository-issues +[user repos api]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[other user repos api]: /rest/reference/repos#list-repositories-for-a-user +[org repos api]: /rest/reference/repos#list-organization-repositories +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[repo issues api]: /rest/reference/issues#list-repository-issues [etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/ko-KR/content/rest/guides/rendering-data-as-graphs.md b/translations/ko-KR/content/rest/guides/rendering-data-as-graphs.md index 292181cd58..ff1c44d330 100644 --- a/translations/ko-KR/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/ko-KR/content/rest/guides/rendering-data-as-graphs.md @@ -333,7 +333,7 @@ Et voila! Beautiful rectangles containing your repo languages, with relative pro [Octokit]: https://github.com/octokit/octokit.rb [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ [D3 treemap]: http://bl.ocks.org/mbostock/4063582 -[language API]: /v3/repos/#list-repository-languages -[language API]: /v3/repos/#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs [new oauth application]: https://github.com/settings/applications/new diff --git a/translations/ko-KR/content/rest/guides/traversing-with-pagination.md b/translations/ko-KR/content/rest/guides/traversing-with-pagination.md index e3171400f0..7783f89877 100644 --- a/translations/ko-KR/content/rest/guides/traversing-with-pagination.md +++ b/translations/ko-KR/content/rest/guides/traversing-with-pagination.md @@ -20,9 +20,9 @@ In this guide, we'll make some calls to the {% data variables.product.product_na To start with, it's important to know a few facts about receiving paginated items: -1. Different API calls respond with different defaults. For example, a call to [List public repositories](/v3/repos/#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API provides items in sets of 100 +1. Different API calls respond with different defaults. For example, a call to [List public repositories](/rest/reference/repos#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API provides items in sets of 100 2. You can specify how many items to receive (up to a maximum of 100); but, -3. For technical reasons, not every endpoint behaves the same. For example, [events](/v3/activity/events/) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. +3. For technical reasons, not every endpoint behaves the same. For example, [events](/rest/reference/activity#events) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. Information about pagination is provided in [the Link header](http://tools.ietf.org/html/rfc5988) of an API call. For example, let's make a curl request to the search API, to find out how many times Mozilla projects use the phrase `addClass`: @@ -201,7 +201,7 @@ puts "The prev page link is #{prev_page_href}" puts "The next page link is #{next_page_href}" ``` -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination [octokit.rb]: https://github.com/octokit/octokit.rb [personal token]: /articles/creating-an-access-token-for-command-line-use diff --git a/translations/ko-KR/content/rest/guides/working-with-comments.md b/translations/ko-KR/content/rest/guides/working-with-comments.md index eb56a1f30e..4b48576560 100644 --- a/translations/ko-KR/content/rest/guides/working-with-comments.md +++ b/translations/ko-KR/content/rest/guides/working-with-comments.md @@ -97,8 +97,8 @@ Note that this API call will retrieve single line comments, as well as comments [commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 [sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 [platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments -[issues]: /v3/issues/comments/ +[issues]: /rest/reference/issues#comments [personal token]: /articles/creating-an-access-token-for-command-line-use [octokit.rb]: https://github.com/octokit/octokit.rb -[PR Review API]: /v3/pulls/comments/ -[commit comment API]: /v3/repos/comments/#get-a-commit-comment +[PR Review API]: /rest/reference/pulls#comments +[commit comment API]: /rest/reference/repos#get-a-commit-comment diff --git a/translations/ko-KR/content/rest/overview/api-previews.md b/translations/ko-KR/content/rest/overview/api-previews.md index ad402f9275..904af72be7 100644 --- a/translations/ko-KR/content/rest/overview/api-previews.md +++ b/translations/ko-KR/content/rest/overview/api-previews.md @@ -15,12 +15,12 @@ API previews let you try out new APIs and changes to existing API methods before During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -To access an API preview, you'll need to provide a custom [media type](/v3/media) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. +To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% if currentVersion == "free-pro-team@latest" %} ### Migrations -Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/v3/migrations/) data to {% data variables.product.prodname_ghe_server %}. +Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/rest/reference/migrations) data to {% data variables.product.prodname_ghe_server %}. **Custom media type:** `wyandotte-preview` **Announced:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) {% endif %} @@ -33,13 +33,13 @@ Exercise greater control over [deployments](/rest/reference/repos#deployments) w ### Reactions -Manage [reactions](/v3/reactions/) for commits, issues, and comments. +Manage [reactions](/rest/reference/reactions) for commits, issues, and comments. **Custom media type:** `squirrel-girl-preview` **Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) ### Timeline -Get a [list of events](/v3/issues/timeline/) for an issue or pull request. +Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request. **Custom media type:** `mockingbird-preview` **Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) @@ -61,40 +61,40 @@ Manage [integrations](/early-access/integrations/) through the API. ### Projects -Manage [projects](/v3/projects/). +Manage [projects](/rest/reference/projects). **Custom media type:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) ### Commit search -[Search commits](/v3/search/). +[Search commits](/rest/reference/search). **Custom media type:** `cloak-preview` **Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% if currentVersion == "free-pro-team@latest" %} ### User blocking -Users can [block other users](/v3/users/blocking/). Organizations can [block users](/v3/orgs/blocking/), too. +Users can [block other users](/rest/reference/users#blocking). Organizations can [block users](/rest/reference/orgs#blocking), too. **Custom media type:** `giant-sentry-fist-preview` **Announced:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Update 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Update 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) {% endif %} ### Repository topics -View a list of [repository topics](/articles/about-topics/) in [calls](/v3/repos/) that return repository results. +View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results. **Custom media type:** `mercy-preview` **Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics) ### Codes of conduct -View all [codes of conduct](/v3/codes_of_conduct) or get which code of conduct a repository has currently. +View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently. **Custom media type:** `scarlet-witch-preview` {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### Nested teams -Include nested team content in [team](/v3/teams/) payloads. +Include nested team content in [team](/rest/reference/teams) payloads. **Custom media type:** `hellcat-preview` **Announced:** [2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) @@ -113,7 +113,7 @@ Enables [global webhooks](/rest/reference/enterprise-admin#global-webhooks/) for {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### Repository transfer -Transfer a [repository](/v3/repos/) to an organization or user. +Transfer a [repository](/rest/reference/repos) to an organization or user. **Custom media type:** `nightshade-preview` **Announced:** [2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) {% endif %} @@ -121,27 +121,27 @@ Transfer a [repository](/v3/repos/) to an organization or user. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### Add lock reason -You can now add a reason when you [lock an issue](/v3/issues/#lock-an-issue). +You can now add a reason when you [lock an issue](/rest/reference/issues#lock-an-issue). **Custom media type:** `sailor-v-preview` **Announced:** [2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) {% endif %} ### Require signed commits -You can now use the API to manage the setting for [requiring signed commits on protected branches](/v3/repos/branches). +You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches). **Custom media type:** `zzzax-preview` **Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) ### Require multiple approving reviews -You can now [require multiple approving reviews](/v3/repos/branches) for a pull request using the API. +You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API. **Custom media type:** `luke-cage-preview` **Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.19" %} ### Retrieve hovercard information -Retrieve information from [someone's hovercard](/v3/users/#get-contextual-information-for-a-user). +Retrieve information from [someone's hovercard](/rest/reference/users#get-contextual-information-for-a-user). **Custom media type:** `hagar-preview` **Announced:** [2018-03-21](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) @@ -150,7 +150,7 @@ Retrieve information from [someone's hovercard](/v3/users/#get-contextual-inform {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} ### Check runs and check suites API -Allows a GitHub App to run external checks on a repository's code. See the [Check runs](/v3/checks/runs/) and [Check suites](/v3/checks/suites/) APIs for more details. +Allows a GitHub App to run external checks on a repository's code. See the [Check runs](/rest/reference/checks#runs) and [Check suites](/rest/reference/checks#suites) APIs for more details. **Custom media type:** `antiope-preview` **Announced:** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) {% endif %} @@ -167,7 +167,7 @@ When a {% data variables.product.prodname_ghe_server %} instance is in private m ### Project card details -The REST API responses for [issue events](/v3/issues/events/) and [issue timeline events](/v3/issues/timeline/) now return the `project_card` field for project-related events. +The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events. **Custom media type:** `starfox-preview` **Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) @@ -189,7 +189,7 @@ You can now update the `environment` of a [deployment status](/rest/reference/re ### Repository creation permissions -You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/v3/orgs/#update-an-organization)" for more details. +You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details. **Custom media types:** `surtur-preview` **Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) @@ -202,7 +202,7 @@ You can now provide more information in GitHub for URLs that link to registered {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### Draft pull requests -You can use the Draft Pull Requests API and its [pull request](/v3/pulls/) endpoints to see whether a pull request is in draft state. To learn more about draft pull requests, see "[About pull requests](/articles/about-pull-requests/)". +You can use the Draft Pull Requests API and its [pull request](/rest/reference/pulls) endpoints to see whether a pull request is in draft state. To learn more about draft pull requests, see "[About pull requests](/articles/about-pull-requests/)". **Custom media types:** `shadow-cat-preview` **Announced:** [2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) @@ -216,48 +216,48 @@ You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to ### List branches or pull requests for a commit -You can use two new endpoints in the [Commits API](/v3/repos/commits/) to list branches or pull requests for a commit. +You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit. **Custom media types:** `groot-preview` **Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### Uninstall a GitHub App -Owners of GitHub Apps can now uninstall an app using the [Apps API](/v3/apps/#delete-an-installation-for-the-authenticated-app). +Owners of GitHub Apps can now uninstall an app using the [Apps API](/rest/reference/apps#delete-an-installation-for-the-authenticated-app). **Custom media types:** `gambit-preview` {% endif %} ### Enable or disable vulnerability alerts for a repository -You can use two new endpoints in the [Repos API](/v3/repos/) to enable or disable vulnerability alerts. +You can use two new endpoints in the [Repos API](/rest/reference/repos) to enable or disable vulnerability alerts. **Custom media types:** `dorian-preview` **Announced:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) ### Update a pull request branch -You can use a new endpoint to [update a pull request branch](/v3/pulls/#update-a-pull-request-branch) with changes from the HEAD of the upstream branch. +You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch. **Custom media types:** `lydian-preview` **Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) {% if currentVersion == "free-pro-team@latest" %} ### Enable or disable automated security fixes -You can use a new set of endpoints to [enable and disable automated security fixes](/v3/repos/#enable-automated-security-fixes). +You can use a new set of endpoints to [enable and disable automated security fixes](/rest/reference/repos#enable-automated-security-fixes). **Custom media types:** `london-preview` **Announced:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ### Create and use repository templates -You can use a new endpoint to [Create a repository using a template](/v3/repos/#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/v3/repos/#get-a-repository) to check whether it's set as a template repository using the `is_template` key. +You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key. **Custom media types:** `baptiste-preview` **Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% if currentVersion == "enterprise-server@2.20" %} ### New OAuth Applications API endpoints -You can more securely manage tokens for OAuth Apps by using OAuth tokens as input parameters instead of path parameters with the new [OAuth Applications API](/v3/apps/oauth_applications/) endpoints. +You can more securely manage tokens for OAuth Apps by using OAuth tokens as input parameters instead of path parameters with the new [OAuth Applications API](/rest/reference/apps#oauth-applications) endpoints. **Custom media types:** `doctor-strange-preview` **Announced:** [2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) {% endif %} @@ -265,7 +265,7 @@ You can more securely manage tokens for OAuth Apps by using OAuth tokens as inpu {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ### New visibility parameter for the Repositories API -You can set and retrieve the visibility of a repository in the [Repositories API](/v3/repos/). +You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos). **Custom media types:** `nebula-preview` **Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/ko-KR/content/rest/overview/media-types.md b/translations/ko-KR/content/rest/overview/media-types.md index 9832b0b002..657c5b2f7b 100644 --- a/translations/ko-KR/content/rest/overview/media-types.md +++ b/translations/ko-KR/content/rest/overview/media-types.md @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### Comment body properties -The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/v3/issues/), [issue comments](/v3/issues/comments/), [pull request comments](/v3/pulls/comments/), and the [gist comments](/v3/gists/comments/) APIs all accept these same media types: +The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: #### Raw @@ -85,7 +85,7 @@ Return raw, text and HTML representations. Response will include `body`, `body_t ### Git blob properties -The following media types are allowed when [getting a blob](/v3/git/blobs/#get-a-blob): +The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): #### JSON @@ -102,7 +102,7 @@ Return the raw blob data. ### Commits, commit comparison, and pull requests -The [commits API](/v3/repos/commits/) and [pull requests API](/v3/pulls/) support [diff][git-diff] and [patch][git-patch] formats: +The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: #### 비교(diff) @@ -147,4 +147,4 @@ The gist contents are base64-encoded before being sent out. This can be useful i [gfm]: http://github.github.com/github-flavored-markdown/ [git-diff]: http://git-scm.com/docs/git-diff [git-patch]: http://git-scm.com/docs/git-format-patch -[versions]: /v3/versions +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/ko-KR/content/rest/overview/other-authentication-methods.md b/translations/ko-KR/content/rest/overview/other-authentication-methods.md index 26fe40cff4..afa1fd3815 100644 --- a/translations/ko-KR/content/rest/overview/other-authentication-methods.md +++ b/translations/ko-KR/content/rest/overview/other-authentication-methods.md @@ -59,7 +59,7 @@ For example, if you're accessing the API via [cURL][curl], the following command ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/v3/auth/#working-with-two-factor-authentication). +If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). {% endif %} @@ -124,8 +124,8 @@ $ curl --request POST \ {% endif %} [curl]: http://curl.haxx.se/ -[oauth-auth]: /v3/#authentication +[oauth-auth]: /rest#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -[user-issues]: /v3/issues/#list-issues-assigned-to-the-authenticated-user +[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md index f1192cf231..598d668d10 100644 --- a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md @@ -14,13 +14,13 @@ This describes the resources that make up the official {% data variables.product ### Current version -By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/v3/versions) of the REST API. We encourage you to [explicitly request this version via the `Accept` header](/v3/media/#request-specific-version). +By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API. We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version). Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -For information about GitHub's GraphQL API, see the [v4 documentation](/v4). For information about migrating to GraphQL, see "[Migrating from REST](/v4/guides/migrating-from-rest/)." +For information about GitHub's GraphQL API, see the [v4 documentation](/graphql). For information about migrating to GraphQL, see "[Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql)." {% endif %} @@ -171,7 +171,7 @@ $ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "gith ### GraphQL global node IDs -See the guide on "[Using Global Node IDs](/v4/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. +See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. ### Client errors @@ -262,7 +262,7 @@ You can then expand these templates using something like the [uri_template][uri] ### Pagination -Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/v3/activity/events/) for example. +Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' @@ -287,7 +287,7 @@ The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination inform _The example includes a line break for readability._ -This `Link` response header contains one or more [Hypermedia](/v3/#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). +This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). The possible `rel` values are: @@ -312,7 +312,7 @@ For unauthenticated requests, the rate limit allows for up to 60 requests per ho {% data reusables.enterprise.rate_limit %} -Note that [the Search API has custom rate limit rules](/v3/search/#rate-limit). +Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). The returned HTTP headers of any API request show your current rate limit status: @@ -355,7 +355,7 @@ If you exceed the rate limit, an error response returns: > } ``` -You can [check your rate limit status](/v3/rate_limit) without incurring an API hit. +You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. #### Increasing the unauthenticated rate limit for OAuth applications @@ -586,9 +586,9 @@ Some requests that create new data, such as creating a new commit, allow you to #### Explicitly providing an ISO 8601 timestamp with timezone information -For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/v3/git/commits). +For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits). -These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/v3/git/commits/#example-input) for how these timestamps can be specified. +These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. #### Using the `Time-Zone` header @@ -598,7 +598,7 @@ It is possible to supply a `Time-Zone` header which defines a timezone according $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/v3/repos/contents/) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. +This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. #### Using the last known timezone for the user diff --git a/translations/ko-KR/content/rest/overview/troubleshooting.md b/translations/ko-KR/content/rest/overview/troubleshooting.md index a71f7348c0..719805a046 100644 --- a/translations/ko-KR/content/rest/overview/troubleshooting.md +++ b/translations/ko-KR/content/rest/overview/troubleshooting.md @@ -23,7 +23,7 @@ To troubleshoot, ensure [you're authenticating correctly](/guides/getting-starte Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support pagination. If you're making requests and receiving an incomplete set of results, you're probably only seeing the first page. You'll need to request the remaining pages in order to get more results. -It's important to *not* try and guess the format of the pagination URL. Not every API call uses the same structure. Instead, extract the pagination information from [the Link Header](/v3/#pagination), which is sent with every request. +It's important to *not* try and guess the format of the pagination URL. Not every API call uses the same structure. Instead, extract the pagination information from [the Link Header](/rest#pagination), which is sent with every request. {% if currentVersion == "free-pro-team@latest" %} ### Basic authentication errors diff --git a/translations/ko-KR/content/rest/reference/apps.md b/translations/ko-KR/content/rest/reference/apps.md index 89a955e9c1..455907f161 100644 --- a/translations/ko-KR/content/rest/reference/apps.md +++ b/translations/ko-KR/content/rest/reference/apps.md @@ -18,7 +18,7 @@ When authenticated as a GitHub App, the GitHub Apps API enables you to get high- 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](/v3/apps/installations/) for a list of these endpoints. +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 %} @@ -36,7 +36,7 @@ You can use this API to manage the OAuth tokens an OAuth application uses to acc 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](/v3/orgs/#list-app-installations-for-an-organization)." +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 %} @@ -70,4 +70,4 @@ Be sure to replace stubbed endpoints with production endpoints before deploying {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ko-KR/content/rest/reference/codes-of-conduct.md b/translations/ko-KR/content/rest/reference/codes-of-conduct.md index 16d7e8bda3..50cb78757e 100644 --- a/translations/ko-KR/content/rest/reference/codes-of-conduct.md +++ b/translations/ko-KR/content/rest/reference/codes-of-conduct.md @@ -9,6 +9,6 @@ versions: github-ae: '*' --- -You can use the Codes of Conduct API to retrieve information about a repository's code of conduct. To get a repository's code of conduct, use the "[Get a repository](/v3/repos/#get-a-repository)" endpoint. +You can use the Codes of Conduct API to retrieve information about a repository's code of conduct. To get a repository's code of conduct, use the "[Get a repository](/rest/reference/repos#get-a-repository)" endpoint. {% include rest_operations_at_current_path %} diff --git a/translations/ko-KR/content/rest/reference/enterprise-admin.md b/translations/ko-KR/content/rest/reference/enterprise-admin.md index c97098a6c8..209d878aff 100644 --- a/translations/ko-KR/content/rest/reference/enterprise-admin.md +++ b/translations/ko-KR/content/rest/reference/enterprise-admin.md @@ -86,7 +86,7 @@ The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/v3/auth/#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." {% endnote %} diff --git a/translations/ko-KR/content/rest/reference/git.md b/translations/ko-KR/content/rest/reference/git.md index ef43832bc6..4d3d088ee8 100644 --- a/translations/ko-KR/content/rest/reference/git.md +++ b/translations/ko-KR/content/rest/reference/git.md @@ -34,7 +34,7 @@ For more information, see "[Media types](/rest/overview/media-types)." ## Commits -A Git commit is a snapshot of the hierarchy ([Git tree](/v3/git/trees)) and the contents of the files ([Git blob](/v3/git/blobs)) in a Git repository. These endpoints allow you to read and write [commit objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) to your Git database on {% data variables.product.product_name %}. +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. These endpoints allow you to read and write [commit objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) to your Git database on {% data variables.product.product_name %}. {% for operation in currentRestOperations %} {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} @@ -50,7 +50,7 @@ A Git reference (`git ref`) is just a file that contains a Git commit SHA-1 hash ## Tags -A Git tag is similar to a [Git reference](/v3/git/refs), but the Git commit that it points to never changes. Git tags are helpful when you want to point to specific releases. These endpoints allow you to read and write [tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) to your Git database on {% data variables.product.product_name %}. The Git tags API only supports [annotated tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), not lightweight tags. +A Git tag is similar to a [Git reference](/rest/reference/git#refs), but the Git commit that it points to never changes. Git tags are helpful when you want to point to specific releases. These endpoints allow you to read and write [tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) to your Git database on {% data variables.product.product_name %}. The Git tags API only supports [annotated tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), not lightweight tags. {% for operation in currentRestOperations %} {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %} diff --git a/translations/ko-KR/content/rest/reference/issues.md b/translations/ko-KR/content/rest/reference/issues.md index 7f7f7136cd..7b1ef41218 100644 --- a/translations/ko-KR/content/rest/reference/issues.md +++ b/translations/ko-KR/content/rest/reference/issues.md @@ -33,7 +33,7 @@ For more information about media types, see "[Custom media types](/rest/overview The Issue Comments API supports listing, viewing, editing, and creating comments on issues and pull requests. -Issue Comments use [these custom media types](#custom-media-types). You can read more about the use of media types in the API [here](/v3/media/). +Issue Comments use [these custom media types](#custom-media-types). 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 == 'comments' %}{% include rest_operation %}{% endif %} diff --git a/translations/ko-KR/content/rest/reference/licenses.md b/translations/ko-KR/content/rest/reference/licenses.md index 0ccf586a35..080f5cba43 100644 --- a/translations/ko-KR/content/rest/reference/licenses.md +++ b/translations/ko-KR/content/rest/reference/licenses.md @@ -16,12 +16,12 @@ If a license is matched, the license key and name returned conforms to the [SPDX **Note:** These endpoints will also return a repository's license information: -- [Get a repository](/v3/repos/#get-a-repository) -- [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -- [List organization repositories](/v3/repos/#list-organization-repositories) +- [Get a repository](/rest/reference/repos#get-a-repository) +- [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user) +- [List organization repositories](/rest/reference/repos#list-organization-repositories) - [List forks](/rest/reference/repos#list-forks) - [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user) -- [List team repositories](/v3/teams/#list-team-repositories) +- [List team repositories](/rest/reference/teams#list-team-repositories) {% warning %} diff --git a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md index 85b9c15d64..ded6db8934 100644 --- a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md @@ -19,63 +19,63 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe {% data reusables.apps.metadata-permissions %} -- [`GET /`](/v3/#root-endpoint) -- [`GET /codes_of_conduct`](/v3/codes_of_conduct/#get-all-codes-of-conduct) -- [`GET /codes_of_conduct/:key`](/v3/codes_of_conduct/#get-a-code-of-conduct) -- [`GET /emojis`](/v3/emojis/#emojis) +- [`GET /`](/rest#root-endpoint) +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +- [`GET /emojis`](/rest/reference/emojis#emojis) - [`GET /feeds`](/rest/reference/activity#get-feeds) -- [`GET /licenses`](/v3/licenses/#get-all-commonly-used-licenses) -- [`GET /licenses/:key`](/v3/licenses/#get-a-license) -- [`POST /markdown`](/v3/markdown/#render-a-markdown-document) -- [`POST /markdown/raw`](/v3/markdown/#render-a-markdown-document-in-raw-mode) -- [`GET /meta`](/v3/meta/#meta) -- [`GET /organizations`](/v3/orgs/#list-organizations) -- [`GET /orgs/:org`](/v3/orgs/#get-an-organization) -- [`GET /orgs/:org/projects`](/v3/projects/#list-organization-projects) -- [`GET /orgs/:org/repos`](/v3/repos/#list-organization-repositories) -- [`GET /rate_limit`](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) -- [`GET /repos/:owner/:repo`](/v3/repos/#get-a-repository) +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license) +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +- [`GET /meta`](/rest/reference/meta#meta) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization) +- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects) +- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories) +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/community/profile`](/v3/repos/community/#get-community-profile-metrics) +- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics) {% endif %} -- [`GET /repos/:owner/:repo/contributors`](/v3/repos/#list-repository-contributors) +- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors) - [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks) -- [`GET /repos/:owner/:repo/languages`](/v3/repos/#list-repository-languages) -- [`GET /repos/:owner/:repo/license`](/v3/licenses/#get-the-license-for-a-repository) +- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository) - [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers) -- [`GET /repos/:owner/:repo/stats/code_frequency`](/v3/repos/statistics/#get-the-weekly-commit-activity) -- [`GET /repos/:owner/:repo/stats/commit_activity`](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -- [`GET /repos/:owner/:repo/stats/contributors`](/v3/repos/statistics/#get-all-contributor-commit-activity) -- [`GET /repos/:owner/:repo/stats/participation`](/v3/repos/statistics/#get-the-weekly-commit-count) -- [`GET /repos/:owner/:repo/stats/punch_card`](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity) +- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity) +- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity) +- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count) +- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) - [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers) -- [`GET /repos/:owner/:repo/tags`](/v3/repos/#list-repository-tags) -- [`GET /repos/:owner/:repo/topics`](/v3/repos#get-all-repository-topics) -- [`GET /repositories`](/v3/repos/#list-public-repositories) -- [`GET /user/repos`](/v3/repos/#list-repositories-for-the-authenticated-user) +- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) - [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) - [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) -- [`GET /users`](/v3/users/#list-users) -- [`GET /users/:username`](/v3/users/#get-a-user) -- [`GET /users/:username/followers`](/v3/users/followers/#list-followers-of-a-user) -- [`GET /users/:username/following`](/v3/users/followers/#list-the-people-a-user-follows) -- [`GET /users/:username/following/:target_user`](/v3/users/followers/#check-if-a-user-follows-another-user) -- [`GET /users/:username/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) -- [`GET /users/:username/orgs`](/v3/orgs/#list-organizations-for-a-user) +- [`GET /users`](/rest/reference/users#list-users) +- [`GET /users/:username`](/rest/reference/users#get-a-user) +- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user) - [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) - [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) -- [`GET /users/:username/repos`](/v3/repos/#list-repositories-for-a-user) +- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) _Collaborators_ -- [`GET /repos/:owner/:repo/collaborators`](/v3/repos/collaborators/#list-repository-collaborators) -- [`GET /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) +- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) +- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) _Commit comments_ -- [`GET /repos/:owner/:repo/comments`](/v3/repos/comments/#list-commit-comments-for-a-repository) -- [`GET /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#get-a-commit-comment) -- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-commit-comment) -- [`GET /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#list-commit-comments) +- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) +- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) +- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) _이벤트_ - [`GET /events`](/rest/reference/activity#list-public-events) @@ -86,311 +86,311 @@ _이벤트_ - [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user) _Git_ -- [`GET /gitignore/templates`](/v3/gitignore/#get-all-gitignore-templates) -- [`GET /gitignore/templates/:key`](/v3/gitignore/#get-a-gitignore-template) +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) +- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) _Keys_ -- [`GET /users/:username/keys`](/v3/users/keys/#list-public-keys-for-a-user) +- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) _Organization members_ -- [`GET /orgs/:org/members`](/v3/orgs/members/#list-organization-members) -- [`GET /orgs/:org/members/:username`](/v3/orgs/members/#check-organization-membership-for-a-user) -- [`GET /orgs/:org/public_members`](/v3/orgs/members/#list-public-organization-members) -- [`GET /orgs/:org/public_members/:username`](/v3/orgs/members/#check-public-organization-membership-for-a-user) +- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`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) _검색_ -- [`GET /search/code`](/v3/search/#search-code) -- [`GET /search/commits`](/v3/search/#search-commits) -- [`GET /search/issues`](/v3/search/#search-issues-and-pull-requests) -- [`GET /search/labels`](/v3/search/#search-labels) -- [`GET /search/repositories`](/v3/search/#search-repositories) -- [`GET /search/topics`](/v3/search/#search-topics) -- [`GET /search/users`](/v3/search/#search-users) +- [`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) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "actions" -- [`GET /repos/:owner/:repo/actions/artifacts`](/v3/actions/artifacts/#list-artifacts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} ### Permission on "administration" -- [`POST /orgs/:org/repos`](/v3/repos/#create-an-organization-repository) (:write) -- [`PATCH /repos/:owner/:repo`](/v3/repos/#update-a-repository) (:write) -- [`DELETE /repos/:owner/:repo`](/v3/repos/#delete-a-repository) (:write) +- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) +- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) +- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) (:read) -- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) (:write)git +- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write)git {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#enable-automated-security-fixes) (:write) +- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#disable-automated-security-fixes) (:write) +- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:write) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write) {% endif %} -- [`PUT /repos/:owner/:repo/topics`](/v3/repos/#replace-all-repository-topics) (:write) -- [`POST /repos/:owner/:repo/transfer`](/v3/repos/#transfer-a-repository) (:write) +- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write) +- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#disable-vulnerability-alerts) (:write) +- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write) {% endif %} -- [`PATCH /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#accept-a-repository-invitation) (:write) -- [`DELETE /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#decline-a-repository-invitation) (:write) +- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write) +- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write) _Branches_ -- [`GET /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#get-branch-protection) (:read) -- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#update-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#delete-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#get-admin-branch-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#set-admin-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#delete-admin-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#get-pull-request-review-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#update-pull-request-review-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#delete-pull-request-review-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#get-commit-signature-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#create-commit-signature-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#delete-commit-signature-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#get-status-checks-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#update-status-check-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#remove-status-check-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#get-all-status-check-contexts) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#add-status-check-contexts) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#set-status-check-contexts) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#remove-status-check-contexts) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#get-access-restrictions) (:read) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#delete-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#add-team-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#set-team-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#remove-team-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#add-user-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#set-user-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read) +- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Collaborators_ -- [`PUT /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#add-a-repository-collaborator) (:write) -- [`DELETE /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#remove-a-repository-collaborator) (:write) +- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) +- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) _Invitations_ -- [`GET /repos/:owner/:repo/invitations`](/v3/repos/invitations/#list-repository-invitations) (:read) -- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#update-a-repository-invitation) (:write) -- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#delete-a-repository-invitation) (:write) +- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) +- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) +- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) _Keys_ -- [`GET /repos/:owner/:repo/keys`](/v3/repos/keys/#list-deploy-keys) (:read) -- [`POST /repos/:owner/:repo/keys`](/v3/repos/keys/#create-a-deploy-key) (:write) -- [`GET /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#get-a-deploy-key) (:read) -- [`DELETE /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#delete-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) +- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) +- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) _Teams_ -- [`GET /repos/:owner/:repo/teams`](/v3/repos/#list-repository-teams) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:write) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) +- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) {% if currentVersion == "free-pro-team@latest" %} _Traffic_ -- [`GET /repos/:owner/:repo/traffic/clones`](/v3/repos/traffic/#get-repository-clones) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/paths`](/v3/repos/traffic/#get-top-referral-paths) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/v3/repos/traffic/#get-top-referral-sources) (:read) -- [`GET /repos/:owner/:repo/traffic/views`](/v3/repos/traffic/#get-page-views) (:read) +- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) +- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "blocking" -- [`GET /user/blocks`](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) (:read) -- [`GET /user/blocks/:username`](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) -- [`PUT /user/blocks/:username`](/v3/users/blocking/#block-a-user) (:write) -- [`DELETE /user/blocks/:username`](/v3/users/blocking/#unblock-a-user) (:write) +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) +- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) +- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (:write) +- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) {% endif %} ### Permission on "checks" -- [`POST /repos/:owner/:repo/check-runs`](/v3/checks/runs/#create-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#update-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`POST /repos/:owner/:repo/check-suites`](/v3/checks/suites/#create-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/v3/checks/suites/#update-repository-preferences-for-check-suites) (:write) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) +- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (:write) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) ### Permission on "contents" -- [`GET /repos/:owner/:repo/:archive_format/:ref`](/v3/repos/contents/#download-a-repository-archive) (:read) +- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:write) +- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#get-a-repository-secret) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) +- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) +- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/commits`](/v3/repos/commits/#list-commits) (:read) -- [`GET /repos/:owner/:repo/commits/:sha`](/v3/repos/commits/#get-a-commit) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/community/code_of_conduct`](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/compare/:base...:head`](/v3/repos/commits/#compare-two-commits) (:read) -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read) +- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`POST /repos/:owner/:repo/dispatches`](/v3/repos/#create-a-repository-dispatch-event) (:write) +- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:read) -- [`POST /repos/:owner/:repo/merges`](/v3/repos/merging/#merge-a-branch) (:write) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#merge-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/v3/repos/contents/#get-a-repository-readme) (:read) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read) +- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read) _Branches_ -- [`GET /repos/:owner/:repo/branches`](/v3/repos/branches/#list-branches) (:read) -- [`GET /repos/:owner/:repo/branches/:branch`](/v3/repos/branches/#get-a-branch) (:read) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#list-apps-with-access-to-the-protected-branch) (:write) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#add-app-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#set-app-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read) +- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Commit comments_ -- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#update-a-commit-comment) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#delete-a-commit-comment) (:write) -- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-commit-comment) (:read) -- [`POST /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#create-a-commit-comment) (:read) +- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) +- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) +- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read) _Git_ -- [`POST /repos/:owner/:repo/git/blobs`](/v3/git/blobs/#create-a-blob) (:write) -- [`GET /repos/:owner/:repo/git/blobs/:sha`](/v3/git/blobs/#get-a-blob) (:read) -- [`POST /repos/:owner/:repo/git/commits`](/v3/git/commits/#create-a-commit) (:write) -- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/v3/git/commits/#get-a-commit) (:read) -- [`POST /repos/:owner/:repo/git/refs`](/v3/git/refs/#create-a-reference) (:write) -- [`GET /repos/:owner/:repo/git/ref/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/v3/git/refs/#list-matching-references) (:read) -- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#update-a-reference) (:write) -- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#delete-a-reference) (:write) -- [`POST /repos/:owner/:repo/git/tags`](/v3/git/tags/#create-a-tag-object) (:write) -- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/v3/git/tags/#get-a-tag) (:read) -- [`POST /repos/:owner/:repo/git/trees`](/v3/git/trees/#create-a-tree) (:write) -- [`GET /repos/:owner/:repo/git/trees/:sha`](/v3/git/trees/#get-a-tree) (:read) +- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write) +- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (:read) +- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (:write) +- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (:read) +- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (:write) +- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (:read) +- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (:read) +- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (:write) +- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (:write) +- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (:write) +- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (:read) +- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (:write) +- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) {% if currentVersion == "free-pro-team@latest" %} _가져오기_ -- [`GET /repos/:owner/:repo/import`](/v3/migrations/source_imports/#get-an-import-status) (:read) -- [`PUT /repos/:owner/:repo/import`](/v3/migrations/source_imports/#start-an-import) (:write) -- [`PATCH /repos/:owner/:repo/import`](/v3/migrations/source_imports/#update-an-import) (:write) -- [`DELETE /repos/:owner/:repo/import`](/v3/migrations/source_imports/#cancel-an-import) (:write) -- [`GET /repos/:owner/:repo/import/authors`](/v3/migrations/source_imports/#get-commit-authors) (:read) -- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/v3/migrations/source_imports/#map-a-commit-author) (:write) -- [`GET /repos/:owner/:repo/import/large_files`](/v3/migrations/source_imports/#get-large-files) (:read) -- [`PATCH /repos/:owner/:repo/import/lfs`](/v3/migrations/source_imports/#update-git-lfs-preference) (:write) +- [`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) +- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (:write) +- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (:read) +- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (:write) +- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (:read) +- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) {% endif %} _Reactions_ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% endif %} _출시_ - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read) @@ -419,195 +419,195 @@ _출시_ ### Permission on "emails" {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /user/email/visibility`](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) (:write) +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) {% endif %} -- [`GET /user/emails`](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) (:read) -- [`POST /user/emails`](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) (:write) -- [`DELETE /user/emails`](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) (:write) -- [`GET /user/public_emails`](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) (:read) +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (:write) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (:write) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) {% endif %} ### Permission on "followers" -- [`GET /user/followers`](/v3/users/followers/#list-followers-of-a-user) (:read) -- [`GET /user/following`](/v3/users/followers/#list-the-people-a-user-follows) (:read) -- [`GET /user/following/:username`](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) (:read) -- [`PUT /user/following/:username`](/v3/users/followers/#follow-a-user) (:write) -- [`DELETE /user/following/:username`](/v3/users/followers/#unfollow-a-user) (:write) +- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) +- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) +- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (:read) +- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) +- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) ### Permission on "gpg keys" -- [`GET /user/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) (:read) -- [`POST /user/gpg_keys`](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) (:write) -- [`GET /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) (:read) -- [`DELETE /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (:read) +- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) ### Permission on "issues" -Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues. +Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues. -- [`GET /repos/:owner/:repo/issues`](/v3/issues/#list-repository-issues) (:read) -- [`POST /repos/:owner/:repo/issues`](/v3/issues/#create-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#get-an-issue) (:read) -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) +- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (:read) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) _Assignees_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _이벤트_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [Get an issue event](/v3/issues/events/#get-an-issue-event) (:read) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [Get an issue event](/rest/reference/issues#get-an-issue-event) (:read) _Labels_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Milestones_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reactions_ -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} ### Permission on "keys" _Keys_ -- [`GET /user/keys`](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) (:read) -- [`POST /user/keys`](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) (:write) -- [`GET /user/keys/:key_id`](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) (:read) -- [`DELETE /user/keys/:key_id`](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) +- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) ### Permission on "members" {% if currentVersion == "free-pro-team@latest" %} -- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#list-idp-groups-for-a-team) (:write) +- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#create-or-update-idp-group-connections) (:write) +- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write) {% endif %} -- [`GET /orgs/:org/outside_collaborators`](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) (:read) -- [`PUT /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) (:write) -- [`DELETE /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) (:write) +- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read) +- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write) +- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/team-sync/groups`](/v3/teams/team_sync/#list-idp-groups-for-an-organization) (:write) +- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write) {% endif %} -- [`GET /orgs/:org/team/:team_id`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users`](/v3/scim/#list-scim-provisioned-identities) (:read) +- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /scim/v2/orgs/:org/Users`](/v3/scim/#provision-and-invite-a-scim-user) (:write) +- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#get-scim-provisioning-information-for-a-user) (:read) +- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#set-scim-information-for-a-provisioned-user) (:write) +- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#update-an-attribute-for-a-scim-user) (:write) +- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#delete-a-scim-user-from-an-organization) (:write) +- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} _Invitations_ -- [`GET /orgs/:org/invitations`](/v3/orgs/members/#list-pending-organization-invitations) (:read) -- [`POST /orgs/:org/invitations`](/v3/orgs/members/#create-an-organization-invitation) (:write) -- [`GET /orgs/:org/invitations/:invitation_id/teams`](/v3/orgs/members/#list-organization-invitation-teams) (:read) -- [`GET /teams/:team_id/invitations`](/v3/teams/members/#list-pending-team-invitations) (:read) +- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) +- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) +- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) +- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) {% endif %} _Organization members_ -- [`DELETE /orgs/:org/members/:username`](/v3/orgs/members/#remove-an-organization-member) (:write) -- [`GET /orgs/:org/memberships/:username`](/v3/orgs/members/#get-organization-membership-for-a-user) (:read) -- [`PUT /orgs/:org/memberships/:username`](/v3/orgs/members/#set-organization-membership-for-a-user) (:write) -- [`DELETE /orgs/:org/memberships/:username`](/v3/orgs/members/#remove-organization-membership-for-a-user) (:write) -- [`PUT /orgs/:org/public_members/:username`](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) (:write) -- [`DELETE /orgs/:org/public_members/:username`](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) (:write) -- [`GET /user/memberships/orgs`](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) (:read) -- [`GET /user/memberships/orgs/:org`](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) (:read) -- [`PATCH /user/memberships/orgs/:org`](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) +- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) +- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) +- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (:write) +- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (:write) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (:read) +- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) +- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) _Team members_ -- [`GET /teams/:team_id/members`](/v3/teams/members/#list-team-members) (:read) -- [`GET /teams/:team_id/memberships/:username`](/v3/teams/members/#get-team-membership-for-a-user) (:read) -- [`PUT /teams/:team_id/memberships/:username`](/v3/teams/members/#add-or-update-team-membership-for-a-user) (:write) -- [`DELETE /teams/:team_id/memberships/:username`](/v3/teams/members/#remove-team-membership-for-a-user) (:write) +- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) +- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) +- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) +- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) _Teams_ -- [`GET /orgs/:org/teams`](/v3/teams/#list-teams) (:read) -- [`POST /orgs/:org/teams`](/v3/teams/#create-a-team) (:write) -- [`GET /orgs/:org/teams/:team_slug`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) +- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) +- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -- [`GET /teams/:team_id`](/v3/teams/#get-a-team) (:read) +- [`GET /teams/:team_id`](/rest/reference/teams#get-a-team) (:read) {% endif %} -- [`PATCH /teams/:team_id`](/v3/teams/#update-a-team) (:write) -- [`DELETE /teams/:team_id`](/v3/teams/#delete-a-team) (:write) +- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write) +- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`GET /teams/:team_id/projects`](/v3/teams/#list-team-projects) (:read) -- [`GET /teams/:team_id/projects/:project_id`](/v3/teams/#check-team-permissions-for-a-project) (:read) -- [`PUT /teams/:team_id/projects/:project_id`](/v3/teams/#add-or-update-team-project-permissions) (:read) -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read) +- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read) +- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% endif %} -- [`GET /teams/:team_id/repos`](/v3/teams/#list-team-repositories) (:read) -- [`GET /teams/:team_id/repos/:owner/:repo`](/v3/teams/#check-team-permissions-for-a-repository) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:read) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) -- [`GET /teams/:team_id/teams`](/v3/teams/#list-child-teams) (:read) +- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read) +- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) +- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) ### Permission on "organization administration" -- [`PATCH /orgs/:org`](/v3/orgs/#update-an-organization) (:write) +- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/interaction-limits`](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) (:read) +- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /orgs/:org/interaction-limits`](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) (:write) +- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /orgs/:org/interaction-limits`](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) (:write) +- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) {% endif %} ### Permission on "organization hooks" @@ -620,7 +620,7 @@ _Teams_ - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write) _Teams_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permission on "organization pre receive hooks" @@ -633,31 +633,31 @@ _Teams_ ### Permission on "organization projects" -- [`POST /orgs/:org/projects`](/v3/projects/#create-an-organization-project) (:write) -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) +- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "organization user blocking" -- [`GET /orgs/:org/blocks`](/v3/orgs/blocking/#list-users-blocked-by-an-organization) (:read) -- [`GET /orgs/:org/blocks/:username`](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) (:read) -- [`PUT /orgs/:org/blocks/:username`](/v3/orgs/blocking/#block-a-user-from-an-organization) (:write) -- [`DELETE /orgs/:org/blocks/:username`](/v3/orgs/blocking/#unblock-a-user-from-an-organization) (:write) +- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) +- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) +- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (:write) +- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) {% endif %} ### Permission on "pages" @@ -675,99 +675,99 @@ _Teams_ Pull requests and issues are closely related.. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests. -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls`](/v3/pulls/#list-pull-requests) (:read) -- [`POST /repos/:owner/:repo/pulls`](/v3/pulls/#create-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#get-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#update-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#list-review-comments-on-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/v3/pulls/#list-commits-on-a-pull-request) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/v3/pulls/#list-pull-requests-files) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#check-if-a-pull-request-has-been-merged) (:read) -- [`GET /repos/:owner/:repo/pulls/comments`](/v3/pulls/comments/#list-review-comments-in-a-repository) (:read) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) (:write) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (:read) +- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (:read) +- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (:read) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) _Assignees_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _이벤트_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [`GET /repos/:owner/:repo/issues/events/:event_id`](/v3/issues/events/#get-an-issue-event) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) _Labels_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Milestones_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reactions_ -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) (:read) -- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) (:write) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read) +- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} _Requested reviewers_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) _Reviews_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#list-reviews-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#create-a-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#get-a-review-for-a-pull-request) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#update-a-review-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#delete-a-pending-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) ### Permission on "repository hooks" -- [`GET /repos/:owner/:repo/hooks`](/v3/repos/hooks/#list-repository-webhooks) (:read) -- [`POST /repos/:owner/:repo/hooks`](/v3/repos/hooks/#create-a-repository-webhook) (:write) -- [`GET /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#get-a-repository-webhook) (:read) -- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#update-a-repository-webhook) (:write) -- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#delete-a-repository-webhook) (:write) -- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/v3/repos/hooks/#ping-a-repository-webhook) (:read) -- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/v3/repos/hooks/#test-the-push-repository-webhook) (:read) +- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) +- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) +- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read) +- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write) +- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write) +- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read) +- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permission on "repository pre receive hooks" @@ -780,70 +780,70 @@ _Reviews_ ### Permission on "repository projects" -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) -- [`GET /repos/:owner/:repo/projects`](/v3/projects/#list-repository-projects) (:read) -- [`POST /repos/:owner/:repo/projects`](/v3/projects/#create-a-repository-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) +- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) +- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) _Teams_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "secrets" -* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:read) -* [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:read) -* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#get-a-repository-secret) (:read) -* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -* [`GET /orgs/:org/actions/secrets/public-key`](/v3/actions/secrets/#get-an-organization-public-key) (:read) -* [`GET /orgs/:org/actions/secrets`](/v3/actions/secrets/#list-organization-secrets) (:read) -* [`GET /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#get-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-an-organization-secret) (:write) -* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) (:write) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-an-organization-secret) (:write) +* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) +* [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) +* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (:read) +* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (:write) +* [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (:read) +* [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (:read) +* [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (:write) +* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (:write) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "security events" -- [`GET /repos/:owner/:repo/code-scanning/alerts`](/v3/code-scanning/#list-code-scanning-alerts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/v3/code-scanning/#get-a-code-scanning-alert) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "self-hosted runners" -- [`GET /orgs/:org/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) (:write) -- [`GET /orgs/:org/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) (:read) -- [`GET /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) (:write) -- [`DELETE /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) +- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) +- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) {% endif %} ### Permission on "single file" -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -- [`PUT /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#create-or-update-file-contents) (:write) -- [`DELETE /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#delete-a-file) (:write) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) +- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) ### Permission on "starring" @@ -853,23 +853,23 @@ _Teams_ ### Permission on "statuses" -- [`GET /repos/:owner/:repo/commits/:ref/status`](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/v3/repos/statuses/#list-commit-statuses-for-a-reference) (:read) -- [`POST /repos/:owner/:repo/statuses/:sha`](/v3/repos/statuses/#create-a-commit-status) (:write) +- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) +- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) ### Permission on "team discussions" -- [`GET /teams/:team_id/discussions`](/v3/teams/discussions/#list-discussions) (:read) -- [`POST /teams/:team_id/discussions`](/v3/teams/discussions/#create-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#get-a-discussion) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#update-a-discussion) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#delete-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#list-discussion-comments) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#create-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#get-a-discussion-comment) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#update-a-discussion-comment) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#delete-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion-comment) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion) (:write) +- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) +- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/ko-KR/content/rest/reference/pulls.md b/translations/ko-KR/content/rest/reference/pulls.md index bae28ba4fb..9fc99c70ca 100644 --- a/translations/ko-KR/content/rest/reference/pulls.md +++ b/translations/ko-KR/content/rest/reference/pulls.md @@ -10,7 +10,7 @@ versions: 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](/v3/issues). +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 @@ -33,16 +33,16 @@ If a diff is corrupt, contact {% data variables.contact.contact_support %}. Incl Pull Requests have these possible link relations: -| 이름 | 설명 | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -| `self` | The API location of this Pull Request. | -| `html` | The HTML location of this Pull Request. | -| `이슈` | The API location of this Pull Request's [Issue](/v3/issues/). | -| `comments` | The API location of this Pull Request's [Issue comments](/v3/issues/comments/). | -| `review_comments` | The API location of this Pull Request's [Review comments](/v3/pulls/comments/). | -| `review_comment` | The [URL template](/v3/#hypermedia) to construct the API location for a [Review comment](/v3/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](/v3/repos/statuses/), which are the statuses of its `head` branch. | +| 이름 | 설명 | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `self` | The API location of this Pull Request. | +| `html` | The HTML location of this Pull Request. | +| `이슈` | 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/repos#statuses), which are the statuses of its `head` branch. | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/ko-KR/content/rest/reference/rate-limit.md b/translations/ko-KR/content/rest/reference/rate-limit.md index b81dff0260..7c33a37028 100644 --- a/translations/ko-KR/content/rest/reference/rate-limit.md +++ b/translations/ko-KR/content/rest/reference/rate-limit.md @@ -13,18 +13,18 @@ The REST API overview documentation describes the [rate limit rules](/rest/overv ### Understanding your rate limit status -The Search API has a [custom rate limit](/v3/search/#rate-limit), separate from the rate limit governing the rest of the REST API. The GraphQL API also has a [custom rate limit](/v4/guides/resource-limitations/#rate-limit) that is separate from and calculated differently than rate limits in the REST API. +The Search API has a [custom rate limit](/rest/reference/search#rate-limit), separate from the rate limit governing the rest of the REST API. The GraphQL API also has a [custom rate limit](/graphql/overview/resource-limitations#rate-limit) that is separate from and calculated differently than rate limits in the REST API. For these reasons, the Rate Limit API response categorizes your rate limit. Under `resources`, you'll see four objects: * The `core` object provides your rate limit status for all non-search-related resources in the REST API. -* The `search` object provides your rate limit status for the [Search API](/v3/search/). +* The `search` object provides your rate limit status for the [Search API](/rest/reference/search). -* The `graphql` object provides your rate limit status for the [GraphQL API](/v4/). +* The `graphql` object provides your rate limit status for the [GraphQL API](/graphql). * The `integration_manifest` object provides your rate limit status for the [GitHub App Manifest code conversion](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration) endpoint. -For more information on the headers and values in the rate limit response, see "[Rate limiting](/v3/#rate-limiting)." +For more information on the headers and values in the rate limit response, see "[Rate limiting](/rest#rate-limiting)." {% include rest_operations_at_current_path %} diff --git a/translations/ko-KR/content/rest/reference/repos.md b/translations/ko-KR/content/rest/reference/repos.md index b32e720b6d..538bc10391 100644 --- a/translations/ko-KR/content/rest/reference/repos.md +++ b/translations/ko-KR/content/rest/reference/repos.md @@ -29,7 +29,7 @@ versions: ### Custom media types for commit comments -These are the supported media types for commit comments. You can read more about the use of media types in the API [here](/v3/media/). +These are the supported media types for commit comments. You can read more about the use of media types in the API [here](/rest/overview/media-types). application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json @@ -65,7 +65,7 @@ These API endpoints let you create, modify, and delete Base64 encoded content in ### Custom media types for repository contents -[READMEs](/v3/repos/contents/#get-a-repository-readme), [files](/v3/repos/contents/#get-repository-content), and [symlinks](/v3/repos/contents/#get-repository-content) support the following custom media types: +[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 @@ -74,13 +74,13 @@ 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](/v3/repos/contents/#get-repository-content) support the following custom media type: +[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](/v3/media/). +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 %} diff --git a/translations/ko-KR/content/rest/reference/scim.md b/translations/ko-KR/content/rest/reference/scim.md index 0b2c566424..edd3c7a5d7 100644 --- a/translations/ko-KR/content/rest/reference/scim.md +++ b/translations/ko-KR/content/rest/reference/scim.md @@ -12,7 +12,7 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/v3/auth/#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." {% endnote %} diff --git a/translations/ko-KR/content/rest/reference/search.md b/translations/ko-KR/content/rest/reference/search.md index 9becc9da47..d79dba3c09 100644 --- a/translations/ko-KR/content/rest/reference/search.md +++ b/translations/ko-KR/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**. -You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/v3/search/#constructing-a-search-query)." +You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." ### Ranking search results @@ -18,7 +18,7 @@ Unless another sort option is provided as a query parameter, results are sorted ### Rate limit -The Search API has a custom rate limit. For requests using [Basic Authentication](/v3/#authentication), [OAuth](/v3/#authentication), or [client ID and secret](/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute. +The Search API has a custom rate limit. For requests using [Basic Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute. {% data reusables.enterprise.rate_limit %} diff --git a/translations/ko-KR/content/rest/reference/teams.md b/translations/ko-KR/content/rest/reference/teams.md index a39f3abce4..7223e949ec 100644 --- a/translations/ko-KR/content/rest/reference/teams.md +++ b/translations/ko-KR/content/rest/reference/teams.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -This API is only available to authenticated members of the team's [organization](/v3/orgs). OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} generates the team's `slug` from the team `name`. +This API is only available to authenticated members of the team's [organization](/rest/reference/orgs). OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} generates the team's `slug` from the team `name`. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -16,7 +16,7 @@ This API is only available to authenticated members of the team's [organization] ## Discussions -The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/v3/orgs) can create and read public discussion posts. For more details, see "[About team discussions](/articles/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/v3/teams/discussion_comments). This API is only available to authenticated members of the team's organization. +The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](/articles/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -24,7 +24,7 @@ The team discussions API allows you to get, create, edit, and delete discussion ## Discussion comments -The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/v3/teams/discussions) post. Any member of the team's [organization](/v3/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/articles/about-team-discussions/)." This API is only available to authenticated members of the team's organization. +The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/articles/about-team-discussions/)." This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -58,4 +58,4 @@ You can manage GitHub team members through your IdP with team synchronization. T {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ko-KR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/ko-KR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 10f9989a12..3d4deaabeb 100644 --- a/translations/ko-KR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/ko-KR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.' reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/ko-KR/data/graphql/graphql_upcoming_changes.public.yml b/translations/ko-KR/data/graphql/graphql_upcoming_changes.public.yml index f12ecd0331..2b5e3ec561 100644 --- a/translations/ko-KR/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ko-KR/data/graphql/graphql_upcoming_changes.public.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.' reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/ko-KR/data/reusables/apps/app-ruby-guides.md b/translations/ko-KR/data/reusables/apps/app-ruby-guides.md index fe649b0de5..19a860b9e9 100644 --- a/translations/ko-KR/data/reusables/apps/app-ruby-guides.md +++ b/translations/ko-KR/data/reusables/apps/app-ruby-guides.md @@ -1,5 +1,5 @@ {% note %} -**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/v3/libraries/). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. +**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/rest/overview/libraries). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. {% endnote %} diff --git a/translations/ko-KR/data/reusables/apps/checks-availability.md b/translations/ko-KR/data/reusables/apps/checks-availability.md index 7360c3112d..441b6cc35b 100644 --- a/translations/ko-KR/data/reusables/apps/checks-availability.md +++ b/translations/ko-KR/data/reusables/apps/checks-availability.md @@ -1 +1 @@ -Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/v3/repos/statuses/). +Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/rest/reference/repos#statuses). diff --git a/translations/ko-KR/data/reusables/apps/deletes_ssh_keys.md b/translations/ko-KR/data/reusables/apps/deletes_ssh_keys.md index 6b5e91b011..c1a3e41f10 100644 --- a/translations/ko-KR/data/reusables/apps/deletes_ssh_keys.md +++ b/translations/ko-KR/data/reusables/apps/deletes_ssh_keys.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/v3/guides/managing-deploy-keys/#deploy-keys). +**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys). {% endwarning %} diff --git a/translations/ko-KR/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/ko-KR/data/reusables/apps/deprecating_auth_with_query_parameters.md index 07fd7f5941..26ea19355f 100644 --- a/translations/ko-KR/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/ko-KR/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/v3/auth/#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). +**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} diff --git a/translations/ko-KR/data/reusables/apps/deprecating_github_services_ghe.md b/translations/ko-KR/data/reusables/apps/deprecating_github_services_ghe.md index 72e5d399fb..b44e17370a 100644 --- a/translations/ko-KR/data/reusables/apps/deprecating_github_services_ghe.md +++ b/translations/ko-KR/data/reusables/apps/deprecating_github_services_ghe.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} {% note %} -**Note:** GitHub Enterprise release 2.17 and higher no longer allows admins to install new GitHub Services, and existing services will stop working in GitHub Enterprise release 2.20 and higher. You can use the [Replacing GitHub Services guide](/v3/guides/replacing-github-services) to help you update your services to webhooks. +**Note:** GitHub Enterprise release 2.17 and higher no longer allows admins to install new GitHub Services, and existing services will stop working in GitHub Enterprise release 2.20 and higher. You can use the [Replacing GitHub Services guide](/developers/overview/replacing-github-services) to help you update your services to webhooks. {% endnote %} {% endif %} diff --git a/translations/ko-KR/data/reusables/code-scanning/example-configuration-files.md b/translations/ko-KR/data/reusables/code-scanning/example-configuration-files.md index 940d94e8d4..f429bb12cf 100644 --- a/translations/ko-KR/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/ko-KR/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), and to exclude the _node_modules_ directory (also relative to the root), as well as any file whose name ends in _.test.js_. +The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. ``` yaml name: "My {% data variables.product.prodname_codeql %} config" @@ -24,9 +24,9 @@ queries: - name: Use a query suite file (run queries from a query suite in this repo) uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls -paths-ignore: - - node_modules - - '**/*.test.js' paths: - src +paths-ignore: + - src/node_modules + - '**/*.test.js' ``` diff --git a/translations/ko-KR/data/reusables/github-actions/matrix-variable-example.md b/translations/ko-KR/data/reusables/github-actions/matrix-variable-example.md new file mode 100644 index 0000000000..ce6e9d6d24 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/matrix-variable-example.md @@ -0,0 +1,26 @@ +In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: + +{% raw %} +```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - node-version: 10.x + site: "prod" + datacenter: "site-a" + - node-version: 12.x + site: "dev" + datacenter: "site-b" + steps: + - name: Echo site details + env: + SITE: ${{ matrix.site }} + DATACENTER: ${{ matrix.datacenter }} + run: echo $SITE $DATACENTER +``` +{% endraw %} diff --git a/translations/ko-KR/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/ko-KR/data/reusables/github-actions/permissions-statement-secrets-api.md index 0e62bb6498..53142b325e 100644 --- a/translations/ko-KR/data/reusables/github-actions/permissions-statement-secrets-api.md +++ b/translations/ko-KR/data/reusables/github-actions/permissions-statement-secrets-api.md @@ -1 +1 @@ -To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/v3/actions/secrets/)." +To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)." diff --git a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 9ac93498fa..0cb603cd97 100644 --- a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,12 +1,12 @@ -1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. - ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. {% warning %} - **Warning** + **경고** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} - diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 8cb48608dd..125c285ead 100644 --- a/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/v3/teams/team_sync/)." +After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/ko-KR/data/reusables/issue-events/issue-event-common-properties.md b/translations/ko-KR/data/reusables/issue-events/issue-event-common-properties.md index 5288291a7c..93fe2705a6 100644 --- a/translations/ko-KR/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/ko-KR/data/reusables/issue-events/issue-event-common-properties.md @@ -1,10 +1,10 @@ -| 이름 | 유형 | 설명 | -| ------------ | --------- | -------------------------------------------------------------------- | -| `id` | `integer` | The unique identifier of the event. | -| `node_id` | `문자열` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `문자열` | The REST API URL for fetching the event. | -| `actor` | `개체` | The person who generated the event. | -| `event` | `문자열` | Identifies the actual type of event that occurred. | -| `commit_id` | `문자열` | The SHA of the commit that referenced this issue. | -| `commit_url` | `문자열` | The GitHub REST API link to the commit that referenced this issue. | -| `created_at` | `문자열` | The timestamp indicating when the event occurred. | +| 이름 | 유형 | 설명 | +| ------------ | --------- | ------------------------------------------------------------------------- | +| `id` | `integer` | The unique identifier of the event. | +| `node_id` | `문자열` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `문자열` | The REST API URL for fetching the event. | +| `actor` | `개체` | The person who generated the event. | +| `event` | `문자열` | Identifies the actual type of event that occurred. | +| `commit_id` | `문자열` | The SHA of the commit that referenced this issue. | +| `commit_url` | `문자열` | The GitHub REST API link to the commit that referenced this issue. | +| `created_at` | `문자열` | The timestamp indicating when the event occurred. | diff --git a/translations/ko-KR/data/reusables/pre-release-program/corsair-preview.md b/translations/ko-KR/data/reusables/pre-release-program/corsair-preview.md index d5131c62d3..7724c1caaf 100644 --- a/translations/ko-KR/data/reusables/pre-release-program/corsair-preview.md +++ b/translations/ko-KR/data/reusables/pre-release-program/corsair-preview.md @@ -1,6 +1,6 @@ {% note %} -**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.corsair-preview+json diff --git a/translations/ko-KR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/ko-KR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md index 6bf0fb2ed4..7bed2bb577 100644 --- a/translations/ko-KR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md +++ b/translations/ko-KR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Note:** Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)." For more information, see "[Expiring user-to-server access tokens for GitHub Apps](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)." diff --git a/translations/ko-KR/data/reusables/pre-release-program/fury-pre-release.md b/translations/ko-KR/data/reusables/pre-release-program/fury-pre-release.md index 25b74a97ea..adf434c97e 100644 --- a/translations/ko-KR/data/reusables/pre-release-program/fury-pre-release.md +++ b/translations/ko-KR/data/reusables/pre-release-program/fury-pre-release.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} {% note %} -**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.fury-preview+json diff --git a/translations/ko-KR/data/reusables/pre-release-program/machine-man-preview.md b/translations/ko-KR/data/reusables/pre-release-program/machine-man-preview.md index d18399b663..82549b4331 100644 --- a/translations/ko-KR/data/reusables/pre-release-program/machine-man-preview.md +++ b/translations/ko-KR/data/reusables/pre-release-program/machine-man-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** To access the API with your GitHub App, you must provide a custom [media type](/v3/media) in the `Accept` Header for your requests. +**Note:** To access the API with your GitHub App, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` Header for your requests. `application/vnd.github.machine-man-preview+json` diff --git a/translations/ko-KR/data/reusables/pre-release-program/sailor-v-preview.md b/translations/ko-KR/data/reusables/pre-release-program/sailor-v-preview.md index fcf2e98e68..ac0d210355 100644 --- a/translations/ko-KR/data/reusables/pre-release-program/sailor-v-preview.md +++ b/translations/ko-KR/data/reusables/pre-release-program/sailor-v-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.sailor-v-preview+json diff --git a/translations/ko-KR/data/reusables/pre-release-program/starfox-preview.md b/translations/ko-KR/data/reusables/pre-release-program/starfox-preview.md index 5de305adb6..138455a9eb 100644 --- a/translations/ko-KR/data/reusables/pre-release-program/starfox-preview.md +++ b/translations/ko-KR/data/reusables/pre-release-program/starfox-preview.md @@ -2,7 +2,7 @@ **Note:** Project card details are now shown in REST API responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events). -To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/v3/media) in the `Accept` header: +To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.starfox-preview+json diff --git a/translations/ko-KR/data/reusables/repositories/deploy-keys.md b/translations/ko-KR/data/reusables/repositories/deploy-keys.md index ae039b459e..3f3948dc84 100644 --- a/translations/ko-KR/data/reusables/repositories/deploy-keys.md +++ b/translations/ko-KR/data/reusables/repositories/deploy-keys.md @@ -1 +1 @@ -You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/v3/guides/delivering-deployments/)." +You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)." diff --git a/translations/ko-KR/data/reusables/webhooks/check_run_properties.md b/translations/ko-KR/data/reusables/webhooks/check_run_properties.md index 2d6c8d09ee..cf76f36f55 100644 --- a/translations/ko-KR/data/reusables/webhooks/check_run_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/check_run_properties.md @@ -1,7 +1,7 @@ | 키 | 유형 | 설명 | | --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `동작` | `문자열` | The action performed. Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/v3/checks/runs/#check-runs-and-requested-actions)."
| -| `check_run` | `개체` | The [check_run](/v3/checks/runs/#get-a-check-run). | +| `동작` | `문자열` | The action performed. Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `check_run` | `개체` | The [check_run](/rest/reference/checks#get-a-check-run). | | `check_run[status]` | `문자열` | The current status of the check run. Can be `queued`, `in_progress`, or `completed`. | | `check_run[conclusion]` | `문자열` | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. | | `check_run[name]` | `문자열` | The name of the check run. | diff --git a/translations/ko-KR/data/reusables/webhooks/check_run_short_desc.md b/translations/ko-KR/data/reusables/webhooks/check_run_short_desc.md index 19fd0846b8..15cbbb7936 100644 --- a/translations/ko-KR/data/reusables/webhooks/check_run_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/check_run_short_desc.md @@ -1 +1 @@ -Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/v3/checks/runs/)" REST API. +Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/rest/reference/checks#runs)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/check_suite_properties.md b/translations/ko-KR/data/reusables/webhooks/check_suite_properties.md index fcc666d069..917cefa668 100644 --- a/translations/ko-KR/data/reusables/webhooks/check_suite_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/check_suite_properties.md @@ -1,7 +1,7 @@ | 키 | 유형 | 설명 | | ---------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `동작` | `문자열` | The action performed. Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| -| `check_suite` | `개체` | The [check_suite](/v3/checks/suites/). | +| `동작` | `문자열` | The action performed. Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| +| `check_suite` | `개체` | The [check_suite](/rest/reference/checks#suites). | | `check_suite[head_branch]` | `문자열` | The head branch name the changes are on. | | `check_suite[head_sha]` | `문자열` | The SHA of the most recent commit for this check suite. | | `check_suite[status]` | `문자열` | The summary status for all check runs that are part of the check suite. Can be `requested`, `in_progress`, or `completed`. | diff --git a/translations/ko-KR/data/reusables/webhooks/check_suite_short_desc.md b/translations/ko-KR/data/reusables/webhooks/check_suite_short_desc.md index 00c4c00937..94ed6dc937 100644 --- a/translations/ko-KR/data/reusables/webhooks/check_suite_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/check_suite_short_desc.md @@ -1 +1 @@ -Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/v3/checks/suites/)" REST API. +Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/rest/reference/checks#suites)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/commit_comment_properties.md b/translations/ko-KR/data/reusables/webhooks/commit_comment_properties.md index ba4d31184d..41010bf744 100644 --- a/translations/ko-KR/data/reusables/webhooks/commit_comment_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/commit_comment_properties.md @@ -1,4 +1,4 @@ -| 키 | 유형 | 설명 | -| ---- | ----- | ------------------------------------------------------------------------ | -| `동작` | `문자열` | The action performed. Can be `created`. | -| `의견` | `개체` | The [commit comment](/v3/repos/comments/#get-a-commit-comment) resource. | +| 키 | 유형 | 설명 | +| ---- | ----- | -------------------------------------------------------------------------- | +| `동작` | `문자열` | The action performed. Can be `created`. | +| `의견` | `개체` | The [commit comment](/rest/reference/repos#get-a-commit-comment) resource. | diff --git a/translations/ko-KR/data/reusables/webhooks/commit_comment_short_desc.md b/translations/ko-KR/data/reusables/webhooks/commit_comment_short_desc.md index 20e258a1ea..7329b1ed61 100644 --- a/translations/ko-KR/data/reusables/webhooks/commit_comment_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/commit_comment_short_desc.md @@ -1 +1 @@ -A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/v3/repos/comments/)" REST API. +A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/rest/reference/repos#comments)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/create_properties.md b/translations/ko-KR/data/reusables/webhooks/create_properties.md index 9db3dd7722..e0920ca081 100644 --- a/translations/ko-KR/data/reusables/webhooks/create_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/create_properties.md @@ -1,6 +1,6 @@ | 키 | 유형 | 설명 | | --------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `문자열` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | +| `ref` | `문자열` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | | `ref_type` | `문자열` | The type of Git ref object created in the repository. Can be either `branch` or `tag`. | | `master_branch` | `문자열` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" %}`main`{% else %}`master`{% endif %}). | | `설명` | `문자열` | The repository's current description. | diff --git a/translations/ko-KR/data/reusables/webhooks/create_short_desc.md b/translations/ko-KR/data/reusables/webhooks/create_short_desc.md index a43ab39943..5cf906a338 100644 --- a/translations/ko-KR/data/reusables/webhooks/create_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/create_short_desc.md @@ -1 +1 @@ -A Git branch or tag is created. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is created. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/delete_properties.md b/translations/ko-KR/data/reusables/webhooks/delete_properties.md index 2e175627aa..2fde814d7c 100644 --- a/translations/ko-KR/data/reusables/webhooks/delete_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ | 키 | 유형 | 설명 | | ---------- | ----- | ------------------------------------------------------------------------------ | -| `ref` | `문자열` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | +| `ref` | `문자열` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | | `ref_type` | `문자열` | The type of Git ref oject deleted in the repository. Can be `branch` or `tag`. | diff --git a/translations/ko-KR/data/reusables/webhooks/delete_short_desc.md b/translations/ko-KR/data/reusables/webhooks/delete_short_desc.md index 7557d8e4ed..726e68df82 100644 --- a/translations/ko-KR/data/reusables/webhooks/delete_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/delete_short_desc.md @@ -1 +1 @@ -A Git branch or tag is deleted. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is deleted. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/deploy_key_properties.md b/translations/ko-KR/data/reusables/webhooks/deploy_key_properties.md index ed2b560f1d..b6403832d3 100644 --- a/translations/ko-KR/data/reusables/webhooks/deploy_key_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/deploy_key_properties.md @@ -1,4 +1,4 @@ -| 키 | 유형 | 설명 | -| ---- | ----- | -------------------------------------------------------------- | -| `동작` | `문자열` | The action performed. Can be either `created` or `deleted`. | -| `키` | `개체` | The [`deploy key`](/v3/repos/keys/#get-a-deploy-key) resource. | +| 키 | 유형 | 설명 | +| ---- | ----- | -------------------------------------------------------------------- | +| `동작` | `문자열` | The action performed. Can be either `created` or `deleted`. | +| `키` | `개체` | The [`deploy key`](/rest/reference/repos#get-a-deploy-key) resource. | diff --git a/translations/ko-KR/data/reusables/webhooks/deploy_key_short_desc.md b/translations/ko-KR/data/reusables/webhooks/deploy_key_short_desc.md index c83fe68579..1d4565e788 100644 --- a/translations/ko-KR/data/reusables/webhooks/deploy_key_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/deploy_key_short_desc.md @@ -1 +1 @@ -A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/v3/repos/keys/)" REST API. +A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/rest/reference/repos#keys)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/fork_properties.md b/translations/ko-KR/data/reusables/webhooks/fork_properties.md index 9869473430..acc4c57099 100644 --- a/translations/ko-KR/data/reusables/webhooks/fork_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/fork_properties.md @@ -1,3 +1,3 @@ -| 키 | 유형 | 설명 | -| -------- | ---- | ----------------------------------------------------------------- | -| `forkee` | `개체` | The created [`repository`](/v3/repos/#get-a-repository) resource. | +| 키 | 유형 | 설명 | +| -------- | ---- | ---------------------------------------------------------------------------- | +| `forkee` | `개체` | The created [`repository`](/rest/reference/repos#get-a-repository) resource. | diff --git a/translations/ko-KR/data/reusables/webhooks/fork_short_desc.md b/translations/ko-KR/data/reusables/webhooks/fork_short_desc.md index 60f88625b0..23b9eff136 100644 --- a/translations/ko-KR/data/reusables/webhooks/fork_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/fork_short_desc.md @@ -1 +1 @@ -A user forks a repository. For more information, see the "[forks](/v3/repos/forks/)" REST API. +A user forks a repository. For more information, see the "[forks](/rest/reference/repos#forks)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/ko-KR/data/reusables/webhooks/installation_repositories_short_desc.md index 63166ba6e2..f1debb10f2 100644 --- a/translations/ko-KR/data/reusables/webhooks/installation_repositories_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/installation_repositories_short_desc.md @@ -1 +1 @@ -Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/installation_short_desc.md b/translations/ko-KR/data/reusables/webhooks/installation_short_desc.md index 4abc1de643..21cffb5f50 100644 --- a/translations/ko-KR/data/reusables/webhooks/installation_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/installation_short_desc.md @@ -1 +1 @@ -Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/issue_comment_properties.md b/translations/ko-KR/data/reusables/webhooks/issue_comment_properties.md index b983deb16f..5a93e1a350 100644 --- a/translations/ko-KR/data/reusables/webhooks/issue_comment_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/issue_comment_properties.md @@ -1 +1 @@ -`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | The previous version of the body if the action was `edited`. `issue`|`object` | The [issue](/v3/issues/) the comment belongs to. `comment`|`object` | The [comment](/v3/issues/comments/) itself. +`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | The previous version of the body if the action was `edited`. `issue`|`object` | The [issue](/rest/reference/issues) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/issues#comments) itself. diff --git a/translations/ko-KR/data/reusables/webhooks/issue_comment_short_desc.md b/translations/ko-KR/data/reusables/webhooks/issue_comment_short_desc.md index cc07764d19..dd67c3de2d 100644 --- a/translations/ko-KR/data/reusables/webhooks/issue_comment_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/issue_comment_short_desc.md @@ -1 +1 @@ -Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/v3/issues/comments/)" REST API. +Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/rest/reference/issues#comments)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/issue_properties.md b/translations/ko-KR/data/reusables/webhooks/issue_properties.md index c146faa968..bff204fc72 100644 --- a/translations/ko-KR/data/reusables/webhooks/issue_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/issue_properties.md @@ -1 +1 @@ -`issue`|`object` | The [issue](/v3/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. +`issue`|`object` | The [issue](/rest/reference/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. diff --git a/translations/ko-KR/data/reusables/webhooks/issues_short_desc.md b/translations/ko-KR/data/reusables/webhooks/issues_short_desc.md index 7dadec073b..3edc02859f 100644 --- a/translations/ko-KR/data/reusables/webhooks/issues_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/issues_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/v3/issues/comments/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/rest/reference/issues#comments)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/label_short_desc.md b/translations/ko-KR/data/reusables/webhooks/label_short_desc.md index c5f7178d8a..a634b7faa7 100644 --- a/translations/ko-KR/data/reusables/webhooks/label_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/label_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/v3/issues/labels/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/rest/reference/issues#labels)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/member_properties.md b/translations/ko-KR/data/reusables/webhooks/member_properties.md index d9e1757f40..add035dc19 100644 --- a/translations/ko-KR/data/reusables/webhooks/member_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/member_properties.md @@ -1 +1 @@ -`member`|`object` | The [user](/v3/users/) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. +`member`|`object` | The [user](/rest/reference/users) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. diff --git a/translations/ko-KR/data/reusables/webhooks/member_short_desc.md b/translations/ko-KR/data/reusables/webhooks/member_short_desc.md index 2e82896773..b664392fdf 100644 --- a/translations/ko-KR/data/reusables/webhooks/member_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/member_short_desc.md @@ -1 +1 @@ -Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/v3/repos/collaborators/)" REST API. +Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/rest/reference/repos#collaborators)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/membership_properties.md b/translations/ko-KR/data/reusables/webhooks/membership_properties.md index 6869d846fc..46828e9d9a 100644 --- a/translations/ko-KR/data/reusables/webhooks/membership_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/membership_properties.md @@ -1,6 +1,6 @@ -| 키 | 유형 | 설명 | -| ----- | ----- | ----------------------------------------------------------- | -| `동작` | `문자열` | The action that was performed. Can be `added` or `removed`. | -| `범위` | `문자열` | The scope of the membership. Currently, can only be `team`. | -| `구성원` | `개체` | The [user](/v3/users/) that was added or removed. | -| `팀` | `개체` | The [team](/v3/teams/) for the membership. | +| 키 | 유형 | 설명 | +| ----- | ----- | ------------------------------------------------------------ | +| `동작` | `문자열` | The action that was performed. Can be `added` or `removed`. | +| `범위` | `문자열` | The scope of the membership. Currently, can only be `team`. | +| `구성원` | `개체` | The [user](/rest/reference/users) that was added or removed. | +| `팀` | `개체` | The [team](/rest/reference/teams) for the membership. | diff --git a/translations/ko-KR/data/reusables/webhooks/membership_short_desc.md b/translations/ko-KR/data/reusables/webhooks/membership_short_desc.md index e557eea902..f7867d25a9 100644 --- a/translations/ko-KR/data/reusables/webhooks/membership_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/membership_short_desc.md @@ -1 +1 @@ -Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/v3/teams/members/)" REST API. +Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/rest/reference/teams#members)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/milestone_short_desc.md b/translations/ko-KR/data/reusables/webhooks/milestone_short_desc.md index 6b6bd073ce..c9edf73236 100644 --- a/translations/ko-KR/data/reusables/webhooks/milestone_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/milestone_short_desc.md @@ -1 +1 @@ -Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/v3/issues/milestones/)" REST API. +Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/rest/reference/issues#milestones)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/org_block_short_desc.md b/translations/ko-KR/data/reusables/webhooks/org_block_short_desc.md index 7c3896f63c..f75660fcdb 100644 --- a/translations/ko-KR/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. +Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/org_desc.md b/translations/ko-KR/data/reusables/webhooks/org_desc.md index 8b344e764c..90d218b876 100644 --- a/translations/ko-KR/data/reusables/webhooks/org_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/org_desc.md @@ -1 +1 @@ -`organization` | `object` | Webhook payloads contain the [`organization`](/v3/orgs/#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. +`organization` | `object` | Webhook payloads contain the [`organization`](/rest/reference/orgs#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. diff --git a/translations/ko-KR/data/reusables/webhooks/organization_short_desc.md b/translations/ko-KR/data/reusables/webhooks/organization_short_desc.md index 895b584aaf..0b539ee364 100644 --- a/translations/ko-KR/data/reusables/webhooks/organization_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/organization_short_desc.md @@ -1 +1 @@ -Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/v3/orgs/)" REST API. +Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/rest/reference/orgs)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/project_card_properties.md b/translations/ko-KR/data/reusables/webhooks/project_card_properties.md index 668ce5ae42..3634400579 100644 --- a/translations/ko-KR/data/reusables/webhooks/project_card_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/project_card_properties.md @@ -4,4 +4,4 @@ | `changes` | `개체` | The changes to the project card if the action was `edited` or `converted`. | | `changes[note][from]` | `문자열` | The previous version of the note if the action was `edited` or `converted`. | | `after_id` | `integer` | The id of the card that this card now follows if the action was "moved". Will be `null` if it is the first card in a column. | -| `project_card` | `개체` | The [project card](/v3/projects/cards) itself. | +| `project_card` | `개체` | The [project card](/rest/reference/projects#cards) itself. | diff --git a/translations/ko-KR/data/reusables/webhooks/project_card_short_desc.md b/translations/ko-KR/data/reusables/webhooks/project_card_short_desc.md index bbea9ea6c4..6fe2904d9e 100644 --- a/translations/ko-KR/data/reusables/webhooks/project_card_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/project_card_short_desc.md @@ -1 +1 @@ -Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/v3/projects/cards)" REST API. +Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/project_column_properties.md b/translations/ko-KR/data/reusables/webhooks/project_column_properties.md index 82e7d2e64b..26135131ad 100644 --- a/translations/ko-KR/data/reusables/webhooks/project_column_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/project_column_properties.md @@ -4,4 +4,4 @@ | `changes` | `개체` | The changes to the project column if the action was `edited`. | | `changes[name][from]` | `문자열` | The previous version of the name if the action was `edited`. | | `after_id` | `integer` | The id of the column that this column now follows if the action was "moved". Will be `null` if it is the first column in a project. | -| `project_column` | `개체` | The [project column](/v3/projects/columns) itself. | +| `project_column` | `개체` | The [project column](/rest/reference/projects#columns) itself. | diff --git a/translations/ko-KR/data/reusables/webhooks/project_column_short_desc.md b/translations/ko-KR/data/reusables/webhooks/project_column_short_desc.md index 19ac3f6412..35d38e4101 100644 --- a/translations/ko-KR/data/reusables/webhooks/project_column_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/project_column_short_desc.md @@ -1 +1 @@ -Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/v3/projects/columns)" REST API. +Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/project_properties.md b/translations/ko-KR/data/reusables/webhooks/project_properties.md index 4adc45332f..a012ed9ade 100644 --- a/translations/ko-KR/data/reusables/webhooks/project_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/project_properties.md @@ -4,4 +4,4 @@ | `changes` | `개체` | The changes to the project if the action was `edited`. | | `changes[name][from]` | `문자열` | The previous version of the name if the action was `edited`. | | `changes[body][from]` | `문자열` | The previous version of the body if the action was `edited`. | -| `프로젝트` | `개체` | The [project](/v3/projects/) itself. | +| `프로젝트` | `개체` | The [project](/rest/reference/projects) itself. | diff --git a/translations/ko-KR/data/reusables/webhooks/project_short_desc.md b/translations/ko-KR/data/reusables/webhooks/project_short_desc.md index 6f18da5d69..2ae5d8be21 100644 --- a/translations/ko-KR/data/reusables/webhooks/project_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/project_short_desc.md @@ -1 +1 @@ -Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/v3/projects)" REST API. +Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_properties.md b/translations/ko-KR/data/reusables/webhooks/pull_request_properties.md index 21544ccd9e..948f78e0b0 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_properties.md @@ -1 +1 @@ -`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls) itself. +`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) itself. diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_properties.md index a38df37d8c..1b854809c7 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_properties.md @@ -1 +1 @@ -`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls/) the comment belongs to. `comment`|`object` | The [comment](/v3/pulls/comments) itself. +`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/pulls#comments) itself. diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_short_desc.md index 7b05ee9a9a..e002a3be49 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_review_comment_short_desc.md @@ -1 +1 @@ -Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/v3/pulls/comments/)" REST API. +Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/rest/reference/pulls#comments)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_review_properties.md b/translations/ko-KR/data/reusables/webhooks/pull_request_review_properties.md index efe385b708..2e0360005c 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ | 키 | 유형 | 설명 | | --------------------- | ----- | ---------------------------------------------------------------------- | | `동작` | `문자열` | The action that was performed. Can be one of:
  • `submitted` - A pull request review is submitted into a non-pending state.
  • `edited` - The body of a review has been edited.
  • `dismissed` - A review has been dismissed.
| -| `pull_request` | `개체` | The [pull request](/v3/pulls/) the review pertains to. | +| `pull_request` | `개체` | The [pull request](/rest/reference/pulls) the review pertains to. | | `검토` | `개체` | The review that was affected. | | `changes[body][from]` | `문자열` | The previous version of the body if the action was `edited`. | diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/ko-KR/data/reusables/webhooks/pull_request_review_short_desc.md index 07b263364d..3329d4b62e 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_review_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_review_short_desc.md @@ -1 +1 @@ -Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/v3/pulls/reviews/)" REST API. +Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/rest/reference/pulls#reviews)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_short_desc.md b/translations/ko-KR/data/reusables/webhooks/pull_request_short_desc.md index ea9e435d03..45bc1b5789 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_short_desc.md @@ -1 +1 @@ -Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/v3/pulls/)" REST API. +Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/rest/reference/pulls)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/release_short_desc.md b/translations/ko-KR/data/reusables/webhooks/release_short_desc.md index e3a9a3bb3a..a8d506f409 100644 --- a/translations/ko-KR/data/reusables/webhooks/release_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/release_short_desc.md @@ -1 +1 @@ -Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/v3/repos/releases/)" REST API. +Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/rest/reference/repos#releases)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/repo_desc.md b/translations/ko-KR/data/reusables/webhooks/repo_desc.md index df26fb3e7a..e0eca4218d 100644 --- a/translations/ko-KR/data/reusables/webhooks/repo_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/repo_desc.md @@ -1 +1 @@ -`repository` | `object` | The [`repository`](/v3/repos/#get-a-repository) where the event occurred. +`repository` | `object` | The [`repository`](/rest/reference/repos#get-a-repository) where the event occurred. diff --git a/translations/ko-KR/data/reusables/webhooks/repository_import_short_desc.md b/translations/ko-KR/data/reusables/webhooks/repository_import_short_desc.md index 056531b019..d4b6cf9aa0 100644 --- a/translations/ko-KR/data/reusables/webhooks/repository_import_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/repository_import_short_desc.md @@ -1 +1 @@ -Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/v3/migrations/source_imports/)" REST API. +Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/rest/reference/migrations#source-imports)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/repository_short_desc.md b/translations/ko-KR/data/reusables/webhooks/repository_short_desc.md index df290ac0ea..b3e90e8d64 100644 --- a/translations/ko-KR/data/reusables/webhooks/repository_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/repository_short_desc.md @@ -1 +1 @@ -Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/v3/repos/)" REST API. +Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/rest/reference/repos)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/star_short_desc.md b/translations/ko-KR/data/reusables/webhooks/star_short_desc.md index f4fb663419..9569c6958e 100644 --- a/translations/ko-KR/data/reusables/webhooks/star_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/star_short_desc.md @@ -1 +1 @@ -Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/status_short_desc.md b/translations/ko-KR/data/reusables/webhooks/status_short_desc.md index 754f871add..6d835788c9 100644 --- a/translations/ko-KR/data/reusables/webhooks/status_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/status_short_desc.md @@ -1 +1 @@ -When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/v3/repos/statuses/)" REST API. +When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/rest/reference/repos#statuses)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/team_add_short_desc.md b/translations/ko-KR/data/reusables/webhooks/team_add_short_desc.md index 914535a212..ff260fc3cb 100644 --- a/translations/ko-KR/data/reusables/webhooks/team_add_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/team_add_short_desc.md @@ -1 +1 @@ -When a [repository is added to a team](/v3/teams/#add-or-update-team-repository-permissions). +When a [repository is added to a team](/rest/reference/teams#add-or-update-team-repository-permissions). diff --git a/translations/ko-KR/data/reusables/webhooks/team_short_desc.md b/translations/ko-KR/data/reusables/webhooks/team_short_desc.md index fdcf742789..ff27913e21 100644 --- a/translations/ko-KR/data/reusables/webhooks/team_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/team_short_desc.md @@ -1 +1 @@ -Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/v3/teams/)" REST API. +Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/rest/reference/teams)" REST API. diff --git a/translations/ko-KR/data/reusables/webhooks/watch_short_desc.md b/translations/ko-KR/data/reusables/webhooks/watch_short_desc.md index a853027b12..1b250fb019 100644 --- a/translations/ko-KR/data/reusables/webhooks/watch_short_desc.md +++ b/translations/ko-KR/data/reusables/webhooks/watch_short_desc.md @@ -1 +1 @@ -When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md index fac5e27b72..53bf333884 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md @@ -1,5 +1,5 @@ --- -title: Criar e estar o Java com o Ant +title: Criar e testar o Java com o Ant intro: Você pode criar um fluxo de trabalho de integração contínua (CI) no GitHub Actions para criar e testar o seu projeto Java com o Ant. product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -38,22 +38,22 @@ Você também pode adicionar este fluxo de trabalho manualmente, criando um novo {% raw %} ```yaml -nome: Java CI +name: Java CI -em: [push] +on: [push] -trabalho: +jobs: build: runs-on: ubuntu-latest - etapa: - - usa: actions/checkout@v2 - - nome: Configure JDK 1. - uso: actionp-java@v1 - com: - java-version: 1. - - nome: Construir com Ant - executar: ant -noinput -buildfile build.xml + steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Build with Ant + run: ant -noinput -buildfile build.xml ``` {% endraw %} @@ -79,13 +79,13 @@ Se você usa comandos diferentes para criar seu projeto ou se você quer executa {% raw %} ```yaml -etapas: - - usa: actions/checkout@v2 - - usa: actions/setup-java@v1 - com: +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Executa o alvo do Ant jar - executa: ant -noinput -buildfile build-ci.xml jar + - name: Run the Ant jar target + run: ant -noinput -buildfile build-ci.xml jar ``` {% endraw %} diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md index 7afadb442f..f4ab8f735b 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md @@ -1,5 +1,5 @@ --- -title: Criar e estar o Java com o Gradle +title: Criar e testar o Java com o Gradle intro: Você pode criar um fluxo de trabalho de integração contínua (CI) no GitHub Actions para criar e testar o seu projeto Java com o Gradle. product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -38,22 +38,22 @@ Você também pode adicionar este fluxo de trabalho manualmente, criando um novo {% raw %} ```yaml -nome: Java CI +name: Java CI -em: [push] +on: [push] -trabalhos: - criar: +jobs: + build: runs-on: ubuntu-latest - etapas: - - usa: actions/checkout@v2 - - nome: Set up JDK 1.8 - usa: actions/setup-java@v1 - com: + steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Criar com Gradle - executar: ./gradlew build + - name: Build with Gradle + run: ./gradlew build ``` {% endraw %} @@ -79,36 +79,36 @@ Se você usa comandos diferentes para criar seu projeto ou se você desejar usar {% raw %} ```yaml -etapas: - - usa: actions/checkout@v2 - - ususaes: actions/setup-java@v1 - com: +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: java-version: 1.8 - - Nome: Executa a tarefa do pacote do Gradle - executar: ./gradlew -b ci.gradle package + - name: Run the Gradle package task + run: ./gradlew -b ci.gradle package ``` {% endraw %} ### Memorizar dependências -Você pode armazenar as suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. Para obter mais informações, consulte "[Memorizando dependências para acelerar os fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" e a ação [`cache`](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml -etapas: - - usa: actions/checkout@v2 - - nome: Set up JDK 1.8 - usa: actions/setup-java@v1 - com: +steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Cache Gradle packages - usa: actions/cache@v2 - com: - caminho: ~/.gradle/caches - Chave: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} + - name: Cache Gradle packages + uses: actions/cache@v2 + with: + path: ~/.gradle/caches + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} restore-keys: ${{ runner.os }}-gradle - - Nome: Criar com Gradle - executar: ./gradlew build + - name: Build with Gradle + run: ./gradlew build ``` {% endraw %} diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md index 549704f853..61693099b8 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md @@ -1,5 +1,5 @@ --- -title: Criar e estar o Java com o Maven +title: Criar e testar o Java com o Maven intro: Você pode criar um fluxo de trabalho de integração contínua (CI) no GitHub Actions para criar e testar o seu projeto Java com o Maven. product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -38,22 +38,22 @@ Você também pode adicionar este fluxo de trabalho manualmente, criando um novo {% raw %} ```yaml -nome: Java CI +name: Java CI -em: [push] +on: [push] -trabalhos: - criar: +jobs: + build: runs-on: ubuntu-latest - etapas: - - usa: actions/checkout@v2 - - nome: Set up JDK 1.8 - usa: actions/setup-java@v1 - com: + steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Criado com Maven - executar: mvn -B package --file pom.xml + - name: Build with Maven + run: mvn -B package --file pom.xml ``` {% endraw %} @@ -79,36 +79,36 @@ Se você usa comandos diferentes para criar seu projeto ou se desejar usar um al {% raw %} ```yaml -etapas: - - usa: actions/checkout@v2 - - usa: actions/setup-java@v1 - com: +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Executar a fase de verificação do Maven - executar: mvn -B verify --file pom-ci.xml + - name: Run the Maven verify phase + run: mvn -B verify --file pom-ci.xml ``` {% endraw %} ### Memorizar dependências -Você pode armazenar as suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Para obter mais informações, consulte "[Memorizando dependências para acelerar os fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" e a ação [`cache`](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml -etapas: - - usa: actions/checkout@v2 - - nome: Set up JDK 1.8 - usa: actions/setup-java@v1 - cpm: +steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Cache Maven packages - usa: actions/cache@v2 - com: - caminho: ~/.m2 - chave: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} + - name: Cache Maven packages + uses: actions/cache@v2 + with: + path: ~/.m2 + key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - - nome: Construir com Maven - executar: mvn -B package --file pom.xml + - name: Build with Maven + run: mvn -B package --file pom.xml ``` {% endraw %} diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md index 2c2dad9f3a..0ad489ba42 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md @@ -91,8 +91,8 @@ steps: Como alternativa, você pode criar e fazes testes com versões exatas do Node.js. ```yaml -estratégia: - matriz: +strategy: + matrix: node-version: [8.16.2, 10.17.0] ``` @@ -129,7 +129,7 @@ Se você não especificar uma versão do Node.js, o {% data variables.product.pr Executores hospedados em {% data variables.product.prodname_dotcom %} têm gerenciadores de dependências npm e Yarn instalados. Você pode usar o npm e o Yarn para instalar dependências no seu fluxo de trabalho antes de criar e testar seu código. Os executores do Windows e Linux hospedados em {% data variables.product.prodname_dotcom %} também têm o Grunt, Gulp, e Bower instalado. -Você também pode memorizar as dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "[Memorizando dependências para acelerar seu fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". #### Exemplo de uso do npm @@ -227,7 +227,7 @@ always-auth=true #### Exemplo de memorização de dependências -Você pode memorizar dependências usando uma chave única e restaurar as dependências ao executar fluxos de trabalho futuros usando a ação `cache`. Para obter mais informações, consulte "[Memorizando dependências para acelerar os fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" e a ação [`cache`](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml @@ -241,7 +241,7 @@ steps: uses: actions/cache@v2 with: # npm cache files are stored in `~/.npm` on Linux/macOS - path: ~/.npm + path: ~/.npm key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }} restore-keys: | ${{ runner.OS }}-node- diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md index f1edb036d5..642f2ada38 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md @@ -1,10 +1,12 @@ --- -title: Building and testing PowerShell -intro: You can create a continuous integration (CI) workflow to build and test your PowerShell project. +title: Criar e testar PowerShell +intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto de PowerShell. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - potatoqualitee --- {% data reusables.actions.enterprise-beta %} @@ -12,25 +14,25 @@ versions: ### Introdução -This guide shows you how to use PowerShell for CI. It describes how to use Pester, install dependencies, test your module, and publish to the PowerShell Gallery. +Este guia mostra como usar PowerShell para CI. Ele descreve como usar o Pester, instalar dependências, testar seu módulo e publicar na Galeria do PowerShell. -{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes PowerShell and Pester. For a full list of up-to-date software and the pre-installed versions of PowerShell and Pester, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +Executores hospedados em {% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado que inclui PowerShell e Pester. Para obter uma lista completa do software atualizado e das versões pré-instaladas do PowerShell e Pester, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". ### Pré-requisitos Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". -We recommend that you have a basic understanding of PowerShell and Pester. Para obter mais informações, consulte: -- [Getting started with PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started) +Recomendamos que você tenha um entendimento básico de PowerShell e Pester. Para obter mais informações, consulte: +- [Primeiros passos com o PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started) - [Pester](https://pester.dev) {% data reusables.actions.enterprise-setup-prereq %} -### Adding a workflow for Pester +### Adicionar um fluxo de trabalho ao Pester -To automate your testing with PowerShell and Pester, you can add a workflow that runs every time a change is pushed to your repository. In the following example, `Test-Path` is used to check that a file called `resultsfile.log` is present. +Para automatizar o seu teste com PowerShell e Pester, você pode adicionar um fluxo de trabalho que é executado toda vez que uma alteração é carregada no seu repositório. No exemplo a seguir, `Test-Path` é usado para verificar se um arquivo denominado `resultsfile.log` está presente. -This example workflow file must be added to your repository's `.github/workflows/` directory: +Este exemplo de arquivo de fluxo de trabalho deve ser adicionado ao diretório `.github/workflows/` do repositório: {% raw %} ```yaml @@ -54,13 +56,13 @@ jobs: ``` {% endraw %} -* `shell: pwsh` - Configures the job to use PowerShell when running the `run` commands. -* `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory. -* `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. Por exemplo: +* `shell: pwsh` - Configura o trabalho para usar PowerShell quando executa os comandos `executar`. +* `run: Test-Path resultsfile.log` - Verifica se um arquivo denominado `resultsfile.log` está presente no diretório raiz do repositório. +* `Should -Be $true` - Usa o Pester para definir um resultado esperado. Se o resultado for inesperado, {% data variables.product.prodname_actions %} irá sinalizar isso como um teste falho. Por exemplo: - ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png) + ![Falha no teste de Pester](/assets/images/help/repository/actions-failed-pester-test.png) -* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following: +* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Usa o Pester para executar testes definidos em um arquivo denominado `Unit.Tests.ps1`. Por exemplo, para realizar o mesmo teste descrito acima, o `Unit.Tests.ps1` conterá o seguinte: ``` Describe "Check results file is present" { It "Check results file is present" { @@ -69,29 +71,29 @@ jobs: } ``` -### PowerShell module locations +### Locais de módulos do PowerShell -The table below describes the locations for various PowerShell modules in each {% data variables.product.prodname_dotcom %}-hosted runner. +A tabela abaixo descreve os locais para diversos módulos do PowerShell em cada executor hospedado em {% data variables.product.prodname_dotcom %}. -| | Ubuntu | macOS | Windows | -| ----------------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ | -| **PowerShell system modules** | `/opt/microsoft/powershell/7/Modules/*` | `/usr/local/microsoft/powershell/7/Modules/*` | `C:\program files\powershell\7\Modules\*` | -| **PowerShell add-on modules** | `/usr/local/share/powershell/Modules/*` | `/usr/local/share/powershell/Modules/*` | `C:\Modules\*` | -| **User-installed modules** | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` | +| | Ubuntu | macOS | Windows | +| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ | +| **Módulos do sistema do PowerShell** | `/opt/microsoft/powershell/7/Modules/*` | `/usr/local/microsoft/powershell/7/Modules/*` | `C:\program files\powershell\7\Modules\*` | +| **Módulos de complementos do PowerShell** | `/usr/local/share/powershell/Modules/*` | `/usr/local/share/powershell/Modules/*` | `C:\Modules\*` | +| **Módulos instalados pelo usuário** | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` | ### Instalar dependências -{% data variables.product.prodname_dotcom %}-hosted runners have PowerShell 7 and Pester installed. You can use `Install-Module` to install additional dependencies from the PowerShell Gallery before building and testing your code. +Executores hospedados em {% data variables.product.prodname_dotcom %} têm PowerShell 7 e o Pester instalado. Você pode usar `Install-Module` para instalar dependências adicionais da Galeria PowerShell antes de construir e testar o seu código. {% note %} -**Note:** The pre-installed packages (such as Pester) used by {% data variables.product.prodname_dotcom %}-hosted runners are regularly updated, and can introduce significant changes. As a result, it is recommended that you always specify the required package versions by using `Install-Module` with `-MaximumVersion`. +**Nota:** Os pacotes pré-instalados (como o Colester) usados pelos executores hospedados em {% data variables.product.prodname_dotcom %} são atualizados regularmente e podem introduzir mudanças significativas. Como resultado, recomenda-se que você sempre especifique as versões necessárias dos pacotes usando o `Install-Module` com `-MaximumVersion`. {% endnote %} -Você também pode memorizar as dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "[Memorizando dependências para acelerar seu fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". -For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules: +Por exemplo, o trabalho a seguir instala os módulos `SqlServer` e `PSScriptAnalyzer`: {% raw %} ```yaml @@ -111,15 +113,15 @@ jobs: {% note %} -**Note:** By default, no repositories are trusted by PowerShell. When installing modules from the PowerShell Gallery, you must explicitly set the installation policy for `PSGallery` to `Trusted`. +**Observação:** Por padrão, nenhum repositório é confiável pelo PowerShell. Ao instalar módulos na Galeria do PowerShell, você deve definir explicitamente a política de instalação para `PSGallery` como `Confiável`. {% endnote %} #### Memorizar dependências -You can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. Para obter mais informações, consulte "[Memorizando dependências para acelerar fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". -PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system. +O PowerShell armazena suas dependências em diferentes locais, dependendo do sistema operacional do executor. Por exemplo, o `caminho` local usado no exemplo do Ubuntu a seguir será diferente para um sistema operacional Windows. {% raw %} ```yaml @@ -144,9 +146,9 @@ steps: Você pode usar os mesmos comandos usados localmente para criar e testar seu código. -#### Using PSScriptAnalyzer to lint code +#### Usar PSScriptAnalyzer para código lint -The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1` files in the repository. For more information, see [PSScriptAnalyzer on GitHub](https://github.com/PowerShell/PSScriptAnalyzer). +O exemplo a seguir instala `PSScriptAnalyzer` e o usa para limpar todos os arquivos `ps1` no repositório. Para obter mais informações, consulte [PSScriptAnalyzer no GitHub](https://github.com/PowerShell/PSScriptAnalyzer). {% raw %} ```yaml @@ -178,7 +180,7 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1` Você pode fazer o upload de artefatos para visualização após a conclusão de um fluxo de trabalho. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". -The following example demonstrates how you can use the `upload-artifact` action to archive the test results received from `Invoke-Pester`. Para obter mais informações, consulte a ação <[`upload-artifact`](https://github.com/actions/upload-artifact). +O exemplo a seguir demonstra como você pode usar a ação `upload-artifact` para arquivar os resultados de teste recebidos de `Invoke-Pester`. Para obter mais informações, consulte a ação <[`upload-artifact`](https://github.com/actions/upload-artifact). {% raw %} ```yaml @@ -204,13 +206,13 @@ jobs: ``` {% endraw %} -The `always()` function configures the job to continue processing even if there are test failures. For more information, see "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)." +A função `always()` configura o trabalho para continuar processando mesmo se houver falhas no teste. Para obter mais informações, consulte "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)". -### Publishing to PowerShell Gallery +### Publicar na Galeria do PowerShell -You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your package. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". +Você pode configurar o seu fluxo de trabalho para publicar o seu módulo do PowerShell para a Galeria PowerShell quando o seu teste de passar. Você pode usar segredos do repositório para armazenar quaisquer tokens ou credenciais necessárias para publicar seu pacote. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". -The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery: +O exemplo a seguir cria um pacote e usa `Publish-Module` para publicá-lo na Galeria do PowerShell: {% raw %} ```yaml diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-python.md b/translations/pt-BR/content/actions/guides/building-and-testing-python.md index 1ced3ffe2c..66003ff6b1 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-python.md @@ -126,27 +126,27 @@ Você pode configurar uma versão específica do python. Por exemplo, 3,8. Como {% raw %} ```yaml -nome: Pacote Python +name: Python package -em: [push] +on: [push] -trabalhos: - criar: +jobs: + build: runs-on: ubuntu-latest - etapas: - - usa: actions/checkout@v2 - - nome: Configura Python 3.x - usa: actions/setup-python@v2 - com: - # Sintaxe do intervalo da versão semântica ou versão exata de uma versão do Python - python-version: '3.x' - # Opcional - x64 or x86 architecture, defaults to x64 - arquitetura: 'x64' - # Você pode testar a sua matriz imprimindo a versão atual do Python - - nome: Exibir uma versão do Python - executar: python -c "import sys; print(sys.version)" + steps: + - uses: actions/checkout@v2 + - name: Set up Python 3.x + uses: actions/setup-python@v2 + with: + # Semantic version range syntax or exact version of a Python version + python-version: '3.x' + # Optional - x64 or x86 architecture, defaults to x64 + architecture: 'x64' + # You can test your matrix by printing the current Python version + - name: Display Python version + run: python -c "import sys; print(sys.version)" ``` {% endraw %} @@ -192,7 +192,7 @@ Recomendamos usar `setup-python` para configurar a versão do Python usada nos s Os executores hospedados em {% data variables.product.prodname_dotcom %} têm instalado o gerenciador do pacote pip. Você pode usar o pip para instalar dependências do registro de pacotes do PyPI antes de criar e testar o seu código. Por exemplo, o YAML abaixo instala ou atualiza o instalador de pacotes `pip` e as os pacotes `setuptools` e `wheel`. -Você também pode memorizar as dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "[Memorizando dependências para acelerar seu fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". {% raw %} ```yaml @@ -228,7 +228,7 @@ etapas: #### Memorizar dependências -Você pode armazenar dependências do pip usando uma chave única e restaurar as dependências quando você executar fluxos de trabalho futuros usando a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "[Memorizando dependências para acelerar fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". O Pip armazena dependências em diferentes locais, dependendo do sistema operacional do executor. O caminho que você precisa efetuar o armazenamento em cache pode ser diferente do exemplo do Ubuntu abaixo, dependendo do sistema operacional que você usa. Para obter mais informações, consulte [Exemplos de armazenamento em cache do Python](https://github.com/actions/cache/blob/main/examples.md#python---pip). diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md index 47bff7c4ae..8b7cec1f07 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md @@ -1,6 +1,6 @@ --- -title: Building and testing Ruby -intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +title: Criar e testar o Ruby +intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto do Ruby. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' @@ -12,18 +12,18 @@ versions: ### Introdução -This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem. +Este guia mostra como criar um fluxo de trabalho de integração contínua (CI) que compila e testa um aplicativo do Rubi. Se o seu teste do CI passar, você deverá implantar seu código ou publicar um gem. ### Pré-requisitos -We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. Para obter mais informações, consulte: +Recomendamos que você tenha um entendimento básico do Ruby, YAML, das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, consulte: - [Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions) -- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) +- [Ruby em 20 minutos](https://www.ruby-lang.org/en/documentation/quickstart/) -### Starting with the Ruby workflow template +### Primeiros passos com o modelo de fluxo de trabalho do Ruby -{% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml). +{% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de trabalho do Ruby que funcionará para a maioria dos projetos do Ruby. Para obter mais informações, consulte o [modelo do workflow do Ruby](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml). Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. @@ -58,13 +58,13 @@ jobs: ``` {% endraw %} -### Specifying the Ruby version +### Especificar a versão do Ruby -The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). +A maneira mais fácil de especificar uma versão do Ruby é usar a ação `ruby/setup-ruby` fornecida pela organização Ruby no GitHub. A ação adiciona qualquer versão do Ruby compatível com `PATH` para cada tarefa executada em um fluxo de trabalho. Para mais informações, consulte [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). -Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. +Usar a ação `ruby/setup-ruby` do Ruby ou a ação `/setup-ruby` do GitHubt é a forma recomendada de usar o Ruby com o GitHub Actions porque garante um comportamento consistente entre diferentes executores e versões do Ruby. -The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. +A ação `setup-ruby` toma uma versão Ruby como uma entrada e configura essa versão no executor. {% raw %} ```yaml @@ -78,11 +78,11 @@ steps: ``` {% endraw %} -Alternatively, you can check a `.ruby-version` file into the root of your repository and `setup-ruby` will use the version defined in that file. +Como alternativa, você pode verificar um arquivo `.ruby-version` na raiz do seu repositório e `setup-ruby` usará a versão definida nesse arquivo. -### Testing with multiple versions of Ruby +### Testar com versões múltiplas do Ruby -You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version. +Você pode adicionar uma estratégia matriz para executar seu fluxo de trabalho com mais de uma versão do Ruby. Por exemplo, você pode testar o seu código para as últimas versões de correção das versões 2.7, 2.6 e 2.5. O "x" é um caractere curinga que corresponde à última versão do patch disponível para uma versão. {% raw %} ```yaml @@ -92,9 +92,9 @@ strategy: ``` {% endraw %} -Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "Workflow syntax for GitHub Actions" and "Context and expression syntax for GitHub Actions." +Cada versão do Ruby especificada no array `ruby-version` cria um trabalho que executa as mesmas etapas. O contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} é usado para acessar a versão atual do trabalho. Para obter mais informações sobre estratégias e contextos da matriz, consulte a "Sintaxe de fluxo de trabalho para Ações no GitHub" e a "Sintaxe de Contexto e expressão para Ações no GitHub." -The full updated workflow with a matrix strategy could look like this: +O fluxo de trabalho totalmente atualizado com uma estratégia de matriz pode parecer com isto: {% raw %} ```yaml @@ -131,9 +131,9 @@ jobs: ``` {% endraw %} -### Installing dependencies with Bundler +### Instalar dependências com o Bundler -The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed. +A ação `setup-ruby` irá instalar o bundler automaticamente para você. A versão é determinada pelo arquivo `gemfile.lock`. Se nenhuma versão estiver presente no seu arquivo de bloqueio, será instalada a última versão compatível. {% raw %} ```yaml @@ -148,9 +148,9 @@ steps: #### Memorizar dependências -The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. -To enable caching, set the following. +Para habilitar o cache, defina o seguinte. {% raw %} ```yaml @@ -161,11 +161,11 @@ steps: ``` {% endraw %} -This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install. +Isso irá configurar o bundler para instalar seus gems em `vendor/cache`. Para cada execução bem sucedida do seu fluxo de trabalho, esta pasta será armazenada em cache por Ações e baixada novamente para subsequentes execuções de fluxo de trabalho. São usados um hash do seu gemfile.lock e versão do Ruby como a chave de cache. Se você instalar qualquer novo gem, ou mudar uma versão, o cache será invalidado e o bundler fará uma nova instalação. -**Caching without setup-ruby** +**Fazer armazenamento em cache sem o setup-ruby** -For greater control over caching, you can use the `actions/cache` Action directly. Para obter mais informações, consulte "[Memorizando dependências para acelerar seu fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)". +For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". {% raw %} ```yaml @@ -183,7 +183,7 @@ steps: ``` {% endraw %} -If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this: +Se você estiver usando uma compilação de matriz, você vai querer incluir as variáveis da matriz na sua chave de cache. Por exemplo, se você tem uma estratégia matriz para diferentes versões do ruby (`matrix. uby-version`) e diferentes sistemas operacionais (`matrix.os`), suas etapas de fluxo de trabalho podem se parecer com isso: {% raw %} ```yaml @@ -201,9 +201,9 @@ steps: ``` {% endraw %} -### Matrix testing your code +### Matriz que testa o seu código -The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS. +O exemplo a seguir da matriz testa todas as versões estáveis e versões principais de MRI, JRuby e TruffleRuby no Ubuntu e no macOS. {% raw %} ```yaml @@ -234,9 +234,9 @@ jobs: ``` {% endraw %} -### Linting your code +### Fazer linting do seu código -The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules. +O exemplo a seguir instala `rubocop` e o utiliza para fazer lint de todos os arquivos. Para obter mais informações, consulte [Rubocop](https://github.com/rubocop-hq/rubocop). Pode [configurar o Rubocop](https://docs.rubocop.org/rubocop/configuration.html) para decidir as regras específicas de linting. {% raw %} ```yaml @@ -258,11 +258,11 @@ jobs: ``` {% endraw %} -### Publishing Gems +### Publicar gems -You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. +Você pode configurar o seu fluxo de trabalho para publicar o seu pacote do Ruby em qualquer pacote de registro que você desejar quando os seus testes de CI passarem. -Você pode armazenar qualquer token de acesso ou credenciais necessárias para publicar seu pacote usando segredos do repositório. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. +Você pode armazenar qualquer token de acesso ou credenciais necessárias para publicar seu pacote usando segredos do repositório. O exemplo a seguir cria e publica um pacote no `Registro de Pacote do GitHub` e `RubyGems`. {% raw %} ```yaml diff --git a/translations/pt-BR/content/actions/guides/index.md b/translations/pt-BR/content/actions/guides/index.md index f7e40ce2e9..8774c1a09c 100644 --- a/translations/pt-BR/content/actions/guides/index.md +++ b/translations/pt-BR/content/actions/guides/index.md @@ -31,6 +31,7 @@ Você pode usar o {% data variables.product.prodname_actions %} para criar fluxo {% link_in_list /building-and-testing-nodejs %} {% link_in_list /building-and-testing-powershell %} {% link_in_list /building-and-testing-python %} +{% link_in_list /building-and-testing-ruby %} {% link_in_list /building-and-testing-java-with-maven %} {% link_in_list /building-and-testing-java-with-gradle %} {% link_in_list /building-and-testing-java-with-ant %} diff --git a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md index 2883119128..055a0ebeec 100644 --- a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md @@ -8,6 +8,8 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 631a3792dd..f0cf61a99c 100644 --- a/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,6 +11,8 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md index 2add474fe8..de100c86f4 100644 --- a/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -131,7 +131,7 @@ O valor `retention-days` não pode exceder o limite de retenção definido pelo Durante a execução de um fluxo de trabalho, você pode usar a ação [`download-artifact`](https://github.com/actions/download-artifact)para fazer o download de artefatos previamente carregados na mesma execução de fluxo de trabalho. -Após a conclusão da execução de um fluxo de trabalho, você pode fazer o download ou excluir artefatos em {% data variables.product.prodname_dotcom %} ou usar a API REST. Para obter mais informações, consulte "[Fazer o download de artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts), "[Remover artefatos do fluxo de trabalho](/actions/managing-workflow-runs/removing-workflow-artifacts)" e "[Artefatos da REST API](/v3/actions/artifacts/)". +Após a conclusão da execução de um fluxo de trabalho, você pode fazer o download ou excluir artefatos em {% data variables.product.prodname_dotcom %} ou usar a API REST. Para obter mais informações, consulte "[Fazer o download de artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts), "[Remover artefatos do fluxo de trabalho](/actions/managing-workflow-runs/removing-workflow-artifacts)" e "[Artefatos da REST API](/rest/reference/actions#artifacts)". #### Fazer o download dos artefatos durante a execução de um fluxo de trabalho @@ -171,12 +171,12 @@ Os trabalhos que são dependentes de artefatos de um trabalho anterior devem agu O Job 1 (Trabalho 1) executa estas etapas: - Realiza um cálculo de correspondência e salva o resultado em um arquivo de texto denominado `math-homework.txt`. -- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the artifact name `homework`. +- Usa a ação `upload-artifact` para fazer upload do arquivo `math-homework.txt` com o nome do artefato `homework`. O Job 2 (Trabalho 2) usa o resultado do trabalho anterior: - Baixa o artefato `homework` carregado no trabalho anterior. Por padrão, a ação `download-artifact` baixa artefatos no diretório da área de trabalho no qual a etapa está sendo executada. Você pode usar o parâmetro da entrada do `caminho` para especificar um diretório diferente para o download. -- Reads the value in the `math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt` again, overwriting its contents. -- Faz upload do arquivo `math-homework.txt`. This upload overwrites the previously uploaded artifact because they share the same name. +- Lê o valor no arquivo `math-homework.txt`, efetua um cálculo matemático e salva o resultado em `math-homework.txt` novamente, sobrescrevendo o seu conteúdo. +- Faz upload do arquivo `math-homework.txt`. Este upload sobrescreve o artefato carregado anteriormente porque compartilham o mesmo nome. O Job 3 (Trabalho 3) mostra o resultado carregado no trabalho anterior: - Baixa o artefato `homework`. 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 95e31e98e9..36c3292cfe 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 @@ -33,7 +33,7 @@ Todas as organizações têm um único grupo de executores auto-hospedados padr Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão quando criados e só podem ser membros de um grupo por vez. Você pode mover um executor do grupo- padrão para qualquer grupo que você criar. -Ao criar um grupo, você deverá escolher uma política que defina quais repositórios têm acesso ao grupo do executor. É possível configurar um grupo do executor para ser acessível a uma lista específica de repositórios, todos repositórios privados ou todos os repositórios na organização. +Ao criar um grupo, você deverá escolher uma política que defina quais repositórios têm acesso ao grupo do executor. {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} @@ -42,10 +42,23 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit ![Adicionar grupo de executor](/assets/images/help/settings/actions-org-add-runner-group.png) 1 -Insira um nome para o seu grupo do seu executor e selecione uma política de acesso na lista suspensa **Acesso ao repositório**. +Enter a name for your runner group, and assign a policy for repository access. - ![Adicionar opções de grupo de executores](/assets/images/help/settings/actions-org-add-runner-group-options.png) -1 Clique em **Salvar grupo** para criar o grupo e aplicar a política. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to a specific list of repositories, all private repositories, or all repositories in the organization.{% endif %} + + {% warning %} + + **Aviso** + + {% indented_data_reference site.data.reusables.github-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 %} + + ![Adicionar opções de grupo de executores](/assets/images/help/settings/actions-org-add-runner-group-options.png) +1 +Clique em **Salvar grupo** para criar o grupo e aplicar a política. ### Criar um grupo de executor auto-hospedado para uma empresa @@ -53,7 +66,7 @@ As empresas podem adicionar seus executores auto-hospedados a grupos para gerenc Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão quando criados e só podem ser membros de um grupo por vez. Você pode atribuir o executor a um grupo específico durante o processo de registro, ou você pode mover o executor do grupo-padrão para um grupo personalizado. -Ao criar um grupo, é necessário escolher uma política que conceda acesso a todas as organizações da empresa ou escolher organizações específicas. +When creating a group, you must choose a policy that defines which organizations have access to the runner group. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -62,7 +75,19 @@ Ao criar um grupo, é necessário escolher uma política que conceda acesso a to 1. Clique em **Adicionar novo** e, em seguida, **Novo grupo**. ![Adicionar grupo de executor](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) -1. Insira um nome para o seu grupo do seu executor e selecione uma política de acesso na lista suspensa **Acesso à organização**. +1. Enter a name for your runner group, and assign a policy for organization access. + + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to all organizations in the enterprise or choose specific organizations.{% endif %} + + {% warning %} + + **Aviso** + + {% indented_data_reference site.data.reusables.github-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 %} ![Adicionar opções de grupo de executores](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png) 1. Clique em **Salvar grupo** para criar o grupo e aplicar a política. diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md index 573d92de1a..7d23c9b917 100644 --- a/translations/pt-BR/content/actions/index.md +++ b/translations/pt-BR/content/actions/index.md @@ -7,31 +7,40 @@ introLinks: reference: /actions/reference featuredLinks: guides: - - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/learn-github-actions + - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions gettingStarted: - /actions/managing-workflow-runs - /actions/hosting-your-own-runners + guideCards: + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/publishing-nodejs-packages + - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - /actions/reference/events-that-trigger-workflows + - /actions/learn-github-actions + - /actions/reference/context-and-expression-syntax-for-github-actions + - /actions/reference/workflow-commands-for-github-actions + - /actions/reference/environment-variables changelog: - - title: Self-Hosted Runner Group Access Changes + title: Remover comandos set-env e add-path em 16 de novembro + date: '2020-11-09' + href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ + - + title: Os últimos fluxos de trabalho do Ubuntu-20.04 + date: '2020-10-29' + href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 + - + title: Pré-visualização para MacOS Big Sur + date: '2020-10-29' + href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview + - + title: Alterações de acesso ao grupo de executores auto-hospedados date: '2020-10-16' href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ - - - title: Ability to change retention days for artifacts and logs - date: '2020-10-08' - href: https://github.blog/changelog/2020-10-08-github-actions-ability-to-change-retention-days-for-artifacts-and-logs - - - title: Deprecating set-env and add-path commands - date: '2020-10-01' - href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands - - - title: Fine-tune access to external actions - date: '2020-10-01' - href: https://github.blog/changelog/2020-10-01-github-actions-fine-tune-access-to-external-actions redirect_from: - /articles/automating-your-workflow-with-github-actions/ - /articles/customizing-your-project-with-github-actions/ @@ -54,107 +63,26 @@ versions: +{% assign actionsCodeExamples = site.data.variables.action_code_examples %} +{% if actionsCodeExamples %}
-

Mais guias

+

Exemplos de códigos

-
-
- -
-

Building and testing Node.js

-

Use GitHub Actions to power CI in your Node.js application.

-
- JavaScript/TypeScript - CI -
-
-
- {% octicon "workflow" class="flex-shrink-0" %} - /guides/building-and-testing-nodejs -
- -
-
- -
-

Building and testing Python

-

Use GitHub Actions to power CI in your Python application.

-
- Python - CI -
-
-
- {% octicon "workflow" class="flex-shrink-0" %} - /guides/building-and-testing-python -
- -
-
- -
-

Building and testing Java with Maven

-

Use GitHub Actions to power CI in your Java project with Maven.

-
- Java - CI -
-
-
- {% octicon "workflow" class="flex-shrink-0" %} - /guides/building-and-testing-java-with-maven -
- -
-
- -
-

Building and testing Java with Gradle

-

Use GitHub Actions to power CI in your Java project with Gradle.

-
- Java - CI -
-
-
- {% octicon "workflow" class="flex-shrink-0" %} - /guides/building-and-testing-java-with-gradle -
- -
-
- -
-

Building and testing Java with Ant

-

Use GitHub Actions to power CI in your Java project with Ant.

-
- Java - CI -
-
-
- {% octicon "workflow" class="flex-shrink-0" %} - /guides/building-and-testing-java-with-ant -
- -
-
- -
-

Publishing Node.js packages

-

Use GitHub Actions to push your Node.js package to GitHub Packages or npm.

-
- JavaScript/TypeScript - CI -
-
-
- {% octicon "workflow" class="flex-shrink-0" %} - /guides/publishing-nodejs-packages -
- -
+
+
- Mostrar todos os guias {% octicon "arrow-right" %} +
+ {% render 'code-example-card' for actionsCodeExamples as example %} +
+ + + +
+
{% octicon "search" width="24" %}
+

Desculpe, não há resultados para

+

Parece que não temos um exemplo que se encaixa no seu filtro.
Tente outro filtro ou adicione seu exemplo de código

+ Saiba como adicionar um exemplo de código {% octicon "arrow-right" %} +
+{% endif %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md index 7c7d0bac96..27acef164a 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -87,7 +87,7 @@ Para obter mais informações, consulte "[Usar o gerenciamento de versões para ### Usar entradas e saídas com uma ação -Uma ação geralmente aceita ou exige entradas e gera saídas que você pode usar. For example, an action might require you to specify a path to a file, the name of a label, or other data it will use as part of the action processing. +Uma ação geralmente aceita ou exige entradas e gera saídas que você pode usar. Por exemplo, uma ação pode exigir que você especifique um caminho para um arquivo, o nome de uma etiqueta ou outros dados que usará como parte do processamento da ação. Para ver as entradas e saídas de uma ação, verifique a `action.yml` ou `action.yaml` no diretório-raiz do repositório. diff --git a/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md index e7ebf1d5c6..99b803b1ab 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -34,7 +34,7 @@ O fluxo de trabalho é um procedimento automatizado que você adiciona ao seu re #### Eventos -Um evento é uma atividade específica que aciona um fluxo de trabalho. Por exemplo, uma atividade pode originar de {% data variables.product.prodname_dotcom %} quando alguém faz o push de um commit em um repositório ou quando são criados um problema ou um pull request. You can also use the [repository dispatch webhook](/rest/reference/repos#create-a-repository-dispatch-event) to trigger a workflow when an external event occurs. Para obter uma lista completa de eventos que podem ser usados para acionar fluxos de trabalho, consulte [Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows). +Um evento é uma atividade específica que aciona um fluxo de trabalho. Por exemplo, uma atividade pode originar de {% data variables.product.prodname_dotcom %} quando alguém faz o push de um commit em um repositório ou quando são criados um problema ou um pull request. Também é possível usar o [webhook de envio de repositórios](/rest/reference/repos#create-a-repository-dispatch-event) para acionar um fluxo de trabalho quando ocorre um evento externo. Para obter uma lista completa de eventos que podem ser usados para acionar fluxos de trabalho, consulte [Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows). #### Trabalhos @@ -42,7 +42,7 @@ Um trabalho é um conjunto de etapas executadas no mesmo executor. Por padrão, #### Etapas -Uma etapa é uma tarefa individual que pode executar comandos (conhecidos como _ações_). Cada etapa de um trabalho é executada no mesmo executor, permitindo que as ações naquele trabalho compartilhem dados entre si. +Uma etapa é uma tarefa individual que pode executar comandos em um trabalho. Uma etapa pode ser uma _ação_ ou um comando de shell. Cada etapa de um trabalho é executada no mesmo executor, permitindo que as ações naquele trabalho compartilhem dados entre si. #### Ações @@ -50,7 +50,7 @@ _Ações_ são comandos autônomos combinados em _etapas_ para criar um _trabalh #### Executores -Um executor é um servidor com a aplicação de executor de {% data variables.product.prodname_actions %} instalada. Você pode usar um executor hospedado em {% data variables.product.prodname_dotcom %} ou você pode hospedar seu próprio. Um executor escuta trabalhos disponíveis, executa um trabalho de cada vez e relata o progresso, os registros e os resultados de volta para {% data variables.product.prodname_dotcom %}. Para executores hospedados em {% data variables.product.prodname_dotcom %}, cada trabalho em um fluxo de trabalho é executado em um novo ambiente virtual. +Um executor é um servidor que tem o[aplicativo do executor de {% data variables.product.prodname_actions %}](https://github.com/actions/runner) instalado. Você pode usar um executor hospedado em {% data variables.product.prodname_dotcom %} ou você pode hospedar seu próprio. Um executor escuta trabalhos disponíveis, executa um trabalho de cada vez e relata o progresso, os registros e os resultados de volta para {% data variables.product.prodname_dotcom %}. Para executores hospedados em {% data variables.product.prodname_dotcom %}, cada trabalho em um fluxo de trabalho é executado em um novo ambiente virtual. Os executores hospedados em {% data variables.product.prodname_dotcom %}runners são baseados no Ubuntu Linux, Microsoft Windows e macOS. Para informações sobre executores hospedados em {% data variables.product.prodname_dotcom %}, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}-](/actions/reference/virtual-environments-for-github-hosted-runners)". Se você precisar de um sistema operacional diferente ou precisar de uma configuração de hardware específica, você poderá hospedar seus próprios executores. Para obter informações sobre executores auto-hospedados, consulte "[Hospedar seus próprios executores](/actions/hosting-your-own-runners)". @@ -197,7 +197,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui #### Visualizar o arquivo de fluxo de trabalho -Neste diagrama, você pode ver o arquivo de fluxo de trabalho que acabou de criar e como os componentes de {% data variables.product.prodname_actions %} estão organizados em uma hierarquia. Cada etapa executa uma única ação. As etapas 1 e 2 usam ações de comunidade pré-criadas. Para encontrar mais ações pré-criadas para seus fluxos de trabalho, consulte "[Encontrar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)". +Neste diagrama, você pode ver o arquivo de fluxo de trabalho que acabou de criar e como os componentes de {% data variables.product.prodname_actions %} estão organizados em uma hierarquia. Cada etapa executa uma única ação ou comando de shell. As etapas 1 e 2 usam ações de comunidade pré-criadas. As etapas 3 e 4 executam comandos de shell diretamente no executor. Para encontrar mais ações pré-criadas para seus fluxos de trabalho, consulte "[Encontrar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)". ![Visão geral do fluxo de trabalho](/assets/images/help/images/overview-actions-event.png) diff --git a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md index 95fa953742..877ed92f90 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -57,7 +57,7 @@ jobs: needs: build runs-on: ubuntu-latest steps: - - run: ./test_server.sh + - run: ./test_server.sh ``` Para obter mais informações, consulte [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). @@ -106,7 +106,7 @@ jobs: ``` {% endraw %} -Para obter mais informações, consulte "[Memorizando dependências para acelerar fluxos de trabalho](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)". +Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". ### Usar bancos de dados e contêineres de serviço diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index bfd0cd507d..a7bdcbea7d 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions -Para obter mais informações, consulte "[Memorizando dependências para acelerar fluxos de trabalho](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)". +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". {% data variables.product.prodname_actions %} não tem o equivalente ao Docker Layer Caching (DLC) do CircleCI. diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 19a18a6325..71c29a33c7 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -262,7 +262,7 @@ jobs: runs-on: ubuntu-latest steps: - run: echo "This job will be run first, in parallel with build_a" - + test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] @@ -346,7 +346,7 @@ jobs: -Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/guides/caching-dependencies-to-speed-up-workflows)". +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". ### Artefatos @@ -367,7 +367,7 @@ GitLab CI/CD {% raw %} ```yaml -script: +script: artifacts: paths: - math-homework.txt @@ -414,7 +414,7 @@ GitLab CI/CD container-job: variables: POSTGRES_PASSWORD: postgres - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port @@ -423,10 +423,10 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - npm ci - # Runs a script that creates a PostgreSQL client, + # Runs a script that creates a PostgreSQL client, # populates the client with data, and retrieves data - node client.js tags: @@ -452,7 +452,7 @@ jobs: - name: Check out repository code uses: actions/checkout@v2 - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - name: Install dependencies run: npm ci @@ -462,7 +462,7 @@ jobs: # populates the client with data, and retrieves data run: node client.js env: - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 3f2ec972ac..ec1ff5e102 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -1,6 +1,6 @@ --- -title: Migrating from Travis CI to GitHub Actions -intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.' +title: Migrar do Travis CI para o GitHub Actions +intro: '{% data variables.product.prodname_actions %} e o Travis CI compartilham várias semelhanças, o que ajuda a tornar relativamente fácil a migração para {% data variables.product.prodname_actions %}.' redirect_from: - /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions versions: @@ -10,48 +10,48 @@ versions: ### Introdução -This guide helps you migrate from Travis CI to {% data variables.product.prodname_actions %}. It compares their concepts and syntax, describes the similarities, and demonstrates their different approaches to common tasks. +Este guia ajuda a você a fazer a migração do Travis CI para {% data variables.product.prodname_actions %}. Ele compara os seus conceitos e sintaxe, descreve as semelhanças e demonstra as suas diferentes abordagens em relação às tarefas comuns. -### Before you start +### Antes de começar -Before starting your migration to {% data variables.product.prodname_actions %}, it would be useful to become familiar with how it works: +Antes de iniciar sua migração para {% data variables.product.prodname_actions %}, seria importante familiarizar-se com a forma como funciona: -- For a quick example that demonstrates a {% data variables.product.prodname_actions %} job, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)." -- To learn the essential {% data variables.product.prodname_actions %} concepts, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)." +- Para um exemplo rápido que demonstra um trabalho de {% data variables.product.prodname_actions %}, consulte "[Início rápido para {% data variables.product.prodname_actions %}](/actions/quickstart)". +- Para aprender os conceitos básicos de {% data variables.product.prodname_actions %}, consulte "[Introdução ao GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)". -### Comparing job execution +### Comparar a execução do trabalho -To give you control over when CI tasks are executed, a {% data variables.product.prodname_actions %} _workflow_ uses _jobs_ that run in parallel by default. Each job contains _steps_ that are executed in a sequence that you define. If you need to run setup and cleanup actions for a job, you can define steps in each job to perform these. +Para dar controle a você sobre quando as tarefas de CI são executadas, um _fluxo de trabalho_ de {% data variables.product.prodname_actions %} usa _trabalhos_ que são executados em paralelo por padrão. Cada trabalho contém _etapas_ que são executadas em uma sequência que você define. Se você precisa executar a configuração e a limpeza de ações para um trabalho, você pode definir etapas em cada trabalho para executá-las. -### Key similarities +### Principais semelhanças -{% data variables.product.prodname_actions %} and Travis CI share certain similarities, and understanding these ahead of time can help smooth the migration process. +{% data variables.product.prodname_actions %} e o Travis CI compartilham certas semelhanças e entendê-las antecipadamente pode ajudar a agilizar o processo de migração. -#### Using YAML syntax +#### Usar a sintaxe de YAML -Travis CI and {% data variables.product.prodname_actions %} both use YAML to create jobs and workflows, and these files are stored in the code's repository. For more information on how {% data variables.product.prodname_actions %} uses YAML, see ["Creating a workflow file](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)." +O Travis CI e o {% data variables.product.prodname_actions %} usam o YAML para criar trabalhos e fluxos de trabalho, e esses arquivos são armazenados no repositório do código. Para obter mais informações sobre como o {% data variables.product.prodname_actions %} usa o YAML, consulte ["Criar um arquivo de fluxo de trabalho](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)". -#### Custom environment variables +#### Variáveis de ambiente personalizadas -Travis CI lets you set environment variables and share them between stages. Similarly, {% data variables.product.prodname_actions %} lets you define environment variables for a step, job, or workflow. For more information, see ["Environment variables](/actions/reference/environment-variables)." +O Travis CI permite que você defina variáveis de ambiente e compartilhe-as entre stages. Da mesma forma, {% data variables.product.prodname_actions %} permite definir variáveis de ambiente para uma etapa, um trabalho ou um fluxo de trabalho. Para obter mais informações, consulte ["Variáveis de ambiente](/actions/reference/environment-variables)". #### Variáveis padrão de ambiente -Travis CI and {% data variables.product.prodname_actions %} both include default environment variables that you can use in your YAML files. For {% data variables.product.prodname_actions %}, you can see these listed in "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)." +O Travis CI e {% data variables.product.prodname_actions %} incluem variáveis de ambiente padrão que você pode usar nos seus arquivos de YAML. Para {% data variables.product.prodname_actions %}, você pode ver estes listados em "[Variáveis de ambiente padrão](/actions/reference/environment-variables#default-environment-variables)". #### Processamento paralelo do trabalho -Travis CI can use `stages` to run jobs in parallel. Similarly, {% data variables.product.prodname_actions %} runs `jobs` in parallel. For more information, see "[Creating dependent jobs](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)." +O Travis CI pode usar `stages` para executar trabalhos em paralelo. Da mesma forma, {% data variables.product.prodname_actions %} executa `trabalhos` em paralelo. Para obter mais informações, consulte "[Criar trabalhos dependentes](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)". -#### Status badges +#### Selos de status -Travis CI and {% data variables.product.prodname_actions %} both support status badges, which let you indicate whether a build is passing or failing. For more information, see ["Adding a workflow status badge to your repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." +O Travis CI e {% data variables.product.prodname_actions %} são compatíveis com selos de status, o que permite que você indique se uma criação está sendo aprovada ou falhando. Para obter mais informações, consulte ["Adicionar um selo de status de fluxo de trabalho ao seu repositório](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". #### Usar uma matriz de criação -Travis CI and {% data variables.product.prodname_actions %} both support a build matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a build matrix](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +O Travis CI e {% data variables.product.prodname_actions %} são compatíveis com uma matriz de criação, o que permite que você realize testes usando combinações de sistemas operacionais e pacotes de software. Para obter mais informações, consulte "[Usar uma matriz de criação](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)". -Below is an example comparing the syntax for each system: +Abaixo, há um exemplo de comparação da sintaxe para cada sistema: @@ -87,9 +87,9 @@ jobs:
-#### Targeting specific branches +#### Apontar para branches específicos -Travis CI and {% data variables.product.prodname_actions %} both allow you to target your CI to a specific branch. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". +O Travis CI e {% data variables.product.prodname_actions %} permitem que você aponte a sua CI para um branch específico. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". Abaixo, há um exemplo da sintaxe para cada sistema: @@ -127,9 +127,9 @@ on: -#### Checking out submodules +#### Verificar submódulos -Travis CI and {% data variables.product.prodname_actions %} both allow you to control whether submodules are included in the repository clone. +O Travis CI e {% data variables.product.prodname_actions %} permitem que você controle se os submódulos estão incluídos no clone do repositório. Abaixo, há um exemplo da sintaxe para cada sistema: @@ -163,39 +163,45 @@ git: -### Key features in {% data variables.product.prodname_actions %} +#### Usando variáveis de ambiente em uma matriz -When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}: +Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. + +In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} + +### Principais recursos em {% data variables.product.prodname_actions %} + +Ao fazer a migração do Travis CI, considere os recursos principais a seguir em {% data variables.product.prodname_actions %}: #### Armazenar segredos -{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} also includes policies that allow you to limit access to secrets at the repository and organization level. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +{% data variables.product.prodname_actions %} permite armazenar segredos e referenciá-los em seus trabalhos. {% data variables.product.prodname_actions %} também inclui políticas que permitem limitar o acesso a segredos no nível do repositório e da organização. Para obter mais informações, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)". -#### Sharing files between jobs and workflows +#### Compartilhar arquivos entre trabalhos e fluxos de trabalho -{% data variables.product.prodname_actions %} includes integrated support for artifact storage, allowing you to share files between jobs in a workflow. You can also save the resulting files and share them with other workflows. For more information, see "[Sharing data between jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)." +{% data variables.product.prodname_actions %} inclui suporte integrado para o armazenamento de artefatos, permitindo que você compartilhe arquivos entre os trabalhos de um fluxo de trabalho. Você também pode salvar os arquivos resultantes e compartilhá-los com outros fluxos de trabalho. Para obter mais informações, consulte "[Compartilhar dados entre trabalhos](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)". #### Hospedar seus próprios executores -If your jobs require specific hardware or software, {% data variables.product.prodname_actions %} allows you to host your own runners and send your jobs to them for processing. {% data variables.product.prodname_actions %} also lets you use policies to control how these runners are accessed, granting access at the organization or repository level. For more information, see ["Hosting your own runners](/actions/hosting-your-own-runners)." +Se os seus trabalhos exigirem hardware ou software específico, {% data variables.product.prodname_actions %} permitirá que você hospede seus próprios executores e envie seus trabalhos para eles processarem. {% data variables.product.prodname_actions %} também permite usar políticas para controlar como esses executores são acessados, concedendo acesso ao nível da organização ou do repositório. Para obter mais informações, consulte ["Hospedar seus próprios executores](/actions/hosting-your-own-runners)". -#### Concurrent jobs and execution time +#### Trabalhos simultâneos e tempo de execução -The concurrent jobs and workflow execution times in {% data variables.product.prodname_actions %} can vary depending on your {% data variables.product.company_short %} plan. Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration)." +Os trabalhos simultâneos e os tempos de execução do fluxo de trabalho em {% data variables.product.prodname_actions %} podem variar dependendo do seu plano de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration)". -#### Using different languages in {% data variables.product.prodname_actions %} +#### Usar diferentes linguagens em {% data variables.product.prodname_actions %} -When working with different languages in {% data variables.product.prodname_actions %}, you can create a step in your job to set up your language dependencies. For more information about working with a particular language, see the specific guide: +Ao trabalhar com diferentes linguagens em {% data variables.product.prodname_actions %}, você pode criar uma etapa no seu trabalho para configurar as dependências da sua linguagem. Para obter mais informações sobre como trabalhar com uma linguagem em particular, consulte o guia específico: - [Criar e testar Node.js](/actions/guides/building-and-testing-nodejs) - - [Building and testing PowerShell](/actions/guides/building-and-testing-powershell) + - [Criar e testar PowerShell](/actions/guides/building-and-testing-powershell) - [Criar e testar o Python](/actions/guides/building-and-testing-python) - [Criar e estar o Java com o Maven](/actions/guides/building-and-testing-java-with-maven) - [Criar e estar o Java com o Gradle](/actions/guides/building-and-testing-java-with-gradle) - [Criar e estar o Java com o Ant](/actions/guides/building-and-testing-java-with-ant) -### Executing scripts +### Executar scripts -{% data variables.product.prodname_actions %} can use `run` steps to run scripts or shell commands. To use a particular shell, you can specify the `shell` type when providing the path to the script. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)". +{% data variables.product.prodname_actions %} pode usar as etapas de `executar` para executar scripts ou comandos de shell. Para usar um shell específico, você pode especificar o tipo de `shell` ao fornecer o caminho para o script. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)". Por exemplo: @@ -206,23 +212,23 @@ Por exemplo: shell: bash ``` -### Error handling in {% data variables.product.prodname_actions %} +### Manuseio de erros em {% data variables.product.prodname_actions %} -When migrating to {% data variables.product.prodname_actions %}, there are different approaches to error handling that you might need to be aware of. +Ao migrar para {% data variables.product.prodname_actions %}, existem diferentes abordagens para a manipulação de erros das quais você precisa estar ciente. -#### Script error handling +#### Manipulação de erros de script -{% data variables.product.prodname_actions %} stops a job immediately if one of the steps returns an error code. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)". +{% data variables.product.prodname_actions %} interrompe um trabalho imediatamente se uma das etapas retornar um código de erro. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)". -#### Job error handling +#### Manipulação de erro de trabalho -{% data variables.product.prodname_actions %} uses `if` conditionals to execute jobs or steps in certain situations. For example, you can run a step when another step results in a `failure()`. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)". You can also use [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) to prevent a workflow run from stopping when a job fails. +{% data variables.product.prodname_actions %} usa condicionais do tipo `se` para executar trabalhos ou etapas em certas situações. Por exemplo, você pode executar um passo quando outro passo resulta em uma `failure()`. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)". Você também pode usar [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) para impedir que uma execução de um fluxo de trabalho seja interrompida quando um trabalho falhar. -### Migrating syntax for conditionals and expressions +### Migrar a sintaxe para condicionais e expressões -To run jobs under conditional expressions, Travis CI and {% data variables.product.prodname_actions %} share a similar `if` condition syntax. {% data variables.product.prodname_actions %} lets you use the `if` conditional to prevent a job or step from running unless a condition is met. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". +Para executar trabalhos sob expressões condicionais, o Travis CI e {% data variables.product.prodname_actions %} compartilham uma sintaxe condicional do tipo `se` similar. {% data variables.product.prodname_actions %} permite que você use a condicional do tipo `se` para evitar que um trabalho ou etapa seja executado, a menos que uma condição seja atendida. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -This example demonstrates how an `if` conditional can control whether a step is executed: +Este exemplo demonstra como uma condicional do tipo `se` pode controlar se uma etapa é executada: ```yaml jobs: @@ -233,9 +239,9 @@ jobs: if: env.str == 'ABC' && env.num == 123 ``` -### Migrating phases to steps +### Migrar fases para etapas -Where Travis CI uses _phases_ to run _steps_, {% data variables.product.prodname_actions %} has _steps_ which execute _actions_. You can find prebuilt actions in the [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. Para obter mais informações, consulte "[Criar ações](/actions/building-actions)". +Quando o Travis CI usa _fases_ para executar _etapas_, {% data variables.product.prodname_actions %} tem _etapas_ que executam _ações_. Você pode encontrar ações pré-criadas no [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), ou você pode criar as suas próprias ações. Para obter mais informações, consulte "[Criar ações](/actions/building-actions)". Abaixo, há um exemplo da sintaxe para cada sistema: @@ -281,7 +287,7 @@ trabalhos: ### Memorizar dependências -Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. +O Travis CI e {% data variables.product.prodname_actions %} permitem que você armazene as as dependências em cache manualmente para reutilização posterior. Esse exemplo demonstra a sintaxe do cache para cada sistema. @@ -316,15 +322,15 @@ cache: npm
-Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/guides/caching-dependencies-to-speed-up-workflows)". +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". ### Exemplos de tarefas comuns -This section compares how {% data variables.product.prodname_actions %} and Travis CI perform common tasks. +Esta seção compara como {% data variables.product.prodname_actions %} e o Travis CI realizam tarefas comuns. -#### Configuring environment variables +#### Configurar variáveis de ambiente -You can create custom environment variables in a {% data variables.product.prodname_actions %} job. Por exemplo: +Você pode criar variáveis de ambiente personalizadas em uma tarefa de {% data variables.product.prodname_actions %}. Por exemplo: @@ -357,7 +363,7 @@ env:
-#### Building with Node.js +#### Criar com Node.js @@ -405,4 +411,4 @@ jobs: ### Próximas etapas -To continue learning about the main features of {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +Para continuar aprendendo sobre os principais recursos de {% data variables.product.prodname_actions %}, consulte "[Aprender {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". diff --git a/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 3f579e27c2..0dd84827a9 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -26,7 +26,7 @@ Os segredos usam [caixas fechadas de Libsodium](https://libsodium.gitbook.io/doc Para ajudar a prevenir a divulgação acidental, o {% data variables.product.product_name %} usa um mecanismo que tenta redigir quaisquer segredos que aparecem nos registros de execução. Esta redação procura correspondências exatas de quaisquer segredos configurados, bem como codificações comuns dos valores, como Base64. No entanto, como há várias maneiras de transformar o valor de um segredo, essa anulação não é garantida. Como resultado, existem certas etapas proativas e boas práticas que você deve seguir para ajudar a garantir que os segredos sejam editados, e para limitar outros riscos associados aos segredos: - **Nunca usar dados estruturados como um segredo** - - Structured data can cause secret redaction within logs to fail, because redaction largely relies on finding an exact match for the specific secret value. Por exemplo, não use um blob de JSON, XML, ou YAML (ou similar) para encapsular o valor de um segredo, já que isso reduz significativamente a probabilidade de os segredos serem devidamente redigidos. Em vez disso, crie segredos individuais para cada valor sensível. + - Os dados estruturados podem fazer com que ocorra uma falha nos registros de segredos, pois a redação depende, em grande parte, de encontrar uma correspondência exata para o valor específico do segredo. Por exemplo, não use um blob de JSON, XML, ou YAML (ou similar) para encapsular o valor de um segredo, já que isso reduz significativamente a probabilidade de os segredos serem devidamente redigidos. Em vez disso, crie segredos individuais para cada valor sensível. - **Registre todos os segredos usados nos fluxos de trabalho** - Se um segredo for usado para gerar outro valor sensível dentro de um fluxo de trabalho, esse valor gerado deve ser formalmente [registrado como um segredo](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret) para que seja reproduzido se alguma vez aparecer nos registros. Por exemplo, se, ao usar uma chave privada para gerar um JWT assinado para acessar uma API web, certifique-se de registrar que JWT é um segredo ou não será redigido se entrar na saída de do registro. - O registro de segredos também aplica-se a qualquer tipo de transformação/codificação. Se seu segredo foi transformado de alguma forma (como Base64 ou URL codificada), certifique-se de registrar o novo valor como um segredo também. @@ -98,7 +98,7 @@ Você também deve considerar o ambiente das máquinas de executores auto-hosped ### Auditar eventos de {% data variables.product.prodname_actions %} -Você pode usar o log de auditoria para monitorar tarefas administrativas em uma organização. The audit log records the type of action, when it was run, and which user account performed the action. +Você pode usar o log de auditoria para monitorar tarefas administrativas em uma organização. O log de auditoria registra o tipo de ação, quando foi executado, e qual conta de usuário executou a ação. Por exemplo, você pode usar o log de auditoria para monitorar o evento de `action:org.update_actions_secret`, que controla as alterações nos segredos da organização: ![Entradas do log de auditoria](/assets/images/help/repository/audit-log-entries.png) @@ -129,6 +129,6 @@ As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_a | `action:org.runner_group_removed` | Acionado quando um administrador da organização remove um grupo de executores auto-hospedados. | | `action:org.runner_group_renamed` | Acionado quando um administrador da organização renomeia um grupo de executores auto-hospedados. | | `action:org.runner_group_runners_added` | Acionada quando um administrador da organização [adiciona um executor auto-hospedado a um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +| `action:org.runner_group_runners_removed` | Acionado quando um administrador da organização remove um grupo de executores auto-hospedados. | diff --git a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index e8626f46a9..75e45c99f4 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -14,7 +14,7 @@ versions: ### Visão Geral -Se você precisar compartilhar fluxos de trabalho e outros recursos de {% data variables.product.prodname_actions %} com a sua equipe, considere colaborar dentro de uma organização de {% data variables.product.prodname_dotcom %}. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. Você também pode criar modelos de fluxo de trabalho no repositório `.github` e compartilhá-los com outros usuários na sua organização. +Se você precisar compartilhar fluxos de trabalho e outros recursos de {% data variables.product.prodname_actions %} com a sua equipe, considere colaborar dentro de uma organização de {% data variables.product.prodname_dotcom %}. Uma organização permite que você armazene e gerencie, centralizadamente, segredos, artefatos e executores auto-hospedados. Você também pode criar modelos de fluxo de trabalho no repositório `.github` e compartilhá-los com outros usuários na sua organização. ### Criar um modelo do fluxo de trabalho diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 75661c7e25..ebc6a5002c 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -10,9 +10,9 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Configuring a workflow to run manually +### Configurar um fluxo de trabalho para ser executado manualmente -Para executar um fluxo de trabalho manualmente, o fluxo de trabalho deve ser configurado para ser executado no evento `workflow_dispatch`. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". +Para executar um fluxo de trabalho manualmente, o fluxo de trabalho deve ser configurado para ser executado no evento `workflow_dispatch`. Para obter mais informações sobre a configuração do evento `workflow_despatch`, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". ### Executar um fluxo de trabalho em {% data variables.product.prodname_dotcom %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md index c68ead7ac9..8374c0bc65 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -10,7 +10,7 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 39f2e7c610..eac8188e84 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -14,7 +14,7 @@ Na página de execução de fluxo de trabalho, você pode verificar se a execuç Se a execução estiver concluída, será possível ver se o resultado teve êxito, se houve falha, se foi cancelado ou se ficou neutro. Em caso de falha, você poderá exibir e pesquisar os logs de criação para diagnosticar a falha e executar o fluxo de trabalho novamente. Você também pode visualizar os minutos da execução do trabalho faturável ou fazer o download dos registros e criar artefatos. -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](/v3/checks/)". +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 %} diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md index 1388f9bd77..9da0b4a78c 100644 --- a/translations/pt-BR/content/actions/quickstart.md +++ b/translations/pt-BR/content/actions/quickstart.md @@ -73,3 +73,69 @@ O fluxo de trabalho do super-linter que você acabou de adicionar é executado s - "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para obter um tutorial aprofundado - "[Guias](/actions/guides)" para casos e exemplos específicos de uso - [github/super-linter](https://github.com/github/super-linter) para obter mais informações sobre a configuração da ação de Super-Linter + + diff --git a/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md b/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md index a85cc79130..3362ce34d1 100644 --- a/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md @@ -79,7 +79,7 @@ Você pode usar o `GITHUB_TOKEN` para fazer chamadas de API autenticada. Este ex ### Permissões para o `GITHUB_TOKEN` -Para obter informações sobre os pontos de extremidade da API que {% data variables.product.prodname_github_apps %} pode acessar com cada permissão, consulte "[Permissões de {% data variables.product.prodname_github_app %}](/v3/apps/permissions/). " +Para obter informações sobre os pontos de extremidade da API que {% data variables.product.prodname_github_apps %} pode acessar com cada permissão, consulte "[Permissões de {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps). " | Permissão | Tipo de acesso | Acesso pelos repositórios bifurcados | | ----------------------- | ---------------- | ------------------------------------ | diff --git a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md index fd52b14239..79537ed880 100644 --- a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -59,7 +59,7 @@ Os contextos são uma forma de acessar informações sobre execuções de fluxo | ---------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `github` | `objeto` | Informações sobre a execução do fluxo de trabalho. Para obter mais informações, consulte [contexto `github`](#github-context). | | `env` | `objeto` | Contém variáveis de ambiente definidas em um fluxo de trabalho, trabalho ou etapa. Para obter mais informações, consulte o contexto contexto [`env`](#env-context). | -| `trabalho` | `objeto` | Tem informações sobre o trabalho em execução no momento. Para obter mais informações, consulte [contexto `trabalho`](#job-context). | +| `job` | `objeto` | Tem informações sobre o trabalho em execução no momento. Para obter mais informações, consulte [contexto `trabalho`](#job-context). | | `steps` | `objeto` | Informações sobre as etapas que foram executadas neste trabalho. Para obter mais informações, consulte [contexto `etapas`](#steps-context). | | `runner` | `objeto` | Informações sobre o executor do trabalho atual. Para obter mais informações, consulte [`runner` context](#runner-context). | | `secrets` | `objeto` | Habilita o acesso a segredos. Para obter mais informações sobre segredos, consulte "[Criar e usar segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". | @@ -123,7 +123,7 @@ O contexto `job` (trabalho) contém informações sobre o trabalho atualmente em | Nome da propriedade | Tipo | Descrição | | ----------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `trabalho` | `objeto` | Esse contexto altera cada trabalho em uma execução de fluxo de trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho. | +| `job` | `objeto` | Esse contexto altera cada trabalho em uma execução de fluxo de trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho. | | `job.container` | `objeto` | Informações sobre o contêiner do trabalho. Para obter mais informações sobre contêineres, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)". | | `job.container.id` | `string` | Identificação do contêiner. | | `job.container.network` | `string` | Identificação da rede do contêiner. O executor cria a rede usada por todos os contêineres em um trabalho. | diff --git a/translations/pt-BR/content/actions/reference/encrypted-secrets.md b/translations/pt-BR/content/actions/reference/encrypted-secrets.md index 5efcfc19b5..e624cd1cf8 100644 --- a/translations/pt-BR/content/actions/reference/encrypted-secrets.md +++ b/translations/pt-BR/content/actions/reference/encrypted-secrets.md @@ -43,11 +43,11 @@ Você pode usar e ler segredos encriptados em um arquivo de fluxo de trabalho se {% endwarning %} -Você também pode gerenciar segredos usando o API REST. Para obter mais informações, consulte "[Segredos](/v3/actions/secrets/)". +Você também pode gerenciar segredos usando o API REST. Para obter mais informações, consulte "[Segredos](/rest/reference/actions#secrets)". #### Permissões limitadas de credenciais -Ao gerar credenciais, recomendamos que você conceda as permissões mínimas possíveis. Por exemplo, em vez de usar credenciais pessoais, use [chaves de implantação](/v3/guides/managing-deploy-keys/#deploy-keys) ou uma conta de serviço. Considere conceder permissões somente leitura se isso o necessário e limite o acesso tanto quanto possível. Ao gerar um token de acesso pessoal (PAT), selecione o menor escopo necessário. +Ao gerar credenciais, recomendamos que você conceda as permissões mínimas possíveis. Por exemplo, em vez de usar credenciais pessoais, use [chaves de implantação](/developers/overview/managing-deploy-keys#deploy-keys) ou uma conta de serviço. Considere conceder permissões somente leitura se isso o necessário e limite o acesso tanto quanto possível. Ao gerar um token de acesso pessoal (PAT), selecione o menor escopo necessário. ### Criar segredos encriptados para um repositório diff --git a/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md index 0cc799e2f7..29e172067e 100644 --- a/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md @@ -100,7 +100,7 @@ Você pode acionar manualmente uma execução de fluxo de trabalho usando a API ##### Exemplo -To use the `workflow_dispatch` event, you need to include it as a trigger in your GitHub Actions workflow file. The example below only runs the workflow when it's manually triggered: +Para usar o evento `workflow_dispatch`, é necessário incluí-lo como um gatilho no seu arquivo de fluxo de trabalho do GitHub Actions. O exemplo abaixo só executa o fluxo de trabalho quando é acionado manualmente: ```yaml on: workflow_dispatch @@ -108,7 +108,7 @@ on: workflow_dispatch ##### Exemplo de configuração de fluxo de trabalho -Este exemplo define o nome `` e `entradas de` domésticas e as imprime usando os contextos `github.event.inputs.name` e `github.event.inputs.home` . If a `home` isn't provided, the default value 'The Octoverse' is printed. +Este exemplo define o nome `` e `entradas de` domésticas e as imprime usando os contextos `github.event.inputs.name` e `github.event.inputs.home` . Se `home` não for fornecido, será impresso o valor-padrão 'The Octoverse'. {% raw %} ```yaml @@ -143,7 +143,7 @@ jobs: {% data reusables.github-actions.branch-requirement %} -Você pode usar a API do {% data variables.product.product_name %} para acionar um evento do webhook denominado [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) quando quiser acionar um fluxo de trabalho para uma atividade que ocorre fora do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Criar um evento de despacho de repositório](/v3/repos/#create-a-repository-dispatch-event)." +Você pode usar a API do {% data variables.product.product_name %} para acionar um evento do webhook denominado [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) quando quiser acionar um fluxo de trabalho para uma atividade que ocorre fora do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Criar um evento de envio do repositório](/rest/reference/repos#create-a-repository-dispatch-event)". Para acionar o evento webhook `repository_dispatch` personalizado, envie uma solicitação `POST` para um ponto de extremidade da API do {% data variables.product.product_name %} e forneça um nome de `event_type` para descrever o tipo de atividade. Para acionar a execução de um fluxo de trabalho, configure também o fluxo de trabalho para usar o evento `repository_dispatch`. @@ -163,7 +163,7 @@ em: #### `check_run` -Executa o fluxo de trabalho sempre que o evento `check_run` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Execuções de verificação](/v3/checks/runs/)". +Executa o fluxo de trabalho sempre que o evento `check_run` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Execuções de verificação](/rest/reference/checks#runs)". {% data reusables.github-actions.branch-requirement %} @@ -183,7 +183,7 @@ on: #### `check_suite` -Executa o fluxo de trabalho sempre que o evento `check_suite` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Conjuntos de verificações](/v3/checks/suites/)". +Executa o fluxo de trabalho sempre que o evento `check_suite` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Conjuntos de verificações](/rest/reference/checks#suites)". {% data reusables.github-actions.branch-requirement %} @@ -209,7 +209,7 @@ on: #### `create` -Executa o fluxo de trabalho sempre que alguém cria um branch ou tag, o que aciona o evento `create`. Para obter informações sobre a API REST, consulte "[Criar uma referência](/v3/git/refs/#create-a-reference)". +Executa o fluxo de trabalho sempre que alguém cria um branch ou tag, o que aciona o evento `create`. Para obter informações sobre a API REST, consulte "[Criar uma referência](/rest/reference/git#create-a-reference)". | Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------- | ------------------ | ------------------------------------- | -------------------- | @@ -224,7 +224,7 @@ on: #### `delete` -Executa o fluxo de trabalho sempre que alguém exclui um branch ou tag, o que aciona o evento `delete`. Para obter informações sobre a API REST, consulte "[Excluir uma referência](/v3/git/refs/#delete-a-reference)". +Executa o fluxo de trabalho sempre que alguém exclui um branch ou tag, o que aciona o evento `delete`. Para obter informações sobre a API REST, consulte "[Excluir uma referência](/rest/reference/git#delete-a-reference)". {% data reusables.github-actions.branch-requirement %} @@ -271,7 +271,7 @@ on: #### `bifurcação` -Executa o fluxo de trabalho sempre que alguém bifurca um repositório, o que aciona o evento `fork`. Para obter informações sobre a API REST, consulte "[Criar uma bifurcação](/v3/repos/forks/#create-a-fork)". +Executa o fluxo de trabalho sempre que alguém bifurca um repositório, o que aciona o evento `fork`. Para obter informações sobre a API REST, consulte "[Criar uma bifurcação](/rest/reference/repos#create-a-fork)". {% data reusables.github-actions.branch-requirement %} @@ -323,10 +323,11 @@ on: types: [created, deleted] ``` -The `issue_comment` event occurs for comments on both issues and pull requests. To determine whether the `issue_comment` event was triggered from an issue or pull request, you can check the event payload for the `issue.pull_request` property and use it as a condition to skip a job. +O evento `issue_comment` ocorre para comentários em ambos os problemas e pull requests. Para determinar se o evento `issue_comment` foi acionado a partir de um problema ou pull request, você poderá verificar a carga do evento para a propriedade `issue.pull_request` e usá-la como condição para ignorar um trabalho. -For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue. +Por exemplo, você pode optar por executar o trabalho `pr_commented` quando eventos de comentários ocorrem em um pull request e executar o trabalho `issue_commented` quando os eventos de comentários ocorrem em um problema. +{% raw %} ```yaml on: issue_comment @@ -349,10 +350,11 @@ jobs: - run: | echo "Comment on issue #${{ github.event.issue.number }}" ``` +{% endraw %} #### `Problemas` -Executa o fluxo de trabalho sempre que o evento `issues` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[problemas](/v3/issues)". +Executa o fluxo de trabalho sempre que o evento `issues` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[problemas](/rest/reference/issues)". {% data reusables.github-actions.branch-requirement %} @@ -372,7 +374,7 @@ on: #### `etiqueta` -Executa o fluxo de trabalho sempre que o evento `label` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Etiquetas](/v3/issues/labels/)". +Executa o fluxo de trabalho sempre que o evento `label` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Etiquetas](/rest/reference/issues#labels)". {% data reusables.github-actions.branch-requirement %} @@ -392,7 +394,7 @@ on: #### `marco` -Executa o fluxo de trabalho sempre que o evento `milestone` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Marcos](/v3/issues/milestones/)". +Executa o fluxo de trabalho sempre que o evento `milestone` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Marcos](/rest/reference/issues#milestones)". {% data reusables.github-actions.branch-requirement %} @@ -412,7 +414,7 @@ on: #### `page_build` -Executa o fluxo de trabalho sempre que alguém faz push em um branch habilitado para o {% data variables.product.product_name %} Pages, o que aciona o evento `page_build`. For information about the REST API, see "[Pages](/rest/reference/repos#pages)." +Executa o fluxo de trabalho sempre que alguém faz push em um branch habilitado para o {% data variables.product.product_name %} Pages, o que aciona o evento `page_build`. Para obter informações sobre a API REST, consulte "[Páginas](/rest/reference/repos#pages)". {% data reusables.github-actions.branch-requirement %} @@ -429,7 +431,7 @@ on: #### `project` -Executa o fluxo de trabalho sempre que o evento `project` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Projetos](/v3/projects/)". +Executa o fluxo de trabalho sempre que o evento `project` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Projetos](/rest/reference/projects)". {% data reusables.github-actions.branch-requirement %} @@ -449,7 +451,7 @@ on: #### `project_card` -Executa o fluxo de trabalho sempre que o evento `project_card` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Cartões de projeto](/v3/projects/cards)". +Executa o fluxo de trabalho sempre que o evento `project_card` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Cartões de projeto](/rest/reference/projects#cards)". {% data reusables.github-actions.branch-requirement %} @@ -469,7 +471,7 @@ on: #### `project_column` -Executa o fluxo de trabalho sempre que o evento `project_column` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Colunas do projeto](/v3/projects/columns)". +Executa o fluxo de trabalho sempre que o evento `project_column` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Colunas do projeto](/rest/reference/projects#columns)". {% data reusables.github-actions.branch-requirement %} @@ -489,7 +491,7 @@ on: #### `público` -Executa o fluxo de trabalho sempre que alguém torna público um repositório privado, o que aciona o evento `public`. Para obter informações sobre a API REST, consulte "[Editar repositórios](/v3/repos/#edit)". +Executa o fluxo de trabalho sempre que alguém torna público um repositório privado, o que aciona o evento `public`. Para obter informações sobre a API REST, consulte "[Editar repositórios](/rest/reference/repos#edit)". {% data reusables.github-actions.branch-requirement %} @@ -506,7 +508,7 @@ on: #### `pull_request` -Executa o fluxo de trabalho sempre que o evento `pull_request` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Pull requests](/v3/pulls)". +Executa o fluxo de trabalho sempre que o evento `pull_request` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Pull requests](/rest/reference/pulls)". {% note %} @@ -532,7 +534,7 @@ on: #### `pull_request_review` -Executa o fluxo de trabalho sempre que o evento `pull_request_review` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Revisões de pull request](/v3/pulls/reviews)". +Executa o fluxo de trabalho sempre que o evento `pull_request_review` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Revisões de pull request](/rest/reference/pulls#reviews)". | Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------- | ------------------------------------------------- | @@ -552,7 +554,7 @@ on: #### `pull_request_review_comment` -Executa o fluxo de trabalho sempre que um comentário no diff unificado de uma pull request é modificado, o que aciona o evento `pull_request_review_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte [Comentários da revisão](/v3/pulls/comments). +Executa o fluxo de trabalho sempre que um comentário no diff unificado de uma pull request é modificado, o que aciona o evento `pull_request_review_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte [Comentários da revisão](/rest/reference/pulls#comments). | Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------- | ------------------------------------------------- | @@ -570,6 +572,8 @@ on: {% data reusables.developer-site.pull_request_forked_repos_link %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + #### `pull_request_target` Este evento é semelhante ao `pull_request`, exceto que é executado no contexto do repositório-base do pull request, em vez de ser executado no commit de merge. Isso significa que você pode disponibilizar os seus segredos de forma mais segura nos fluxos de trabalho acionados pelo pull request, porque apenas os fluxos de trabalho definidos no commit no repositório-base são executados. Por exemplo, este evento permite que você crie fluxos de trabalho que etiquetam e façam comentários em pull requests, com base no conteúdo da carga do evento. @@ -587,11 +591,13 @@ on: pull_request_target types: [assigned, opened, synchronize, reopened] ``` +{% endif %} + #### `push` {% note %} -**Observação:** a carga de webhook disponível para o GitHub Actions não inclui os atributos `added`, `removed` e `modified` no objeto `commit`. É possível recuperar o objeto de commit completo usando a API REST. Para obter mais informações, consulte "[Obter um único commit](/v3/repos/commits/#get-a-single-commit)"". +**Observação:** a carga de webhook disponível para o GitHub Actions não inclui os atributos `added`, `removed` e `modified` no objeto `commit`. É possível recuperar o objeto de commit completo usando a API REST. Para obter mais informações, consulte "[Obter um único commit](/rest/reference/repos#get-a-single-commit)"". {% endnote %} @@ -634,7 +640,7 @@ em: {% endnote %} -Executa o fluxo de trabalho sempre que o evento `release` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Versões](/v3/repos/releases/)". +Executa o fluxo de trabalho sempre que o evento `release` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Versões](/rest/reference/repos#releases)". | Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | ------------- | @@ -652,7 +658,7 @@ on: #### `status` -Executa o fluxo de trabalho sempre que o status de um commit do Git muda, o que aciona o evento `status`. Para obter informações sobre a API REST, consulte [Status](/v3/repos/statuses/). +Executa o fluxo de trabalho sempre que o status de um commit do Git muda, o que aciona o evento `status`. Para obter informações sobre a API REST, consulte [Status](/rest/reference/repos#statuses). {% data reusables.github-actions.branch-requirement %} @@ -669,7 +675,7 @@ on: #### `inspecionar` -Executa o fluxo de trabalho sempre que o evento `watch` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Marcar com uma estrela](/v3/activity/starring/)". +Executa o fluxo de trabalho sempre que o evento `watch` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Marcar com uma estrela](/rest/reference/activity#starring)". {% data reusables.github-actions.branch-requirement %} @@ -687,6 +693,8 @@ on: types: [started] ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + #### `workflow_run` {% data reusables.webhooks.workflow_run_desc %} @@ -709,6 +717,8 @@ on: - requested ``` +{% endif %} + ### Acionar novos fluxos de trabalho usando um token de acesso pessoal {% 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)". diff --git a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md index a919016587..84ee8a1a71 100644 --- a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md @@ -31,7 +31,7 @@ Você pode especificar o tipo de executor para cada trabalho em um fluxo de trab O {% data variables.product.prodname_dotcom %} hospeda executores do Linux e Windows no Standard_DS2_v2 máquinas virtuais no Microsoft Azure com o aplicativo do executor {% data variables.product.prodname_actions %} instalado. A o aplicativo do executor hospedado no {% data variables.product.prodname_dotcom %} é uma bifurcação do agente do Azure Pipelines. Os pacotes ICMP de entrada estão bloqueados para todas as máquinas virtuais do Azure. Portanto, é possível que os comandos ping ou traceroute não funcionem. Para obter mais informações sobre os recursos da máquina Standard_DS2_v2, consulte "[Dv2 e DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" na documentação do Microsoft Azure. -O {% data variables.product.prodname_dotcom %} usa [MacStadium](https://www.macstadium.com/) para hospedar os executores do macOS. +{% data variables.product.prodname_dotcom %} hospedas executores do macOS na nuvem do macOS do próprio {% data variables.product.prodname_dotcom %}. #### Privilégios administrativos os executores hospedados no {% data variables.product.prodname_dotcom %} diff --git a/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md index 3a754d50e9..a12f044a09 100644 --- a/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md @@ -79,6 +79,7 @@ Para obter mais informações, consulte: - "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Aplicar as políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" para {% data variables.product.prodname_ghe_cloud %}{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Desabilitar e habilitar fluxos de trabalho Você pode habilitar e desabilitar os fluxos de trabalho individuais no seu repositório em {% data variables.product.prodname_dotcom %}. @@ -86,3 +87,4 @@ Você pode habilitar e desabilitar os fluxos de trabalho individuais no seu repo {% data reusables.actions.scheduled-workflows-disabled %} Para obter mais informações, consulte "[Desabilitar e habilitar um fluxo de trabalho](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)". +{% endif %} diff --git a/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md index 70980a1067..056b5a3f1a 100644 --- a/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md @@ -164,14 +164,14 @@ Cria uma mensagem de erro e a imprime no log. Cria uma mensagem de erro e a impr echo "::error file=app.js,line=10,col=15::Something went wrong" ``` -### Grouping log lines +### Agrupar linhas dos registros ``` ::group::{title} ::endgroup:: ``` -Creates an expandable group in the log. To create a group, use the `group` command and specify a `title`. Anything you print to the log between the `group` and `endgroup` commands is nested inside an expandable entry in the log. +Cria um grupo expansível no registro. Para criar um grupo, use o comando `grupo` e especifique um `título`. Qualquer coisa que você imprimir no registro entre os comandos `grupo` e `endgroup` estará aninhada dentro de uma entrada expansível no registro. #### Exemplo @@ -181,7 +181,7 @@ echo "Inside group" echo "::endgroup::" ``` -![Foldable group in workflow run log](/assets/images/actions-log-group.png) +![Grupo dobrável no registro da execução do fluxo de trabalho](/assets/images/actions-log-group.png) ### Mascarar um valor no registro @@ -278,7 +278,7 @@ echo "action_state=yellow" >> $GITHUB_ENV Executar `$action_state` em uma etapa futura agora retornará `amarelo` -#### Multiline strings +#### Strings de linha múltipla Para strings linha múltipla, você pode usar um delimitador com a seguinte sintaxe. diff --git a/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md index 2d4d9a44df..b5bf5e3677 100644 --- a/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md @@ -1,7 +1,7 @@ --- -title: Workflow syntax for GitHub Actions -shortTitle: Workflow syntax -intro: A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your workflow configuration. +title: Sintaxe de fluxo de trabalho para o GitHub Actions +shortTitle: Sintaxe de fluxo de trabalho +intro: Um fluxo de trabalho é um processo automatizado configurável constituído de um ou mais trabalhos. Você deve criar um arquivo YAML para definir a configuração do seu fluxo de trabalho. product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/workflow-syntax-for-github-actions @@ -15,45 +15,45 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### About YAML syntax for workflows +### Sobre sintaxe YAML para fluxos de trabalho -Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." +Arquivos de fluxo de trabalho usam sintaxe YAML e devem ter uma extensão de arquivo `.yml` ou `.yaml`. Se você não souber o que é YAMLe quiser saber mais, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". -You must store workflow files in the `.github/workflows` directory of your repository. +Você deve armazenar os arquivos de fluxo de trabalho no diretório `.github/workflows` do seu repositório. ### **`name`** -The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository. +Nome do fluxo de trabalho. O {% data variables.product.prodname_dotcom %} exibe os nomes dos fluxos de trabalho na página de ações do repositório. Se você omitir o `nome`, o {% data variables.product.prodname_dotcom %} irá defini-lo como o caminho do arquivo do fluxo de trabalho relativo à raiz do repositório. ### **`on`** -**Required** The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. You can provide a single event `string`, `array` of events, `array` of event `types`, or an event configuration `map` that schedules a workflow or restricts the execution of a workflow to specific files, tags, or branch changes. For a list of available events, see "[Events that trigger workflows](/articles/events-that-trigger-workflows)." +**Obrigatório** Nome do evento do {% data variables.product.prodname_dotcom %} que aciona o fluxo de trabalho. Você pode fornecer uma única `string` de evento, um `array` de eventos, um `array` de `types` (tipos) de eventos ou um `map` (mapa) de configuração de eventos que programe um fluxo de trabalho ou restrinja a execução do fluxo de trabalho a alterações em determinados arquivos, tags ou branches. Para obter uma lista de eventos disponíveis, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows)". {% data reusables.github-actions.actions-on-examples %} ### **`on..types`** -Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is `published`, `unpublished`, `created`, `edited`, `deleted`, or `prereleased`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary. +Seleciona os tipos de atividades que acionarão a execução de um fluxo de trabalho. A maioria dos eventos GitHub são acionados por mais de um tipo de atividade. Por exemplo, o evento para o recurso release (versão) é acionado quando uma versão é `published` (publicada), `unpublished` (a publicação é cancelada), `created` (criada), `edited` (editada), `deleted` (excluída) ou `prereleased` (versão prévia). A palavra-chave `types` (tipos) permite que você limite a atividade que faz com que o fluxo de trabalho seja executado. Quando somente um tipo de atividade aciona um evento de webhook, a palavra-chave `types` (tipos) é desnecessária. -You can use an array of event `types`. For more information about each event and their activity types, see "[Events that trigger workflows](/articles/events-that-trigger-workflows#webhook-events)." +É possível usar um array de `types` (tipos) de evento. Para obter mais informações sobre cada evento e seus tipos de atividades, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows#webhook-events)". ```yaml -# Trigger the workflow on pull request activity +# Aciona o fluxo de trabalho na atividade de pull request on: release: - # Only use the types keyword to narrow down the activity types that will trigger your workflow. + # Usa apenas a palavra-chave types (tipos) para limitar os tipos de atividades que acionam o fluxo de trabalho. types: [published, created, edited] ``` ### **`on..`** -When using the `push` and `pull_request` events, you can configure a workflow to run on specific branches or tags. For a `pull_request` event, only branches and tags on the base are evaluated. If you define only `tags` or only `branches`, the workflow won't run for events affecting the undefined Git ref. +Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado em branches ou tags específicos. Para um evento de `pull_request`, são avaliados apenas os branches e tags na base. Se você definir apenas `tags` ou `branches`, o fluxo de trabalho não será executado para eventos que afetam o Git ref indefinido. -The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one branch or tag name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." +As palavras-chave `branches`, `branches-ignore`, `tags` e `tags-ignore` aceitam padrões glob que usam os caracteres curinga `*` e `**` para coincidir com mais de um nome de branch ou tag. Para obter mais informações, consulte a "[Folha de consulta de filtro padrão](#filter-pattern-cheat-sheet)". -#### Example including branches and tags +#### Exemplo com branches e tags -The patterns defined in `branches` and `tags` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**` will match the `refs/heads/releases/10` Git ref. +Os padrões definidos nos `branches` e `tags` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**` corresponderá ao Git ref `refs/heads/releases/10`. ```yaml on: @@ -72,37 +72,37 @@ on: - v1.* # Push events to v1.0, v1.1, and v1.9 tags ``` -#### Example ignoring branches and tags +#### Exemplo desconsiderando branches e tags -Anytime a pattern matches the `branches-ignore` or `tags-ignore` pattern, the workflow will not run. The patterns defined in `branches-ignore` and `tags-ignore` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**-alpha` in `branches` will match the `refs/releases/beta/3-alpha` Git ref. +Sempre que um padrão corresponde ao padrão `branches-ignore` ou `tags-ignore`, o fluxo de trabalho não será executado. Os padrões definidos em `branches-ignore` e `tags-ignore` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**-alpha` em `branches` corresponderá ao Git ref `refs/releases/beta/3-alpha`. ```yaml -on: +em: push: - # Sequence of patterns matched against refs/heads + # Sequência de padrões que correspondem a refs/heads branches-ignore: - # Push events to branches matching refs/heads/mona/octocat + # Push de eventos para branches que correspondem a refs/heads/mona/octocat - 'mona/octocat' - # Push events to branches matching refs/heads/releases/beta/3-alpha + # Push de eventos para branches que correspondem a refs/heads/releases/beta/3-alpha - 'releases/**-alpha' - # Sequence of patterns matched against refs/tags + # Sequência de padrões que correspondem a refs/tags tags-ignore: - v1.* # Push events to tags v1.0, v1.1, and v1.9 ``` -#### Excluding branches and tags +#### Excluir branches e tags -You can use two types of filters to prevent a workflow from running on pushes and pull requests to tags and branches. -- `branches` or `branches-ignore` - You cannot use both the `branches` and `branches-ignore` filters for the same event in a workflow. Use the `branches` filter when you need to filter branches for positive matches and exclude branches. Use the `branches-ignore` filter when you only need to exclude branch names. -- `tags` or `tags-ignore` - You cannot use both the `tags` and `tags-ignore` filters for the same event in a workflow. Use the `tags` filter when you need to filter tags for positive matches and exclude tags. Use the `tags-ignore` filter when you only need to exclude tag names. +Você pode usar dois tipos de filtros para impedir a execução de um fluxo de trabalho em pushes e pull requests para tags e branches. +- `branches` ou `branches-ignore` - não é possível usar os dois filtros `branches` e `branches-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `branches` quando você precisa filtrar branches para correspondências positivas e excluir branches. Use o filtro `branches-ignore` quando você só precisa excluir nomes de branches. +- `tags` ou `tags-ignore` - não é possível usar os dois filtros `tags` e `tags-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `tags` quando você precisa filtrar tags para correspondências positivas e excluir tags. Use o filtro `tags-ignore` quando você só precisa excluir nomes de tags. -#### Example using positive and negative patterns +#### Exemplo com padrões positivos e negativos -You can exclude `tags` and `branches` using the `!` character. The order that you define patterns matters. - - A matching negative pattern (prefixed with `!`) after a positive match will exclude the Git ref. - - A matching positive pattern after a negative match will include the Git ref again. +Você pode excluir `tags` e `branches` usando o caractere `!`. A ordem de definição dos padrões é importante. + - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o Git ref. + - Um padrão positivo correspondente após uma correspondência negativa incluirá a Git ref novamente. -The following workflow will run on pushes to `releases/10` or `releases/beta/mona`, but not on `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern. +O fluxo de trabalho a seguir será executado em pushes para `releases/10` ou `releases/beta/mona`, mas não em `releases/10-alpha` ou `releases/beta/3-alpha`, pois o padrão negativo `!releases/**-alpha` está na sequência do padrão positivo. ```yaml on: @@ -114,13 +114,13 @@ on: ### **`on..paths`** -When using the `push` and `pull_request` events, you can configure a workflow to run when at least one file does not match `paths-ignore` or at least one modified file matches the configured `paths`. Path filters are not evaluated for pushes to tags. +Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado quando pelo menos um arquivo não corresponde a `paths-ignore` ou pelo menos um arquivo modificado corresponde ao `paths` configurado. Flitros de caminho não são avaliados em pushes para tags. -The `paths-ignore` and `paths` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." +As palavras-chave `paths-ignore` e `paths` aceitam padrões glob que usam os caracteres curinga `*` e `**` para coincidir com mais de um nome de caminho. Para obter mais informações, consulte a "[Folha de consulta de filtro padrão](#filter-pattern-cheat-sheet)". -#### Example ignoring paths +#### Exemplo desconsiderando caminhos -Anytime a path name matches a pattern in `paths-ignore`, the workflow will not run. {% data variables.product.prodname_dotcom %} evaluates patterns defined in `paths-ignore` against the path name. A workflow with the following path filter will only run on `push` events that include at least one file outside the `docs` directory at the root of the repository. +Sempre que um nome de caminho corresponder a um padrão em `paths-ignore`, o fluxo de trabalho não será executado. O {% data variables.product.prodname_dotcom %} avalia os padrões definidos em `paths-ignore` com relação ao nome do caminho. Um fluxo de trabalho com o seguinte filtro de caminho só será executado em eventos `push` que tiverem pelo menos um arquivo fora do diretório `docs` na raiz do repositório. ```yaml on: @@ -129,9 +129,9 @@ on: - 'docs/**' ``` -#### Example including paths +#### Exemplo incluindo caminhos -If at least one path matches a pattern in the `paths` filter, the workflow runs. To trigger a build anytime you push a JavaScript file, you can use a wildcard pattern. +Se pelo menos um caminho corresponder a um padrão no filtro `paths`, o fluxo de trabalho será executado. Para acionar uma compilação sempre que você fizer push de um arquivo JavaScript, você pode usar um padrão curinga. ```yaml on: @@ -140,19 +140,19 @@ on: - '**.js' ``` -#### Excluding paths +#### Excluir caminhos -You can exclude paths using two types of filters. You cannot use both of these filters for the same event in a workflow. -- `paths-ignore` - Use the `paths-ignore` filter when you only need to exclude path names. -- `paths` - Use the `paths` filter when you need to filter paths for positive matches and exclude paths. +Você pode excluir caminhos com dois tipos de filtros. Não é possível usar ambos os filtros para o mesmo evento em um fluxo de trabalho. +- `paths-ignore` - use o filtro `paths-ignore` quando você precisa somente excluir nomes de caminhos. +- `paths` - use o filtro `paths` quando você precisa filtrar caminhos para correspondências positivas e excluir caminhos. -#### Example using positive and negative patterns +#### Exemplo com padrões positivos e negativos -You can exclude `paths` using the `!` character. The order that you define patterns matters: - - A matching negative pattern (prefixed with `!`) after a positive match will exclude the path. - - A matching positive pattern after a negative match will include the path again. +Você pode excluir `paths` usando o caractere `!`. A ordem de definição dos padrões é importante: + - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o caminho. + - Um padrão positivo correspondente após uma correspondência negativa incluirá o caminho novamente. -This example runs anytime the `push` event includes a file in the `sub-project` directory or its subdirectories, unless the file is in the `sub-project/docs` directory. For example, a push that changed `sub-project/index.js` or `sub-project/src/index.js` will trigger a workflow run, but a push changing only `sub-project/docs/readme.md` will not. +Este exemplo é executado sempre que o evento `push` inclui um arquivo no diretório `sub-project` ou seus subdiretórios, a menos que o arquivo esteja no diretório `sub-project/docs`. Por exemplo, um push que alterou `sub-project/index.js` ou `sub-project/src/index.js` acionará uma execução de fluxo de trabalho, mas um push que altere somente`sub-project/docs/readme.md` não acionará. ```yaml on: @@ -162,55 +162,55 @@ on: - '!sub-project/docs/**' ``` -#### Git diff comparisons +#### Comparações Git diff {% note %} -**Note:** If you push more than 1,000 commits, or if {% data variables.product.prodname_dotcom %} does not generate the diff due to a timeout (diffs that are too large diffs), the workflow will always run. +**Observação:** se você fizer push de mais de 1.000 commits ou se o {% data variables.product.prodname_dotcom %} não gera o diff devido a um tempo limite esgotado (diffs muito grandes), o fluxo de trabalho sempre será executado. {% endnote %} -The filter determines if a workflow should run by evaluating the changed files and running them against the `paths-ignore` or `paths` list. If there are no files changed, the workflow will not run. +O filtro determina se um fluxo de trabalho deve ser executado avaliando os arquivos alterados e comparando-os à lista de `paths-ignore` ou `paths`. Se não houver arquivos alterados, o fluxo de trabalho não será executado. -{% data variables.product.prodname_dotcom %} generates the list of changed files using two-dot diffs for pushes and three-dot diffs for pull requests: -- **Pull requests:** Three-dot diffs are a comparison between the most recent version of the topic branch and the commit where the topic branch was last synced with the base branch. -- **Pushes to existing branches:** A two-dot diff compares the head and base SHAs directly with each other. -- **Pushes to new branches:** A two-dot diff against the parent of the ancestor of the deepest commit pushed. +O {% data variables.product.prodname_dotcom %} gera a lista de arquivos alterados usando diffs de dois pontos para pushes e diffs de três pontos para pull requests: +- **Pull requests:** diffs de três pontos são uma comparação entre a versão mais recente do branch de tópico e o commit onde o branch de tópico foi sincronizado pela última vez com o branch de base. +- **Pushes para branches existentes:** um diff de dois pontos compara os SHAs head e base, um com o outro. +- **Pushes para novos branches:** um diff de dois pontos compara o principal do ancestral do commit mais extenso que foi feito push. -For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)." +Para obter mais informações, consulte "[Sobre comparação de branches em pull requests](/articles/about-comparing-branches-in-pull-requests)". ### **`on.schedule`** {% data reusables.repositories.actions-scheduled-workflow-example %} -For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)." +Para obter mais informações sobre a sintaxe cron, consulte "[Eventos que acionam fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)". ### **`env`** -A `map` of environment variables that are available to all jobs and steps in the workflow. You can also set environment variables that are only available to a job or step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps.env`](#jobsjob_idstepsenv). +Um `map` (mapa) das variáveis de ambiente que estão disponíveis para todos os trabalhos e etapas do fluxo de trabalho. Também é possível configurar variáveis de ambiente que estão disponíveis apenas para um trabalho ou etapa. Para obter mais informações, consulte [`jobs..env`](#jobsjob_idenv) e [`jobs..steps.env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### Example +#### Exemplo ```yaml env: SERVER: production ``` -### **`defaults`** +### **`padrões`** -A `map` of default settings that will apply to all jobs in the workflow. You can also set default settings that are only available to a job. For more information, see [`jobs..defaults`](#jobsjob_iddefaults). +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`](#jobsjob_iddefaults). {% data reusables.github-actions.defaults-override %} ### **`defaults.run`** -You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a workflow. You can also set default settings for `run` that are only available to a job. For more information, see [`jobs..defaults.run`](#jobsjob_iddefaultsrun). You cannot use contexts or expressions in this keyword. +Você pode fornecer opções-padrão de `shell` e `working-directory` para todas as etapas de [`executar`](#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`](#jobsjob_iddefaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave. {% data reusables.github-actions.defaults-override %} -#### Example +#### Exemplo ```yaml defaults: @@ -221,19 +221,19 @@ defaults: ### **`jobs`** -A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs..needs` keyword. +A execução de um fluxo de trabalho consiste em um ou mais trabalhos. Por padrão, os trabalhos são executados paralelamente. Para executar trabalhos sequencialmente, você pode definir dependências em outros trabalhos usando a palavra-chave `jobs..needs`. -Each job runs in an environment specified by `runs-on`. +Cada trabalho é executado em um ambiente especificado por `runs-on`. -You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. +Você pode executar quantos trabalhos desejar, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados. -If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/v3/actions/workflow-jobs)." +Se você precisar encontrar o identificador exclusivo de um trabalho e execução em um fluxo de trabalho, você poderá usar a API {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Trabalhos do fluxo de trabalho](/rest/reference/actions#workflow-jobs)". ### **`jobs.`** -Each job must have an id to associate with the job. The key `job_id` is a string and its value is a map of the job's configuration data. You must replace `` with a string that is unique to the `jobs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. +Cada trabalho deve ter um id associado. A chave `job_id` é uma string, e seu valor é um mapa dos dados de configuração do trabalho. Você deve substituir `` por uma string exclusiva para o objeto `jobs`. `` deve começar por uma letra ou `_`, além de conter somente caracteres alfanuméricos, `-` ou `_`. -#### Example +#### Exemplo ```yaml jobs: @@ -245,13 +245,13 @@ jobs: ### **`jobs..name`** -The name of the job displayed on {% data variables.product.prodname_dotcom %}. +Nome do trabalho no {% data variables.product.prodname_dotcom %}. ### **`jobs..needs`** -Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional statement that causes the job to continue. +Identifica todos os trabalhos a serem concluídos com êxito antes da execução deste trabalho. Esse código pode ser uma string ou array de strings. Se houver falha em um trabalho, todos os trabalhos que dependem dele serão ignorados, a menos que os trabalhos usem uma instrução condicional que faça o trabalho continuar. -#### Example +#### Exemplo ```yaml jobs: @@ -262,9 +262,9 @@ jobs: needs: [job1, job2] ``` -In this example, `job1` must complete successfully before `job2` begins, and `job3` waits for both `job1` and `job2` to complete. +Neste exemplo, `job1` deve ser concluído com êxito antes do início de `job2`, e `job3` aguarda a conclusão de `job1` e `job2`. -The jobs in this example run sequentially: +Os trabalhos neste exemplo são executados sequencialmente: 1. `job1` 2. `job2` @@ -272,49 +272,49 @@ The jobs in this example run sequentially: ### **`jobs..runs-on`** -**Required** The type of machine to run the job on. The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner. +**Obrigatório** O tipo de máquina para executar o trabalho. A máquina pode ser ou um executor hospedado em {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado. {% data reusables.actions.enterprise-github-hosted-runners %} -#### {% data variables.product.prodname_dotcom %}-hosted runners +#### Runners hospedados no {% data variables.product.prodname_dotcom %} -If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a virtual environment specified by `runs-on`. +Se você usar um executor hospedado no {% data variables.product.prodname_dotcom %}, cada trabalho será executado em uma nova instância de um ambiente virtual especificado por `runs-on`. -Available {% data variables.product.prodname_dotcom %}-hosted runner types are: +Os tipos de executor disponíveis para {% data variables.product.prodname_dotcom %} são: {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} -##### **Example** +##### **Exemplo** ```yaml runs-on: ubuntu-latest ``` -For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." +Para obter mais informações, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". -#### Self-hosted runners +#### Executores auto-hospedados {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### **Example** +##### **Exemplo** ```yaml runs-on: [self-hosted, linux] ``` -For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-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)." +Para obter mais informações, consulte "[Sobre executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" e "[Usar executores auto-hospedados em um fluxo de trabalho](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." ### **`jobs..outputs`** -A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs..needs`](#jobsjob_idneeds). +Um `mapa` de saídas para um trabalho. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre a definição de dependências de trabalhos, consulte [`jobs..needs`](#jobsjob_idneeds). -Job outputs are strings, and job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}. +As saídas de trabalho são strings e saídas de trabalho que contêm expressões são avaliadas no executor ao final de cada trabalho. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}. -To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)." +Para usar as saídas de trabalho em um trabalho dependente, você poderá usar o contexto `needs`. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)". -#### **Example** +#### **Exemplo** {% raw %} ```yaml @@ -340,11 +340,11 @@ jobs: ### **`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). +Um `map` (mapa) das variáveis de ambiente que estão disponíveis para todos as etapas do trabalho. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou uma etapa individual. Para obter mais informações, consulte [`env`](#env) e [`jobs..steps.env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### **Example** +#### **Exemplo** ```yaml jobs: @@ -355,19 +355,19 @@ jobs: ### **`jobs..defaults`** -A `map` of default settings that will apply to all steps in the job. You can also set default settings for the entire workflow. For more information, see [`defaults`](#defaults). +Um `mapa` com as configurações- padrão que serão aplicadas 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`](#defaults). {% data reusables.github-actions.defaults-override %} ### **`jobs..defaults.run`** -Provide default `shell` and `working-directory` to all `run` steps in the job. Context and expression are not allowed in this section. +Forneça o `shell` e `working-directory` para todas as etapas do trabalho `executar`. Não são permitidos contexto e expressão nesta seção. -You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a job. You can also set default settings for `run` for the entire workflow. For more information, see [`jobs.defaults.run`](#defaultsrun). You cannot use contexts or expressions in this keyword. +Você pode fornecer as opções-padrão de `shell` e `working-directory` para todas as etapas de [`execução`](#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`](#defaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave. {% data reusables.github-actions.defaults-override %} -#### Example +#### Exemplo ```yaml jobs: @@ -381,17 +381,17 @@ jobs: ### **`jobs..if`** -You can use the `if` conditional to prevent a job from running unless a condition is met. You can use any supported context and expression to create a conditional. +Você pode usar a condicional `if` (se) 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 %} For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". ### **`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. +Trabalhos contêm sequências de tarefas chamadas `steps`. As etapas podem executar comandos, executar trabalhos de configuração ou executar ações no seu repositório, em repositórios públicos, ou ações publicadas em registros do Docker. Nem todas as etapas executam ações, mas todas as ações são executadas como etapas. Cada etapa é executada em seu próprio processo no ambiente do executor, tendo acesso ao espaço de trabalho e ao sistema de arquivos. Como as etapas são executadas em seus próprios processos, as alterações nas variáveis de ambiente não são preservadas entre as etapas. O {% data variables.product.prodname_dotcom %} fornece etapas integradas para configurar e concluir trabalhos. -You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. +Você pode executar quantas etapas quiser, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados. -#### Example +#### Exemplo {% raw %} ```yaml @@ -417,17 +417,17 @@ jobs: #### **`jobs..steps.id`** -A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +Identificador exclusivo da etapa. Você pode usar `id` para fazer referência à etapa em contextos. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". #### **`jobs..steps.if`** -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. +Você pode usar a condicional `if` (se) 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 %} For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -##### Example using contexts +##### Exemplo usando contextos - This step only runs when the event type is a `pull_request` and the event action is `unassigned`. + Essa etapa somente é executada quando o tipo de evento é uma `pull_request` e a ação do evento é `unassigned` (não atribuída). ```yaml steps: @@ -436,9 +436,9 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -##### Example using status check functions +##### Exemplo usando funções de verificação de status -The `my backup step` only runs when the previous step of a job fails. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)." +A função `my backup step` (minha etapa de backup) somente é executada quando houver falha em uma etapa anterior do trabalho. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)". ```yaml steps: @@ -446,27 +446,27 @@ steps: uses: monacorp/action-name@main - name: My backup step if: {% raw %}${{ failure() }}{% endraw %} - uses: actions/heroku@master + uses: actions/heroku@1.0.0 ``` #### **`jobs..steps.name`** -A name for your step to display on {% data variables.product.prodname_dotcom %}. +Nome da etapa no {% data variables.product.prodname_dotcom %}. #### **`jobs..steps.uses`** -Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/). +Seleciona uma ação para executar como parte de uma etapa no trabalho. A ação é uma unidade reutilizável de código. Você pode usar uma ação definida no mesmo repositório que o fluxo de trabalho, um repositório público ou em uma [imagem publicada de contêiner Docker](https://hub.docker.com/). -We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update. -- Using the commit SHA of a released action version is the safest for stability and security. -- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work. -- Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break. +É altamente recomendável incluir a versão da ação que você está usando ao especificar um número de tag Docker, SHA ou ref do Git. Se você não especificar uma versão, ela poderá interromper seus fluxos de trabalho ou causar um comportamento inesperado quando o proprietário da ação publicar uma atualização. +- Usar o commit SHA de uma versão de ação lançada é a maneira mais garantida de obter estabilidade e segurança. +- Usar a versão principal da ação permite receber correções importantes e patches de segurança sem perder a compatibilidade. Fazer isso também garante o funcionamento contínuo do fluxo de trabalho. +- Usar o branch-padrão de uma ação pode ser conveniente, mas se alguém lançar uma nova versão principal com uma mudança significativa, seu fluxo de trabalho poderá ter problemas. -Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required. +Algumas ações requerem entradas que devem ser definidas com a palavra-chave [`with`](#jobsjob_idstepswith) (com). Revise o arquivo README da ação para determinar as entradas obrigatórias. -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). +Ações são arquivos JavaScript ou contêineres Docker. Se a ação em uso for um contêiner do Docker, você deverá executar o trabalho em um ambiente do Linux. Para obter mais detalhes, consulte [`runs-on`](#jobsjob_idruns-on). -##### Example using versioned actions +##### Exemplo usando ações com versão ```yaml steps: @@ -480,11 +480,11 @@ steps: - uses: actions/setup-node@main ``` -##### Example using a public action +##### Exemplo usando uma ação pública `{owner}/{repo}@{ref}` -You can specific branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository. +Você pode especificar um branch, ref ou SHA em um repositório público {% data variables.product.prodname_dotcom %}. ```yaml jobs: @@ -492,17 +492,17 @@ jobs: steps: - name: My first step # Uses the default branch of a public repository - uses: actions/heroku@master + uses: actions/heroku@1.0.0 - name: My second step # Uses a specific version tag of a public repository uses: actions/aws@v2.0.1 ``` -##### Example using a public action in a subdirectory +##### Exemplo usando uma ação pública em um subdiretório `{owner}/{repo}/{path}@{ref}` -A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA. +Subdiretório em um repositório público do {% data variables.product.prodname_dotcom %} em um branch, ref ou SHA específico. ```yaml jobs: @@ -512,11 +512,11 @@ jobs: uses: actions/aws/ec2@main ``` -##### Example using action in the same repository as the workflow +##### Exemplo usando a ação no mesmo repositório que o fluxo de trabalho `./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. +Caminho para o diretório que contém a ação no repositório do seu fluxo de trabalho. Você deve reservar seu repositório antes de usar a ação. ```yaml jobs: @@ -528,11 +528,11 @@ jobs: uses: ./.github/actions/my-action ``` -##### Example using a Docker Hub action +##### Exemplo usando uma ação do Docker Hub `docker://{image}:{tag}` -A Docker image published on [Docker Hub](https://hub.docker.com/). +Imagem Docker publicada no [Docker Hub](https://hub.docker.com/). ```yaml jobs: @@ -542,11 +542,11 @@ jobs: uses: docker://alpine:3.8 ``` -##### Example using a Docker public registry action +##### Exemplo usando uma ação do registro público do Docker Hub `docker://{host}/{image}:{tag}` -A Docker image in a public registry. +Imagem Docker em um registro público. ```yaml jobs: @@ -558,20 +558,20 @@ 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. +Executa programas de linha de comando usando o shell do sistema operacional. Se você não informar um `name`, o nome da etapa será configurado por padrão como o texto indicado no comando `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 "[Using a specific shell](#using-a-specific-shell)." +Por padrão, os comandos run usam shells de não login. Você pode escolher um shell diferente e personalizar o shell usado para executar comandos. Para obter mais informações, consulte "[Usar um shell específico](#using-a-specific-shell)". -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. For example: +Cada palavra-chave `run` representa um novo processo e shell no ambiente do executor. Quando você fornece comandos de várias linhas, cada linha será executada no mesmo shell. Por exemplo: -* A single-line command: +* Um comando de linha única: ```yaml - name: Install Dependencies run: npm install ``` -* A multi-line command: +* Um comando de várias linhas: ```yaml - name: Clean install dependencies and build @@ -580,7 +580,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. +Com a palavra-chave `working-directory` (diretório de trabalho), é possível especificar o diretório de trabalho de onde o comando será executado. ```yaml - name: Clean temp directory @@ -588,20 +588,20 @@ Using the `working-directory` keyword, you can specify the working directory of working-directory: ./temp ``` -##### Using a specific shell +##### Usar um shell específico -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. +Você pode anular as configurações padrão de shell no sistema operacional do executor usando a palavra-chave `shell`. É possível usar palavras-chave integradas a `shell` ou definir um conjunto personalizado de opções de shell. -| Supported platform | `shell` parameter | Description | Command run internally | -|--------------------|-------------------|-------------|------------------------| -| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | -| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | -| All | `python` | Executes the python command. | `python {0}` | -| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | This is the default shell used on Windows. The Desktop PowerShell. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | +| Plataforma compatível | Parâmetro `shell` | Descrição | Comando executado internamente | +| --------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| Todas | `bash` | O shell padrão em plataformas que não sejam Windows como uma alternativa para `sh`. Ao especificar um shell bash no Windows, é utilizado o shell bash incluído no Git para Windows. | `bash --noprofile --norc -eo pipefail {0}` | +| Todas | `pwsh` | Powershell Core. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. | `pwsh -command ". '{0}'"` | +| Todas | `python` | Executa o comando python. | `python {0}` | +| Linux / macOS | `sh` | Comportamento alternativo para plataformas que não sejam Windows se nenhum shell for fornecido e o `bash` não for encontrado no caminho. | `sh -e {0}` | +| Windows | `cmd` | O {% data variables.product.prodname_dotcom %} anexa a extensão `.cmd` ao nome do script e a substitui por `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `powershell` | Essa é a shell padrão usada no Windows. PowerShell Desktop. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. | `powershell -command ". '{0}'"`. | -##### Example running a script using bash +##### Exemplo de execução de um script usando bash: ```yaml steps: @@ -610,7 +610,7 @@ steps: shell: bash ``` -##### Example running a script using Windows `cmd` +##### Exemplo de execução de um script usando Windows `cmd` ```yaml steps: @@ -619,7 +619,7 @@ steps: shell: cmd ``` -##### Example running a script using PowerShell Core +##### Exemplo de execução de um script usando PowerShell Core ```yaml steps: @@ -628,7 +628,7 @@ steps: shell: pwsh ``` -##### Example running a python script +##### Exemplo de execução de um script python ```yaml steps: @@ -639,35 +639,35 @@ steps: shell: python ``` -##### Custom shell +##### Shell personalizado -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}`. +Você pode usar o valor `shell` em um string modelo usando `command […options] {0} [..more_options]`. O {% data variables.product.prodname_dotcom %} interpreta a primeira palavra da string delimitada por um espaço em branco como o comando e insere o nome do arquivo para o script temporário em `{0}`. -##### Exit codes and error action preference +##### Preferências de ação de erro e códigos de saída -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. +Para palavras-chave de shell integradas, fornecemos os seguintes padrões usados por executores hospedados no {% data variables.product.prodname_dotcom %}. Você deve seguir estas diretrizes quando executar scripts shell. - `bash`/`sh`: - - Fail-fast behavior using `set -e o pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms. - - You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`. - - sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code. + - Comportamento fail-fast usando `set -e o pipefail`: padrão para `bash` e `shell` integrado. Também é o padrão quando você não der opção em plataformas que não sejam Windows. + - Você pode cancelar o fail-fast e assumir o controle fornecendo uma string de modelo para as opções do shell. Por exemplo, `bash {0}`. + - Shells do tipo sh saem com o código de saída do último comando executado em um script, que também é o comportamento padrão das ações. O executor relatará o status da etapa como falha/êxito com base nesse código de saída. - `powershell`/`pwsh` - - Fail-fast behavior when possible. For `pwsh` and `powershell` built-in shell, we will prepend `$ErrorActionPreference = 'stop'` to script contents. - - We append `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` to powershell scripts so action statuses reflect the script's last exit code. - - Users can always opt out by not using the built-in shell, and providing a custom shell option like: `pwsh -File {0}`, or `powershell -Command "& '{0}'"`, depending on need. + - Comportamento fail-fast quando possível. Para shell integrado `pwsh` e `powershell`, precederemos `$ErrorActionPreference = 'stop'` para conteúdos de script. + - Vincularemos `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` a scripts powershell para que os status da ação reflitam o código de saída mais recente do script. + - Os usuários podem sempre optar por não usar o shell integrado e fornecer uma opção personalizada, como: `pwsh -File {0}` ou `powershell -Command "& '{0}'"`, dependendo da situação. - `cmd` - - There doesn't seem to be a way to fully opt into fail-fast behavior other than writing your script to check each error code and respond accordingly. Because we can't actually provide that behavior by default, you need to write this behavior into your script. - - `cmd.exe` will exit with the error level of the last program it executed, and it will and return the error code to the runner. This behavior is internally consistent with the previous `sh` and `pwsh` default behavior and is the `cmd.exe` default, so this behavior remains intact. + - Parece não haver uma forma de optar totalmente por um comportamento fail-fast que não seja gravar seu script para verificar cada código de erro e reagir de acordo. Como não podemos fornecer esse comportamento por padrão, você precisa gravá-lo em seu script. + - `cmd.exe` sairá com o nível de erro do último programa que executou e retornará o código de erro para o executor. Este comportamento é internamente consistente o padrão de comportamento anterior `sh` e `pwsh`, e é o padrão `cmd.exe`; portanto, ele fica intacto. #### **`jobs..steps.with`** -A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case. +Um `map` (mapa) dos parâmetros de entrada definidos pela ação. Cada parâmetro de entrada é um par chave/valor. Parâmetros de entrada são definidos como variáveis de ambiente. A variável é precedida por `INPUT_` e convertida em letras maiúsculas. -##### Example +##### Exemplo -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. +Define os três parâmetros de entrada (`first_name`, `middle_name` e `last_name`) definidos pela ação `hello_world`. Essas variáveis de entrada estarão acessíveis para a ação `hello-world` como variáveis de ambiente `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` e `INPUT_LAST_NAME`. ```yaml jobs: @@ -683,9 +683,9 @@ jobs: #### **`jobs..steps.with.args`** -A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. An `array of strings` is not supported by this parameter. +Uma `string` que define as entradas para um contêiner Docker. O {% data variables.product.prodname_dotcom %} entrega os `args` ao `ENTRYPOINT` do contêiner quando o contêiner inicia. Um `array de strings` não é compatível com esse parâmetro. -##### Example +##### Exemplo {% raw %} ```yaml @@ -698,17 +698,17 @@ steps: ``` {% endraw %} -The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference: +`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: -1. Document required arguments in the action's README and omit them from the `CMD` instruction. -1. Use defaults that allow using the action without specifying any `args`. -1. If the action exposes a `--help` flag, or something similar, use that as the default to make your action self-documenting. +1. Documente os argumentos necessários no LEIAME das ações e omita-os da instrução `CMD`. +1. Use padrões que permitam o uso da ação sem especificação de `args`. +1. Se a ação expõe um sinalizador `--help` ou similar, use isso como padrão para que a ação se documente automaticamente. #### **`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. +Anula o `ENTRYPOINT` Docker no `Dockerfile` ou define-o caso ainda não tenha sido especificado. Diferentemente da instrução Docker `ENTRYPOINT` que tem um formulário shell e exec, a palavra-chave `entrypoint` aceita apena uma única string que define o executável. -##### Example +##### Exemplo ```yaml steps: @@ -718,83 +718,83 @@ steps: entrypoint: /a/different/executable ``` -The `entrypoint` keyword is meant to use with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. +A palavra-chave `entrypoint` é para ser usada com ações de contêiner Docker, mas você também pode usá-la com ações JavaScript que não definem nenhuma entrada. #### **`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). +Define variáveis de ambiente para etapas a serem usadas no ambiente do executor. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou para um trabalho. Para obter mais informações, consulte [`env`](#env) e [`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 "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +Ações públicas podem especificar variáveis de ambiente esperadas no arquivo LEIAME. Se você está configurando um segredo em uma variável de ambiente, use o contexto `secrets`. Para obter mais informações, consulte "[Usar variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)e "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -##### Example +##### Exemplo {% raw %} ```yaml steps: - - name: My first action - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - FIRST_NAME: Mona - LAST_NAME: Octocat + - name: minha primeira ação + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + FIRST_NAME: Mona + LAST_NAME: Octocat ``` {% endraw %} #### **`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. +Impede a falha de um trabalho se uma etapa não funcionar. Defina `true` (verdadeiro) para permitir que um trabalho aconteça quando essa etapa falhar. #### **`jobs..steps.timeout-minutes`** -The maximum number of minutes to run the step before killing the process. +Número máximo de minutos para executar a etapa antes de interromper o processo. ### **`jobs..timeout-minutes`** -The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360 +Número máximo de minutos para permitir a execução de um trabalho o antes que o {% data variables.product.prodname_dotcom %} o cancele automaticamente. Padrão: 360 ### **`jobs..strategy`** -A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in. +Estratégias criam matrizes de compilação para os trabalhos. Você pode definir variações diferentes dos ambientes em que vai executar os trabalhos. #### **`jobs..strategy.matrix`** -You can define a matrix of different job configurations. A matrix allows you to create multiple jobs by performing variable substitution in a single job definition. For example, you can use a matrix to create jobs for more than one supported version of a programming language, operating system, or tool. A matrix reuses the job's configuration and creates a job for each matrix you configure. +Você pode definir uma matriz de diferentes configurações de trabalho. 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 %} -Each option you define in the `matrix` has a key and value. The keys you define become properties in the `matrix` context and you can reference the property in other areas of your workflow file. For example, if you define the key `os` that contains an array of operating systems, you can use the `matrix.os` property as the value of the `runs-on` keyword to create a job for each operating system. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +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 "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. +A ordem que você define uma `matriz` importa. A primeira opção que você definir será a primeira que será executada no seu fluxo de trabalho. -##### Example running with more than one version of Node.js +##### Exemplo de execução com mais de uma versão do Node.js -You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 6, 8, and 10, you could specify an array of those versions in the `matrix`. +Você pode especificar uma matriz ao fornecer um array para as opções de configuração. Por exemplo, se o executor for compatível com as versões 6, 8 e 10 do Node.js versões, você poderá especificar um array dessas versões na `matriz`. -This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version. +Este exemplo cria uma matriz de três trabalhos, definindo a chave `nó` para um array de três versões do Node.js. Para usar a matriz, o exemplo define a propriedade do contexto `matrix.node` como o valor do parâmetro `setup-node` de entrada da ação `node-version`. Como resultado, três trabalhos serão executados, cada uma usando uma versão diferente do Node.js. {% raw %} ```yaml -strategy: - matrix: - node: [6, 8, 10] -steps: - # Configures the node version used on GitHub-hosted runners - - uses: actions/setup-node@v1 - with: - # The Node.js version to configure +estratégia: + matriz: + nó: [6, 8, 10] +etapas: + # Configura a versão do nó usada nos executores hospedados no GitHub + - usa: actions/setup-node@v1 + com: + # A versão do Node.js a ser configurada node-version: ${{ matrix.node }} ``` {% endraw %} -The `setup-node` action is the recommended way to configure a Node.js version when using {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see the [`setup-node`](https://github.com/actions/setup-node) action. +A ação setup-node `` é a forma recomendada de configurar uma versão do Node.js ao usar executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a ação [`setup-node`](https://github.com/actions/setup-node). -##### Example running with more than one operating system +##### Exemplo de execução com mais de um sistema operacional -You can create a matrix to run workflows on more than one runner operating system. You can also specify more than one matrix configuration. This example creates a matrix of 6 jobs: +Você pode criar uma matriz para executar fluxos de trabalho em mais de um sistema operacional do executor. Você também pode especificar mais de uma configuração da matriz. Este exemplo cria uma matriz de 6 trabalhos: -- 2 operating systems specified in the `os` array -- 3 Node.js versions specified in the `node` array +- 2 sistemas operacionais especificados na array `os` +- 3 versões do Node.js especificadas na array do `nó` {% data reusables.repositories.actions-matrix-builds-os %} @@ -812,11 +812,11 @@ steps: ``` {% endraw %} -To find supported configuration options for {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." +Para encontrar opções de configuração compatíveis com os executores hospedados em {% data variables.product.prodname_dotcom %}, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." -##### Example including additional values into combinations +##### Exemplo de inclusão valores adicionais em combinações -You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 4 of `node` runs, you can use `include` to specify that additional option. +Você pode adicionar opções de configurações para um trabalho de matriz de compilação existente. Por exemplo, se você quer usar uma versão específica do `npm` quando o trabalho que usa o `windows-latest` e a versão 4 do `nó` é executado, você pode usar `incluir` para especificar a opção adicional. {% raw %} ```yaml @@ -834,9 +834,9 @@ strategy: ``` {% endraw %} -##### Example including new combinations +##### Exemplo de inclusão novas combinações -You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 12 to build on multiple operating systems, but wanted one extra experimental job using node version 13 on Ubuntu, you can use `include` to specify that additional job. +Você pode usar `incluir` para adicionar novos trabalhos a uma matriz de criação. Qualquer configuração sem correspondência de incluir será adicionadas à matriz. Por exemplo, se você quiser usar a versão 12 do `nó` para compilar em vários sistemas operacionais, mas quiser uma tarefa experimental extra usando o node 13 no Ubuntu, você poderá usar `incluir` para especificar essa tarefa adicional. {% raw %} ```yaml @@ -852,9 +852,9 @@ strategy: ``` {% endraw %} -##### Example excluding configurations from a matrix +##### Exemplo excluindo configurações de uma matriz -You can remove a specific configurations defined in the build matrix using the `exclude` option. Using `exclude` removes a job defined by the build matrix. The number of jobs is the cross product of the number of operating systems (`os`) included in the arrays you provide, minus any subtractions (`exclude`). +Você pode remover uma configuração específica definida na matriz de compilação usando a opção `exclude` (excluir). `exclude` remove um trabalho definido pela matriz de compilação. O número de trabalhos é o produto cruzado do número de sistemas operacionais (`os`) incluídos nos arrays fornecidos por você, menos quaisquer subtrações (`exclude`). {% raw %} ```yaml @@ -872,17 +872,23 @@ strategy: {% note %} -**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded. +**Observação:** Todas as combinações de `incluir` são processadas depois de `excluir`. Isso permite que você use `incluir` para voltar a adicionar combinações que foram excluídas anteriormente. {% endnote %} +##### Usando variáveis de ambiente em uma matriz + +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 %} + ### **`jobs..strategy.fail-fast`** -When set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs if any `matrix` job fails. Default: `true` +Quando definido como `true`, o {% data variables.product.prodname_dotcom %} cancela todos os trabalhos em andamento em caso de falha de algum trabalho de `matrix`. Padrão: `true` ### **`jobs..strategy.max-parallel`** -The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. By default, {% data variables.product.prodname_dotcom %} will maximize the number of jobs run in parallel depending on the available runners on {% data variables.product.prodname_dotcom %}-hosted virtual machines. +Número máximo de trabalhos que podem ser executados simultaneamente ao usar uma estratégia de trabalho de `matrix`. Por padrão, o {% data variables.product.prodname_dotcom %} maximizará o número de trabalhos executados em paralelo dependendo dos executores disponíveis nas máquinas virtuais hospedadas no {% data variables.product.prodname_dotcom %}. ```yaml strategy: @@ -891,11 +897,11 @@ strategy: ### **`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. +Impede que ocorra falha na execução de um fluxo de trabalho quando ocorrer uma falha em um trabalho. Defina como `verdadeiro` para permitir que uma execução de um fluxo de trabalho passe quando este trabalho falhar. -#### Example preventing a specific failing matrix job from failing a workflow run +#### Exemplo do impedimento de uma matriz falha específica de gerar uma falha na execução do fluxo de trabalho -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 `13` to fail without failing the workflow run. +Você pode permitir que as tarefas específicas em uma matriz de tarefas falhem sem que ocorra falha na execução do fluxo de trabalho. Por exemplo, se você deseja permitir apenas um trabalho experimental com o `nó` definido como `13` sem falhar a execução do fluxo de trabalho. {% raw %} ```yaml @@ -916,11 +922,11 @@ strategy: ### **`jobs..container`** -A container to run any steps in a job that don't already specify a container. If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts. +Contêiner para executar qualquer etapa em um trabalho que ainda não tenha especificado um contêiner. Se você tiver etapas que usam ações de script e de contêiner, as ações de contêiner serão executadas como contêineres irmãos na mesma rede e com as mesmas montagens de volume. -If you do not set a `container`, all steps will run directly on the host specified by `runs-on` unless a step refers to an action configured to run in a container. +Se você não definir um `container`, todas as etapas serão executadas diretamente no host especificado por `runs-on`, a menos que uma etapa se refira a uma ação configurada para execução em um contêiner. -#### Example +#### Exemplo ```yaml jobs: @@ -936,7 +942,7 @@ jobs: options: --cpus 1 ``` -When you only specify a container image, you can omit the `image` keyword. +Ao especificar somente uma imagem de contêiner, você pode omitir a palavra-chave `image`. ```yaml jobs: @@ -946,14 +952,14 @@ jobs: #### **`jobs..container.image`** -The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name. +Imagem Docker a ser usada como contêiner para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um {% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2.23" %}nome de registro{% endif %} público. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} #### **`jobs..container.credentials`** {% data reusables.actions.registry-credentials %} -##### Example +##### Exemplo {% raw %} ```yaml @@ -968,23 +974,23 @@ container: #### **`jobs..container.env`** -Sets a `map` of environment variables in the container. +Define um `mapa` das variáveis de ambiente no contêiner. #### **`jobs..container.ports`** -Sets an `array` of ports to expose on the container. +Define um `array` de portas para expor no contêiner. #### **`jobs..container.volumes`** -Sets an `array` of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. +Define um `array` de volumes para uso do contêiner. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host. -To specify a volume, you specify the source and destination path: +Para especificar um volume, especifique o caminho de origem e destino: `:`. -The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. +`` é um nome de volume ou caminho absoluto na máquina host, e `` é um caminho absoluto no contêiner. -##### Example +##### Exemplo ```yaml volumes: @@ -995,23 +1001,23 @@ volumes: #### **`jobs..container.options`** -Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." +Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". ### **`jobs..services`** {% data reusables.github-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. +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. -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. +Se você configurar seu trabalho para ser executado em um contêiner, ou a sua etapa usar ações ao contêiner, você não precisará mapear as portas para acessar o serviço ou a ação. O Docker expõe automaticamente todas as portas entre os contêineres da mesma rede de ponte definida pelo usuário. Você pode fazer referência ao contêiner de serviço diretamente pelo seu nome de host. O nome do host é mapeado automaticamente com o nome da etiqueta que você configurar para o serviço no fluxo de trabalho. -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. +Se você configurar a tarefa para executar diretamente na máquina do executor e sua etapa não usar uma ação de contêiner, você deverá mapear todas as portas de contêiner de serviço do Docker necessárias para o host do Docker (a máquina do executor). Você pode acessar o contêiner de serviço usando host local e a porta mapeada. -For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)." +Para obter mais informações sobre as diferenças entre os contêineres de serviço de rede, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers)". -#### Example using localhost +#### Exemplo de uso de host local -This example creates two services: nginx and redis. When you specify the Docker host port but not the container port, the container port is randomly assigned to a free port. {% 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. +Este exemplo cria dois serviços: nginx e redis. Ao especificar a porta do host do Docker mas não a porta do contêiner, a porta do contêiner será atribuída aleatoriamente a uma porta livre. O {% data variables.product.prodname_dotcom %} define a porta de contêiner atribuída no contexto {% raw %}`${{job.services..ports}}`{% endraw %}. Neste exemplo, você pode acessar as portas do contêiner de serviço usando os contextos {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} e {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %}. ```yaml services: @@ -1029,14 +1035,14 @@ 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 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name. +Imagem Docker a ser usada como contêiner de serviço para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um {% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2.23" %}nome de registro{% endif %} público. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} #### **`jobs..services..credentials`** {% data reusables.actions.registry-credentials %} -##### Example +##### Exemplo {% raw %} ```yaml @@ -1057,23 +1063,23 @@ services: #### **`jobs..services..env`** -Sets a `map` of environment variables in the service container. +Define um `maá` das variáveis de ambiente no contêiner do serviço. #### **`jobs..services..ports`** -Sets an `array` of ports to expose on the service container. +Define um `array` de portas para expor no contêiner de serviço. #### **`jobs..services..volumes`** -Sets an `array` of volumes for the service container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. +Define um `array` de volumes para uso do contêiner de serviço. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host. -To specify a volume, you specify the source and destination path: +Para especificar um volume, especifique o caminho de origem e destino: `:`. -The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. +`` é um nome de volume ou caminho absoluto na máquina host, e `` é um caminho absoluto no contêiner. -##### Example +##### Exemplo ```yaml volumes: @@ -1084,63 +1090,63 @@ volumes: #### **`jobs..services..options`** -Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." +Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". -### Filter pattern cheat sheet +### Folha de consulta de filtro padrão -You can use special characters in path, branch, and tag filters. +Você pode usar caracteres especiais nos filtros de caminhos, branches e tags. -- `*`: Matches zero or more characters, but does not match the `/` character. For example, `Octo*` matches `Octocat`. -- `**`: Matches zero or more of any character. -- `?`: Matches zero or one single character. For example, `Octoc?t` matches `Octocat`. -- `+`: Matches one or more of the preceding character. -- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-f]` matches any digits or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. -- `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character. +- `*`: Corresponde a zero ou mais caracteres, mas não Corresponde ao caractere `/`. Por exemplo, `Octo*` corresponde a `Octocat`. +- `**`: Corresponde a zero ou mais de qualquer caractere. +- `?`: Corresponde a zero ou a um único caractere. Por exemplo, `Octoc?t` corresponde a `Octocat`. +- `+`: Corresponde a um ou mais dos caracteres anteriores. +- `[]` Corresponde a um caractere listado entre colchetes ou incluído nos intervalos. Os intervalos só podem incluir valores de `a-z`, `A-Z`, e `0-9`. Por exemplo, o intervalo`[0-9a-f]` corresponde a qualquer letra maiúscula ou minúscula. Por exemplo, `[CB]at` corresponde a `Cat` ou `Bat` e `[1-2]00` corresponde a `100` e `200`. +- `!` No início de um padrão faz com que ele anule padrões positivos anteriores. Não tem nenhum significado especial caso não seja o primeiro caractere. -The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. +Os caracteres `*`, `[` e `!` são caracteres especiais em YAML. Se você iniciar um padrão com `*`, `[` ou `!`, você deverá colocá-lo entre aspas. ```yaml -# Valid +# Válido - '**/README.md' -# Invalid - creates a parse error that -# prevents your workflow from running. +# Inválido - Cria um erro de análise que +# impede que o seu fluxo de trabalho seja executado. - **/README.md ``` -For more information about branch, tag, and path filter syntax, see "[`on..`](#onpushpull_requestbranchestags)" and "[`on..paths`](#onpushpull_requestpaths)." +Para obter mais informações sobre a sintaxe de filtros de branches, tags e caminhos, consulte "[`on..`](#onpushpull_requestbranchestags)" e "[`on..paths`](#onpushpull_requestpaths)". -#### Patterns to match branches and tags +#### Padrões para corresponder branches e tags -| Pattern | Description | Example matches | -|---------|------------------------|---------| -| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). | -`feature/my-branch`
-`feature/your-branch` | -| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | -`feature/beta-a/my-branch`
-`feature/your-branch`
-`feature/mona/the/octocat` | -| -`main`
-`releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | -`main`
-`releases/mona-the-octocat` | -| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`main`
-`releases` | -| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | -`all/the/branches`
-`every/tag` | -| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`mona-feature`
-`feature`
-`ver-10-feature` | -| `v2*` | Matches branch and tag names that start with `v2`. | -`v2`
-`v2.0`
-`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | -`v1.10.1`
-`v2.0.0` | +| Padrão | Descrição | Exemplos de correspondências | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | +| `feature/*` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). | -`feature/my-branch`
-`feature/your-branch` | +| `feature/**` | `**` correspondem a qualquer caractere, incluindo a barra (`/`) em nomes de branches e tags. | -`feature/beta-a/my-branch`
-`feature/your-branch`
-`feature/mona/the/octocat` | +| -`main`
-`releases/mona-the-octcat` | Corresponde ao nome exato de um branch ou tag. | -`main`
-`releases/mona-the-octocat` | +| `'*'` | Corresponde a todos os nomes de branches e tags que não contêm uma barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | -`main`
-`releases` | +| `'**'` | Corresponde a todos os nomes de branches e tags. Esse é o comportamento padrão quando você não usa um filtro de `branches` ou `tags`. | -`all/the/branches`
-`every/tag` | +| `'*feature'` | O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | -`mona-feature`
-`feature`
-`ver-10-feature` | +| `v2*` | Corresponde aos nomes de branches e tags que iniciam com `v2`. | -`v2`
-`v2.0`
-`v2.9` | +| `v[12].[0-9]+.[0-9]+` | Corresponde a todas as tags de versão semântica com a versão principal 1 ou 2 | -`v1.10.1`
-`v2.0.0` | -#### Patterns to match file paths +#### Padrões para corresponder a caminhos de arquivos -Path patterns must match the whole path, and start from the repository's root. +Padrões de caminhos devem corresponder ao caminho completo e iniciar a partir da raiz do repositório. -| Pattern | Description of matches | Example matches | -|---------|------------------------|-----------------| -| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`README.md`
-`server.rb` | -| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | -`page.js`
-`page.jsx` | -| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | -`all/the/files.md` | -| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | -`app.js`
-`index.js` -| `'**.js'` | Matches all `.js` files in the repository. | -`index.js`
-`js/index.js`
-`src/js/app.js` | -| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | -`docs/README.md`
-`docs/file.txt` | -| `docs/**` | Any files in the `/docs` directory at the root of the repository. | -`docs/README.md`
-`docs/mona/octocat.txt` | -| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | -`docs/README.md`
-`docs/mona/hello-world.md`
-`docs/a/markdown/file.md` -| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | -`/docs/hello.md`
-`dir/docs/my-file.txt`
-`space/docs/plan/space.doc` -| `'**/README.md'` | A README.md file anywhere in the repository. | -`README.md`
-`js/README.md` -| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | -`a/src/app.js`
-`my-src/code/js/app.js` -| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | -`my-post.md`
-`path/their-post.md` | -| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | -`migrate-10909.sql`
-`db/migrate-v1.0.sql`
-`db/sept/migrate-v1.sql` | -| -`*.md`
-`!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | -`hello.md`
_Does not match_
-`README.md`
-`docs/hello.md` | -| -`*.md`
-`!README.md`
-`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | -`hello.md`
-`README.md`
-`README.doc`| +| Padrão | Descrição das correspondências | Exemplos de correspondências | +| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | +| `'*'` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | -`LEIAME.md`
-`server.rb` | +| `'*.jsx?'` | O caractere `?` corresponde a zero ou a um dos caracteres anteriores. | -`page.js`
-`page.jsx` | +| `'**'` | `**` corresponde a qualquer caractere incluindo a barra (`/`). Esse é o comportamento padrão quando você não usa um filtro de `path`. | -`all/the/files.md` | +| `'*.js'` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). Corresponde a todos os arquivos `.js` na raiz do repositório. | -`app.js`
-`index.js` | +| `'**.js'` | Corresponde a todos os arquivos `.js` no repositório. | -`index.js`
-`js/index.js`
-`src/js/app.js` | +| `docs/*` | Todos os arquivos dentro da raiz do diretório `docs`, na raiz do repositório. | -`docs/LEIAME.md`
-`docs/file.txt` | +| `docs/**` | Qualquer arquivo no diretório `docs`, na raiz do repositório. | -`docs/LEIAME.md`
-`docs/mona/octocat.txt` | +| `docs/**/*.md` | Um arquivo com um sufixo `.md` em qualquer local do diretório `docs`. | -`docs/LEIAME.md`
-`docs/mona/hello-world.md`
-`docs/a/markdown/file.md` | +| `'**/docs/**'` | Qualquer arquivo no diretório `docs`, em qualquer local do repositório. | -`/docs/hello.md`
-`dir/docs/my-file.txt`
-`space/docs/plan/space.doc` | +| `'**/README.md'` | Um arquivo LEIAME.md em qualquer local do repositório. | -`LEIAME.md`
-`js/LEIAME.md` | +| `'**/*src/**'` | Qualquer arquivo em uma pasta com o sufixo `src` em qualquer local do repositório. | -`a/src/app.js`
-`my-src/code/js/app.js` | +| `'**/*-post.md'` | Um arquivo com o sufixo `-post.md` em qualquer local do repositório. | -`my-post.md`
-`path/their-post.md` | +| `'**/migrate-*.sql'` | Um arquivo com o prefixo `migrate-` e sufixo `.sql` em qualquer local do repositório. | -`migrate-10909.sql`
-`db/migrate-v1.0.sql`
-`db/sept/migrate-v1.sql` | +| -`*.md`
-`!LEIAME.md` | Usar um sinal de exclamação (`!`) na frente de um padrão o anula. Quando um arquivo corresponde a um padrão e também corresponde a um padrão negativo definido posteriormente no arquivo, o arquivo não será incluído. | -`hello.md`
_Does not match_
-`LEIAME.md`
-`docs/hello.md` | +| -`*.md`
-`!LEIAME.md`
-`LEIAME*` | Os padrões são verificados sequencialmente. Um padrão que anula um padrão anterior irá incluir caminhos de arquivos novamente. | -`hello.md`
-`LEIAME.md`
-`LEIAME.doc` | diff --git a/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md index 66b09f5d74..adb7a3e762 100644 --- a/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md @@ -1,27 +1,27 @@ --- -title: About identity and access management for your enterprise -shortTitle: About identity and access management -intro: 'You can use {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}''s built-in authentication, or choose between CAS, LDAP, or SAML{% else %}SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM){% endif %} to centrally manage access {% if currentVersion == "free-pro-team@latest" %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}to {% data variables.product.product_location %}{% endif %}.' +title: Sobre a identidade e gestão de acesso para a sua empresa +shortTitle: Sobre identidade e gestão de acesso +intro: 'Você pode usar a autenticação incluída em {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} ou escolher entre CAS, LDAP, ou SAML{% else %}o logon único SAML (SSO) e o Sistema de Administração de Identidade de Domínio Cruzado (SCIM){% endif %} para administrar o acesso centralizadamente{% if currentVersion == "free-pro-team@latest" %}para que as organizações pertencentes à sua empresa em {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a {% data variables.product.product_location %}{% endif %}.' product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About identity and access management for your enterprise +### Sobre a identidade e gestão de acesso para a sua empresa {% if currentVersion == "github-ae@latest" %} {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -After you configure the application for {% data variables.product.product_name %} on your IdP, you can grant access to {% data variables.product.product_location %} by assigning the application to users on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." +Depois de configurar o aplicativo para {% data variables.product.product_name %} no seu IdP, você pode conceder acesso a {% data variables.product.product_location %} ao atribuir o aplicativo aos usuários no seu IdP. Para obter mais informações sobre o SAML SSO para {% data variables.product.product_name %}, consulte "[Configurar o logon único SAML para a sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)". -{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.scim.after-you-configure-saml %} Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". -To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." +Para aprender como configurar tanto o provisionamento de autenticação quanto o usuário para {% data variables.product.product_location %} com seu IdP específico, consulte "[Configurar autenticação e provisionamento com o seu provedor de identidade](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)". {% endif %} ### Leia mais -- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website -- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website +- [Wiki de SAML](https://wiki.oasis-open.org/security) no site OASIS +- [Sistema para Gerenciamento de Identidade de entre Domínios: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) no site do IETF diff --git a/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md b/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md index 4149fb466c..6a43289ead 100644 --- a/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md +++ b/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: As contas de usuário no {% data variables.product.product_location %} são preservadas quando você altera o método de autenticação, e os usuários continuarão fazendo login na mesma conta (desde que não haja alteração nos nomes de usuário). -Se o novo método de autenticação alterar nomes de usuários, serão criadas novas contas. Como administrador, você pode renomear os usuários nas configurações de administração do site ou usando a [a API de administração do usuário](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user). +Se o novo método de autenticação alterar nomes de usuários, serão criadas novas contas. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). Veja outras questões que você deve manter em mente: diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index bc52bd49c8..2d0ae19053 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -1,50 +1,41 @@ --- -title: Configuring authentication and provisioning for your enterprise using Azure AD -shortTitle: Configuring with Azure AD -intro: You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.product_location %}. -permissions: Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}. +title: Configurar a autenticação e provisionamento para sua empresa usando o Azure AD +shortTitle: Configurar com Azure AD +intro: Você pode usar um inquilino no Azure Active Directory (Azure AD) como um provedor de identidade (IdP) para gerenciar centralizadamente autenticação e provisionamento de usuário para {% data variables.product.product_location %}. +permissions: Os proprietários das empresas podem configurar a autenticação e o provisionamento de uma empresa em {% data variables.product.product_name %}. product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About authentication and user provisioning with Azure AD +### Sobre autenticação e provisionamento de usuário com Azure AD -Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs. +O Azure Active Directory (Azure AD) é um serviço da Microsoft que permite gerenciar centralmente as contas de usuários e acessar aplicativos da web. Para obter mais informações, consulte [O que é Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) na documentação da Microsoft. -To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access with SCIM. This configuration allows you to assign or unassign the {% data variables.product.prodname_ghe_managed %} application for a user account in your Azure AD tenant to automatically create, grant access to, or deactivate a corresponding user account on {% data variables.product.product_name %}. +Para gerenciar identidade e acesso para {% data variables.product.product_name %}, você pode usar um inquilino no Azure AD como um IdP de SAML para autenticação. Você também pode configurar o Azure AD para fornecer automaticamente contas e acesso com o SCIM. Esta configuração permite atribuir ou desatribuir o aplicativo de {% data variables.product.prodname_ghe_managed %} para uma conta de usuário no seu inquilino do Azure AD para automaticamente criar conceder acesso ou desativar uma conta de usuário correspondente em {% data variables.product.product_name %}. -For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." +Para obter mais informações sobre gerenciamento de identidade e acesso para a sua empresa em {% data variables.product.product_location %}, consulte "[Gerenciar identidade e acesso da sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". ### Pré-requisitos -To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs. +Para configurar o provisionamento de autenticação e usuário para {% data variables.product.product_name %} usando o Azure AD, você deve ter uma conta do Azure AD e um inquilino. Para obter mais informações, consulte o [site do Azure AD](https://azure.microsoft.com/free/active-directory) e o [Início rápido: Crie um inquilino do Azure Active Directory](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) na documentação da Microsoft. -{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs. +{% data reusables.saml.assert-the-administrator-attribute %} Para mais informações sobre a inclusão do atributo do `administrador` na solicitação do SAML do Azure AD, consulte [Como personalizar solicitações emitidas no token SAML para aplicativos corporativos](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) na documentação da Microsoft. {% data reusables.saml.create-a-machine-user %} -### Configuring authentication and user provisioning with Azure AD +### Configurar autenticação e provisionamento de usuário com Azure AD {% if currentVersion == "github-ae@latest" %} -1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. +1. No Azure AD, adicione {% data variables.product.ae_azure_ad_app_link %} ao seu inquilino e configure logon único. Para obter mais informações, consulte o [Tutorial: integração do logon único (SSO) do Azure Active Directory com {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) na documentação da Microsoft. - | Value in Azure AD | Value from {% data variables.product.prodname_ghe_managed %} - |:---------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Identifier (Entity ID) | `https://YOUR-GITHUB-AE-HOSTNAME - - - -
Reply URLhttps://YOUR-GITHUB-AE-HOSTNAME/saml/consume` | - | Sign on URL | https://YOUR-GITHUB-AE-HOSTNAME/sso | - -1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. +1. Em {% data variables.product.prodname_ghe_managed %}, insira os detalhes para o seu inquilino do Azure AD. - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} - - If you've already configured SAML SSO for {% data variables.product.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)." + - Se você já configurou SSO de SAML para {% data variables.product.product_location %} usando outro IdP e você deseja usar o Azure AD, você pode editar a sua configuração. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)". -1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)." +1. Habilitar provisionamento do usuário em {% data variables.product.product_name %} e configurar provisionamento do usuário no Azure AD. Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)". {% endif %} diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md index ef320ac2ce..d2461efe4a 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md +++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md @@ -1,6 +1,6 @@ --- -title: Configuring authentication and provisioning with your identity provider -intro: You can use an identity provider (IdP) that supports both SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to configure authentication and user provisioning for {% data variables.product.product_location %}. +title: Configurar a autenticação e provisionamento com seu provedor de identidade +intro: Você Pode usar um provedor de identidade (IdP) compatível tanto com o logon único SAML (SSO) quanto com o Sistema de Gerenciamento de Identidades de Domínio Cruzado (SCIM) para configurar a autenticação e provisionamento do usuário para {% data variables.product.product_location %}. mapTopic: true versions: github-ae: '*' diff --git a/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md index eebe52d89f..c95fb420de 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md @@ -1,9 +1,9 @@ --- -title: Configuring SAML single sign-on for your enterprise -shortTitle: Configuring SAML SSO -intro: You can configure SAML single sign-on (SSO) for your enterprise, which allows you to centrally control authentication for {% data variables.product.product_location %} using your identity provider (IdP). +title: Configurar o logon único SAML para sua empresa +shortTitle: Configurando o SAML SSO +intro: Você pode configurar o logon único SAML (SSO) para sua empresa, o que permite que você controle centralmente a autenticação para {% data variables.product.product_location %} usando seu provedor de identidade (IdP). product: '{% data reusables.gated-features.saml-sso %}' -permissions: Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}. +permissions: Os proprietários das empresas podem configurar o SAML SSO para uma empresa em {% data variables.product.product_name %}. versions: github-ae: '*' --- @@ -12,45 +12,51 @@ versions: {% if currentVersion == "github-ae@latest" %} -SAML SSO allows you to centrally control and secure access to {% data variables.product.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user. +O SAML SSO permite que você controle centralmente e proteja o acesso ao {% data variables.product.product_location %} a partir do seu IdP SAML. Quando um usuário não autenticado visita {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} redirecionará o usuário para seu IdP do SAML para efetuar a autenticação. Depois que o usuário efetua a autenticação com sucesso com uma conta no IdP, o usuário do IdP redireciona o usuário de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IdP e, em seguida, concede acesso ao usuário. -After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.product.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP. +Depois que um usuário efetua a autenticação com sucesso no seu IdP, a sessão do SAML do usuário para {% data variables.product.product_location %} fica ativa no navegador por 24 horas. Depois de 24 horas, o usuário deve efetuar a autenticação novamente com o seu IdP. {% data reusables.saml.assert-the-administrator-attribute %} -{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.scim.after-you-configure-saml %} Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". {% endif %} -### Supported identity providers +### Provedores de identidade compatíveis -{% data variables.product.product_name %} supports SAML SSO with IdPs that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. +{% data variables.product.product_name %} é compatível com o SAML SSO, com IdPs que implementam o padrão SAML 2.0. Para obter mais informações, consulte a [Wiki do SAML](https://wiki.oasis-open.org/security) no site do OASIS. -{% data variables.product.company_short %} has tested SAML SSO for {% data variables.product.product_name %} with the following IdPs. +{% data variables.product.company_short %} testou o SAML SSO para {% data variables.product.product_name %} com os seguintes IdPs. {% if currentVersion == "github-ae@latest" %} - Azure AD {% endif %} -### Enabling SAML SSO +### Habilitar o SAML SSO {% if currentVersion == "github-ae@latest" %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML Service Provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. +Os seguintes IdPs fornecem documentação sobre a configuração de do SAML SSO para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}. -| Valor | Other names | Descrição | Exemplo | -|:--------------------------------------- |:----------- |:-------------------------------------------------------------------------- |:------------------------- | -| SP Entity ID | SP URL | Your top-level URL for {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME | -| SP Assertion Consumer Service (ACS) URL | Reply URL | URL where IdP sends SAML responses | https://YOUR-GITHUB-AE-HOSTNAME/saml/consume | -| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO | https://YOUR-GITHUB-AE-HOSTNAME/sso | + | IdP | Mais informações | + |:-------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | + | Azure AD | [Tutorial: integração do logon único (SSO) do Azure Active Directory com {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) na documentação da Microsoft | + +Durante a inicialização para {% data variables.product.product_name %}, você deve configurar {% data variables.product.product_name %} como um Provedor de Serviço do SAML (SP) no seu IdP. Você deve inserir vários valores únicos no seu IdP para configurar {% data variables.product.product_name %} como um SP válido. + +| Valor | Outros nomes | Descrição | Exemplo | +|:------------------------------------------------------ |:--------------- |:---------------------------------------------------------------------------------- |:------------------------- | +| ID da Entidade do SP | URL do SP | Sua URL de nível superior para {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME | +| URL do Serviço do Consumidor de Declaração (ACS) do SP | URL de resposta | URL em que o IdP envia respostas do SAML | https://YOUR-GITHUB-AE-HOSTNAME/saml/consume | +| URL de logon único (SSO) do SP | | URL em que o IdP começa com SSO | https://YOUR-GITHUB-AE-HOSTNAME/sso | {% endif %} -### Editing the SAML SSO configuration +### Editar a configuração SAML SSO -If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.product.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate. +Se os detalhes para o seu IdP forem alterados, você deverá editar a configuração SAML SSO para o {% data variables.product.product_location %}. Por exemplo, se o certificado de seu IdP expirar, você poderá editar o valor para o certificado público. {% if currentVersion == "github-ae@latest" %} @@ -63,23 +69,23 @@ If the details for your IdP change, you'll need to edit the SAML SSO configurati {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", type the new details for your IdP. ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png) -1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method. ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) +1. Em "logon único SAML", digite os novos detalhes para o seu IdP. ![Os campos de entrada de texto com detalhes de IdP para configuração SAML SSO para uma empresa](/assets/images/help/saml/ae-edit-idp-details.png) +1. Opcionalmente, clique em {% octicon "pencil" aria-label="The edit icon" %} para configurar uma nova assinatura ou método de resumo. ![Ícone de editar para alterar a assinatura e o método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) - - Use the drop-down menus and choose the new signature or digest method. ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) -1. To ensure that the information you've entered is correct, click **Test SAML configuration**. !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) -1. Clique em **Salvar**. !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png) -1. Optionally, to automatically provision and deprovision user accounts for {% data variables.product.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." + - Use os menus suspensos e escolha a nova assinatura ou o método de resumo. ![Menus suspensos para escolher uma nova assinatura ou método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. Para garantir que a informação inserida está correta, clique em **Testar configuração de SAML**. ![Botão "Testar configuração do SAML"](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. Clique em **Salvar**. ![Botão "Salvar" para configuração do SAML SSO](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. Opcionalmente, para provisionar e desprovisionar contas de usuário automaticamente para {% data variables.product.product_location %}, reconfigure o provisionamento de usuário com SCIM. Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". {% endif %} -### Disabling SAML SSO +### Desabilitar SAML SSO {% if currentVersion == "github-ae@latest" %} {% warning %} -**Warning**: If you disable SAML SSO for {% data variables.product.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.product.product_location %}. SAML SSO sessions on {% data variables.product.product_location %} end after 24 hours. +**Aviso**: se você desabilitar o SAML SSO para {% data variables.product.product_location %}, os usuários sem sessões SAML SSO existentes não poderão entrar em {% data variables.product.product_location %}. As sessões SAML SSO em {% data variables.product.product_location %} terminam após 24 horas. {% endwarning %} @@ -92,7 +98,7 @@ If the details for your IdP change, you'll need to edit the SAML SSO configurati {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", unselect **Enable SAML authentication**. ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png) -1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**. !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png) +1. Em "Logon único SAML", selecione **Habilitar autenticação do SAML**. ![Caixa de seleção para "Habilitar autenticação do SAML"](/assets/images/help/saml/ae-saml-disabled.png) +1. Para desabilitar o SAML SSO e exigir o login com a conta de usuário integrada que você criou durante a inicialização, clique em **Salvar**. ![Botão "Salvar" para configuração do SAML SSO](/assets/images/help/saml/ae-saml-disabled-save.png) {% endif %} diff --git a/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index d65730e271..cc57824de0 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -1,30 +1,30 @@ --- -title: Configuring user provisioning for your enterprise -shortTitle: Configuring user provisioning -intro: You can configure System for Cross-domain Identity Management (SCIM) for your enterprise, which automatically provisions user accounts on {% data variables.product.product_location %} when you assign the application for {% data variables.product.product_location %} to a user on your identity provider (IdP). -permissions: Enterprise owners can configure user provisioning for an enterprise on {% data variables.product.product_name %}. +title: Configurar o provisionamento do usuário para a sua empresa +shortTitle: Configurar o provisionamento do usuário +intro: Você pode configurar o Sistema para Gerenciamento de Identidades entre Domínios (SCIM) para sua empresa, que automaticamente fornece contas de usuário em {% data variables.product.product_location %} quando você atribuir o aplicativo para {% data variables.product.product_location %} a um usuário no seu provedor de identidade (IdP). +permissions: Os proprietários das empresas podem configurar o provisionamento de usuários para uma empresa em {% data variables.product.product_name %}. product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About user provisioning for your enterprise +### Sobre provisionamento de usuários para sua empresa -{% data reusables.saml.ae-uses-saml-sso %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." +{% data reusables.saml.ae-uses-saml-sso %} Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)". -{% data reusables.scim.after-you-configure-saml %} For more information about SCIM, see [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website. +{% data reusables.scim.after-you-configure-saml %} Para obter mais informações sobre SCIM, consulte [Sistema para Gerenciamento de Identidade de Domínio Cruzado: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) no site de IETF. {% if currentVersion == "github-ae@latest" %} -Configuring provisioning allows your IdP to communicate with {% data variables.product.product_location %} when you assign or unassign the application for {% data variables.product.product_name %} to a user on your IdP. When you assign the application, your IdP will prompt {% data variables.product.product_location %} to create an account and send an onboarding email to the user. When you unassign the application, your IdP will communicate with {% data variables.product.product_name %} to invalidate any SAML sessions and disable the member's account. +A configuração do provisionamento permite que o seu IdP se comunique com {% data variables.product.product_location %} quando você atribuir ou cancela a atribuição do aplicativo para {% data variables.product.product_name %} a um usuário no seu IdP. Ao atribuir o aplicativo, seu IdP pedirá que {% data variables.product.product_location %} crie uma conta e enviar um e-mail de integração para o usuário. Ao desatribuir o aplicativo, o seu IdP irá comunicar-se com {% data variables.product.product_name %} para invalidar quaisquer sessões de SAML e desabilitar a conta do integrante. -To configure provisioning for your enterprise, you must enable provisioning on {% data variables.product.product_name %}, then install and configure a provisioning application on your IdP. +Para configurar o provisionamento para o seu negócio, você deve habilitar o provisionamento em {% data variables.product.product_name %} e, em seguida, instalar e configurar um aplicativo de provisionamento no seu IdP. -The provisioning application on your IdP communicates with {% data variables.product.product_name %} via our SCIM API for enterprises. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#scim)" in the {% data variables.product.prodname_dotcom %} REST API documentation. +O aplicativo de provisionamento no seu IdP comunica-se com {% data variables.product.product_name %} através da nossa API de SCIM para empresas. Para obter mais informações, consulte "[Administração do GitHub Enterprise](/rest/reference/enterprise-admin#scim)" na documentação da API REST de {% data variables.product.prodname_dotcom %}. {% endif %} -### Supported identity providers +### Provedores de identidade compatíveis {% data reusables.scim.supported-idps %} @@ -32,41 +32,49 @@ The provisioning application on your IdP communicates with {% data variables.pro {% if currentVersion == "github-ae@latest" %} -To automatically provision and deprovision access to {% data variables.product.product_location %} from your IdP, you must first configure SAML SSO when you initialize {% data variables.product.product_name %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." +Para prover e desprover automaticamente o acesso a {% data variables.product.product_location %} a partir do seu IdP, primeiro você deve configurar o SSO de SAML ao inicializar {% data variables.product.product_name %}. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". -You must have administrative access on your IdP to configure the application for user provisioning for {% data variables.product.product_name %}. +Você deve ter acesso administrativo no seu IdP para configurar o aplicativo para o provisionamento do usuário para {% data variables.product.product_name %}. {% endif %} -### Enabling user provisioning for your enterprise +### Habilitar provisionamento de usuários para a sua empresa {% if currentVersion == "github-ae@latest" %} -1. While signed into +1. Enquanto estiver conectado -{% data variables.product.product_location %} as an enterprise owner, create a personal access token with **admin:enterprise** scope. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." +{% data variables.product.product_location %} como proprietário corporativo, crie um token de acesso pessoal com o escopo **admin:enterprise**. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." {% note %} **Atenção**: - - To create the personal access token, we recommend using the account for the first enterprise owner that you created during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." - - You'll need this personal access token to configure the application for SCIM on your IdP. Store the token securely in a password manager until you need the token again later in these instructions. + - Para criar o token de acesso pessoal, recomendamos usar a conta para o primeiro proprietário da empresa criado durante a inicialização. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". + - Você precisará deste token de acesso pessoal para configurar o aplicativo para o SCIM no seu IdP. Armazene o token com segurança em um gerenciador de senhas até que você precise do token novamente posteriormente nestas instruções. {% endnote %} {% warning %} - **Warning**: If the user account for the enterprise owner who creates the personal access token is deactivated or deprovisioned, your IdP will no longer provision and deprovision user accounts for your enterprise automatically. Another enterprise owner must create a new personal access token and reconfigure provisioning on the IdP. + **Aviso**: Se a conta de usuário para o dono da empresa que cria o token de acesso pessoal está desativada ou desprovisionada, seu IdP não vai mais provisionar e desprovisionar contas de usuário a sua empresa automaticamente. Outro proprietário da empresa deve criar um novo token de acesso pessoal e reconfigurar o provisionamento no IdP. {% endwarning %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**. ![Checkbox for "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) -1. Clique em **Salvar**. ![Save button under "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-scim-save.png) -1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}. +1. Em "Provisionamento do Usuário do SCIM", selecione **Exigir o provisionamento do usuário do SCIM**. ![Caixa de seleção para "Exigir o provisionamento do usuário do SCIM" nas configurações de segurança das empresas](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) +1. Clique em **Salvar**. ![Salvar botão em "Exigir o provisionamento do usuário SCIM" nas configurações de segurança da empresa](/assets/images/help/enterprises/settings-scim-save.png) +1. Configurar provisionamento de usuário no aplicativo para {% data variables.product.product_name %} no seu IdP. - | Valor | Other names | Descrição | Exemplo | - |:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- | - | URL | Tenant URL | URL to the SCIM provisioning API for your enterprise on {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME/scim/v2 | - | Shared secret | Personal access token, secret token | Token for application on your IdP to perform provisioning tasks on behalf of an enterprise owner | Personal access token you created in step 1 | + Os seguintes IdPs fornecem documentação sobre configuração de provisionamento para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}. + + | IdP | Mais informações | + |:-------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | + | Azure AD | [Tutorial: Configurar {% data variables.product.prodname_ghe_managed %} para provisionamento automático do usuário](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) na documentação da Microsoft. | + + O aplicativo no seu IdP exige dois valores para provisionar ou desprovisionar contas de usuário em {% data variables.product.product_location %}. + + | Valor | Outros nomes | Descrição | Exemplo | + |:------------------ |:-------------------------------------- |:---------------------------------------------------------------------------------------------------------------- |:------------------------------------------------- | + | URL | URL do inquilino | URL para a API de provisionamento SCIM para a sua empresa em {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME/scim/v2 | + | Segredo partilhado | Token de acesso pessoal, token secreto | Token para aplicativo no seu IdP para executar tarefas de provisionamento em nome do proprietário de uma empresa | Token de acesso pessoal que você criou no passo 1 | {% endif %} diff --git a/translations/pt-BR/content/admin/authentication/index.md b/translations/pt-BR/content/admin/authentication/index.md index 5c95b61411..a442518aa3 100644 --- a/translations/pt-BR/content/admin/authentication/index.md +++ b/translations/pt-BR/content/admin/authentication/index.md @@ -1,6 +1,6 @@ --- title: Autenticação -intro: You can configure how users sign into {% data variables.product.product_name %}. +intro: Você pode configurar como os usuários conectam-se a {% data variables.product.product_name %}. redirect_from: - /enterprise/admin/authentication versions: diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md index 9b4b3f0a0a..b037d6f7ea 100644 --- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Managing identity and access for your enterprise -shortTitle: Managing identity and access -intro: You can centrally manage accounts and access to {% data variables.product.product_location %}. +title: Gerenciar identidade e acesso para a sua empresa +shortTitle: Gerenciar identidade e acesso +intro: Você pode gerenciar as contas centralmente e ter acesso a {% data variables.product.product_location %}. mapTopic: true versions: github-ae: '*' diff --git a/translations/pt-BR/content/admin/authentication/using-saml.md b/translations/pt-BR/content/admin/authentication/using-saml.md index c1c8230c9d..3304f0e048 100644 --- a/translations/pt-BR/content/admin/authentication/using-saml.md +++ b/translations/pt-BR/content/admin/authentication/using-saml.md @@ -29,7 +29,7 @@ Cada nome de usuário do {% data variables.product.prodname_ghe_server %} é det O elemento `NameID` é obrigatório, mesmo que os outros atributos estejam presentes. -A mapping is created between the `NameID` and the {% data variables.product.prodname_ghe_server %} username, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +É criado um mapeamento entre `NameID` e o nome de usuário do {% data variables.product.prodname_ghe_server %}. Portanto, o `NameID` deve ser persistente, exclusivo e não estar sujeito a alterações no ciclo de vida do usuário. {% note %} diff --git a/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md b/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md index a343b03be7..da4bcad0fd 100644 --- a/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md +++ b/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md @@ -1,31 +1,31 @@ --- -title: About enterprise configuration -intro: 'You can use the site admin dashboard{% if enterpriseServerVersions contains currentVersion %}, {% data variables.enterprise.management_console %}, and administrative shell (SSH) {% elsif currentVersion == "github-ae@latest" %} and enterprise settings or contact support{% endif %} to manage your enterprise.' +title: Sobre a configuração corporativa +intro: 'Você pode usar o painel de administração do site{% if enterpriseServerVersions contains currentVersion %}, {% data variables.enterprise.management_console %} e o shell administrativo (SSH) {% elsif currentVersion == "github-ae@latest" %} e as configurações corporativas ou entrar em contato com o suporte{% endif %} para gerenciar a sua empresa.' versions: enterprise-server: '*' github-ae: '*' --- {% if enterpriseServerVersions contains currentVersion %} -{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %} For more information, see "[Site admin dashboard](/admin/configuration/site-admin-dashboard)." +{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %} Para obter mais informações, consulte "[Painel de administração do site](/admin/configuration/site-admin-dashboard)". -{% data reusables.enterprise_site_admin_settings.about-the-management-console %} For more information, see "[Accessing the management console](/admin/configuration/accessing-the-management-console)." +{% data reusables.enterprise_site_admin_settings.about-the-management-console %} Para obter mais informações, consulte "[Acessar o console de gerenciamento](/admin/configuration/accessing-the-management-console)". -{% data reusables.enterprise_site_admin_settings.about-ssh-access %} For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +{% data reusables.enterprise_site_admin_settings.about-ssh-access %} Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". {% endif %} {% if currentVersion == "github-ae@latest" %} -The first time you access your enterprise, you will complete an initial configuration to get -{% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an idP, authenticating with SAML SSO, and configuring policies for repositories and organizations in your enterprise. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." +A primeira vez que você acessar sua empresa, você irá definir uma configuração inicial para fazer com que +{% data variables.product.product_name %} esteja pronto para usar. A configuração inicial inclui conectar a sua empresa a um idP, efetuar a autenticação com o SSO SAML e configurar políticas para repositórios e organizações da sua empresa. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". -For users to receive any emails from {% data variables.product.product_name %} after the initial configuration, you must ask {% data variables.contact.github_support %} to configure outbound email support with your SMTP server. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)." +Para os usuários receberem qualquer e-mail de {% data variables.product.product_name %} após a configuração inicial, você precisa pedir que {% data variables.contact.github_support %} configure o suporte a email de saída com o seu servidor SMTP. Para obter mais informações, consulte "[Configurar e-mail para notificações](/admin/configuration/configuring-email-for-notifications). -Later, you can use the site admin dashboard and enterprise settings to further configure your enterprise, manage users, organizations and repositories, and set policies that reduce risk and increase quality. +Posteriormente, você poderá usar o painel de administração do site e as configurações corporativas para configurar ainda mais sua empresa, gerenciar usuários, organizações e repositórios e definir políticas que reduzem o risco e aumentam a qualidade. -All enterprises are configured with subdomain isolation and support for TLS 1.2 and higher for encrypted traffic only. +Todas as empresas estão configuradas com isolamento de subdomínio e suporte para TLS 1.2 e posterior apenas para tráfego criptografado. {% endif %} ### Leia mais -- "[Managing users, organizations, and repositories](/admin/user-management)" -- "[Setting policies for your enterprise](/admin/policies)" +- "[Gerenciar usuários, organizações e repositórios](/admin/user-management)" +- "[Configurar políticas para a sua empresa](/admin/policies)" diff --git a/translations/pt-BR/content/admin/configuration/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/command-line-utilities.md index f6a1ea9840..3f33b5b25d 100644 --- a/translations/pt-BR/content/admin/configuration/command-line-utilities.md +++ b/translations/pt-BR/content/admin/configuration/command-line-utilities.md @@ -84,7 +84,7 @@ Permite encontrar o uuid do nó em `cluster.conf`. 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)". ``` shell -$ ghe-config app.github.rate_limiting_exempt_users "hubot github-actions" +$ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions" # Exempts the users hubot and github-actions from rate limits ``` {% endif %} @@ -159,7 +159,7 @@ $ ghe-es-index-status -do | column -ts, #### ghe-legacy-github-services-report -Este utilitário lista os repositórios no appliance que usam o {% data variables.product.prodname_dotcom %} Services, um método de integração que será descontinuado em 1 de outubro de 2018. Os usuários do seu appliance podem ter configurado o {% data variables.product.prodname_dotcom %} Services para criar notificações de pushes em determinados repositórios. Para obter mais informações, consulte "[Anunciar a depreciação dos serviços de {% data variables.product.prodname_dotcom %}](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" em {% data variables.product.prodname_blog %} ou "[Substituir serviços de {% data variables.product.prodname_dotcom %}](/v3/guides/replacing-github-services/)". Para saber mais sobre este comando ou consultar opções adicionais, use o sinalizador `-h`. +Este utilitário lista os repositórios no appliance que usam o {% data variables.product.prodname_dotcom %} Services, um método de integração que será descontinuado em 1 de outubro de 2018. Os usuários do seu appliance podem ter configurado o {% data variables.product.prodname_dotcom %} Services para criar notificações de pushes em determinados repositórios. Para obter mais informações, consulte "[Anunciar a depreciação dos serviços de {% data variables.product.prodname_dotcom %}](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" em {% data variables.product.prodname_blog %} ou "[Substituir serviços de {% data variables.product.prodname_dotcom %}](/developers/overview/replacing-github-services)". Para saber mais sobre este comando ou consultar opções adicionais, use o sinalizador `-h`. ```shell ghe-legacy-github-services-report diff --git a/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index 595cb26b3e..fa33e83cea 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -1,32 +1,32 @@ --- -title: Configuring data encryption for your enterprise -shortTitle: Configuring data encryption -intro: 'For encryption at rest, you can provide your own encryption key to encrypt your data under your encryption policies.' +title: Configurar criptografia de dados para a sua empresa +shortTitle: Configurar criptografia de dados +intro: 'Para criptografia estática, você pode fornecer sua própria chave de criptografia para criptografar seus dados conforme as suas políticas de criptografia.' versions: github-ae: '*' --- {% note %} -**Note:** Configuring encryption at rest with a customer-managed key is currently in beta and subject to change. +**Observação:** A configuração de criptografia estática com uma chave gerenciada pelo cliente está atualmente na versão beta e sujeita a alterações. {% endnote %} -### About data encryption +### Sobre a criptografia de dados -To provide a high level of security, {% data variables.product.product_name %} encrypts your data while at rest in the data centers and while your data is in transit between users' machines and the data centers. +Proporcionar um alto nível de segurança {% data variables.product.product_name %} criptografa seus dados em modo estático nos centros de dados e enquanto seus dados estão em trânsito entre as máquinas dos usuários e os centros de dados. -For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. After you've initialized your enterprise, you can choose to provide your own key instead. Your key should be a 2048 bit RSA private key in PEM format. +Para criptografia em trânsito, {% data variables.product.product_name %} usa o Transport Layer Security (TLS). Para criptografia em modo estático, {% data variables.product.product_name %} fornece uma chave RSA padrão. Depois de ter inicializado a sua empresa, você pode escolher fornecer a sua própria chave. A sua chave deve ser uma chave RSA privada de 2048 bits no formato PEM. -The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages. +A chave que você fornecer é armazenada em um módulo de segurança de hardware (HSM) em um cofre chave que {% data variables.product.company_short %} gerencia. -To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and delete your encryption key. Note that deleting your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. +Para configurar sua chave de criptografia, use a API REST. Existem vários pontos de extremidade da API, por exemplo, para verificar o status da criptografia, atualizar sua chave de criptografia e excluir sua chave de criptografia. Observe que que apagar sua chave irá congelar a sua empresa. Para obter mais informações sobre os pontos de extremidade da API, consulte "[Criptografia estática](/rest/reference/enterprise-admin#encryption-at-rest)" na documentação da API REST. -### Adding or updating an encryption key +### Adicionar ou atualizar uma chave de criptografia -You can add a new encryption key as often as you need. When you add a new key, the old key is discarded. Your enterprise won't experience downtime when you update the key. +Você pode adicionar uma nova chave de criptografia sempre que precisar. Ao adicionar uma chave nova, a chave antiga é descartada. A sua empresa não vai ter inatividade quando você atualizar a chave. -Your 2048 bit RSA private key should be in PEM format, for example in a file called _private-key.pem_. +Sua chave privada RSA de 2048 bits deve estar no formato PEM como, por exemplo, em um arquivo denominado _private-key.pem_. ``` -----BEGIN RSA PRIVATE KEY----- @@ -35,32 +35,32 @@ Your 2048 bit RSA private key should be in PEM format, for example in a file cal -----END RSA PRIVATE KEY----- ``` -1. To add your key, use the `PATCH /enterprise/encryption` endpoint, replacing *~/private-key.pem* with the path to your private key. +1. Para adicionar a sua chave, use o ponto de extremidade `PATCH /enterprise/encryption`, substituindo *~/private-key.pem* pelo caminho para sua chave privada. ```shell curl -X PATCH http(s)://hostname/api/v3/enterprise/encryption \ -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }" ``` -2. Optionally, check the status of the update operation. +2. Opcionalmente, verifique o status da operação de atualização. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Deleting your encryption key +### Excluir a sua chave de criptografia -To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key. +Para congelar a sua empresa, por exemplo, no caso de uma violação, você pode desabilitar a criptografia, excluindo sua chave de criptografia. -To unfreeze your enterprise after you've deleted your encryption key, contact support. Para obter mais informações, consulte "[Sobre o {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)". +Para descongelar a sua empresa depois de ter excluído sua chave de criptografia, entre em contato com o suporte. Para obter mais informações, consulte "[Sobre o {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)". -1. To delete your key and disable encryption at rest, use the `DELETE /enterprise/encryption` endpoint. +1. Para excluir sua chave e desabilitar a criptografia estática, use o ponto de extremidade `DELETE /enterprise/encryption`. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Optionally, check the status of the delete operation. +2. Opcionalmente, verifique o status da operação de exclusão. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id @@ -68,4 +68,4 @@ To unfreeze your enterprise after you've deleted your encryption key, contact su ### Leia mais -- "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation +- "[Criptografia estática](/rest/reference/enterprise-admin#encryption-at-rest)" na documentação da API REST diff --git a/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md index a64ee9b62f..28a6f4a3e0 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md @@ -6,7 +6,7 @@ redirect_from: - /enterprise/admin/articles/troubleshooting-email/ - /enterprise/admin/articles/email-configuration-and-troubleshooting/ - /enterprise/admin/user-management/configuring-email-for-notifications -intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure your enterprise to send email notifications on issue, pull request, and commit comments{% if enterpriseServerVersions contains currentVersion %}, as well as additional settings to allow inbound email replies{% endif %}.' +intro: 'Para facilitar a resposta rápida dos usuários à atividade em {% data variables.product.product_name %}, você pode configurar sua empresa para enviar notificações por e-mail sobre problemas, pull request e comentários de commit{% if enterpriseServerVersions contains currentVersion %}, bem como configurações adicionais para permitir respostas de e-mail de envio{% endif %}.' versions: enterprise-server: '*' github-ae: '*' @@ -15,16 +15,16 @@ versions: Os e-mails de notificação serão enviados se houver atividades no repositório em que o usuário estiver participando, se houver atividades em pull requests ou problemas em que ele esteja envolvido, ou se houver @menções ao usuário ou à equipe da qual ele é integrante. {% if currentVersion == "github-ae@latest" %} -Your dedicated technical account manager in -{% data variables.contact.github_support %} can configure email for notifications to be sent through your SMTP server. Make sure you include the following details in your support request. +O seu gerente de contas técnico dedicado em +{% data variables.contact.github_support %} pode configurar o e-mail para notificações serem enviadas através de seu servidor SMTP. Certifique-se de incluir os detalhes a seguir na sua solicitação de suporte. -- Your SMTP server address -- The port your SMTP server uses to send email -- The domain name that your SMTP server will send with a HELO response, if any -- The type of encryption used by your SMTP server -- The no-reply email address to use in the `From` and `To` field for all notifications +- O endereço do seu servidor SMTP +- A porta que o seu servidor SMTP usa para enviar e-mail +- O nome de domínio que o seu servidor SMTP enviará com uma resposta HELO, se houver +- O tipo de criptografia usado pelo seu servidor SMTP +- O endereço de e-mail "no-reply" a ser usado nos campos `De` e `Para` para todas as notificações -For more information about contacting support, see "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)." +Para obter mais informações sobre como entrar em contato com o suporte, consulte "[Sobre {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)". {% else %} ### Configurar SMTP @@ -161,7 +161,7 @@ Para processar corretamente os e-mails de entrada, você deve configurar um regi Se a {% data variables.product.product_location %} estiver atrás de um firewall ou estiver funcionando com um grupo de segurança do AWS, verifique se a porta 25 está aberta para todos os servidores de e-mail que enviam mensagens para `reply@reply.[hostname]`. #### Entrar em contato com o suporte -If you're still unable to resolve the problem, contact +Se ainda não conseguir resolver o problema, entre em contato {% data variables.contact.contact_ent_support %}. Para nos ajudar a resolver a questão, anexe o arquivo de saída de `http(s)://[hostname]/setup/diagnostics` ao seu e-mail. {% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md index e7f2358345..a7e0a46830 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Configuring GitHub Pages for your enterprise -intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise and choose whether to make sites publicly accessible.' +title: Configurar o GitHub Pages para a sua empresa +intro: 'Você pode habilitar ou desabilitar {% data variables.product.prodname_pages %} para a sua empresa e escolher se deseja tornar os sites acessíveis ao público.' redirect_from: - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/ - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/ @@ -13,13 +13,13 @@ versions: github-ae: '*' --- -### Enabling public sites for {% data variables.product.prodname_pages %} +### Habilitar sites públicos para {% data variables.product.prodname_pages %} -{% if enterpriseServerVersions contains currentVersion %}If private mode is enabled on your enterprise, the {% else %}The {% endif %}public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites. +{% if enterpriseServerVersions contains currentVersion %}Se o modo privado for habilitado na sua empresa, o {% else %}O {% endif %}público não poderá acessar sites de {% data variables.product.prodname_pages %} hospedados pela sua empresa, a menos que você habilite os sites públicos. {% warning %} -**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public. +**Aviso:** Se você habilitar sites públicos para {% data variables.product.prodname_pages %}, todos os sites em cada repositório da sua empresa serão acessíveis ao público. {% endwarning %} @@ -33,15 +33,15 @@ versions: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.pages-tab %} -5. Under "Pages policies", select **Public {% data variables.product.prodname_pages %}**. ![Checkbox to enable public {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/public-github-pages-checkbox.png) +5. Em "Páginas políticas", selecione **{% data variables.product.prodname_pages %}públicas**. ![Caixa de seleção para habilitar as {% data variables.product.prodname_pages %} públicas](/assets/images/enterprise/business-accounts/public-github-pages-checkbox.png) {% data reusables.enterprise-accounts.pages-policies-save %} {% endif %} -### Disabling {% data variables.product.prodname_pages %} for your enterprise +### Desabilitar {% data variables.product.prodname_pages %} para a sua empresa {% if enterpriseServerVersions contains currentVersion %} -If subdomain isolation is disabled for your enterprise, you should also disable -{% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. Para obter mais informações, consulte "[Habilitar o isolamento de subdomínio](/admin/configuration/enabling-subdomain-isolation)". +Se o isolamento de subdomínio estiver desabilitado para sua empresa, você também deverá desabilitar +{% data variables.product.prodname_pages %} para proteger você de possíveis vulnerabilidades de segurança. Para obter mais informações, consulte "[Habilitar o isolamento de subdomínio](/admin/configuration/enabling-subdomain-isolation)". {% endif %} {% if enterpriseServerVersions contains currentVersion %} @@ -54,12 +54,12 @@ If subdomain isolation is disabled for your enterprise, you should also disable {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.pages-tab %} -5. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**. ![Caixa de seleção para desabilitar o{% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) +5. Em "Páginas políticas", desmarque **{% data variables.product.prodname_pages %}públicas**. ![Caixa de seleção para desabilitar o{% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) {% data reusables.enterprise-accounts.pages-policies-save %} {% endif %} {% if enterpriseServerVersions contains currentVersion %} ### Leia mais -- "[Enabling private mode](/admin/configuration/enabling-private-mode)" +- "[Habilitar o modo privado](/admin/configuration/enabling-private-mode)" {% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise.md index 86c9b6baae..e3ac6f8214 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Configurar a sua empresa -intro: "After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization's needs." +intro: "Depois que {% data variables.product.product_name %} estiver pronto e funcionando, você poderá configurar a sua empresa para atender às necessidades da sua organização." redirect_from: - /enterprise/admin/guides/installation/basic-configuration/ - /enterprise/admin/guides/installation/administrative-tools/ diff --git a/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md index b85293af35..a7554f21e2 100644 --- a/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md +++ b/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md @@ -37,7 +37,7 @@ O {% data variables.product.prodname_ghe_server %} armazena as credenciais do {% Habilitar o {% data variables.product.prodname_github_connect %} não permitirá que os usuários do {% data variables.product.prodname_dotcom_the_website %} façam alterações no {% data variables.product.prodname_ghe_server %}. -Para obter mais informações sobre o gerenciamento de contas corporativas usando a API GraphQL, consulte "[Contas corporativas](/v4/guides/managing-enterprise-accounts)". +Para obter mais informações sobre o gerenciamento de contas corporativas usando a API GraphQL, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)". ### Habilitar o {% data variables.product.prodname_github_connect %} 1. Fazer login em diff --git a/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md index 5c3243a4cf..4112082aae 100644 --- a/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -18,17 +18,17 @@ Você pode conectar {% data variables.product.product_location %} a {% data vari Depois de conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %} e habilitar {% if currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %} para dependências vulneráveis, os dados de vulnerabilidade serão sincronizados de {% data variables.product.prodname_dotcom_the_website %} para a sua instância uma vez por hora. Também é possível sincronizar os dados de vulnerabilidade manualmente a qualquer momento. Nenhum código ou informações sobre o código da {% data variables.product.product_location %} são carregados para o {% data variables.product.prodname_dotcom_the_website %}. -{% if currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate {% data variables.product.prodname_dependabot_alerts %}. You can customize how you receive {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)". +{% if currentVersion ver_gt "enterprise-server@2. 1" %}Quando {% data variables.product.product_location %} recebe informações sobre uma vulnerabilidade, ele identificará repositórios na sua instância que usam a versão afetada da dependência e irá gerar {% data variables.product.prodname_dependabot_alerts %}. Você pode personalizar como você recebe {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)". {% endif %} -{% if currentVersion == "enterprise-server@2.21" %}When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate security alerts. Você pode personalizar a forma como recebe os alertas de segurança. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-security-alerts)". +{% if currentVersion == "enterprise-server@2. 1" %}Quando {% data variables.product.product_location %} recebe informações sobre uma vulnerabilidade, ele identifica repositórios na sua instância que usam a versão afetada da dependência e envia alertas de segurança. Você pode personalizar a forma como recebe os alertas de segurança. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-security-alerts)". {% endif %} -{% if currentVersion ver_lt "enterprise-server@2.21" %}When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate security alerts. Você pode personalizar a forma como recebe os alertas de segurança. Para obter mais informações, consulte "[Escolher o método de entrega das suas notificações](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications#choosing-the-delivery-method-for-security-alerts-for-vulnerable-dependencies)". +{% if currentVersion ver_lt "enterprise-server@2. 1" %}Quando {% data variables.product.product_location %} recebe informações sobre uma vulnerabilidade, ele identificará repositórios na sua instância que usam a versão afetada da dependência e irá gerar alertas de segurança. Você pode personalizar a forma como recebe os alertas de segurança. Para obter mais informações, consulte "[Escolher o método de entrega das suas notificações](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications#choosing-the-delivery-method-for-security-alerts-for-vulnerable-dependencies)". {% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" %} -### Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %} +### Habilitar {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis em {% data variables.product.prodname_ghe_server %} {% else %} ### Habilitar alertas de segurança para dependências vulneráveis no {% data variables.product.prodname_ghe_server %} {% endif %} @@ -37,7 +37,7 @@ Antes de habilitar {% if currentVersion ver_gt "enterprise-server@2. 1" %}{% dat {% if currentVersion ver_gt "enterprise-server@2.20" %} -{% if currentVersion ver_gt "enterprise-server@2.21" %}We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}Recomendamos configurar {% data variables.product.prodname_dependabot_alerts %} sem notificações para os primeiros dias a fim de evitar uma sobrecarga de e-mails. Após alguns dias, você poderá habilitar as notificações para receber {% data variables.product.prodname_dependabot_alerts %}, como de costume.{% endif %} {% if currentVersion == "enterprise-server@2.21" %}Recomendamos configurar alertas de segurança sem notificações nos primeiros dias para evitar uma sobrecarga de e-mails. Após alguns dias, você pode habilitar notificações para receber alertas de segurança como de costume.{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/index.md b/translations/pt-BR/content/admin/configuration/index.md index 3024b7a519..1968eda320 100644 --- a/translations/pt-BR/content/admin/configuration/index.md +++ b/translations/pt-BR/content/admin/configuration/index.md @@ -1,7 +1,7 @@ --- title: Configurar o GitHub Enterprise shortTitle: Configurar o GitHub Enterprise -intro: "You can configure your enterprise to suit your organization's needs." +intro: "É possível configurar sua empresa para atender às necessidades da sua organização." redirect_from: - /enterprise/admin/configuration versions: diff --git a/translations/pt-BR/content/admin/configuration/initializing-github-ae.md b/translations/pt-BR/content/admin/configuration/initializing-github-ae.md index aa6af7a305..ca8b44834e 100644 --- a/translations/pt-BR/content/admin/configuration/initializing-github-ae.md +++ b/translations/pt-BR/content/admin/configuration/initializing-github-ae.md @@ -1,27 +1,27 @@ --- -title: Initializing GitHub AE -intro: 'To get your enterprise ready to use, you can complete the initial configuration of {% data variables.product.product_name %}.' +title: Inicializar o GitHub AE +intro: 'Para deixar a sua empresa pronta para uso, você pode definir a configuração inicial de {% data variables.product.product_name %}.' versions: github-ae: '*' --- -### About initialization +### Sobre a inicialização -Before you can initialize your enterprise, you must purchase {% data variables.product.product_name %}. For more information, contact {% data variables.contact.contact_enterprise_sales %}. +Antes de inicializar sua empresa, você deve comprar {% data variables.product.product_name %}. Para mais informações, entre em contato com {% data variables.contact.contact_enterprise_sales %}. -After you purchase {% data variables.product.product_name %}, we'll ask you to provide an email address and username for the person you want to initialize the enterprise. Your dedicated technical account manager in {% data variables.contact.enterprise_support %} will create an account for the enterprise owner and send the enterprise owner an email to log into {% data variables.product.product_name %} and complete the initialization. Make sure the information you provide matches the intended enterprise owner's information in the IdP. For more information about enterprise owners, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-owner)." +Após comprar {% data variables.product.product_name %}, pediremos que você informe um endereço de e-mail e nome de usuário da pessoa que deseja inicializar a empresa. O seu gerente de conta técnico dedicado em {% data variables.contact.enterprise_support %} criará uma conta para o proprietário da empresa e enviará um e-mail para o dono da empresa para entrar em {% data variables.product.product_name %} e concluir a inicialização. Certifique-se de que as informações fornecidas correspondam às informações do proprietário da empresa pretendido no IdP. Para obter mais informações sobre os proprietários corporativos, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-owner)". -During initialization, the enterprise owner will name your enterprise, configure SAML SSO, create policies for all organizations in your enterprise, and configure a support contact for your users. +Durante a inicialização, o proprietário da empresa irá nomear a sua empresa, configurar o SAML SSO, criar políticas para todas as organizações da sua empresa e configurar um contato de suporte para seus usuários. ### Pré-requisitos {% note %} -**Note**: Before you begin initialization, store the initial username and password for {% data variables.product.prodname_ghe_managed %} securely in a password manager. {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Observação**: Antes de dar início à inicialização, armazene o nome de usuário e senha iniciais para {% data variables.product.prodname_ghe_managed %} de forma segura em um gerenciador de senhas. {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -1. To initialize {% data variables.product.product_location %}, you must have a SAML identity provider (IdP). {% data reusables.saml.ae-uses-saml-sso %} To connect your IdP to your enterprise during initialization, you should have your IdP's Entity ID (SSO) URL, Issuer ID URL, and public signing certificate (Base64-encoded). For more information, see "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)." +1. Para inicializar {% data variables.product.product_location %}, você deve ter um provedor de identidade (IdP) SAML. {% data reusables.saml.ae-uses-saml-sso %} Para conectar seu IdP à sua empresa durante a inicialização, você deve ter a URL do ID da Entidade do seu IdP (SSO), a URL do ID do Emissor e o certificado de assinatura pública (codificado em Base64). Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso para sua empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)". {% note %} @@ -31,43 +31,43 @@ During initialization, the enterprise owner will name your enterprise, configure 2. {% data reusables.saml.assert-the-administrator-attribute %} -### Signing in and naming your enterprise +### Efetuar login e nomear a sua empresa -1. Follow the instructions in your welcome email to reach your enterprise. -2. Type your credentials under "Change password", then click **Change password**. -3. Under "What would you like your enterprise account to be named?", type the enterprise's name, then click **Save and continue**. !["Save and continue" button for naming an enterprise](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) +1. Siga as instruções no seu e-mail de boas-vindas para chegar à sua empresa. +2. Digite as suas credenciais em "Alterar senha" e, em seguida, clique em **Alterar senha**. +3. Em "Como você gostaria que sua conta corporativa fosse nomeada?", digite o nome da empresa e clique em **Salvar e continuar**. ![Botão "Salvar e continuar" para nomear uma empresa](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) -### Connecting your IdP to your enterprise +### Conectar o seu IdP à sua empresa -To configure authentication for {% data variables.product.product_name %}, you must provide {% data variables.product.product_name %} with the details for your SAML IdP. {% data variables.product.company_short %} recommends using Azure AD as your IdP. For more information, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." +Para configurar a autenticação para {% data variables.product.product_name %}, você deve fornecer os detalhes do seu IdP SAML para {% data variables.product.product_name %}. {% data variables.product.company_short %} recomenda usar o Azure AD como seu IdP. Para obter mais informações, consulte "[Configurar a autenticação e provisionamento com seu provedor de identidade](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)". -1. To the right of "Set up your identity provider", click **Configure**. !["Configure" button for IdP configuration](/assets/images/enterprise/configuration/ae-idp-configure.png) -1. Under "Sign on URL", copy and paste the URL for your SAML IdP. ![Text field for SAML IdP's sign-on URL](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) -1. Under "Issuer", copy and paste the issuer URL for your SAML IdP. ![Text field for SAML IdP's issuer URL](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) -1. Under "Public certificate", copy and paste the public certificate for your SAML IdP. ![Text field for SAML IdP's public certificate](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) -1. Click **Test SAML configuration** to ensure that the information you've entered is correct. !["Test SAML configuration" button](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) -1. Clique em **Salvar**. !["Save" button for IdP configuration](/assets/images/enterprise/configuration/ae-save.png) +1. À direita de "Configure o seu provedor de identidade", clique em **Configurar**. ![Botão "Configurar" para configuração de IdP](/assets/images/enterprise/configuration/ae-idp-configure.png) +1. Em "URL de logon", copie e cole a URL no seu IdP do SAML. ![Campo de texto para URL de logon do IdP do SAML](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) +1. Em "Emissor", copie e cole a URL do emissor para o seu IdP do SAML. ![Campo de texto para a URL do emissor do IdP do SAML](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) +1. Em "Certificado público, copie e cole o certificado público no seu IdP do SAML. ![Campo de texto para o certificado público do IdP do SAML](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) +1. Clique em **Testar a configuração do SAML** para garantir que a informação inserida está correta. ![Botão "Testar configuração do SAML"](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) +1. Clique em **Salvar**. ![Botão "Salvar" para configuração de IdP](/assets/images/enterprise/configuration/ae-save.png) -### Setting your enterprise policies +### Configurar as suas políticas empresariais -Configuring policies will set limitations for repository and organization management for your enterprise. These can be reconfigured after the initialization process. +A configuração de políticas definirá limitações para o gerenciamento do repositório e da organização para a sua empresa. Elas podem ser reconfiguradas após o processo de inicialização. -1. To the right of "Set your enterprise policies", click **Configure**. !["Configure" button for policies configuration](/assets/images/enterprise/configuration/ae-policies-configure.png) -2. Under "Default Repository Permissions", use the drop-down menu and click a default permissions level for repositories in your enterprise. If a person has multiple avenues of access to an organization, either individually, through a team, or as an organization member, the highest permission level overrides any lower permission levels. Optionally, to allow organizations within your enterprise to set their default repository permissions, click **No policy** ![Drop-down menu for default repository permissions options](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) -3. Under "Repository creation", choose whether you want to allow members to create repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy**. !["Members can create repositories" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) -4. Under "Repository forking", choose whether to allow forking of private and internal repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy** ![Drop-down menu for repository forking permissions options](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) -5. Under "Repository invitations", choose whether members or organization owners can invite collaborators to repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy** ![Drop-down menu for repository invitation permissions options](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) -6. Under "Default repository visibility", use the drop-down menu and click the default visibility setting for new repositories. ![Drop-down menu for default repository visibility options](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) -7. Under "Users can create organizations", use the drop-down menu to enable or disable organization creation access for members of the enterprise. ![Drop-down menu for organization creation permissions options](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) -8. Under "Force pushes", use the drop-down menu and choose whether to allow or block force pushes. ![Drop-down menu for force pushes configuration options](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) -9. Under "Git SSH access", use the drop-down menu and choose whether to enable Git SSH access for all repositories in the enterprise. ![Drop-down menu for Git SSH access options](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) -10. Clique em **Salvar** !["Save" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-save.png) -11. Optionally, to reset all selections, click "Reset to default policies". ![Link to reset all default policies](/assets/images/enterprise/configuration/ae-reset-default-options.png) +1. À direita de "Configurar as suas políticas corporativas", clique em **Configurar**. ![Botão "Configurar" para configuração de políticas](/assets/images/enterprise/configuration/ae-policies-configure.png) +2. Em "Permissões padrão de repositórios" use o menu suspenso e clique em um nível padrão de permissões para repositórios da sua empresa. Se uma pessoa tem várias possibilidades de acesso a uma organização, individualmente, por meio de uma equipe ou como integrante da organização, o nível de permissão mais alto substitui todos os níveis de permissão inferiores. Opcionalmente, para permitir que as organizações da sua empresa definam suas permissões padrão no repositório, clique em **Sem políticas** ![Menu suspenso para opções de permissões padrão do repositório](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) +3. Em "Criação de repositório", escolha se deseja permitir que os integrantes criem repositórios. Opcionalmente, para permitir que as organizações dentro da empresa definam permissões, clique em **Sem política**. ![Botão "Integrantes podem criar repositórios" para configuração de políticas corporativas](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) +4. Na "Bifurcação do repositório", escolha se deseja permitir a bifurcação de repositórios privados ou internos. Opcionalmente, para permitir que as organizações dentro da empresa definam permissões, clique em **Sem política** ![Menu suspenso para opções de permissões de bifurcação do repositório](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) +5. Em "Convites do repositório", escolha se os integrantes ou proprietários ou da organização podem convidar colaboradores para repositórios. Opcionalmente, para permitir que as organizações dentro da empresa definam permissões, clique em **Sem política** ![Menu suspenso para opções de permissões de convite de repositório](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) +6. Em "Visibilidade padrão do repositório", use o menu suspenso e clique na configuração de visibilidade padrão para novos repositórios. ![Menu suspenso para opções padrão de visibilidade do repositório](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) +7. Em "Os usuários podem criar organizações", use o menu suspenso para habilitar ou desabilitar o acesso à criação da organização para os integrantes da empresa. ![Menu suspenso para opções de permissão de criação de organização](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) +8. Em "Pushes forçados", use o menu suspenso e escolha se deseja permitir ou bloquear pushes forçados. ![Menu suspenso para opções de configuração de push forçado](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) +9. Em "Acesso SSH ao Git", use o menu suspenso e escolha se deseja habilitar o acesso SSH ao Git para todos os repositórios da empresa. ![Menu suspenso para opções de acesso SSH ao Git](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) +10. Clique em **Salvar** ![Botão "Salvar" para configuração das políticas corporativas](/assets/images/enterprise/configuration/ae-save.png) +11. Opcionalmente, para redefinir todas as seleções, clique em "Redefinir para as políticas padrão". ![Link para redefinir todas as políticas padrão](/assets/images/enterprise/configuration/ae-reset-default-options.png) -### Setting your internal support contact +### Configurar seu contato de suporte interno -You can configure the method your users will use to contact your internal support team. This can be reconfigured after the initialization process. +Você pode configurar o método que os seus usuários usarão para entrar em contato com sua equipe de suporte interno. Isto pode ser reconfigurado após o processo de inicialização. -1. To the right of "Internal support contact", click **Configure**. !["Configure" button for internal support contact configuration](/assets/images/enterprise/configuration/ae-support-configure.png) -2. Under "Internal support contact", select the method for users of your enterprise to contact support, through a URL or an e-mail address. Then, type the support contact information. ![Text field for internal support contact URL](/assets/images/enterprise/configuration/ae-support-link-url.png) -3. Clique em **Salvar**. !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png) +1. À direita do "Contato de suporte interno", clique em **Configurar**. ![Botão "Configurar" para configuração do contato de suporte interno](/assets/images/enterprise/configuration/ae-support-configure.png) +2. Em "Contato de suporte interno, selecione o método para os usuários da sua empresa contactar o suporte, por meio de um URL ou endereço de e-mail. Em seguida, digite as informações de contato de suporte. ![Campo de texto para a URL de contato de suporte interno](/assets/images/enterprise/configuration/ae-support-link-url.png) +3. Clique em **Salvar**. ![Botão "Salvar" para configuração de contato de suporte do Enterprise](/assets/images/enterprise/configuration/ae-save.png) diff --git a/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index d20a711bd0..645f01789e 100644 --- a/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -1,11 +1,11 @@ --- -title: Restricting network traffic to your enterprise -shortTitle: Restricting network traffic -intro: 'You can restrict access to your enterprise to connections from specified IP addresses.' +title: Restringir o tráfego de rede para a sua empresa +shortTitle: Restringir tráfego de rede +intro: 'Você pode restringir o acesso a conexões corporativas a partir de endereços IP especificados.' versions: github-ae: '*' --- -By default, authorized users can access your enterprise from any IP address. You can restrict access to specific IP addresses such as your physical office locations by contacting support. +Por padrão, os usuários autorizados podem acessar sua empresa a partir de qualquer endereço IP. Você pode restringir o acesso a endereços IP específicos, como seus locais físico de escritório, entrando em contato com o suporte. -Contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access your enterprise. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules for your enterprise to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/receiving-help-from-github-support)." +Entre em contato com {% data variables.contact.github_support %} com os endereços IP que devem ter permissão para acessar a sua empresa. Especifica os intervalos de endereços usando o formato CIDR padrão (Encaminhamento sem Classe entre Domínios). {% data variables.contact.github_support %} irá configurar as regras de firewall apropriadas para sua empresa para restringir o acesso à rede por meio de HTTP, SSH, HTTPS e SMTP. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/receiving-help-from-github-support)". diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md b/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md index 89d045d1e7..c62ef59472 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md @@ -11,7 +11,7 @@ versions: ### Configurar um servidor externo `collectd` -Se você ainda não configurou um servidor externo `collectd`, será preciso fazê-lo antes de ativar o encaminhamento `collectd` na {% data variables.product.product_location %}. Seu servidor `collectd` deve ser configurado executando uma versão `collectd` 5.x ou mais recente. +Se você ainda não configurou um servidor externo `collectd`, será preciso fazê-lo antes de ativar o encaminhamento `collectd` na {% data variables.product.product_location %}. Seu servidor `collectd` deve estar executando uma versão `collectd` 5.x ou superior. 1. Faça login no servidor `collectd`. 2. Crie ou edite o arquivo de configuração `collectd` para carregar o plugin de rede e preencher as diretivas de servidor e porta com os valores adequados. Na maioria das distribuições, esses dados ficam em `/etc/collectd/collectd.conf` diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index 56f9b9cace..65a7243970 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -57,32 +57,36 @@ Antes de definir um centro de dados secundário para seus nós passivos, certifi mysql-master = HOSTNAME redis-master = HOSTNAME primary-datacenter = default - ``` + ``` - Opcionalmente, altere o nome do centro de dados primário para algo mais descritivo ou preciso, editando o valor do `primary-datacenter`. 4. {% data reusables.enterprise_clustering.configuration-file-heading %} Embaixo do cabeçalho de cada nó, adicione um novo par chave-valor para atribuir o nó a um centro de dados. Use o mesmo valor do `primary-datacenter` da etapa 3 acima. Por exemplo, se você quiser usar o nome-padrão (`padrão`) adicionar o seguinte par de chave-valor à seção para cada nó. - centro de dados = padrão + ``` + centro de dados = padrão + ``` Ao concluir, a seção para cada nó no arquivo de configuração de cluster deve parecer-se com o exemplo a seguir. {% data reusables.enterprise_clustering.key-value-pair-order-irrelevant %} - ```shell - [cluster "HOSTNAME"] - datacenter = default - hostname = HOSTNAME - ipv4 = IP ADDRESS + ```shell + [cluster "HOSTNAME"] + datacenter = default + hostname = HOSTNAME + ipv4 = IP ADDRESS + ... ... - ... - ``` + ``` - {% note %} + {% note %} - **Observação**: Se você alterou o nome do centro de dados primário no passo 3, encontre o par chave-valor `consul-datacenter` chave-valor na seção para cada nó e altere o valor para o centro de dados primário renomeado. Por exemplo, se você nomeou o centro de dados `primário`, use o seguinte par de chave-valor para cada nó. + **Observação**: Se você alterou o nome do centro de dados primário no passo 3, encontre o par chave-valor `consul-datacenter` chave-valor na seção para cada nó e altere o valor para o centro de dados primário renomeado. Por exemplo, se você nomeou o centro de dados `primário`, use o seguinte par de chave-valor para cada nó. - consul-datacenter = primary + ``` + consul-datacenter = primary + ``` - {% endnote %} + {% endnote %} {% data reusables.enterprise_clustering.apply-configuration %} @@ -103,31 +107,37 @@ Para uma exemplo de configuração, consulte "[Exemplo de Configuração'](#exam 1. Para cada nó no seu cluster, forneça uma máquina virtual correspondente com especificações idênticas, executando a mesma versão do {% data variables.product.prodname_ghe_server %}. Observe o endereço de host e endereço IPv4 para cada novo nó de cluster. Para obter mais informações, consulte "[Pré-requisitos](#prerequisites)". - {% note %} + {% note %} - **Observação**: Se você estiver reconfigurando alta disponibilidade após um failover, você poderá usar os nós antigos do centro de dados principal. + **Observação**: Se você estiver reconfigurando alta disponibilidade após um failover, você poderá usar os nós antigos do centro de dados principal. - {% endnote %} + {% endnote %} {% data reusables.enterprise_clustering.ssh-to-a-node %} 3. Faça o backup da sua configuração de cluster existente. - - cp /data/user/common/cluster.conf ~/$(date +%Y-%m-%d)-cluster.conf.backup + + ``` + cp /data/user/common/cluster.conf ~/$(date +%Y-%m-%d)-cluster.conf.backup + ``` 4. Crie uma cópia do seu arquivo de configuração de cluster existente em um local temporário, como _/home/admin/cluster-passive.conf_. Excluir pares de chave-valor únicos para endereços IP (`ipv*`), UUIDs (`uid`) e chaves públicas para WireGuard (`wireguard-pubkey`). - - grep -Ev "(?:|ipv|uuid|vpn|wireguard\-pubkey)" /data/user/common/cluster.conf > ~/cluster-passive.conf + + ``` + grep -Ev "(?:|ipv|uuid|vpn|wireguard\-pubkey)" /data/user/common/cluster.conf > ~/cluster-passive.conf + ``` 5. Remova a seção `[cluster]` do arquivo de configuração temporário do cluster que você copiou na etapa anterior. - - git config -f ~/cluster-passive.conf --remove-section cluster + + ``` + git config -f ~/cluster-passive.conf --remove-section cluster + ``` 6. Defina um nome para o centro de dados secundário onde você forneceu seus nós passivos e, em seguida, atualize o arquivo de configuração temporário do cluster com o novo nome do centro de dados. Substitua `SEGUNDÁRIO` pelo nome escolhido. ```shell - sed -i 's/datacenter = default/datacenter = SECONDARY/g' ~/cluster-passive.conf - ``` + sed -i 's/datacenter = default/datacenter = SECONDARY/g' ~/cluster-passive.conf + ``` 7. Defina um padrão para os nomes de host dos nós passivos. @@ -140,7 +150,7 @@ Para uma exemplo de configuração, consulte "[Exemplo de Configuração'](#exam 8. Abra o arquivo de configuração temporário do cluster da etapa 3 em um editor de texto. Por exemplo, você pode usar o Vim. ```shell - sudo vim ~/cluster-passive.conf + sudo vim ~/cluster-passive.conf ``` 9. Em cada seção dentro do arquivo de configuração temporária, atualize as configurações do nó. {% data reusables.enterprise_clustering.configuration-file-heading %} @@ -150,37 +160,37 @@ Para uma exemplo de configuração, consulte "[Exemplo de Configuração'](#exam - Adicione um novo par de chave-valor, `réplica = habilitado`. ```shell - [cluster "NEW PASSIVE NODE HOSTNAME"] + [cluster "NEW PASSIVE NODE HOSTNAME"] + ... + hostname = NEW PASSIVE NODE HOSTNAME + ipv4 = NEW PASSIVE NODE IPV4 ADDRESS + replica = enabled + ... ... - hostname = NEW PASSIVE NODE HOSTNAME - ipv4 = NEW PASSIVE NODE IPV4 ADDRESS - replica = enabled - ... - ... ``` 10. Adicione o conteúdo do arquivo de configuração de cluster temporário que você criou na etapa 4 ao arquivo de configuração ativo. ```shell - cat ~/cluster-passive.conf >> /data/user/common/cluster.conf - ``` + cat ~/cluster-passive.conf >> /data/user/common/cluster.conf + ``` 11. Nomeie os nós primários do MySQL e Redis no centro de dados secundário. Substitua `MYSQL REPLICA PRIMARY HOSTNAME` e `REPLICA REDIS PRIMARY HOSTNAME` pelos nomes de host do nó passivo que você forneceu para corresponder aos seus MySQL e Redis primários. ```shell - git config -f /data/user/common/cluster.conf cluster.mysql-master-replica REPLICA MYSQL PRIMARY HOSTNAME - git config -f /data/user/common/cluster.conf cluster.redis-master-replica REPLICA REDIS PRIMARY HOSTNAME - ``` + git config -f /data/user/common/cluster.conf cluster.mysql-master-replica REPLICA MYSQL PRIMARY HOSTNAME + git config -f /data/user/common/cluster.conf cluster.redis-master-replica REPLICA REDIS PRIMARY HOSTNAME + ``` 12. Habilite o MySQL para falhar automaticamente quando você gerar uma falha para os nós de réplica passiva. ```shell - git config -f /data/user/common/cluster.conf cluster.mysql-auto-failover true + git config -f /data/user/common/cluster.conf cluster.mysql-auto-failover true ``` - {% warning %} + {% warning %} - **Aviso**: Revise seu arquivo de configuração de cluster antes de prosseguir. + **Aviso**: Revise seu arquivo de configuração de cluster antes de prosseguir. - Na seção de nível superior `[cluster]`, certifique-se de que os valores para `mysql-master-replica` e `redis-master-replica` são os nomes corretos para os nós passivos no centro de dados secundário que servirão como MySQL e Redis primários após um failover. - Em cada seção para um nó ativo denominado `[cluster "ACTIVE NODE HOSTNAME"]`, verifique novamente os seguintes pares de chave-valor. @@ -194,9 +204,9 @@ Para uma exemplo de configuração, consulte "[Exemplo de Configuração'](#exam - A `réplica` deve ser configurada como `habilitada`. - Aproveite a oportunidade para remover seções para nós off-line que não estão mais sendo usados. - Para revisar uma configuração de exemplo, consulte "[Exemplo de confoguração](#example-configuration)". + Para revisar uma configuração de exemplo, consulte "[Exemplo de confoguração](#example-configuration)". - {% endwarning %} + {% endwarning %} 13. Inicializar a nova configuração de cluster. {% data reusables.enterprise.use-a-multiplexer %} @@ -207,7 +217,7 @@ Para uma exemplo de configuração, consulte "[Exemplo de Configuração'](#exam 14. Após a conclusão da inicialização , {% data variables.product.prodname_ghe_server %} exibirá a seguinte mensagem. ```shell - Inicialização de cluster concluída + Inicialização de cluster concluída ``` {% data reusables.enterprise_clustering.apply-configuration %} @@ -293,20 +303,28 @@ A replicação inicial entre os nós ativos e passivos do seu cluster leva tempo Você pode monitorar o progresso em qualquer nó do cluster, usando ferramentas de linha de comando disponíveis através do shell administrativo do {% data variables.product.prodname_ghe_server %}. Para obter mais informações sobre o shell administrativa, consulte "[Acessar o shell administrativo (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)". - Monitorar replicação dos bancos de dados: - - /usr/local/share/enterprise/ghe-cluster-status-mysql + + ``` + /usr/local/share/enterprise/ghe-cluster-status-mysql + ``` - Monitorar replicação do repositório e dos dados do Gist: - - ghe-spokes status + + ``` + ghe-spokes status + ``` - Monitorar replicação dos anexo e dos dados de LFS: - - ghe-storage replication-status + + ``` + ghe-storage replication-status + ``` - Monitorar replicação dos dados das páginas: - - ghe-dpages replication-status + + ``` + ghe-dpages replication-status + ``` Você pode usar `ghe-cluster-status` para revisar a saúde geral do seu cluster. Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-cluster-status)". diff --git a/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md index c18f580928..b585ba614e 100644 --- a/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md +++ b/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md @@ -20,6 +20,8 @@ versions: {% endnote %} +#### Requisitos mínimos + {% data reusables.enterprise_installation.hardware-rec-table %} ### Aumentar o tamanho da partição de dados diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md index 4043491892..7ab408f8ff 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md @@ -49,19 +49,19 @@ admin@ghe-data-node-0:~$ status-ghe-cluster | grep erro {% enddanger %} {% note %} - **Note:** If you're using a distribution of Linux that doesn't support the Ed25519 algorithm, use the command: + **Observação:** Se você estiver usando uma distribuição do Linux que não seja compatível com o algoritmo Ed25519, use o comando: ```shell nagiosuser@nagios:~$ ssh-keygen -t rsa -b 4096 ``` {% endnote %} -2. Copy the private key (`id_ed25519`) to the `nagios` home folder and set the appropriate ownership. +2. Copie a chave privada (`id_ed25519`) para a pasta inicial `nagios` e defina a propriedade adequada. ```shell nagiosuser@nagios:~$ sudo cp .ssh/id_ed25519 /var/lib/nagios/.ssh/ nagiosuser@nagios:~$ sudo chown nagios:nagios /var/lib/nagios/.ssh/id_ed25519 ``` -3. Para autorizar a chave pública a executar *somente* o comando `ghe-cluster-status-n`, use o prefixo `command=` no arquivo `/data/user/common/authorized_keys`. No shell administrativo de qualquer nó, modifique esse arquivo para incluir a chave pública gerada na etapa 1. For example: `command="/usr/local/bin/ghe-cluster-status -n" ssh-ed25519 AAAA....` +3. Para autorizar a chave pública a executar *somente* o comando `ghe-cluster-status-n`, use o prefixo `command=` no arquivo `/data/user/common/authorized_keys`. No shell administrativo de qualquer nó, modifique esse arquivo para incluir a chave pública gerada na etapa 1. Por exemplo: `command="/usr/local/bin/ghe-cluster-status -n" ssh-ed25519 AAAA....` 4. Valide e copie a configuração para cada nó do cluster executando `ghe-cluster-config-apply` no nó em que você modificou o arquivo `/data/user/common/authorized_keys`. diff --git a/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md index 13f5d92a6c..e3335854c4 100644 --- a/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md @@ -1,6 +1,6 @@ --- title: Sobre o Suporte do GitHub Enterprise -intro: '{% data variables.contact.github_support %} can help you troubleshoot issues that arise on {% data variables.product.product_name %}.' +intro: '{% data variables.contact.github_support %} pode ajudar você a resolver problemas que surgem em {% data variables.product.product_name %}.' redirect_from: - /enterprise/admin/enterprise-support/about-github-enterprise-support versions: @@ -16,28 +16,28 @@ versions: ### Sobre o {% data variables.contact.enterprise_support %} -{% data variables.product.product_name %} includes {% data variables.contact.enterprise_support %} in English{% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %}. +{% data variables.product.product_name %} inclui {% data variables.contact.enterprise_support %} em inglês{% if enterpriseServerVersions contains currentVersion %}e japonês{% endif %}. {% if enterpriseServerVersions contains currentVersion %} -You can contact -{% data variables.contact.enterprise_support %} through {% data variables.contact.contact_enterprise_portal %} for help with: +Você pode entrar em contato com +{% data variables.contact.enterprise_support %} por meio de {% data variables.contact.contact_enterprise_portal %} para obter ajuda com: - Instalar e usar o {% data variables.product.product_name %}; - Identificar e verificar as causas dos erros. {% endif %} -In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.premium_support %}{% else %}support for {% data variables.product.product_name %}{% endif %} offers: +Além de todos os benefícios de {% data variables.contact.enterprise_support %}, {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.premium_support %}{% else %}o suporte para {% data variables.product.product_name %}{% endif %} oferece: - Suporte gravado por meio de nosso portal de suporte 24 horas por dias, 7 dias por semana - Suporte por telefone 24 horas por dia, 7 dias por semana - - A{% if currentVersion == "github-ae@latest" %}n enhanced{% endif %} Service Level Agreement (SLA) {% if enterpriseServerVersions contains currentVersion %}with guaranteed initial response times{% endif %} + - Um{% if currentVersion == "github-ae@latest" %}n melhorou{% endif %} Contrato de Nível de Serviço (SLA) {% if enterpriseServerVersions contains currentVersion %}com tempo de resposta inicial garantido{% endif %} {% if currentVersion == "github-ae@latest" %} - - An assigned Technical Service Account Manager - - Quarterly support reviews - - Managed Admin services + - Um gerente de conta de serviço técnico atribuído + - Revisões de suporte trimestrais + - Serviços de administração gerenciados {% else if enterpriseServerVersions contains currentVersion %} - - Technical account managers + - Gerentes técnicos de conta - Acesso a conteúdo premium - Verificação de integridade agendadas - - Managed Admin hours + - Horas administrativas gerenciadas {% endif %} {% data reusables.support.government-response-times-may-vary %} @@ -50,7 +50,7 @@ Para obter mais informações, consulte a seção "[Sobre o {% data variables.co ### Entrar em contato com o {% data variables.contact.enterprise_support %} -You can contact {% data variables.contact.enterprise_support %} through {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} the {% data variables.contact.ae_azure_portal %}{% endif %} to report issues in writing. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." +Você pode entrar em contato com {% data variables.contact.enterprise_support %} através de {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} o {% data variables.contact.ae_azure_portal %}{% endif %} para relatar problemas por escrito. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)". ### Horas de operação @@ -61,7 +61,7 @@ You can contact {% data variables.contact.enterprise_support %} through {% if en {% if enterpriseServerVersions contains currentVersion %} Para problemas não urgentes, oferecemos suporte em inglês 24 horas por dia e 5 dias por semana, exceto nos fins de semana e feriados nacionais dos EUA. feriados. O tempo padrão de resposta é de 24 horas. -For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 days per week, even during national U.S. feriados. +Para problemas urgentes, nós {% else %}Nós{% endif %} estamos disponíveis 24 horas por dia, 7 dias por semana, mesmo durante feriados nacionais nos EUA. feriados. {% data reusables.support.government-response-times-may-vary %} @@ -70,16 +70,16 @@ For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 Para problemas não urgentes, o suporte em japonês está disponível de segunda-feira à sexta-feira, das 9h às 17h JST, exceto durante os feriados nacionais no Japão. Para problemas urgentes, oferecemos suporte em inglês 24 horas por dia, 7 dias por semana, mesmo durante os feriados nacionais nos EUA. feriados. -Para obter uma lista completa dos EUA. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."{% endif %} +Para obter uma lista completa dos EUA. Para ver uma lista de feriados nacionais no Japão observados por {% data variables.contact.enterprise_support %}, consulte "[Cronogramas de feriados](#holiday-schedules){% endif %} {% if enterpriseServerVersions contains currentVersion %} ### Calendário de feriados -Para problemas urgentes, fornecemos suporte em inglês 44 horas por dia, 7 dias por semana, incluindo nos EUA. {% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %} holidays. +Para problemas urgentes, fornecemos suporte em inglês 44 horas por dia, 7 dias por semana, incluindo nos EUA. {% if enterpriseServerVersions contains currentVersion %}e{% endif %} feriados japoneses. #### Feriados nos Estados Unidos -O {% data variables.contact.enterprise_support %} observa esses feriados dos EUA. holidays{% if enterpriseServerVersions contains currentVersion %}, although our global support team is available to answer urgent tickets{% endif %}. +O {% data variables.contact.enterprise_support %} observa esses feriados dos EUA. feriados{% if enterpriseServerVersions contains currentVersion %}, embora nossa equipe de suporte global esteja disponível para responder tíquetes urgentes{% endif %}. | EUA Feriado | Data de observação | | ----------------------- | ----------------------------- | @@ -124,7 +124,7 @@ Ao entrar em contato com {% data variables.contact.enterprise_support %}, você {% if enterpriseServerVersions contains currentVersion %} - [Perguntas frequentes sobre o {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) -- Section 10 on Support in the "[{% data variables.product.prodname_ghe_server %} License Agreement](https://enterprise.github.com/license)"{% endif %} -- "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% if enterpriseServerVersions contains currentVersion %} -- "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} +- Seção 10 sobre suporte no Contrato de Licença de "[{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/license)"{% endif %} +- "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% if enterpriseServerVersions contains currentVersion %} +- "[Preparar para enviar um tíquete](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} - [Enviar um tíquete](/enterprise/admin/guides/enterprise-support/submitting-a-ticket) diff --git a/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md index 3ac2a84849..18de3b0597 100644 --- a/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md +++ b/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md @@ -1,6 +1,6 @@ --- title: Preparar para enviar um tíquete -intro: 'You can expedite your issue with {% data variables.contact.enterprise_support %} by following these suggestions before you open a support ticket.' +intro: 'Você pode agilizar o seu problema com {% data variables.contact.enterprise_support %} seguindo essas sugestões antes de abrir um tíquete de suporte.' redirect_from: - /enterprise/admin/enterprise-support/preparing-to-submit-a-ticket versions: diff --git a/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md index c687980e23..b1d5b8a546 100644 --- a/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md @@ -85,7 +85,7 @@ Você pode usar essas etapas para criar e compartilhar um pacote de suporte se c #### Criar um pacote de suporte usando SSH -You can use these steps to create and share a support bundle if you have SSH access to {% data variables.product.product_location %} and have outbound internet access. +Você pode usar esses passos para criar e compartilhar um pacote de suporte se você tiver acesso de SSH ao {% data variables.product.product_location %} e tiver acesso à internet de saída. {% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} @@ -110,8 +110,8 @@ You can use these steps to create and share a support bundle if you have SSH acc #### Fazer upload de um pacote de suporte usando SSH Você pode fazer upload diretamente de um pacote de suporte para o nosso servidor nas seguintes situações: -- You have SSH access to {% data variables.product.product_location %}. -- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.product.product_location %}. +- Você tem acesso de SSH a {% data variables.product.product_location %}. +- São permitidas as conexões de saída HTTPS por meio da porta TCP 443 a partir de {% data variables.product.product_location %}. 1. Faça upload do pacote para o nosso servidor de pacotes de suporte: ```shell @@ -126,7 +126,7 @@ Para evitar que fiquem grandes demais, os pacotes só têm logs que não passara #### Criar um pacote de suporte estendido usando SSH -You can use these steps to create and share an extended support bundle if you have SSH access to {% data variables.product.product_location %} and you have outbound internet access. +Você pode usar essas etapas para criar e compartilhar um pacote de suporte estendido se você tiver acesso de SSH ao {% data variables.product.product_location %} e tiver acesso à internet de saída. 1. Baixe o pacote de suporte estendido via SSH adicionando o sinalizador `-x` ao comando `ghe-support-bundle`: ```shell @@ -138,8 +138,8 @@ You can use these steps to create and share an extended support bundle if you ha #### Fazer upload de um pacote de suporte estendido usando SSH Você pode fazer upload diretamente de um pacote de suporte para o nosso servidor nas seguintes situações: -- You have SSH access to {% data variables.product.product_location %}. -- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.product.product_location %}. +- Você tem acesso de SSH a {% data variables.product.product_location %}. +- São permitidas as conexões de saída HTTPS por meio da porta TCP 443 a partir de {% data variables.product.product_location %}. 1. Faça upload do pacote para o nosso servidor de pacotes de suporte: ```shell diff --git a/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md b/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md index c31d8df26e..8bd24a4b45 100644 --- a/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md +++ b/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md @@ -1,6 +1,6 @@ --- title: Entrar em contato com o suporte do GitHub -intro: 'Contact {% data variables.contact.enterprise_support %} using the {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or{% endif %} the support portal.' +intro: 'Entre em contato com {% data variables.contact.enterprise_support %} usando o {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} ou{% endif %} o portal de suporte.' redirect_from: - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support/ - /enterprise/admin/enterprise-support/reaching-github-support @@ -14,7 +14,7 @@ Embora a nossa equipe de suporte faça o melhor para responder às solicitaçõe ### Entrar em contato com o {% data variables.contact.enterprise_support %} -{% data variables.contact.enterprise_support %} customers can open a support ticket using the {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the {% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} the {% data variables.contact.contact_ae_portal %}{% endif %}. Marque a prioridade do tíquete como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} ou {% data variables.product.support_ticket_priority_low %}. Para obter mais informações, consulte "[Atribuir uma prioridade a um tíquete de suporte](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)" e "[Enviar um tíquete](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". +Os clientes de {% data variables.contact.enterprise_support %} podem abrir um tíquete de suporte usando o {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} ou o {% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} o {% data variables.contact.contact_ae_portal %}{% endif %}. Marque a prioridade do tíquete como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} ou {% data variables.product.support_ticket_priority_low %}. Para obter mais informações, consulte "[Atribuir uma prioridade a um tíquete de suporte](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)" e "[Enviar um tíquete](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". ### Entrar em contato com o {% data variables.contact.enterprise_support %} diff --git a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support.md b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support.md index f986bff946..c6f1b83034 100644 --- a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support.md +++ b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support.md @@ -1,6 +1,6 @@ --- title: Receber ajuda do Suporte do GitHub -intro: 'You can contact {% data variables.contact.enterprise_support %} to report a range of issues for your enterprise.' +intro: 'Você pode entrar em contato com {% data variables.contact.enterprise_support %} para relatar uma série de problemas referentes à sua empresa.' redirect_from: - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support/ - /enterprise/admin/enterprise-support/receiving-help-from-github-support diff --git a/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md b/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md index 500cc3cdcc..2338266d9a 100644 --- a/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md +++ b/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md @@ -1,6 +1,6 @@ --- title: Enviar um tíquete -intro: 'You can submit a support ticket using the {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or{% endif %} the support portal.' +intro: 'Você pode enviar um tíquete de suporte usando {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} de {% data variables.enterprise.management_console %} ou{% endif %} o portal de suporte.' redirect_from: - /enterprise/admin/enterprise-support/submitting-a-ticket versions: @@ -13,8 +13,8 @@ versions: Antes de enviar um ticket, reúna informações úteis sobre o {% data variables.contact.github_support %} e defina a melhor pessoa para fazer o contato. Para obter mais informações, consulte "[Preparar para enviar um tíquete](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)". {% if enterpriseServerVersions contains currentVersion %} -After submitting your support request and optional diagnostic information, -{% data variables.contact.github_support %} may ask you to download and share a support bundle with us. Para obter mais informações, consulte "[Enviar dados ao {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)". +Após enviar a sua solicitação de suporte e informações opcionais de diagnóstico, +{% data variables.contact.github_support %} poderá pedir que você baixe e compartilhe um pacote de suporte conosco. Para obter mais informações, consulte "[Enviar dados ao {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)". ### Enviar um tíquete usando o {% data variables.contact.enterprise_portal %} @@ -51,13 +51,13 @@ After submitting your support request and optional diagnostic information, {% if currentVersion == "github-ae@latest" %} ### Enviar um tíquete usando o {% data variables.contact.ae_azure_portal %} -Commercial customers can submit a support request in the {% data variables.contact.contact_ae_portal %}. Government customers should use the [Azure portal for government customers](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade). For more information, see [Create an Azure support request](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) in the Microsoft documentation. +Os clientes comerciais podem enviar um pedido de suporte no {% data variables.contact.contact_ae_portal %}. Clientes do governo devem usar os [Portal do Azure para clientes do governo](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade). Para obter mais informações, consulte [Criar uma solicitação de suporte ao Azure](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) na documentação da Microsoft. -For urgent issues, to ensure a quick response, after you submit a ticket, please call the support hotline immediately. Your Technical Support Account Manager (TSAM) will provide you with the number to use in your onboarding session. +Para problemas urgentes, a fim de garantir uma resposta rápida, depois que enviar um ticket, chame a linha suporte imediatamente. Seu Administrador de Conta de Suporte Técnico (TSAM) irá fornecer a você o número a ser usado na sua sessão de integração. {% endif %} ### Leia mais -- "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% if enterpriseServerVersions contains currentVersion %} -- "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)."{% endif %} +- "[Sobre {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% if enterpriseServerVersions contains currentVersion %} +- "[Sobre {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)."{% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index 8757267bb2..3123ee0986 100644 --- a/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -12,7 +12,7 @@ versions: ### Sobre as permissões de {% data variables.product.prodname_actions %} para sua empresa -Ao habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, ele fica habilitado para todas as organizações da sua empresa. Você pode optar por desativar {% data variables.product.prodname_actions %} para todas as organizações da sua empresa ou permitir apenas organizações específicas. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. +Ao habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, ele fica habilitado para todas as organizações da sua empresa. Você pode optar por desativar {% data variables.product.prodname_actions %} para todas as organizações da sua empresa ou permitir apenas organizações específicas. Você também pode limitar o uso de ações públicas, de modo que as pessoas só possam usar ações locais que existem na sua empresa. ### Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua empresa diff --git a/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 83b767df11..e2b743fada 100644 --- a/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -24,7 +24,7 @@ A ferramenta `actions-sync` só pode fazer download de ações de {% data variab ### Pré-requisitos -* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino existam na instância corporativa. O exemplo a seguir demonstra como sincronizar ações com uma organização denominada `synced-actions` em uma instância corporativa. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino existam na instância corporativa. O exemplo a seguir demonstra como sincronizar ações com uma organização denominada `synced-actions` em uma instância corporativa. Para obter mais informações, consulte "[Criar uma nova organização do zero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". * Você deve criar um token de acesso pessoal (PAT) na instância corporativa que pode criar e gravar em repositórios nas organizações de destino. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." ### Exemplo: Usando a ferramenta de `actions-sync` diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md index 556efca9fb..bf33586b9d 100644 --- a/translations/pt-BR/content/admin/index.md +++ b/translations/pt-BR/content/admin/index.md @@ -3,7 +3,7 @@ title: Administradores da Empresa redirect_from: - /enterprise/admin/hidden/migrating-from-github-fi/ - /enterprise/admin -intro: Documentation and guides for enterprise administrators, system administrators, and security specialists who {% if enterpriseServerVersions contains currentVersion %}deploy, {% endif %}configure{% if enterpriseServerVersions contains currentVersion %},{% endif %} and manage {% data variables.product.product_name %}. +intro: Documentação e guias para administradores da empresa, administradores de sistema e especialistas em segurança que {% if enterpriseServerVersions contains currentVersion %}implementam, {% endif %}configuram{% if enterpriseServerVersions contains currentVersion %},{% endif %} e gerenciam {% data variables.product.product_name %}. versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index da19bdf83d..d650283415 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -26,14 +26,14 @@ Antes de iniciar a {% data variables.product.product_location %} no Google Cloud O {% data variables.product.prodname_ghe_server %} é compatível nos seguintes tipos de máquina do Google Compute Engine (GCE). Para obter mais informações, consulte o [artigo sobre tipos de máquina do Google Cloud Platform](https://cloud.google.com/compute/docs/machine-types). -| | Memória alta | -| | ------------- | -| | n1-highmem-4 | -| | n1-highmem-8 | -| | n1-highmem-16 | -| | n1-highmem-32 | -| | n1-highmem-64 | -| | n1-highmem-96 | +| Memória alta | +| ------------- | +| n1-highmem-4 | +| n1-highmem-8 | +| n1-highmem-16 | +| n1-highmem-32 | +| n1-highmem-64 | +| n1-highmem-96 | #### Tipos de máquina recomendados @@ -54,7 +54,7 @@ Com base na contagem de licenças de usuário, recomendamos os seguintes tipos d 1. Usando a ferramenta de linha de comando [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/), liste as imagens públicas do {% data variables.product.prodname_ghe_server %}: ```shell $ gcloud compute images list --project github-enterprise-public --no-standard-images - ``` + ``` 2. Anote o nome da imagem GCE mais recente do {% data variables.product.prodname_ghe_server %}. @@ -63,18 +63,18 @@ Com base na contagem de licenças de usuário, recomendamos os seguintes tipos d Máquinas virtuais GCE são criadas como integrantes de uma rede que tem um firewall. Na rede associada à VM do {% data variables.product.prodname_ghe_server %}, você terá que configurar o firewall para permitir as portas necessárias da tabela abaixo. Para obter mais informações sobre as regras de firewall no Google Cloud Platform, consulte o guia "[Visão geral das regras de firewall](https://cloud.google.com/vpc/docs/firewalls)" do Google. 1. Usando a ferramenta de linha de comando gcloud compute, crie a rede. Para obter mais informações, consulte "[criar redes com gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" na documentação do Google. - ```shell - $ gcloud compute networks create NETWORK-NAME --subnet-mode auto - ``` + ```shell + $ gcloud compute networks create NETWORK-NAME --subnet-mode auto + ``` 2. Crie uma regra de firewall para cada porta da tabela abaixo. Para obter mais informações, consulte "[regras de firewall do gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" na documentação do Google. - ```shell - $ gcloud compute firewall-rules create RULE-NAME \ - --network NETWORK-NAME \ - --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp - ``` - Esta tabela identifica as portas necessárias e o uso de cada uma delas. + ```shell + $ gcloud compute firewall-rules create RULE-NAME \ + --network NETWORK-NAME \ + --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp + ``` + Esta tabela identifica as portas necessárias e o uso de cada uma delas. - {% data reusables.enterprise_installation.necessary_ports %} + {% data reusables.enterprise_installation.necessary_ports %} ### Alocar uma IP estática e associá-la com a VM @@ -87,21 +87,21 @@ Nas configurações de alta disponibilidade de produção, os appliances primár Para criar a instância do {% data variables.product.prodname_ghe_server %}, você deve criar uma instância do GCE com a imagem do {% data variables.product.prodname_ghe_server %} e vincular um volume de armazenamento adicional aos dados da sua instância. Para obter mais informações, consulte "[Considerações de hardware](#hardware-considerations)". 1. Usando a ferramenta de linha de comando gcloud compute, crie um disco de dados para usar como volume de armazenamento para os dados da sua instância e configure o tamanho com base na contagem de licenças de usuário. Para obter mais informações, consulte "[criar discos no gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" na documentação do Google. - ```shell - $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE - ``` + ```shell + $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE + ``` 2. Em seguida, crie uma instância usando o nome da imagem selecionada do {% data variables.product.prodname_ghe_server %} e vincule o disco de dados. Para obter mais informações, consulte "[criar instâncias no gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" na documentação do Google. - ```shell - $ gcloud compute instances create INSTANCE-NAME \ - --machine-type n1-standard-8 \ - --image GITHUB-ENTERPRISE-IMAGE-NAME \ - --disk name=DATA-DISK-NAME \ - --metadata serial-port-enable=1 \ - --zone ZONE \ - --network NETWORK-NAME \ - --image-project github-enterprise-public - ``` + ```shell + $ gcloud compute instances create INSTANCE-NAME \ + --machine-type n1-standard-8 \ + --image GITHUB-ENTERPRISE-IMAGE-NAME \ + --disk name=DATA-DISK-NAME \ + --metadata serial-port-enable=1 \ + --zone ZONE \ + --network NETWORK-NAME \ + --image-project github-enterprise-public + ``` ### Configurar a instância diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index e0ad620614..7b3202222a 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -1,26 +1,31 @@ --- title: Sobre contas corporativas -intro: 'Com {% data variables.product.prodname_ghe_server %}, você pode criar uma conta corporativa para dar aos administradores um único ponto de visibilidade e gestão para seu faturamento e uso da licença.' +intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management{% if enterpriseServerVersions contains currentVersion %} for billing and license usage{% endif %}.' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts - /enterprise/admin/overview/about-enterprise-accounts versions: - enterprise-server: '*' + enterprise-server: '>=2.20' + github-ae: '*' --- -### Sobre as contas corporativas do {% data variables.product.prodname_ghe_server %} +### Sobre as contas corporativas do {% data variables.product.product_name %} -Uma conta corporativa permite que você gerencie múltiplas organizações {% data variables.product.prodname_dotcom %} e instâncias {% data variables.product.prodname_ghe_server %}. Sua conta corporativa deve ter um manipulador, como uma conta pessoal ou organizacional no {% data variables.product.prodname_dotcom %}. Os administradores corporativos podem gerenciar configurações e preferências, como: +An enterprise account allows you to manage multiple organizations{% if enterpriseServerVersions contains currentVersion %} and {% data variables.product.prodname_ghe_server %} instances{% else %} on {% data variables.product.product_name %}{% endif %}. Sua conta corporativa deve ter um manipulador, como uma conta pessoal ou organizacional no {% data variables.product.prodname_dotcom %}. Os administradores corporativos podem gerenciar configurações e preferências, como: -- Acesso e gerenciamento de integrantes (integrantes da organização, colaboradores externos) -- Faturamento e uso de instâncias de ({% data variables.product.prodname_ghe_server %}, licenças de usuário, pacotes de {% data variables.large_files.product_name_short %}) -- Segurança (logon único, autenticação de dois fatores) -- Solicitações e compartilhamento de pacote de suporte com {% data variables.contact.enterprise_support %} +- Member access and management (organization members, outside collaborators){% if enterpriseServerVersions contains currentVersion %} +- Billing and usage ({% data variables.product.prodname_ghe_server %} instances, user licenses, {% data variables.large_files.product_name_short %} packs){% endif %} +- Security{% if enterpriseServerVersions contains currentVersion %}(single sign-on, two factor authentication) +- Requests {% if enterpriseServerVersions contains currentVersion %}and support bundle sharing {% endif %}with {% data variables.contact.enterprise_support %}{% endif %} -{% data reusables.enterprise-accounts.enterprise-accounts-billing %} +{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." + +{% if enterpriseServerVersions contains currentVersion %} Para obter mais informações sobre o {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}, consulte "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)". Para atualizar para {% data variables.product.prodname_enterprise %} ou para começar com uma conta corporativa, entre em contato com {% data variables.contact.contact_enterprise_sales %}. ### Gerenciando as licenças {% data variables.product.prodname_ghe_server %} vinculadas à sua conta corporativa {% data reusables.enterprise-accounts.admin-managing-licenses %} + +{% endif %} diff --git a/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md b/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md index 155c8606d5..45dc6b3816 100644 --- a/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md +++ b/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md @@ -1,6 +1,6 @@ --- -title: About the GitHub Enterprise API -intro: '{% data variables.product.product_name %} supports REST and GraphQL APIs.' +title: Sobre a API do GitHub Enterprise +intro: '{% data variables.product.product_name %} é compatível com APIs REST e do GraphQL.' redirect_from: - /enterprise/admin/installation/about-the-github-enterprise-server-api - /enterprise/admin/articles/about-the-enterprise-api/ @@ -13,12 +13,12 @@ versions: github-ae: '*' --- -With the APIs, you can automate many administrative tasks. Veja alguns exemplos: +Com as APIs, você pode automatizar muitas tarefas administrativas. Veja alguns exemplos: {% if enterpriseServerVersions contains currentVersion %} - Fazer alterações no {% data variables.enterprise.management_console %}. Para obter mais informações, consulte "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)." - Configurar a sincronização LDAP. Para obter mais informações, consulte "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#admin-stats)".{% endif %} -- Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)." -- Gerenciar sua conta corporativa. Para obter mais informações, consulte "[Contas corporativas](/v4/guides/managing-enterprise-accounts)". +- Colete estatísticas sobre sua empresa. Para obter mais informações, consulte " As[Estatísticas de Administrador](/rest/reference/enterprise-admin#admin-stats)". +- Gerenciar sua conta corporativa. Para obter mais informações, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)". -For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). \ No newline at end of file +Para a documentação completa sobre {% data variables.product.prodname_enterprise_api %}, consulte [{% data variables.product.prodname_dotcom %} API REST](/rest) e [{% data variables.product.prodname_dotcom%} API do GraphQL](/graphql). diff --git a/translations/pt-BR/content/admin/overview/index.md b/translations/pt-BR/content/admin/overview/index.md index 764e02bae5..5e243d5ad1 100644 --- a/translations/pt-BR/content/admin/overview/index.md +++ b/translations/pt-BR/content/admin/overview/index.md @@ -1,6 +1,6 @@ --- title: Visão Geral -intro: 'You can learn about {% data variables.product.product_name %} and manage{% if enterpriseServerVersions contains currentVersion %} accounts and access, licenses, and{% endif %} billing.' +intro: 'Você pode aprender sobre {% data variables.product.product_name %} e gerenciar contas de {% if enterpriseServerVersions contains currentVersion %} e acesso, licenças e{% endif %} faturamento.' redirect_from: - /enterprise/admin/overview versions: diff --git a/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md index 8e42153b82..0ef2520a96 100644 --- a/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Managing billing for your enterprise -intro: 'You can view billing information for your enterprise.' +title: Gerenciar a cobrança para a sua empresa +intro: 'Você pode visualizar as informações de cobrança para a sua empresa.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /enterprise/admin/installation/managing-billing-for-github-enterprise @@ -13,26 +13,26 @@ versions: {% if currentVersion == "github-ae@latest" %} -{% data reusables.github-ae.about-billing %} Once per day, {% data variables.product.prodname_dotcom %} will count the number of users with a license for your enterprise. {% data variables.product.company_short %} bills you for each licensed user regardless of whether the user logged into {% data variables.product.prodname_ghe_managed %} that day. +{% data reusables.github-ae.about-billing %} Uma vez por dia, {% data variables.product.prodname_dotcom %} contará o número de usuários com uma licença para sua empresa. {% data variables.product.company_short %} efetua a cobrança para cada usuário licenciado independentemente de o usuário estar conectado a {% data variables.product.prodname_ghe_managed %} nesse dia. -For commercial regions, the price per user per day is $1.2580645161. For 31-day months, the monthly cost for each user is $39. For months with fewer days, the monthly cost is lower. Each billing month begins at a fixed time on the first day of the calendar month. +Para regiões comerciais, o preço por usuário por dia é de $ 1,2580645161. Por meses de 31 dias, o custo mensal para cada usuário é de $ 39. Nos meses com menos dias, o custo mensal é menor. Cada mês de cobrança começa em um horário fixo no primeiro dia do mês do calendário. -If you add a licensed user mid-month, that user will only be included in the count for the days they have a license. When you remove a licensed user, that user will remain in the count until the end of that month. Therefore, if you add a user mid-month and later remove the user in the same month, the user will be included in the count from the day the user was added through the end of the month. There is no additional cost if you re-add a user during the same month the user was removed. +Se você adicionar um usuário licenciado no meio do mês, esse usuário será incluído apenas na contagem dos dias em que tem uma licença. Ao remover um usuário licenciado, esse usuário permanecerá na contagem até o final desse mês. Portanto, se você adicionar um usuário durante o mês ou depois remover o usuário no mesmo mês, o usuário será incluído na contagem a partir do dia em que o usuário foi adicionado até o final do mês. Não há custos adicionais se você adicionar novamente um usuário no mesmo mês em que o usuário foi removido. -For example, here are the costs for users with licenses on different dates. +Por exemplo, aqui estão os custos para os usuários com licenças em datas diferentes. -| Usuário | License dates | Counted days | Cost | -| --------- | ------------------------------------------------------- | ------------ | ------ | -| @octocat | January 1 - January 31 | 31 | $39 | -| @robocat | February 1 - February 28 | 29 | $35.23 | -| @devtocat | January 15 - January 31 | 17 | $21.39 | -| @doctocat | January 1 - January 15 | 31 | $39 | -| @prodocat | January 7 - January 15 | 25 | $31.45 | -| @monalisa | January 1 - January 7,
January 15 - January 31 | 31 | $39 | +| Usuário | Datas de licença | Dias contados | Custo | +| --------- | ------------------------------------------------------------------ | ------------- | ------- | +| @octocat | 1 de Janeiro - 31 de Janeiro | 31 | $ 39 | +| @robocat | 1 de fevereiro - 28 de fevereiro | 29 | $ 35,23 | +| @devtocat | 15 de Janeiro - 31 de Janeiro | 17 | $ 21,39 | +| @doctocat | 1 de Janeiro - 15 de Janeiro | 31 | $ 39 | +| @prodocat | 7 de Janeiro - 15 de Janeiro | 25 | $ 31,45 | +| @monalisa | 1 de janeiro - 7 de janeiro
15 de janeiro - 31 de janeiro | 31 | $ 39 | -Your enterprise can include one or more instances. {% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day. +A sua empresa pode incluir uma ou mais instâncias. {% data variables.product.prodname_ghe_managed %} tem uma instância mínima de 500 usuários. {% data variables.product.company_short %} cobra de você um mínimo de 500 usuários por instância, mesmo que haja menos de 500 usuários com uma licença nesse dia. -You can see your current usage in your [Azure account portal](https://portal.azure.com). +Você pode ver seu uso atual no seu [Portal da conta do Azure](https://portal.azure.com). {% else %} @@ -40,7 +40,7 @@ You can see your current usage in your [Azure account portal](https://portal.azu As contas corporativas atualmente estão disponíveis para clientes do {% data variables.product.prodname_enterprise %} que pagam com fatura. A cobrança de todas as organizações e instâncias {% data variables.product.prodname_ghe_server %} conectadas à sua conta corporativa é agregada em uma única fatura para todos os seus serviços pagos do {% data variables.product.prodname_dotcom_the_website %} (incluindo licenças pagas nas organizações, pacotes de dados do {% data variables.large_files.product_name_long %} e assinaturas de apps do {% data variables.product.prodname_marketplace %}). -Proprietários corporativos e gerentes de cobrança podem acessar e gerenciar todas as configurações de cobrança relativas a contas corporativas. For more information about enterprise accounts, {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and {% endif %}"[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)."For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +Proprietários corporativos e gerentes de cobrança podem acessar e gerenciar todas as configurações de cobrança relativas a contas corporativas. Para mais informações sobre contas corporativas, {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" e {% endif %}"[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization). "Para obter mais informações sobre como gerenciar gerentes de cobrança, consulte "[Convidar pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". ### Visualizando sua fatura atual diff --git a/translations/pt-BR/content/admin/overview/system-overview.md b/translations/pt-BR/content/admin/overview/system-overview.md index 8dad72f6f5..902c96e5c3 100644 --- a/translations/pt-BR/content/admin/overview/system-overview.md +++ b/translations/pt-BR/content/admin/overview/system-overview.md @@ -77,7 +77,7 @@ A equipe de segurança de aplicativos do {% data variables.product.prodname_dotc #### Serviços externos e acesso ao suporte -O {% data variables.product.prodname_ghe_server %} pode operar sem acessos de saída da sua rede para serviços externos. Alternativamente, você pode habilitar a integração com serviços externos de correio eletrônico, monitoramento externo e encaminhamento de logs. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)," "[Setting up external monitoring](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)," and "[Log forwarding](/admin/user-management/log-forwarding)." +O {% data variables.product.prodname_ghe_server %} pode operar sem acessos de saída da sua rede para serviços externos. Alternativamente, você pode habilitar a integração com serviços externos de correio eletrônico, monitoramento externo e encaminhamento de logs. Para obter mais informações, consulte "[Configurar e-mail para notificações](/admin/configuration/configuring-email-for-notifications), "[Configurar o monitoramento externo](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)" e "[Encaminhamento de registro](/admin/user-management/log-forwarding)". Você pode levantar e enviar dados de soluções de problemas para o {% data variables.contact.github_support %}. Para obter mais informações, consulte "[Enviar dados para o {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)". @@ -108,7 +108,7 @@ O {% data variables.product.prodname_ghe_server %} oferece quatro métodos de au #### Log de auditoria e acesso -O {% data variables.product.prodname_ghe_server %} armazena logs do sistema operacional tradicional e de aplicativos. O aplicativo também grava logs de auditoria e segurança detalhados, que são armazenados permanentemente pelo {% data variables.product.prodname_ghe_server %}. Os dois tipos de logs podem ser encaminhados em tempo real para destinos múltiplos via protocolo `syslog-ng`. For more information, see "[Log forwarding](/admin/user-management/log-forwarding)." +O {% data variables.product.prodname_ghe_server %} armazena logs do sistema operacional tradicional e de aplicativos. O aplicativo também grava logs de auditoria e segurança detalhados, que são armazenados permanentemente pelo {% data variables.product.prodname_ghe_server %}. Os dois tipos de logs podem ser encaminhados em tempo real para destinos múltiplos via protocolo `syslog-ng`. Para obter mais informações, consulte "[Encaminhamento de registro](/admin/user-management/log-forwarding)". Logs de acesso e auditoria contêm informações como as seguintes. diff --git a/translations/pt-BR/content/admin/packages/configuring-third-party-storage-for-packages.md b/translations/pt-BR/content/admin/packages/configuring-third-party-storage-for-packages.md index c23aba8618..3b99b93bf2 100644 --- a/translations/pt-BR/content/admin/packages/configuring-third-party-storage-for-packages.md +++ b/translations/pt-BR/content/admin/packages/configuring-third-party-storage-for-packages.md @@ -13,7 +13,7 @@ versions: {% data variables.product.prodname_registry %} em {% data variables.product.prodname_ghe_server %} usa armazenamento externo de blob para armazenar seus pacotes. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_registry %}. -No momento, {% data variables.product.prodname_registry %} é compatível com o armazenamento do blob com Amazon Web Services (AWS) S3. MinIO também é compatível, mas a configuração não está atualmente implementada na interface de {% data variables.product.product_name %}. You can use MinIO for storage by following the instructions for AWS S3, entering the analogous information for your MinIO configuration. +No momento, {% data variables.product.prodname_registry %} é compatível com o armazenamento do blob com Amazon Web Services (AWS) S3. MinIO também é compatível, mas a configuração não está atualmente implementada na interface de {% data variables.product.product_name %}. Você pode usar MinIO para armazenamento, seguindo as instruções para AWS S3, inserindo as informações análogas para a configuração do seu MinIO. Antes de configurar o armazenamento de terceiros para {% data variables.product.prodname_registry %} em {% data variables.product.prodname_dotcom %}, você deve configurar um bucket com seu provedor de armazenamento de terceiros. Para mais informações sobre como instalar e executar um bucket de minIO para usar com {% data variables.product.prodname_registry %}, consulte o "[Início rápido para configurar o armazenamento de MinIO](/admin/packages/quickstart-for-configuring-minio-storage)". Para a melhor experiência, recomendamos o uso de um bucket dedicado para {% data variables.product.prodname_registry %}, separado do bucket usado para armazenamento para {% data variables.product.prodname_actions %}. @@ -21,7 +21,10 @@ Para a melhor experiência, recomendamos o uso de um bucket dedicado para {% dat {% warning %} -**Aviso:** Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. +**Avisos:** +- É fundamental que você defina as políticas de acesso restritivas que você deseja para o seu bucket de armazenamento porque {% data variables.product.company_short %} não aplica permissões específicas de objeto ou listas de controle de acesso adicionais (ACLs) à configuração do seu bucket de armazenamento. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. Para obter mais informações, consulte [Configurar as permissões de acesso de objetos](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html) na documentação do AWS. +- Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. +- Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. {% endwarning %} diff --git a/translations/pt-BR/content/admin/packages/index.md b/translations/pt-BR/content/admin/packages/index.md index 1b91d14bf7..2a5c94fda0 100644 --- a/translations/pt-BR/content/admin/packages/index.md +++ b/translations/pt-BR/content/admin/packages/index.md @@ -1,6 +1,5 @@ --- title: Gerenciar o GitHub Packages para a sua empresa -shortTitle: GitHub Package Registry intro: 'Você pode habilitar o {% data variables.product.prodname_registry %} para a sua empresa e gerenciar configurações de {% data variables.product.prodname_registry %} e tipos de pacotes permitidos.' redirect_from: - /enterprise/admin/packages @@ -11,5 +10,6 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} {% link_with_intro /enabling-github-packages-for-your-enterprise %} +{% link_with_intro /quickstart-for-configuring-minio-storage %} {% link_with_intro /configuring-packages-support-for-your-enterprise %} {% link_with_intro /configuring-third-party-storage-for-packages %} diff --git a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md index ac25e08892..0b2f16875e 100644 --- a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md +++ b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md @@ -21,10 +21,10 @@ Você pode usar uma ferramenta de gerenciamento de contêineres do Linux para cr {% data reusables.linux.ensure-docker %} 2. Crie o arquivo `Dockerfile.alpine-3.3` que contém estas informações: - ``` - FROM gliderlabs/alpine:3.3 - RUN apk add --no-cache git bash - ``` + ``` + FROM gliderlabs/alpine:3.3 + RUN apk add --no-cache git bash + ``` 3. No diretório que contém `Dockerfile.alpine-3.3`, crie uma imagem: ```shell @@ -36,37 +36,37 @@ Você pode usar uma ferramenta de gerenciamento de contêineres do Linux para cr > ---> Using cache > ---> 0250ab3be9c5 > Successfully built 0250ab3be9c5 - ``` + ``` 4. Crie um contêiner: ```shell $ docker create --name pre-receive.alpine-3.3 pre-receive.alpine-3.3 /bin/true - ``` + ``` 5. Exporte o contêiner Docker para um arquivo `tar` compactado por `gzip`: ```shell $ docker export pre-receive.alpine-3.3 | gzip > alpine-3.3.tar.gz - ``` + ``` - O arquivo `alpine-3.3.tar.gz` está pronto para o upload no appliance do {% data variables.product.prodname_ghe_server %}. + O arquivo `alpine-3.3.tar.gz` está pronto para o upload no appliance do {% data variables.product.prodname_ghe_server %}. ### Criar um ambiente de hook pre-receive usando chroot 1. Crie um ambiente Linux `chroot`. 2. Crie um arquivo `tar` do diretório `chroot` compactado em um `gzip`. - ```shell - $ cd /path/to/chroot - $ tar -czf /path/to/pre-receive-environment.tar.gz . + ```shell + $ cd /path/to/chroot + $ tar -czf /path/to/pre-receive-environment.tar.gz . ``` - {% note %} + {% note %} - **Notas:** - - Não inclua caminhos do diretório principal de arquivos dentro do arquivo tar, como `/path/to/chroot`. - - `/bin/sh` deve existir e ser executável, como o ponto de entrada no ambiente chroot. - - Ao contrário de chroots tradicionais, o diretório `dev` não é exigido pelo ambiente chroot para hooks pre-receive. + **Notas:** + - Não inclua caminhos do diretório principal de arquivos dentro do arquivo tar, como `/path/to/chroot`. + - `/bin/sh` deve existir e ser executável, como o ponto de entrada no ambiente chroot. + - Ao contrário de chroots tradicionais, o diretório `dev` não é exigido pelo ambiente chroot para hooks pre-receive. - {% endnote %} + {% endnote %} Para obter mais informações sobre como criar um ambiente chroot, consulte "[Chroot](https://wiki.debian.org/chroot)" na *Debian Wiki*, "[BasicChroot](https://help.ubuntu.com/community/BasicChroot)" na *Ubuntu Community Help Wiki* ou "[Instalar Alpine Linux em chroot](http://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot)" na *Alpine Linux Wiki*. @@ -89,4 +89,4 @@ Para obter mais informações sobre como criar um ambiente chroot, consulte "[Ch ```shell admin@ghe-host:~$ ghe-hook-env-create AlpineTestEnv /home/admin/alpine-3.3.tar.gz > Pre-receive hook environment 'AlpineTestEnv' (2) has been created. - ``` + ``` diff --git a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md index 39458b5454..a93c3ebc6c 100644 --- a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -70,19 +70,19 @@ Recomendamos consolidar os hooks em um único repositório. Se o repositório co ```shell $ sudo chmod +x SCRIPT_FILE.sh - ``` - Para usuários de Windows, certifique-se de que os scripts tenham estas permissões de execução: + ``` + Para usuários de Windows, certifique-se de que os scripts tenham estas permissões de execução: - ```shell - git update-index --chmod=+x SCRIPT_FILE.sh - ``` + ```shell + git update-index --chmod=+x SCRIPT_FILE.sh + ``` 2. Faça commit e push para o seu repositório designado de hooks pre-receive na instância do {% data variables.product.prodname_ghe_server %}. ```shell $ git commit -m "YOUR COMMIT MESSAGE" $ git push - ``` + ``` 3. [Crie o hook pre-receive](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) na instância do {% data variables.product.prodname_ghe_server %}. @@ -93,40 +93,40 @@ Antes de criar ou atualizar um script de hook pre-receive no appliance do {% dat 2. Crie um arquivo de nome `Dockerfile.dev` contendo: - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ``` + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` 3. Crie um script pre-receive de teste chamado `always_reject.sh`. Este exemplo de script rejeitará todos os pushes, o que é importante para bloquear um repositório: - ``` - #!/usr/bin/env bash + ``` + #!/usr/bin/env bash - echo "error: rejeitar todos os pushes" - exit 1 - ``` + echo "error: rejecting all pushes" + exit 1 + ``` 4. Certifique-se de que os scripts `always_reject.sh` têm permissões de execução: ```shell $ chmod +x always_reject.sh - ``` + ``` 5. No diretório contendo `Dockerfile.dev`, crie uma imagem: @@ -149,32 +149,32 @@ Antes de criar ou atualizar um script de hook pre-receive no appliance do {% dat ....saída truncada.... > Initialized empty Git repository in /home/git/test.git/ > Successfully built dd8610c24f82 - ``` + ``` 6. Execute um contêiner de dados que contenha uma chave SSH gerada: ```shell $ docker run --name data pre-receive.dev /bin/true - ``` + ``` 7. Copie o hook pre-receive de teste `always_reject.sh` no contêiner de dados: ```shell $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive - ``` + ``` 8. Execute um contêiner de aplicativo que execute `sshd` e o hook. Anote o ID do contêiner: ```shell $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58 - ``` + ``` 9. Copie a chave SSH gerada do contêiner de dados para a máquina local: ```shell $ docker cp data:/home/git/.ssh/id_ed25519 . - ``` + ``` 10. Modifique o remote de um repositório de teste e faça push para o repo `test.git` no contêiner Docker. Este exemplo usa o `git@github.com:octocat/Hello-World.git`, mas você pode usar o repositório de sua preferência. Este exemplo pressupõe que a sua máquina local (127.0.0.1) está vinculando a porta 52311, mas você pode usar outro endereço IP se o docker estiver sendo executado em uma máquina remota. @@ -193,9 +193,9 @@ Antes de criar ou atualizar um script de hook pre-receive no appliance do {% dat > To git@192.168.99.100:test.git > ! [remote rejected] master -> master (pre-receive hook declined) > error: failed to push some refs to 'git@192.168.99.100:test.git' - ``` + ``` - Observe que o push foi rejeitado após a execução do hook pre-receive e o eco da saída do script. + Observe que o push foi rejeitado após a execução do hook pre-receive e o eco da saída do script. ### Leia mais - "[Personalizar o Git - Um exemplo da aplicação da política do Git](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" no *site do Pro Git* diff --git a/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md index 6a536c064a..79552b39ee 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md @@ -30,11 +30,11 @@ versions: github-ae: '*' --- -### Configuring the default visibility of new repositories in your enterprise +### Configurar a visibilidade padrão de novos repositórios na sua empresa -Each time someone creates a new repository on your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. Para obter mais informações sobre a visibilidade de repositório, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". +Toda vez que alguém criar um novo repositório na sua empresa, essa pessoa deverá escolher uma visibilidade para o repositório. Ao configurar uma configuração padrão de visibilidade para a empresa, você escolhe qual visibilidade será selecionada por padrão. Para obter mais informações sobre a visibilidade de repositório, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". -Se um administrador do site impedir que os membros criem certos tipos de repositórios, os membros não serão capazes de criar esse tipo de repositório, mesmo se a configuração de visibilidade for padrão para esse tipo. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)." +If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)". {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} @@ -43,15 +43,15 @@ Se um administrador do site impedir que os membros criem certos tipos de reposit {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %} -1. Em "Default repository visibility" (Visibilidade padrão do repositório), clique no menu suspenso e selecione uma visibilidade padrão.![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) +1. Em "Default repository visibility" (Visibilidade padrão do repositório), clique no menu suspenso e selecione uma visibilidade padrão.![Menu suspenso para escolher a visibilidade padrão do repositório para a sua empresa](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) {% data reusables.enterprise_installation.image-urls-viewable-warning %} ### Definir uma política para alterar a visibilidade de um repositório -Se você impedir que os integrantes alterem a visibilidade do repositório, somente os administradores do site poderão tornar privados os repositórios públicos ou tornar públicos os repositórios privados. +When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository. -Se um administrador do site tiver restringido a criação do repositório somente aos proprietários da organização, os integrantes não poderão alterar a visibilidade do repositório. Além disso, se o administrador do site restringir a criação de repositórios apenas aos repositórios privados, os integrantes só conseguirão tornar privados os repositórios públicos. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)." +If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)". {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -75,6 +75,15 @@ Se um administrador do site tiver restringido a criação do repositório soment 6. Em "Repository creation" (Criação de repositórios), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de criação de repositórios](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png) {% endif %} +### Aplicar uma política de bifurcação de repositórios internos ou privados + +Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. Na guia **Repository policies** (Políticas de repositório), em Repository forking" (Bifurcação de repositórios), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +4. Em "Repository forking" (Bifurcação de repositórios), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de bifurcação de repositórios](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png) + ### Definir uma política de exclusão e transferência de repositório {% data reusables.enterprise-accounts.access-enterprise %} @@ -86,7 +95,7 @@ Se um administrador do site tiver restringido a criação do repositório soment ### Definir uma política para limites de push do Git -To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise. +Para manter o tamanho do repositório gerenciável e evitar problemas de desempenho, você pode configurar um limite de tamanho de arquivo para os repositórios na sua empresa. Por padrão, quando você impõe os limites de upload do repositório, as pessoas não podem adicionar ou atualizar arquivos maiores que 100 MB. @@ -106,7 +115,7 @@ Por padrão, quando você impõe os limites de upload do repositório, as pessoa {% endif %} {% data reusables.enterprise-accounts.options-tab %} 4. Em "Repository upload limit" (Limite de upload de repositório), use o menu suspenso e clique para definir o tamanho máximo do objeto. ![Menu suspenso com opções de tamanho máximo de objeto](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png) -5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select **Enforce on all repositories** ![Opção de limitar o tamanho máximo de objeto em todos os repositórios](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) +5. Opcionalmente, para aplicar um limite máximo de upload para todos os repositórios na sua empresa, selecione **Aplicar em todos os repositórios** ![Opção de limitar o tamanho máximo de objeto em todos os repositórios](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) ### Configurar o editor de conflitos de merge para pull requests entre repositórios @@ -123,7 +132,7 @@ Solicitar que os usuário resolvam conflitos de merge em seus respectivos comput ### Configurar pushes forçados -Cada repositório herda uma configuração padrão de push forçado das configurações da conta de usuário ou da organização à qual pertence. Likewise, each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, it will change for all repositories owned by any user or organization. +Cada repositório herda uma configuração padrão de push forçado das configurações da conta de usuário ou da organização à qual pertence. Da mesma forma, cada conta de organização e usuário herda uma configuração padrão de push forçado a partir da configuração de push forçado para a empresa. Se você alterar a configuração de push forçado para a empresa, ela mudará para todos os repositórios pertencentes a qualquer usuário ou organização. #### Bloquear todos as pushes forçados no seu dispositivo @@ -151,7 +160,7 @@ Cada repositório herda uma configuração padrão de push forçado das configur #### Bloquear pushes forçados em repositórios pertencentes a uma organização ou conta de usuário -Os repositórios herdam as configurações de push forçado da conta do usuário ou da organização à qual pertencem. User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise. +Os repositórios herdam as configurações de push forçado da conta do usuário ou da organização à qual pertencem. As contas de usuários e organizações herdam as configurações de push forçado a partir das configurações de push forçado para a empresa. Você pode substituir as configurações padrão herdadas definindo as configurações da conta de usuário ou da organização. @@ -164,17 +173,19 @@ Você pode substituir as configurações padrão herdadas definindo as configura 5. Em "Repository default settings" (Configurações padrão do repositório) na seção "Force pushes" (Pushes forçados), selecione - **Block** (Bloquear) para bloquear os pushes forçados em todos os branches. - **Block to the default branch** (Bloquear no branch padrão) para bloquear os pushes forçados apenas no branch padrão. ![Bloquear pushes forçados](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png) -6. Você também pode selecionar a opção **Enforce on all repositories** (Forçar em todos os repositórios), que substituirá as configurações específicas do repositório. Note that this will **not** override an enterprise-wide policy. ![Bloquear pushes forçados](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) +6. Você também pode selecionar a opção **Enforce on all repositories** (Forçar em todos os repositórios), que substituirá as configurações específicas do repositório. Observe que isso **não** substituirá uma política para toda a empresa. ![Bloquear pushes forçados](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) + +{% if enterpriseServerVersions contains currentVersion %} ### Configurar o acesso de leitura anônimo do Git {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %} -{% if enterpriseServerVersions contains currentVersion %}If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) on your enterprise, you {% else %}You {% endif %}can allow repository administrators to enable anonymous Git read access to public repositories. +{% if enterpriseServerVersions contains currentVersion %}Se você tiver o [habilitado o modo privado](/enterprise/admin/configuration/enabling-private-mode) na sua empresa, você {% else %}Você {% endif %}pode permitir que administradores de repositórios habilitem o acesso de leitura anônimo do Git aos repositórios públicos. -Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. Quando você ou um administrador de repositório habilitar essa configuração de acesso em um repositório, as operações não autenticadas do Git (e qualquer pessoa com acesso de rede ao {% data variables.product.product_name %}) terão acesso de leitura sem autenticação ao repositório. +Habilitar o acesso de leitura anônimo do Git permite que os usuários ignorem a autenticação para ferramentas personalizadas na sua empresa. Quando você ou um administrador de repositório habilitar essa configuração de acesso em um repositório, as operações não autenticadas do Git (e qualquer pessoa com acesso de rede ao {% data variables.product.product_name %}) terão acesso de leitura sem autenticação ao repositório. -If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on your enterprise by locking the repository's access settings. Após o bloqueio, somente um administrador de site poderá alterar a configuração do acesso de leitura anônimo do Git. +Se necessário, você pode impedir que os administradores do repositório alterem configurações anônimas de acesso do Git para repositórios, bloqueando as configurações de acesso do repositório. Após o bloqueio, somente um administrador de site poderá alterar a configuração do acesso de leitura anônimo do Git. {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %} @@ -191,9 +202,8 @@ If necessary, you can prevent repository administrators from changing anonymous {% data reusables.enterprise-accounts.options-tab %} 4. Em "Anonymous Git read access" (Acesso de leitura anônimo do Git), use o menu suspenso e clique em **Enabled** (Habilitado). ![Menu suspenso de acesso de leitura anônimo do Git com as opções "Enabled" (Habilitado) e "Disabled" (Desabilitado) ](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png) -3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your enterprise, select **Prevent repository admins from changing anonymous Git read access**. ![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your enterprise](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png) +3. Opcionalmente, para impedir que os administradores do repositório alterem as configurações de acesso de leitura anônimas do Git em todos os repositórios da sua empresa, selecione **Impedir que os administradores do repositório de alterarem o acesso de leitura anônimo do Git**. ![Marque a caixa de seleção para evitar que os administradores do repositório alterem as configurações de acesso de leitura anônimas do Git para todos os repositórios da sua empresa](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png) -{% if enterpriseServerVersions contains currentVersion %} #### Definir acesso de leitura anônimo do Git para um repositório específico {% data reusables.enterprise_site_admin_settings.access-settings %} @@ -204,6 +214,7 @@ If necessary, you can prevent repository administrators from changing anonymous 6. Em "Danger Zone" (Zona de perigo), ao lado de "Enable anonymous Git read access" (Habilitar acesso de leitura anônimo do Git), clique em **Enable** (Habilitar). ![Botão "Enabled" (Habilitado) na opção "Enable anonymous Git read access" (Habilitar acesso de leitura anônimo do Git) na zona de perigo das configurações de administração do site ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png) 7. Revise as alterações. Para confirmar, clique em **Yes, enable anonymous Git read access** (Sim, permitir acesso de leitura anônimo ao Git). ![Confirmar configuração de acesso de leitura anônimo do Git na janela pop-up](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png) 8. Para impedir que os administradores de repositório alterem a configuração nesse repositório, você também pode selecionar **Prevent repository admins from changing anonymous Git read access** (Impedir administradores de repositório de alterarem o acesso de leitura anônimo do Git). ![Marcar a caixa de seleção para impedir que administradores de repositório alterem as configurações de acesso de leitura anônimo do Git em todos os repositórios da instância](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png) + {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} diff --git a/translations/pt-BR/content/admin/user-management/activity-dashboard.md b/translations/pt-BR/content/admin/user-management/activity-dashboard.md index 120209106b..0c2d58fe31 100644 --- a/translations/pt-BR/content/admin/user-management/activity-dashboard.md +++ b/translations/pt-BR/content/admin/user-management/activity-dashboard.md @@ -1,6 +1,6 @@ --- title: Painel Atividade -intro: 'The Activity dashboard gives you an overview of all the activity in your enterprise.' +intro: 'O painel de atividades oferece uma visão geral de toda a atividade da sua empresa.' redirect_from: - /enterprise/admin/articles/activity-dashboard/ - /enterprise/admin/installation/activity-dashboard @@ -24,8 +24,8 @@ O painel Atividade gera gráficos semanais, mensais e anuais informando o númer ![Painel Atividade](/assets/images/enterprise/activity/activity-dashboard-yearly.png) {% if enterpriseServerVersions contains currentVersion %} -For more analytics based on data from -{% data variables.product.product_name %}, you can purchase {% data variables.product.prodname_insights %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/about-github-insights)." +Para mais análises com base em dados de +{% data variables.product.product_name %}, você pode comprar {% data variables.product.prodname_insights %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/about-github-insights)." {% endif %} ### Acessar o painel Atividade diff --git a/translations/pt-BR/content/admin/user-management/audit-logging.md b/translations/pt-BR/content/admin/user-management/audit-logging.md index 420adacf63..825e6d827a 100644 --- a/translations/pt-BR/content/admin/user-management/audit-logging.md +++ b/translations/pt-BR/content/admin/user-management/audit-logging.md @@ -1,6 +1,6 @@ --- title: Gerar logs de auditoria -intro: '{% data variables.product.product_name %} keeps logs of audited{% if enterpriseServerVersions contains currentVersion %} system,{% endif %} user, organization, and repository events. Os logs são úteis para fins de depuração e conformidade interna e externa.' +intro: '{% data variables.product.product_name %} mantém registros de{% if enterpriseServerVersions contains currentVersion %} sistema auditado,{% endif %} eventos de usuários, organização e repositórios. Os logs são úteis para fins de depuração e conformidade interna e externa.' redirect_from: - /enterprise/admin/articles/audit-logging/ - /enterprise/admin/installation/audit-logging @@ -10,22 +10,22 @@ versions: github-ae: '*' --- -For a full list, see "[Audited actions](/admin/user-management/audited-actions)." For more information on finding a particular action, see "[Searching the audit log](/admin/user-management/searching-the-audit-log)." +Para obter uma lista completa, consulte "[Ações auditadas](/admin/user-management/audited-actions)". Para obter mais informações sobre como encontrar uma ação em particular, consulte "[Pesquisar no log de auditoria](/admin/user-management/searching-the-audit-log)". ### Logs de push -Todas as operações de push no Git têm um log. For more information, see "[Viewing push logs](/admin/user-management/viewing-push-logs)." +Todas as operações de push no Git têm um log. Para obter mais informações, consulte "[Visualizar logs de push](/admin/user-management/viewing-push-logs)". {% if enterpriseServerVersions contains currentVersion %} ### Eventos do sistema Todos os eventos auditados do sistema, inclusive pushes e pulls, são registrados em logs no caminho `/var/log/github/audit.log`. Os logs passam por rotação a cada 24 horas e ficam guardados por sete dias. -O pacote de suporte inclui logs de sistema. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/admin/enterprise-support/providing-data-to-github-support)." +O pacote de suporte inclui logs de sistema. Para obter mais informações, consulte "[Fornecer dados para suporte de {% data variables.product.prodname_dotcom %}](/admin/enterprise-support/providing-data-to-github-support)." ### Pacotes de suporte -Todas as informações de auditoria são registradas no arquivo `audit.log`, no diretório `github-logs` de qualquer pacote de suporte. Se o encaminhamento de logs estiver habilitado, você poderá transmitir esses dados para um consumidor de fluxo de syslog externo, como o [Splunk](http://www.splunk.com/) ou o [Logstash](http://logstash.net/). Todas as entradas desse log usam a palavra-chave `github_audit` e podem ser filtradas por ela. For more information see "[Log forwarding](/admin/user-management/log-forwarding)." +Todas as informações de auditoria são registradas no arquivo `audit.log`, no diretório `github-logs` de qualquer pacote de suporte. Se o encaminhamento de logs estiver habilitado, você poderá transmitir esses dados para um consumidor de fluxo de syslog externo, como o [Splunk](http://www.splunk.com/) ou o [Logstash](http://logstash.net/). Todas as entradas desse log usam a palavra-chave `github_audit` e podem ser filtradas por ela. Para obter mais informações, consulte "[Encaminhamento de registro](/admin/user-management/log-forwarding)". Por exemplo, esta entrada mostra que um repositório foi criado. diff --git a/translations/pt-BR/content/admin/user-management/audited-actions.md b/translations/pt-BR/content/admin/user-management/audited-actions.md index 7381c7b38b..fb75a36cfc 100644 --- a/translations/pt-BR/content/admin/user-management/audited-actions.md +++ b/translations/pt-BR/content/admin/user-management/audited-actions.md @@ -12,18 +12,18 @@ versions: #### Autenticação -| Nome | Descrição | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------- | -| `oauth_access.create` | Um [token de acesso OAuth][] foi [gerado][generate token] para uma conta de usuário. | -| `oauth_access.destroy` | Um [token de acesso OAuth][] foi excluído de uma conta de usuário. | -| `oauth_application.destroy` | Um [aplicativo OAuth][] foi excluído de uma organização ou conta de usuário. | -| `oauth_application.reset_secret` | A chave secreta de um [aplicativo OAuth][] foi redefinida. | -| `oauth_application.transfer` | Um [aplicativo OAuth][] foi transferido de uma organização ou conta de usuário para outra. | -| `public_key.create` | Uma chave SSH foi [adicionada][add key] a uma conta de usuário ou uma [chave de implantação][] foi adicionada ao repositório. | -| `public_key.delete` | Uma chave SSH foi removida de uma conta de usuário ou uma [chave de implantação][] foi removida de um repositório. | -| `public_key.update` | A user account's SSH key or a repository's [deploy key][] was updated.{% if enterpriseServerVersions contains currentVersion %} -| `two_factor_authentication.enabled` | A [autenticação de dois fatores][2fa] foi habilitada para uma conta de usuário. | -| `two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.{% endif %} +| Nome | Descrição | +| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `oauth_access.create` | Um [token de acesso OAuth][] foi [gerado][generate token] para uma conta de usuário. | +| `oauth_access.destroy` | Um [token de acesso OAuth][] foi excluído de uma conta de usuário. | +| `oauth_application.destroy` | Um [aplicativo OAuth][] foi excluído de uma organização ou conta de usuário. | +| `oauth_application.reset_secret` | A chave secreta de um [aplicativo OAuth][] foi redefinida. | +| `oauth_application.transfer` | Um [aplicativo OAuth][] foi transferido de uma organização ou conta de usuário para outra. | +| `public_key.create` | Uma chave SSH foi [adicionada][add key] a uma conta de usuário ou uma [chave de implantação][] foi adicionada ao repositório. | +| `public_key.delete` | Uma chave SSH foi removida de uma conta de usuário ou uma [chave de implantação][] foi removida de um repositório. | +| `public_key.update` | A chave SSH de uma conta de usuário ou a [chave de implantação de um repositório][] foi atualizada.{% if enterpriseServerVersions contains currentVersion %} +| `two_factor_authentication.enabled` | A [autenticação de dois fatores][2fa] foi habilitada para uma conta de usuário. | +| `two_factor_authentication.disabled` | [A autenticação de dois fatores][2fa] foi desabilitada para uma conta de usuário.{% endif %} #### Hooks @@ -34,66 +34,66 @@ versions: | `hook.destroy` | Um hook foi excluído. | | `hook.events_changed` | Os eventos configurados de um hook foram alterados. | -#### Enterprise configuration settings +#### Configurações da empresa -| Nome | Descrição | -| -------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `business.update_member_repository_creation_permission` | A site admin restricts repository creation in organizations in the enterprise. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | -| `business.clear_members_can_create_repos` | A site admin clears a restriction on repository creation in organizations in the enterprise. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | -| `enterprise.config.lock_anonymous_git_access` | A site admin locks anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | -| `enterprise.config.unlock_anonymous_git_access` | A site admin unlocks anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | +| Nome | Descrição | +| -------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `business.update_member_repository_creation_permission` | Um administrador do site restringe a criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | +| `business.clear_members_can_create_repos` | Um administrador do site elimina uma restrição de criação de repositórios em organizações da empresa. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% if enterpriseServerVersions contains currentVersion %} +| `enterprise.config.lock_anonymous_git_access` | Um administrador do site bloqueia acessos de leitura anônimos do Git para impedir que os administradores do repositório alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | +| `enterprise.config.unlock_anonymous_git_access` | Um administrador do site desbloqueia acessos de leitura anônimos do Git para permitir que administradores alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."{% endif %} #### Problemas e pull requests -| Nome | Descrição | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `issue.update` | O texto de um problema (comentário inicial) foi alterado. | -| `issue_comment.update` | Um comentário em um problema (que não seja o inicial) foi alterado. | -| `pull_request_review_comment.delete` | Foi excluído um comentário em um pull request. | -| `issue.destroy` | Um problema foi excluído do repositório. For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)." | +| Nome | Descrição | +| ------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `issue.update` | O texto de um problema (comentário inicial) foi alterado. | +| `issue_comment.update` | Um comentário em um problema (que não seja o inicial) foi alterado. | +| `pull_request_review_comment.delete` | Foi excluído um comentário em um pull request. | +| `issue.destroy` | Um problema foi excluído do repositório. Para obter mais informações, consulte "[Excluir uma problema](/github/managing-your-work-on-github/deleting-an-issue)". | #### Organizações -| Nome | Descrição | -| ------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org.async_delete` | Um usuário iniciou um trabalho em segundo plano para excluir uma organização. | -| `org.delete` | An organization was deleted by a user-initiated background job.{% if currentVersion != "github-ae@latest" %} -| `org.transform` | A conta de usuário foi convertida em organização. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %} +| Nome | Descrição | +| ------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `org.async_delete` | Um usuário iniciou um trabalho em segundo plano para excluir uma organização. | +| `org.delete` | Uma organização foi excluída por um trabalho de segundo plano iniciado pelo usuário.{% if currentVersion != "github-ae@latest" %} +| `org.transform` | A conta de usuário foi convertida em organização. Para obter mais informações, consulte "[Converter um usuário em uma organização](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %} #### Branches protegidos -| Nome | Descrição | -| ------------------------------------------------------------------:| ------------------------------------------------------------------------------------- | -| `protected_branch.create` | A proteção do branch está habilitada em um branch. | -| `protected_branch.destroy` | A proteção do branch está desabilitada em um branch. | -| `protected_branch.update_admin_enforced` | A proteção do branch é exigida para os administradores do repositório. | -| `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review is updated on a branch. | -| `protected_branch.dismiss_stale_reviews` | A exigência de ignorar pull requests obsoletas é atualizada em um branch. | -| `protected_branch.update_signature_requirement_enforcement_level` | A exigência de assinatura de commit obrigatória é atualizada em um branch. | -| `protected_branch.update_pull_request_reviews_enforcement_level` | A exigência de revisões obrigatórias de pull request é atualizada em um branch. | -| `protected_branch.update_required_status_checks_enforcement_level` | A exigência de verificações de status obrigatórias é atualizada em um branch. | -| `protected_branch.rejected_ref_update` | Uma tentativa de atualização do branch é rejeitada. | -| `protected_branch.policy_override` | Um requisito de proteção do branch é sobrescrito por um administrador do repositório. | +| Nome | Descrição | +| ------------------------------------------------------------------:| --------------------------------------------------------------------------------------- | +| `protected_branch.create` | A proteção do branch está habilitada em um branch. | +| `protected_branch.destroy` | A proteção do branch está desabilitada em um branch. | +| `protected_branch.update_admin_enforced` | A proteção do branch é exigida para os administradores do repositório. | +| `protected_branch.update_require_code_owner_review` | A execução da revisão necessária do código do proprietário foi atualizada em um branch. | +| `protected_branch.dismiss_stale_reviews` | A exigência de ignorar pull requests obsoletas é atualizada em um branch. | +| `protected_branch.update_signature_requirement_enforcement_level` | A exigência de assinatura de commit obrigatória é atualizada em um branch. | +| `protected_branch.update_pull_request_reviews_enforcement_level` | A exigência de revisões obrigatórias de pull request é atualizada em um branch. | +| `protected_branch.update_required_status_checks_enforcement_level` | A exigência de verificações de status obrigatórias é atualizada em um branch. | +| `protected_branch.rejected_ref_update` | Uma tentativa de atualização do branch é rejeitada. | +| `protected_branch.policy_override` | Um requisito de proteção do branch é sobrescrito por um administrador do repositório. | #### Repositórios -| Nome | Descrição | -| ------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo.access` | Um repositório privado passou a ser público, ou um repositório público passou a ser privado. | -| `repo.archive` | Um repositório foi arquivado. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)." | -| `repo.add_member` | Um colaborador foi adicionado ao repositório. | -| `repo.config` | Um administrador do site bloqueou a opção de forçar pushes. Para obter mais informações, consulte [Bloquear pushes forçados em um repositório](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/). | -| `repo.create` | Um repositório foi criado. | -| `repo.destroy` | Um repositório foi excluído. | -| `repo.remove_member` | Um colaborador foi removido do repositório. | -| `repo.rename` | Um repositório foi renomeado. | -| `repo.transfer` | Um usuário aceitou uma solicitação para receber um repositório transferido. | -| `repo.transfer_start` | Um usuário enviou uma solicitação para transferir um repositório a outro usuário ou organização. | -| `repo.unarchive` | Um repositório teve o arquivamento cancelado. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)." | -| `repo.config.disable_anonymous_git_access` | O acesso de leitura anônimo do Git está desabilitado em um repositório público. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | -| `repo.config.enable_anonymous_git_access` | O acesso de leitura anônimo do Git está habilitado em um repositório público. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | -| `repo.config.lock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está bloqueado, impedindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | -| `repo.config.unlock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está desbloqueado, permitindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | +| Nome | Descrição | +| ------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.access` | The visibility of a repository changed to private{% if enterpriseServerVersions contains currentVersion %}, public,{% endif %} or internal. | +| `repo.archive` | Um repositório foi arquivado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | +| `repo.add_member` | Um colaborador foi adicionado ao repositório. | +| `repo.config` | Um administrador do site bloqueou a opção de forçar pushes. Para obter mais informações, consulte [Bloquear pushes forçados em um repositório](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/). | +| `repo.create` | Um repositório foi criado. | +| `repo.destroy` | Um repositório foi excluído. | +| `repo.remove_member` | Um colaborador foi removido do repositório. | +| `repo.rename` | Um repositório foi renomeado. | +| `repo.transfer` | Um usuário aceitou uma solicitação para receber um repositório transferido. | +| `repo.transfer_start` | Um usuário enviou uma solicitação para transferir um repositório a outro usuário ou organização. | +| `repo.unarchive` | Um repositório teve o arquivamento cancelado. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% if enterpriseServerVersions contains currentVersion %} +| `repo.config.disable_anonymous_git_access` | Anonymous Git read access is disabled for a repository. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | +| `repo.config.enable_anonymous_git_access` | Anonymous Git read access is enabled for a repository. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | +| `repo.config.lock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está bloqueado, impedindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | +| `repo.config.unlock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está desbloqueado, permitindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %} #### Ferramentas de administração do site @@ -115,30 +115,30 @@ versions: #### Usuários -| Nome | Descrição | -| ---------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | Um endereço de e-mail foi adicionado a uma conta de usuário. | -| `user.async_delete` | An asynchronous job was started to destroy a user account, eventually triggering `user.delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.change_password` | A user changed his or her password.{% endif %} -| `user.create` | Uma nova conta de usuário foi criada. | -| `user.delete` | Uma conta de usuário foi destruída por um trabalho assíncrono. | -| `user.demote` | Um administrador do site foi rebaixado a uma conta de usuário regular. | -| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.failed_login` | Um usuário tentou fazer login com nome de usuário, senha ou código de autenticação de dois fatores incorretos. | -| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} -| `user.login` | Um usuário fez login. | -| `user.promote` | Uma conta de usuário regular foi promovida a administrador do site. | -| `user.remove_email` | Um endereço de e-mail foi removido de uma conta de usuário. | -| `user.rename` | Um nome de usuário foi alterado. | -| `user.suspend` | A user account was suspended by a site admin.{% if enterpriseServerVersions contains currentVersion %} -| `user.two_factor_requested` | A user was prompted for a two-factor authentication code.{% endif %} -| `user.unsuspend` | Uma conta de usuário teve a suspensão cancelada por um administrador do site. | +| Nome | Descrição | +| ---------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user.add_email` | Um endereço de e-mail foi adicionado a uma conta de usuário. | +| `user.async_delete` | Um trabalho assíncrono foi iniciado para destruir uma conta de usuário, eventualmente acionando `user.delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.change_password` | Um usuário alterou sua senha.{% endif %} +| `user.create` | Uma nova conta de usuário foi criada. | +| `user.delete` | Uma conta de usuário foi destruída por um trabalho assíncrono. | +| `user.demote` | Um administrador do site foi rebaixado a uma conta de usuário regular. | +| `user.destroy` | Um usuário excluiu a sua conta, acionando `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | Um usuário tentou fazer login com nome de usuário, senha ou código de autenticação de dois fatores incorretos. | +| `user.forgot_password` | Um usuário solicitou uma redefinição de senha através da página de login.{% endif %} +| `user.login` | Um usuário fez login. | +| `user.promote` | Uma conta de usuário regular foi promovida a administrador do site. | +| `user.remove_email` | Um endereço de e-mail foi removido de uma conta de usuário. | +| `user.rename` | Um nome de usuário foi alterado. | +| `user.suspend` | Uma conta de usuário foi suspensa por um administrador do site.{% if enterpriseServerVersions contains currentVersion %} +| `user.two_factor_requested` | Um código de autenticação de dois fatores foi solicitado de um usuário.{% endif %} +| `user.unsuspend` | Uma conta de usuário teve a suspensão cancelada por um administrador do site. | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [chave de implantação]: /guides/managing-deploy-keys/#deploy-keys - [deploy key]: /guides/managing-deploy-keys/#deploy-keys + [chave de implantação de um repositório]: /guides/managing-deploy-keys/#deploy-keys [generate token]: /articles/creating-an-access-token-for-command-line-use - [token de acesso OAuth]: /v3/oauth/ + [token de acesso OAuth]: /developers/apps/authorizing-oauth-apps [aplicativo OAuth]: /guides/basics-of-authentication/#registering-your-app [2fa]: /articles/about-two-factor-authentication [2fa]: /articles/about-two-factor-authentication diff --git a/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md index 092d928cd9..e86bf5098f 100644 --- a/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Auditing users across your enterprise -intro: 'The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the past 90 days, including details such as who performed the action, what the action was, and when the action was performed.' +title: Auditar de usuários em toda a sua empresa +intro: 'O painel de log de auditoria mostra aos administradores do site as ações realizadas por todos os usuários e organizações de sua empresa nos últimos 90 dias incluindo detalhes como quem executou a ação, qual era a ação e quando a ação foi realizada.' redirect_from: - /enterprise/admin/guides/user-management/auditing-users-across-an-organization/ - /enterprise/admin/user-management/auditing-users-across-your-instance @@ -12,7 +12,7 @@ versions: ### Acessar o log de auditoria -The audit log dashboard gives you a visual display of audit data across your enterprise. +O painel de log de auditoria oferece uma exibição visual de dados de auditoria na sua empresa. ![Painel de log de auditoria da instância](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) @@ -22,9 +22,9 @@ The audit log dashboard gives you a visual display of audit data across your ent No mapa, você pode aplicar zoom e visão panorâmica para ver os eventos do mundo todo. Posicione o mouse sobre um país para ver a contagem de eventos ocorridos nele. -### Searching for events across your enterprise +### Pesquisar eventos na sua empresa -The audit log lists the following information about actions made within your enterprise: +O log de auditoria lista as seguintes informações sobre as ações feitas na sua empresa: * [O repositório](#search-based-on-the-repository) em que a ação ocorreu; * [O usuário](#search-based-on-the-user) que fez a ação; @@ -37,7 +37,7 @@ The audit log lists the following information about actions made within your ent **Notas:** -- Embora não seja possível usar texto para pesquisar entradas de auditoria, você pode criar consultas de pesquisa usando filtros diversificados. {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". +- Embora não seja possível usar texto para pesquisar entradas de auditoria, você pode criar consultas de pesquisa usando filtros diversificados. {% data variables.product.product_name %} é compatível com muitos operadores para fazer pesquisa em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". - Para pesquisar eventos com mais de 90 dias, use o qualificador `created`. {% endwarning %} @@ -66,13 +66,13 @@ Só é possível usar o nome de usuário do {% data variables.product.product_na O qualificador `org` limita as ações a uma organização específica. Por exemplo: -* `org:my-org` finds all events that occurred for the `my-org` organization. +* `org:my-org` encontrou todos os eventos que ocorreram na organização `minha-org`. * `org:my-org action:team` localiza todos os eventos de equipe que ocorreram na organização `my-org`; -* `-org:my-org` excludes all events that occurred for the `my-org` organization. +* `-org:my-org` exclui todos os eventos que ocorreram na organização `minha-org`. #### Pesquisar com base na ação -O qualificador `action` pesquisa eventos específicos, agrupados em categorias. For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)". +O qualificador `action` pesquisa eventos específicos, agrupados em categorias. Para informações sobre os eventos associados a essas categorias, consulte "[Ações auditadas](/admin/user-management/audited-actions)". | Categoria | Descrição | | --------- | --------------------------------------------------------------------------------- | diff --git a/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md b/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md index 4065fb06c5..e8bc534018 100644 --- a/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md +++ b/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md @@ -1,6 +1,6 @@ --- title: Práticas recomendadas de segurança de usuários -intro: '{% if enterpriseServerVersions contains currentVersion %}Outside of instance-level security measures (SSL, subdomain isolation, configuring a firewall) that a site administrator can implement, there {% else %}There {% endif %}are steps your users can take to help protect your enterprise.' +intro: '{% if enterpriseServerVersions contains currentVersion %}Medidas de segurança fora do nível da instância (SSL, isolamento de subdomínio, configuração de um firewall) que um administrador do site pode implementar, há {% else %} Há{% endif %}etapas que seus usuários podem seguir para ajudar a proteger a sua empresa.' redirect_from: - /enterprise/admin/user-management/best-practices-for-user-security versions: @@ -18,7 +18,7 @@ Para obter mais informações sobre como configurar a autenticação de dois fat ### Exigir um gerenciador de senhas -We strongly recommend requiring your users to install and use a password manager--such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/)--on any computer they use to connect to your enterprise. Essa medida garante senhas mais fortes e muito menos passíveis de violação ou roubo. +É altamente recomendável que os usuários instalem e usem um gerenciador de senhas, como, por exemplo, o [LastPass](https://lastpass.com/), [1Password](https://1password.com/) ou [Keeper](https://keepersecurity.com/)--em qualquer computador que usarem para conectar-se à sua empresa. Essa medida garante senhas mais fortes e muito menos passíveis de violação ou roubo. ### Restringir o acesso a equipes e repositórios diff --git a/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md index 6a12c83f44..ae30d72ca3 100644 --- a/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md @@ -19,7 +19,7 @@ versions: ### Sobre o {% data variables.large_files.product_name_long %} -{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} You can use {% data variables.large_files.product_name_long %} with a single repository, all of your personal or organization repositories, or with every repository in your enterprise. Before you can enable {% data variables.large_files.product_name_short %} for specific repositories or organizations, you need to enable {% data variables.large_files.product_name_short %} for your enterprise. +{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} Você pode usar {% data variables.large_files.product_name_long %} com um único repositório, todos os seus repositórios pessoais ou organizacionais, ou com cada repositório na sua empresa. Antes de habilitar {% data variables.large_files.product_name_short %} para repositórios ou organizações específicos, você deve habilitar {% data variables.large_files.product_name_short %} para a sua empresa. {% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} @@ -28,7 +28,7 @@ Para obter mais informações, consulte "[Sobre o {% data variables.large_files. {% data reusables.large_files.can-include-lfs-objects-archives %} -### Configuring {% data variables.large_files.product_name_long %} for your enterprise +### Configurar {% data variables.large_files.product_name_long %} para a sua empresa {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} @@ -65,7 +65,7 @@ Para obter mais informações, consulte "[Sobre o {% data variables.large_files. {% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} -1. Disable {% data variables.large_files.product_name_short %} on {% data variables.product.product_location %}. For more information, see "[Configuring {% data variables.large_files.product_name_long %} for your enterprise](#configuring-git-large-file-storage-for-your-enterprise)." +1. Desabilite {% data variables.large_files.product_name_short %} em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar {% data variables.large_files.product_name_long %} para a sua empresa](#configuring-git-large-file-storage-for-your-enterprise)". 2. Crie um arquivo de configuração do {% data variables.large_files.product_name_short %} que aponte para o servidor de terceiros. ```shell @@ -99,7 +99,7 @@ Para obter mais informações, consulte "[Sobre o {% data variables.large_files. ### Migrar para outro servidor do Git Large File Storage -Before migrating to a different {% data variables.large_files.product_name_long %} server, you must configure {% data variables.large_files.product_name_short %} to use a third party server. For more information, see "[Configuring {% data variables.large_files.product_name_long %} to use a third party server](#configuring-git-large-file-storage-to-use-a-third-party-server)." +Antes de migrar para outro servidor do {% data variables.large_files.product_name_long %}, configure o {% data variables.large_files.product_name_short %} para usar um servidor de terceiros. Para obter mais informações, consulte "[Configurar o {% data variables.large_files.product_name_long %} para utilizar um servidor de terceiros](#configuring-git-large-file-storage-to-use-a-third-party-server)". 1. Configure o repositório com outro remote. ```shell diff --git a/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md index 02652de2e2..9b315050d4 100644 --- a/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md +++ b/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md @@ -1,6 +1,6 @@ --- title: Configurar a visibilidade dos integrantes da organização -intro: You can set visibility for new organization members across your enterprise to public or private. Também é possível impedir que os integrantes alterem a visibilidade padrão. +intro: Você pode definir visibilidade para novos integrantes da organização em toda a sua empresa como pública ou privada. Também é possível impedir que os integrantes alterem a visibilidade padrão. redirect_from: - /enterprise/admin/user-management/configuring-visibility-for-organization-membership versions: @@ -21,4 +21,4 @@ Além disso, você pode impor a sua configuração padrão para todos os integra {% data reusables.enterprise-accounts.options-tab %} 3. No menu suspenso em "Default organization membership visibility" (Visibilidade padrão dos integrantes da organização), clique em **Private** (Privada) ou **Public** (Pública). ![Menu suspenso com a opção de configurar a visibilidade padrão dos integrantes da organização como pública ou privada](/assets/images/enterprise/site-admin-settings/default-organization-membership-visibility-drop-down-menu.png) 4. Para impedir que os integrantes alterem a visibilidade padrão, selecione **Enforce on organization members** (Aplicar aos integrantes da organização). ![Checkbox to enforce the default setting on all members](/assets/images/enterprise/site-admin-settings/enforce-default-org-membership-visibility-setting.png){% if enterpriseServerVersions contains currentVersion %} -5. Se você quiser aplicar a nova configuração de visibilidade a todos os integrantes, use o utilitário da linha de comando `ghe-org-membership-update`. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)."{% endif %} +5. Se você quiser aplicar a nova configuração de visibilidade a todos os integrantes, use o utilitário da linha de comando `ghe-org-membership-update`. Para obter mais informações, consulte "[Utilitários da linha de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)."{% endif %} diff --git a/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index 4500fd7e5f..c298b992da 100644 --- a/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -1,10 +1,10 @@ --- -title: Customizing user messages for your enterprise +title: Personalizar mensagens de usuário para sua empresa redirect_from: - /enterprise/admin/user-management/creating-a-custom-sign-in-message/ - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-on-your-instance -intro: 'You can create custom messages that users will see on the{% if enterpriseServerVersions contains currentVersion %} sign in and sign out pages{% else %} sign out page{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} or in an announcement banner at the top of every page{% endif %}.' +intro: 'Você pode criar mensagens personalizadas que os usuários verão nas{% if enterpriseServerVersions contains currentVersion %} páginas de login e logout{% else %} página de logout{% endif %}{% if currentVersion ver_gt "enterprise-server@2. 1" ou versão atual == "github-ae@latest" %} ou em um banner de anúncio na parte superior de cada página{% endif %}.' versions: enterprise-server: '*' github-ae: '*' @@ -51,7 +51,7 @@ Você pode definir um banner de anúncio global para ser exibido para todos os u {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -You can also set an announcement banner{% if enterpriseServerVersions contains currentVersion %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." +Você também pode definir um banner de anúncio{% if enterpriseServerVersions contains currentVersion %} no shell administrativo usando um utilitário de linha de comando ou{% endif %} usando a API. Para obter mais informações, consulte {% if enterpriseServerVersions contains currentVersion %}"[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" e {% endif %}"[Administração de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". {% else %} diff --git a/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md index 6feb06436c..4f71883b51 100644 --- a/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Disabling Git SSH access on your enterprise +title: Desabilitar o acesso ao SSH do Git na sua empresa redirect_from: - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account/ - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account/ @@ -13,7 +13,7 @@ redirect_from: - /enterprise/admin/installation/disabling-git-ssh-access-on-github-enterprise-server - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server -intro: 'You can prevent people from using Git over SSH for certain or all repositories on your enterprise.' +intro: 'Você pode impedir que as pessoas usem o Git através do SSH para certos ou todos os repositórios da sua empresa.' versions: enterprise-server: '*' github-ae: '*' @@ -41,7 +41,7 @@ versions: {% data reusables.enterprise_site_admin_settings.admin-tab %} 7. Em "Git SSH access" (Acesso por SSH do Git), use o menu suspenso e clique em **Disabled** (Desabilitado). Em seguida, selecione **Enforce on all repositories** (Aplicar a todos os repositórios). ![Menu suspenso de acesso por SSH do Git com a opção Desabilitado](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png) -### Disabling Git SSH access to all repositories in your enterprise +### Desabilitar acesso SSH do Git para todos os repositórios da sua empresa {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} diff --git a/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md index b01323c4c2..e4c432405d 100644 --- a/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md +++ b/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md @@ -27,7 +27,7 @@ versions: Para exportar os dados do repositório do {% data variables.product.prodname_dotcom_the_website %}, use a API de Migrações. -No momento, a API de Migrações está em período de exibição. Ou seja, os pontos de extremidade e os parâmetros podem mudar no futuro. Para acessar a API de Migrações, você deve informar um [tipo de mídia](/v3/media) personalizado no cabeçalho `Accept`: `application/vnd.github.wyandotte-preview+json`. Os exemplos abaixo incluem o tipo de mídia personalizado. +No momento, a API de Migrações está em período de exibição. Ou seja, os pontos de extremidade e os parâmetros podem mudar no futuro. Para acessar a API de Migrações, você deve informar um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Accept`: `application/vnd.github.wyandotte-preview+json`. Os exemplos abaixo incluem o tipo de mídia personalizado. ### Gerar arquivos de migração @@ -37,7 +37,7 @@ No momento, a API de Migrações está em período de exibição. Ou seja, os po 2. Comece a migração fazendo `POST` no ponto de extremidade da migração. Você precisará do seguinte: * Token de acesso para autenticação; - * Uma [lista de repositórios](/v3/repos/#list-organization-repositories) que você pretende migrar: + * Uma [lista de repositórios](/rest/reference/repos#list-organization-repositories) que você pretende migrar: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ diff --git a/translations/pt-BR/content/admin/user-management/index.md b/translations/pt-BR/content/admin/user-management/index.md index 598ef14528..196578e022 100644 --- a/translations/pt-BR/content/admin/user-management/index.md +++ b/translations/pt-BR/content/admin/user-management/index.md @@ -1,7 +1,7 @@ --- title: 'Gerenciar usuários, organizações e repositórios' shortTitle: 'Gerenciar usuários, organizações e repositórios' -intro: 'This guide describes authentication methods for users signing in to your enterprise, how to create organizations and teams for repository access and collaboration, and suggested best practices for user security.' +intro: 'Este guia descreve os métodos de autenticação para usuários que fazem login na sua empresa, além de mostrar como criar organizações e equipes para acesso e colaboração nos repositórios, bem como sugerir práticas recomendadas para a segurança do usuário.' redirect_from: - /enterprise/admin/categories/user-management/ - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration diff --git a/translations/pt-BR/content/admin/user-management/log-forwarding.md b/translations/pt-BR/content/admin/user-management/log-forwarding.md index b5ebba4ea9..1deccde915 100644 --- a/translations/pt-BR/content/admin/user-management/log-forwarding.md +++ b/translations/pt-BR/content/admin/user-management/log-forwarding.md @@ -1,6 +1,6 @@ --- title: Encaminhamento de logs -intro: '{% data variables.product.product_name %} uses `syslog-ng` to forward {% if enterpriseServerVersions contains currentVersion %}system{% elsif currentVersion == "github-ae@latest" %}Git{% endif %} and application logs to the server you specify.' +intro: '{% data variables.product.product_name %} usa `syslog-ng` para encaminhar {% if enterpriseServerVersions contains currentVersion %}sistema{% elsif currentVersion == "github-ae@latest" %}Git{% endif %} e logs de aplicativo para o servidor que você especificou.' redirect_from: - /enterprise/admin/articles/log-forwarding/ - /enterprise/admin/installation/log-forwarding @@ -25,18 +25,18 @@ Qualquer sistema de coleta de logs com suporte a fluxos de logs do estilo syslog {% elsif currentVersion == "github-ae@latest" %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Under {% octicon "gear" aria-label="The Settings gear" %} **Settings**, click **Log forwarding**. ![Log forwarding tab](/assets/images/enterprise/business-accounts/log-forwarding-tab.png) -1. Under "Log forwarding", select **Enable log forwarding**. ![Checkbox to enable log forwarding](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png) -1. Under "Server address", enter the address of the server you want to forward logs to. ![Server address field](/assets/images/enterprise/business-accounts/server-address-field.png) -1. Use the "Protocol" drop-down menu, and select a protocol. ![Protocol drop-down menu](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png) -1. Optionally, to enable TLS encrypted communication between syslog endpoints, select **Enable TLS**. ![Checkbox to enable TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png) -1. Under "Public certificate", paste your x509 certificate. ![Text box for public certificate](/assets/images/enterprise/business-accounts/public-certificate-text-box.png) -1. Clique em **Salvar**. ![Save button for log forwarding](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) +1. Em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**, clique em **Encaminhamento de registro**. ![Aba de encaminhamento de log](/assets/images/enterprise/business-accounts/log-forwarding-tab.png) +1. Em "Encaminhamento de registro", selecione **Habilitar o encaminhamento de registro**. ![Caixa de seleção para habilitar o encaminhamento de registro](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png) +1. Em "Endereço do servidor, digite o endereço do servidor para o qual você deseja encaminhar o registro. ![Campo endereço do servidor](/assets/images/enterprise/business-accounts/server-address-field.png) +1. Use o menu suspenso "Protocolo" e selecione um protocolo. ![Menu suspenso de protocolo](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png) +1. Opcionalmente, para habilitar comunicação encriptada TLS entre os pontos de extremidade do syslog, selecione **Habilitar TLS**. ![Caixa de seleção para habilitar TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png) +1. Em "Certificado público", cole o seu certificado x509. ![Caixa de texto para certificado público](/assets/images/enterprise/business-accounts/public-certificate-text-box.png) +1. Clique em **Salvar**. ![Botão Salvar para encaminhamento de registro](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) {% endif %} {% if enterpriseServerVersions contains currentVersion %} ### Solução de Problemas -If you run into issues with log forwarding, contact +Se você tiver problemas com o encaminhamento de registro, entre em contato com -{% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email. +{% data variables.contact.contact_ent_support %} e anexe o arquivo de saída de `http(s)://[hostname]/setup/diagnostics` ao seu e-mail. {% endif %} diff --git a/translations/pt-BR/content/admin/user-management/managing-dormant-users.md b/translations/pt-BR/content/admin/user-management/managing-dormant-users.md index 108ac5bfa2..499a075434 100644 --- a/translations/pt-BR/content/admin/user-management/managing-dormant-users.md +++ b/translations/pt-BR/content/admin/user-management/managing-dormant-users.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/articles/viewing-dormant-users/ - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant/ - /enterprise/admin/user-management/managing-dormant-users -intro: A user account is considered to be dormant if it has not been active for at least a month.{% if enterpriseServerVersions contains currentVersion %} You may choose to suspend dormant users to free up user licenses.{% endif %} +intro: Uma conta de usuário é considerada inativa se não estiver ativa por pelo menos um mês.{% if enterpriseServerVersions contains currentVersion %} Você pode optar por suspender usuários adormecidos para liberar licenças de usuário.{% endif %} versions: enterprise-server: '*' github-ae: '*' @@ -15,7 +15,7 @@ O termo "atividade" inclui, entre outros: - Fazer login no {% data variables.product.product_name %}; - Fazer comentários em problemas ou pull requests; - Criar, excluir, ver e marcar repositórios como favoritos; -- Pushing commits.{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Push de commits.{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} - Acessar recursos usando um token de acesso pessoal ou chave SSH.{% endif %} ### Exibir usuários inativos diff --git a/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md b/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md index d54dcc96fe..244a03011d 100644 --- a/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md +++ b/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md @@ -1,6 +1,6 @@ --- title: Gerenciar webhooks globais -intro: 'Site administrators can view, add, edit, and delete global webhooks to track events for the enterprise.' +intro: 'Administradores do site podem visualizar, adicionar, editar e excluir webhooks globais para acompanhar os eventos da empresa.' redirect_from: - /enterprise/admin/user-management/about-global-webhooks - /enterprise/admin/user-management/managing-global-webhooks @@ -11,7 +11,7 @@ versions: ### Sobre webhooks globais -You can use global webhooks to automatically monitor, respond to, or enforce rules for user and organization management for your enterprise. Por exemplo, você pode configurar os webhooks para serem executados sempre que: +Você pode usar webhooks globais para monitorar, responder ou aplicar regras automaticamente para o gerenciamento de usuários e organizações do seu negócio. Por exemplo, você pode configurar os webhooks para serem executados sempre que: - Uma conta de usuário for criada ou excluída; - Uma organização foi criada ou excluída - Um colaborador for adicionado ou removido de um repositório; diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise.md index 47023a9480..cf6fd593f2 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/categories/admin-bootcamp/ - /enterprise/admin/user-management/organizations-and-teams - /enterprise/admin/user-management/managing-organizations-in-your-enterprise -intro: 'As organizações são uma forma excelente de criar conjuntos distintos de usuários na empresa, como divisões ou grupos que trabalham em projetos semelhantes. Os repositórios públicos de uma organização ficam acessíveis para os usuários de outras organizações, enquanto os repositórios privados são inacessíveis para qualquer pessoa que não seja integrante da organização.' +intro: 'As organizações são uma forma excelente de criar conjuntos distintos de usuários na empresa, como divisões ou grupos que trabalham em projetos semelhantes. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to users in other organizations, while private repositories are inaccessible to anyone but members of the organization that are granted access.' mapTopic: true versions: enterprise-server: '*' diff --git a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise.md index bf3d4ff9be..04a6fbf4bd 100644 --- a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Gerenciar repositórios na sua empresa -intro: 'You can manage the settings available to repository administrators in your enterprise.' +intro: 'Você pode gerenciar as configurações disponíveis para administradores de repositórios na sua empresa.' redirect_from: - /enterprise/admin/user-management/repositories - /enterprise/admin/user-management/managing-repositories-in-your-enterprise diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise.md index 863fc30cdc..6311f01b8c 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Gerenciar usuários na sua empresa -intro: 'You can audit user activity and manage user settings.' +intro: 'Você pode controlar atividades do usuário e gerenciar configurações de usuário.' redirect_from: - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ - /enterprise/admin/user-management/basic-account-settings diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md index 9a5585ab3e..3422dbd951 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### Excluir repositórios de uma organização no {% data variables.product.prodname_dotcom_the_website %} -Depois de desbloquear os repositórios da organização do {% data variables.product.prodname_dotcom_the_website %}, você deve excluir todos os repositórios migrados anteriormente usando o [endpoint de exclusão de repositórios](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository). Você precisará do token de acesso para autenticação: +After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). Você precisará do token de acesso para autenticação: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md index 662db838e5..9912307bd3 100644 --- a/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md +++ b/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md @@ -1,6 +1,6 @@ --- title: Impor retenção legal a usuários ou organizações -intro: 'You can place a legal hold on a user or organization to ensure that repositories they own cannot be permanently removed from your enterprise.' +intro: 'Você pode colocar uma retenção legal em um usuário ou organização para garantir que os repositórios que ele possui não possam ser removidos permanentemente da sua empresa.' redirect_from: - /enterprise/admin/user-management/placing-a-legal-hold-on-a-user-or-organization versions: diff --git a/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md index 3452bbbb1e..e11d29c2d5 100644 --- a/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md +++ b/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md @@ -4,7 +4,7 @@ redirect_from: - /enterprise/admin/articles/preventing-users-from-creating-organizations/ - /enterprise/admin/hidden/preventing-users-from-creating-organizations/ - /enterprise/admin/user-management/preventing-users-from-creating-organizations -intro: 'You can prevent users from creating organizations in your enterprise.' +intro: 'Você pode impedir que usuários criem organizações na sua empresa.' versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md index 64cdb229c6..ac7ac87545 100644 --- a/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md +++ b/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md @@ -7,7 +7,7 @@ versions: enterprise-server: '*' --- -When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.product.product_location %}. Os administradores da organização podem exigir que os integrantes habilitem a autenticação de dois fatores. +Ao usar o LDAP ou autenticação integrada, a autenticação de dois fatores será compatível em {% data variables.product.product_location %}. Os administradores da organização podem exigir que os integrantes habilitem a autenticação de dois fatores. {% data reusables.enterprise_user_management.external_auth_disables_2fa %} diff --git a/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md b/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md index 882f6ad22d..4ec3603287 100644 --- a/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md +++ b/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md @@ -1,6 +1,6 @@ --- title: Pesquisar no log de auditoria -intro: 'Site administrators can search an extensive list of audited actions on the enterprise.' +intro: 'Os administradores do site podem pesquisar uma extensa lista de ações auditadas sobre a empresa.' redirect_from: - /enterprise/admin/articles/searching-the-audit-log/ - /enterprise/admin/installation/searching-the-audit-log @@ -19,7 +19,7 @@ Crie uma consulta de pesquisa com um ou mais pares chave-valor separados por ope | `actor_id` | ID da conta do usuário que iniciou a ação. | | `actor` | Nome da conta do usuário que iniciou a ação. | | `oauth_app_id` | ID do aplicativo OAuth associado à ação. | -| `Ação` | Name of the audited action | +| `Ação` | Nome da ação auditada | | `user_id` | ID do usuário afetado pela ação. | | `usuário` | Nome do usuário afetado pela ação. | | `repo_id` | ID do repositório afetado pela ação (se aplicável). | @@ -35,7 +35,7 @@ Por exemplo, para ver todas as ações que afetaram o repositório `octocat/Spoo `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]` -For a full list of actions, see "[Audited actions](/admin/user-management/audited-actions)." +Para obter uma lista completa de ações, consulte "[Ações auditadas](/admin/user-management/audited-actions)". ### Pesquisar no log de auditoria diff --git a/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md index 663c0ea5e7..c0848bd3cb 100644 --- a/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ Assim como na suspensão, o cancelamento da suspensão de um usuário ocorre na ``` ### Leia mais -- "[Suspender um usuário](/enterprise/{{ currentVersion }}/v3/enterprise-admin/users/#suspend-a-user)" +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/pt-BR/content/admin/user-management/viewing-push-logs.md b/translations/pt-BR/content/admin/user-management/viewing-push-logs.md index 6bdb33e07c..8328b8c545 100644 --- a/translations/pt-BR/content/admin/user-management/viewing-push-logs.md +++ b/translations/pt-BR/content/admin/user-management/viewing-push-logs.md @@ -1,6 +1,6 @@ --- title: Exibir logs de push -intro: 'Site administrators can view a list of Git push operations for any repository on the enterprise.' +intro: 'Os administradores do site podem ver uma lista de operações de push do Git para qualquer repositório na empresa.' redirect_from: - /enterprise/admin/articles/viewing-push-logs/ - /enterprise/admin/installation/viewing-push-logs diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md index 9b4acc8e1e..bb485e8c33 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -36,17 +36,23 @@ As alterações feitas nos arquivos via editor de texto e salvas no local també #### Criar um commit parcial -Se um arquivo tiver várias alterações e você quiser incluir somente *algumas* no commit, será possível criar um commit parcial. O restante das alterações ficará intacto, de modo que você possa fazer outras modificações e commits. Essa opção permite fazer commits separados mais relevantes, como manter alterações de quebra de linha em um commit separado das alterações de código. +Se um arquivo tiver várias alterações e você quiser incluir somente algumas no commit, será possível criar um commit parcial. O restante das alterações ficará intacto, de modo que você possa fazer outras modificações e commits. Essa opção permite fazer commits separados mais relevantes, como manter alterações de quebra de linha em um commit separado das alterações de código. -Durante a revisão do diff do arquivo, as linhas a serem incluídas no commit ficam destacadas em azul. Para excluir a alteração, clique na linha alterada para que o destaque azul desapareça. +{% note %} -![Linhas desmarcadas em um arquivo](/assets/images/help/desktop/partial-commit.png) +**Observação:** Dividir diff encontra-se atualmente na versão beta e está sujeito a alterações. -#### Descartar alterações +{% endnote %} -Você pode descartar todas as alterações sem commits em um arquivo ou intervalo de arquivos. Também é possível descartar todas as alterações em todos os arquivos desde a última confirmação. +1. Para escolher como as alterações são exibidas, no canto superior direito do arquivo alterado, use {% octicon "gear" aria-label="The Gear icon" %} para selecionar **Unificado** ou **Dividido**. ![Ícone de equipamento com diffs unificados e divididos](/assets/images/help/desktop/gear-diff-select.png) +2. Para excluir linhas alteradas do seu commit, clique em uma ou mais linhas alteradas para que o azul desapareça. As linhas ainda em destaque em azul serão incluídas no commit. ![Linhas desmarcadas em um arquivo](/assets/images/help/desktop/partial-commit.png) -{% mac %} +### 3. Descartar alterações +Se você tiver alterações não realizadas que não deseja manter, poderá descartar as alterações. Isso removerá as alterações dos arquivos no seu computador. Você pode descartar todas as alterações não realizadas em um ou mais arquivos ou pode descartar as linhas específicas que adicionou. + +As alterações descartadas são salvas em um arquivo datado na Lixeira. Você pode recuperar as alterações descartadas até que a lixeira seja esvaziada. + +#### Descartar alterações em um ou mais arquivos {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -54,30 +60,25 @@ Você pode descartar todas as alterações sem commits em um arquivo ou interval {% data reusables.desktop.confirm-discard-files %} ![Botão Discard Changes (Descartar alterações) na caixa de diálogo Confirmation (Confirmação)](/assets/images/help/desktop/discard-changes-confirm-mac.png) -{% tip %} +#### Descartar alterações em uma ou mais linhas +Você pode descartar uma ou mais linhas alteradas que não foram confirmadas. -**Dica:** as alterações descartadas são salvas em um arquivo com data em Trash (Lixeira), e será possível recuperá-las até que a lixeira seja esvaziada. +{% note %} -{% endtip %} +**Observação:** Descartar linhas únicas está desabilitado em um grupo de alterações que adiciona e remove linhas. -{% endmac %} +{% endnote %} -{% windows %} +Para descartar uma linha adicionada, na lista de linhas alteradas, clique com o botão direito na linha que você deseja descartar e selecione **Descartar linha adicionada**. -{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %} - ![Opção Discard Changes (Descartar alterações) no menu de contexto](/assets/images/help/desktop/discard-changes-win.png) -{% data reusables.desktop.confirm-discard-files %} - ![Botão Discard Changes (Descartar alterações) na caixa de diálogo Confirmation (Confirmação)](/assets/images/help/desktop/discard-changes-confirm-win.png) + ![Descartar uma única linha na caixa de diálogo de confirmação](/assets/images/help/desktop/discard-single-line.png) -{% tip %} +Para descartar um grupo de linhas alteradas, clique com o botão direito na barra vertical à direita dos números de linha para as linhas que você deseja descartar e, em seguida, selecione **Descartar linhas adicionadas**. -**Dica:** as alterações descartadas são salvas em um arquivo com data em Recycle Bin (Lixo), e será possível recuperá-las até a lixeira ser esvaziada. + ![Descartar um grupo de linhas adicionadas na caixa de diálogo de confirmação](/assets/images/help/desktop/discard-multiple-lines.png) -{% endtip %} -{% endwindows %} - -### 3. Mensagem de commit e envio das alterações +### 4. Mensagem de commit e envio das alterações Ao concluir as alterações que você decidiu fazer no commit, escreva a mensagem do commit e envie as alterações. Se o commit envolveu trabalho em colaboração, será possível atribuí-lo a mais de um autor. diff --git a/translations/pt-BR/content/developers/apps/about-apps.md b/translations/pt-BR/content/developers/apps/about-apps.md index c19cb3a47f..97855febdd 100644 --- a/translations/pt-BR/content/developers/apps/about-apps.md +++ b/translations/pt-BR/content/developers/apps/about-apps.md @@ -1,6 +1,6 @@ --- title: Sobre o aplicativo -intro: 'You can build integrations with the {% data variables.product.prodname_dotcom %} APIs to add flexibility and reduce friction in your own workflow.{% if currentVersion == "free-pro-team@latest" %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' +intro: 'Você pode construir integrações com as APIS de {% data variables.product.prodname_dotcom %} para adicionar flexibilidade e reduzir fricção no seu próprio fluxo de trabalho.{% if currentVersion == "free-pro-team@latest" %} Você também pode compartilhar integrações com outras pessoas em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' redirect_from: - /apps/building-integrations/setting-up-a-new-integration/ - /apps/building-integrations/ @@ -67,13 +67,13 @@ Tenha isso em mente ao criar {% data variables.product.prodname_oauth_app %}s: * Não crie um {% data variables.product.prodname_oauth_app %} para atuar como um aplicativo para sua equipe ou empresa. {% data variables.product.prodname_oauth_app %}s efetuam a autenticação como um único usuário. Portanto, se uma pessoa criar um {% data variables.product.prodname_oauth_app %} para a empresa usar e depois sair da empresa, ninguém mais terá acesso a ele.{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -Para obter mais informações sobre {% data variables.product.prodname_oauth_app %}, consulte "[Criar um {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" e "[Registrando seu aplicativo](/v3/guides/basics-of-authentication/#registering-your-app)". +For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." ### Tokens de acesso pessoal Um [token de acesso pessoal](/articles/creating-a-personal-access-token-for-the-command-line/) é uma string de caracteres que funciona da mesma forma que um [token do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/), cujas permissões você pode especificar por meio de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Um token de acesso pessoal também é semelhante a uma senha, mas você pode ter muitos delas e você pode revogar o acesso a cada uma a qualquer momento. -Como exemplo, você pode habilitar um token de acesso pessoal para escrever em seus repositórios. Em seguida, se você executar um comando cURL ou escrever um script que [cria um problema](/v3/issues/#create-an-issue) no seu repositório, você informaria o token de acesso pessoal para efetuar a autenticação. Você pode armazenar o token de acesso pessoal como uma variável de ambiente para evitar ter de digitá-lo toda vez que você usá-lo. +Como exemplo, você pode habilitar um token de acesso pessoal para escrever em seus repositórios. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. Você pode armazenar o token de acesso pessoal como uma variável de ambiente para evitar ter de digitá-lo toda vez que você usá-lo. Tenha em mente essas ideias ao usar os tokens de acesso pessoais: diff --git a/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md b/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md index 730041adee..1b3f209e7a 100644 --- a/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md @@ -118,13 +118,13 @@ Você deverá criar um novo JWT após o tempo expirar. ### Acessar os pontos finais da API como um {% data variables.product.prodname_github_app %} -Para obter uma lista dos pontos finais da API REST que você pode usar para obter informações de alto nível sobre um {% data variables.product.prodname_github_app %}, consulte "[aplicativos GitHub](/v3/apps/)". +Para obter uma lista dos pontos finais da API REST que você pode usar para obter informações de alto nível sobre um {% data variables.product.prodname_github_app %}, consulte "[aplicativos GitHub](/rest/reference/apps)". ### Autenticar como uma instalação Autenticar como uma instalação permite que você execute ações na API para essa instalação. Antes de autenticar como uma instalação, você deverá criar um token de acesso de instalação. Estes tokens de acesso de instalação são usados por {% data variables.product.prodname_github_app %}s para efetuar a autenticação. -Por padrão, os tokens de acesso de instalação são limitados em todos os repositórios que uma instalação pode acessar. É possível limitar o escopo do token de acesso de instalação a repositórios específicos usando o parâmetro `repository_ids`. Consulte [Criar um token de acesso de instalação para um ponto final de um aplicativo](/v3/apps/#create-an-installation-access-token-for-an-app) para obter mais informações. Os tokens de acesso de instalação têm as permissões configuradas pelo {% data variables.product.prodname_github_app %} e expiram após uma hora. +Por padrão, os tokens de acesso de instalação são limitados em todos os repositórios que uma instalação pode acessar. É possível limitar o escopo do token de acesso de instalação a repositórios específicos usando o parâmetro `repository_ids`. Consulte [Criar um token de acesso de instalação para um ponto final de um aplicativo](/rest/reference/apps#create-an-installation-access-token-for-an-app) para obter mais informações. Os tokens de acesso de instalação têm as permissões configuradas pelo {% data variables.product.prodname_github_app %} e expiram após uma hora. Para criar um token de acesso de instalação, inclua o JWT [gerado acima](#jwt-payload) no cabeçalho de autorização na solicitação de API: @@ -144,7 +144,7 @@ $ curl -i -X POST \ ``` {% endif %} -A resposta incluirá seu token de acesso de instalação, a data de validade, as permissões do token e os repositórios que o token pode acessar. Para obter mais informações sobre o formato de resposta, consulte [Criar um token de acesso de instalação para um ponto de final do](/v3/apps/#create-an-installation-access-token-for-an-app)aplicativo. +A resposta incluirá seu token de acesso de instalação, a data de validade, as permissões do token e os repositórios que o token pode acessar. Para obter mais informações sobre o formato de resposta, consulte [Criar um token de acesso de instalação para um ponto de final do](/rest/reference/apps#create-an-installation-access-token-for-an-app)aplicativo. Para efetuar a autenticação com um token de acesso de instalação, inclua-o no cabeçalho de autorização na solicitação de API: @@ -168,9 +168,9 @@ $ curl -i \ ### Acessar pontos finais da API como uma instalação -Para obter uma lista de pontos finais da API REST disponíveis para uso por {% data variables.product.prodname_github_app %}s usando um token de acesso de instalação, consulte "[Pontos finais disponíveis](/v3/apps/available-endpoints/)". +Para obter uma lista de pontos finais da API REST disponíveis para uso por {% data variables.product.prodname_github_app %}s usando um token de acesso de instalação, consulte "[Pontos finais disponíveis](/rest/overview/endpoints-available-for-github-apps)". -Para obter uma lista de pontos finais relacionados a instalações, consulte "[Instalações](/v3/apps/installations/)". +Para obter uma lista de pontos finais relacionados a instalações, consulte "[Instalações](/rest/reference/apps#installations)". ### Acesso Git baseado em HTTP por uma instalação diff --git a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md index bbd0d6f1e9..655d7d41b8 100644 --- a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md @@ -115,11 +115,13 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### Device flow +{% if currentVersion ver_lt "enterprise-server@3.1" %} {% note %} -**Note:** The device flow is in public beta and subject to change.{% if currentVersion == "free-pro-team@latest" %} To enable this beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} +**Note:** The device flow is in public beta and subject to change. {% endnote %} +{% endif %} The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. @@ -234,13 +236,13 @@ For more information, see the "[OAuth 2.0 Device Authorization Grant](https://to ### Non-Web application flow -Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/v3/auth#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. +Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} **Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with -two-factor authentication](/v3/auth/#working-with-two-factor-authentication) if +two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if you or your users have two-factor authentication enabled. {% endnote %} @@ -294,7 +296,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% tip %} -**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/v3/guides/discovering-resources-for-a-user/)." +**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." {% endtip %} diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md index aa8181b06d..aca9d29137 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -52,16 +52,16 @@ A pessoa que está criando o aplicativo será redirecionada para uma página do ##### Parâmetros do manifesto do aplicativo GitHub - | Nome | Tipo | Descrição | - | --------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | - | `name` | `string` | O nome do aplicativo GitHub. | - | `url` | `string` | **Obrigatório.** A página inicial do seu aplicativo GitHub. | - | `hook_attributes` | `objeto` | A configuração do webhook do aplicativo GitHub. | - | `redirect_url` | `string` | A URL completa para onde redirecionar depois que a pessoa instalar o aplicativo GitHub. | - | `descrição` | `string` | Uma descrição do aplicativo GitHub. | - | `público` | `boolean` | Defina como `verdadeiro` quando o seu aplicativo GitHub estiver disponível para o público ou `falso` quando for acessível somente pelo proprietário do aplicativo. | - | `default_events` | `array` | Lista de [eventos](/webhooks/event-payloads) assinada pelo aplicativo GitHub. | - | `default_permissions` | `objeto` | O conjunto de [permissões](/v3/apps/permissions/) exigido pelo aplicativo GitHub. O formato do objeto usa o nome de permissão para a chave (por exemplo, `problemas`) e o tipo de acesso para o valor (por exemplo, `gravar`). | + | Nome | Tipo | Descrição | + | --------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `string` | O nome do aplicativo GitHub. | + | `url` | `string` | **Obrigatório.** A página inicial do seu aplicativo GitHub. | + | `hook_attributes` | `objeto` | A configuração do webhook do aplicativo GitHub. | + | `redirect_url` | `string` | A URL completa para onde redirecionar depois que a pessoa instalar o aplicativo GitHub. | + | `descrição` | `string` | Uma descrição do aplicativo GitHub. | + | `público` | `boolean` | Defina como `verdadeiro` quando o seu aplicativo GitHub estiver disponível para o público ou `falso` quando for acessível somente pelo proprietário do aplicativo. | + | `default_events` | `array` | Lista de [eventos](/webhooks/event-payloads) assinada pelo aplicativo GitHub. | + | `default_permissions` | `objeto` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. O formato do objeto usa o nome de permissão para a chave (por exemplo, `problemas`) e o tipo de acesso para o valor (por exemplo, `gravar`). | O objeto `hook_attributes` tem a chave a seguir: @@ -153,13 +153,13 @@ Se você forneceu um parâmetro `estado`, você também verá esse parâmetro em #### 3. Você troca o código temporário para recuperar a configuração do aplicativo -Para concluir o handshake, enviar o código temporário `` em uma solicitação `POST` para [Criar um aplicativo GitHub a partir do ponto final](/v3/apps/#create-a-github-app-from-a-manifest) de um manifesto. A resposta incluirá o `id` (ID do aplicativo GitHub), `pem` (chave privada) e `webhook_secret`. O GitHub cria um segredo webhook para o aplicativo automaticamente. Você pode armazenar esses valores em variáveis de ambiente no servidor do aplicativo. Por exemplo, se o aplicativo usar [dotenv](https://github.com/bkeepers/dotenv) para armazenar variáveis de ambiente, você armazenará as variáveis no arquivo `.env` do seu aplicativo. +To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. A resposta incluirá o `id` (ID do aplicativo GitHub), `pem` (chave privada) e `webhook_secret`. O GitHub cria um segredo webhook para o aplicativo automaticamente. Você pode armazenar esses valores em variáveis de ambiente no servidor do aplicativo. Por exemplo, se o aplicativo usar [dotenv](https://github.com/bkeepers/dotenv) para armazenar variáveis de ambiente, você armazenará as variáveis no arquivo `.env` do seu aplicativo. Você deve concluir esta etapa do fluxo do manifesto do aplicativo GitHub em uma hora. {% note %} -**Observação:** Esse ponto final tem limite de taxa. Consulte [Limites de taxa](/v3/rate_limit/) para saber como obter seu status atual do limite de taxa. +**Observação:** Esse ponto final tem limite de taxa. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status. {% endnote %} @@ -170,7 +170,7 @@ Você deve concluir esta etapa do fluxo do manifesto do aplicativo GitHub em uma POST /app-manifests/:code/conversions -Para obter mais informações sobre a resposta do ponto final, consulte [Criar um aplicativo GitHub a partir de um manifesto](/v3/apps/#create-a-github-app-from-a-manifest). +For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest). Quando a etapa final do fluxo de manifesto for concluída, a pessoa que estiver criando o aplicativo a partir do fluxo será proprietária de um aplicativo GitHub registrado e poderá instalar em qualquer um dos seus repositórios pessoais. A pessoa pode optar por estender o aplicativo usando as APIs do GitHub, transferir a propriedade para outra pessoa ou excluí-lo a qualquer momento. @@ -191,4 +191,4 @@ Ao usar [dotenv](https://github.com/bkeepers/dotenv), o Probot cria um arquivo ` #### Hospedar seu aplicativo com Glitch -Você pode ver um [exemplo do aplicativo Probot](https://glitch.com/~auspicious-aardwolf) que usa o [Glitch](https://glitch.com/) para hospedar e compartilhar o aplicativo. O exemplo usa a [API de verificação](/v3/checks/) e seleciona as verificações e permissões necessárias dos eventos da API e no arquivo `app.yml`. Glitch é uma ferramenta que permite que você "mescle seus próprios aplicativos". Mesclar um aplicativo cria uma cópia do aplicativo que a Glitch hospeda e implementa. Consulte "[Sobre a Glitch](https://glitch.com/about/)" para aprender sobre como mesclar aplicativos Glitch. +Você pode ver um [exemplo do aplicativo Probot](https://glitch.com/~auspicious-aardwolf) que usa o [Glitch](https://glitch.com/) para hospedar e compartilhar o aplicativo. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch é uma ferramenta que permite que você "mescle seus próprios aplicativos". Mesclar um aplicativo cria uma cópia do aplicativo que a Glitch hospeda e implementa. Consulte "[Sobre a Glitch](https://glitch.com/about/)" para aprender sobre como mesclar aplicativos Glitch. diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md index 383af47903..1d7cdd6ec4 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -1,6 +1,6 @@ --- -title: Creating a GitHub App using URL parameters -intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.' +title: Criar um aplicativo GitHub usando parâmetros de URL +intro: 'Você pode pré-selecionar as configurações de um novo {% data variables.product.prodname_github_app %} usando URL [parâmetros de consulta](https://en.wikipedia.org/wiki/Query_string) para definir rapidamente a configuração do novo {% data variables.product.prodname_github_app %}.' redirect_from: - /apps/building-github-apps/creating-github-apps-using-url-parameters versions: @@ -10,112 +10,112 @@ versions: --- -### About {% data variables.product.prodname_github_app %} URL parameters +### Sobre parâmetros de URL do {% data variables.product.prodname_github_app %}. -You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account: -* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new` -* **Organization account:** `{% data variables.product.oauth_host_code %}/:org/settings/apps/new` +Você pode adicionar parâmetros de consulta a essas URLs para pré-selecionar a configuração de um {% data variables.product.prodname_github_app %} em uma conta pessoal ou de organização: +* **Conta de usuário:** `{% data variables.product.oauth_host_code %}/settings/apps/new` +* **Conta de organização:** ` {% data variables.product.oauth_host_code %}/:org/settings/apps/new` -The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app. +A pessoa que está criando o aplicativo pode editar os valores pré-selecionados a partir da página de registro do {% data variables.product.prodname_github_app %}, antes de enviar o aplicativo. Se você não incluir os parâmetros necessários na string de consulta da URL, como, por exemplo, o `nome`, a pessoa que criar o aplicativo deverá inserir um valor antes de enviar o aplicativo. -The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: +A URL a seguir cria um novo aplicativo pública denominado `octocat-github-app` com uma descrição pré-configurada e URL de chamada de retorno. Esta URL também seleciona permissões de leitura e gravação para `verificações`, inscreve-se nos eventos webhook de check_run` e check_suite` e seleciona a opção de solicitar autorização do usuário (OAuth) durante a instalação: ``` {% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite ``` -The complete list of available query parameters, permissions, and events is listed in the sections below. +Lista completa de parâmetros de consulta, permissões e eventos disponíveis encontra-se nas seções abaixo. -### {% data variables.product.prodname_github_app %} configuration parameters +### Parâmetros de configuração do {% data variables.product.prodname_github_app %} - Name | Type | Description ------|------|------------- -`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. -`description` | `string` | A description of the {% data variables.product.prodname_github_app %}. -`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage. -`callback_url` | `string` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. -`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. -`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation. -`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed. -`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app. -`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to. -`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details. -`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`. -`domain` | `string` | The URL of a content reference. -`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %} + | Nome | Tipo | Descrição | + | -------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `string` | O nome do {% data variables.product.prodname_github_app %}. Dê um nome claro e sucinto ao seu aplicativo. Seu aplicativo não pode ter o mesmo nome de um usuário existente no GitHub, a menos que seja o seu próprio nome de usuário ou da sua organização. Uma versão movida do nome do seu aplicativo será exibida na interface do usuário quando sua integração realizar uma ação. | + | `descrição` | `string` | Uma descrição do {% data variables.product.prodname_github_app %}. | + | `url` | `string` | A URL completa da página inicial do site do seu {% data variables.product.prodname_github_app %}. | + | `callback_url` | `string` | A URL completa para onde redirecionar após alguém autorizar uma instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. | + | `request_oauth_on_install` | `boolean` | Se seu aplicativo autoriza usuários a usar o fluxo OAuth, você poderá definir essa opção como `verdadeiro` para permitir que pessoas autorizem o aplicativo ao instalá-lo, economizando um passo. Se você selecionar esta opção, `setup_url` irá tornar-se indisponível e os usuários serão redirecionados para sua `callback_url` após instalar o aplicativo. | + | `setup_url` | `string` | A URL completa para redirecionamento após alguém instalar o {% data variables.product.prodname_github_app %}, se o aplicativo precisar de configuração adicional após a instalação. | + | `setup_on_update` | `boolean` | Defina como `verdadeiro` para redirecionar as pessoas para a URL de configuração quando as instalações forem atualizadas, por exemplo, após os repositórios serem adicionados ou removidos. | + | `público` | `boolean` | Defina `verdadeiro` quando seu {% data variables.product.prodname_github_app %} estiver disponível para o público ou como `falso` quando só for acessível pelo proprietário do aplicativo. | + | `webhook_url` | `string` | A URL completa para a qual você deseja enviar as cargas do evento de webhook. | + | `webhook_secret` | `string` | Você pode especificar um segredo para proteger seus webhooks. Consulte "[Protegendo seus webhooks](/webhooks/securing/)" para obter mais detalhes. | + | `eventos` | `array de strigns` | Eventos webhook. Alguns eventos de webhook exigem permissões de `leitura` ou `gravação` para um recurso antes de poder selecionar o evento ao registrar um novo {% data variables.product.prodname_github_app %}, . Consulte a seção "[{% data variables.product.prodname_github_app %} eventos de webhook](#github-app-webhook-events)" para eventos disponíveis e suas permissões necessárias. Você pode selecionar vários eventos em uma string de consulta. Por exemplo, `eventos[]=public&eventos[]=label`. | + | `domínio` | `string` | A URL de uma referência de conteúdo. | + | `single_file_name` | `string` | Esta é uma permissão de escopo limitado que permite que o aplicativo acesse um único arquivo em qualquer repositório. Quando você define a permissão `single_file` para `read` ou `write`, este campo fornece o caminho para o único arquivo que o {% data variables.product.prodname_github_app %} gerenciará. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Se você precisar gerenciar vários arquivos, veja `single_file_paths` abaixo. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + | `single_file_paths` | `array de strigns` | Isso permite que o aplicativo acesse até dez arquivos especificados em um repositório. Quando você define a permissão `single_file` para `read` ou `write`, este array pode armazenar os caminhos de até dez arquivos que seu {% data variables.product.prodname_github_app %} gerenciará. Todos esses arquivos recebem a mesma permissão definida por `single_file`, e não têm permissões individuais separadas. Quando dois ou mais arquivos estão configurados, a API retorna `multiple_single_files=true`, caso contrário retorna `multiple_single_files=false`.{% endif %} -### {% data variables.product.prodname_github_app %} permissions +### Permissões do {% data variables.product.prodname_github_app %} -You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission. +Você pode selecionar permissões em uma string de consultas usando o nome da permissão na tabela a seguir como o nome do parâmetro de consulta e o tipo de permissão como valor da consulta. Por exemplo, para selecionar permissões de `Leitura & gravação` na interface de usuário para `conteúdo`, sua string de consulta incluiria `&contents=write`. Para selecionar as permissões `Somente leitura` na interface de usuário para `bloquear`, sua string de consulta incluiria `&blocking=read`. Para selecionar `sem acesso` na interface do usuário para `verificações`, sua string de consulta não incluiria a permissão `verificações`. -Permission | Description ----------- | ----------- -[`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -[`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/v3/users/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -[`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/v3/checks/). Can be one of: `none`, `read`, or `write`. -`content_references` | Grants access to the "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. -[`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. -[`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -[`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/v3/users/emails/). Can be one of: `none`, `read`, or `write`.{% endif %} -[`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/v3/users/followers/). Can be one of: `none`, `read`, or `write`. -[`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/v3/users/gpg_keys/). Can be one of: `none`, `read`, or `write`. -[`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/v3/issues/). Can be one of: `none`, `read`, or `write`. -[`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/v3/users/keys/). Can be one of: `none`, `read`, or `write`. -[`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -[`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. -[`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/v3/orgs/#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} -[`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`. -`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/v3/orgs/#get-an-organization)" endpoint. Can be one of: `none` or `read`. -[`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} -[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/v3/orgs/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -[`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`. -`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/v3/users/#get-a-user)" endpoint. Can be one of: `none` or `read`. -[`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. -[`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/v3/repos/hooks/). Can be one of: `none`, `read`, or `write`. -[`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`. -[`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/v3/repos/contents/). Can be one of: `none`, `read`, or `write`. -[`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/v3/activity/starring/). Can be one of: `none`, `read`, or `write`. -[`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/v3/repos/statuses/). Can be one of: `none`, `read`, or `write`. -[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/v3/teams/discussions/) and the [Team Discussion Comments API](/v3/teams/discussion_comments/). Can be one of: `none`, `read`, or `write`. -`vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. -`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. +| Permissão | Descrição | +| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`administração`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Concede acesso a vários pontos finais para administração de organização e repositório. Pode ser: `nenhum`, `leitura`ou `gravação`.{% if currentVersion == "free-pro-team@latest" %} +| [`bloqueio`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Concede acesso à [API de usuários de bloqueio](/rest/reference/users#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} +| [`Verificações`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Concede acesso à [API de verificação](/rest/reference/checks). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| `content_references` | Concede acesso ao ponto final "[Criar um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Conteúdo`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Concede acesso a vários pontos finais que permitem modificar o conteúdo do repositório. Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Implantações`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Concede acesso à [API de implementação](/rest/reference/repos#deployments). Pode ser um das: `none`, `read`, ou `write`{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Concede acesso à [API de e-mails](/rest/reference/users#emails). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} +| [`seguidores`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Concede acesso à [API de seguidores](/rest/reference/users#followers). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Concede acesso à [API de chaves de GPG](/rest/reference/users#gpg-keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Problemas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Concede acesso à [API de problemas](/rest/reference/issues). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`chaves`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Concede acesso à [API de chaves públicas](/rest/reference/users#keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Concede acesso para gerenciar os membros de uma organização. Pode ser: `nenhum`, `leitura`ou `gravação`.{% if currentVersion == "free-pro-team@latest" %} +| [`metadados`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Concede acesso a pontos finais somente leitura que não vazam dados confidenciais. Pode ser `leitura ` ou `nenhum`. O padrão é `leitura`, ao definir qualquer permissão, ou `nenhum` quando você não especificar nenhuma permissão para o {% data variables.product.prodname_github_app %}. | +| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Concede acesso ao ponto final "[Atualizar uma organização](/rest/reference/orgs#update-an-organization)" ponto final e Pa [API de restrições de interação da organização](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Concede acesso à [API de webhooks da organização](/rest/reference/orgs#webhooks/). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| `organization_plan` | Concede acesso para obter informações sobre o plano de uma organização usando o ponto final "[Obter uma organização](/rest/reference/orgs#get-an-organization)". Pode ser: `nenhum` ou `leitura`. | +| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leitura`, `gravação` ou `admin`. {% if currentVersion == "free-pro-team@latest" %} +| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Concede acesso à [API de usuários de bloqueio da organização](/rest/reference/orgs#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} +| [`Páginas`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Concede acesso à [API de páginas](/rest/reference/repos#pages). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| `plano` | Concede acesso para obter informações sobre o plano de um usuário do GitHub que usa o ponto final "[Obter um usuário](/rest/reference/users#get-a-user)". Pode ser: `nenhum` ou `leitura`. | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Concede acesso a vários pontos finais do pull request. Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Concede acesso à [API de webhooks do repositório](/rest/reference/repos#hooks). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leutra`, `gravação` ou `administrador`. | +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Concede acesso à [API de conteúdo](/rest/reference/repos#contents). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`estrela`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Concede acesso à [API estrelada](/rest/reference/activity#starring). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Status`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Concede acesso à [API de status](/rest/reference/repos#statuses). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Concede acesso à [API de discussões de equipe](/rest/reference/teams#discussions) e à [API de comentários de discussão de equipe](/rest/reference/teams#discussion-comments). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| `vulnerability_alerts` | Concede acesso a alertas de segurança para dependências vulneráveis em um repositório. Consulte "[Sobre alertas de segurança para dependências vulneráveis](/articles/about-security-alerts-for-vulnerable-dependencies)" para saber mais. Pode ser: `nenhum` ou `leitura`. | +| `inspecionando` | Concede acesso à lista e alterações de repositórios que um usuário assinou. Pode ser: `nenhum`, `leitura` ou `gravação`. | -### {% data variables.product.prodname_github_app %} webhook events +### Eventos webhook do {% data variables.product.prodname_github_app %} -Webhook event name | Required permission | Description ------------------- | ------------------- | ----------- -[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %} -[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %} -[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %} -[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %} -[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %} -[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %} -[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %} -[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %} -[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %} -[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %} -[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %} -[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %} -[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %} -[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} -[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} -[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} -[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} -[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} -[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %} -[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %} -[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} -[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} -[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %} -[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} -[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} -[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} -[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %} -[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %} -[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} -[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %} -[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %} -[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} -[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} -[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %} +| Nome do evento webhook | Permissão necessária | Descrição | +| -------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | +| [`check_run`](/webhooks/event-payloads/#check_run) | `Verificações` | {% data reusables.webhooks.check_run_short_desc %} +| [`check_suite`](/webhooks/event-payloads/#check_suite) | `Verificações` | {% data reusables.webhooks.check_suite_short_desc %} +| [`commit_comment`](/webhooks/event-payloads/#commit_comment) | `Conteúdo` | {% data reusables.webhooks.commit_comment_short_desc %} +| [`content_reference`](/webhooks/event-payloads/#content_reference) | `content_references` | {% data reusables.webhooks.content_reference_short_desc %} +| [`create`](/webhooks/event-payloads/#create) | `Conteúdo` | {% data reusables.webhooks.create_short_desc %} +| [`delete`](/webhooks/event-payloads/#delete) | `Conteúdo` | {% data reusables.webhooks.delete_short_desc %} +| [`implantação`](/webhooks/event-payloads/#deployment) | `Implantações` | {% data reusables.webhooks.deployment_short_desc %} +| [`implantação_status`](/webhooks/event-payloads/#deployment_status) | `Implantações` | {% data reusables.webhooks.deployment_status_short_desc %} +| [`bifurcação`](/webhooks/event-payloads/#fork) | `Conteúdo` | {% data reusables.webhooks.fork_short_desc %} +| [`gollum`](/webhooks/event-payloads/#gollum) | `Conteúdo` | {% data reusables.webhooks.gollum_short_desc %} +| [`Problemas`](/webhooks/event-payloads/#issues) | `Problemas` | {% data reusables.webhooks.issues_short_desc %} +| [`issue_comment`](/webhooks/event-payloads/#issue_comment) | `Problemas` | {% data reusables.webhooks.issue_comment_short_desc %} +| [`etiqueta`](/webhooks/event-payloads/#label) | `metadados` | {% data reusables.webhooks.label_short_desc %} +| [`integrante`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} +| [`filiação`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} +| [`marco`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} +| [`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} +| [`organização`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} +| [`page_build`](/webhooks/event-payloads/#page_build) | `Páginas` | {% data reusables.webhooks.page_build_short_desc %} +| [`project`](/webhooks/event-payloads/#project) | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_short_desc %} +| [`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} +| [`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} +| [`público`](/webhooks/event-payloads/#public) | `metadados` | {% data reusables.webhooks.public_short_desc %} +| [`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} +| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} +| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} +| [`push`](/webhooks/event-payloads/#push) | `Conteúdo` | {% data reusables.webhooks.push_short_desc %} +| [`versão`](/webhooks/event-payloads/#release) | `Conteúdo` | {% data reusables.webhooks.release_short_desc %} +| [`repositório`](/webhooks/event-payloads/#repository) | `metadados` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} +| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `Conteúdo` | Permite aos integradores que usam o GitHub Actions acionar eventos personalizados.{% endif %} +| [`status`](/webhooks/event-payloads/#status) | `Status` | {% data reusables.webhooks.status_short_desc %} +| [`equipe`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} +| [`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} +| [`inspecionar`](/webhooks/event-payloads/#watch) | `metadados` | {% data reusables.webhooks.watch_short_desc %} diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app.md b/translations/pt-BR/content/developers/apps/creating-a-github-app.md index f8c8325f68..7e245d2b0d 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app.md @@ -32,11 +32,11 @@ versions: 6. Opcionalmente, em "Descrição", digite uma descrição do aplicativo que os usuários irão ver. ![Campo para uma descrição do seu aplicativo GitHub](/assets/images/github-apps/github_apps_description.png) 7. Em "URL da página inicial", digite a URL completa do site do seu aplicativo. ![Campo para a URL da página inicial do seu aplicativo GitHub](/assets/images/github-apps/github_apps_homepage_url.png) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -8. In "Callback URL", type the full URL to redirect to after a user authorizes the installation. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. +8. Em "URL de retorno de chamada", digite a URL completa para redirecionar após um usuário autorizar a instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. - You can use **Add callback URL** to provide additional callback URLs, up to a maximum of 10. + Você pode usar **Adicionar URL de retorno de chamada** para fornecer URLs de retorno de chamadas adicionais até o limite máximo de 10. - ![Button for 'Add callback URL' and field for callback URL](/assets/images/github-apps/github_apps_callback_url_multiple.png) + ![Botão para 'Adicionar URL de retorno de chamada' e campo para URL de retorno de chamada](/assets/images/github-apps/github_apps_callback_url_multiple.png) {% else %} 8. Em "URL de chamada de retorno de autorização do usuário", digite a URL completa para redirecionamento após um usuário autorizar uma instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. ![Campo para a URL de chamada de retorno de autorização do usuário do seu aplicativo GitHub](/assets/images/github-apps/github_apps_user_authorization.png) diff --git a/translations/pt-BR/content/developers/apps/creating-an-oauth-app.md b/translations/pt-BR/content/developers/apps/creating-an-oauth-app.md index 2f86c3061c..cb758383bc 100644 --- a/translations/pt-BR/content/developers/apps/creating-an-oauth-app.md +++ b/translations/pt-BR/content/developers/apps/creating-an-oauth-app.md @@ -42,7 +42,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} - **Note:** OAuth Apps cannot have multiple callback URLs, unlike {% data variables.product.prodname_github_apps %}. + **Observação:** Os aplicativos OAuth não podem ter várias URLs de retorno de chamada, diferente de {% data variables.product.prodname_github_apps %}. {% endnote %} {% endif %} diff --git a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 7fb85f4ed2..59086b56d2 100644 --- a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introdução -Este guia irá apresentá-lo aos [aplicativos Github](/apps/) e à [API de verificação](/v3/checks/), que você usará para criar um servidor de integração contínua (CI) que executa testes. +This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. A CI é uma prática de software que exige o commit do código em um repositório compartilhado. Fazer commits de códigos com frequência detecta erros com mais antecedência e reduz a quantidade de código necessária para depuração quando os desenvolvedores chegam à origem de um erro. As atualizações frequentes de código também facilitam o merge de alterações dos integrantes de uma equipe de desenvolvimento de software. Assim, os desenvolvedores podem se dedicar mais à gravação de códigos e se preocupar menos com erros de depuração ou conflitos de merge. 🙌 @@ -22,15 +22,15 @@ Um código de host do servidor de CI que executa testes de CI, como, por exemplo #### Visão geral da API de verificação -A [API de verificação](/v3/checks/) permite que você configure testes de CI executados automaticamente em cada commit de código em um repositório. A API de verificação relata informações detalhadas sobre cada verificação no GitHub na aba **Verificações** do pull request. Com a API de Verificações, você pode criar anotações com detalhes adicionais para linhas específicas de código. As anotações são visíveis na aba **Verificações**. Ao criar uma anotação para um arquivo que faz parte do pull request, as anotações também são exibidas na aba **Arquivos alterados**. +The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. A API de verificação relata informações detalhadas sobre cada verificação no GitHub na aba **Verificações** do pull request. Com a API de Verificações, você pode criar anotações com detalhes adicionais para linhas específicas de código. As anotações são visíveis na aba **Verificações**. Ao criar uma anotação para um arquivo que faz parte do pull request, as anotações também são exibidas na aba **Arquivos alterados**. -Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Usar esses status com [branches protegidos](/v3/repos/branches/) pode impedir que as pessoas mesclem de pull requests prematuramente. Consulte "[Habilitando as verificações de status necessárias](/articles/enabling-required-status-checks/)" para mais detalhes. +Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. Consulte "[Habilitando as verificações de status necessárias](/articles/enabling-required-status-checks/)" para mais detalhes. -A API de verificações envia o evento do webhook [`check_suite` webhook](/webhooks/event-payloads/#check_suite) para todos os aplicativos GitHub instalados em um repositório sempre que um novo código for enviado para o repositório. Para receber todas as ações do evento de verificações da API, o aplicativo deverá ter a permissão de `checks:write`. O GitHub cria automaticamente eventos `check_suite` para novos códigos de commits em um repositório usando o fluxo-padrão, embora [Atualizar preferências do repositório para o conjunto de verificações](/v3/checks/suites/#update-repository-preferences-for-check-suites) esteja disponível se desejar. Veja como funciona o fluxo-padrão: +A API de verificações envia o evento do webhook [`check_suite` webhook](/webhooks/event-payloads/#check_suite) para todos os aplicativos GitHub instalados em um repositório sempre que um novo código for enviado para o repositório. Para receber todas as ações do evento de verificações da API, o aplicativo deverá ter a permissão de `checks:write`. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Veja como funciona o fluxo-padrão: 1. Sempre que alguém fizer push do código para o repositório, o GitHub envia o evento `check_suite` com uma ação de `necessária` a todos os aplicativos GitHub instalados no repositório com a permissão `checks:write`. Este evento permite que os aplicativos saibam que o código foi enviado e que o GitHub criou um novo conjunto de verificações automaticamente. -1. Quando seu aplicativo recebe este evento, ele pode [adicionar uma verificação executa](/v3/checks/runs/#create-a-check-run) para esse conjunto. -1. Seus execuções de verificação podem incluir [anotações](/v3/checks/runs/#annotations-object), que são exibidas em linhas específicas de código. +1. When your app receives this event, it can [add check runs](/rest/reference/checks#create-a-check-run) to that suite. +1. Your check runs can include [annotations](/rest/reference/checks#annotations-object) that are displayed on specific lines of code. **Neste guia, você aprenderá:** @@ -49,7 +49,7 @@ Para ter uma ideia do que seu servidor de CI da API de verificações fará quan ### Pré-requisitos -Antes de começar, é possível que você deseje familiarizar-se com os [aplicativos Github](/apps/), [Webhooks](/webhooks) e a [API de verificação](/v3/checks/), caso você ainda não esteja familiarizado. Você encontrará mais APIs na [documentação da API REST](/v3/). A API de Verificações também está disponível para uso no [GraphQL](/v4/), mas este início rápido foca no REST. Consulte o GraphQL [Conjunto de verificações](/v4/object/checksuite/) e os objetos de [execução de verificação](/v4/object/checkrun/) objetos para obter mais informações. +Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). A API de Verificações também está disponível para uso no [GraphQL](/graphql), mas este início rápido foca no REST. Consulte o GraphQL [Conjunto de verificações](/graphql/reference/objects#checksuite) e os objetos de [execução de verificação](/graphql/reference/objects#checkrun) objetos para obter mais informações. Você usará a [linguagem de programação Ruby](https://www.ruby-lang.org/en/), o serviço de entrega de da carga do webhook [Smee](https://smee.io/), a [biblioteca do Ruby Octokit.rb](http://octokit.github.io/octokit.rb/) para a API REST do GitHub e a [estrutura web Sinatra](http://sinatrarb.com/) para criar seu aplicativo do servidor de verificações de CI da API. @@ -140,7 +140,7 @@ Você irá adicionar este novo método como um [Auxiliar do Sinatra](https://git def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -159,7 +159,7 @@ end def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -175,7 +175,7 @@ end ``` {% endif %} -Este código chama o ponto final "[Criar uma execução de verificação](/v3/checks/runs/#create-a-check-run)" que usa o método genérico [HTTP `POST`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). Este método tem dois parâmetros: a URL do ponto final e os parâmetros de entrada do método. +This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). Este método tem dois parâmetros: a URL do ponto final e os parâmetros de entrada do método. Para criar uma execução de verificação, são necessários apenas dois parâmetros de entrada: `nome` e `head_sha`. Vamos usar o [Rubocop](https://rubocop.readthedocs.io/en/latest/) para implementar o teste CI mais adiante início rápido. Por esse motivo, o nome "Octo Rubocop" é usado aqui, mas você pode escolher qualquer nome que desejar para a execução da verificação. @@ -240,7 +240,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -276,7 +276,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -305,11 +305,11 @@ end ``` {% endif %} -O código acima chama o ponto de extremidade da API "[Atualizar uma execução de verificação](/v3/checks/runs/#update-a-check-run)" usando o método genérico [`patch` HTTP](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) para atualizar a execução de verificação que você já criou. +The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. Veja o que este código está fazendo. Primeiro, ele atualiza o status de verificação de execução para `in_progress` e define o tempo do `started_at` para o tempo atual. Na [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) deste início rápido, você irá adicionar um código que inicia um teste de CI real em `***** EXECUTAR UM TEST DE CI *****`. Por enquanto, você sairá da seção como um espaço reservado, para que o código que o segue apenas simule que o processo de CI seja bem-sucedido e todos os testes sejam aprovados. Finalmente, o código atualiza o status da execução de verificação novamente para `concluído`. -Você observará na documentação "[Atualizar uma execução de verificação](/v3/checks/runs/#update-a-check-run)" que, quando você fornece um status de `concluído`, os parâmetros `conclusão` e `completed_at` são necessários. A conclusão `` resume o resultado de uma verificação de resultado e pode ser `sucesso`, `falha`, `neutro`, `cancelado`, `timed_out` ou `action_required`. Você irá definir a conclusão como `sucesso`, o tempo `completed_at` como a hora atual e o status como `concluído`. +You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. A conclusão `` resume o resultado de uma verificação de resultado e pode ser `sucesso`, `falha`, `neutro`, `cancelado`, `timed_out` ou `action_required`. Você irá definir a conclusão como `sucesso`, o tempo `completed_at` como a hora atual e o status como `concluído`. Você também pode fornecer mais informações sobre o que a sua verificação está fazendo, mas você poderá fazer isso na próxima seção. Vamos testar este código de novo executando `template_server.rb` novamente: @@ -435,7 +435,7 @@ O código acima obtém o nome completo do repositório e o SHA principal do comm ### Etapa 2.3. Executar o RuboCop -Ótimo! Você está clonando o repositório e criando execuções de verificação usando seu servidor de CI. Agora você irá entrar nas informações principais do [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) e das [anotações da API de verificação](/v3/checks/runs/#create-a-check-run). +Ótimo! Você está clonando o repositório e criando execuções de verificação usando seu servidor de CI. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). O código a seguir executa RuboCop e salva os erros do código de estilo no formato JSON. Adicione este código abaixo da chamada para `clone_repository` que você adicionou na [etapa anterior](#step-22-cloning-the-repository) e acima do código que atualiza a execução de verificação para concluir. @@ -523,11 +523,11 @@ Você deve ver os erros de linting na saída de depuração, embora não sejam i A variável `@output` contém os resultados do JSON analisados do relatório do RuboCop. Conforme mostrado acima, os resultados contêm uma seção `resumo` que seu código pode usar para determinar rapidamente se existem erros. O código a seguir definirá a conclusão de execução de verificação para o `sucesso` quando não houver erros relatados. O RuboCop relata erros para cada arquivo no array dos `arquivos`. Portanto, se houver erros, você deverá extrair alguns dados do objeto arquivo. -A API de verificação permite que você crie anotações para linhas específicas do código. Ao criar ou atualizar uma execução de verificação, você pode adicionar anotações. Neste início rápido, você está [atualizando a execução de verificações](/v3/checks/runs/#update-a-check-run) com anotações. +A API de verificação permite que você crie anotações para linhas específicas do código. Ao criar ou atualizar uma execução de verificação, você pode adicionar anotações. In this quickstart you are [updating the check run](/rest/reference/checks#update-a-check-run) with annotations. -A API de verificação limita o número de anotações a um máximo de 50 por solicitação de API. Para criar mais de 50 anotações, você deve fazer várias solicitações para o ponto de extremidade [Atualizar uma execução de verificação](/v3/checks/runs/#update-a-check-run). Por exemplo, para criar 105 anotações você deve chamar o ponto de extremidade[Atualizar uma execução de verificação](/v3/checks/runs/#update-a-check-run) três vezes. Cada uma das duas primeiras solicitações teria 50 anotações e a terceira solicitação incluiria as cinco anotações restantes. Cada vez que você atualizar a execução de verificação, as anotações são anexadas à lista de anotações que já existem para a execução de verificação. +A API de verificação limita o número de anotações a um máximo de 50 por solicitação de API. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint three times. Cada uma das duas primeiras solicitações teria 50 anotações e a terceira solicitação incluiria as cinco anotações restantes. Cada vez que você atualizar a execução de verificação, as anotações são anexadas à lista de anotações que já existem para a execução de verificação. -Uma execução de verificação espera anotações como um array de objetos. Cada objeto de anotação deve incluir o `caminho`, `start_line`,, `end_line`, `annotation_level` e `mensagem`. O RuboCop também fornece `start_column` e `end_column`. Portanto, você pode incluir esses parâmetros opcionais na anotação. As anotações são compatíveis apenas com `start_column` e `end_column` na mesma linha. Para obter mais informações, consulte a documentação de referência do [`objeto` anotações](/v3/checks/runs/#annotations-object-1). +Uma execução de verificação espera anotações como um array de objetos. Cada objeto de anotação deve incluir o `caminho`, `start_line`,, `end_line`, `annotation_level` e `mensagem`. O RuboCop também fornece `start_column` e `end_column`. Portanto, você pode incluir esses parâmetros opcionais na anotação. As anotações são compatíveis apenas com `start_column` e `end_column` na mesma linha. See the [`annotations` object](/rest/reference/checks#annotations-object-1) reference documentation for details. Você irá extrair as informações necessárias do RuboCop para criar cada anotação. Acrescente o seguinte código ao código que você adicionou na [seção anterior](#step-23-running-rubocop): @@ -536,7 +536,7 @@ annotations = [] # You can create a maximum of 50 annotations per request to the Checks # API. To add more than 50 annotations, use the "Update a check run" API # endpoint. Este código de exemplo limita o número de anotações a 50. -# See /v3/checks/runs/#update-a-check-run +# See /rest/reference/checks#update-a-check-run # for details. max_annotations = 50 @@ -836,7 +836,7 @@ Aqui estão alguns problemas comuns e algumas soluções sugeridas. Se você tiv * **P:** Meu aplicativo não está enviando código para o GitHub. Eu não vejo as correções que o RuboCop faz automaticamente! - **A:** Make sure you have **Read & write** permissions for "Repository contents," and that you are cloning the repository with your installation token. Consulte [Etapa 2.2. Clonar o repositório](#step-22-cloning-the-repository) para obter detalhes. + **R:** Certifique-se de que você tem permissões de **Leitura & gravação** para "conteúdo de repositório" e que você está clonando o repositório com seu token de instalação. Consulte [Etapa 2.2. Clonar o repositório](#step-22-cloning-the-repository) para obter detalhes. * **P:** Vejo um erro no saída de depuração de `template_server.rb` relacionado à clonagem do meu repositório. @@ -869,4 +869,4 @@ Depois ler este guia, você aprendeu os princípios básicos para usar a API de Aqui estão algumas ideias do que você pode fazer a seguir: * Atualmente, o botão "Corrija isso" sempre é exibido. Atualize o código que você escreveu para exibir o botão "Corrija isso" somente quando o RuboCop encontrar erros. -* Se preferir que RuboCop não comprometa os arquivos diretamente para o branch principal, você pode atualizar o código para [criar um pull request](/v3/pulls/#create-a-pull-request) com um novo branch baseado no branch principal. +* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch. diff --git a/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 04870a98c9..82e88f73a2 100644 --- a/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -90,10 +90,10 @@ Ao contrário dos aplicativos OAuth, os aplicativos GitHub têm permissões dire ### Acesso Git -| Aplicativos do GitHub | Aplicativos OAuth | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Os aplicativos GitHub solicitam permissão de conteúdo de repositórios e usam seu token de instalação para efetuar a autenticação por meio do [Git baseado em HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Os aplicativos OAuth solicitam escopo `write:public_key` e [Criar uma chave de implantação](/v3/repos/keys/#create-a-deploy-key) por meio da API. Você pode usar essa chave para realizar comandos do Git. | -| O token é usado como senha HTTP. | O token é usado como nome de usuário HTTP. | +| Aplicativos do GitHub | Aplicativos OAuth | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Os aplicativos GitHub solicitam permissão de conteúdo de repositórios e usam seu token de instalação para efetuar a autenticação por meio do [Git baseado em HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Os aplicativos OAuth solicitam escopo `write:public_key` e [Criar uma chave de implantação](/rest/reference/repos#create-a-deploy-key) por meio da API. Você pode usar essa chave para realizar comandos do Git. | +| O token é usado como senha HTTP. | O token é usado como nome de usuário HTTP. | ### Máquina vs. contas de bot diff --git a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 60a7f9be39..b2ab669b84 100644 --- a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Identifying and authorizing users for GitHub Apps +title: Identificar e autorizar usuários para aplicativos GitHub intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}' redirect_from: - /early-access/integrations/user-identification-authorization/ @@ -14,80 +14,80 @@ versions: {% data reusables.pre-release-program.expiring-user-access-tokens-beta %} -When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build. +Quando o seu aplicativo GitHub age em nome de um usuário, ele realiza solicitações de usuário para servidor. Essas solicitações devem ser autorizadas com o token de acesso de um usuário. As solicitações de usuário para servidor incluem a solicitação de dados para um usuário, como determinar quais repositórios devem ser exibidos para um determinado usuário. Essas solicitações também incluem ações acionadas por um usuário, como executar uma criação. {% data reusables.apps.expiring_user_authorization_tokens %} -### Identifying users on your site +### Identificando usuários no seu site -To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow). +Para autorizar usuários para aplicativos-padrão executados no navegador, use o [fluxo de aplicativo web](#web-application-flow). {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628). +Para autorizar usuários para aplicativos sem acesso direto ao navegador, como ferramentas de CLI ou gerentes de credenciais do Git, use o [fluxo de dispositivos](#device-flow). O fluxo de dispositivo usa o OAuth 2.0 [Concessão de autorização do dispositivo](https://tools.ietf.org/html/rfc8628). {% endif %} -### Web application flow +### Fluxo do aplicativo web -Using the web application flow, the process to identify users on your site is: +Ao usar o fluxo de aplicativo web, o processo para identificar usuários no seu site é: -1. Users are redirected to request their GitHub identity -2. Users are redirected back to your site by GitHub -3. Your GitHub App accesses the API with the user's access token +1. Os usuários são redirecionados para solicitar sua identidade do GitHub +2. Os usuários são redirecionados de volta para o seu site pelo GitHub +3. Seu aplicativo GitHub acessa a API com o token de acesso do usuário -If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)." +Se você selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo, a etapa 1 será concluída durante a instalação do aplicativo. Para obter mais informações, consulte "[Autorizando usuários durante a instalação](/apps/installing-github-apps/#authorizing-users-during-installation)". -#### 1. Request a user's GitHub identity +#### 1. Solicitar identidade do GitHub de um usuário GET {% data variables.product.oauth_host_code %}/login/oauth/authorize -When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. +Quando seu aplicativo GitHub especifica um parâmetro do `login`, ele solicita aos usuários com uma conta específica que podem usar para iniciar sessão e autorizar seu aplicativo. -##### Parameters +##### Parâmetros -Name | Type | Description ------|------|------------ -`client_id` | `string` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. -`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters. -`state` | `string` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data. -`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. +| Nome | Tipo | Descrição | +| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **Obrigatório.** O ID do cliente para o seu aplicativo GitHub. Você pode encontrá-lo em suas [configurações do aplicativo GitHub](https://github.com/settings/apps) quando você selecionar seu aplicativo. | +| `redirect_uri` | `string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Este deve ser um match exato para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} um dos URLs fornecidos como uma **URL de Callback**{% else %} a URL fornecida no campo de **URL de callback de autorização do usuário**{% endif %} ao configurar o aplicativo GitHub e não pode conter nenhum parâmetro adicional. | +| `estado` | `string` | Isso deve conter uma string aleatória para proteger contra ataques falsificados e pode conter quaisquer outros dados arbitrários. | +| `login` | `string` | Sugere uma conta específica para iniciar a sessão e autorizar o aplicativo. | {% note %} -**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user. +**Observação:** Você não precisa fornecer escopos na sua solicitação de autorização. Ao contrário do OAuth tradicional, o token de autorização é limitado às permissões associadas ao seu aplicativo GitHub e às do usuário. {% endnote %} -#### 2. Users are redirected back to your site by GitHub +#### 2. Os usuários são redirecionados de volta para o seu site pelo GitHub -If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted. +Se o usuário aceitar o seu pedido, O GitHub irá fazer o redirecionamento para seu site com um `código temporário` em um parâmetro de código, bem como o estado que você forneceu na etapa anterior em um parâmetro do `estado`. Se os estados não corresponderem, o pedido foi criado por terceiros e o processo deve ser abortado. {% note %} -**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation. +**Observação:** Se você selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo, o GitHub irá retornar um `código temporário` que você precisará trocar por um token de acesso. O parâmetro `estado` não é retornado quando o GitHub inicia o fluxo OAuth durante a instalação do aplicativo. {% endnote %} -Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." +Troque este `código` por um token de acesso. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} Quando os tokens com expiração estão habilitados, o token de acesso expira em 8 horas e o token de atualização expira em 6 meses. Toda vez que você atualizar o token, você receberá um novo token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/developers/apps/refreshing-user-to-server-access-tokens)." -Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} +Os tokens de usuário expirados atualmente fazem parte da expiração do token beta de usuário para servidor e estão sujeitos a alterações. Para optar por participar do recurso beta do token de usuário para servidor com expiração, consulte "[Ativar os recursos beta para aplicativos](/developers/apps/activating-beta-features-for-apps)".{% endif %} POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -##### Parameters +##### Parâmetros -Name | Type | Description ------|------|------------ -`client_id` | `string` | **Required.** The client ID for your GitHub App. -`client_secret` | `string` | **Required.** The client secret for your GitHub App. -`code` | `string` | **Required.** The code you received as a response to Step 1. -`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters. -`state` | `string` | The unguessable random string you provided in Step 1. +| Nome | Tipo | Descrição | +| --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **Obrigatório.** O ID do cliente para o seu aplicativo GitHub. | +| `client_secret` | `string` | **Obrigatório.** O segredo do cliente do seu aplicativo GitHub. | +| `código` | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1. | +| `redirect_uri` | `string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Este deve ser um match exato para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} um dos URLs fornecidos como uma **URL de Callback**{% else %} a URL fornecida no campo de **URL de callback de autorização do usuário**{% endif %} ao configurar o aplicativo GitHub e não pode conter nenhum parâmetro adicional. | +| `estado` | `string` | A string aleatória inexplicável que você forneceu na etapa 1. | -##### Response +##### Resposta {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`, and `refresh_token_expires_in` are only returned when you enable the beta for expiring user-to-server access tokens. +Por padrão, a resposta assume o seguinte formato. Os parâmetros de resposta `expires_in`, `atualizar_token`, e `refresh_token_expires_in` são apenas retornados quando você ativar o beta para expirar os tokens de acesso do usuário para servidor. ``` { @@ -101,831 +101,833 @@ By default, the response takes the following form. The response parameters `expi ``` {% else %} -By default, the response takes the following form: +Por padrão, a resposta assume o seguinte formato: access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer {% endif %} -#### 3. Your GitHub App accesses the API with the user's access token +#### 3. Seu aplicativo GitHub acessa a API com o token de acesso do usuário -The user's access token allows the GitHub App to make requests to the API on behalf of a user. +O token de acesso do usuário permite que o aplicativo GitHub faça solicitações para a API em nome de um usuário. - Authorization: token OAUTH-TOKEN + Autorização: token OUTH-TOKEN GET {% data variables.product.api_url_code %}/user -For example, in curl you can set the Authorization header like this: +Por exemplo, no cURL você pode definir o cabeçalho de autorização da seguinte forma: ```shell curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user ``` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -### Device flow +### Fluxo de dispositivo +{% if currentVersion ver_lt "enterprise-server@3.1" %} {% note %} -**Note:** The device flow is in public beta and subject to change.{% if currentVersion == "free-pro-team@latest" %} To enable this beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} +**Nota:** O fluxo do dispositivo está na versão beta pública e sujeito a alterações. {% endnote %} +{% endif %} -The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. +O fluxo de dispositivos permite que você autorize usuários para um aplicativo sem cabeçalho, como uma ferramenta de CLI ou um gerenciador de credenciais do Git. -For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)". +Para obter mais informações sobre autorização de usuários que usam o fluxo do dispositivo, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". {% endif %} -### Check which installation's resources a user can access +### Verifique quais recursos de instalação um usuário pode acessar {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% data reusables.pre-release-program.machine-man-preview %} {% data reusables.pre-release-program.api-preview-warning %} {% endif %} -Once you have an OAuth token for a user, you can check which installations that user can access. +Depois de ter um token OAuth para um usuário, você pode verificar quais instalações o usuário poderá acessar. Authorization: token OAUTH-TOKEN GET /user/installations -You can also check which repositories are accessible to a user for an installation. +Você também pode verificar quais repositórios são acessíveis a um usuário para uma instalação. Authorization: token OAUTH-TOKEN GET /user/installations/:installation_id/repositories -More details can be found in: [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token). +Você pode encontrar mais informações em: [Listar instalações de aplicativos acessíveis para o token de acesso do usuário](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) e [Listar repositórios acessíveis para o token de acesso do usuário](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). -### Handling a revoked GitHub App authorization +### Tratar uma autorização revogada do aplicativo GitHub -If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %} +Se um usuário revogar sua autorização de um aplicativo GitHub, o aplicativo receberá o webhook [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) por padrão. Os aplicativos GitHub não podem cancelar a assinatura deste evento. {% data reusables.webhooks.authorization_event %} -### User-level permissions +### Permissões no nível do usuário -You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/v3/apps/permissions/), which are granted at the time of installation on an organization or user account. +Você pode adicionar permissões de nível de usuário ao seu aplicativo GitHub para acessar os recursos de usuários, como, por exemplo, e-mails de usuários, concedidos por usuários individuais como parte do fluxo de autorização do usuário [](#identifying-users-on-your-site). As permissões de nível de usuário diferem das [permissões do repositório do nível de organização](/rest/reference/permissions-required-for-github-apps), que são concedidas no momento da instalação em uma conta de organização ou usuário. -You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." +Você pode selecionar permissões de nível de usuário nas configurações do seu aplicativo GitHub na seção **Permissões de usuário** na página **Permissões & webhooks**. Para obter mais informações sobre como selecionar permissões, consulte "[Editando permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)". -When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions. +Quando um usuário instala seu aplicativo em sua conta, o prompt de instalação listará as permissões de nível de usuário que seu aplicativo solicita e explicará que o aplicativo pode pedir essas permissões a usuários individuais. -Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests. +Como as permissões de nível de usuário são concedidas em uma base de usuário individual, você poderá adicioná-las ao aplicativo existente sem pedir que os usuários façam a atualização. No entanto, você precisa enviar usuários existentes através do fluxo de autorização do usuário para autorizar a nova permissão e obter um novo token de usuário para servidor para essas solicitações. -### User-to-server requests +### Solicitações de usuário para servidor -While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/v4/) or [REST v3](/v3/) endpoints. +Embora a maior parte da interação da sua API deva ocorrer usando os tokens de acesso de servidor para servidor, certos pontos de extremidade permitem que você execute ações por meio da API usando um token de acesso do usuário. Seu aplicativo pode fazer as seguintes solicitações usando pontos de extremidade do [GraphQL v4](/graphql) ou [REST v3](/rest). -#### Supported endpoints +#### Pontos de extremidade compatíveis {% if currentVersion == "free-pro-team@latest" %} -##### Actions Runners +##### Executores de ações -* [List runner applications for a repository](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) -* [List self-hosted runners for a repository](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) -* [Get a self-hosted runner for a repository](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) -* [Delete a self-hosted runner from a repository](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) -* [Create a registration token for a repository](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) -* [Create a remove token for a repository](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) -* [List runner applications for an organization](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) -* [List self-hosted runners for an organization](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) -* [Get a self-hosted runner for an organization](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) -* [Delete a self-hosted runner from an organization](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) -* [Create a registration token for an organization](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) -* [Create a remove token for an organization](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) +* [Listar aplicativos executores para um repositório](/rest/reference/actions#list-runner-applications-for-a-repository) +* [Listar executores auto-hospedados para um repositório](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [Obter um executor auto-hospedado para um repositório](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [Excluir um executor auto-hospedado de um repositório](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [Criar um token de registro para um repositório](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [Criar um token de remoção para um repositório](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [Listar aplicativos executores para uma organização](/rest/reference/actions#list-runner-applications-for-an-organization) +* [Listar executores auto-hospedados para uma organização](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [Obter um executor auto-hospedado para uma organização](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [Excluir um executor auto-hospedado de uma organização](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [Criar um token de registro para uma organização](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [Criar um token de remoção para uma organização](/rest/reference/actions#create-a-remove-token-for-an-organization) -##### Actions Secrets +##### Segredos de ações -* [Get a repository public key](/v3/actions/secrets/#get-a-repository-public-key) -* [List repository secrets](/v3/actions/secrets/#list-repository-secrets) -* [Get a repository secret](/v3/actions/secrets/#get-a-repository-secret) -* [Create or update a repository secret](/v3/actions/secrets/#create-or-update-a-repository-secret) -* [Delete a repository secret](/v3/actions/secrets/#delete-a-repository-secret) -* [Get an organization public key](/v3/actions/secrets/#get-an-organization-public-key) -* [List organization secrets](/v3/actions/secrets/#list-organization-secrets) -* [Get an organization secret](/v3/actions/secrets/#get-an-organization-secret) -* [Create or update an organization secret](/v3/actions/secrets/#create-or-update-an-organization-secret) -* [List selected repositories for an organization secret](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) -* [Set selected repositories for an organization secret](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) -* [Add selected repository to an organization secret](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) -* [Remove selected repository from an organization secret](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) -* [Delete an organization secret](/v3/actions/secrets/#delete-an-organization-secret) +* [Obter uma chave pública do repositório](/rest/reference/actions#get-a-repository-public-key) +* [Listar segredos do repositório](/rest/reference/actions#list-repository-secrets) +* [Obter um segredo do repositório](/rest/reference/actions#get-a-repository-secret) +* [Criar ou atualizar o segredo de um repositório](/rest/reference/actions#create-or-update-a-repository-secret) +* [Excluir o segredo de um repositório](/rest/reference/actions#delete-a-repository-secret) +* [Obter chave pública de uma organização](/rest/reference/actions#get-an-organization-public-key) +* [Listar segredos da organização](/rest/reference/actions#list-organization-secrets) +* [Obter segredo de uma organização](/rest/reference/actions#get-an-organization-secret) +* [Criar ou atualizar o segredo de uma organização](/rest/reference/actions#create-or-update-an-organization-secret) +* [Listar repositórios selecionados para o segredo de uma organização](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [Definir repositórios selecionados para o segredo de uma organização](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [Adicionar o repositório selecionado ao segredo de uma organização](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [Remover o repositório selecionado do segredo de uma organização](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [Excluir o segredo de uma organização](/rest/reference/actions#delete-an-organization-secret) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### Artifacts +##### Artefatos -* [List artifacts for a repository](/v3/actions/artifacts/#list-artifacts-for-a-repository) -* [List workflow run artifacts](/v3/actions/artifacts/#list-workflow-run-artifacts) -* [Get an artifact](/v3/actions/artifacts/#get-an-artifact) -* [Delete an artifact](/v3/actions/artifacts/#delete-an-artifact) -* [Download an artifact](/v3/actions/artifacts/#download-an-artifact) +* [Listar artefatos para um repositório](/rest/reference/actions#list-artifacts-for-a-repository) +* [Listar artefatos executados por fluxo de trabalho](/rest/reference/actions#list-workflow-run-artifacts) +* [Obter um artefato](/rest/reference/actions#get-an-artifact) +* [Excluir um artefato](/rest/reference/actions#delete-an-artifact) +* [Fazer o download de um artefato](/rest/reference/actions#download-an-artifact) {% endif %} -##### Check Runs +##### Execuções de verificação -* [Create a check run](/v3/checks/runs/#create-a-check-run) -* [Get a check run](/v3/checks/runs/#get-a-check-run) -* [Update a check run](/v3/checks/runs/#update-a-check-run) -* [List check run annotations](/v3/checks/runs/#list-check-run-annotations) -* [List check runs in a check suite](/v3/checks/runs/#list-check-runs-in-a-check-suite) -* [List check runs for a Git reference](/v3/checks/runs/#list-check-runs-for-a-git-reference) +* [Criar uma verificação de execução](/rest/reference/checks#create-a-check-run) +* [Obter uma verificação de execução](/rest/reference/checks#get-a-check-run) +* [Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run) +* [Listar anotações de execução de verificação](/rest/reference/checks#list-check-run-annotations) +* [Listar execuções de verificações em um conjunto de verificações](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [Listar execuções de verificação para uma referência do GIt](/rest/reference/checks#list-check-runs-for-a-git-reference) -##### Check Suites +##### conjuntos de verificações -* [Create a check suite](/v3/checks/suites/#create-a-check-suite) -* [Get a check suite](/v3/checks/suites/#get-a-check-suite) -* [Rerequest a check suite](/v3/checks/suites/#rerequest-a-check-suite) -* [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) -* [List check suites for a Git reference](/v3/checks/suites/#list-check-suites-for-a-git-reference) +* [Criar um conjunto de verificações](/rest/reference/checks#create-a-check-suite) +* [Obter um conjunto de verificações](/rest/reference/checks#get-a-check-suite) +* [Ressolicitar um conjunto de verificação](/rest/reference/checks#rerequest-a-check-suite) +* [Atualizar preferências do repositório para conjuntos de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [Listar os conjuntos de verificação para uma referência do Git](/rest/reference/checks#list-check-suites-for-a-git-reference) -##### Codes Of Conduct +##### Códigos de conduta -* [Get all codes of conduct](/v3/codes_of_conduct/#get-all-codes-of-conduct) -* [Get a code of conduct](/v3/codes_of_conduct/#get-a-code-of-conduct) +* [Obter todos os códigos de conduta](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [Obter um código de conduta](/rest/reference/codes-of-conduct#get-a-code-of-conduct) -##### Deployment Statuses +##### Status da implementação -* [List deployment statuses](/rest/reference/repos#list-deployment-statuses) -* [Create a deployment status](/rest/reference/repos#create-a-deployment-status) -* [Get a deployment status](/rest/reference/repos#get-a-deployment-status) +* [Listar status de implementação](/rest/reference/repos#list-deployment-statuses) +* [Criar um status de implementação](/rest/reference/repos#create-a-deployment-status) +* [Obter um status de implementação](/rest/reference/repos#get-a-deployment-status) -##### Deployments +##### Implantações -* [List deployments](/rest/reference/repos#list-deployments) -* [Create a deployment](/rest/reference/repos#create-a-deployment) -* [Get a deployment](/rest/reference/repos#get-a-deployment){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a deployment](/rest/reference/repos#delete-a-deployment){% endif %} +* [Listar implementações](/rest/reference/repos#list-deployments) +* [Criar uma implementação](/rest/reference/repos#create-a-deployment) +* [Faça um deploy](/rest/reference/repos#get-a-deployment){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +* [Excluir um deploy](/rest/reference/repos#delete-a-deployment){% endif %} -##### Events +##### Eventos -* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories) -* [List public organization events](/rest/reference/activity#list-public-organization-events) +* [Listar eventos públicos de uma rede de repositórios](/rest/reference/activity#list-public-events-for-a-network-of-repositories) +* [Listar eventos públicos da organização](/rest/reference/activity#list-public-organization-events) ##### Feeds -* [Get feeds](/rest/reference/activity#get-feeds) +* [Obter feeds](/rest/reference/activity#get-feeds) -##### Git Blobs +##### Blobs do Git -* [Create a blob](/v3/git/blobs/#create-a-blob) -* [Get a blob](/v3/git/blobs/#get-a-blob) +* [Criar um blob](/rest/reference/git#create-a-blob) +* [Obter um blob](/rest/reference/git#get-a-blob) -##### Git Commits +##### Commits do Git -* [Create a commit](/v3/git/commits/#create-a-commit) -* [Get a commit](/v3/git/commits/#get-a-commit) +* [Criar um commit](/rest/reference/git#create-a-commit) +* [Obter um commit](/rest/reference/git#get-a-commit) -##### Git Refs +##### Refs do Git -* [Create a reference](/v3/git/refs/#create-a-reference)* [Get a reference](/v3/git/refs/#get-a-reference) -* [List matching references](/v3/git/refs/#list-matching-references) -* [Update a reference](/v3/git/refs/#update-a-reference) -* [Delete a reference](/v3/git/refs/#delete-a-reference) +* [Criar uma referência](/rest/reference/git#create-a-reference)* [Obter uma referência](/rest/reference/git#get-a-reference) +* [Lista de referências correspondentes](/rest/reference/git#list-matching-references) +* [Atualizar uma referência](/rest/reference/git#update-a-reference) +* [Excluir uma referência](/rest/reference/git#delete-a-reference) -##### Git Tags +##### Tags do Git -* [Create a tag object](/v3/git/tags/#create-a-tag-object) -* [Get a tag](/v3/git/tags/#get-a-tag) +* [Criar um objeto de tag](/rest/reference/git#create-a-tag-object) +* [Obter uma tag](/rest/reference/git#get-a-tag) -##### Git Trees +##### Árvores do Git -* [Create a tree](/v3/git/trees/#create-a-tree) -* [Get a tree](/v3/git/trees/#get-a-tree) +* [Criar uma árvore](/rest/reference/git#create-a-tree) +* [Obter uma árvore](/rest/reference/git#get-a-tree) -##### Gitignore Templates +##### Modelos do Gitignore -* [Get all gitignore templates](/v3/gitignore/#get-all-gitignore-templates) -* [Get a gitignore template](/v3/gitignore/#get-a-gitignore-template) +* [Obter todos os modelos do gitignore](/rest/reference/gitignore#get-all-gitignore-templates) +* [Obter um modelo do gitignore](/rest/reference/gitignore#get-a-gitignore-template) -##### Installations +##### Instalações -* [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token) +* [Listar repositórios acessíveis ao token de acesso do usuário](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -##### Interaction Limits +##### Limites de interação -* [Get interaction restrictions for an organization](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) -* [Set interaction restrictions for an organization](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) -* [Remove interaction restrictions for an organization](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) -* [Get interaction restrictions for a repository](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) -* [Set interaction restrictions for a repository](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) -* [Remove interaction restrictions for a repository](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) +* [Obter restrições de interação para uma organização](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [Definir restrições de interação para uma organização](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [Remover restrições de interação para uma organização](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [Obter restrições de interação para um repositório](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [Definir restrições de interação para um repositório](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [Remover restrições de interação para um repositório](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) {% endif %} -##### Issue Assignees +##### Responsáveis pelo problema -* [Add assignees to an issue](/v3/issues/assignees/#add-assignees-to-an-issue) -* [Remove assignees from an issue](/v3/issues/assignees/#remove-assignees-from-an-issue) +* [Adicionar responsáveis a um problema](/rest/reference/issues#add-assignees-to-an-issue) +* [Remover responsáveis de um problema](/rest/reference/issues#remove-assignees-from-an-issue) -##### Issue Comments +##### Comentários do problema -* [List issue comments](/v3/issues/comments/#list-issue-comments) -* [Create an issue comment](/v3/issues/comments/#create-an-issue-comment) -* [List issue comments for a repository](/v3/issues/comments/#list-issue-comments-for-a-repository) -* [Get an issue comment](/v3/issues/comments/#get-an-issue-comment) -* [Update an issue comment](/v3/issues/comments/#update-an-issue-comment) -* [Delete an issue comment](/v3/issues/comments/#delete-an-issue-comment) +* [Listar comentários do problema](/rest/reference/issues#list-issue-comments) +* [Criar um comentário do problema](/rest/reference/issues#create-an-issue-comment) +* [Listar comentários de problemas para um repositório](/rest/reference/issues#list-issue-comments-for-a-repository) +* [Obter um comentário do issue](/rest/reference/issues#get-an-issue-comment) +* [Atualizar um comentário do problema](/rest/reference/issues#update-an-issue-comment) +* [Excluir comentário do problema](/rest/reference/issues#delete-an-issue-comment) -##### Issue Events +##### Eventos do problema -* [List issue events](/v3/issues/events/#list-issue-events) +* [Listar eventos do problema](/rest/reference/issues#list-issue-events) -##### Issue Timeline +##### Linha do tempo do problema -* [List timeline events for an issue](/v3/issues/timeline/#list-timeline-events-for-an-issue) +* [Listar eventos da linha do tempo para um problema](/rest/reference/issues#list-timeline-events-for-an-issue) -##### Issues +##### Problemas -* [List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user) -* [List assignees](/v3/issues/assignees/#list-assignees) -* [Check if a user can be assigned](/v3/issues/assignees/#check-if-a-user-can-be-assigned) -* [List repository issues](/v3/issues/#list-repository-issues) -* [Create an issue](/v3/issues/#create-an-issue) -* [Get an issue](/v3/issues/#get-an-issue) -* [Update an issue](/v3/issues/#update-an-issue) -* [Lock an issue](/v3/issues/#lock-an-issue) -* [Unlock an issue](/v3/issues/#unlock-an-issue) +* [Listar problemas atribuídos ao usuário autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [Listar responsáveis](/rest/reference/issues#list-assignees) +* [Verificar se um usuário pode ser atribuído](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [Listar problemas do repositório](/rest/reference/issues#list-repository-issues) +* [Cria um problema](/rest/reference/issues#create-an-issue) +* [Obter um problema](/rest/reference/issues#get-an-issue) +* [Atualizar um problema](/rest/reference/issues#update-an-issue) +* [Bloquear um problema](/rest/reference/issues#lock-an-issue) +* [Desbloquear um problema](/rest/reference/issues#unlock-an-issue) {% if currentVersion == "free-pro-team@latest" %} -##### Jobs +##### Trabalhos -* [Get a job for a workflow run](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) -* [Download job logs for a workflow run](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) -* [List jobs for a workflow run](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) +* [Obter um trabalho para uma execução de fluxo de trabalho](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [Fazer o download dos registros de trabalho para execução de um fluxo de trabalho](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [Listar tarefas para execução de um fluxo de trabalho](/rest/reference/actions#list-jobs-for-a-workflow-run) {% endif %} -##### Labels +##### Etiquetas -* [List labels for an issue](/v3/issues/labels/#list-labels-for-an-issue) -* [Add labels to an issue](/v3/issues/labels/#add-labels-to-an-issue) -* [Set labels for an issue](/v3/issues/labels/#set-labels-for-an-issue) -* [Remove all labels from an issue](/v3/issues/labels/#remove-all-labels-from-an-issue) -* [Remove a label from an issue](/v3/issues/labels/#remove-a-label-from-an-issue) -* [List labels for a repository](/v3/issues/labels/#list-labels-for-a-repository) -* [Create a label](/v3/issues/labels/#create-a-label) -* [Get a label](/v3/issues/labels/#get-a-label) -* [Update a label](/v3/issues/labels/#update-a-label) -* [Delete a label](/v3/issues/labels/#delete-a-label) -* [Get labels for every issue in a milestone](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) +* [Listar etiquetas para um problema](/rest/reference/issues#list-labels-for-an-issue) +* [Adicionar etiquetas a um problema](/rest/reference/issues#add-labels-to-an-issue) +* [Definir etiquetas para um problema](/rest/reference/issues#set-labels-for-an-issue) +* [Remover todas as etiquetas de um problema](/rest/reference/issues#remove-all-labels-from-an-issue) +* [Remover uma etiqueta de um problema](/rest/reference/issues#remove-a-label-from-an-issue) +* [Listar etiquetas para um repositório](/rest/reference/issues#list-labels-for-a-repository) +* [Criar uma etiqueta](/rest/reference/issues#create-a-label) +* [Obter uma etiqueta](/rest/reference/issues#get-a-label) +* [Atualizar uma etiqueta](/rest/reference/issues#update-a-label) +* [Excluir uma etiqueta](/rest/reference/issues#delete-a-label) +* [Obter etiquetas para cada problema em um marco](/rest/reference/issues#list-labels-for-issues-in-a-milestone) -##### Licenses +##### Licenças -* [Get all commonly used licenses](/v3/licenses/#get-all-commonly-used-licenses) -* [Get a license](/v3/licenses/#get-a-license) +* [Obter todas as licenças comumente usadas](/rest/reference/licenses#get-all-commonly-used-licenses) +* [Obtenha uma licença](/rest/reference/licenses#get-a-license) -##### Markdown +##### markdown -* [Render a Markdown document](/v3/markdown/#render-a-markdown-document) -* [Render a markdown document in raw mode](/v3/markdown/#render-a-markdown-document-in-raw-mode) +* [Renderizar um documento markdown](/rest/reference/markdown#render-a-markdown-document) +* [Renderizar um documento markdown no modo bruto](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) ##### Meta -* [Meta](/v3/meta/#meta) +* [Meta](/rest/reference/meta#meta) -##### Milestones +##### Marcos -* [List milestones](/v3/issues/milestones/#list-milestones) -* [Create a milestone](/v3/issues/milestones/#create-a-milestone) -* [Get a milestone](/v3/issues/milestones/#get-a-milestone) -* [Update a milestone](/v3/issues/milestones/#update-a-milestone) -* [Delete a milestone](/v3/issues/milestones/#delete-a-milestone) +* [Listar marcos](/rest/reference/issues#list-milestones) +* [Criar um marco](/rest/reference/issues#create-a-milestone) +* [Obter um marco](/rest/reference/issues#get-a-milestone) +* [Atualizar um marco](/rest/reference/issues#update-a-milestone) +* [Excluir um marco](/rest/reference/issues#delete-a-milestone) -##### Organization Hooks +##### Hooks da organização -* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks) -* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook) -* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook) -* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook) -* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) -* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) +* [Listar webhooks da organização](/rest/reference/orgs#webhooks/#list-organization-webhooks) +* [Criar um webhook da organização](/rest/reference/orgs#webhooks/#create-an-organization-webhook) +* [Obter um webhook da organização](/rest/reference/orgs#webhooks/#get-an-organization-webhook) +* [Atualizar um webhook da organização](/rest/reference/orgs#webhooks/#update-an-organization-webhook) +* [Excluir um webhook da organização](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) +* [Consultar um webhook da organização](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) {% if currentVersion == "free-pro-team@latest" %} -##### Organization Invitations +##### Convites da organização -* [List pending organization invitations](/v3/orgs/members/#list-pending-organization-invitations) -* [Create an organization invitation](/v3/orgs/members/#create-an-organization-invitation) -* [List organization invitation teams](/v3/orgs/members/#list-organization-invitation-teams) +* [Listar convites pendentes para organizações](/rest/reference/orgs#list-pending-organization-invitations) +* [Criar um convite de organização](/rest/reference/orgs#create-an-organization-invitation) +* [Listar equipes de convite da organização](/rest/reference/orgs#list-organization-invitation-teams) {% endif %} -##### Organization Members +##### Integrantes da organização -* [List organization members](/v3/orgs/members/#list-organization-members) -* [Check organization membership for a user](/v3/orgs/members/#check-organization-membership-for-a-user) -* [Remove an organization member](/v3/orgs/members/#remove-an-organization-member) -* [Get organization membership for a user](/v3/orgs/members/#get-organization-membership-for-a-user) -* [Set organization membership for a user](/v3/orgs/members/#set-organization-membership-for-a-user) -* [Remove organization membership for a user](/v3/orgs/members/#remove-organization-membership-for-a-user) -* [List public organization members](/v3/orgs/members/#list-public-organization-members) -* [Check public organization membership for a user](/v3/orgs/members/#check-public-organization-membership-for-a-user) -* [Set public organization membership for the authenticated user](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) -* [Remove public organization membership for the authenticated user](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) +* [Listar integrantes da organização](/rest/reference/orgs#list-organization-members) +* [Verificar associação da organização para um usuário](/rest/reference/orgs#check-organization-membership-for-a-user) +* [Remover um membro da organização](/rest/reference/orgs#remove-an-organization-member) +* [Obter a associação de uma organização para um usuário](/rest/reference/orgs#get-organization-membership-for-a-user) +* [Definir associação de organização para um usuário](/rest/reference/orgs#set-organization-membership-for-a-user) +* [Remover associação de organização para um usuário](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [Listar membros públicos da organização](/rest/reference/orgs#list-public-organization-members) +* [Verificar a associação da organização pública para um usuário](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [Definir associação à organização pública para o usuário autenticado](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [Remover associação à organização pública para o usuário autenticado](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) -##### Organization Outside Collaborators +##### Colaboradores externos da organização -* [List outside collaborators for an organization](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) -* [Convert an organization member to outside collaborator](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) -* [Remove outside collaborator from an organization](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) +* [Listar colaboradores externos para uma organização](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [Converter um integrante da organização em colaborador externo](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [Remover colaboradores externos de uma organização](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) {% if enterpriseServerVersions contains currentVersion %} -##### Organization Pre Receive Hooks +##### Hooks pre-receive da organização -* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) -* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) -* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) -* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) +* [Listar hooks pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) +* [Obter um hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) +* [Atualizar a aplicação do hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) +* [Remover a aplicação do hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -##### Organization Team Projects +##### Projetos da aquipe da organização -* [List team projects](/v3/teams/#list-team-projects) -* [Check team permissions for a project](/v3/teams/#check-team-permissions-for-a-project) -* [Add or update team project permissions](/v3/teams/#add-or-update-team-project-permissions) -* [Remove a project from a team](/v3/teams/#remove-a-project-from-a-team) +* [Listar projetos da equipe](/rest/reference/teams#list-team-projects) +* [Verificar permissões da equipe para um projeto](/rest/reference/teams#check-team-permissions-for-a-project) +* [Adicionar ou atualizar as permissões do projeto da equipe](/rest/reference/teams#add-or-update-team-project-permissions) +* [Remover um projeto de uma equipe](/rest/reference/teams#remove-a-project-from-a-team) {% endif %} -##### Organization Team Repositories +##### Repositórios da equipe da organização -* [List team repositories](/v3/teams/#list-team-repositories) -* [Check team permissions for a repository](/v3/teams/#check-team-permissions-for-a-repository) -* [Add or update team repository permissions](/v3/teams/#add-or-update-team-repository-permissions) -* [Remove a repository from a team](/v3/teams/#remove-a-repository-from-a-team) +* [Listar repositórios da equipe](/rest/reference/teams#list-team-repositories) +* [Verificar permissões da equipe para um repositório](/rest/reference/teams#check-team-permissions-for-a-repository) +* [Adicionar ou atualizar as permissões do repositório da equipe](/rest/reference/teams#add-or-update-team-repository-permissions) +* [Remover um repositório de uma equipe](/rest/reference/teams#remove-a-repository-from-a-team) {% if currentVersion == "free-pro-team@latest" %} -##### Organization Team Sync +##### Sincronizar equipe da organização -* [List idp groups for a team](/v3/teams/team_sync/#list-idp-groups-for-a-team) -* [Create or update idp group connections](/v3/teams/team_sync/#create-or-update-idp-group-connections) -* [List IdP groups for an organization](/v3/teams/team_sync/#list-idp-groups-for-an-organization) +* [Listar grupos de idp para uma equipe](/rest/reference/teams#list-idp-groups-for-a-team) +* [Criar ou atualizar conexões do grupo de idp](/rest/reference/teams#create-or-update-idp-group-connections) +* [Listar grupos de IdP para uma organização](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} -##### Organization Teams +##### Equipes da organização -* [List teams](/v3/teams/#list-teams) -* [Create a team](/v3/teams/#create-a-team) -* [Get a team by name](/v3/teams/#get-a-team-by-name) +* [Listar equipes](/rest/reference/teams#list-teams) +* [Criar uma equipe](/rest/reference/teams#create-a-team) +* [Obter uma equipe por nome](/rest/reference/teams#get-a-team-by-name) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -* [Get a team](/v3/teams/#get-a-team) +* [Obter uma equipe](/rest/reference/teams#get-a-team) {% endif %} -* [Update a team](/v3/teams/#update-a-team) -* [Delete a team](/v3/teams/#delete-a-team) +* [Atualizar uma equipe](/rest/reference/teams#update-a-team) +* [Excluir uma equipe](/rest/reference/teams#delete-a-team) {% if currentVersion == "free-pro-team@latest" %} -* [List pending team invitations](/v3/teams/members/#list-pending-team-invitations) +* [Listar convites pendentes da equipe](/rest/reference/teams#list-pending-team-invitations) {% endif %} -* [List team members](/v3/teams/members/#list-team-members) -* [Get team membership for a user](/v3/teams/members/#get-team-membership-for-a-user) -* [Add or update team membership for a user](/v3/teams/members/#add-or-update-team-membership-for-a-user) -* [Remove team membership for a user](/v3/teams/members/#remove-team-membership-for-a-user) -* [List child teams](/v3/teams/#list-child-teams) -* [List teams for the authenticated user](/v3/teams/#list-teams-for-the-authenticated-user) +* [Listar integrantes da equipe](/rest/reference/teams#list-team-members) +* [Obter a associação à equipe para um usuário](/rest/reference/teams#get-team-membership-for-a-user) +* [Adicionar ou atualizar membros de equipe para um usuário](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [Remover associação à equipe para um usuário](/rest/reference/teams#remove-team-membership-for-a-user) +* [Listar equipes secundárias](/rest/reference/teams#list-child-teams) +* [Listar equipes para o usuário autenticado](/rest/reference/teams#list-teams-for-the-authenticated-user) -##### Organizations +##### Organizações -* [List organizations](/v3/orgs/#list-organizations) -* [Get an organization](/v3/orgs/#get-an-organization) -* [Update an organization](/v3/orgs/#update-an-organization) -* [List organization memberships for the authenticated user](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) -* [Get an organization membership for the authenticated user](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) -* [Update an organization membership for the authenticated user](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) -* [List organizations for the authenticated user](/v3/orgs/#list-organizations-for-the-authenticated-user) -* [List organizations for a user](/v3/orgs/#list-organizations-for-a-user) +* [Listar organizações](/rest/reference/orgs#list-organizations) +* [Obter uma organização](/rest/reference/orgs#get-an-organization) +* [Atualizar uma organização](/rest/reference/orgs#update-an-organization) +* [Listar associações de organizações para os usuários autenticados](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [Obter uma associação de organização para o usuário autenticado](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [Atualizar uma associação de organização para o usuário autenticado](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [Listar organizações para o usuário autenticado](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [Listar organizações para um usuário](/rest/reference/orgs#list-organizations-for-a-user) {% if currentVersion == "free-pro-team@latest" %} -##### Organizations Credential Authorizations +##### Autorizações de credencial das organizações -* [List SAML SSO authorizations for an organization](/v3/orgs/#list-saml-sso-authorizations-for-an-organization) -* [Remove a SAML SSO authorization for an organization](/v3/orgs/#remove-a-saml-sso-authorization-for-an-organization) +* [Listar autorizações do SAML SSO para uma organização](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [Remover uma autorização do SAML SSO para uma organização](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### Organizations Scim +##### Scim das organizações -* [List SCIM provisioned identities](/v3/scim/#list-scim-provisioned-identities) -* [Provision and invite a SCIM user](/v3/scim/#provision-and-invite-a-scim-user) -* [Get SCIM provisioning information for a user](/v3/scim/#get-scim-provisioning-information-for-a-user) -* [Set SCIM information for a provisioned user](/v3/scim/#set-scim-information-for-a-provisioned-user) -* [Update an attribute for a SCIM user](/v3/scim/#update-an-attribute-for-a-scim-user) -* [Delete a SCIM user from an organization](/v3/scim/#delete-a-scim-user-from-an-organization) +* [Listar identidades provisionadas de SCIM](/rest/reference/scim#list-scim-provisioned-identities) +* [Provisionamento e convite para um usuário de SCIM](/rest/reference/scim#provision-and-invite-a-scim-user) +* [Obter informações de provisionamento de SCIM para um usuário](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [Definir informações de SCIM para um usuário provisionado](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [Atualizar um atributo para um usuário de SCIM](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [Excluir um usuário de SCIM de uma organização](/rest/reference/scim#delete-a-scim-user-from-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### Source Imports +##### Importação de fonte -* [Get an import status](/v3/migrations/source_imports/#get-an-import-status) -* [Start an import](/v3/migrations/source_imports/#start-an-import) -* [Update an import](/v3/migrations/source_imports/#update-an-import) -* [Cancel an import](/v3/migrations/source_imports/#cancel-an-import) -* [Get commit authors](/v3/migrations/source_imports/#get-commit-authors) -* [Map a commit author](/v3/migrations/source_imports/#map-a-commit-author) -* [Get large files](/v3/migrations/source_imports/#get-large-files) -* [Update Git LFS preference](/v3/migrations/source_imports/#update-git-lfs-preference) +* [Obter um status de importação](/rest/reference/migrations#get-an-import-status) +* [Iniciar importação](/rest/reference/migrations#start-an-import) +* [Atualizar uma importação](/rest/reference/migrations#update-an-import) +* [Cancelar uma importação](/rest/reference/migrations#cancel-an-import) +* [Obtenha autores do commit](/rest/reference/migrations#get-commit-authors) +* [Mapear um autor de commit](/rest/reference/migrations#map-a-commit-author) +* [Obter arquivos grandes](/rest/reference/migrations#get-large-files) +* [Atualizar preferência de LFS do Git](/rest/reference/migrations#update-git-lfs-preference) {% endif %} -##### Project Collaborators +##### Colaboradores do projeto -* [List project collaborators](/v3/projects/collaborators/#list-project-collaborators) -* [Add project collaborator](/v3/projects/collaborators/#add-project-collaborator) -* [Remove project collaborator](/v3/projects/collaborators/#remove-project-collaborator) -* [Get project permission for a user](/v3/projects/collaborators/#get-project-permission-for-a-user) +* [Listar colaboradores do projeto](/rest/reference/projects#list-project-collaborators) +* [Adicionar colaborador do projeto](/rest/reference/projects#add-project-collaborator) +* [Remover colaborador do projeto](/rest/reference/projects#remove-project-collaborator) +* [Obter permissão de projeto para um usuário](/rest/reference/projects#get-project-permission-for-a-user) -##### Projects +##### Projetos -* [List organization projects](/v3/projects/#list-organization-projects) -* [Create an organization project](/v3/projects/#create-an-organization-project) -* [Get a project](/v3/projects/#get-a-project) -* [Update a project](/v3/projects/#update-a-project) -* [Delete a project](/v3/projects/#delete-a-project) -* [List project columns](/v3/projects/columns/#list-project-columns) -* [Create a project column](/v3/projects/columns/#create-a-project-column) -* [Get a project column](/v3/projects/columns/#get-a-project-column) -* [Update a project column](/v3/projects/columns/#update-a-project-column) -* [Delete a project column](/v3/projects/columns/#delete-a-project-column) -* [List project cards](/v3/projects/cards/#list-project-cards) -* [Create a project card](/v3/projects/cards/#create-a-project-card) -* [Move a project column](/v3/projects/columns/#move-a-project-column) -* [Get a project card](/v3/projects/cards/#get-a-project-card) -* [Update a project card](/v3/projects/cards/#update-a-project-card) -* [Delete a project card](/v3/projects/cards/#delete-a-project-card) -* [Move a project card](/v3/projects/cards/#move-a-project-card) -* [List repository projects](/v3/projects/#list-repository-projects) -* [Create a repository project](/v3/projects/#create-a-repository-project) +* [Listar projetos da organização](/rest/reference/projects#list-organization-projects) +* [Criar um projeto da organização](/rest/reference/projects#create-an-organization-project) +* [Obter um projeto](/rest/reference/projects#get-a-project) +* [Atualizar um projeto](/rest/reference/projects#update-a-project) +* [Excluir um projeto](/rest/reference/projects#delete-a-project) +* [Listar colunas do projeto](/rest/reference/projects#list-project-columns) +* [Criar uma coluna do projeto](/rest/reference/projects#create-a-project-column) +* [Obter uma coluna do projeto](/rest/reference/projects#get-a-project-column) +* [Atualizar uma coluna do projeto](/rest/reference/projects#update-a-project-column) +* [Excluir uma coluna do projeto](/rest/reference/projects#delete-a-project-column) +* [Listar cartões do projeto](/rest/reference/projects#list-project-cards) +* [Criar um cartão de projeto](/rest/reference/projects#create-a-project-card) +* [Mover uma coluna do projeto](/rest/reference/projects#move-a-project-column) +* [Obter um cartão do projeto](/rest/reference/projects#get-a-project-card) +* [Atualizar um cartão do projeto](/rest/reference/projects#update-a-project-card) +* [Excluir um cartão do projeto](/rest/reference/projects#delete-a-project-card) +* [Mover um cartão do projeto](/rest/reference/projects#move-a-project-card) +* [Listar projetos do repositório](/rest/reference/projects#list-repository-projects) +* [Criar um projeto do repositório](/rest/reference/projects#create-a-repository-project) -##### Pull Comments +##### Commentários pull -* [List review comments on a pull request](/v3/pulls/comments/#list-review-comments-on-a-pull-request) -* [Create a review comment for a pull request](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) -* [List review comments in a repository](/v3/pulls/comments/#list-review-comments-in-a-repository) -* [Get a review comment for a pull request](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) -* [Update a review comment for a pull request](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) -* [Delete a review comment for a pull request](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) +* [Listar comentários de revisão em um pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [Criar um comentário de revisão para um pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [Listar comentários de revisão em um repositório](/rest/reference/pulls#list-review-comments-in-a-repository) +* [Obter um comentário de revisão para um pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [Atualizar um comentário de revisão para um pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [Excluir um comentário de revisão para um pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) -##### Pull Request Review Events +##### Eventos de revisão de pull request -* [Dismiss a review for a pull request](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) -* [Submit a review for a pull request](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) +* [Ignorar uma revisão para um pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [Enviar uma revisão para um pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request) -##### Pull Request Review Requests +##### Solicitações de revisão de pull request -* [List requested reviewers for a pull request](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) -* [Request reviewers for a pull request](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) -* [Remove requested reviewers from a pull request](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) +* [Listar revisores solicitados para um pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [Solicitar revisores para um pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [Remover revisores solicitados de um pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) -##### Pull Request Reviews +##### Revisões de pull request -* [List reviews for a pull request](/v3/pulls/reviews/#list-reviews-for-a-pull-request) -* [Create a review for a pull request](/v3/pulls/reviews/#create-a-review-for-a-pull-request) -* [Get a review for a pull request](/v3/pulls/reviews/#get-a-review-for-a-pull-request) -* [Update a review for a pull request](/v3/pulls/reviews/#update-a-review-for-a-pull-request) -* [List comments for a pull request review](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) +* [Listar comentários para um pull request](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [Criar uma revisão para um pull request](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [Obter uma revisão para um pull request](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [Atualizar uma revisão para um pull request](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [Listar comentários para uma revisão de pull request](/rest/reference/pulls#list-comments-for-a-pull-request-review) ##### Pulls -* [List pull requests](/v3/pulls/#list-pull-requests) -* [Create a pull request](/v3/pulls/#create-a-pull-request) -* [Get a pull request](/v3/pulls/#get-a-pull-request) -* [Update a pull request](/v3/pulls/#update-a-pull-request) -* [List commits on a pull request](/v3/pulls/#list-commits-on-a-pull-request) -* [List pull requests files](/v3/pulls/#list-pull-requests-files) -* [Check if a pull request has been merged](/v3/pulls/#check-if-a-pull-request-has-been-merged) -* [Merge a pull request (Merge Button)](/v3/pulls/#merge-a-pull-request) +* [Listar pull requests](/rest/reference/pulls#list-pull-requests) +* [Criar um pull request](/rest/reference/pulls#create-a-pull-request) +* [Obter um pull request](/rest/reference/pulls#get-a-pull-request) +* [Atualizar um pull request](/rest/reference/pulls#update-a-pull-request) +* [Listar commits em um pull request](/rest/reference/pulls#list-commits-on-a-pull-request) +* [Listar arquivos de pull requests](/rest/reference/pulls#list-pull-requests-files) +* [Verifiarse um pull request foi mesclado](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [Mesclar um pull request (Botão de mesclar)](/rest/reference/pulls#merge-a-pull-request) -##### Reactions +##### Reações -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/v3/reactions/#delete-a-reaction-legacy){% else %}* [Delete a reaction](/v3/reactions/#delete-a-reaction){% endif %} -* [List reactions for a commit comment](/v3/reactions/#list-reactions-for-a-commit-comment) -* [Create reaction for a commit comment](/v3/reactions/#create-reaction-for-a-commit-comment) -* [List reactions for an issue](/v3/reactions/#list-reactions-for-an-issue) -* [Create reaction for an issue](/v3/reactions/#create-reaction-for-an-issue) -* [List reactions for an issue comment](/v3/reactions/#list-reactions-for-an-issue-comment) -* [Create reaction for an issue comment](/v3/reactions/#create-reaction-for-an-issue-comment) -* [List reactions for a pull request review comment](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) -* [Create reaction for a pull request review comment](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) -* [List reactions for a team discussion comment](/v3/reactions/#list-reactions-for-a-team-discussion-comment) -* [Create reaction for a team discussion comment](/v3/reactions/#create-reaction-for-a-team-discussion-comment) -* [List reactions for a team discussion](/v3/reactions/#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/v3/reactions/#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a commit comment reaction](/v3/reactions/#delete-a-commit-comment-reaction) -* [Delete an issue reaction](/v3/reactions/#delete-an-issue-reaction) -* [Delete a reaction to a commit comment](/v3/reactions/#delete-an-issue-comment-reaction) -* [Delete a pull request comment reaction](/v3/reactions/#delete-a-pull-request-comment-reaction) -* [Delete team discussion reaction](/v3/reactions/#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/v3/reactions/#delete-team-discussion-comment-reaction){% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Excluir uma reação](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Excluir uma reação](/rest/reference/reactions#delete-a-reaction){% endif %} +* [Listar reações para um comentário de commit](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [Criar reação para um comentário de commit](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [Listar reações para um problema](/rest/reference/reactions#list-reactions-for-an-issue) +* [Criar reação para um problema](/rest/reference/reactions#create-reaction-for-an-issue) +* [Listar reações para um comentário do problema](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [Criar reação para um comentário do problema](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [Listar reações para um comentário de revisão de pull request](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [Criar reação para um comentário de revisão de pull request](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [Listar reações para um comentário de discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [Criar reação para um comentário de discussão em equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [Listar reações para uma discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [Crie uma reação para discussão de equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [Excluir uma reação de comentário de commit](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [Excluir uma reação do problema](/rest/reference/reactions#delete-an-issue-reaction) +* [Excluir uma reação a um comentário do commit](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [Excluir reação de comentário do pull request](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [Excluir reação para discussão em equipe](/rest/reference/reactions#delete-team-discussion-reaction) +* [Excluir reação de comentário para discussão de equipe](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} -##### Repositories +##### Repositórios -* [List organization repositories](/v3/repos/#list-organization-repositories) -* [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) -* [Get a repository](/v3/repos/#get-a-repository) -* [Update a repository](/v3/repos/#update-a-repository) -* [Delete a repository](/v3/repos/#delete-a-repository) -* [Compare two commits](/v3/repos/commits/#compare-two-commits) -* [List repository contributors](/v3/repos/#list-repository-contributors) -* [List forks](/rest/reference/repos#list-forks) -* [Create a fork](/v3/repos/forks/#create-a-fork) -* [List repository languages](/v3/repos/#list-repository-languages) -* [List repository tags](/v3/repos/#list-repository-tags) -* [List repository teams](/v3/repos/#list-repository-teams) -* [Transfer a repository](/v3/repos/#transfer-a-repository) -* [List public repositories](/v3/repos/#list-public-repositories) -* [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) -* [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -* [Create repository using a repository template](/v3/repos/#create-repository-using-a-repository-template) +* [Listar repositórios da organização](/rest/reference/repos#list-organization-repositories) +* [Criar um repositório para o usuário autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [Obter um repositório](/rest/reference/repos#get-a-repository) +* [Atualizar um repositório](/rest/reference/repos#update-a-repository) +* [Excluir um repositório](/rest/reference/repos#delete-a-repository) +* [Comparar dois commits](/rest/reference/repos#compare-two-commits) +* [Listar contribuidores do repositório](/rest/reference/repos#list-repository-contributors) +* [Listar bifurcações](/rest/reference/repos#list-forks) +* [Criar uma bifurcação](/rest/reference/repos#create-a-fork) +* [Listar idiomas do repositório](/rest/reference/repos#list-repository-languages) +* [Listar tags do repositório](/rest/reference/repos#list-repository-tags) +* [Listar equipes do repositório](/rest/reference/repos#list-repository-teams) +* [Transferir um repositório](/rest/reference/repos#transfer-a-repository) +* [Listar repositórios públicos](/rest/reference/repos#list-public-repositories) +* [Listar repositórios para o usuário autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [Listar repositórios para um usuário](/rest/reference/repos#list-repositories-for-a-user) +* [Criar repositório usando um modelo de repositório](/rest/reference/repos#create-repository-using-a-repository-template) -##### Repository Activity +##### Atividade do repositório -* [List stargazers](/rest/reference/activity#list-stargazers) -* [List watchers](/rest/reference/activity#list-watchers) -* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user) -* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) -* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user) -* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) -* [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user) +* [Listar observadores](/rest/reference/activity#list-stargazers) +* [Listar inspetores](/rest/reference/activity#list-watchers) +* [Listar repositórios favoritados pelo usuário](/rest/reference/activity#list-repositories-starred-by-a-user) +* [Verificar se um repositório foi favoritado pelo usuário autenticado](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) +* [Favorite um repositório para o usuário autenticado](/rest/reference/activity#star-a-repository-for-the-authenticated-user) +* [Desmarque um repositório como favorito para o usuário autenticado](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) +* [Listar repositórios inspecionados por um usuário](/rest/reference/activity#list-repositories-watched-by-a-user) {% if currentVersion == "free-pro-team@latest" %} -##### Repository Automated Security Fixes +##### Correções de segurança automatizadas no repositório -* [Enable automated security fixes](/v3/repos/#enable-automated-security-fixes) -* [Disable automated security fixes](/v3/repos/#disable-automated-security-fixes) +* [Habilitar as correções de segurança automatizadas](/rest/reference/repos#enable-automated-security-fixes) +* [Desabilitar as correções de segurança automatizadas](/rest/reference/repos#disable-automated-security-fixes) {% endif %} -##### Repository Branches +##### Branches do repositório -* [List branches](/v3/repos/branches/#list-branches) -* [Get a branch](/v3/repos/branches/#get-a-branch) -* [Get branch protection](/v3/repos/branches/#get-branch-protection) -* [Update branch protection](/v3/repos/branches/#update-branch-protection) -* [Delete branch protection](/v3/repos/branches/#delete-branch-protection) -* [Get admin branch protection](/v3/repos/branches/#get-admin-branch-protection) -* [Set admin branch protection](/v3/repos/branches/#set-admin-branch-protection) -* [Delete admin branch protection](/v3/repos/branches/#delete-admin-branch-protection) -* [Get pull request review protection](/v3/repos/branches/#get-pull-request-review-protection) -* [Update pull request review protection](/v3/repos/branches/#update-pull-request-review-protection) -* [Delete pull request review protection](/v3/repos/branches/#delete-pull-request-review-protection) -* [Get commit signature protection](/v3/repos/branches/#get-commit-signature-protection) -* [Create commit signature protection](/v3/repos/branches/#create-commit-signature-protection) -* [Delete commit signature protection](/v3/repos/branches/#delete-commit-signature-protection) -* [Get status checks protection](/v3/repos/branches/#get-status-checks-protection) -* [Update status check protection](/v3/repos/branches/#update-status-check-protection) -* [Remove status check protection](/v3/repos/branches/#remove-status-check-protection) -* [Get all status check contexts](/v3/repos/branches/#get-all-status-check-contexts) -* [Add status check contexts](/v3/repos/branches/#add-status-check-contexts) -* [Set status check contexts](/v3/repos/branches/#set-status-check-contexts) -* [Remove status check contexts](/v3/repos/branches/#remove-status-check-contexts) -* [Get access restrictions](/v3/repos/branches/#get-access-restrictions) -* [Delete access restrictions](/v3/repos/branches/#delete-access-restrictions) -* [List teams with access to the protected branch](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) -* [Add team access restrictions](/v3/repos/branches/#add-team-access-restrictions) -* [Set team access restrictions](/v3/repos/branches/#set-team-access-restrictions) -* [Remove team access restriction](/v3/repos/branches/#remove-team-access-restrictions) -* [List user restrictions of protected branch](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) -* [Add user access restrictions](/v3/repos/branches/#add-user-access-restrictions) -* [Set user access restrictions](/v3/repos/branches/#set-user-access-restrictions) -* [Remove user access restrictions](/v3/repos/branches/#remove-user-access-restrictions) -* [Merge a branch](/v3/repos/merging/#merge-a-branch) +* [Listar branches](/rest/reference/repos#list-branches) +* [Obter um branch](/rest/reference/repos#get-a-branch) +* [Obter proteção do branch](/rest/reference/repos#get-branch-protection) +* [Atualizar proteção do branch](/rest/reference/repos#update-branch-protection) +* [Excluir proteção do branch](/rest/reference/repos#delete-branch-protection) +* [Obter proteção do branch do administrador](/rest/reference/repos#get-admin-branch-protection) +* [Definir proteção do branch de administrador](/rest/reference/repos#set-admin-branch-protection) +* [Excluir proteção do branch de administrador](/rest/reference/repos#delete-admin-branch-protection) +* [Obter proteção de revisão do pull request](/rest/reference/repos#get-pull-request-review-protection) +* [Atualizar proteção de revisão do pull request](/rest/reference/repos#update-pull-request-review-protection) +* [Excluir proteção de revisão do pull request](/rest/reference/repos#delete-pull-request-review-protection) +* [Obter proteção de assinatura do commit](/rest/reference/repos#get-commit-signature-protection) +* [Criar proteção de assinatura do commit](/rest/reference/repos#create-commit-signature-protection) +* [Excluir proteção de assinatura do commit](/rest/reference/repos#delete-commit-signature-protection) +* [Obter proteção contra verificações de status](/rest/reference/repos#get-status-checks-protection) +* [Atualizar proteção da verificação de status](/rest/reference/repos#update-status-check-protection) +* [Remover proteção da verificação de status](/rest/reference/repos#remove-status-check-protection) +* [Obter todos os contextos de verificação de status](/rest/reference/repos#get-all-status-check-contexts) +* [Adicionar contextos de verificação de status](/rest/reference/repos#add-status-check-contexts) +* [Definir contextos de verificação de status](/rest/reference/repos#set-status-check-contexts) +* [Remover contextos de verificação de status](/rest/reference/repos#remove-status-check-contexts) +* [Obter restrições de acesso](/rest/reference/repos#get-access-restrictions) +* [Excluir restrições de acesso](/rest/reference/repos#delete-access-restrictions) +* [Listar equipes com acesso ao branch protegido](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [Adicionar restrições de acesso da equipe](/rest/reference/repos#add-team-access-restrictions) +* [Definir restrições de acesso da equipe](/rest/reference/repos#set-team-access-restrictions) +* [Remover restrição de acesso da equipe](/rest/reference/repos#remove-team-access-restrictions) +* [Listar restrições de usuário do branch protegido](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [Adicionar restrições de acesso do usuário](/rest/reference/repos#add-user-access-restrictions) +* [Definir restrições de acesso do usuário](/rest/reference/repos#set-user-access-restrictions) +* [Remover restrições de acesso do usuário](/rest/reference/repos#remove-user-access-restrictions) +* [Mesclar um branch](/rest/reference/repos#merge-a-branch) -##### Repository Collaborators +##### Colaboradores do repositório -* [List repository collaborators](/v3/repos/collaborators/#list-repository-collaborators) -* [Check if a user is a repository collaborator](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) -* [Add a repository collaborator](/v3/repos/collaborators/#add-a-repository-collaborator) -* [Remove a repository collaborator](/v3/repos/collaborators/#remove-a-repository-collaborator) -* [Get repository permissions for a user](/v3/repos/collaborators/#get-repository-permissions-for-a-user) +* [Listar colaboradores do repositório](/rest/reference/repos#list-repository-collaborators) +* [Verifique se um usuário é colaborador de um repositório](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [Adicionar colaborador de repositório](/rest/reference/repos#add-a-repository-collaborator) +* [Remover um colaborador de repositório](/rest/reference/repos#remove-a-repository-collaborator) +* [Obter permissões de repositório para um usuário](/rest/reference/repos#get-repository-permissions-for-a-user) -##### Repository Commit Comments +##### Comentários do commit do repositório -* [List commit comments for a repository](/v3/repos/comments/#list-commit-comments-for-a-repository) -* [Get a commit comment](/v3/repos/comments/#get-a-commit-comment) -* [Update a commit comment](/v3/repos/comments/#update-a-commit-comment) -* [Delete a commit comment](/v3/repos/comments/#delete-a-commit-comment) -* [List commit comments](/v3/repos/comments/#list-commit-comments) -* [Create a commit comment](/v3/repos/comments/#create-a-commit-comment) +* [Listar comentários de commit para um repositório](/rest/reference/repos#list-commit-comments-for-a-repository) +* [Obter um comentário de commit](/rest/reference/repos#get-a-commit-comment) +* [Atualizar um comentário de commit](/rest/reference/repos#update-a-commit-comment) +* [Excluir um comentário de commit](/rest/reference/repos#delete-a-commit-comment) +* [Listar comentários de commit](/rest/reference/repos#list-commit-comments) +* [Criar um comentário de commit](/rest/reference/repos#create-a-commit-comment) -##### Repository Commits +##### Commits do repositório -* [List commits](/v3/repos/commits/#list-commits) -* [Get a commit](/v3/repos/commits/#get-a-commit) -* [List branches for head commit](/v3/repos/commits/#list-branches-for-head-commit) -* [List pull requests associated with commit](/v3/repos/commits/#list-pull-requests-associated-with-commit) +* [Listar commits](/rest/reference/repos#list-commits) +* [Obter um commit](/rest/reference/repos#get-a-commit) +* [Listar branches para o commit principal](/rest/reference/repos#list-branches-for-head-commit) +* [Listar pull requests associados ao commit](/rest/reference/repos#list-pull-requests-associated-with-commit) -##### Repository Community +##### Comunidade do repositório -* [Get the code of conduct for a repository](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) +* [Obter o código de conduta para um repositório](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% if currentVersion == "free-pro-team@latest" %} -* [Get community profile metrics](/v3/repos/community/#get-community-profile-metrics) +* [Obter métricas do perfil da comunidade](/rest/reference/repos#get-community-profile-metrics) {% endif %} -##### Repository Contents +##### Conteúdo do repositório -* [Download a repository archive](/v3/repos/contents/#download-a-repository-archive) -* [Get repository content](/v3/repos/contents/#get-repository-content) -* [Create or update file contents](/v3/repos/contents/#create-or-update-file-contents) -* [Delete a file](/v3/repos/contents/#delete-a-file) -* [Get a repository README](/v3/repos/contents/#get-a-repository-readme) -* [Get the license for a repository](/v3/licenses/#get-the-license-for-a-repository) +* [Fazer o download de um arquivo do repositório](/rest/reference/repos#download-a-repository-archive) +* [Obter conteúdo de repositório](/rest/reference/repos#get-repository-content) +* [Criar ou atualizar conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents) +* [Excluir um arquivo](/rest/reference/repos#delete-a-file) +* [Obter um LEIAME do repositório](/rest/reference/repos#get-a-repository-readme) +* [Obter a licença para um repositório](/rest/reference/licenses#get-the-license-for-a-repository) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -##### Repository Event Dispatches +##### Envio de eventos do repositório -* [Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event) +* [Criar um evento de envio de repositório](/rest/reference/repos#create-a-repository-dispatch-event) {% endif %} -##### Repository Hooks +##### Hooks do repositório -* [List repository webhooks](/v3/repos/hooks/#list-repository-webhooks) -* [Create a repository webhook](/v3/repos/hooks/#create-a-repository-webhook) -* [Get a repository webhook](/v3/repos/hooks/#get-a-repository-webhook) -* [Update a repository webhook](/v3/repos/hooks/#update-a-repository-webhook) -* [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) -* [Ping a repository webhook](/v3/repos/hooks/#ping-a-repository-webhook) -* [Test the push repository webhook](/v3/repos/hooks/#test-the-push-repository-webhook) +* [Listar webhooks de repositório](/rest/reference/repos#list-repository-webhooks) +* [Criar um webhook do repositório](/rest/reference/repos#create-a-repository-webhook) +* [Obter um webhook do repositório](/rest/reference/repos#get-a-repository-webhook) +* [Atualizar um webhook do repositório](/rest/reference/repos#update-a-repository-webhook) +* [Excluir um webhook do repositório](/rest/reference/repos#delete-a-repository-webhook) +* [Fazer ping no webhook de um repositório](/rest/reference/repos#ping-a-repository-webhook) +* [Testar o webhook do repositório de push](/rest/reference/repos#test-the-push-repository-webhook) -##### Repository Invitations +##### Convites do repositório -* [List repository invitations](/v3/repos/invitations/#list-repository-invitations) -* [Update a repository invitation](/v3/repos/invitations/#update-a-repository-invitation) -* [Delete a repository invitation](/v3/repos/invitations/#delete-a-repository-invitation) -* [List repository invitations for the authenticated user](/v3/repos/invitations/#list-repository-invitations-for-the-authenticated-user) -* [Accept a repository invitation](/v3/repos/invitations/#accept-a-repository-invitation) -* [Decline a repository invitation](/v3/repos/invitations/#decline-a-repository-invitation) +* [Listar convites para repositórios](/rest/reference/repos#list-repository-invitations) +* [Atualizar um convite para um repositório](/rest/reference/repos#update-a-repository-invitation) +* [Excluir um convite para um repositório](/rest/reference/repos#delete-a-repository-invitation) +* [Listar convites de repositório para o usuário autenticado](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [Aceitar um convite de repositório](/rest/reference/repos#accept-a-repository-invitation) +* [Recusar um convite de repositório](/rest/reference/repos#decline-a-repository-invitation) -##### Repository Keys +##### Chaves de repositório -* [List deploy keys](/v3/repos/keys/#list-deploy-keys) -* [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) -* [Get a deploy key](/v3/repos/keys/#get-a-deploy-key) -* [Delete a deploy key](/v3/repos/keys/#delete-a-deploy-key) +* [Listar chaves de implantação](/rest/reference/repos#list-deploy-keys) +* [Criar uma chave de implantação](/rest/reference/repos#create-a-deploy-key) +* [Obter uma chave de implantação](/rest/reference/repos#get-a-deploy-key) +* [Excluir uma chave de implantação](/rest/reference/repos#delete-a-deploy-key) -##### Repository Pages +##### Páginas do repositório -* [Get a GitHub Pages site](/rest/reference/repos#get-a-github-pages-site) -* [Create a GitHub Pages site](/rest/reference/repos#create-a-github-pages-site) -* [Update information about a GitHub Pages site](/rest/reference/repos#update-information-about-a-github-pages-site) -* [Delete a GitHub Pages site](/rest/reference/repos#delete-a-github-pages-site) -* [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) -* [Request a GitHub Pages build](/rest/reference/repos#request-a-github-pages-build) -* [Get GitHub Pages build](/rest/reference/repos#get-github-pages-build) -* [Get latest pages build](/rest/reference/repos#get-latest-pages-build) +* [Obter um site do GitHub Pages](/rest/reference/repos#get-a-github-pages-site) +* [Criar um site do GitHub Pages](/rest/reference/repos#create-a-github-pages-site) +* [Atualizar informações sobre um site do GitHub Pages](/rest/reference/repos#update-information-about-a-github-pages-site) +* [Excluir um site do GitHub Pages](/rest/reference/repos#delete-a-github-pages-site) +* [Listar criações do GitHub Pages](/rest/reference/repos#list-github-pages-builds) +* [Solicitar uma criação do GitHub Pages](/rest/reference/repos#request-a-github-pages-build) +* [Obter uma criação do GitHub Pages](/rest/reference/repos#get-github-pages-build) +* [Obter a última criação de páginas](/rest/reference/repos#get-latest-pages-build) {% if enterpriseServerVersions contains currentVersion %} -##### Repository Pre Receive Hooks +##### Hooks pre-receive do repositório -* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) -* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) -* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) -* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) +* [Listar hooks pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) +* [Obter um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) +* [Atualizar a aplicação de um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) +* [Remover a aplicação de um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) {% endif %} -##### Repository Releases +##### Versões do repositório -* [List releases](/rest/reference/repos/#list-releases) -* [Create a release](/rest/reference/repos/#create-a-release) -* [Get a release](/rest/reference/repos/#get-a-release) -* [Update a release](/rest/reference/repos/#update-a-release) -* [Delete a release](/rest/reference/repos/#delete-a-release) -* [List release assets](/rest/reference/repos/#list-release-assets) -* [Get a release asset](/rest/reference/repos/#get-a-release-asset) -* [Update a release asset](/rest/reference/repos/#update-a-release-asset) -* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset) -* [Get the latest release](/rest/reference/repos/#get-the-latest-release) -* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name) +* [Listar versões](/rest/reference/repos/#list-releases) +* [Criar uma versão](/rest/reference/repos/#create-a-release) +* [Obter uma versão](/rest/reference/repos/#get-a-release) +* [Atualizar uma versão](/rest/reference/repos/#update-a-release) +* [Excluir uma versão](/rest/reference/repos/#delete-a-release) +* [Listar ativos da versão](/rest/reference/repos/#list-release-assets) +* [Obter um ativo da versão](/rest/reference/repos/#get-a-release-asset) +* [Atualizar um ativo da versão](/rest/reference/repos/#update-a-release-asset) +* [Excluir um ativo da versão](/rest/reference/repos/#delete-a-release-asset) +* [Obter a atualização mais recente](/rest/reference/repos/#get-the-latest-release) +* [Obter uma versão pelo nome da tag](/rest/reference/repos/#get-a-release-by-tag-name) -##### Repository Stats +##### Estatísticas do repositório -* [Get the weekly commit activity](/v3/repos/statistics/#get-the-weekly-commit-activity) -* [Get the last year of commit activity](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -* [Get all contributor commit activity](/v3/repos/statistics/#get-all-contributor-commit-activity) -* [Get the weekly commit count](/v3/repos/statistics/#get-the-weekly-commit-count) -* [Get the hourly commit count for each day](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +* [Obter a atividade semanal do commit](/rest/reference/repos#get-the-weekly-commit-activity) +* [Obter o último ano da atividade de commit](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [Obter toda a atividade do commit do contribuidor](/rest/reference/repos#get-all-contributor-commit-activity) +* [Obter a contagem semanal do commit](/rest/reference/repos#get-the-weekly-commit-count) +* [Obter a contagem do commit por hora para cada dia](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) {% if currentVersion == "free-pro-team@latest" %} -##### Repository Vulnerability Alerts +##### Alertas de vulnerabilidade de repositório -* [Enable vulnerability alerts](/v3/repos/#enable-vulnerability-alerts) -* [Disable vulnerability alerts](/v3/repos/#disable-vulnerability-alerts) +* [Habilitar alertas de vulnerabilidade](/rest/reference/repos#enable-vulnerability-alerts) +* [Desabilitar alertas de vulnerabilidade](/rest/reference/repos#disable-vulnerability-alerts) {% endif %} -##### Root +##### Raiz -* [Root endpoint](/v3/#root-endpoint) -* [Emojis](/v3/emojis/#emojis) -* [Get rate limit status for the authenticated user](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) +* [Ponto de extremidade raiz](/rest#root-endpoint) +* [Emojis](/rest/reference/emojis#emojis) +* [Obter status do limite de taxa para o usuário autenticado](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) -##### Search +##### Pesquisar -* [Search code](/v3/search/#search-code) -* [Search commits](/v3/search/#search-commits) -* [Search labels](/v3/search/#search-labels) -* [Search repositories](/v3/search/#search-repositories) -* [Search topics](/v3/search/#search-topics) -* [Search users](/v3/search/#search-users) +* [Buscar código](/rest/reference/search#search-code) +* [Pesquisar commits](/rest/reference/search#search-commits) +* [Pesquisar etiquetas](/rest/reference/search#search-labels) +* [Pesquisar repositórios](/rest/reference/search#search-repositories) +* [Pesquisar tópicos](/rest/reference/search#search-topics) +* [Pesquisar usuários](/rest/reference/search#search-users) -##### Statuses +##### Status -* [Get the combined status for a specific reference](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) -* [List commit statuses for a reference](/v3/repos/statuses/#list-commit-statuses-for-a-reference) -* [Create a commit status](/v3/repos/statuses/#create-a-commit-status) +* [Obter o status combinado para uma referência específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [Listar status de commit para uma referência](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [Criar um status de commit](/rest/reference/repos#create-a-commit-status) -##### Team Discussions +##### Discussões de equipe -* [List discussions](/v3/teams/discussions/#list-discussions) -* [Create a discussion](/v3/teams/discussions/#create-a-discussion) -* [Get a discussion](/v3/teams/discussions/#get-a-discussion) -* [Update a discussion](/v3/teams/discussions/#update-a-discussion) -* [Delete a discussion](/v3/teams/discussions/#delete-a-discussion) -* [List discussion comments](/v3/teams/discussion_comments/#list-discussion-comments) -* [Create a discussion comment](/v3/teams/discussion_comments/#create-a-discussion-comment) -* [Get a discussion comment](/v3/teams/discussion_comments/#get-a-discussion-comment) -* [Update a discussion comment](/v3/teams/discussion_comments/#update-a-discussion-comment) -* [Delete a discussion comment](/v3/teams/discussion_comments/#delete-a-discussion-comment) +* [Listar discussões](/rest/reference/teams#list-discussions) +* [Criar discussão](/rest/reference/teams#create-a-discussion) +* [Obter discussão](/rest/reference/teams#get-a-discussion) +* [Atualizar uma discussão](/rest/reference/teams#update-a-discussion) +* [Excluir uma discussão](/rest/reference/teams#delete-a-discussion) +* [Listar comentários da discussão](/rest/reference/teams#list-discussion-comments) +* [Criar um comentário da discussão](/rest/reference/teams#create-a-discussion-comment) +* [Obter um comentário da discussão](/rest/reference/teams#get-a-discussion-comment) +* [Atualizar um comentário da discussão](/rest/reference/teams#update-a-discussion-comment) +* [Excluir um comentário da discussão](/rest/reference/teams#delete-a-discussion-comment) -##### Topics +##### Tópicos -* [Get all repository topics](/v3/repos#get-all-repository-topics) -* [Replace all repository topics](/v3/repos/#replace-all-repository-topics) +* [Obter todos os tópicos do repositório](/rest/reference/repos#get-all-repository-topics) +* [Substituir todos os tópicos do repositório](/rest/reference/repos#replace-all-repository-topics) {% if currentVersion == "free-pro-team@latest" %} -##### Traffic +##### Tráfego -* [Get repository clones](/v3/repos/traffic/#get-repository-clones) -* [Get top referral paths](/v3/repos/traffic/#get-top-referral-paths) -* [Get top referral sources](/v3/repos/traffic/#get-top-referral-sources) -* [Get page views](/v3/repos/traffic/#get-page-views) +* [Obter clones do repositório](/rest/reference/repos#get-repository-clones) +* [Obter caminhos de referência superior](/rest/reference/repos#get-top-referral-paths) +* [Obter fontes de referência superior](/rest/reference/repos#get-top-referral-sources) +* [Obter visualizações de páginas](/rest/reference/repos#get-page-views) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### User Blocking +##### Bloquear usuário -* [List users blocked by the authenticated user](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) -* [Check if a user is blocked by the authenticated user](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) -* [List users blocked by an organization](/v3/orgs/blocking/#list-users-blocked-by-an-organization) -* [Check if a user is blocked by an organization](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) -* [Block a user from an organization](/v3/orgs/blocking/#block-a-user-from-an-organization) -* [Unblock a user from an organization](/v3/orgs/blocking/#unblock-a-user-from-an-organization) -* [Block a user](/v3/users/blocking/#block-a-user) -* [Unblock a user](/v3/users/blocking/#unblock-a-user) +* [Listar usuários bloqueados pelo usuário autenticado](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [Verificar se um usuário está bloqueado pelo usuário autenticado](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [Listar usuários bloqueados por uma organização](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [Verificar se um usuário está bloqueado por uma organização](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [Bloquear um usuário de uma organização](/rest/reference/orgs#block-a-user-from-an-organization) +* [Desbloquear um usuário de uma organização](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [Bloquear usuário](/rest/reference/users#block-a-user) +* [Desbloquear usuário](/rest/reference/users#unblock-a-user) {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -##### User Emails +##### Emails do usuário {% if currentVersion == "free-pro-team@latest" %} -* [Set primary email visibility for the authenticated user](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) +* [Configurar visibilidade do e-mail principal para o usuário autenticado](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %} -* [List email addresses for the authenticated user](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) -* [Add email address(es)](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) -* [Delete email address(es)](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) -* [List public email addresses for the authenticated user](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) +* [Listar endereços de e-mail para o usuário autenticado](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [Adicionar endereço(s) de e-mail](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [Excluir endereço(s) de e-mail](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [Listar endereços de e-mail públicos para o usuário autenticado](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) {% endif %} -##### User Followers +##### Seguidores do usuário -* [List followers of a user](/v3/users/followers/#list-followers-of-a-user) -* [List the people a user follows](/v3/users/followers/#list-the-people-a-user-follows) -* [Check if a person is followed by the authenticated user](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) -* [Follow a user](/v3/users/followers/#follow-a-user) -* [Unfollow a user](/v3/users/followers/#unfollow-a-user) -* [Check if a user follows another user](/v3/users/followers/#check-if-a-user-follows-another-user) +* [Listar seguidores de um usuário](/rest/reference/users#list-followers-of-a-user) +* [Listar as pessoas que um usuário segue](/rest/reference/users#list-the-people-a-user-follows) +* [Verificar se uma pessoa é seguida pelo usuário autenticado](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [Seguir um usuário](/rest/reference/users#follow-a-user) +* [Deixar de seguir um usuário](/rest/reference/users#unfollow-a-user) +* [Verificar se um usuário segue outro usuário](/rest/reference/users#check-if-a-user-follows-another-user) -##### User Gpg Keys +##### Chaves Gpg do usuário -* [List GPG keys for the authenticated user](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) -* [Create a GPG key for the authenticated user](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) -* [Get a GPG key for the authenticated user](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) -* [Delete a GPG key for the authenticated user](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) -* [List gpg keys for a user](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) +* [Listar chaves GPG para o usuário autenticado](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [Criar uma chave GPG para o usuário autenticado](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [Obter uma chave GPG para o usuário autenticado](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [Excluir uma chave GPG para o usuário autenticado](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [Listar chaves gpg para um usuário](/rest/reference/users#list-gpg-keys-for-a-user) -##### User Public Keys +##### Chaves públicas do usuário -* [List public SSH keys for the authenticated user](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) -* [Create a public SSH key for the authenticated user](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) -* [Get a public SSH key for the authenticated user](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) -* [Delete a public SSH key for the authenticated user](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) -* [List public keys for a user](/v3/users/keys/#list-public-keys-for-a-user) +* [Listar chaves SSH públicas para o usuário autenticado](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [Criar uma chave SSH pública para o usuário autenticado](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [Obter uma chave SSH pública para o usuário autenticado](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [Excluir uma chave SSH pública para o usuário autenticado](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [Listar chaves públicas para um usuário](/rest/reference/users#list-public-keys-for-a-user) -##### Users +##### Usuários -* [Get the authenticated user](/v3/users/#get-the-authenticated-user) -* [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) +* [Obter o usuário autenticado](/rest/reference/users#get-the-authenticated-user) +* [Listar instalações de aplicativos acessíveis ao token de acesso do usuário](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [Listar assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% endif %} -* [List users](/v3/users/#list-users) -* [Get a user](/v3/users/#get-a-user) +* [Listar usuários](/rest/reference/users#list-users) +* [Obter um usuário](/rest/reference/users#get-a-user) {% if currentVersion == "free-pro-team@latest" %} -##### Workflow Runs +##### Execuções do fluxo de trabalho -* [List workflow runs for a repository](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) -* [Get a workflow run](/v3/actions/workflow-runs/#get-a-workflow-run) -* [Cancel a workflow run](/v3/actions/workflow-runs/#cancel-a-workflow-run) -* [Download workflow run logs](/v3/actions/workflow-runs/#download-workflow-run-logs) -* [Delete workflow run logs](/v3/actions/workflow-runs/#delete-workflow-run-logs) -* [Re run a workflow](/v3/actions/workflow-runs/#re-run-a-workflow) -* [List workflow runs](/v3/actions/workflow-runs/#list-workflow-runs) -* [Get workflow run usage](/v3/actions/workflow-runs/#get-workflow-run-usage) +* [Listar execuções do fluxo de trabalho para um repositório](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [Obter execução de um fluxo de trabalho](/rest/reference/actions#get-a-workflow-run) +* [Cancelar execução de um fluxo de trabalho](/rest/reference/actions#cancel-a-workflow-run) +* [Fazer o download dos registros de execução do fluxo de trabalho](/rest/reference/actions#download-workflow-run-logs) +* [Excluir registros de execução do fluxo de trabalho](/rest/reference/actions#delete-workflow-run-logs) +* [Rexecutar um fluxo de trabalho](/rest/reference/actions#re-run-a-workflow) +* [Listar execuções do fluxo de trabalho](/rest/reference/actions#list-workflow-runs) +* [Obter uso da execução do fluxo de trabalho](/rest/reference/actions#get-workflow-run-usage) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### Workflows +##### Fluxos de trabalho -* [List repository workflows](/v3/actions/workflows/#list-repository-workflows) -* [Get a workflow](/v3/actions/workflows/#get-a-workflow) -* [Get workflow usage](/v3/actions/workflows/#get-workflow-usage) +* [Listar fluxos de trabalho do repositório](/rest/reference/actions#list-repository-workflows) +* [Obter um fluxo de trabalho](/rest/reference/actions#get-a-workflow) +* [Obter uso do workflow](/rest/reference/actions#get-workflow-usage) {% endif %} diff --git a/translations/pt-BR/content/developers/apps/installing-github-apps.md b/translations/pt-BR/content/developers/apps/installing-github-apps.md index f277541f14..aa0c0c07cb 100644 --- a/translations/pt-BR/content/developers/apps/installing-github-apps.md +++ b/translations/pt-BR/content/developers/apps/installing-github-apps.md @@ -47,13 +47,13 @@ Essas etapas pressupõem que você [criou um {% data variables.product.prodname_ 1. Na [página de configurações dos aplicativos GitHub](https://github.com/settings/apps), selecione o aplicativo público que você deseja configurar para que outras pessoas instalem. 2. Em "URL da página inicial", digite a URL para a página inicial do seu aplicativo e clique em **Salvar as alterações**. ![URL da página inicial](/assets/images/github-apps/github_apps_homepageURL.png) 3. O GitHub fornece uma página inicial para o seu aplicativo que inclui um link para a "URL da página inicial" do seu aplicativo. Para visitar a página inicial no GitHub, copie a URL do "Link público" e cole-a em um navegador. ![Link público](/assets/images/github-apps/github_apps_public_link.png) -4. Create a homepage for your app that includes the app installation URL: `{% data variables.product.oauth_host_code %}/apps//installations/new`. +4. Crie uma página inicial para o seu aplicativo que inclui a URL de instalação do aplicativo: `{% data variables.product.oauth_host_code %}/apps//installations/new`. ### Autorizar usuários durante a instalação Você pode simplificar o processo de autorização concluindo-o durante a instalação do aplicativo. Para fazer isso, selecione **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo no GitHub. Consulte "[Criando um aplicativo GitHub](/apps/building-github-apps/creating-a-github-app/)" para saber mais. -Assim que alguém tiver instalado seu aplicativo, você deverá obter um token de acesso para o usuário. See steps 2 and 3 in "[Identifying users on your site](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)" to learn more. +Assim que alguém tiver instalado seu aplicativo, você deverá obter um token de acesso para o usuário. Veja as etapas 2 e 3 em "[Identificar usuários no seu site](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)" para saber mais. ### Preservar o estado do aplicativo durante a instalação Você pode fornecer um parâmetro de `estado` na URL de instalação de um aplicativo para preservar o estado da página do aplicativo e fazer com que as pessoas retornem para seu estado após efetuarem a instalação, autenticação ou aceitarem as atualizações no seu aplicativo GitHub. Por exemplo, você poderia usar o `estado` para correlacionar uma instalação a um usuário ou conta. diff --git a/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 6b718ad69d..19f4bc35f4 100644 --- a/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -23,7 +23,7 @@ Este artigo fornece orientações para integradores existentes que estão consid - O suporte integrado para o OAuth ainda está disponível para aplicativos GitHub usando [pontos finais de usuário para servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). - [Os limites de taxa de API](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) dedicados para as contas do bot são escalados com a sua integração. - Os proprietários de repositórios podem [instalar aplicativos GitHub](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) em repositórios de organizações. Se a configuração de um aplicativo GitHub tiver permissões que solicitam os recursos de uma organização, o proprietário d organização deverá aprovar a instalação. -- O suporte da comunidade do código aberto está disponível nas [bibliotecas do Octokit](/v3/libraries/) e outros estruturas como, por exemplo, o [Probot](https://probot.github.io/). +- O suporte da comunidade do código aberto está disponível nas [bibliotecas do Octokit](/rest/overview/libraries) e outros estruturas como, por exemplo, o [Probot](https://probot.github.io/). - Os integradores que constroem os aplicativos GitHub têm a oportunidade de adotar acesso prévio às APIs. ### Converter um aplicativo OAuth em um aplicativo GitHub @@ -42,13 +42,13 @@ Essas diretrizes assumem que você tem um aplicativo OAuth registrado{% if curre #### Revise os pontos finais da API disponíveis para os aplicativos do GitHub -Embora a maioria dos pontos finais da [API REST](/v3) e as consultas do [GraphQL](/v4) estejam disponíveis para os aplicativos GitHub atualmente, ainda estamos em vias de habilitar alguns pontos finais. Revise os [pontos finais da REST disponíveis](/v3/apps/available-endpoints/) para garantir que os pontos finais de que você precisa sejam compatíveis com o aplicativo GitHub. Observe que alguns dos pontos finais da API ativados para os aplicativos GitHub permitem que o aplicativo aja em nome do usuário. Consulte "[Solicitações de usuário para servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" para obter uma lista de pontos finais que permitem que um aplicativo GitHub seja autenticado como usuário. +Embora a maioria dos pontos finais da [API REST](/rest) e as consultas do [GraphQL](/graphql) estejam disponíveis para os aplicativos GitHub atualmente, ainda estamos em vias de habilitar alguns pontos finais. Revise os [pontos finais da REST disponíveis](/rest/overview/endpoints-available-for-github-apps) para garantir que os pontos finais de que você precisa sejam compatíveis com o aplicativo GitHub. Observe que alguns dos pontos finais da API ativados para os aplicativos GitHub permitem que o aplicativo aja em nome do usuário. Consulte "[Solicitações de usuário para servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" para obter uma lista de pontos finais que permitem que um aplicativo GitHub seja autenticado como usuário. Recomendamos que você reveja a lista de pontos finais de API de que você precisa assim que possível. Informe o a equipe de suporte caso haja um ponto final necessário que ainda não esteja habilitado para {% data variables.product.prodname_github_app %}s. #### Projete para permanecer dentro dos limites de taxa da API -Os aplicativos GitHub usam [regras móveis para limites de taxa](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), que podem aumentar com base no número de repositórios e usuários da organização. Um aplicativo do GitHub também pode usar [solicitações condicionais](/v3/#conditional-requests) ou consolidar solicitações usando [GraphQL API V4](/v4/). +Os aplicativos GitHub usam [regras móveis para limites de taxa](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), que podem aumentar com base no número de repositórios e usuários da organização. Um aplicativo do GitHub também pode usar [solicitações condicionais](/rest#conditional-requests) ou consolidar solicitações usando [GraphQL API V4](/graphql). #### Cadastre um novo aplicativo GitHub @@ -56,7 +56,7 @@ Uma vez que você decidiu fazer a troca para os aplicativos GitHub, você precis #### Determine as permissões de que seu aplicativo precisa -Ao registrar seu aplicativo GitHub, você deverá selecionar as permissões necessárias por cada ponto final usado no código do seu aplicativo. Consulte "[Permissões do aplicativo GitHub](/v3/apps/permissions/)" para obter uma lista das permissões necessárias para cada ponto final disponível nos aplicativos GitHub. +Ao registrar seu aplicativo GitHub, você deverá selecionar as permissões necessárias por cada ponto final usado no código do seu aplicativo. Consulte "[Permissões do aplicativo GitHub](/rest/reference/permissions-required-for-github-apps)" para obter uma lista das permissões necessárias para cada ponto final disponível nos aplicativos GitHub. Nas configurações do seu aplicativo GitHub, você pode especificar se seu aplicativo precisa de acesso `Sem Acesso`, `somente leitura`, ou `Leitura & Gravação` para cada tipo de permissão. As permissões refinadas permitem que seu aplicativo obtenha acesso direcionado ao subconjunto de dados de que você precisa. Recomendamos especificar o menor conjunto de permissões possível que fornece a funcionalidade desejada. @@ -90,11 +90,11 @@ Uma vez que você fez a transição de um aplicativo OAuth para um aplicativo Gi https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -Você deverá substituir `YOUR_APP_NAME` pelo nome do seu aplicativo GitHub, `ID_OF_USER_OR_ORG` pelo ID do seu usuário-alvo ou organização, e incluir até 100 IDs de repositório (`REPO_A_ID` e `REPO_B_ID`). Para obter uma lista de repositórios à qual seu aplicativo OAuth tem acesso, use os pontos finais [Listar repositórios para o usuário autenticado](/v3/repos/#list-repositories-for-the-authenticated-user) e [Listar repositórios de organização](/v3/repos/#list-organization-repositories). +Você deverá substituir `YOUR_APP_NAME` pelo nome do seu aplicativo GitHub, `ID_OF_USER_OR_ORG` pelo ID do seu usuário-alvo ou organização, e incluir até 100 IDs de repositório (`REPO_A_ID` e `REPO_B_ID`). Para obter uma lista de repositórios à qual seu aplicativo OAuth tem acesso, use os pontos finais [Listar repositórios para o usuário autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user) e [Listar repositórios de organização](/rest/reference/repos#list-organization-repositories). #### Remova quaisquer hooks de repositório desnecessários -Uma vez que seu aplicativo GitHub foi instalado em um repositório, você deve remover quaisquer webhooks desnecessários criados pelo seu aplicativo de legado OAuth. Se ambos os aplicativos estiverem instalados em um repositório, eles poderão duplicar a funcionalidade do usuário. Para remover os webhooks, Você pode ouvir [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) com a ação `repositórios_added` e [Excluir um webhook do repositório](/v3/repos/hooks/#delete-a-repository-webhook) naqueles repositórios criados pelo seu aplicativo OAuth. +Uma vez que seu aplicativo GitHub foi instalado em um repositório, você deve remover quaisquer webhooks desnecessários criados pelo seu aplicativo de legado OAuth. Se ambos os aplicativos estiverem instalados em um repositório, eles poderão duplicar a funcionalidade do usuário. Para remover os webhooks, Você pode ouvir [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) com a ação `repositórios_added` e [Excluir um webhook do repositório](/rest/reference/repos#delete-a-repository-webhook) naqueles repositórios criados pelo seu aplicativo OAuth. #### Incentive os usuários a revogar o acesso ao seu aplicativo OAuth diff --git a/translations/pt-BR/content/developers/apps/rate-limits-for-github-apps.md b/translations/pt-BR/content/developers/apps/rate-limits-for-github-apps.md index 013c1d782b..421c0438e1 100644 --- a/translations/pt-BR/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/rate-limits-for-github-apps.md @@ -34,8 +34,6 @@ Os {% data variables.product.prodname_github_app %}s que estão instalados em um ### Solicitações de usuário para servidor -{% data reusables.apps.deprecating_password_auth %} - {% data variables.product.prodname_github_app %}s também podem agir [em nome de um usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), fazendo solicitações de usuário para servidor. {% if currentVersion == "free-pro-team@latest" %} @@ -46,13 +44,13 @@ Aplicam-se diferentes limites de taxa de solicitação de usuário para servidor {% endif %} -As solicitações usuário para servidor são limitadas a 5.000 solicitações por hora e por usuário autenticado. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% if currentVersion == "github-ae@latest" %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user. +As solicitações usuário para servidor são limitadas a 5.000 solicitações por hora e por usuário autenticado. Todos os aplicativos OAuth autorizados por esse usuário, tokens de acesso pessoal pertencentes a esse usuário e solicitações autenticadas com o usuário {% if currentVersion == "github-ae@latest" %} token{% else %} usuário e senha{% endif %} compartilham a mesma cota de 5.000 solicitações por hora para esse usuário. {% if currentVersion == "free-pro-team@latest" %} #### Limites de taxa de usuário para servidor de {% data variables.product.prodname_ghe_cloud %} -Quando um usuário pertence a uma conta de {% data variables.product.prodname_ghe_cloud %}, as solicitações de usuário para servidor para recursos pertencentes à mesma conta de {% data variables.product.prodname_ghe_cloud %} são limitadas em 15.000 solicitações por hora e por usuário autenticado. Todos os aplicativos OAuth autorizados por esse usuário, tokens de acesso pessoal pertencentes a esse usuário, e pedidos autenticados com o nome de usuário e senha compartilham a mesma cota de 5.000 solicitações por hora para esse usuário. +Quando um usuário pertence a uma conta de {% data variables.product.prodname_ghe_cloud %}, as solicitações de usuário para servidor para recursos pertencentes à mesma conta de {% data variables.product.prodname_ghe_cloud %} são limitadas em 15.000 solicitações por hora e por usuário autenticado. Todos os aplicativos OAuth autorizados por esse usuário, tokens de acesso pessoal pertencentes a esse usuário e solicitações de {% data variables.product.prodname_ghe_cloud %} autenticadas com o usuário e senha desse usuário compartilham a mesma cota de 5.000 solicitações por hora para esse usuário. {% endif %} diff --git a/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md index 1e1b0080b9..931a044d2d 100644 --- a/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -25,7 +25,7 @@ Para renovar um token de acesso do usuário para servidor, você pode trocar o ` `POST https://github.com/login/oauth/access_token` -Esta solicitação de retorno de chamada enviará um novo token de acesso e um novo token de atualização. Essa solicitação de retorno de chamada é semelhante à solicitação do OAuth que usaria para trocar um `código` temporário por um token de acesso. Para obter mais informações, consulte "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" e "[Princípios básicos da autenticação](/v3/guides/basics-of-authentication/#providing-a-callback)". +Esta solicitação de retorno de chamada enviará um novo token de acesso e um novo token de atualização. Essa solicitação de retorno de chamada é semelhante à solicitação do OAuth que usaria para trocar um `código` temporário por um token de acesso. Para obter mais informações, consulte "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" e "[Princípios básicos da autenticação](/rest/guides/basics-of-authentication#providing-a-callback)". #### Parâmetros diff --git a/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md index da1c5b3d56..5b43679ee0 100644 --- a/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Scopes for OAuth Apps +title: Escopos para aplicativos OAuth intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/ @@ -11,19 +11,20 @@ versions: github-ae: '*' --- -When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. +Ao configurar um aplicativo OAuth no GitHub, os escopos solicitados são exibidos para o usuário no formulário de autorização. {% note %} -**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +**Observação:** Se você está criando um aplicativo no GitHub, você não precisa fornecer escopos na sua solicitação de autorização. Para obter mais informações sobre isso, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." +Se o seu +{% data variables.product.prodname_oauth_app %} não tem acesso a um navegador, como uma ferramenta CLI, você não precisa especificar um escopo para que os usuários efetuem a autenticação no seu aplicativo. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". {% endif %} -Check headers to see what OAuth scopes you have, and what the API action accepts: +Verifique os cabeçalhos para ver quais escopos do OAuth você tem e o que a ação da API aceita: ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I @@ -32,52 +33,51 @@ X-OAuth-Scopes: repo, user X-Accepted-OAuth-Scopes: user ``` -* `X-OAuth-Scopes` lists the scopes your token has authorized. -* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. +* `X-OAuth-Scopes` lista o escopo que seu token autorizou. +* `X-Accepted-OAuth-Scopes` lista os escopos verificados pela ação. -### Available scopes +### Escopos disponíveis -Name | Description ------|-----------| -**`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/v3/enterprise-admin).{% endif %} -**`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. - `repo:status`| Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. - `repo_deployment`| Grants access to [deployment statuses](/v3/repos/deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. - `public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. - `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} - `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/v3/code-scanning).{% endif %} -**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. - `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. - `read:repo_hook`| Grants read and ping access to hooks in public or private repositories. -**`admin:org`** | Fully manage the organization and its teams, projects, and memberships. - `write:org`| Read and write access to organization membership, organization projects, and team membership. - `read:org`| Read-only access to organization membership, organization projects, and team membership. -**`admin:public_key`** | Fully manage public keys. - `write:public_key`| Create, list, and view details for public keys. - `read:public_key`| List and view details for public keys. -**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user. -**`gist`** | Grants write access to gists. -**`notifications`** | Grants:
* read access to a user's notifications
* mark as read access to threads
* watch and unwatch access to a repository, and
* read, write, and delete access to thread subscriptions. -**`user`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. - `read:user`| Grants access to read a user's profile data. - `user:email`| Grants read access to a user's email addresses. - `user:follow`| Grants access to follow or unfollow other users. -**`delete_repo`** | Grants access to delete adminable repositories. -**`write:discussion`** | Allows read and write access for team discussions. - `read:discussion` | Allows read access for team discussions.{% if currentVersion == "free-pro-team@latest" %} -**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". -**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". -**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting packages](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} -**`admin:gpg_key`** | Fully manage GPG keys. - `write:gpg_key`| Create, list, and view details for GPG keys. - `read:gpg_key`| List and view details for GPG keys.{% if currentVersion == "free-pro-team@latest" %} -**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes, see https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token for details.{% endif %} +| Nome | Descrição | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| **`(sem escopo)`** | Concede acesso somente leitura a informações públicas (inclui informações de perfil do usuário público, informações de repositório público e gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| **`site_admin`** | Concede acesso de administrador aos pontos de extremidades da API de administração [{% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %} +| **`repo`** | Concede acesso total a repositórios privados e públicos. Isso inclui acesso de leitura/gravação ao código, status do commit, repositório e projetos da organização, convites, colaboradores, adição de associações de equipe, status de implantação e webhooks de repositórios para repositórios e organizações públicos e privados. Também concede capacidade para gerenciar projetos de usuário. | +|  `repo:status` | Concede acesso de leitura/gravação aos status do commit do repositório público e privado. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de compromisso de repositórios privados *sem* conceder acesso ao código. | +|  `repo_deployment` | Concede acesso aos [status de implantação](/rest/reference/repos#deployments) para repositórios públicos e privados. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso ao status de implantação, *sem* conceder acesso ao código. | +|  `public_repo` | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados com uma estrela. | +|  `repo:invite` | Concede habilidades de aceitar/recusar convites para colaborar em um repositório. Este escopo só é necessário para conceder a outros usuários ou servicos acesso a convites *sem* conceder acesso ao código.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +|  `security_events` | Concede acesso de leitura e escrita a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning).{% endif %} +| **`admin:repo_hook`** | Concede acesso de leitura, gravação e ping aos hooks do repositório em repositórios públicos e privados. O escopos do `repo` e `public_repo` concede acesso total aos repositórios, incluindo hooks de repositório. Use o escopo `admin:repo_hook` para limitar o acesso apenas a hooks de repositório. | +|  `write:repo_hook` | Concede acesso de leitura, escrita e ping para os hooks em repositórios públicos ou privados. | +|  `read:repo_hook` | Concede acesso de leitura e ping para hooks em repositórios públicos ou privados. | +| **`admin:org`** | Gerencia totalmente a organização e suas equipes, projetos e associações. | +|  `write:org` | Acesso de leitura e gravação à associação da organização, aos projetos da organização e à associação da equipe. | +|  `read:org` | Acesso somente leitura à associação da organização, aos projetos da organização e à associação da equipe. | +| **`admin:public_key`** | Gerenciar totalmente as chaves públicas. | +|  `write:public_key` | Criar, listar e visualizar informações das chaves públicas. | +|  `read:public_key` | Listar e visualizar informações para as chaves públicas. | +| **`admin:org_hook`** | Concede acesso de leitura, gravação, ping e e exclusão de hooks da organização. **Observação:** Os tokens do OAuth só serão capazes de realizar essas ações nos hooks da organização que foram criados pelo aplicativo OAuth. Os tokens de acesso pessoal só poderão realizar essas ações nos hooks da organização criados por um usuário. | +| **`gist`** | Concede acesso de gravação aos gists. | +| **`notificações`** | Condece:
* acesso de gravação a notificações de um usuário
* acesso para marcar como leitura nos threads
* acesso para inspecionar e não inspecionar um repositório e
* acesso de leitura, gravação e exclusão às assinaturas dos threads. | +| **`usuário`** | Concede acesso de leitura/gravação apenas às informações do perfil. Observe que este escopo inclui `user:email` e `user:follow`. | +|  `read:user` | Concede acesso para ler as informações do perfil de um usuário. | +|  `usuário:email` | Concede acesso de leitura aos endereços de e-mail de um usuário. | +|  `user:follow` | Concede acesso para seguir ou deixar de seguir outros usuários. | +| **`delete_repo`** | Concede acesso para excluir repositórios administráveis. | +| **`write:discussion`** | Permite acesso de leitura e gravação para discussões da equipe. | +|  `leia:discussion` | Permite acesso de leitura para as discussões de equipe.{% if currentVersion == "free-pro-team@latest" %} +| **`write:packages`** | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)". | +| **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Instalando um pacote](/github/managing-packages-with-github-packages/installing-a-package)". | +| **`delete:packages`** | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir pacotes](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} +| **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | +|  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | +|  `read:gpg_key` | Liste e visualize informações para as chaves GPG.{% if currentVersion == "free-pro-team@latest" %} +| **`fluxo de trabalho`** | Concede a capacidade de adicionar e atualizar arquivos do fluxo de trabalho do {% data variables.product.prodname_actions %}. Os arquivos do fluxo de trabalho podem ser confirmados sem este escopo se o mesmo arquivo (com o mesmo caminho e conteúdo) existir em outro branch no mesmo repositório. Os arquivos do fluxo de trabalho podem expor `GITHUB_TOKEN` que pode ter um conjunto diferente de escopos. Consulte https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token para detalhes.{% endif %} {% note %} -**Note:** Your OAuth App can request the scopes in the initial redirection. You -can specify multiple scopes by separating them with a space: +**Observação:** O seu aplicativo OAuth pode solicitar os escopos no redirecionamento inicial. Você pode especificar vários escopos separando-os com um espaço: https://github.com/login/oauth/authorize? client_id=...& @@ -85,31 +85,16 @@ can specify multiple scopes by separating them with a space: {% endnote %} -### Requested scopes and granted scopes +### Escopos solicitados e escopos concedidos -The `scope` attribute lists scopes attached to the token that were granted by -the user. Normally, these scopes will be identical to what you requested. -However, users can edit their scopes, effectively -granting your application less access than you originally requested. Also, users -can edit token scopes after the OAuth flow is completed. -You should be aware of this possibility and adjust your application's behavior -accordingly. +O atributo `escopo` lista os escopos adicionados ao token que foram concedido pelo usuário. Normalmente, estes escopos são idênticos aos que você solicitou. No entanto, os usuários podem editar seus escopos, concedendo, efetivamente, ao seu aplicativo um acesso menor do que você solicitou originalmente. Além disso, os usuários podem editar o escopo do token depois que o fluxo do OAuth for concluído. Você deve ter em mente esta possibilidade e ajustar o comportamento do seu aplicativo de acordo com isso. -It's important to handle error cases where a user chooses to grant you -less access than you originally requested. For example, applications can warn -or otherwise communicate with their users that they will see reduced -functionality or be unable to perform some actions. +É importante lidar com casos de erro em que um usuário escolhe conceder menos acesso do que solicitado originalmente. Por exemplo, os aplicativos podem alertar ou informar aos seus usuários que a funcionalidade será reduzida ou não serão capazes de realizar algumas ações. -Also, applications can always send users back through the flow again to get -additional permission, but don’t forget that users can always say no. +Além disso, os aplicativos sempre podem enviar os usuários de volta através do fluxo para obter permissão adicional, mas não se esqueça de que os usuários sempre podem dizer não. -Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which -provides tips on handling modifiable token scopes. +Confira o [Príncípios do guia de autenticação](/guides/basics-of-authentication/), que fornece dicas para lidar com escopos de token modificável. -### Normalized scopes +### Escopos normalizados -When requesting multiple scopes, the token is saved with a normalized list -of scopes, discarding those that are implicitly included by another requested -scope. For example, requesting `user,gist,user:email` will result in a -token with `user` and `gist` scopes only since the access granted with -`user:email` scope is included in the `user` scope. +Ao solicitar vários escopos, o token é salvo com uma lista normalizada de escopos, descartando aqueles que estão implicitamente incluídos pelo escopo solicitado. Por exemplo, a solicitação do usuário `user,gist,user:email` irá gerar apenas um token com escopos de `usuário` e `gist`, desde que o acesso concedido com o escopo `user:email` esteja incluído no escopo `usuário`. diff --git a/translations/pt-BR/content/developers/apps/setting-permissions-for-github-apps.md b/translations/pt-BR/content/developers/apps/setting-permissions-for-github-apps.md index bc5a25c1dd..5bee72c811 100644 --- a/translations/pt-BR/content/developers/apps/setting-permissions-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/setting-permissions-for-github-apps.md @@ -17,4 +17,4 @@ Ao criar um aplicativo GitHub, você pode selecionar as permissões de que preci Por padrão, os aplicativos GitHub têm acesso `somente leitura` aos pontos de extremidade dos metadados. Metadados é uma coleção de pontos de extremidade somente leitura que fornecem informações gerais sobre recursos que a instalação autorizada pode acessar. -{% data reusables.apps.metadata-permissions %} Para obter uma lista de pontos de extremidade dos metadados, consulte "[Permissões dos metadados](/v3/apps/permissions/#metadata-permissions)". +{% data reusables.apps.metadata-permissions %} Para obter uma lista de pontos de extremidade dos metadados, consulte "[Permissões dos metadados](/rest/reference/permissions-required-for-github-apps#metadata-permissions)". diff --git a/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index a8d4850586..ce366e1f24 100644 --- a/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -37,7 +37,7 @@ Você pode achar útil ter um entendimento básico do seguinte: * [Aplicativos do GitHub](/apps/about-apps) * [Webhooks](/webhooks) * [Linguagem de programação Ruby](https://www.ruby-lang.org/en/) -* [APIs REST](/v3) +* [APIs REST](/rest) * [Sinatra](http://sinatrarb.com/) Mas é possível acompanhar o processo em qualquer nível de experiência. Nós vamos nos conectar a informações de que você precisa ao longo do caminho! @@ -220,7 +220,7 @@ end #### Defina um gerenciador de encaminhamento -Um encaminhamento vazio está incluído no código do modelo. Este código gerencia todas as solicitações `POST` para o encaminhamento `/event_handler`. Você não vai escrever este manipulador de eventos neste início rápido, mas veja os outros [guias de início rápido](/apps/quickstart-guides/) para obter exemplos de como estender o aplicativo deste modelo. +Um encaminhamento vazio está incluído no código do modelo. Este código gerencia todas as solicitações `POST` para o encaminhamento `/event_handler`. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. ``` ruby post '/event_handler' do diff --git a/translations/pt-BR/content/developers/apps/using-content-attachments.md b/translations/pt-BR/content/developers/apps/using-content-attachments.md index cc45d98d60..bca23e3044 100644 --- a/translations/pt-BR/content/developers/apps/using-content-attachments.md +++ b/translations/pt-BR/content/developers/apps/using-content-attachments.md @@ -55,7 +55,7 @@ O fluxo de anexo de conteúdo mostra a relação entre a URL no problema ou pull } ``` -**Etapa 4.** O aplicativo usa o `content_reference` `id` para [Criar um anexo de conteúdo](/v3/apps/installations/#create-a-content-attachment) usando a API REST. Você também precisará do `id` da `instalação` para efetuar a autenticação como uma [instalação do aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. Você também precisará do `id` da `instalação` para efetuar a autenticação como uma [instalação do aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -116,7 +116,7 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -Para obter mais informações sobre `node_id`, consulte "[Usando IDs de nó globais](/v4/guides/using-global-node-ids/)". +For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ### Exemplo de uso de manifestos do Probot e do aplicativo GitHub diff --git a/translations/pt-BR/content/developers/apps/using-the-github-api-in-your-app.md b/translations/pt-BR/content/developers/apps/using-the-github-api-in-your-app.md index a234d366cb..068a82da12 100644 --- a/translations/pt-BR/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/pt-BR/content/developers/apps/using-the-github-api-in-your-app.md @@ -31,7 +31,7 @@ Você pode achar útil ter um entendimento básico do seguinte: * [Aplicativos do GitHub](/apps/about-apps) * [Webhooks](/webhooks) * [Linguagem de programação Ruby](https://www.ruby-lang.org/en/) -* [APIs REST](/v3) +* [APIs REST](/rest) * [Sinatra](http://sinatrarb.com/) Mas é possível acompanhar o processo em qualquer nível de experiência. Nós vamos nos conectar a informações de que você precisa ao longo do caminho! @@ -143,11 +143,11 @@ Antes que a etiqueta possa ser _adicionada_ em qualquer lugar, você precisará {% tip %} -**Dica**: Não seria ótimo se o aplicativo pudesse criar a etiqueta de forma programática? [Ele pode](/v3/issues/labels/#create-a-label)! Adicione o código para fazer isso por conta própria depois de concluir as etapas deste guia. +**Dica**: Não seria ótimo se o aplicativo pudesse criar a etiqueta de forma programática? [Ele pode](/rest/reference/issues#create-a-label)! Adicione o código para fazer isso por conta própria depois de concluir as etapas deste guia. {% endtip %} -Agora que o rótulo foi criado, você pode programar seu aplicativo para usar a API REST para [adicionar a etiqueta a qualquer problema recém-aberto](/v3/issues/labels/#add-labels-to-an-issue). +Agora que o rótulo foi criado, você pode programar seu aplicativo para usar a API REST para [adicionar a etiqueta a qualquer problema recém-aberto](/rest/reference/issues#add-labels-to-an-issue). ### Etapa 4. Adicionar gerenciamento de etiqueta diff --git a/translations/pt-BR/content/developers/github-marketplace/billing-customers.md b/translations/pt-BR/content/developers/github-marketplace/billing-customers.md index f9b728270c..47d8bec872 100644 --- a/translations/pt-BR/content/developers/github-marketplace/billing-customers.md +++ b/translations/pt-BR/content/developers/github-marketplace/billing-customers.md @@ -25,7 +25,7 @@ Os clientes devem ser capazes de executar as seguintes ações no site do seu ap Siga estas diretrizes para upgrades, downgrade e cancelamentos para manter um processo de cobrança claro e consistente. Para obter instruções mais detalhadas sobre os eventos de compra do {% data variables.product.prodname_marketplace %}, consulte "[Fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)". -Você pode usar a chave do `marketplace_purchase` do webhook `effective_date` para determinar quando a mudança de um plano irá ocorrer e sincronizar periodicamente as [Lista de contas para um plano](/v3/apps/marketplace/#list-accounts-for-a-plan). +Você pode usar a chave do `marketplace_purchase` do webhook `effective_date` para determinar quando a mudança de um plano irá ocorrer e sincronizar periodicamente as [Lista de contas para um plano](/rest/reference/apps#list-accounts-for-a-plan). #### Atualizações diff --git a/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index a135345273..de8682dc7a 100644 --- a/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -68,7 +68,7 @@ Depois que o cliente concluir a autorização, seu aplicativo receberá um token ### Etapa 4. Provisionar as contas dos clientes -Seu aplicativo deve fornecer uma conta de cliente para todas as novas compras. Usar o token de acesso que você recebeu para o cliente na [Etapa 3. Autorização](#step-3-authorization), chame o ponto de extremidade "[Lista de assinaturas para o usuário autenticado](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user)". A resposta incluirá a `conta` do cliente e mostrará se está em um teste grátis (`on_free_trial`). Use estas informações para concluir a configuração e o provisionamento. +Seu aplicativo deve fornecer uma conta de cliente para todas as novas compras. Usar o token de acesso que você recebeu para o cliente na [Etapa 3. Autorização](#step-3-authorization), chame o ponto de extremidade "[Lista de assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)". A resposta incluirá a `conta` do cliente e mostrará se está em um teste grátis (`on_free_trial`). Use estas informações para concluir a configuração e o provisionamento. {% data reusables.marketplace.marketplace-double-purchases %} @@ -76,6 +76,6 @@ Se a compra for para uma organização e por usuário, você poderá solicitar q É possível personalizar a forma como os integrantes da organização recebem acesso ao seu aplicativo. Aqui estão algumas sugestões: -**Preços fixos:** Se a compra for feita para uma organização que usa preços fixos, seu aplicativo poderá [obter todos os integrantes da organização](/v3/orgs/members/#list-organization-members) através da API e solicitar ao administrador da organização que escolha quais integrantes terão usuários pagos no lado do integrador. +**Preços fixos:** Se a compra for feita para uma organização que usa preços fixos, seu aplicativo poderá [obter todos os integrantes da organização](/rest/reference/orgs#list-organization-members) através da API e solicitar ao administrador da organização que escolha quais integrantes terão usuários pagos no lado do integrador. **Preços por unidade:** Um método de provisionamento de estações por unidade é permitir que os usuários ocupem uma estação enquanto iniciam a sessão do aplicativo. Quando o cliente atingir o limite de contagem da estação, seu aplicativo poderá alertar o usuário de que ele precisa fazer a atualização do plano de {% data variables.product.prodname_marketplace %}. diff --git a/translations/pt-BR/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/pt-BR/content/developers/github-marketplace/handling-plan-cancellations.md index 7c5488c9cc..46266ccadc 100644 --- a/translations/pt-BR/content/developers/github-marketplace/handling-plan-cancellations.md +++ b/translations/pt-BR/content/developers/github-marketplace/handling-plan-cancellations.md @@ -28,6 +28,6 @@ Quando um cliente cancela um plano grátis ou pago, seu aplicativo deve realizar {% note %} -**Obsevação:** Recomendamos usar a `effective_date` do webhook [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) para determinar quando ocorrerá a mudança do plano e sincronizar periodicamente [Listar as contas para um plano](/v3/apps/marketplace/#list-accounts-for-a-plan). Para obter mais informações sobre webhooks, consulte "[eventos de webhook do {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)". +**Obsevação:** Recomendamos usar a `effective_date` do webhook [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) para determinar quando ocorrerá a mudança do plano e sincronizar periodicamente [Listar as contas para um plano](/rest/reference/apps#list-accounts-for-a-plan). Para obter mais informações sobre webhooks, consulte "[eventos de webhook do {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)". {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/handling-plan-changes.md b/translations/pt-BR/content/developers/github-marketplace/handling-plan-changes.md index 31b7010bcf..3d67db4c80 100644 --- a/translations/pt-BR/content/developers/github-marketplace/handling-plan-changes.md +++ b/translations/pt-BR/content/developers/github-marketplace/handling-plan-changes.md @@ -54,7 +54,7 @@ https://www.github.com/marketplace//upgrade// Por exemplo, se você notar que um cliente está em um plano de 5 pessoas e precisa passar para um plano de 10 pessoas, você poderia exibir um botão na interface do usuário do seu aplicativo que diz "Aqui está como atualizar" ou exibir um banner com um link para a URL de atualização. A URL atualização leva o cliente para a página de confirmação de confirmação da atualização do seu plano da listagem. -Use o `LISTING_PLAN_NUMBER` para o plano que o cliente gostaria de comprar. Ao criar novos planos de preços, eles recebem um `LISTING_PLAN_NUMBER`, que é exclusivo para cada plano na sua listagem, e um `LISTING_PLAN_ID`, que é exclusivo para cada plano no {% data variables.product.prodname_marketplace %}. Você pode encontrar esses números ao [Listar planos](/v3/apps/marketplace/#list-plans), que identifica os seus planos de preços da listagem. Use o `LISTING_PLAN_ID` e "[Listar contas de um plano](/v3/apps/marketplace/#list-accounts-for-a-plan)" para obter o `CUSTOMER_ACCOUNT_ID`. +Use o `LISTING_PLAN_NUMBER` para o plano que o cliente gostaria de comprar. Ao criar novos planos de preços, eles recebem um `LISTING_PLAN_NUMBER`, que é exclusivo para cada plano na sua listagem, e um `LISTING_PLAN_ID`, que é exclusivo para cada plano no {% data variables.product.prodname_marketplace %}. Você pode encontrar esses números ao [Listar planos](/rest/reference/apps#list-plans), que identifica os seus planos de preços da listagem. Use o `LISTING_PLAN_ID` e "[Listar contas de um plano](/rest/reference/apps#list-accounts-for-a-plan)" para obter o `CUSTOMER_ACCOUNT_ID`. {% note %} diff --git a/translations/pt-BR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md b/translations/pt-BR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md index e82a47ae29..cfd6234e2a 100644 --- a/translations/pt-BR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md +++ b/translations/pt-BR/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- title: Pontos de extremidade de REST para a API do GitHub Marketplace -intro: 'To help manage your app on {% data variables.product.prodname_marketplace %}, use these {% data variables.product.prodname_marketplace %} API endpoints.' +intro: 'Para ajudar a gerenciar seu aplicativo em {% data variables.product.prodname_marketplace %}, use esses pontos de extremidade da API de {% data variables.product.prodname_marketplace %}.' redirect_from: - /apps/marketplace/github-marketplace-api-endpoints/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints/ @@ -13,10 +13,10 @@ versions: Aqui estão alguns pontos de extremidade úteis e disponíveis para listagens do Marketplace: -* [Listar planos](/v3/apps/marketplace/#list-plans) -* [Listar contas de um plano](/v3/apps/marketplace/#list-accounts-for-a-plan) -* [Obter um plano de assinatura para uma conta](/v3/apps/marketplace/#get-a-subscription-plan-for-an-account) -* [Listar assinaturas para o usuário autenticado](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [Listar planos](/rest/reference/apps#list-plans) +* [Listar contas de um plano](/rest/reference/apps#list-accounts-for-a-plan) +* [Obter um plano de assinatura para uma conta](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [Listar assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) Veja estas páginas para obter informações sobre como efetuar a autenticação ao usar a API do {% data variables.product.prodname_marketplace %}: @@ -25,6 +25,6 @@ Veja estas páginas para obter informações sobre como efetuar a autenticação {% note %} -**Observação:** [Os limites de taxa para a API REST](/v3/#rate-limiting) aplicam-se a todos os pontos de extremidade da API de {% data variables.product.prodname_marketplace %}. +**Observação:** [Os limites de taxa para a API REST](/rest#rate-limiting) aplicam-se a todos os pontos de extremidade da API de {% data variables.product.prodname_marketplace %}. {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md b/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md index cef915415f..643eff4c24 100644 --- a/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md @@ -37,7 +37,7 @@ Seus cenários de teste podem exigir a definição de planos de listagem que ofe ### Testar APIs -Para a maioria dos pontos de extremidade da API de do {% data variables.product.prodname_marketplace %}, nós também fornecemos pontos de extremidade de teste da API, que retornam dados falsos de código que você pode usar para testes. Para receber dados de teste, você deve especificar as URLs de teste, que incluem `/teste` no encaminhamento (por exemplo, `/user/marketplace_purchases/stubbed`). Para obter uma lista de pontos de extremidade compatíveis com essa abordagem de dados de teste, consulte [pontos de extremidade do {% data variables.product.prodname_marketplace %} ](/v3/apps/marketplace/#github-marketplace). . +Para a maioria dos pontos de extremidade da API de do {% data variables.product.prodname_marketplace %}, nós também fornecemos pontos de extremidade de teste da API, que retornam dados falsos de código que você pode usar para testes. Para receber dados de teste, você deve especificar as URLs de teste, que incluem `/teste` no encaminhamento (por exemplo, `/user/marketplace_purchases/stubbed`). Para obter uma lista de pontos de extremidade compatíveis com essa abordagem de dados de teste, consulte [pontos de extremidade do {% data variables.product.prodname_marketplace %} ](/rest/reference/apps#github-marketplace). . ### Testar webhooks diff --git a/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index d1f9946146..db521efa27 100644 --- a/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -31,15 +31,15 @@ Cada carga útil do webhook de `marketplace_purchase` terá as seguintes informa O objeto `marketplace_purchase` tem as seguintes chaves: -| Tecla | Tipo | Descrição | -| -------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `conta` | `objeto` | A conta da `organização` ou do `usuário` associada à assinatura. As contas da organização incluirão `organization_billing_email`, que é o endereço de e-mail administrativo da organização. Para encontrar endereços de e-mail para contas pessoais, você pode usar o ponto de extremidade [Obter o usuário autenticado](/v3/users/#get-the-authenticated-user). | -| `billing_cycle` | `string` | Pode ser `anual` ou `mensal`. Quando a o proprietário da `conta` tem um plano grátis do GitHub e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `billing_cycle` será `nulo`. | -| `unit_count` | `inteiro` | Número de unidades compradas. | -| `on_free_trial` | `boolean` | `verdadeiro` quando a `conta` está em um teste grátis. | -| `free_trial_ends_on` | `string` | A data em que o teste grátis expirará. | -| `next_billing_date` | `string` | A data em que começará o próximo ciclo de faturamento. Quando o proprietário da `conta` tem um plano grátis do GitHub.com e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `next_billing_date` será `nulo`. | -| `plano` | `objeto` | O plano comprado pelo usuário `` ou `organização`. | +| Tecla | Tipo | Descrição | +| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `conta` | `objeto` | A conta da `organização` ou do `usuário` associada à assinatura. As contas da organização incluirão `organization_billing_email`, que é o endereço de e-mail administrativo da organização. Para encontrar endereços de e-mail para contas pessoais, você pode usar o ponto de extremidade [Obter o usuário autenticado](/rest/reference/users#get-the-authenticated-user). | +| `billing_cycle` | `string` | Pode ser `anual` ou `mensal`. Quando a o proprietário da `conta` tem um plano grátis do GitHub e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `billing_cycle` será `nulo`. | +| `unit_count` | `inteiro` | Número de unidades compradas. | +| `on_free_trial` | `boolean` | `verdadeiro` quando a `conta` está em um teste grátis. | +| `free_trial_ends_on` | `string` | A data em que o teste grátis expirará. | +| `next_billing_date` | `string` | A data em que começará o próximo ciclo de faturamento. Quando o proprietário da `conta` tem um plano grátis do GitHub.com e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `next_billing_date` será `nulo`. | +| `plano` | `objeto` | O plano comprado pelo usuário `` ou `organização`. | O objeto `plano` tem as chaves a seguir: diff --git a/translations/pt-BR/content/developers/overview/about-githubs-apis.md b/translations/pt-BR/content/developers/overview/about-githubs-apis.md index 1de36116d7..a8a337a2a7 100644 --- a/translations/pt-BR/content/developers/overview/about-githubs-apis.md +++ b/translations/pt-BR/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -Existem duas versões estáveis da API do GitHub: a [API REST](/v3/) e a [API do GraphQL](/v4/). +Existem duas versões estáveis da API do GitHub: a [API REST](/rest) e a [API do GraphQL](/graphql). -Ao usar a API REST, incentivamos que você a [solicite a v3 por meio do cabeçalho `Aceitar`](/v3/media/#request-specific-version). +Ao usar a API REST, incentivamos que você a [solicite a v3 por meio do cabeçalho `Aceitar`](/rest/overview/media-types#request-specific-version). -Para obter informações sobre como usar a API do GraphQL, consulte a [documentação da v4](/v4/). +Para obter informações sobre como usar a API do GraphQL, consulte a [documentação da v4](/graphql). ## Versões obsoletas diff --git a/translations/pt-BR/content/developers/overview/github-developer-program.md b/translations/pt-BR/content/developers/overview/github-developer-program.md index b3e018a6b5..a2ee8874ca 100644 --- a/translations/pt-BR/content/developers/overview/github-developer-program.md +++ b/translations/pt-BR/content/developers/overview/github-developer-program.md @@ -19,7 +19,7 @@ Crie suas próprias ferramentas que integram-se perfeitamente ao lugar que você ## Assuma a empresa -[Obtain developer licenses](http://github.com/contact?form%5Bsubject%5D=Development+licenses) to build and test your application against {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}. +[Obtenha licenças de desenvolvedor](http://github.com/contact?form%5Bsubject%5D=Development+licenses) para criar e testar sua o seu aplicativo para {% data variables.product.prodname_ghe_server %} ou {% data variables.product.prodname_ghe_managed %}. ## Você tem uma integração que é compatível com o GitHub? diff --git a/translations/pt-BR/content/developers/overview/index.md b/translations/pt-BR/content/developers/overview/index.md index e1db964b98..12d0387cb4 100644 --- a/translations/pt-BR/content/developers/overview/index.md +++ b/translations/pt-BR/content/developers/overview/index.md @@ -1,6 +1,6 @@ --- title: Visão Geral -intro: 'Learn about {% data variables.product.prodname_dotcom %}''s APIs{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} and secure your deployments.{% else %}, secure your deployments, and join {% data variables.product.prodname_dotcom %}''s Developer Program.{% endif %}' +intro: 'Aprenda sobre as APIs de {% data variables.product.prodname_dotcom %}''{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} e proteja suas implantações.{% else %}, proteja as suas implantações e participe do Programa de Desenvolvedor de {% data variables.product.prodname_dotcom %}.{% endif %}' versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md index f51e83ca29..3985047aa7 100644 --- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md +++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md @@ -86,6 +86,40 @@ Execute o procedimento `ssh-keygen` no seu servidor e lembre-se do local onde vo +##### Usar vários repositórios em um servidor + +Se você usar vários repositórios em um servidor, você deverá gerar um par de chaves dedicado para cada um. Você não pode reutilizar uma chave de implantação para vários repositórios. + +No arquivo de configuração do SSH do servidor (geralmente `~/.ssh/config`), adicione uma entrada de pseudônimo para cada repositório. Por exemplo: + + + +```bash +Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0 + Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %} + IdentityFile=/home/user/.ssh/repo-0_deploy_key + +Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1 + Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %} + IdentityFile=/home/user/.ssh/repo-1_deploy_key +``` + + +* `Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}meu-GHE-hostname.com{% endif %}-repo-0` - Pseudônimo do repositório. +* `Nome de host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}meu-GHE-hostname.com{% endif %}` - Configura o nome de host a ser usado com o pseudônimo. +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Atribui uma chave privada ao pseudônimo. + +Em seguida, você pode usar o apelido do host para interagir com o repositório usando SSH, que usará a chave de deploy exclusiva atribuída a esse pseudônimo. Por exemplo: + + + +```bash +$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git +``` + + + + ### Usuários máquina Se o seu servidor precisar acessar vários repositórios, você poderá criar uma conta nova no {% data variables.product.product_name %} e anexar uma chave SSH que será usada exclusivamente para automação. Como esta conta do {% data variables.product.product_name %} não será usada por uma pessoa, ela será denominada _usuário máquina_. É possível adicionar o usuário máquina como [colaborador][collaborator] em um repositório pessoal (concedendo acesso de leitura e gravação), como [colaborador externo][outside-collaborator] em um repositório da organização (concedendo leitura, acesso gravação, ou administrador) ou como uma [equipe][team], com acesso aos repositórios que precisa automatizar (concedendo as permissões da equipe). diff --git a/translations/pt-BR/content/developers/overview/secret-scanning.md b/translations/pt-BR/content/developers/overview/secret-scanning.md index 04f6e9d14e..1017a9386b 100644 --- a/translations/pt-BR/content/developers/overview/secret-scanning.md +++ b/translations/pt-BR/content/developers/overview/secret-scanning.md @@ -79,7 +79,7 @@ Content-Length: 0123 ] ``` -O corpo da mensagem é um array do JSON que contém um ou mais objetos com o seguinte conteúdo. Quando várias correspondências forem encontradas, o {% data variables.product.prodname_dotcom %} pode enviar uma única mensagem com mais de uma correspondência secreta. +O corpo da mensagem é um array do JSON que contém um ou mais objetos com o seguinte conteúdo. Quando várias correspondências forem encontradas, o {% data variables.product.prodname_dotcom %} pode enviar uma única mensagem com mais de uma correspondência secreta. Seu ponto de extremidade deve ser capaz de lidar com solicitações com um grande número de correspondências sem exceder o tempo. * **Token**: O valor da correspondência secreta. * **Tipo**: O nome único que você forneceu para identificar sua expressão regular. diff --git a/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md b/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md index 8e9ba94714..a0d1bdd15c 100644 --- a/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md +++ b/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md @@ -22,7 +22,7 @@ Confira o [Guia das Dicas Técnicas de Steve Friedl][tech-tips] para obter uma e Certifique-se de que sua própria chave SSH esteja configurada e funcionando. Você pode usar [nosso guia sobre a geração de chaves SSH][generating-keys], caso ainda não tenha feito isso. -You can test that your local key works by entering `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` in the terminal: +Você pode testar se a chave local funciona, inserindo `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}nome de host{% else %}github. om{% endif %}` no terminal: ```shell $ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %} @@ -48,7 +48,7 @@ Começamos bem. Vamos configurar SSH para permitir o encaminhamento de agentes p ### Testar o encaminhamento de agente SSH -To test that agent forwarding is working with your server, you can SSH into your server and run `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` once more. Se tudo correr bem, você retornará à mesma mensagem apresentada quando você fez localmente. +Para testar se o encaminhamento de agente está funcionando com seu servidor, você pode ingressar por SSH no servidor e executar `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}nome de host{% else %}github.com{% endif %}` mais uma vez. Se tudo correr bem, você retornará à mesma mensagem apresentada quando você fez localmente. Se você não tiver certeza se sua chave local está sendo usada, você também poderá inspecionar a variável `SSH_AUTH_SOCK` no seu servidor: diff --git a/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md index 5287299c61..3123eb3183 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md @@ -31,4 +31,4 @@ See "[Webhook event payloads](/webhooks/event-payloads)" for the list of availab For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. [org-hooks]: /rest/reference/orgs#webhooks/ -[repo-hooks]: /v3/repos/hooks/ +[repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md index 1e5268af0a..48fd64cce1 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md @@ -65,5 +65,5 @@ Ao terminar, clique em **Adicionar webhook**. Ufa! Agora que você criou o webho Para configurar um webhook para todos os eventos, use o caractere curinga (`*`) para especificar os eventos de webhook. Ao adicionar o evento curinga, substituiremos todos os eventos existentes que você tenha configurado pelo evento curinga e enviaremos todas as cargas para os eventos compatíveis. Você também obterá automaticamente todos os novos eventos que possamos adicionar no futuro. [webhooks-overview]: /webhooks/ -[webhook-api]: /v3/repos/hooks/ +[webhook-api]: /rest/reference/repos#hooks [hooks-api]: /webhooks/#events diff --git a/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md b/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md index de0cd07b78..188da206f7 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md @@ -40,7 +40,7 @@ Os objetos de evento retornados dos pontos de extremidade da API de eventos têm #### Exemplo de objeto de evento WatchEvent -Este exemplo mostra o formato da resposta do [WatchEvent](#watchevent) ao usar a [API de eventos](/v3/activity/events). +Este exemplo mostra o formato da resposta do [WatchEvent](#watchevent) ao usar a [API de eventos](/rest/reference/activity#events). ``` Status: 200 OK @@ -198,22 +198,22 @@ Este evento retorna um objeto de `carga` vazio. {% data reusables.webhooks.events_api_payload %} -| Tecla | Tipo | Descrição | -| -------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `push_id` | `inteiro` | Identificador único para o push. | -| `size` | `inteiro` | O número de commits no push. | -| `distinct_size` | `inteiro` | O número de commits distintos no push. | -| `ref` | `string` | O [`git ref`](/v3/git/refs/) completo que foi carregado. Exemplo: `refs/heads/master`. | -| `head` | `string` | O SHA do último commit no `ref` após o push. | -| `antes` | `string` | O SHA do último commit em `ref` antes do push. | -| `commits` | `array` | Um array de objetos de commit, que descreve os commits carregados. (O array inclui um máximo de 20 commits. Se necessário, você poderá usar a [API de commits](/v3/repos/commits/) para recuperar commits adicionais. Este limite é aplicado apenas aos eventos da linha do tempo e não é aplicado às entregas do webhook.) | -| `commits[][sha]` | `string` | O SHA do commit. | -| `commits[][message]` | `string` | A mensagem do commit. | -| `commits[][author]` | `objeto` | O autor do git do commit. | -| `commits[][author][name]` | `string` | O nome do autor do git. | -| `commits[][author][email]` | `string` | O endereço de e-mail do autor do git. | -| `commits[][url]` | `url` | URL que aponta para o recurso de commit de API. | -| `commits[][distinct]` | `boolean` | Se este compromisso é diferente de qualquer outro que tenha sido carregado anteriormente. | +| Tecla | Tipo | Descrição | +| -------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `push_id` | `inteiro` | Identificador único para o push. | +| `size` | `inteiro` | O número de commits no push. | +| `distinct_size` | `inteiro` | O número de commits distintos no push. | +| `ref` | `string` | O [`git ref completo`](/rest/reference/git#refs) que foi empurrado. Exemplo: `refs/heads/master`. | +| `head` | `string` | O SHA do último commit no `ref` após o push. | +| `antes` | `string` | O SHA do último commit em `ref` antes do push. | +| `commits` | `array` | Um array de objetos de commit, que descreve os commits carregados. (O array inclui um máximo de 20 commits. Se necessário, você pode usar a [API de Commits](/rest/reference/repos#commits) para obter commits adicionais. Este limite é aplicado apenas aos eventos da linha do tempo e não é aplicado às entregas do webhook.) | +| `commits[][sha]` | `string` | O SHA do commit. | +| `commits[][message]` | `string` | A mensagem do commit. | +| `commits[][author]` | `objeto` | O autor do git do commit. | +| `commits[][author][name]` | `string` | O nome do autor do git. | +| `commits[][author][email]` | `string` | O endereço de e-mail do autor do git. | +| `commits[][url]` | `url` | URL que aponta para o recurso de commit de API. | +| `commits[][distinct]` | `boolean` | Se este compromisso é diferente de qualquer outro que tenha sido carregado anteriormente. | ### ReleaseEvent diff --git a/translations/pt-BR/content/developers/webhooks-and-events/issue-event-types.md b/translations/pt-BR/content/developers/webhooks-and-events/issue-event-types.md index 372ceef49b..e58bb7afec 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/issue-event-types.md @@ -10,7 +10,7 @@ versions: --- -Eventos de problemas são acionados pela atividade em problemas e pull requests e estão disponíveis na [API de eventos de problemas](/v3/issues/events) e na [API de eventos da linha do tempo](/v3/issues/timeline). Cada tipo de evento especifica se o evento está disponível nos eventos do problema ou na API de eventos da linha do tempo. +Eventos de problemas são acionados pela atividade em problemas e pull requests e estão disponíveis na [API de eventos de problemas](/rest/reference/issues#events) e na [API de eventos da linha do tempo](/rest/reference/issues#timeline). Cada tipo de evento especifica se o evento está disponível nos eventos do problema ou na API de eventos da linha do tempo. A API REST do GitHub considera que todo pull request é um problema, mas nem todos os problemas são pull request. Por este motivo, os eventos de problemas e os pontos de extremidade dos eventos da linha do tempo podem retornar problemas e pull requests na resposta. Pull requests têm uma propriedade `pull_request` no objeto `problema`. Como os pull requests são problemas, os números de problemas e pull requests não se sobrepõem em um repositório. Por exemplo, se você abrir seu primeiro problema em um repositório, o número será 1. Se você abrir um pull request, o número será 2. Cada tipo de evento especifica se o evento ocorre em um pull request, em um problema ou em ambos. @@ -129,7 +129,7 @@ Um comentário foi adicionado ao problema ou pull request. | `html_url` | `string` | A URL de HTML do comentário do problema. | | `issue_url` | `string` | A URL de HTML do problema. | | `id` | `inteiro` | O identificador exclusivo do evento. | -| `node_id` | `string` | O [ID de nó global](/v4/guides/using-global-node-ids) do evento. | +| `node_id` | `string` | O [Global Node ID](/graphql/guides/using-global-node-ids) do evento. | | `usuário` | `objeto` | A pessoa que comentou sobre o problema. | | `created_at` | `string` | A marca de tempo que indica quando o comentário foi adicionado. | | `updated_at` | `string` | A marca de tempo que indica quando o comentário foi atualizado ou criado, se o comentário nunca for atualizado. | @@ -152,19 +152,19 @@ Um commit foi adicionado ao branch `HEAD` do pull request. {% data reusables.issue-events.timeline_events_object_properties %} -| Nome | Tipo | Descrição | -| ------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sha` | `string` | O SHA do commit no pull request. | -| `node_id` | `string` | O [ID de nó global](/v4/guides/using-global-node-ids) do evento. | -| `url` | `string` | A URL da API REST para recuperar o commit. | -| `html_url` | `string` | A URL de HTML do commit. | -| `autor` | `objeto` | A pessoa que autorizou o commit. | -| `committer` | `objeto` | A pessoa que confirmou o commit em nome do autor. | -| `árvore` | `objeto` | A árvore Git do commit. | -| `mensagem` | `string` | A mensagem do commit. | -| `principais` | `array de objetos` | Uma lista de commits principais. | -| `verificação` | `objeto` | O resultado de verificação da assinatura do commit. Para obter mais informações, consulte "[Objeto verificação de assinatura](/v3/git/commits/#signature-verification-object)". | -| `event` | `string` | O valor do evento é `"commited"`. | +| Nome | Tipo | Descrição | +| ------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sha` | `string` | O SHA do commit no pull request. | +| `node_id` | `string` | O [Global Node ID](/graphql/guides/using-global-node-ids) do evento. | +| `url` | `string` | A URL da API REST para recuperar o commit. | +| `html_url` | `string` | A URL de HTML do commit. | +| `autor` | `objeto` | A pessoa que autorizou o commit. | +| `committer` | `objeto` | A pessoa que confirmou o commit em nome do autor. | +| `árvore` | `objeto` | A árvore Git do commit. | +| `mensagem` | `string` | A mensagem do commit. | +| `principais` | `array de objetos` | Uma lista de commits principais. | +| `verificação` | `objeto` | O resultado de verificação da assinatura do commit. Para obter mais informações, consulte "[Objeto verificação de assinatura](/rest/reference/git#signature-verification-object)". | +| `event` | `string` | O valor do evento é `"commited"`. | ### conectado @@ -632,7 +632,7 @@ O pull request foi revisado. | Nome | Tipo | Descrição | | -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `inteiro` | O identificador exclusivo do evento. | -| `node_id` | `string` | O [ID de nó global](/v4/guides/using-global-node-ids) do evento. | +| `node_id` | `string` | O [Global Node ID](/graphql/guides/using-global-node-ids) do evento. | | `usuário` | `objeto` | A pessoa que comentou sobre o problema. | | `texto` | `string` | O texto do resumo da revisão. | | `commit_id` | `string` | O SHA do último commit no pull request no momento da revisão. | diff --git a/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md index 3bac571670..ba8cd0bb52 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -35,7 +35,7 @@ $ export SECRET_TOKEN=your_token ### Validar cargas do GitHub -Quando seu token secreto está definido, {% data variables.product.product_name %} o utiliza para criar uma assinatura de hash com cada carga. This hash signature is included with the headers of each request as {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature`{% endif %}. +Quando seu token secreto está definido, {% data variables.product.product_name %} o utiliza para criar uma assinatura de hash com cada carga. Esta assinatura hash está incluída com os cabeçalhos de cada solicitação como {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" ou currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature`{% endif %}. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} @@ -81,7 +81,7 @@ end{% endif %} A sua linguagem e implementações do servidor podem ser diferentes deste código de exemplo. No entanto, há uma série de aspectos muito importantes a destacar: -* No matter which implementation you use, the hash signature starts with {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or "github-ae@latest" %}`sha256=`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`sha1=`{% endif %}, using the key of your secret token and your payload body. +* Não importa qual implementação você usar, a assinatura hash começa com {% if currentVersion == "free-pro-team@latest" ou currentVersion ver_gt "enterprise-server@2. 2" or "github-ae@latest" %}`sha256=`{% elsif currentVersion ver_lt "enterprise-server@2. 3" %}`sha1=`{% endif %}, usando a chave do seu token secreto e o seu texto de carga. * Não **se recomenda** usar um operador simples de`==`. Um método como [`secure_compare`][secure_compare] executa uma comparação de strings "tempo constante", o que ajuda a mitigar certos ataques de tempo contra operadores de igualdade regular. diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md index dee4a96791..f48511fa62 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -1,6 +1,6 @@ --- -title: Eventos de webhook e cargas -intro: 'Para cada evento de webhook, você pode revisar quando o evento ocorrer, uma carga de exemplo, bem como as descrições sobre os parâmetros do objeto da carga.' +title: Webhook events and payloads +intro: 'For each webhook event, you can review when the event occurs, an example payload, and descriptions about the payload object parameters.' product: '{% data reusables.gated-features.enterprise_account_webhooks %}' redirect_from: - /early-access/integrations/webhooks/ @@ -19,44 +19,44 @@ versions: {% data reusables.webhooks.webhooks_intro %} -Você pode criar webhooks que assinam os eventos listados nesta página. Cada evento de webhook inclui uma descrição das propriedades do webhook e uma carga de exemplo. Para obter mais informações, consulte "[Criar webhooks](/webhooks/creating/)." +You can create webhooks that subscribe to the events listed on this page. Each webhook event includes a description of the webhook properties and an example payload. For more information, see "[Creating webhooks](/webhooks/creating/)." -### Propriedades comuns do objeto da carga do webhook +### Webhook payload object common properties -Cada carga do evento do webhook também contém propriedades únicas para o evento. Você pode encontrar as propriedades únicas nas seções individuais de tipos de evento. +Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections. -| Tecla | Tipo | Descrição | -| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A maioria das cargas de webhook contém uma ação `` propriedade que contém a atividade específica que acionou o evento. | -{% data reusables.webhooks.sender_desc %} Esta propriedade está incluída em todas as cargas do webhook. -{% data reusables.webhooks.repo_desc %} As cargas do webhook contêm a propriedade `repository` quando ocorre o evento a partir da atividade em um repositório. +Key | Type | Description +----|------|------------- +`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event. +{% data reusables.webhooks.sender_desc %} This property is included in every webhook payload. +{% data reusables.webhooks.repo_desc %} Webhook payloads contain the `repository` property when the event occurs from activity in a repository. {% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} Para obter mais informações, consulte "[Criar um {% data variables.product.prodname_github_app %}](/apps/building-github-apps/). +{% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)." -As propriedades únicas para um evento de webhook são as mesmas que você encontrará na propriedade `carga` ao usar a [API de eventos](/v3/activity/events/). Uma exceção é o evento de [`push`](#push). As propriedades únicas da carga do webhook do evento `push` e a propriedade `carga` na API de eventos são diferentes. A carga do webhook contém informações mais detalhadas. +The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. {% tip %} -**Observação:** As cargas são limitados a 25 MB. Se o seu evento gerar uma carga maior, um webhook não será disparado. Isso pode acontecer, por exemplo, em um evento `criar`, caso muitos branches ou tags sejam carregados de uma só vez. Sugerimos monitorar o tamanho da sua carga para garantir a entrega. +**Note:** Payloads are capped at 25 MB. If your event generates a larger payload, a webhook will not be fired. This may happen, for example, on a `create` event if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. {% endtip %} -#### Cabeçalhos de entrega +#### Delivery headers -As cargas de HTTP POST que são entregues no ponto de extremidade da URL configurado do seu webhook conterão vários cabeçalhos especiais: +HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: -| Header | Descrição | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | Nome do evento que ativou a entrega. | -| `X-GitHub-Delivery` | A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `X-GitHub-Enterprise-Version` | A versão da instância do {% data variables.product.prodname_ghe_server %} que enviou a carga do HTTP POST. | -| `X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} -| `X-Hub-Signature` | Este cabeçalho é enviado se o webhook for configurado com um [`secreto`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `X-Hub-Signature-256` | Este cabeçalho é enviado se o webhook for configurado com um [`secreto`](/v3/repos/hooks/#create-hook-config-params). Este é o resumo hexadecimal HMAC do texto da solicitação e é gerado usando a função hash SHA-256 e a `segredo` como a `chave` HMAC.{% endif %} +Header | Description +-------|-------------| +`X-GitHub-Event`| Name of the event that triggered the delivery. +`X-GitHub-Delivery`| A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +`X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. +`X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} +`X-Hub-Signature`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`X-Hub-Signature-256`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} -Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hookshot/`. +Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. -#### Exemplo de entrega +#### Example delivery ```shell > POST /payload HTTP/1.1 @@ -103,13 +103,13 @@ Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hooks {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} -#### Disponibilidade +#### Availability -- Os webhooks de repositório só recebem cargas para os tipos de evento `criados` e `concluídos` em um repositório -- Os webhooks da organização só recebem cargas para os tipos de eventos `criados` e `concluídos` nos repositórios -- Os {% data variables.product.prodname_github_app %}s com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `requested_action`. As cargas do tipo de evento `solicitadas` e `requested_action` são enviadas apenas para o {% data variables.product.prodname_github_app %} que está sendo solicitado. Os {% data variables.product.prodname_github_app %}s com `checks:write` são automaticamente inscritos neste evento webhook. +- Repository webhooks only receive payloads for the `created` and `completed` event types in a repository +- Organization webhooks only receive payloads for the `created` and `completed` event types in repositories +- {% data variables.product.prodname_github_app %}s with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_app %}s with the `checks:write` are automatically subscribed to this webhook event. -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.check_run_properties %} {% data reusables.webhooks.repo_desc %} @@ -117,7 +117,7 @@ Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hooks {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.check_run.created }} @@ -127,13 +127,13 @@ Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hooks {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} -#### Disponibilidade +#### Availability -- Os webhooks de repositório só recebem cargas para os tipos de evento `concluídos` em um repositório -- Os webhooks da organização só recebem cargas para os tipos de eventos `concluídos` nos repositórios -- Os {% data variables.product.prodname_github_app %}s com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `ressolicitados.`. As cargas de evento `solicitadas` e `ressolicitadas` são enviadas apenas para {% data variables.product.prodname_github_app %} que está sendo solicitado. Os {% data variables.product.prodname_github_app %}s com `checks:write` são automaticamente inscritos neste evento webhook. +- Repository webhooks only receive payloads for the `completed` event types in a repository +- Organization webhooks only receive payloads for the `completed` event types in repositories +- {% data variables.product.prodname_github_app %}s with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_app %}s with the `checks:write` are automatically subscribed to this webhook event. -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.check_suite_properties %} {% data reusables.webhooks.repo_desc %} @@ -141,30 +141,30 @@ Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hooks {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.check_suite.completed }} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### code_scanning_alert -Os {% data variables.product.prodname_github_app %}s com a permissão `security_events` +{% data reusables.webhooks.code_scanning_alert_event_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de `conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `security_events :read` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.code_scanning_alert_event_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -remetente`| objeto` | Se a de ação ` for reopened_by_user` ou `closed_by_user`, o objeto `remetente` será o usuário que ativou o evento. O objeto `remetente` está vazio para todas as outras ações. +`sender` | `object` | If the `action` is `reopened_by_user` or `closed_by_user`, the `sender` object will be the user that triggered the event. The `sender` object is empty for all other actions. -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }} @@ -172,13 +172,13 @@ Os {% data variables.product.prodname_github_app %}s com a permissão `security_ {% data reusables.webhooks.commit_comment_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.commit_comment_properties %} {% data reusables.webhooks.repo_desc %} @@ -186,7 +186,7 @@ Os {% data variables.product.prodname_github_app %}s com a permissão `security_ {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.commit_comment.created }} {% endif %} @@ -195,11 +195,11 @@ Os {% data variables.product.prodname_github_app %}s com a permissão `security_ {% data reusables.webhooks.content_reference_short_desc %} -Os eventos de webhook são acionados com base na especificidade do domínio que você registra. Por exemplo, se você registrar um subdomínio (`https://subdomain.example.com`), apenas as URLs para o subdomínio irão ativar este evento. Se você registrar um domínio (`https://example.com`), as URLs para domínio e todos os subdomínios irão ativar este evento. Consulte "[Criar um anexo de conteúdo](/v3/apps/installations/#create-a-content-attachment)" para criar um novo anexo de conteúdo. +Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. -Apenas os {% data variables.product.prodname_github_app %}s podem receber este evento. Os {% data variables.product.prodname_github_app %}s devem ter a permissão de `content_reference` `gravação` para assinar este evento. +Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event. -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.content_reference.created }} @@ -209,17 +209,17 @@ Apenas os {% data variables.product.prodname_github_app %}s podem receber este e {% note %} -**Observação:** Você não receberá um webhook para este evento ao fazer push de mais de três tags de uma vez. +**Note:** You will not receive a webhook for this event when you push more than three tags at once. {% endnote %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.create_properties %} {% data reusables.webhooks.repo_desc %} @@ -227,7 +227,7 @@ Apenas os {% data variables.product.prodname_github_app %}s podem receber este e {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.create }} @@ -237,17 +237,17 @@ Apenas os {% data variables.product.prodname_github_app %}s podem receber este e {% note %} -**Observação:** Você não receberá um webhook para este evento ao excluir mais de três tags de uma só vez. +**Note:** You will not receive a webhook for this event when you delete more than three tags at once. {% endnote %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.delete_properties %} {% data reusables.webhooks.repo_desc %} @@ -255,7 +255,7 @@ Apenas os {% data variables.product.prodname_github_app %}s podem receber este e {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.delete }} @@ -263,73 +263,73 @@ Apenas os {% data variables.product.prodname_github_app %}s podem receber este e {% data reusables.webhooks.deploy_key_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização +- Repository webhooks +- Organization webhooks -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.deploy_key_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.deploy_key.created }} -### implantação +### deployment {% data reusables.webhooks.deployment_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de `implantação` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `deployments` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} -| `implantação` | `objeto` | The [implantação](/rest/reference/repos#list-deployments). | +Key | Type | Description +----|------|-------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +`action` |`string` | The action performed. Can be `created`.{% endif %} +`deployment` |`object` | The [deployment](/rest/reference/repos#list-deployments). {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.deployment }} -### implantação_status +### deployment_status {% data reusables.webhooks.deployment_status_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de `implantação` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `deployments` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} -| `implantação_status` | `objeto` | O [estado de implantação](/rest/reference/repos#list-deployment-statuses). | -| `deployment_status["state"]` | `string` | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`. | -| `deployment_status["target_url"]` | `string` | O link opcional adicionado ao status. | -| `deployment_status["description"]` | `string` | A descrição opcional legível para pessoas adicionada ao status. | -| `implantação` | `objeto` | A [implantação](/rest/reference/repos#list-deployments) à qual este status está associado. | +Key | Type | Description +----|------|-------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +`action` |`string` | The action performed. Can be `created`.{% endif %} +`deployment_status` |`object` | The [deployment status](/rest/reference/repos#list-deployment-statuses). +`deployment_status["state"]` |`string` | The new state. Can be `pending`, `success`, `failure`, or `error`. +`deployment_status["target_url"]` |`string` | The optional link added to the status. +`deployment_status["description"]`|`string` | The optional human-readable description added to the status. +`deployment` |`object` | The [deployment](/rest/reference/repos#list-deployments) that this status is associated with. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.deployment_status }} @@ -339,33 +339,33 @@ Apenas os {% data variables.product.prodname_github_app %}s podem receber este e {% data reusables.webhooks.enterprise_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)." +- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------ | -------- | ------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `anonymous_access_enabled` ou `anonymous_access_disabled`. | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `anonymous_access_enabled` or `anonymous_access_disabled`. -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }} {% endif %} -### bifurcação +### fork {% data reusables.webhooks.fork_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.fork_properties %} {% data reusables.webhooks.repo_desc %} @@ -373,28 +373,28 @@ Apenas os {% data variables.product.prodname_github_app %}s podem receber este e {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.fork }} ### github_app_authorization -Este evento ocorre quando alguém revoga a autorização de um {% data variables.product.prodname_github_app %}. Um {% data variables.product.prodname_github_app %} recebe este webhook por padrão e não pode cancelar a assinatura deste evento. +When someone revokes their authorization of a {% data variables.product.prodname_github_app %}, this event occurs. A {% data variables.product.prodname_github_app %} receives this webhook by default and cannot unsubscribe from this event. -{% data reusables.webhooks.authorization_event %} Para obter informações sobre solicitações de usuário para servidor, que exigem autorização do {% data variables.product.prodname_github_app %}, consulte "[Identificando e autorizando usuários para os {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +{% data reusables.webhooks.authorization_event %} For details about user-to-server requests, which require {% data variables.product.prodname_github_app %} authorization, see "[Identifying and authorizing users for {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -#### Disponibilidade +#### Availability - {% data variables.product.prodname_github_app %}s -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------ | -------- | -------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `revogada`. | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `revoked`. {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }} @@ -402,13 +402,13 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables {% data reusables.webhooks.gollum_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.gollum_properties %} {% data reusables.webhooks.repo_desc %} @@ -416,39 +416,39 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.gollum }} -### instalação +### installation {% data reusables.webhooks.installation_short_desc %} {% note %} -**Observação:** Você não receberá um webhook para este evento ao excluir mais de três tags de uma só vez. +**Note:** This event replaces the deprecated `integration_installation` event. {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} {% note %} -**Observação:** {% data reusables.pre-release-program.suspend-installation-beta %} Para obter mais informações, consulte "[Suspender uma instalação do {% data variables.product.prodname_github_app %}](/apps/managing-github-apps/suspending-a-github-app-installation/)". +**Note:** {% data reusables.pre-release-program.suspend-installation-beta %} For more information, see "[Suspending a {% data variables.product.prodname_github_app %} installation](/apps/managing-github-apps/suspending-a-github-app-installation/)." {% endnote %} {% endif %} -#### Disponibilidade +#### Availability - {% data variables.product.prodname_github_app %}s -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.installation_properties %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.installation.deleted }} @@ -458,21 +458,21 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables {% note %} -`repository` quando ocorre o evento a partir da atividade em um repositório. +**Note:** This event replaces the deprecated `integration_installation_repositories` event. {% endnote %} -#### Disponibilidade +#### Availability - {% data variables.product.prodname_github_app %}s -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.installation_repositories_properties %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.installation_repositories.added }} @@ -480,266 +480,177 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables {% data reusables.webhooks.issue_comment_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão problemas` - +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `issues` permission -

Objeto da carga do webhook

+#### Webhook payload object -

{% data reusables.webhooks.issue_comment_webhook_properties %}

- -

-

- -

{% data reusables.webhooks.issue_comment_properties %}

- -

-

- -

{% data reusables.webhooks.repo_desc %}

- -

-

- -

{% data reusables.webhooks.org_desc %}

- -

-

- -

{% data reusables.webhooks.app_desc %}

- -

-

- -

{% data reusables.webhooks.sender_desc %}

- -

Exemplo de carga de webhook

- -

{{ webhookPayloadsForCurrentVersion.issue_comment.created }}

- -

Problemas

- -

{% data reusables.webhooks.issues_short_desc %}

- -

Disponibilidade

- -
    -
  • Webhooks do repositório
    • -
  • Webhooks da organização
    • -
  • Os {% data variables.product.prodname_github_app %}s com a permissão `problemas`
    • -
- -

Objeto da carga do webhook

- -

{% data reusables.webhooks.issue_webhook_properties %}

- -

-

- -

{% data reusables.webhooks.issue_properties %}

- -

-

- -

{% data reusables.webhooks.repo_desc %}

- -

-

- -

{% data reusables.webhooks.org_desc %}

- -

-

- -

{% data reusables.webhooks.app_desc %}

- -

-

- -

{% data reusables.webhooks.sender_desc %}

- -

Exemplo de carga de webhook quando alguém editar um problema

- -

{{ webhookPayloadsForCurrentVersion.issues.edited }}

- -

etiqueta

- -

{% data reusables.webhooks.label_short_desc %}

- -

Disponibilidade

- -
    -
  • Webhooks do repositório
    • -
  • Webhooks da organização
    • -
  • Os {% data variables.product.prodname_github_app %}s com a permissão metadados` - -#### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ---------------------- | -------- | --------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Pode ser `criado`, `editado` ou `excluído`. | -| `etiqueta` | `objeto` | A etiqueta que foi adicionada. | -| `alterações` | `objeto` | As alterações na etiqueta se a ação foi `editada`. | -| `changes[name][from]` | `string` | A versão anterior do nome se a ação foi `editada`. | -| `changes[color][from]` | `string` | A versão anterior da cor se a ação foi `editada`. | +{% data reusables.webhooks.issue_comment_webhook_properties %} +{% data reusables.webhooks.issue_comment_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example + +{{ webhookPayloadsForCurrentVersion.issue_comment.created }} + +### issues + +{% data reusables.webhooks.issues_short_desc %} + +#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `issues` permission + +#### Webhook payload object + +{% data reusables.webhooks.issue_webhook_properties %} +{% data reusables.webhooks.issue_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Webhook payload example when someone edits an issue + +{{ webhookPayloadsForCurrentVersion.issues.edited }} + +### label + +{% data reusables.webhooks.label_short_desc %} + +#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `metadata` permission + +#### Webhook payload object + +Key | Type | Description +----|------|------------- +`action`|`string` | The action that was performed. Can be `created`, `edited`, or `deleted`. +`label`|`object` | The label that was added. +`changes`|`object`| The changes to the label if the action was `edited`. +`changes[name][from]`|`string` | The previous version of the name if the action was `edited`. +`changes[color][from]`|`string` | The previous version of the color if the action was `edited`. +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.label.deleted }} {% if currentVersion == "free-pro-team@latest" %} ### marketplace_purchase -Atividade relacionada a uma compra do GitHub Marketplace. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte o "[GitHub Marketplace](/marketplace/)". +Activity related to a GitHub Marketplace purchase. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub Marketplace](/marketplace/)." -#### Disponibilidade +#### Availability - {% data variables.product.prodname_github_app %}s -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada para um plano do [GitHub Marketplace](https://github.com/marketplace). Pode ser uma das ações a seguir:
    • `comprado` - Alguém comprou um plano do GitHub Marketplace. A mudança deve entrar em vigor na conta imediatamente.
    • `pending_change` - Você receberá o evento `pending_change` quando alguém tiver feito o downgrade ou cancelado um plano do GitHub Marketplace para indicar que uma alteração ocorrerá na conta. O novo plano ou cancelamento entra em vigor no final do ciclo de cobrança. O tipo de evento `cancelado` ou `alterado` será enviado quando o ciclo de cobrança terminar e o cancelamento ou o novo plano entrarem em vigor.
    • `pending_change_cancelled` - Alguém cancelou uma alteração pendente. Alterações pendentes incluem planos de cancelamento e downgrades que entrarão em vigor ao fim de um ciclo de cobrança.
    • `alterado` - Alguém fez o upgrade ou downgrade de um plano do GitHub Marketplace e a alteração entrará em vigor na conta imediatamente.
    • `cancelado` - Alguém cancelou um plano do GitHub Marketplace e o último ciclo de cobrança foi finalizado. A mudança deve entrar em vigor na conta imediatamente.
    | +Key | Type | Description +----|------|------------- +`action` | `string` | The action performed for a [GitHub Marketplace](https://github.com/marketplace) plan. Can be one of:
    • `purchased` - Someone purchased a GitHub Marketplace plan. The change should take effect on the account immediately.
    • `pending_change` - You will receive the `pending_change` event when someone has downgraded or cancelled a GitHub Marketplace plan to indicate a change will occur on the account. The new plan or cancellation takes effect at the end of the billing cycle. The `cancelled` or `changed` event type will be sent when the billing cycle has ended and the cancellation or new plan should take effect.
    • `pending_change_cancelled` - Someone has cancelled a pending change. Pending changes include plan cancellations and downgrades that will take effect at the end of a billing cycle.
    • `changed` - Someone has upgraded or downgraded a GitHub Marketplace plan and the change should take effect on the account immediately.
    • `cancelled` - Someone cancelled a GitHub Marketplace plan and the last billing cycle has ended. The change should take effect on the account immediately.
    -Para obter uma descrição detalhada desta carga e da carga para cada tipo de `ação`, consulte [eventos do webhook de {% data variables.product.prodname_marketplace %} ](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). +For a detailed description of this payload and the payload for each type of `action`, see [{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). -#### Exemplo de carga de webhook quando alguém compra o plano +#### Webhook payload example when someone purchases the plan {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} {% endif %} -### integrante +### member {% data reusables.webhooks.member_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão     membros`
    • -
+- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `members` permission -

Objeto da carga do webhook

+#### Webhook payload object -

{% data reusables.webhooks.member_webhook_properties %}

+{% data reusables.webhooks.member_webhook_properties %} +{% data reusables.webhooks.member_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} -

-

+#### Webhook payload example -

{% data reusables.webhooks.member_properties %}

+{{ webhookPayloadsForCurrentVersion.member.added }} -

-

+### membership -

{% data reusables.webhooks.repo_desc %}

+{% data reusables.webhooks.membership_short_desc %} -

-

+#### Availability -

{% data reusables.webhooks.org_desc %}

+- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `members` permission -

-

+#### Webhook payload object -

{% data reusables.webhooks.app_desc %}

+{% data reusables.webhooks.membership_properties %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} -

-

+#### Webhook payload example -

{% data reusables.webhooks.sender_desc %}

+{{ webhookPayloadsForCurrentVersion.membership.removed }} -

Exemplo de carga de webhook

+### meta -

{{ webhookPayloadsForCurrentVersion.member.added }}

+The webhook this event is configured on was deleted. This event will only listen for changes to the particular hook the event is installed on. Therefore, it must be selected for each hook that you'd like to receive meta events for. -

filiação

+#### Availability -

{% data reusables.webhooks.membership_short_desc %}

+- Repository webhooks +- Organization webhooks -

Disponibilidade

+#### Webhook payload object -
    -
  • Webhooks da organização
    • -
  • Os {% data variables.product.prodname_github_app %}s com a permissão `membros`
    • -
- -

Objeto da carga do webhook

- -

{% data reusables.webhooks.membership_properties %}

- -

-

- -

{% data reusables.webhooks.org_desc %}

- -

-

- -

{% data reusables.webhooks.app_desc %}

- -

-

- -

{% data reusables.webhooks.sender_desc %}

- -

Exemplo de carga de webhook

- -

{{ webhookPayloadsForCurrentVersion.membership.removed }}

- -

meta

- -

O webhook em que este evento está configurado em foi excluído. Este evento só ouvirá alterações no hook em que o evento está instalado. Portanto, deve ser selecionado para cada hook para o qual você gostaria de receber metaeventos.

- -

Disponibilidade

- -
    -
  • Webhooks do repositório
    • -
  • Webhooks da organização
    • -
- -

Objeto da carga do webhook

- -

- - - - - - - - - - - -
TeclaTipoDescrição
Ação`

+Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `deleted`. +`hook_id` |`integer` | The id of the modified webhook. +`hook` |`object` | The modified webhook. This will contain different keys based on the type of webhook it is: repository, organization, business, app, or GitHub Marketplace. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.meta.deleted }} -### marco +### milestone {% data reusables.webhooks.milestone_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.milestone_properties %} {% data reusables.webhooks.repo_desc %} @@ -747,42 +658,33 @@ Para obter uma descrição detalhada desta carga e da carga para cada tipo de `a {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.milestone.created }} -### organização +### organization {% data reusables.webhooks.organization_short_desc %} -#### Disponibilidade +#### Availability {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -- Os webhooks do GitHub Enterprise recebem apenas eventos `criados` e `excluídos`. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} -- Os webhooks da organização recebem apenas os eventos `excluídos`, `adicionados`, `removidos`, `renomeado` e `convidados` -- Os {% data variables.product.prodname_github_app %}s com a permissão membros` - +- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} +- Organization webhooks only receive the `deleted`, `added`, `removed`, `renamed`, and `invited` events +- {% data variables.product.prodname_github_app %}s with the `members` permission -

Objeto da carga do webhook

+#### Webhook payload object -

- - - - - - - - - - - -
TeclaTipoDescrição
Ação`

+Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. Can be one of:{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, or `member_invited`. +`invitation` |`object` | The invitation for the user or email if the action is `member_invited`. +`membership` |`object` | The membership between the user and the organization. Not present when the action is `member_invited`. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.organization.member_added }} @@ -792,42 +694,42 @@ Para obter uma descrição detalhada desta carga e da carga para cada tipo de `a {% data reusables.webhooks.org_block_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `organization_administration` +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `organization_administration` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| -------------- | -------- | --------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `bloqueado` ou `desbloqueado`. | -| `blocked_user` | `objeto` | Informações sobre o usuário bloqueado ou desbloqueado. | +Key | Type | Description +----|------|------------ +`action` | `string` | The action performed. Can be `blocked` or `unblocked`. +`blocked_user` | `object` | Information about the user that was blocked or unblocked. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.org_block.blocked }} -### pacote +### package -Atividade relacionada a {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte o[Bloqueando usuários da organização](/v3/orgs/blocking/)" da API REST. Para obter mais informações, consulte "[Gerenciando pacotes com {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para saber mais sobre {% data variables.product.prodname_registry %}. +Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização +- Repository webhooks +- Organization webhooks -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.package_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.package.published }} {% endif %} @@ -836,24 +738,24 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.page_build_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `páginas` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `pages` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------- | --------- | --------------------------------------------------------------------------------------- | -| `id` | `inteiro` | O identificador exclusivo da criação de páginas. | -| `build` | `objeto` | A [Listar as criações do GitHub Pages](/rest/reference/repos#list-github-pages-builds). | +Key | Type | Description +----|------|------------ +`id` | `integer` | The unique identifier of the page build. +`build` | `object` | The [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) itself. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.page_build }} @@ -861,25 +763,25 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.ping_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s recebem um evento de ping com um `app_id` usado para registrar o aplicativo +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s receive a ping event with an `app_id` used to register the app -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| -------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `zen` | `string` | String aleatória do Github zen. | -| `hook_id` | `inteiro` | O ID do webhook que acionou o ping. | -| `hook` | `objeto` | A [configuração do webhook](/v3/repos/hooks/#get-a-repository-webhook). | -| `hook[app_id]` | `inteiro` | Ao registrar um novo {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} envia um evento de ping para a **URL do webhook** que você especificou no registro. O evento contém o `app_id`, que é necessário para a [efetuar a autenticação](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) em um aplicativo. | +Key | Type | Description +----|------|------------ +`zen` | `string` | Random string of GitHub zen. +`hook_id` | `integer` | The ID of the webhook that triggered the ping. +`hook` | `object` | The [webhook configuration](/rest/reference/repos#get-a-repository-webhook). +`hook[app_id]` | `integer` | When you register a new {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} sends a ping event to the **webhook URL** you specified during registration. The event contains the `app_id`, which is required for [authenticating](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) an app. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.ping }} @@ -887,13 +789,13 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.project_card_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `repository_projects` ou `organization_projects` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.project_card_properties %} {% data reusables.webhooks.repo_desc %} @@ -901,7 +803,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.project_card.created }} @@ -909,13 +811,13 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.project_column_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `repository_projects` ou `organization_projects` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.project_column_properties %} {% data reusables.webhooks.repo_desc %} @@ -923,7 +825,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.project_column.created }} @@ -931,13 +833,13 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.project_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `repository_projects` ou `organization_projects` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.project_properties %} {% data reusables.webhooks.repo_desc %} @@ -945,31 +847,30 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.project.created }} -### público +### public {% data reusables.webhooks.public_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `metadados` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `metadata` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ----- | ---- | --------- | -| | | | +Key | Type | Description +----|------|------------- {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.public }} @@ -977,13 +878,13 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.pull_request_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.pull_request_webhook_properties %} {% data reusables.webhooks.pull_request_properties %} @@ -992,9 +893,9 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example -As entregas para eventos `review_requested` e `review_request_removed` terão um campo adicional denominado `requested_reviewer`. +Deliveries for `review_requested` and `review_request_removed` events will have an additional field called `requested_reviewer`. {{ webhookPayloadsForCurrentVersion.pull_request.opened }} @@ -1002,13 +903,13 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um {% data reusables.webhooks.pull_request_review_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.pull_request_review_properties %} {% data reusables.webhooks.repo_desc %} @@ -1016,7 +917,7 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }} @@ -1024,13 +925,13 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um {% data reusables.webhooks.pull_request_review_comment_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.pull_request_review_comment_webhook_properties %} {% data reusables.webhooks.pull_request_review_comment_properties %} @@ -1039,7 +940,7 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }} @@ -1049,62 +950,62 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um {% note %} -**Observação:** Você não receberá um webhook para este evento ao fazer push de mais de três tags de uma vez. +**Note:** You will not receive a webhook for this event when you push more than three tags at once. {% endnote %} {% tip %} -**Observação**: O exemplo da carga do webhook que segue a tabela difere significativamente da carga da API de eventos descrita na tabela. Entre outras diferenças, a carga do webhook inclui os objetos `remetente` `pusher`. Remetente e pusher são os mesmos usuários que iniciaram o evento `push`, mas o objeto `remetente` contém mais detalhes. +**Note**: The webhook payload example following the table differs significantly from the Events API payload described in the table. Among other differences, the webhook payload includes both `sender` and `pusher` objects. Sender and pusher are the same user who initiated the `push` event, but the `sender` object contains more detail. {% endtip %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| -------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | O [`git ref`](/v3/git/refs/) completo que foi carregado. Exemplo: `refs/heads/master`. | -| `antes` | `string` | O SHA do último commit em `ref` antes do push. | -| `depois` | `string` | O SHA do último commit no `ref` após o push. | -| `commits` | `array` | Um array de objetos de commit, que descreve os commits carregados. (O array inclui um máximo de 20 commits. Se necessário, você poderá usar a [API de commits](/v3/repos/commits/) para recuperar commits adicionais. Este limite é aplicado apenas aos eventos da linha do tempo e não é aplicado às entregas do webhook.) | -| `commits[][id]` | `string` | O SHA do commit. | -| `commits[][timestamp]` | `string` | O carimbo de tempo ISO 8601 do commit. | -| `commits[][message]` | `string` | A mensagem do commit. | -| `commits[][author]` | `objeto` | O autor do git do commit. | -| `commits[][author][name]` | `string` | O nome do autor do git. | -| `commits[][author][email]` | `string` | O endereço de e-mail do autor do git. | -| `commits[][url]` | `url` | URL que aponta para o recurso de commit de API. | -| `commits[][distinct]` | `boolean` | Se este compromisso é diferente de qualquer outro que tenha sido carregado anteriormente. | -| `commits[][added]` | `array` | Um array de arquivos adicionados no commit. | -| `commits[][modified]` | `array` | Um array de arquivos modificados pelo commit. | -| `commits[][removed]` | `array` | Um array de arquivos removidos no commit. | -| `pusher` | `objeto` | O usuário que fez o push dos commits. | +Key | Type | Description +----|------|------------- +`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. +`before`|`string` | The SHA of the most recent commit on `ref` before the push. +`after`|`string` | The SHA of the most recent commit on `ref` after the push. +`commits`|`array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) +`commits[][id]`|`string` | The SHA of the commit. +`commits[][timestamp]`|`string` | The ISO 8601 timestamp of the commit. +`commits[][message]`|`string` | The commit message. +`commits[][author]`|`object` | The git author of the commit. +`commits[][author][name]`|`string` | The git author's name. +`commits[][author][email]`|`string` | The git author's email address. +`commits[][url]`|`url` | URL that points to the commit API resource. +`commits[][distinct]`|`boolean` | Whether this commit is distinct from any that have been pushed before. +`commits[][added]`|`array` | An array of files added in the commit. +`commits[][modified]`|`array` | An array of files modified by the commit. +`commits[][removed]`|`array` | An array of files removed in the commit. +`pusher` | `object` | The user who pushed the commits. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.push }} -### versão +### release {% data reusables.webhooks.release_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.release_webhook_properties %} {% data reusables.webhooks.release_properties %} @@ -1113,66 +1014,66 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.release.published }} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### repository_dispatch -Este evento ocorre quando um {% data variables.product.prodname_github_app %} envia uma solicitação de `POST` para o ponto de extremidade "[Criar um evento de envio de repositório](/v3/repos/#create-a-repository-dispatch-event)". +This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. -#### Disponibilidade +#### Availability -- Os {% data variables.product.prodname_github_app %}s devem ter a permissão de `conteúdo` para receber este webhook. +- {% data variables.product.prodname_github_app %}s must have the `contents` permission to receive this webhook. -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository_dispatch }} {% endif %} -### repositório +### repository {% data reusables.webhooks.repository_short_desc %} -#### Disponibilidade +#### Availability -- Os webhooks do repositório recebem todos os tipos de eventos, exceto `excluído` -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de `metadados` recebem todos os tipos de eventos, exceto `excluídos` +- Repository webhooks receive all event types except `deleted` +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `metadata` permission receive all event types except `deleted` -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------ | -------- | ---------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Este pode ser um dos seguintes:
  • `created` - Um repositório foi criado.
  • `deleted` - Um repositório foi excluído. Este tipo de evento está disponível apenas para [hooks de organização](/rest/reference/orgs#webhooks/)
  • `archived` - Um repositório está arquivado.
  • `unarchived` - Um repositório não está arquivado.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - Um repositório está [habilitado para acesso anônimo do Git](/v3/previews/#anonymous-git-access-to-repositories), `anonymous_access_disabled` - Um repositório está [desabilitado para acesso anônimo do Git](/v3/previews/#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - As informações de um repositório são editadas.
  • `renamed` - Um repositório é renomeado.
  • `transferred` - Um repositório é transferido.
  • `publicized` - Um repositório é publicado.
  • `privatizado` - Um repositório é privatizado.
| +Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
{% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository.publicized }} {% if currentVersion == "free-pro-team@latest"%} ### repository_import -{% data reusables.webhooks.repository_import_short_desc %} Para receber este evento para um repositório pessoal, você deve criar um repositório vazio antes da importação. Este evento pode ser acionado usando o [Importador do GitHub](/articles/importing-a-repository-with-github-importer/) ou a [API de importações de fonte](/v3/migrations/source_imports/). +{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports). -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização +- Repository webhooks +- Organization webhooks -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.repository_import_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository_import }} @@ -1180,19 +1081,19 @@ Este evento ocorre quando um {% data variables.product.prodname_github_app %} en {% data reusables.webhooks.repository_vulnerability_alert_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização +- Repository webhooks +- Organization webhooks -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.repository_vulnerability_alert_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }} @@ -1200,67 +1101,67 @@ Este evento ocorre quando um {% data variables.product.prodname_github_app %} en ### security_advisory -Atividade relacionada a uma consultora de segurança. Uma consultoria de segurança fornece informações sobre vulnerabilidades relacionadas à segurança em softwares no GitHub. O conjunto de dados da consultoria de segurança também promove os alertas de segurança do GitHub, consulte "[Sobre os alertas de segurança para dependências vulneráveis](/articles/about-security-alerts-for-vulnerable-dependencies/)." +Activity related to a security advisory. A security advisory provides information about security-related vulnerabilities in software on GitHub. The security advisory dataset also powers the GitHub security alerts, see "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies/)." -#### Disponibilidade +#### Availability -- Os {% data variables.product.prodname_github_app %}s com a permissão `security_events` +- {% data variables.product.prodname_github_app %}s with the `security_events` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. A ação pode ser `publicadas`, `atualizadas`, ou `executadas` para todos os novos eventos. | -| `security_advisory` | `objeto` | As informações da consultoria de segurança, incluindo resumo, descrição e gravidade. | +Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. The action can be one of `published`, `updated`, or `performed` for all new events. +`security_advisory` |`object` | The details of the security advisory, including summary, description, and severity. -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.security_advisory.published }} {% if currentVersion == "free-pro-team@latest" %} -### patrocínio +### sponsorship {% data reusables.webhooks.sponsorship_short_desc %} -Você só pode criar um webhook de patrocínio em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Configurar webhooks para eventos na sua conta patrocinada](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)". +You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)". -#### Disponibilidade +#### Availability -- Contas patrocinadas +- Sponsored accounts -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.sponsorship_webhook_properties %} {% data reusables.webhooks.sponsorship_properties %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook quando alguém cria um patrocínio +#### Webhook payload example when someone creates a sponsorship {{ webhookPayloadsForCurrentVersion.sponsorship.created }} -#### Exemplo de carga de webhook quando alguém faz o downgrade de um patrocínio +#### Webhook payload example when someone downgrades a sponsorship {{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }} {% endif %} -### estrela +### star {% data reusables.webhooks.star_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização +- Repository webhooks +- Organization webhooks -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.star_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.star.created }} @@ -1268,60 +1169,58 @@ Você só pode criar um webhook de patrocínio em {% data variables.product.prod {% data reusables.webhooks.status_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `status` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `statuses` permission -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `inteiro` | O identificador exclusivo do status. | -| `sha` | `string` | O SHA do commit. | -| `estado` | `string` | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`. | -| `descrição` | `string` | A descrição opcional legível para pessoas adicionada ao status. | -| `url_destino` | `string` | O link opcional adicionado ao status. | -| `branches` | `array` | Um array de objetos de branch que contém o SHA do status. Cada branch contém o SHA fornecido, mas o SHA pode ou não ser o cabeçalho do branch. O array inclui, no máximo, 10 branches. | +Key | Type | Description +----|------|------------- +`id` | `integer` | The unique identifier of the status. +`sha`|`string` | The Commit SHA. +`state`|`string` | The new state. Can be `pending`, `success`, `failure`, or `error`. +`description`|`string` | The optional human-readable description added to the status. +`target_url`|`string` | The optional link added to the status. +`branches`|`array` | An array of branch objects containing the status' SHA. Each branch contains the given SHA, but the SHA may or may not be the head of the branch. The array includes a maximum of 10 branches. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.status }} -### equipe +### team {% data reusables.webhooks.team_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão membros` - +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `members` permission -

Objeto da carga do webhook

+#### Webhook payload object -

- - - - - - - - - - - -
TeclaTipoDescrição
Ação`

+Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. Can be one of `created`, `deleted`, `edited`, `added_to_repository`, or `removed_from_repository`. +`team` |`object` | The team itself. +`changes`|`object` | The changes to the team if the action was `edited`. +`changes[description][from]` |`string` | The previous version of the description if the action was `edited`. +`changes[name][from]` |`string` | The previous version of the name if the action was `edited`. +`changes[privacy][from]` |`string` | The previous version of the team's privacy if the action was `edited`. +`changes[repository][permissions][from][admin]` | `boolean` | The previous version of the team member's `admin` permission on a repository, if the action was `edited`. +`changes[repository][permissions][from][pull]` | `boolean` | The previous version of the team member's `pull` permission on a repository, if the action was `edited`. +`changes[repository][permissions][from][push]` | `boolean` | The previous version of the team member's `push` permission on a repository, if the action was `edited`. +`repository`|`object` | The repository that was added or removed from to the team's purview if the action was `added_to_repository`, `removed_from_repository`, or `edited`. For `edited` actions, `repository` also contains the team's new permission levels for the repository. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.team.added_to_repository }} @@ -1329,64 +1228,54 @@ Você só pode criar um webhook de patrocínio em {% data variables.product.prod {% data reusables.webhooks.team_add_short_desc %} -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão membros` - +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `members` permission -

Objeto da carga do webhook

+#### Webhook payload object -

- - - - - - - - - - -
TeclaTipoDescrição
equipe`

+Key | Type | Description +----|------|------------- +`team`|`object` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.team_add }} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -### usuário +### user -Quando um usuário é `criado` ou `excluído`. +When a user is `created` or `deleted`. -#### Disponibilidade -- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)." +#### Availability +- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.user.created }} {% endif %} -### inspecionar +### watch {% data reusables.webhooks.watch_short_desc %} -O ator do evento é o [usuário](/v3/users/) que favoritou um repositório, e o repositório do evento é [repositório](/v3/repos/) que foi favoritado. +The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. -#### Disponibilidade +#### Availability -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão `metadados` +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `metadata` permission -#### Objeto da carga do webhook +#### Webhook payload object {% data reusables.webhooks.watch_properties %} {% data reusables.webhooks.repo_desc %} @@ -1394,41 +1283,43 @@ O ator do evento é o [usuário](/v3/users/) que favoritou um repositório, e o {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.watch.started }} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### workflow_dispatch -Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no GitHub ou envia uma solicitação de `POST` para o ponto de extremidade "[Criar um evento de envio de fluxo de trabalho](/rest/reference/actions/#create-a-workflow-dispatch-event)". Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". +This event occurs when someone triggers a workflow run on GitHub or sends a `POST` request to the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" endpoint. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)." -#### Disponibilidade +#### Availability -- Os {% data variables.product.prodname_github_app %}s devem ter a permissão de `conteúdo` para receber este webhook. +- {% data variables.product.prodname_github_app %}s must have the `contents` permission to receive this webhook. -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### workflow_run -Quando uma execução do fluxo de trabalho de {% data variables.product.prodname_actions %} for solicitada ou concluída. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_run)". +When a {% data variables.product.prodname_actions %} workflow run is requested or completed. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_run)." -#### Disponibilidade +#### Availability -- {% data variables.product.prodname_github_app %} com as `ações` ou permissões de `conteúdo`. +- {% data variables.product.prodname_github_app %}s with the `actions` or `contents` permissions. -#### Objeto da carga do webhook +#### Webhook payload object -| Tecla | Tipo | Descrição | -| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A maioria das cargas de webhook contém uma ação `` propriedade que contém a atividade específica que acionou o evento. | +Key | Type | Description +----|------|------------- +`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.sender_desc %} -#### Exemplo de carga de webhook +#### Webhook payload example {{ webhookPayloadsForCurrentVersion.workflow_run }} +{% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/about-branch-restrictions.md b/translations/pt-BR/content/github/administering-a-repository/about-branch-restrictions.md index 8e23902c7a..3e16e26580 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-branch-restrictions.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-branch-restrictions.md @@ -1,6 +1,6 @@ --- title: Sobre restrições de branch -intro: 'Branches within repositories that belong to organizations can be configured so that only certain users, teams, or apps can push to the branch.' +intro: 'Os branches em repositórios que pertencem a organizações podem ser configurados de modo que apenas alguns usuários, equipes ou aplicativos possam fazer push para o branch.' product: '{% data reusables.gated-features.branch-restrictions %}' redirect_from: - /articles/about-branch-restrictions diff --git a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md index 58af138a95..942931397c 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -1,5 +1,5 @@ --- -title: About Dependabot version updates +title: Sobre as atualizações da versão do Dependabot intro: 'Você pode usar o {% data variables.product.prodname_dependabot %} para manter os pacotes que usa atualizados para as versões mais recentes.' redirect_from: - /github/administering-a-repository/about-dependabot @@ -18,7 +18,7 @@ Você habilita o {% data variables.product.prodname_dependabot_version_updates % Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)." -Se você habilitar atualizações de segurança, {% data variables.product.prodname_dependabot %} também promove pull requests para atualizar dependências vulneráveis. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +Se você habilitar atualizações de segurança, {% data variables.product.prodname_dependabot %} também promove pull requests para atualizar dependências vulneráveis. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% data reusables.dependabot.dependabot-tos %} diff --git a/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index 4bfcbe12c6..d4a28706c6 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -25,7 +25,7 @@ Cada notificação de e-mail para um push no repositório lista os novos commits - Os arquivos que foram alterados como parte do commit - A mensagem do commit; -É possível filtrar notificações de e-mail que você recebe para pushes em um repositório. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About notification emails](/github/receiving-notifications-about-activity-on-github/about-email-notifications)." Você também pode desativar notificações por email para pushes. Para obter mais informações, consulte " +É possível filtrar notificações de e-mail que você recebe para pushes em um repositório. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Sobre e-mails de notificação](/github/receiving-notifications-about-activity-on-github/about-email-notifications)". Você também pode desativar notificações por email para pushes. Para obter mais informações, consulte " [Escolher o método de entrega das suas notificações](/enterprise/{{ page.version }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}".

diff --git a/translations/pt-BR/content/github/administering-a-repository/about-releases.md b/translations/pt-BR/content/github/administering-a-repository/about-releases.md index 121135ce20..b43680a4f6 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-releases.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-releases.md @@ -21,7 +21,7 @@ Versões são iterações de software implementáveis que você pode empacotar e As versões se baseiam em [tags Git](https://git-scm.com/book/en/Git-Basics-Tagging), que marcam um ponto específico no histórico do seu repositório. Uma data de tag pode ser diferente de uma data de versão, já que elas podem ser criadas em momentos diferentes. Para obter mais informações sobre como visualizar as tags existentes, consulte "[Visualizar tags e versões do seu repositório](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)". -Você pode receber notificações quando novas versões são publicadas em um repositório sem receber notificações sobre outras atualizações para o repositório. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching releases for a repository](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." +Você pode receber notificações quando novas versões são publicadas em um repositório sem receber notificações sobre outras atualizações para o repositório. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Visualizar as suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Inspecionar e não inspecionar as versões de um repositório](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." Qualquer pessoa com acesso de leitura a um repositório pode ver e comparar versões, mas somente pessoas com permissões de gravação a um repositório podem gerenciar versões. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)." @@ -37,13 +37,13 @@ Pessoas com permissões de administrador para um repositório podem escolher se Se uma versão consertar uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. -{% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." Você pode visualizar a aba **Dependentes** do gráfico de dependências para ver quais repositórios e pacotes dependem do código no repositório e pode, portanto, ser afetado por uma nova versão. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". {% endif %} -Você também pode usar a API de Releases para reunir informações, tais como o número de vezes que as pessoas baixam um ativo de versão. Para obter mais informações, consulte "[Versões](/v3/repos/releases/)". +Você também pode usar a API de Releases para reunir informações, tais como o número de vezes que as pessoas baixam um ativo de versão. Para obter mais informações, consulte "[Versões](/rest/reference/repos#releases)". {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/pt-BR/content/github/administering-a-repository/about-required-status-checks.md b/translations/pt-BR/content/github/administering-a-repository/about-required-status-checks.md index 0182321146..597fa31b8a 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-required-status-checks.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-required-status-checks.md @@ -36,7 +36,7 @@ Você pode optar por tornar mais ou menos rígidas as verificações de status, ### Solução de problemas de verificações de status necessárias -Se você tiver uma verificação e um status com o mesmo nome e selecionar esse nome como uma verificação de status obrigatória, a verificação e o status serão obrigatórios. Para obter mais informações, consulte "[Verificações](/v3/checks/)". +Se você tiver uma verificação e um status com o mesmo nome e selecionar esse nome como uma verificação de status obrigatória, a verificação e o status serão obrigatórios. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)". Após configuração das verificações de status obrigatórias, o branch deverá ser atualizado com o branch base antes da ação de merge. Isso garante que o branch foi testado com o código mais recente do branch base. Se o branch estiver desatualizado, você precisará fazer merge do branch base no seu branch. @@ -62,7 +62,7 @@ remote: error: Required status check "ci-build" is failing {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Por vezes, os resultados das verificações de status para o commit de mescla teste e o commit principal entrarão em conflito. Se o commit de mescla teste tiver um status, ele deve passar. Caso contrário, o status do commit principal deve passar antes de você poder mesclar o branch. Para obter mais informações sobre os commits de mescla teste, consulte "[Pull requests](/v3/pulls/#response-1)". +Por vezes, os resultados das verificações de status para o commit de mescla teste e o commit principal entrarão em conflito. Se o commit de mescla teste tiver um status, ele deve passar. Caso contrário, o status do commit principal deve passar antes de você poder mesclar o branch. Para obter mais informações sobre os commits de mescla teste, consulte "[Pull requests](/rest/reference/pulls#response-1)". ![Branch com commits de mescla conflitantes](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md b/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md index f079e6206f..dc44c26603 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md @@ -1,6 +1,7 @@ --- title: Sobre a varredura de segredo intro: 'O {% data variables.product.product_name %} verifica repositórios em busca de tipos de segredos conhecidos a fim de impedir o uso fraudulento de segredos que sofreram commit acidentalmente.' +product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /github/administering-a-repository/about-token-scanning - /articles/about-token-scanning @@ -17,6 +18,8 @@ Os provedores de serviço podem fazer parceria com o {% data variables.product.c ### Sobre o {% data variables.product.prodname_secret_scanning %} para repositórios públicos + {% data variables.product.prodname_secret_scanning_caps %} é automaticamente habilitado em repositórios públicos, em que faz a varredura de código para saber se há segredos, para verificar os formatos de segredos conhecidos. Quando uma correspondência do seu formato de segredo é encontrada em um repositório público, {% data variables.product.company_short %} não divulga publicamente as informações como um alerta, mas envia uma carga para um ponto de extremidade de HTTP da sua escolha. Para uma visão geral de como a varredura de segredo funciona em repositórios públicos, consulte "[Varredura de segredo](/developers/overview/secret-scanning)". + Quando você faz push para um repositório público, o {% data variables.product.product_name %} verifica segredos no conteúdo dos commits. Se você alternar um repositório privado para público, o {% data variables.product.product_name %} verifica segredos em todo o repositório. Quando o {% data variables.product.prodname_secret_scanning %} detecta um conjunto de credenciais, notificamos o provedor de serviço que emitiu o segredo. O provedor de serviço valida a credencial e decide se deve revogar o segredo, emitir um novo segredo ou entrar em contato com você diretamente, o que dependerá dos riscos associados a você ou ao provedor de serviço. @@ -64,6 +67,8 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p {% data reusables.secret-scanning.beta %} +Se você for um administrador de repositório ou um proprietário da organização, você poderá habilitar {% data variables.product.prodname_secret_scanning %} para repositórios privados que pertençam a organizações. Você pode habilitar {% data variables.product.prodname_secret_scanning %} para todos os seus repositórios ou para todos os novos repositórios da organização. {% data variables.product.prodname_secret_scanning_caps %} não está disponível para repositórios privados de contas de usuário. Para mais informações consulte "[Gerenciar as configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" e "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". + Quando você faz push de commits em um repositório privado com o {% data variables.product.prodname_secret_scanning %} habilitado, o {% data variables.product.product_name %} verifica o conteúdo dos commits em busca de segredos. Quando o {% data variables.product.prodname_secret_scanning %} detecta um segredo em um repositório privado, o {% data variables.product.prodname_dotcom %} envia alertas. @@ -72,6 +77,8 @@ Quando o {% data variables.product.prodname_secret_scanning %} detecta um segred - O {% data variables.product.prodname_dotcom %} exibe um alerta no repositório. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." +Os administradores do repositório e proprietários da organização podem conceder acesso a alertas de {% data variables.product.prodname_secret_scanning %} aos usuários e à equipe. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". + O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. - Adafruit diff --git a/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md index 9e96152167..0033ab237c 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md @@ -21,13 +21,13 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod Discute em particular e corrige vulnerabilidades de segurança no código do seu repositório. Em seguida, você pode publicar uma consultoria de segurança para alertar a sua comunidade sobre a vulnerabilidade e incentivá-los a fazer a atualização. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". -- **{% data variables.product.prodname_dependabot_alerts %} and security updates** +- **{% data variables.product.prodname_dependabot_alerts %} e atualizações de segurança** - Ver alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e escolher se deseja gerar pull requests para atualizar essas dependências automaticamente. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." + Ver alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e escolher se deseja gerar pull requests para atualizar essas dependências automaticamente. Para obter mais informações, consulte "[Sobre alertas de dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) e "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". -- **{% data variables.product.prodname_dependabot %} version updates** +- **atualizações de versão de {% data variables.product.prodname_dependabot %}** - Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". + Use {% data variables.product.prodname_dependabot %} para levantar automaticamente os pull requests a fim de manter suas dependências atualizadas. Isso ajuda a reduzir a exposição a versões mais antigas de dependências. Usar versões mais recentes facilita a aplicação de patches, caso as vulnerabilidades de segurança sejam descobertas e também torna mais fácil para {% data variables.product.prodname_dependabot_security_updates %} levantar, com sucesso, os pull requests para atualizar as dependências vulneráveis. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". - **Alertas de {% data variables.product.prodname_code_scanning_capc %}** @@ -43,6 +43,6 @@ O gráfico de dependências de {% data variables.product.prodname_dotcom %} perm * Ecossistemas e pacotes dos quais o repositório depende * Repositórios e pacotes que dependem do seu repositório -You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. +Você deve habilitar o gráfico de dependências antes de {% data variables.product.prodname_dotcom %} pode gerar {% data variables.product.prodname_dependabot_alerts %} para dependências com vulnerabilidades de segurança. Você pode encontrar o gráfico de dependências na aba **Ideias** para o seu repositório. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". diff --git a/translations/pt-BR/content/github/administering-a-repository/classifying-your-repository-with-topics.md b/translations/pt-BR/content/github/administering-a-repository/classifying-your-repository-with-topics.md index 3558507856..c59f160d83 100644 --- a/translations/pt-BR/content/github/administering-a-repository/classifying-your-repository-with-topics.md +++ b/translations/pt-BR/content/github/administering-a-repository/classifying-your-repository-with-topics.md @@ -1,6 +1,6 @@ --- -title: Classifying your repository with topics -intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.' +title: Classificar repositório com tópicos +intro: 'Para ajudar outras pessoas a encontrar seu projeto e a contribuir com ele, você pode adicionar tópicos ao repositório relacionados à intenção do projeto, área de assunto, grupos de afinidade ou outras características importantes.' redirect_from: - /articles/about-topics/ - /articles/classifying-your-repository-with-topics @@ -10,36 +10,30 @@ versions: github-ae: '*' --- -### About topics +### Sobre tópicos -With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% if currentVersion == "free-pro-team@latest" %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}. +Com tópicos, você pode explorar repositórios em uma área de assunto específica, encontrar projetos com os quais contribuir e descobrir novas soluções para um problema específico. Os tópicos aparecem na página principal de um repositório. Você pode clicar em um nome de tópico para {% if currentVersion == "free-pro-team@latest" %}ver tópicos relacionados e uma lista de outros repositórios classificados com esse tópico{% else %}buscar outros repositórios com esse tópico{% endif %}. -![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png) +![Página principal do repositório de teste mostrando tópicos](/assets/images/help/repository/os-repo-with-topics.png) -To browse the most used topics, go to https://github.com/topics/. +Para procurar os tópicos mais usados, vá para https://github.com/topics/. -{% if currentVersion == "free-pro-team@latest" %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %} +{% if currentVersion == "free-pro-team@latest" %}Você pode contribuir para o conjunto de tópicos em destaque de {% data variables.product.product_name %}no repositório [github/explore](https://github.com/github/explore). {% endif %} -Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% if currentVersion == "free-pro-team@latest" %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %} +Os administradores de repositório podem adicionar qualquer tópico que desejarem a um repositório. Tópicos úteis para classificar um repositório incluem o propósito pretendido, área de assunto, comunidade ou linguagem.{% if currentVersion == "free-pro-team@latest" %} Adicionalmente, {% data variables.product.product_name %} analisa o conteúdo do repositório público e gera tópicos sugeridos que os administradores do repositório podem aceitar ou rejeitar. O conteúdo do repositório privado não é analisado e não recebe sugestões de tópico.{% endif %} -Public and private repositories can have topics, although you will only see private repositories that you have access to in topic search results. +{% if currentVersion == "github-ae@latest" %}Interno {% else %}Público, interna, {% endif %}e repositórios privados podem ter tópicos, embora você veja apenas repositórios privados aos quais você tem acesso nos resultados de pesquisa de tópicos. -You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/articles/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/articles/searching-topics)." +Você pode pesquisar repositórios que são associados a um tópico específico. Para obter mais informações, consulte "[Pesquisar repositórios](/articles/searching-for-repositories#search-by-topic)". Também é possível pesquisar uma lista de tópicos no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Pesquisar tópicos](/articles/searching-topics)". -### Adding topics to your repository +### Adicionar tópicos ao repositório {% data reusables.repositories.navigate-to-repo %}{% if currentVersion ver_lt "enterprise-server@2.22" %} -2. Under your repository description, click **Add topics**. - ![Add topics link on a repository's main page](/assets/images/help/repository/add-topics-link.png) -3. Type the topic you want to add to your repository, then type a space. - ![Form to enter topics](/assets/images/help/repository/add-topic-form.png) -4. After you've finished adding topics, click **Done**. - ![Form with a list of topics and Done button](/assets/images/help/repository/add-topics-done-button.png) +2. Abaixo da descrição do repositório, clique em **Add topics** (Adicionar tópicos). ![Adicionar link de tópicos na página principal de um repositório](/assets/images/help/repository/add-topics-link.png) +3. Digite o tópico que deseja adicionar ao repositório e digite um espaço. ![Formulário para inserir tópicos](/assets/images/help/repository/add-topic-form.png) +4. Depois que acabar de adicionar tópicos, clique em **Done** (Concluído). ![Formulário com uma lista de tópicos e botão Done (Concluído)](/assets/images/help/repository/add-topics-done-button.png) {% else %} -2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}. - ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png) -3. Under "Topics", type the topic you want to add to your repository, then type a space. - ![Form to enter topics](/assets/images/help/repository/add-topic-form.png) -4. After you've finished adding topics, click **Save changes**. - !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png) +2. À direita de "Sobre", clique em {% octicon "gear" aria-label="The Gear icon" %}. ![Ícone de engrenagem na página principal de um repositório](/assets/images/help/repository/edit-repository-details-gear.png) +3. Em "Tópicos", digite o tópico que você deseja adicionar ao seu repositório e, em seguida, digite um espaço. ![Formulário para inserir tópicos](/assets/images/help/repository/add-topic-form.png) +4. Depois que acabar de adicionar tópicos, clique em **Salvar alterações**. ![Botão de "Salvar alterações" em "Editar detalhes do repositório"](/assets/images/help/repository/edit-repository-details-save-changes-button.png) {% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index d8da8921c7..5a1f04a204 100644 --- a/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -12,7 +12,7 @@ versions: O arquivo de configuração do {% data variables.product.prodname_dependabot %} , *dependabot.yml*, usa a sintaxe YAML. Se você não souber o que é YAMLe quiser saber mais, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". -Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. Quaisquer opções que também afetem as atualizações de segurança são usadas na próxima vez que um alerta de segurança acionar um pull request para uma atualização de segurança. Para obter mais informações, consulte "[Habilitar e desabilitar as atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)" e "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". ### Opções de configuração para *dependabot.yml* diff --git a/translations/pt-BR/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md b/translations/pt-BR/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md index 956ff2b6ed..25ff8c4712 100644 --- a/translations/pt-BR/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md +++ b/translations/pt-BR/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md @@ -10,7 +10,7 @@ versions: github-ae: '*' --- -Anyone with admin permissions to a repository can configure autolink references to link issues, pull requests,{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} commit messages, and release descriptions{% else %} and commit messages{% endif %} to external third-party services. +Qualquer pessoa com permissões de administrador em um repositório pode configurar referências de link automático para vincular problemas, pull requests,{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} mensagens de commit e versão{% else %} e mensagens do commit{% endif %} para serviços externos de terceiros. Se você usa o Zendesk para acompanhar tíquetes relatados pelo usuário, por exemplo, é possível fazer referência a um número de tíquete na pull request que você abre para corrigir o problema. diff --git a/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md index db204e574c..6e1a84bf45 100644 --- a/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md +++ b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md @@ -1,6 +1,7 @@ --- title: Configurando escaneamento secreto de repositórios privados intro: 'Você pode configurar como o {% data variables.product.product_name %} verifica seus repositórios privados em busca de segredos.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'Pessoas com permissões de administrador em um repositório privado podem habilitar o {% data variables.product.prodname_secret_scanning %} para o repositório.' versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/github/administering-a-repository/customizing-dependency-updates.md b/translations/pt-BR/content/github/administering-a-repository/customizing-dependency-updates.md index 405e97a07d..85b0144c05 100644 --- a/translations/pt-BR/content/github/administering-a-repository/customizing-dependency-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/customizing-dependency-updates.md @@ -20,7 +20,7 @@ Depois que você habilitou as atualizações de versão, você pode personalizar Para obter mais informações sobre as opções de configuração, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates)". -Ao atualizar o arquivo *dependabot.yml* no seu repositório, o {% data variables.product.prodname_dependabot %} executa uma verificação imediata com a nova configuração. Within minutes you will see an updated list of dependencies on the **{% data variables.product.prodname_dependabot %}** tab, this may take longer if the repository has many dependencies. Você também pode ver novas pull requests para atualizações de versão. Para obter mais informações, consulte "[Listando dependências configuradas para atualizações da versão](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)". +Ao atualizar o arquivo *dependabot.yml* no seu repositório, o {% data variables.product.prodname_dependabot %} executa uma verificação imediata com a nova configuração. Dentro de minutos você verá uma lista atualizada de dependências na aba **{% data variables.product.prodname_dependabot %}**. Isso pode demorar mais se o repositório tiver muitas dependências. Você também pode ver novas pull requests para atualizações de versão. Para obter mais informações, consulte "[Listando dependências configuradas para atualizações da versão](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)". ### Impacto das alterações de configuração nas atualizações de segurança diff --git a/translations/pt-BR/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md b/translations/pt-BR/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md index 8863ac4426..e6b7dac2dd 100644 --- a/translations/pt-BR/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md +++ b/translations/pt-BR/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md @@ -11,7 +11,7 @@ versions: Até você adicionar uma imagem, os links de repositório se expandem para mostrar informações básicas sobre o repositório e o avatar do proprietário. Adicionar uma imagem ao repositório ajuda a identificar seu projeto em várias plataformas sociais. -É possível fazer upload de uma imagem em um repositório privado, mas sua imagem só pode ser compartilhada de um repositório público. +{% if currentVersion != "github-ae@latest" %}You can upload an image to a private repository, but your image can only be shared from a public repository.{% endif %} {% tip %} Dica: a imagem deve ser um arquivo PNG, JPG ou GIF com menos de 1 MB. Para renderização de melhor qualidade, é recomendável manter a imagem em 640 x 320 pixels. diff --git a/translations/pt-BR/content/github/administering-a-repository/deleting-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/deleting-a-repository.md index 468f9f50ee..867982525d 100644 --- a/translations/pt-BR/content/github/administering-a-repository/deleting-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/deleting-a-repository.md @@ -13,17 +13,16 @@ versions: Os {% data reusables.organizations.owners-and-admins-can %} excluem um repositório da organização. Se a opção **Allow members to delete or transfer repositories for this organization** (Permitir que os integrantes excluam ou transfiram repositórios desta organização) tiver sido desabilitada, somente proprietários da organização poderão excluir repositórios da organização. {% data reusables.organizations.new-repo-permissions-more-info %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion != "github-ae@latest" %}Deleting a public repository will not delete any forks of the repository.{% endif %} + {% warning %} -**Aviso**: a exclusão de um repositório excluirá **permanentemente** anexos de versão e permissões da equipe. Esta ação **não pode** ser desfeita. +**Avisos**: + +- Deleting a repository will **permanently** delete release attachments and team permissions. Esta ação **não pode** ser desfeita. +- Deleting a private {% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}or internal {% endif %}repository will delete all forks of the repository. {% endwarning %} -{% endif %} - -Lembre-se também que: -- A exclusão de um repositório privado eliminará todas as bifurcações dele. -- A exclusão de um repositório público não eliminará as bifurcações dele. {% if currentVersion == "free-pro-team@latest" %} Você pode restaurar alguns repositórios excluídos em até 90 dias. Para obter mais informações, consulte "[Restaurar um repositório excluído](/articles/restoring-a-deleted-repository)". diff --git a/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index b21e6a0afb..e7a08f76d4 100644 --- a/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -23,7 +23,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% note %} -**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. Para obter mais informações, consulte "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" ou {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account). {% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Aplicar políticas de {% data variables.product.prodname_actions %} para a sua empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -44,7 +44,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% note %} -**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." +**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. Para obter mais informações, consulte "[Habilitar ou desabilitar {% data variables.product.prodname_actions %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" ou {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account). {% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} para a sua empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". {% endif %} @@ -63,7 +63,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. ![Adicionar ações para permitir lista](/assets/images/help/repository/actions-policy-allow-list.png) +1. Em **Permissões de ações**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. ![Adicionar ações para permitir lista](/assets/images/help/repository/actions-policy-allow-list.png) 2. Clique em **Salvar**. {% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index 2f4b8ed5c0..451a2bfdcc 100644 --- a/translations/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -10,7 +10,7 @@ versions: ### Sobre atualizações de versão para dependências -Você habilita {% data variables.product.prodname_dependabot_version_updates %}, verificando um arquivo de configuração *dependabot.yml* no diretório do seu repositório `.github`. {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. Para cada dependência do gerenciador de pacotes que você deseja atualizar, você deve especificar a localização dos arquivos de manifesto do pacote e a frequência de busca por atualizações nas dependências listadas nesses arquivos. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +Você habilita {% data variables.product.prodname_dependabot_version_updates %}, verificando um arquivo de configuração *dependabot.yml* no diretório do seu repositório `.github`. Em seguida, o {% data variables.product.prodname_dependabot %} cria um pull request para manter as dependências que você configura atualizadas. Para cada dependência do gerenciador de pacotes que você deseja atualizar, você deve especificar a localização dos arquivos de manifesto do pacote e a frequência de busca por atualizações nas dependências listadas nesses arquivos. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." {% data reusables.dependabot.initial-updates %} Para obter mais informações, consulte "[Personalizar atualizações de dependência](/github/administering-a-repository/customizing-dependency-updates)". @@ -72,7 +72,7 @@ Em uma bifurcação, você também precisa habilitar explicitamente {% data vari ### Verificando o status das atualizações da versão -Depois que você habilitar as atualizações da versão, você verá uma nova aba **Dependabot** no gráfico de dependências para o repositório. This tab shows which package managers {% data variables.product.prodname_dependabot %} is configured to monitor and when {% data variables.product.prodname_dependabot %} last checked for new versions. +Depois que você habilitar as atualizações da versão, você verá uma nova aba **Dependabot** no gráfico de dependências para o repositório. Esta aba mostra quais gerentes de pacote de {% data variables.product.prodname_dependabot %} estão configurados para monitorar e quando {% data variables.product.prodname_dependabot %} fez a última verificação com relação a novas versões. ![Aba de Insights do Repositório, gráfico de dependências, aba Dependabot](/assets/images/help/dependabot/dependabot-tab-view-beta.png) diff --git a/translations/pt-BR/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md index c306f5a990..716425cc13 100644 --- a/translations/pt-BR/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md @@ -5,12 +5,11 @@ redirect_from: - /articles/enabling-anonymous-git-read-access-for-a-repository versions: enterprise-server: '*' - github-ae: '*' --- Os administradores de repositório poderão alterar a configuração do acesso de leitura anônimo do Git de um repositório específico se: - Um administrador de site tiver habilitado o modo privado e o acesso de leitura anônimo do Git. -- The repository is public on the enterprise and is not a fork. +- O repositório é público na empresa e não é uma bifurcação. - Um administrador de site não tiver desabilitado o acesso de leitura anônimo do Git do repositório. {% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %} diff --git a/translations/pt-BR/content/github/administering-a-repository/enabling-branch-restrictions.md b/translations/pt-BR/content/github/administering-a-repository/enabling-branch-restrictions.md index 1b1588186a..625794839c 100644 --- a/translations/pt-BR/content/github/administering-a-repository/enabling-branch-restrictions.md +++ b/translations/pt-BR/content/github/administering-a-repository/enabling-branch-restrictions.md @@ -1,6 +1,6 @@ --- title: Habilitar restrições de branch -intro: 'You can enforce branch restrictions so that only certain users, teams, or apps can push to a protected branch in repositories owned by your organization.' +intro: 'Você pode impor restrições de branch para que apenas alguns usuários, equipes ou aplicativos possam fazer push em um branch protegido em repositórios pertencentes à sua organização.' product: '{% data reusables.gated-features.branch-restrictions %}' redirect_from: - /articles/enabling-branch-restrictions diff --git a/translations/pt-BR/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md b/translations/pt-BR/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md index 685c5215eb..d5176f462a 100644 --- a/translations/pt-BR/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/pt-BR/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md @@ -1,5 +1,5 @@ --- -title: Keeping your actions up to date with Dependabot +title: Manter as suas ações atualizadas com o Dependabot intro: 'Você pode usar o {% data variables.product.prodname_dependabot %} para manter as ações que você utiliza atualizadas para as versões mais recentes.' redirect_from: - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index 941376e498..48918cac69 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -1,6 +1,7 @@ --- title: Gerenciando alertas do escaneamento secreto intro: Você pode visualizar e fechar alertas de segredos verificados para seu repositório. +product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' --- diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md index b00d6e5b99..97346e253b 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -14,8 +14,8 @@ versions: O {% data variables.product.product_name %} cria arquivos de código-fonte do seu repositório na forma de arquivos ZIP e tarballs. As pessoas podem baixar esses arquivos na página principal do seu repositório ou como ativos de versão. Por padrão, os objetos {% data variables.large_files.product_name_short %} não estão incluídos nesses arquivos, apenas os arquivos de ponteiro para esses objetos. Para melhorar a usabilidade dos arquivos no seu repositório, você pode optar por incluir os objetos do {% data variables.large_files.product_name_short %}. {% if currentVersion != "github-ae@latest" %} -If you choose to include -{% data variables.large_files.product_name_short %} objects in archives of your repository, every download of those archives will count towards bandwidth usage for your account. Cada conta recebe {% data variables.large_files.initial_bandwidth_quota %} por mês de largura de banda gratuitamente, e você pode pagar pelo uso adicional. Para obter mais informações, consulte "[Sobre armazenamento e uso de largura de banda](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)" e "[Gerenciamento de cobrança para {% data variables.large_files.product_name_long %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage)". +Se optar por incluir +objetos de {% data variables.large_files.product_name_short %} nos arquivos do seu repositório, cada download desses arquivos será contabilizado no uso da banda larga para a sua conta. Cada conta recebe {% data variables.large_files.initial_bandwidth_quota %} por mês de largura de banda gratuitamente, e você pode pagar pelo uso adicional. Para obter mais informações, consulte "[Sobre armazenamento e uso de largura de banda](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)" e "[Gerenciamento de cobrança para {% data variables.large_files.product_name_long %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage)". {% endif %} ### Gerenciando objetos {% data variables.large_files.product_name_short %} nos arquivos diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-pull-requests-for-dependency-updates.md b/translations/pt-BR/content/github/administering-a-repository/managing-pull-requests-for-dependency-updates.md index b997f5b299..27f4effc04 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-pull-requests-for-dependency-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-pull-requests-for-dependency-updates.md @@ -11,7 +11,7 @@ versions: {% data reusables.dependabot.pull-request-introduction %} -Quando o {% data variables.product.prodname_dependabot %} cria uma pull request, você é notificado pelo método escolhido para o repositório. Each pull request contains detailed information about the proposed change, taken from the package manager. Essas pull requests seguem as verificações e testes normais definidas no seu repositório. Além disso, onde informações suficientes estão disponíveis, você verá uma pontuação de compatibilidade. Isso também pode ajudá-lo a decidir se deve ou não mesclar a alteração. For information about this score, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +Quando o {% data variables.product.prodname_dependabot %} cria uma pull request, você é notificado pelo método escolhido para o repositório. Cada pull request contém informações detalhadas sobre a mudança proposta, retirada do gerenciador de pacotes. Essas pull requests seguem as verificações e testes normais definidas no seu repositório. Além disso, onde informações suficientes estão disponíveis, você verá uma pontuação de compatibilidade. Isso também pode ajudá-lo a decidir se deve ou não mesclar a alteração. Para obter informações sobre essa pontuação, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." Se você tem muitas dependências para gerenciar, você pode querer personalizar a configuração para cada gerenciador de pacotes para que as pull requests tenham revisores, responsáveis e etiquetas específicos. Para obter mais informações, consulte "[Personalizar atualizações de dependência](/github/administering-a-repository/customizing-dependency-updates)". diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md index 46964492ac..0ef1cf5cda 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,12 +15,15 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} + ### Sobre o gerenciamento da versão -Você também pode publicar uma ação de uma versão específica em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "Publicar uma ação no {% data variables.product.prodname_marketplace %}" - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} +You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "Publicar uma ação no {% data variables.product.prodname_marketplace %}" +{% endif %} Você pode escolher se + {% data variables.large_files.product_name_long %} os objetos de ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte " [Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-repository-settings.md b/translations/pt-BR/content/github/administering-a-repository/managing-repository-settings.md index 912567005e..1436489ba4 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-repository-settings.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-repository-settings.md @@ -1,6 +1,6 @@ --- title: Gerenciar configurações do repositório -intro: 'Administradores de repositórios e proprietários de organziações podem alterar várias configurações, inclusive os nomes e propriedade de um repositório e a visibilidade pública ou privada do repositório. Eles também podem excluir um repositório.' +intro: 'Repository administrators and organization owners can change settings for a repository, like the name, ownership, and visibility, or delete the repository.' mapTopic: true redirect_from: - /articles/managing-repository-settings diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index f17b0d37b1..7e05aa25da 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -22,28 +22,28 @@ versions: {% data reusables.repositories.navigate-to-security-and-analysis %} 4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) -### Concessão de acesso a {% data variables.product.prodname_dependabot_alerts %} +### Conceder acesso aos alertas de segurança -Depois que você habilitar o {% data variables.product.prodname_dependabot_alerts %} para um repositório em uma organização, proprietários da organização e administradores de repositórios poderão ver os alertas por padrão. Você pode dar acesso a outras equipes e pessoas aos alertas de um repositório. +Depois de habilitar alertas de {% data variables.product.prodname_dependabot %} ou {% data variables.product.prodname_secret_scanning %} para um repositório em uma organização, os proprietários da organização e os administradores de repositório podem visualizar os alertas por padrão. Você pode dar acesso a outras equipes e pessoas aos alertas de um repositório. {% note %} -Os proprietários e administradores de repositórios da organização só podem conceder acesso para visualizar {% data variables.product.prodname_dependabot_alerts %} a pessoas ou equipes que tenham acesso de gravação no repositório. +Os proprietários e administradores da organização só podem conceder acesso para ver os alertas de segurança, como os alertas de {% data variables.product.prodname_dependabot %} e {% data variables.product.prodname_secret_scanning %} para pessoas ou equipes que têm acesso de gravação ao repositório. {% endnote %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Alertas dependabot", no campo de busca, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar, em seguida, clique em um nome na lista de correspondências. ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas do Dependabot](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) -5. Clique em **Save changes** (Salvar alterações). ![Botão "salvar alterações" para alterações nas configurações de alerta do Dependabot](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) +4. Em "Acesso aos alertas", no campo de pesquisa, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar e, em seguida, clique em um nome na lista de correspondências. ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +5. Clique em **Save changes** (Salvar alterações). ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) -### Revogar acesso à {% data variables.product.prodname_dependabot_alerts %} +### Remover o acesso aos alertas de segurança {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Alertas dependabot", à direita da pessoa ou da equipe cujo acesso você deseja remover, clique em {% octicon "x" aria-label="X symbol" %}. ![Botão "X" para remover o acesso de alguém aos alertas do Dependabot para o seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Em "Acesso aos alertas", à direita da pessoa ou da equipe cujo acesso você deseja remover, clique em {% octicon "x" aria-label="X symbol" %}. ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) ### Leia mais diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index d9e76dbe84..c7d6abc451 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -1,6 +1,6 @@ --- title: Gerenciando a política de bifurcação para seu repositório -intro: 'You can allow or prevent the forking of a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or internal{% endif %} repository owned by an organization.' +intro: 'Você pode permitir ou impedir a bifurcação de um repositórios privado específico{% if currentVersion == "free-pro-team@latest" or currentversion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} ou interno{% endif %} pertencente a uma organização.' redirect_from: - /articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization - /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. Para obter mais informações, consulte "[Gerenciando a política de bifurcação para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)". +Um proprietário da organização deve permitir bifurcações de repositórios privado{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} e internos{% endif %} no nível da organização antes de permitir ou não permitir bifurcações em um repositório específico. Para obter mais informações, consulte "[Gerenciando a política de bifurcação para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)". {% data reusables.organizations.internal-repos-enterprise %} diff --git a/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md b/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md index 4308f33ded..cb58758588 100644 --- a/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md @@ -19,17 +19,36 @@ Os proprietários da organização podem restringir a capacidade de alterar a vi Recomendamos revisar as seguintes advertências antes de alterar a visibilidade de um repositório. #### Tornar um repositório privado +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +* O {% data variables.product.product_name %} destacará bifurcações públicas do repositório público e as colocará em uma nova rede. Public forks are not made private.{% endif %} +* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} +* If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} +* Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} +* O {% data variables.product.prodname_dotcom %} não incluirá mais o repositório no {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* Anonymous Git read access is no longer available. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".{% endif %} - * O {% data variables.product.prodname_dotcom %} destacará bifurcações públicas do repositório público e as colocará em uma nova rede. As bifurcações públicas não se tornam privadas. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-public-repository-to-a-private-repository)" - {% if currentVersion == "free-pro-team@latest" %}* Se você estiver usando {% data variables.product.prodname_free_user %} para contas de usuários ou organizações, alguns recursos não estarão disponíveis no repositório depois que você alterar a visibilidade para privada. {% data reusables.gated-features.more-info %} - * Qualquer site publicado do {% data variables.product.prodname_pages %} terá sua publicação cancelada automaticamente. Se você adicionou um domínio personalizado ao site do {% data variables.product.prodname_pages %}, deverá remover ou atualizar os registros de DNS antes de tornar o repositório privado para evitar o risco de uma aquisição de domínio. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". - * O {% data variables.product.prodname_dotcom %} não incluirá mais o repositório no {% data variables.product.prodname_archive %}. Para obter mais informações, consulte "[Sobre como arquivar conteúdo e dados no {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)".{% endif %} - {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}* Anonymous Git read access is no longer available. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} + +#### Tornar um repositório interno + +{% note %} + +**Observação:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} #### Tornar um repositório público - * O {% data variables.product.prodname_dotcom %} irá destacar bifurcações privadas e transformá-las em um repositório privado independente. Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou muda de visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)" - * Se você estiver convertendo seu repositório privado em um repositório público, como parte de um movimento para a criação de um projeto de código aberto, consulte os [Guias de Código Aberto](http://opensource.guide) para obter dicas e diretrizes úteis.{% if currentVersion == "free-pro-team@latest" %} Você também pode fazer um curso grátis sobre como gerenciar um projeto de código aberto com [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Quando seu repositório é público, você também pode visualizar o perfil da comunidade do repositório para ver se os projetos atendem às práticas recomendadas de suporte aos contribuidores. Para obter mais informações, consulte "[Exibir o perfil da comunidade](/articles/viewing-your-community-profile)."{% endif %} +* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Quando seu repositório é público, você também pode visualizar o perfil da comunidade do repositório para ver se os projetos atendem às práticas recomendadas de suporte aos contribuidores. Para obter mais informações, consulte "[Exibir o perfil da comunidade](/articles/viewing-your-community-profile)."{% endif %} + +{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-anonymized-image-urls.md b/translations/pt-BR/content/github/authenticating-to-github/about-anonymized-image-urls.md index f43dcde0de..9102e49818 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-anonymized-image-urls.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-anonymized-image-urls.md @@ -8,7 +8,7 @@ versions: free-pro-team: '*' --- -Para hospedar imagens, o {% data variables.product.product_name %} usa o [Camo do projeto de código aberto](https://github.com/atmos/camo). O camo gera um proxy de URL anônimo para cada imagem que começa com `https://camo.githubusercontent.com/` e oculta os detalhes do navegador e informações relacionadas de outros usuários. +Para hospedar imagens, o {% data variables.product.product_name %} usa o [Camo do projeto de código aberto](https://github.com/atmos/camo). Camo gera um proxy de URL anônimo para cada imagem que oculta os detalhes do seu navegador e informações relacionadas de outros usuários. A URL começa `https://.githubusercontent.com/`, com subdomínios diferentes dependendo de como você fez o upload da imagem. Qualquer pessoa que recebe sua URL anônima de imagem, direta ou indiretamente, pode exibir a imagem. Para manter a privacidade de imagens confidenciais, restrinja-as a uma rede privada ou a um servidor que exija autenticação em vez de usar o Camo. diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md index 822fa6965c..03a84d4d4c 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md @@ -9,17 +9,17 @@ versions: ### Sobre autenticação no {% data variables.product.prodname_dotcom %} -To keep your account secure, you must authenticate before you can access{% if currentVersion != "github-ae@latest" %} certain{% endif %} resources on {% data variables.product.product_name %}. Ao efetuar a autenticação em {% data variables.product.product_name %}, você fornece ou confirma credenciais que são exclusivas que provam quem você declara ser. +Para manter sua conta protegida, você deve efetuar a autenticação antes de poder acessar{% if currentVersion != "github-ae@latest" %} certos{% endif %} recursos em {% data variables.product.product_name %}. Ao efetuar a autenticação em {% data variables.product.product_name %}, você fornece ou confirma credenciais que são exclusivas que provam quem você declara ser. Você pode acessar seus recursos em {% data variables.product.product_name %} de várias formas: no navegador, por meio do {% data variables.product.prodname_desktop %} ou outro aplicativo da área de trabalho, com a API ou por meio da linha de comando. Cada forma de acessar o {% data variables.product.product_name %} é compatível com diferentes modos de autenticação. -- {% if currentVersion == "github-ae@latest" %}Your identity provider (IdP){% else %}Username and password with two-factor authentication{% endif %} +- {% if currentVersion == "github-ae@latest" %}Seu provedor de identidade (IdP){% else %}Nome de usuário e senha com autenticação de dois fatores{% endif %} - Token de acesso de pessoal - Chave SSH ### Efetuar a autenticação no seu navegador -You can authenticate to {% data variables.product.product_name %} in your browser {% if currentVersion == "github-ae@latest" %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. +Você pode efetuar a autenticação no {% data variables.product.product_name %} no navegador {% if currentVersion == "github-ae@latest" %}usando o seu IdP. Para obter mais informações, consulte "[Sobre a autenticação com o logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}de formas diferentes. - **Apenas nome de usuário e senha** - Você criará uma senha ao criar sua conta de usuário em {% data variables.product.product_name %}. Recomendamos que você use um gerenciador de senhas para gerar uma senha aleatória e única. Para obter mais informações, consulte "[Criar uma senha forte](/github/authenticating-to-github/creating-a-strong-password)". @@ -38,7 +38,7 @@ Autenticar-se no {% data variables.product.prodname_dotcom %}."

### Efetuar a autenticação com a API -You can authenticate with the API in different ways. +Você pode efetuar a autenticação com a API de diferentes formas. - **Tokens de acesso pessoal** - Em algumas situações, como, por exemplo, testes, você pode usar um token de acesso pessoal para acessar a API. Usar um token de acesso pessoal permite que você revogue o acesso a qualquer momento. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index 50648ad2c8..051502db07 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Sobre a autenticação com SAML SSO -intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}' +intro: 'Você pode acessar {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}uma organização que usa o logon único SAML (SSO){% endif %}, efetuando a autenticação {% if currentVersion == "github-ae@latest" %}com o logon único SAML (SSO) {% endif %}através de um provedor de identidade (IdP).{% if currentVersion == "free-pro-team@latest" %}Para efetuar a autenticação com a API ou Git na linha de comando quando uma organização aplica o SAML SSO, você deve autorizar seu token de acesso pessoal ou chave SSH.{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on @@ -11,11 +11,11 @@ versions: {% if currentVersion == "github-ae@latest" %} -SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. +O SAML SSO permite que um proprietário corporativo realize o controle central e proteja o acesso para {% data variables.product.product_name %} a partir de um IdP do SAML. Ao acessar {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} irá redirecioná-lo para seu IdP para efetuar a autenticação. Depois de concluir a autenticação com sucesso com uma conta no IdP, este irá redirecionar você de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IpD e, em seguida, concede acesso. {% data reusables.saml.you-must-periodically-authenticate %} -If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. +Se você não puder acessar {% data variables.product.product_name %}, entre em contato com o proprietário da empresa local ou administrador para {% data variables.product.product_name %}. Você pode conseguir localizar informações de contato para sua empresa clicando em **Suporte** na parte inferior de qualquer página em {% data variables.product.product_name %}. {% data variables.product.company_short %} e {% data variables.contact.github_support %} não têm acesso ao seu IdP e não podem solucionar problemas de autenticação. {% endif %} @@ -43,5 +43,5 @@ Você deve ter uma sessão de SAML ativa toda vez que autorizar um {% data varia ### Leia mais -{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} -{% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[Sobre identidade e gerenciamento de acesso com logon único SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% if currentVersion == "github-ae@latest" %}- "[Sobre identidade e gerenciamento de acesso para a sua empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md index 833904e667..fd4100bc43 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -1,6 +1,6 @@ --- title: Sobre a verificação de assinatura de commit -intro: 'Using GPG or S/MIME, you can sign tags and commits locally. Esses commits ou tags são marcados como verificados no {% data variables.product.product_name %} para que outras pessoas tenham a segurança de que as alterações vêm de uma fonte confiável.' +intro: 'Ao usar GPG ou S/MIME, você pode assinar tags e commits localmente. Esses commits ou tags são marcados como verificados no {% data variables.product.product_name %} para que outras pessoas tenham a segurança de que as alterações vêm de uma fonte confiável.' redirect_from: - /articles/about-gpg-commit-and-tag-signatures/ - /articles/about-gpg/ diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/pt-BR/content/github/authenticating-to-github/about-githubs-ip-addresses.md index 4004d884bd..2dde6955fa 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-githubs-ip-addresses.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -12,7 +12,7 @@ versions: free-pro-team: '*' --- -Você pode recuperar uma lista de endereços IP do {% data variables.product.prodname_dotcom %} no ponto de extremidade da API [meta](https://api.github.com/meta). Para obter mais informações, consulte "[Meta](/v3/meta/)". +Você pode recuperar uma lista de endereços IP do {% data variables.product.prodname_dotcom %} no ponto de extremidade da API [meta](https://api.github.com/meta). Para obter mais informações, consulte "[Meta](/rest/reference/meta)". Esses intervalos estão na [notação CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). É possível usar uma ferramenta de conversão online, como essa [Calculadora Supernet CIDR/VLSM](http://www.subnet-calculator.com/cidr.php), para fazer a conversão de notação CIDR em intervalos de endereços IP. diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md b/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md index 76ba848f35..8da751e495 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md @@ -1,6 +1,6 @@ --- title: Sobre o SSH -intro: 'Usando o protocolo SSH, você pode se conectar a servidores e serviços remotos e se autenticar neles. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.' +intro: 'Usando o protocolo SSH, você pode se conectar a servidores e serviços remotos e se autenticar neles. Com chaves SSH, você pode conectar-se a {% data variables.product.product_name %} sem inserir seu nome de usuário e token de acesso pessoal em cada visita.' redirect_from: - /articles/about-ssh versions: diff --git a/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index cd55d7943f..f44c8b8f6c 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -24,8 +24,8 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product Se o arquivo da chave SSH tiver um nome diferente do código de exemplo, modifique o nome do arquivo para corresponder à sua configuração atual. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. ```shell - $ pbcopy < ~/.ssh/id_rsa.pub - # Copia o conteúdo do arquivo id_rsa.pub na área de transferência + $ pbcopy < ~/.ssh/id_ed25519.pub + # Copies the contents of the id_ed25519.pub file to your clipboard ``` {% tip %} @@ -51,8 +51,8 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product Se o arquivo da chave SSH tiver um nome diferente do código de exemplo, modifique o nome do arquivo para corresponder à sua configuração atual. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. ```shell - $ clip < ~/.ssh/id_rsa.pub - # Copia o conteúdo do arquivo id_rsa.pub na área de transferência + $ clip < ~/.ssh/id_ed25519.pub + # Copies the contents of the id_ed25519.pub file to your clipboard ``` {% tip %} @@ -81,8 +81,8 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product $ sudo apt-get install xclip # Baixa e instala xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`) - $ xclip -selection clipboard < ~/.ssh/id_rsa.pub - # Copies the contents of the id_rsa.pub file to your clipboard + $ xclip -selection clipboard < ~/.ssh/id_ed25519.pub + # Copies the contents of the id_ed25519.pub file to your clipboard ``` {% tip %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md b/translations/pt-BR/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md index 802cd946f4..f74dfd75cb 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Sobre a autenticação com logon único SAML -intro: 'You can authenticate to {% if currentVersion == "free-pro-team@latest" %}a {% data variables.product.product_name %} organization {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %}with SAML single sign-on (SSO){% if currentVersion == "free-pro-team@latest" %} and view your active sessions{% endif %}.' +intro: 'Você pode efetuar a autenticação em {% if currentVersion == "free-pro-team@latest" %}a organização {% data variables.product.product_name %} {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %}com o logon único SAML (SSO){% if currentVersion == "free-pro-team@latest" %} e visualizar as suas sessões ativas{% endif %}.' mapTopic: true product: '{% data reusables.gated-features.saml-sso %}' redirect_from: diff --git a/translations/pt-BR/content/github/authenticating-to-github/connecting-with-third-party-applications.md b/translations/pt-BR/content/github/authenticating-to-github/connecting-with-third-party-applications.md index 939b19d593..8c89752239 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/connecting-with-third-party-applications.md +++ b/translations/pt-BR/content/github/authenticating-to-github/connecting-with-third-party-applications.md @@ -55,10 +55,10 @@ Há vários tipos de dados que os aplicativos podem solicitar. | Tipos de dados | Descrição | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Status do commit | Você pode conceder acesso para que um aplicativo de terceiro relate seu status de commit. O acesso ao status do commit permite que os aplicativos determinem se uma compilação foi bem-sucedida em relação a um commit específico. Os apps não terão acesso ao seu código, mas poderão ler e gravar informações de status em relação a um commit específico. | -| Implantações | Deployment status access allows applications to determine if a deployment is successful against a specific commit for public and private repositories. Applications won't have access to your code. | +| Implantações | O acesso ao status de implantação permite que os aplicativos determinem se uma implantação é bem-sucedida com base em um commit específico para repositórios públicos e privados. Os aplicativos não terão acesso ao seu código. | | Gists | O acesso ao [Gist](https://gist.github.com) permite que os aplicativos leiam ou gravem em seus Gists secretos e públicos. | | Hooks | O acesso aos [webhooks](/webhooks) permite que os aplicativos leiam ou gravem configurações de hook em repositórios que você gerencia. | -| Notificações | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. No entanto, os aplicativos continuam sem poder acessar nada nos repositórios. | +| Notificações | O acesso às notificações permite que os aplicativos leiam suas notificações de {% data variables.product.product_name %}, como, por exemplo, comentários em problemas e pull requests. No entanto, os aplicativos continuam sem poder acessar nada nos repositórios. | | Organizações e equipes | O acesso às organizações e equipes permite que os apps acessem e gerenciem a associação à organização e à equipe. | | Dados pessoais do usuário | Os dados do usuário incluem informações encontradas no seu perfil de usuário, como nome, endereço de e-mail e localização. | | Repositórios | As informações de repositório incluem os nomes dos contribuidores, os branches que você criou e os arquivos reais dentro do repositório. Os aplicativos podem solicitar acesso para repositórios públicos ou privados em um nível amplo de usuário. | diff --git a/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md index ed678f4bf3..91745a82b6 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -12,7 +12,7 @@ versions: github-ae: '*' --- -Os tokens de acesso pessoal (PATs) são uma alternativa para o uso de senhas para autenticação no {% data variables.product.product_name %} ao usar a [API do GitHub](/v3/auth/#via-oauth-and-personal-access-tokens) ou a [linha de comando](#using-a-token-on-the-command-line). +Os tokens de acesso pessoal (PATs) são uma alternativa para o uso de senhas para autenticação no {% data variables.product.product_name %} ao usar a [API do GitHub](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) ou a [linha de comando](#using-a-token-on-the-command-line). {% if currentVersion == "free-pro-team@latest" %}Se você deseja usar um PAT para acessar recursos pertencentes a uma organização que usa SAML SSO, você deve autorizar o PAT. Para mais informações consulte "[Sobre autenticação com logon único SAML](/articles/about-authentication-with-saml-single-sign-on)" e "[Autorizando um token de acesso pessoal para uso com logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 0abf639d7a..a0bee20473 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -24,7 +24,7 @@ Caso não queira reinserir sua frase secreta cada vez que usa a chave SSH, é po ``` {% note %} - **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use: + **Observação:** Se você estiver usando um sistema legado que não é compatível com o algoritmo Ed25519, use: ```shell $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` @@ -89,7 +89,7 @@ Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, v $ touch ~/.ssh/config ``` - * Open your `~/.ssh/config` file, then modify the file, replacing `~/.ssh/id_ed25519` if you are not using the default location and name for your `id_ed25519` key. + * Abre o seu arquivo `~/.ssh/config` file, then modify the file, replacing `~/.ssh/id_ed25519` se você não estiver usando o local e nome padrão para a sua chave `id_ed25519`. ``` Host * @@ -98,13 +98,19 @@ Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, v IdentityFile ~/.ssh/id_ed25519 ``` + {% note %} + + **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line. + + {% endnote %} + 3. Adicione sua chave SSH privada ao ssh-agent e armazene sua frase secreta no keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell $ ssh-add -K ~/.ssh/id_ed25519 ``` {% note %} - **Observação:** a opção `-K` está presente na versão padrão da Apple do `ssh-add` e armazena a frase secreta no keychain quando você adiciona uma chave SSH ao ssh-agent. + **Observação:** a opção `-K` está presente na versão padrão da Apple do `ssh-add` e armazena a frase secreta no keychain quando você adiciona uma chave SSH ao ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. Caso não tenha a versão standard da Apple instalada, você poderá receber uma mensagem de erro. Para obter mais informações sobre como resolver esse erro, consulte "[Erro: ssh-add: opção ilícita -- K](/articles/error-ssh-add-illegal-option-k)". diff --git a/translations/pt-BR/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md b/translations/pt-BR/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md index f225fe1a38..89c37b5330 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md +++ b/translations/pt-BR/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -These are {% data variables.product.prodname_dotcom %}'s public key fingerprints: +Estas são as impressões digitais de chave pública de {% data variables.product.prodname_dotcom %}: - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) - `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA) diff --git a/translations/pt-BR/content/github/authenticating-to-github/index.md b/translations/pt-BR/content/github/authenticating-to-github/index.md index 58ae2c0692..d8a94860f8 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/index.md +++ b/translations/pt-BR/content/github/authenticating-to-github/index.md @@ -1,7 +1,7 @@ --- title: Autenticar com o GitHub shortTitle: Autenticação -intro: 'Keep your account and data secure with features like {% if currentVersion != "github-ae@latest" %}two-factor authentication, {% endif %}SSH{% if currentVersion != "github-ae@latest" %},{% endif %} and commit signature verification.' +intro: 'Mantenha sua conta e dados protegidos com recursos como {% if currentVersion != "github-ae@latest" %}autenticação de dois fatores, {% endif %}SSH{% if currentVersion ! "github-ae@latest" %},{% endif %} e verificação de assinatura do commit.' redirect_from: - /categories/56/articles/ - /categories/ssh/ diff --git a/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md b/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md index 4970bdd54d..183fecb7f3 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md +++ b/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md @@ -1,6 +1,6 @@ --- -title: Proteger sua conta e dados -intro: 'Para proteger suas informações pessoais, você deve manter sua conta {% data variables.product.product_name %} e quaisquer dados associados a ela seguros.' +title: Keeping your account and data secure +intro: 'To protect your personal information, you should keep both your {% data variables.product.product_name %} account and any associated data secure.' mapTopic: true redirect_from: - /articles/keeping-your-account-and-data-secure diff --git a/translations/pt-BR/content/github/authenticating-to-github/managing-commit-signature-verification.md b/translations/pt-BR/content/github/authenticating-to-github/managing-commit-signature-verification.md index 326ea4c476..f5ca5f2c74 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/managing-commit-signature-verification.md +++ b/translations/pt-BR/content/github/authenticating-to-github/managing-commit-signature-verification.md @@ -1,6 +1,6 @@ --- title: Gerenciar a verificação de assinatura de commit -intro: 'You can sign your work locally using GPG or S/MIME. {% data variables.product.product_name %} irá verificar essas assinaturas para que outras pessoas saibam que seus commits vêm de uma fonte de confiança. {% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} irá assinar automaticamente os commits que você fizer usando a interface da web.{% data variables.product.product_name %}{% endif %}' +intro: 'Você pode assinar seu trabalho localmente usando GPG ou S/MIME. {% data variables.product.product_name %} irá verificar essas assinaturas para que outras pessoas saibam que seus commits vêm de uma fonte de confiança. {% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} irá assinar automaticamente os commits que você fizer usando a interface da web.{% data variables.product.product_name %}{% endif %}' redirect_from: - /articles/generating-a-gpg-key/ - /articles/signing-commits-with-gpg/ diff --git a/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md index 264a3a22b0..51f7b922a7 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -1,6 +1,7 @@ --- -title: Reviewing your security log -intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you. +title: Revisar seus logs de segurança +intro: Você pode revisar o log de segurança da sua conta de usuário para entender melhor as ações que você realizou e ações realizadas por outras pessoas que envolvem você. +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/reviewing-your-security-log versions: @@ -9,242 +10,243 @@ versions: github-ae: '*' --- -### Accessing your security log +### Acessar o log de segurança -The security log lists all actions performed within the last 90 days{% if currentVersion ver_lt "enterprise-server@2.20" %}, up to 50{% endif %}. +O log de segurança lista todas as ações realizadas nos últimos 90 dias{% if currentVersion ver_lt "enterprise-server@2.20" %}, até 50{% endif %}. {% data reusables.user_settings.access_settings %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -2. In the user settings sidebar, click **Security log**. - ![Security log tab](/assets/images/help/settings/audit-log-tab.png) +2. Na barra lateral de configurações do usuário, clique em **log de segurança**. ![Aba do log de segurança](/assets/images/help/settings/audit-log-tab.png) {% else %} {% data reusables.user_settings.security %} -3. Under "Security history," your log is displayed. - ![Security log](/assets/images/help/settings/user_security_log.png) -4. Click on an entry to see more information about the event. - ![Security log](/assets/images/help/settings/user_security_history_action.png) +3. O log é exibido em "Security history" (Histórico de segurança). ![Log de segurança](/assets/images/help/settings/user_security_log.png) +4. Clique em uma entrada para ver mais informações sobre o evento. ![Log de segurança](/assets/images/help/settings/user_security_history_action.png) {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### Searching your security log +### Pesquisar no seu registro de segurança {% data reusables.audit_log.audit-log-search %} -#### Search based on the action performed +#### Pesquisar com base na ação {% else %} -### Understanding events in your security log - -Actions listed in your security log are grouped within the following categories: +### Entender eventos no seu log de segurança {% endif %} -| Category Name | Description -|------------------|-------------------{% if currentVersion == "free-pro-team@latest" %} -| `account_recovery_token` | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods). -| `billing` | Contains all activities related to your billing information. -| `marketplace_agreement_signature` | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. -| `marketplace_listing` | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %} -| `oauth_access` | Contains all activities related to [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) you've connected with.{% if currentVersion == "free-pro-team@latest" %} -| `payment_method` | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %} -| `profile_picture` | Contains all activities related to your profile picture. -| `project` | Contains all activities related to project boards. -| `public_key` | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account). -| `repo` | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %} -| `sponsors` | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `team` | Contains all activities related to teams you are a part of.{% endif %}{% if currentVersion != "github-ae@latest" %} -| `two_factor_authentication` | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %} -| `user` | Contains all activities related to your account. +Os eventos listados no seu registro de segurança são acionados por suas ações. As ações são agrupadas nas seguintes categorias: -A description of the events within these categories is listed below. +| Categoria | Descrição | +| -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`account_recovery_token`](#account_recovery_token-category-actions) | Contém todas as atividade relacionadas a [adicionar um token de recuperação](/articles/configuring-two-factor-authentication-recovery-methods). | +| [`cobrança`](#billing-category-actions) | Contém todas as atividades relacionadas às suas informações de cobrança. | +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contém todas as atividades relacionadas à assinatura do Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}. | +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contém todas as atividades relacionadas aos aplicativos listados no {% data variables.product.prodname_marketplace %}.{% endif %} +| [`oauth_access`](#oauth_access-category-actions) | Contém todas as atividades relacionadas a [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) com as quais você se conectou.{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contém todas as atividades relacionadas ao pagamento da sua assinatura do {% data variables.product.prodname_dotcom %}.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contém todas as atividades relacionadas à imagem do seu perfil. | +| [`project`](#project-category-actions) | Contém todas as atividades relacionadas aos quadros de projeto. | +| [`public_key`](#public_key-category-actions) | Contém todas as atividades relacionadas às [chaves SSH públicas](/articles/adding-a-new-ssh-key-to-your-github-account). | +| [`repo`](#repo-category-actions) | Contém todas as atividades relacionadas aos repositórios que você possui.{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | Contém todos os eventos relacionados a {% data variables.product.prodname_sponsors %} e botões de patrocinador (veja "[Sobre {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" e "[ Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| [`equipe`](#team-category-actions) | Contém todas as atividades relacionadas a equipes das quais você faz parte.{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contem todas as atividades relacionadas a [autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %} +| [`usuário`](#user-category-actions) | Contém todas as atividades relacionadas à sua conta. | {% if currentVersion == "free-pro-team@latest" %} -#### The `account_recovery_token` category - -| Action | Description -|------------------|------------------- -| confirm | Triggered when you successfully [store a new token with a recovery provider](/articles/configuring-two-factor-authentication-recovery-methods). -| recover | Triggered when you successfully [redeem an account recovery token](/articles/recovering-your-account-if-you-lose-your-2fa-credentials). -| recover_error | Triggered when a token is used but {% data variables.product.prodname_dotcom %} is not able to validate it. - -#### The `billing` category - -| Action | Description -|------------------|------------------- -| change_billing_type | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}. -| change_email | Triggered when you [change your email address](/articles/changing-your-primary-email-address). - -#### The `marketplace_agreement_signature` category - -| Action | Description -|------------------|------------------- -| create | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. - -#### The `marketplace_listing` category - -| Action | Description -|------------------|------------------- -| approve | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. -| create | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. -| delist | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. -| redraft | Triggered when your listing is sent back to draft state. -| reject | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. - -{% endif %} - -#### The `oauth_access` category - -| Action | Description -|------------------|------------------- -| create | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps). -| destroy | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations). - -{% if currentVersion == "free-pro-team@latest" %} - -#### The `payment_method` category - -| Action | Description -|------------------|------------------- -| clear | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed. -| create | Triggered when a new payment method is added, such as a new credit card or PayPal account. -| update | Triggered when an existing payment method is updated. - -{% endif %} - -#### The `profile_picture` category - -| Action | Description -|------------------|------------------- -| update | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/). - -#### The `project` category - -| Action | Description -|--------------------|--------------------- -| `create` | Triggered when a project board is created. -| `rename` | Triggered when a project board is renamed. -| `update` | Triggered when a project board is updated. -| `delete` | Triggered when a project board is deleted. -| `link` | Triggered when a repository is linked to a project board. -| `unlink` | Triggered when a repository is unlinked from a project board. -| `project.access` | Triggered when a project board's visibility is changed. -| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed. - -#### The `public_key` category - -| Action | Description -|------------------|------------------- -| create | Triggered when you [add a new public SSH key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). -| delete | Triggered when you [remove a public SSH key to your {% data variables.product.product_name %} account](/articles/reviewing-your-ssh-keys). - -#### The `repo` category - -| Action | Description -|------------------|------------------- -| access | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa). -| add_member | Triggered when a {% data variables.product.product_name %} user is {% if currentVersion == "free-pro-team@latest" %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository. -| add_topic | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. -| archived | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| config.disable_anonymous_git_access | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| config.enable_anonymous_git_access | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| config.lock_anonymous_git_access | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). -| config.unlock_anonymous_git_access | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} -| create | Triggered when [a new repository is created](/articles/creating-a-new-repository). -| destroy | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} -| disable | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| enable | Triggered when a repository is re-enabled.{% endif %} -| remove_member | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). -| remove_topic | Triggered when a repository owner removes a topic from a repository. -| rename | Triggered when [a repository is renamed](/articles/renaming-a-repository). -| transfer | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). -| transfer_start | Triggered when a repository transfer is about to occur. -| unarchived | Triggered when a repository owner unarchives a repository. - -{% if currentVersion == "free-pro-team@latest" %} -#### The `sponsors` category - -| Action | Description -|------------------|------------------- -| repo_funding_link_button_toggle | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| repo_funding_links_file_action | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| sponsor_sponsorship_cancel | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| sponsor_sponsorship_create | Triggered when you sponsor a developer (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor#sponsoring-a-developer)") -| sponsor_sponsorship_preference_change | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/articles/managing-your-sponsorship)") -| sponsor_sponsorship_tier_change | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| sponsored_developer_approve | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| sponsored_developer_create | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| sponsored_developer_profile_update | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") -| sponsored_developer_request_approval | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| sponsored_developer_tier_description_update | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") -| sponsored_developer_update_newsletter_send | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)") -| waitlist_invite_sponsored_developer | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| waitlist_join | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -#### The `successor_invitation` category - -| Action | Description -|------------------|------------------- -| accept | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| cancel | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| create | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| decline | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| revoke | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -{% endif %} - -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - -#### The `team` category - -| Action | Description -|------------------|------------------- -| add_member | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team). -| add_repository | Triggered when a team you are a member of is given control of a repository. -| create | Triggered when a new team in an organization you belong to is created. -| destroy | Triggered when a team you are a member of is deleted from the organization. -| remove_member | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of. -| remove_repository | Triggered when a repository is no longer under a team's control. - -{% endif %} - -{% if currentVersion != "github-ae@latest" %} -#### The `two_factor_authentication` category - -| Action | Description -|------------------|------------------- -| enabled | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled. -| disabled | Triggered when two-factor authentication is disabled. -{% endif %} - -#### The `user` category - -| Action | Description -|--------------------|--------------------- -| add_email | Triggered when you {% if currentVersion != "github-ae@latest" %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}. -| create | Triggered when you create a new user account. -| remove_email | Triggered when you remove an email address. -| rename | Triggered when you rename your account.{% if currentVersion != "github-ae@latest" %} -| change_password | Triggered when you change your password. -| forgot_password | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} -| login | Triggered when you log in to {% data variables.product.product_location %}. -| failed_login | Triggered when you failed to log in successfully.{% if currentVersion != "github-ae@latest" %} -| two_factor_requested | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %} -| show_private_contributions_count | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). -| hide_private_contributions_count | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion == "free-pro-team@latest" %} -| report_content | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/articles/reporting-abuse-or-spam).{% endif %} - -#### The `user_status` category - -| Action | Description -|--------------------|--------------------- -| update | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)." -| destroy | Triggered when you clear the status on your profile. - -{% if currentVersion == "free-pro-team@latest" %} - -### Exporting your security log +### Exportar o seu log de segurança {% data reusables.audit_log.export-log %} {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} + +### Ações do log de segurança + +Uma visão geral de algumas das ações mais comuns que são registradas como eventos no log de segurança. + +{% if currentVersion == "free-pro-team@latest" %} + +#### `account_recovery_token` ações de categoria + +| Ação | Descrição | +| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | +| `confirm` | Acionada quando você [armazena um novo token com um provedor de recuperação](/articles/configuring-two-factor-authentication-recovery-methods). | +| `recover` | Acionada quando você [resgata um token de recuperação de conta](/articles/recovering-your-account-if-you-lose-your-2fa-credentials). | +| `recover_error` | Acionada quando um token é usado, mas o {% data variables.product.prodname_dotcom %} não consegue validá-lo. | + +#### ações de categoria de `cobrança` + +| Ação | Descrição | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| `change_billing_type` | Acionada quando você [altera o modo de pagamento](/articles/adding-or-editing-a-payment-method) do {% data variables.product.prodname_dotcom %}. | +| `change_email` | Acionada quando você [altera o endereço de e-mail](/articles/changing-your-primary-email-address). | + +#### ações de categoria de `marketplace_agreement_signature` + +| Ação | Descrição | +| -------- | ------------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando você assina o Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}. | + +#### ações de categoria de `marketplace_listing` + +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------ | +| `aprovar` | Acionada quando sua lista é aprovada para inclusão no {% data variables.product.prodname_marketplace %}. | +| `create` | Acionada quando você cria uma lista para seu app no {% data variables.product.prodname_marketplace %}. | +| `delist` | Acionada quando sua lista é removida do {% data variables.product.prodname_marketplace %}. | +| `redraft` | Triggered when your listing is sent back to draft state. | +| `reject` | Acionada quando sua lista não é aprovada para inclusão no {% data variables.product.prodname_marketplace %}. | + +{% endif %} + +#### ações de categoria`Oauth_access` + +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Acionada quando você [concede acesso a um {% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps). | +| `destroy` | Acionada quando você [revoga o acesso de um {% data variables.product.prodname_oauth_app %}a sua conta](/articles/reviewing-your-authorized-integrations). | + +{% if currentVersion == "free-pro-team@latest" %} + +#### ações de categoria `payment_method` + +| Ação | Descrição | +| -------- | ---------------------------------------------------------------------------------------------------------- | +| `clear` | Acionada quando [um método de pagamento](/articles/removing-a-payment-method) registrado é removido. | +| `create` | Acionada quando um novo método de pagamento, como um novo cartão de crédito ou conta PayPal, é adicionado. | +| `update` | Acionada quando um método de pagamento é atualizado. | + +{% endif %} + +#### ações de categoria `profile_picture` + +| Ação | Descrição | +| -------- | --------------------------------------------------------------------------------------------------------- | +| `update` | Acionada quando você [configura ou atualiza sua foto do perfil](/articles/setting-your-profile-picture/). | + +#### ações de categoria `project` + +| Ação | Descrição | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | +| `access` | Acionada quando a visibilidade de um quadro de projeto é alterada. | +| `create` | Acionada quando um quadro de projeto é criado. | +| `rename` | Acionada quando um quadro de projeto é renomeado. | +| `update` | Acionada quando um quadro de projeto é atualizado. | +| `delete` | Acionada quando um quadro de projeto é excluído. | +| `link` | Acionada quando um repositório é vinculado a um quadro de projeto. | +| `unlink` | Acionada quando um repositório é desvinculado de um quadro de projeto. | +| `update_user_permission` | Acionada quando um colaborador externo é adicionado ou removido de um quadro de projeto ou tem seu nível de permissão alterado. | + +#### ações de categoria `public_key` + +| Ação | Descrição | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando você [adiciona uma nova chave SSH pública a sua conta do {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account). | +| `delete` | Acionada quando você [remove uma chave SSH pública da sua conta do {% data variables.product.product_name %}](/articles/reviewing-your-ssh-keys). | + +#### ações de categoria `repo` + +| Ação | Descrição | +| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | Acionada quando um repositório seu é [alterado de "privado" para "público"](/articles/making-a-private-repository-public) (ou vice-versa). | +| `add_member` | Acionada quando um usuário de {% data variables.product.product_name %} é {% if currentVersion == "free-pro-team@latest" %}[convidado a ter acesso de colaboração](/articles/inviting-collaborators-to-a-personal-repository){% else %}[dado acesso de colaboração](/articles/inviting-collaborators-to-a-personal-repository){% endif %} a um repositório. | +| `add_topic` | Acionada quando um proprietário do repositório [adiciona um tópico](/articles/classifying-your-repository-with-topics) a um repositório. | +| `archived` | Acionada quando um proprietário do repositório [arquiva um repositório](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} +| `config.disable_anonymous_git_access` | Acionada quando um [acesso de leitura anônimo do Git é desabilitado](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) em um repositório público. | +| `config.enable_anonymous_git_access` | Acionada quando um [acesso de leitura anônimo do Git é habilitado](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) em um repositório público. | +| `config.lock_anonymous_git_access` | Acionada quando a [configuração de acesso de leitura anônimo do Git de um repositório é bloqueada](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | +| `config.unlock_anonymous_git_access` | Acionada quando a [configuração de acesso de leitura anônimo do Git de um repositório é desbloqueada](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `create` | Acionada quando [um repositório é criado](/articles/creating-a-new-repository). | +| `destroy` | Acionada quando [um repositório é excluído](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `desabilitar` | Acionada quando um repositório é desabilitado (por exemplo, por [fundos insuficientes](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `habilitar` | Acionada quando um repositório é habilitado novamente.{% endif %} +| `remove_member` | Acionada quando um usuário do {% data variables.product.product_name %} é [removido de um repositório como um colaborador](/articles/removing-a-collaborator-from-a-personal-repository). | +| `remove_topic` | Acionada quando um proprietário do repositório remove um tópico de um repositório. | +| `rename` | Acionada quando [um repositório é renomeado](/articles/renaming-a-repository). | +| `transferir` | Acionada quando [um repositório é transferido](/articles/how-to-transfer-a-repository). | +| `transfer_start` | Acionada quando uma transferência de repositório está prestes a ocorrer. | +| `unarchived` | Acionada quando um proprietário do repositório desarquiva um repositório. | + +{% if currentVersion == "free-pro-team@latest" %} +#### ações de categoria de `patrocinadores` + +| Ação | Descrição | +| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo_funding_link_button_toggle` | Acionada quando você habilita ou desabilita um botão de patrocinador no repositório (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create` | Acionadas quando você patrocina um desenvolvedor (consulte "[Patrocinar um colaborador de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor#sponsoring-a-developer)") | +| `sponsor_sponsorship_preference_change` | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/articles/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsored_developer_approve` | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (ver "[Configuração de {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `sponsored_developer_create` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é criada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `sponsored_developer_profile_update` | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval` | Acionada quando você enviar seu aplicativo para {% data variables.product.prodname_sponsors %} para aprovação (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `sponsored_developer_tier_description_update` | Acionada quando você altera a descrição de um nível de patrocínio (consulte "[Alterar níveis de patrocínio](/articles/changing-your-sponsorship-tiers)") | +| `sponsored_developer_update_newsletter_send` | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/articles/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer` | Acionada quando você é convidado a juntar-se a {% data variables.product.prodname_sponsors %} a partir da lista de espera (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `waitlist_join` | Acionada quando você se junta à lista de espera para tornar-se um desenvolvedor patrocinado (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### ações de categoria `successor_invitation` + +| Ação | Descrição | +| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `aceitar` | Acionada quando você aceita um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da conta do seu usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `cancelar` | Acionado quando você cancela um convite de sucessão (consulte"[Manter a continuidade da propriedade dos repositórios da conta do seu usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `create` | Acionado quando você cria um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da conta do usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `recusar` | Acionado quando você recusa um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da conta do usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `revogar` | Acionado quando você revoga um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +{% endif %} + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + +#### ações de categoria de `equipe` + +| Ação | Descrição | +| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member` | Acionada quando um integrante de uma organização à qual você pertence [adiciona você em uma equipe](/articles/adding-organization-members-to-a-team). | +| `add_repository` | Acionada quando uma equipe da qual você faz parte recebe o controle de um repositório. | +| `create` | Acionada quando uma equipe é criada em uma organização à qual você pertence. | +| `destroy` | Acionada quando uma equipe da qual você faz parte é excluída da organização. | +| `remove_member` | Acionada quando um integrante de uma organização é [removido de uma equipe](/articles/removing-organization-members-from-a-team) da qual você faz parte. | +| `remove_repository` | Acionada quando um repositório deixa de ser controlado por uma equipe. | + +{% endif %} + +{% if currentVersion != "github-ae@latest" %} +#### ações de categoria`two_factor_authentication` + +| Ação | Descrição | +| ---------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| `enabled` | Acionada quando a [autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) é habilitada. | +| `disabled` | Acionada quando a autenticação de dois fatores é desabilitada. | +{% endif %} + +#### ações de categoria `user` + +| Ação | Descrição | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_email` | Acionada quando você {% if currentVersion != "github-ae@latest" %}[adiciona um novo endereço de email](/articles/changing-your-primary-email-address){% else %}adiciona um novo endereço de email{% endif %}. | +| `create` | Acionada quando você cria uma nova conta de usuário.{% if currentVersion != "github-ae@latest" %} +| `change_password` | Acionada quando você altera a senha. | +| `forgot_password` | Acionada quando você solicita [a redefinição da senha](/articles/how-can-i-reset-my-password).{% endif %} +| `hide_private_contributions_count` | Acionada quando você [oculta as contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | +| `login` | Acionada quando você faz login no {% data variables.product.product_location %}. | +| `failed_login` | Acionada quando você não consegue fazer login. | +| `remove_email` | Acionada quando você remove um endereço de e-mail. | +| `rename` | Acionada quando você renomeia a conta.{% if currentVersion == "free-pro-team@latest" %} +| `report_content` | Acionada quando você [denuncia um problema ou uma pull request, ou um comentário em um problema, uma pull request, ou commit](/articles/reporting-abuse-or-spam).{% endif %} +| `show_private_contributions_count` | Acionada quando você [divulga contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} +| `two_factor_requested` | Acionada quando {% data variables.product.product_name %} pede a você por [seu código de autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication).{% endif %} + +#### ações de categoria `user_status` + +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `update` | Acionada quando você configura ou altera o status no perfil. Para obter mais informações, consulte "[Configurar um status](/articles/personalizing-your-profile/#setting-a-status)". | +| `destroy` | Acionada quando você remove o status no perfil. | + + diff --git a/translations/pt-BR/content/github/authenticating-to-github/signing-commits.md b/translations/pt-BR/content/github/authenticating-to-github/signing-commits.md index 234002448a..cdddaf6e8b 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/signing-commits.md +++ b/translations/pt-BR/content/github/authenticating-to-github/signing-commits.md @@ -1,6 +1,6 @@ --- title: Assinar commits -intro: You can sign commits locally using GPG or S/MIME. +intro: Você pode assinar commits localmente usando GPG ou S/MIME. redirect_from: - /articles/signing-commits-and-tags-using-gpg/ - /articles/signing-commits-using-gpg/ diff --git a/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md index 2970b800c2..93aa14be43 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md +++ b/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md @@ -1,6 +1,6 @@ --- title: Informar ao Git sobre a chave de assinatura -intro: "To sign commits locally, you need to inform Git that there's a GPG or X.509 key you'd like to use." +intro: "Para assinar commits localmente, você precisa informar ao Git que há uma chave GPG ou X.509 que você gostaria de usar." redirect_from: - /articles/telling-git-about-your-gpg-key/ - /articles/telling-git-about-your-signing-key diff --git a/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md index 7c167c514b..127c351dea 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md +++ b/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md @@ -1,6 +1,6 @@ --- title: Atualizar credenciais de acesso do GitHub -intro: '{% data variables.product.product_name %} credentials include{% if currentVersion != "github-ae@latest" %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Se houver necessidade, você mesmo pode redefinir todas essas credenciais de acesso.' +intro: 'As credenciais de {% data variables.product.product_name %} incluem{% if currentVersion ! "github-ae@latest" %} não apenas sua senha, mas também{% endif %} os tokens de acesso, Chaves SSH e tokens do aplicativo da API que você usa para se comunicar com {% data variables.product.product_name %}. Se houver necessidade, você mesmo pode redefinir todas essas credenciais de acesso.' redirect_from: - /articles/rolling-your-credentials/ - /articles/how-can-i-reset-my-password/ diff --git a/translations/pt-BR/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md b/translations/pt-BR/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md index 119a6b2cac..7194c19e93 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md +++ b/translations/pt-BR/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md @@ -11,7 +11,11 @@ versions: Depois que você cria modelos de problema e pull request no repositório, os contribuidores podem usá-los para abrir problemas ou descrever as alterações propostas nas respectivas pull requests, de acordo com as diretrizes de contribuição do repositório. Para obter mais informações sobre como adicionar diretrizes de contribuição a um repositório, consulte "[Configurar diretrizes para contribuidores de repositório](/articles/setting-guidelines-for-repository-contributors)". -You can create default issue and pull request templates for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +You can create default issue and pull request templates for your organization or user account. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} ### Modelos de problema diff --git a/translations/pt-BR/content/github/building-a-strong-community/about-team-discussions.md b/translations/pt-BR/content/github/building-a-strong-community/about-team-discussions.md index 53072cd01a..eea10923a9 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/about-team-discussions.md +++ b/translations/pt-BR/content/github/building-a-strong-community/about-team-discussions.md @@ -27,7 +27,7 @@ Quando alguém posta ou responde a uma discussão pública na página de uma equ {% tip %} -**Dica:** dependendo das suas configurações de notificação, você receberá atualizações por e-mail, pela página de notificações da web no {% data variables.product.product_name %}, ou por ambos. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." +**Dica:** dependendo das suas configurações de notificação, você receberá atualizações por e-mail, pela página de notificações da web no {% data variables.product.product_name %}, ou por ambos. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Sobre notificações de e-mail](/github/receiving-notifications-about-activity-on-github/about-email-notifications)e "[Sobre notificações da web](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." {% endtip %} @@ -35,7 +35,7 @@ Por padrão, se seu nome de usuário for mencionado em uma discussão de equipe, Para desativar notificações de discussões de equipe, você pode cancelar a assinatura de uma postagem de discussão específica ou alterar as configurações de notificação para cancelar a inspeção ou ignorar completamente discussões de uma equipe específica. É possível assinar para receber notificações de uma postagem de discussão específica se você estiver cancelando a inspeção de discussões dessa equipe. -For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)." +Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Visualizar suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Assinar e cancelar a assinatura das notificações](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" e "[Equipes aninhadas](/articles/about-teams/#nested-teams)". ### Leia mais diff --git a/translations/pt-BR/content/github/building-a-strong-community/about-wikis.md b/translations/pt-BR/content/github/building-a-strong-community/about-wikis.md index e8738e9cb3..000344a0b7 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/about-wikis.md +++ b/translations/pt-BR/content/github/building-a-strong-community/about-wikis.md @@ -15,9 +15,9 @@ Cada repositório do {% data variables.product.product_name %} é equipado com u Com wikis, é possível gravar conteúdo assim como em qualquer outro lugar no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Começando a escrever e formatar no {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)". Usamos [nossa biblioteca de markup de código aberto](https://github.com/github/markup) para converter diferentes formatos em HTML, de modo que seja possível optar por escrever em markdown ou qualquer outro formato compatível. -Os wikis estão disponíveis para o público em repositórios públicos e limitados a pessoas com acesso ao repositório em repositórios privados. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/articles/setting-repository-visibility)". +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}If you create a wiki in a public repository, the wiki is available to {% if enterpriseServerVersions contains currentVersion %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in an internal or private repository, {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}people{% elsif currentVersion == "github-ae@latest" %}enterprise members{% endif %} with access to the repository can also access the wiki. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/articles/setting-repository-visibility)". -Você pode editar wikis diretamente no {% data variables.product.product_name %} ou editar arquivos wiki localmente. Por padrão, somente pessoas com acesso de gravação ao seu repositório podem fazer alterações nos wikis, embora você possa permitir que todos no {% data variables.product.product_name %} contribuam com um wiki em um repositório público. Para obter mais informações, consulte "[Alterar permissões de acesso para wikis](/articles/changing-access-permissions-for-wikis)". +Você pode editar wikis diretamente no {% data variables.product.product_name %} ou editar arquivos wiki localmente. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.product.product_location %} to contribute to a wiki in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository. Para obter mais informações, consulte "[Alterar permissões de acesso para wikis](/articles/changing-access-permissions-for-wikis)". ### Leia mais diff --git a/translations/pt-BR/content/github/building-a-strong-community/adding-a-license-to-a-repository.md b/translations/pt-BR/content/github/building-a-strong-community/adding-a-license-to-a-repository.md index c589f37378..96f7c172a9 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/adding-a-license-to-a-repository.md +++ b/translations/pt-BR/content/github/building-a-strong-community/adding-a-license-to-a-repository.md @@ -6,7 +6,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '*' - github-ae: '*' --- Se você incluir uma licença detectável no seu repositório, as pessoas que o visitam o verão no topo da página do repositório. Para ler o arquivo de licença inteiro, clique no nome da licença. diff --git a/translations/pt-BR/content/github/building-a-strong-community/adding-support-resources-to-your-project.md b/translations/pt-BR/content/github/building-a-strong-community/adding-support-resources-to-your-project.md index 6a27df12db..70d05686ec 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/adding-support-resources-to-your-project.md +++ b/translations/pt-BR/content/github/building-a-strong-community/adding-support-resources-to-your-project.md @@ -13,7 +13,11 @@ Para direcionar pessoas a recursos de suporte específicos, é possível adicion ![Diretrizes de suporte](/assets/images/help/issues/support_guidelines_in_issue.png) -You can create default support resources for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +You can create default support resources for your organization or user account. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} {% tip %} diff --git a/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 398985d286..81c18a34f2 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -20,7 +20,7 @@ Você pode bloquear um usuário nas configurações da sua conta ou no perfil do Quando você bloqueia um usuário: - O usuário para de seguir você - O usuário para de inspecionar e deixa de fixar seus repositórios -- The user is not able to join any organizations you are an owner of +- O usuário não pode participar de nenhuma organização da qual você é proprietário - As estrelas e atribuições de problema do usuário são removidas dos repositórios - As bifurcações dos seus repositórios são excluídas - Você exclui qualquer bifurcação dos repositórios do usuário diff --git a/translations/pt-BR/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md b/translations/pt-BR/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md index fc990a72be..8b7c7c01ec 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md +++ b/translations/pt-BR/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md @@ -10,10 +10,16 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + {% data reusables.repositories.default-issue-templates %} +{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} + ### Criando modelos de problemas + {% endif %} {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md b/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md index bcae1fbbf1..98b56edfdb 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md +++ b/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md @@ -7,43 +7,42 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '*' - github-ae: '*' --- ### Sobre arquivos padrão de integridade da comunidade -You can add default community health files to the root of a public repository called `.github` that is owned by an organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. +Você pode adicionar arquivos padrão de saúde da comunidade à raiz de um repositório público denominado `.github` pertencente a uma organização{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} ou conta de usuário{% endif %}. {% data variables.product.product_name %} usará e exibirá arquivos padrão para qualquer repositório público de propriedade da conta que não tenha seu próprio arquivo desse tipo em nenhum dos seguintes locais: - a raiz do repositório - a pasta `.github` - a pasta `docs` -Por exemplo, qualquer pessoa que cria um problema ou uma pull request em um repositório público que não tem o próprio arquivo CONTRIBUTING verá um link para o arquivo CONTRIBUTING padrão. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used. +Por exemplo, qualquer pessoa que cria um problema ou uma pull request em um repositório público que não tem o próprio arquivo CONTRIBUTING verá um link para o arquivo CONTRIBUTING padrão. Se um repositório tiver arquivos na usa própria pasta `.github/ISSUE_TEMPLATE`{% if currentVersion == "free-pro-team@latest" or currentversion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}, incluindo modelos de problema ou um arquivo *config.yml*,{% endif %} nenhum conteúdo da pasta padrão `.github/ISSUE_TEMPLATE` será usado. Os arquivos padrão não são incluídos em clones, pacotes ou downloads de repositórios individuais, pois eles são armazenados somente no repositório `.github`. ### Tipos de arquivo compatíveis -You can create defaults in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} for the following community health files: +Você pode criar padrões na sua organização{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} ou conta de usuário{% endif %} para os seguintes arquivos de saúde da comunidade: -| Arquivo de integridade da comunidade | Descrição | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| *CODE_OF_CONDUCT.md* | Um arquivo CODE_OF_CONDUCT define os padrões de como ingressar em uma comunidade. Para obter mais informações, consulte "[Adicionar um código de conduta ao projeto](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %} -| *CONTRIBUTING.md* | Um arquivo CONTRIBUTING comunica como as pessoas devem contribuir com o seu projeto. Para obter mais informações, consulte "[Definir diretrizes para contribuidores de repositórios](/articles/setting-guidelines-for-repository-contributors/)".{% if currentVersion == "free-pro-team@latest" %} -| *FUNDING.yml* | Um arquivo FUNDING exibe um botão de patrocinador no repositório para aumentar a visibilidade das opções de financiamento para seu projeto de código aberto. Para obter mais informações, consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %} -| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Os modelos de problema e pull request personalizam e padronizam as informações que você deseja que contribuidores incluam quando eles abrem problemas e pull requests no seu repositório. Para obter mais informações, consulte "[Sobre problemas e modelos de pull request](/articles/about-issue-and-pull-request-templates/).{% if currentVersion == "free-pro-team@latest" %} -| *SECURITY.md* | Um arquivo SECURITY fornece instruções sobre como relatar com responsabilidade uma vulnerabilidade de segurança em seu projeto. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/articles/adding-a-security-policy-to-your-repository)".{% endif %} -| *SUPPORT.md* | Um arquivo SUPPORT permite que as pessoas conheçam maneiras de obter ajudar com seu projeto. Para obter mais informações, consulte "[Adicionar recursos de suporte ao projeto](/articles/adding-support-resources-to-your-project/)". | +| Arquivo de integridade da comunidade | Descrição | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| *CODE_OF_CONDUCT.md* | Um arquivo CODE_OF_CONDUCT define os padrões de como ingressar em uma comunidade. Para obter mais informações, consulte "[Adicionar um código de conduta ao projeto](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %} +| *CONTRIBUTING.md* | Um arquivo CONTRIBUTING comunica como as pessoas devem contribuir com o seu projeto. Para obter mais informações, consulte "[Definir diretrizes para contribuidores de repositórios](/articles/setting-guidelines-for-repository-contributors/)".{% if currentVersion == "free-pro-team@latest" %} +| *FUNDING.yml* | Um arquivo FUNDING exibe um botão de patrocinador no repositório para aumentar a visibilidade das opções de financiamento para seu projeto de código aberto. Para obter mais informações, consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %} +| Modelos de problemas e pull request{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e *config.yml*{% endif %} | Os modelos de problema e pull request personalizam e padronizam as informações que você deseja que contribuidores incluam quando eles abrem problemas e pull requests no seu repositório. Para obter mais informações, consulte "[Sobre problemas e modelos de pull request](/articles/about-issue-and-pull-request-templates/).{% if currentVersion == "free-pro-team@latest" %} +| *SECURITY.md* | Um arquivo SECURITY fornece instruções sobre como relatar com responsabilidade uma vulnerabilidade de segurança em seu projeto. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/articles/adding-a-security-policy-to-your-repository)".{% endif %} +| *SUPPORT.md* | Um arquivo SUPPORT permite que as pessoas conheçam maneiras de obter ajudar com seu projeto. Para obter mais informações, consulte "[Adicionar recursos de suporte ao projeto](/articles/adding-support-resources-to-your-project/)". | Você não pode criar um arquivo de licença padrão. Os arquivos de licença devem ser adicionados a repositórios individuais para que o arquivo seja incluído quando um projeto for clonado, empacotado ou baixado. ### Criar um repositório para arquivos padrão {% data reusables.repositories.create_new %} -2. Use the **Owner** drop-down menu, and select the organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} you want to create default files for. ![Menu suspenso Owner (Proprietário)](/assets/images/help/repository/create-repository-owner.png) +2. Use o menu suspenso **Proprietário** e selecione a organização{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} ou conta de usuário{% endif %} para a qual você deseja criar arquivos padrão. ![Menu suspenso Owner (Proprietário)](/assets/images/help/repository/create-repository-owner.png) 3. Digite **.github** como o nome para seu repositório e uma descrição opcional. ![Campo Create repository (Criar repositório)](/assets/images/help/repository/default-file-repository-name.png) 4. Certifique-se de que o status do repositório está definido como **Público** (um repositório-padrão para arquivos não pode ser privado). ![Botões de opção para selecionar status privado ou público](/assets/images/help/repository/create-repository-public-private.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -7. No repositório, crie um dos arquivos compatíveis de integridade da comunidade. Issue templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. Todos os outros arquivos compatíveis devem estar na raiz do repositório. Para obter mais informações, consulte "[Criar arquivos](/articles/creating-new-files/)". +7. No repositório, crie um dos arquivos compatíveis de integridade da comunidade. Modelos de problema{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} e o seu arquivo de configuração{% endif %} deve estar em uma pasta denominada `.github/ISSUE_TEMPLATE`. Todos os outros arquivos compatíveis devem estar na raiz do repositório. Para obter mais informações, consulte "[Criar arquivos](/articles/creating-new-files/)". diff --git a/translations/pt-BR/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md b/translations/pt-BR/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md index 0bc1f8edfb..02e4abdb45 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md +++ b/translations/pt-BR/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md @@ -13,7 +13,11 @@ Para obter mais informações, consulte "[Sobre modelos de problema e pull reque Você pode criar um subdiretório *PULL_REQUEST_TEMPLATE/* em qualquer uma das pastas compatíveis para conter vários modelos de pull request, bem como usar o parâmetro de consulta `template` para especificar o modelo que preencherá o texto da pull request. Para obter mais informações, consulte "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)". -You can create default pull request templates for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Você pode criar modelos-padrão de pull request para a sua organização{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} ou conta de usuário{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} ### Adicionar um modelo de pull request diff --git a/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md b/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md index 02e1c3b8ee..32f75a3e33 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md +++ b/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md @@ -1,26 +1,26 @@ --- -title: Limiting interactions for your user account -intro: 'You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your user account.' +title: Limitar interações para sua conta de usuário +intro: 'Você pode aplicar temporariamente um período de atividade limitada para certos usuários em todos os repositórios públicos pertencentes à sua conta de usuário.' versions: free-pro-team: '*' -permissions: Anyone can limit interactions for their own user account. +permissions: Qualquer pessoa pode limitar as interações para sua própria conta de usuário. --- -### About temporary interaction limits +### Sobre limites temporários de interação -Limiting interactions for your user account enables temporary interaction limits for all public repositories owned by your user account. {% data reusables.community.interaction-limits-restrictions %} +Limitar interações para sua conta de usuário permite limites temporários de interação para todos os repositórios públicos pertencentes à sua conta de usuário. {% data reusables.community.interaction-limits-restrictions %} -{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your public repositories. +{% data reusables.community.interaction-limits-duration %} Após a duração do seu limite, os usuários podem retomar a atividade normal nos seus repositórios públicos. {% data reusables.community.types-of-interaction-limits %} -When you enable user-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/articles/limiting-interactions-in-your-repository)." +Ao habilitar limitações de atividade para todos os usuários, você não pode habilitar ou desabilitar limites de interação em repositórios individuais. Para obter mais informações sobre limitação de atividade para um repositório individual, consulte "[Limitar interações no repositório](/articles/limiting-interactions-in-your-repository)". -You can also block users. For more information, see "[Blocking a user from your personal account](/github/building-a-strong-community/blocking-a-user-from-your-personal-account)." +Você também pode bloquear usuários. Para obter mais informações, consulte "[Bloquear um usuário da sua conta pessoal](/github/building-a-strong-community/blocking-a-user-from-your-personal-account)". -### Limiting interactions for your user account +### Limitar interações para sua conta de usuário {% data reusables.user_settings.access_settings %} -1. In your user settings sidebar, under "Moderation settings", click **Interaction limits**. !["Interaction limits" tab in the user settings sidebar](/assets/images/help/settings/settings-sidebar-interaction-limits.png) +1. Na barra lateral de configurações do usuário, em "Configurações de moderação", clique em **Limites de interação**. ![Aba "Limites de interação" na barra lateral de configurações do usuário](/assets/images/help/settings/settings-sidebar-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png) \ No newline at end of file diff --git a/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md b/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md index a5b193c110..c682d4316a 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md +++ b/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md @@ -1,35 +1,35 @@ --- title: Restringir interações na organização -intro: 'You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.' +intro: 'É possível aplicar temporariamente um período de atividade limitada para determinados usuários em todos os repositórios públicos pertencentes à sua organização.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/limiting-interactions-in-your-organization - /articles/limiting-interactions-in-your-organization versions: free-pro-team: '*' -permissions: Organization owners can limit interactions in an organization. +permissions: Os proprietários da organização podem limitar interações em uma organização. --- -### About temporary interaction limits +### Sobre limites temporários de interação -Limiting interactions in your organization enables temporary interaction limits for all public repositories owned by the organization. {% data reusables.community.interaction-limits-restrictions %} +O limite de interações na organização habilita limites de interação temporária para todos os repositórios públicos pertencentes à organização. {% data reusables.community.interaction-limits-restrictions %} -{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your organization's public repositories. +{% data reusables.community.interaction-limits-duration %} Após a duração do seu limite passar, os usuários podem retomar a atividade normal nos repositórios públicos da sua organização. {% data reusables.community.types-of-interaction-limits %} -Members of the organization are not affected by any of the limit types. +Os integrantes da organização não são afetados por nenhum dos tipos de limite. -Quando você habilita restrições de atividades para toda a organização, você não pode habilitar ou desabilitar restrições de interação em repositórios individuais. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/articles/limiting-interactions-in-your-repository)." +Quando você habilita restrições de atividades para toda a organização, você não pode habilitar ou desabilitar restrições de interação em repositórios individuais. Para obter mais informações sobre limitação de atividade para um repositório individual, consulte "[Limitar interações no repositório](/articles/limiting-interactions-in-your-repository)". -Organization owners can also block users for a specific amount of time. Após o término do bloqueio, o usuário é automaticamente desbloqueado. Para obter mais informações, consulte "[Bloquear um usuário em sua organização](/articles/blocking-a-user-from-your-organization)". +Os proprietários da organização também podem bloquear os usuários por um determinado período de tempo. Após o término do bloqueio, o usuário é automaticamente desbloqueado. Para obter mais informações, consulte "[Bloquear um usuário em sua organização](/articles/blocking-a-user-from-your-organization)". ### Restringir interações na organização {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} -1. In the organization settings sidebar, click **Moderation settings**. !["Moderation settings" in the organization settings sidebar](/assets/images/help/organizations/org-settings-moderation-settings.png) -1. Under "Moderation settings", click **Interaction limits**. !["Interaction limits" in the organization settings sidebar](/assets/images/help/organizations/org-settings-interaction-limits.png) +1. Na barra lateral de configurações da organização, clique em **Configurações de moderação**. !["Configurações de moderação" na barra lateral das configurações da organização](/assets/images/help/organizations/org-settings-moderation-settings.png) +1. Em "Configurações de moderação", clique em **Limites de interação**. !["Limites de interação" na barra lateral de configurações da organização](/assets/images/help/organizations/org-settings-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) diff --git a/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md b/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md index 24e8f07689..e1b843b11b 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md +++ b/translations/pt-BR/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md @@ -1,30 +1,30 @@ --- title: Restringir interações no repositório -intro: 'You can temporarily enforce a period of limited activity for certain users on a public repository.' +intro: 'É possível aplicar temporariamente um período de atividades limitadas para certos usuários em um repositório público.' redirect_from: - /articles/limiting-interactions-with-your-repository/ - /articles/limiting-interactions-in-your-repository versions: free-pro-team: '*' -permissions: People with admin permissions to a repository can temporarily limit interactions in that repository. +permissions: As pessoas com permissões de administrador em um repositório podem limitar temporariamente as interações nesse repositório. --- -### About temporary interaction limits +### Sobre limites temporários de interação {% data reusables.community.interaction-limits-restrictions %} -{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your repository. +{% data reusables.community.interaction-limits-duration %} Após a duração do seu limite, os usuários podem retomar à atividade normal no seu repositório. {% data reusables.community.types-of-interaction-limits %} -You can also enable activity limitations on all repositories owned by your user account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your user account](/github/building-a-strong-community/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/github/building-a-strong-community/limiting-interactions-in-your-organization)." +Você também pode habilitar limitações de atividade em todos os repositórios pertencentes à sua conta de usuário ou organização. Se o limite de um usuário ou organização estiver habilitado, não será possível limitar a atividade para repositórios individuais pertencentes à conta. Para obter mais informações, consulte "[Limitar interações para a sua conta de usuário](/github/building-a-strong-community/limiting-interactions-for-your-user-account)" e "[Limitar interações na sua organização](/github/building-a-strong-community/limiting-interactions-in-your-organization)". ### Restringir interações no repositório {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. In the left sidebar, click **Moderation settings**. !["Moderation settings" in repository settings sidebar](/assets/images/help/repository/repo-settings-moderation-settings.png) -1. Under "Moderation settings", click **Interaction limits**. ![Interaction limits (Restrições de interação) em Settings (Configurações) do repositório ](/assets/images/help/repository/repo-settings-interaction-limits.png) +1. Na barra lateral esquerda, clique em **Configurações de moderação**. !["Configurações de moderação" na barra lateral de configurações do repositório](/assets/images/help/repository/repo-settings-moderation-settings.png) +1. Em "Configurações de moderação", clique em **Limites de interação**. ![Interaction limits (Restrições de interação) em Settings (Configurações) do repositório ](/assets/images/help/repository/repo-settings-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/repository/temporary-interaction-limits-options.png) diff --git a/translations/pt-BR/content/github/building-a-strong-community/locking-conversations.md b/translations/pt-BR/content/github/building-a-strong-community/locking-conversations.md index 382b02f7d6..fb1908ee0b 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/locking-conversations.md +++ b/translations/pt-BR/content/github/building-a-strong-community/locking-conversations.md @@ -1,6 +1,6 @@ --- -title: Locking conversations -intro: 'Repository owners and collaborators, and people with write access to a repository, can lock conversations on issues, pull requests, and commits permanently or temporarily to defuse a heated interaction.' +title: Bloquear conversas +intro: 'Proprietários e colaboradores de repositórios e pessoas com acesso de gravação em um repositório podem bloquear permanentemente ou temporariamente conversas sobre problemas, pull requests e commits para neutralizar uma interação acalorada.' redirect_from: - /articles/locking-conversations versions: @@ -9,32 +9,28 @@ versions: github-ae: '*' --- -It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. When you lock a conversation, you can also specify a reason, which is publicly visible. +É apropriado bloquear uma conversa quando toda a conversa não é construtiva ou viola o código de conduta da sua comunidade{% if currentVersion == "free-pro-team@latest" %} ou as [diretrizes da comunidade do GitHub](/articles/github-community-guidelines){% endif %}. Quando você bloqueia uma conversa, você também pode especificar o motivo, que é visível publicamente. -Locking a conversation creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who locked the conversation is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized. +Bloquear uma conversa cria um evento na linha do tempo visível a qualquer um com acesso de leitura ao repositório. No entanto, o nome de usuário da pessoa que bloqueou a conversa somente pode ser visualizado pelas pessoas com acesso de gravação ao repositório. Para qualquer pessoa sem acesso de gravação, o evento na linha do tempo é anônimo. -![Anonymized timeline event for a locked conversation](/assets/images/help/issues/anonymized-timeline-entry-for-locked-conversation.png) +![Evento anônimo de linha do tempo de uma conversa bloqueada](/assets/images/help/issues/anonymized-timeline-entry-for-locked-conversation.png) -While a conversation is locked, only [people with write access](/articles/repository-permission-levels-for-an-organization/) and [repository owners and collaborators](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-on-a-repository-owned-by-a-user-account) can add, hide, and delete comments. +Quando uma conversa é bloqueada, somente [pessoas com acesso de gravação](/articles/repository-permission-levels-for-an-organization/) e [proprietários e colaboradores de repositórios](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account) podem adicionar, ocultar ou excluir comentários. -To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see "[Searching issues and pull requests](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)." +Para pesquisar conversas bloqueadas em um repositório que não está arquivado, é posível usar os qualificadores de pesquisa `is:locked` e `archived:false`. As conversas são automaticamente bloqueadas em repositórios arquivados. Para obter mais informações, consulte "[Pesquisar problemas e pull requests](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)". -1. Optionally, write a comment explaining why you're locking the conversation. -2. In the right margin of the issue or pull request, or above the comment box on the commit page, click **Lock conversation**. -![Lock conversation link](/assets/images/help/repository/lock-conversation.png) -3. Optionally, choose a reason for locking the conversation. -![Reason for locking a conversation menu](/assets/images/help/repository/locking-conversation-reason-menu.png) -4. Read the information about locking conversations and click **Lock conversation on this issue**, **Lock conversation on this pull request**, or **Lock conversation on this commit**. -![Confirm lock with a reason dialog box](/assets/images/help/repository/lock-conversation-confirm-with-reason.png) -5. When you're ready to unlock the conversation, click **Unlock conversation**. -![Unlock conversation link](/assets/images/help/repository/unlock-conversation.png) +1. Como opção, escreva um comentário explicando por que você está bloqueando a conversa. +2. Na margem direita do problema ou pull request ou acima da caixa de comentários na página de commit, clique em **Lock conversation** (Bloquear conversa). ![Link Lock conversation (Bloquear conversa)](/assets/images/help/repository/lock-conversation.png) +3. Opcionalmente, selecione um motivo para bloquear a conversa. ![Menu Reason for locking a conversation (Motivo para bloquear uma conversa)](/assets/images/help/repository/locking-conversation-reason-menu.png) +4. Leia as informações sobre bloqueio de conversas e clique em **Lock conversation on this issue** (Bloquear conversa sobre este problema), **Lock conversation on this pull request** (Bloquear conversa sobre esta pull request) ou **Lock conversation on this commit** (Bloquear conversa sobre este commit). ![Caixa de diálogo Confirm lock with a reason (Confirmar bloqueio com um motivo)](/assets/images/help/repository/lock-conversation-confirm-with-reason.png) +5. Quando você quiser desbloquear a conversa, clique em **Unlock conversation** (Desbloquear conversa). ![Link Unlock conversation (Desbloquear conversa)](/assets/images/help/repository/unlock-conversation.png) -### Further reading +### Leia mais -- "[Setting up your project for healthy contributions](/articles/setting-up-your-project-for-healthy-contributions)" -- "[Using templates to encourage useful issues and pull requests](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" -- "[Managing disruptive comments](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} -- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" -- "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)" -- "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" +- "[Configurar seu projeto para contribuições úteis](/articles/setting-up-your-project-for-healthy-contributions)" +- "[Usando modelos para encorajar problemas úteis e pull requests](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Gerenciar comentários disruptivos](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} +- "[Mantendo sua segurança no {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" +- "[Denunciar abuso ou spam](/articles/reporting-abuse-or-spam)" +- "[Limitando interações em seu repositório](/github/building-a-strong-community/limiting-interactions-in-your-repository)" {% endif %} diff --git a/translations/pt-BR/content/github/building-a-strong-community/managing-disruptive-comments.md b/translations/pt-BR/content/github/building-a-strong-community/managing-disruptive-comments.md index 16acb1360c..efdcd36649 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/managing-disruptive-comments.md +++ b/translations/pt-BR/content/github/building-a-strong-community/managing-disruptive-comments.md @@ -1,6 +1,6 @@ --- -title: Managing disruptive comments -intro: 'You can {% if currentVersion == "free-pro-team@latest" %}hide, edit,{% else %}edit{% endif %} or delete comments on issues, pull requests, and commits.' +title: Gerenciar comentários conflituosos +intro: 'Podes {% if currentVersion == "free-pro-team@latest" %}hide, editar,{% else %}edit{% endif %} ou excluir comentários em problemas, pull requests e commits.' redirect_from: - /articles/editing-a-comment/ - /articles/deleting-a-comment/ @@ -11,76 +11,69 @@ versions: github-ae: '*' --- -### Hiding a comment +### Ocultar um comentário -Anyone with write access to a repository can hide comments on issues, pull requests, and commits. +Qualquer pessoa com acesso de gravação em um repositório podem ocultar comentários sobre problemas, pull requests e commits. -If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them. +Se um comentário não diz respeito ao assunto, está desatualizado ou resolvido, pode ser que você queira ocultar o comentário para manter o foco da discussão ou fazer uma pull request mais simples para navegar e revisar. Comentários ocultos são minimizados, mas as pessoas com acesso de leitura no repositório podem expandi-los. -![Minimized comment](/assets/images/help/repository/hidden-comment.png) +![Comentário minimizado](/assets/images/help/repository/hidden-comment.png) -1. Navigate to the comment you'd like to hide. -2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**. - ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete options](/assets/images/help/repository/comment-menu.png) -3. Using the "Choose a reason" drop-down menu, click a reason to hide the comment. Then click, **Hide comment**. +1. Navegue até o comentário que deseja ocultar. +2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Hide** (Ocultar). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, hide, delete (editar, ocultar, excluir)](/assets/images/help/repository/comment-menu.png) +3. Com o menu suspenso "Choose a reason" (Selecione um motivo), clique em um motivo para ocultar o comentário. Depois clique em **Hide comment** (Ocultar comentário). {% if currentVersion == "free-pro-team@latest" %} - ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment.png) + ![Menu suspenso Choose reason for hiding comment (Selecione um motivo para ocultar o comentário)](/assets/images/help/repository/choose-reason-for-hiding-comment.png) {% else %} - ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png) + ![Menu suspenso Choose reason for hiding comment (Selecione um motivo para ocultar o comentário)](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png) {% endif %} -### Unhiding a comment +### Mostrar um comentário -Anyone with write access to a repository can unhide comments on issues, pull requests, and commits. +Qualquer pessoa com acesso de gravação em um repositório pode reexibir comentários sobre problemas, pull requests e commits. -1. Navigate to the comment you'd like to unhide. -2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**. - ![Show comment text](/assets/images/help/repository/hidden-comment-show.png) -3. On the right side of the expanded comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Unhide**. - ![The horizontal kebab icon and comment moderation menu showing the edit, unhide, delete options](/assets/images/help/repository/comment-menu-hidden.png) +1. Navegue até o comentário que deseja mostrar. +2. No canto superior direito do comentário, clique em **{% octicon "fold" aria-label="The fold icon" %} Show comment** (Mostrar comentário). ![Mostrar texto de comentário](/assets/images/help/repository/hidden-comment-show.png) +3. No lado direito do comentário expandido, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e **Unhide** (Mostrar). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, unhide, delete (editar, mostrar, excluir)](/assets/images/help/repository/comment-menu-hidden.png) -### Editing a comment +### Editar um comentário -Anyone with write access to a repository can edit comments on issues, pull requests, and commits. +Qualquer pessoa com acesso de gravação em um repositório pode editar comentários sobre problemas, pull requests e commits. -It's appropriate to edit a comment and remove content that doesn't contribute to the conversation and violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. +Considera-se apropriado editar um comentário e remover o conteúdo que não contribui para a conversa e viole o código de conduta da sua comunidade{% if currentVersion == "free-pro-team@latest" %} ou as diretrizes [da Comunidade do GitHub](/articles/github-community-guidelines){% endif %}. -When you edit a comment, note the location that the content was removed from and optionally, the reason for removing it. +Quando editar um comentário, anote a localização de onde o comentário foi removido e, opcionalmente, os motivos para a remoção. -Anyone with read access to a repository can view a comment's edit history. The **edited** dropdown at the top of the comment contains a history of edits showing the user and timestamp for each edit. +Qualquer pessoa com acesso de leitura em um repositório pode visualizar o histórico de edição do comentário. O menu suspenso **edited** (editado) na parte superior do comentário tem um histório de edições mostrando o usuário e o horário de cada edição. -![Comment with added note that content was redacted](/assets/images/help/repository/content-redacted-comment.png) +![Comentário com observação adicional que o conteúdo foi redacted (suprimido)](/assets/images/help/repository/content-redacted-comment.png) -Comment authors and anyone with write access to a repository can also delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/github/building-a-strong-community/tracking-changes-in-a-comment)." +Autores do comentário e pessoas com acesso de gravação a um repositório podem excluir informações confidenciais do histórico de edição de um comentário. Para obter mais informações, consulte "[Controlar as alterações em um comentário](/github/building-a-strong-community/tracking-changes-in-a-comment)". -1. Navigate to the comment you'd like to edit. -2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. - ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png) -3. In the comment window, delete the content you'd like to remove, then type `[REDACTED]` to replace it. - ![Comment window with redacted content](/assets/images/help/issues/redacted-content-comment.png) -4. At the bottom of the comment, type a note indicating that you have edited the comment, and optionally, why you edited the comment. - ![Comment window with added note that content was redacted](/assets/images/help/issues/note-content-redacted-comment.png) -5. Click **Update comment**. +1. Navegue até o comentário que deseja editar. +2. No canto superior direito do comentário, clique em{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Edit** (Editar). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, hide, delete e report (editar, ocultar, excluir e denunciar)](/assets/images/help/repository/comment-menu.png) +3. Na janela do comentário, exclua o conteúdo que deseja remover e digite `[REDACTED]` para substitui-lo. ![Janela de comentário com conteúdo redacted (suprimido)](/assets/images/help/issues/redacted-content-comment.png) +4. Na parte inferior do comentário, digite uma observação indicando que editou o comentário e, opcionalmente, o motivo da edição. ![Janela de comentário com observação adicional que o conteúdo foi redacted (suprimido)](/assets/images/help/issues/note-content-redacted-comment.png) +5. Clique em **Update comment** (Atualizar comentário). -### Deleting a comment +### Excluir um comentário -Anyone with write access to a repository can delete comments on issues, pull requests, and commits. Organization owners, team maintainers, and the comment author can also delete a comment on a team page. +Qualquer pessoa com acesso de gravação em um repositório pode excluir comentários sobre problemas, pull requests e commits. Proprietários de organização, mantenedores de equipes e o autor do comentário também podem excluir um comentário na página da equipe. -Deleting a comment is your last resort as a moderator. It's appropriate to delete a comment if the entire comment adds no constructive content to a conversation and violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. +Excluir um comentário é o seu último recurso como moderador. É apropriado excluir um comentário se todo o comentário não adicionar conteúdo construtivo a uma conversa e violar o código de conduta da sua comunidade{% if currentVersion == "free-pro-team@latest" %} ou [Diretrizes da Comunidade](/articles/github-community-guidelines){% endif %}. -Deleting a comment creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who deleted the comment is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized. +Excluir um comentário cria um evento na linha do tempo visível a qualquer um com acesso de leitura no repositório. No entanto, o nome de usuário da pessoa que excluiu o comentário somente pode ser visualizado pelas pessoas com acesso de gravação ao repositório. Para qualquer pessoa sem acesso de gravação, o evento na linha do tempo é anônimo. -![Anonymized timeline event for a deleted comment](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png) +![Evento anônimo de linha do tempo de um comentário excluído](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png) -If a comment contains some constructive content that adds to the conversation in the issue or pull request, you can edit the comment instead. +Se o comentário contém algum conteúdo construtivo que contribui para a conversa sobre o problema ou pull request, você pode editar o comentário. {% note %} -**Note:** The initial comment (or body) of an issue or pull request can't be deleted. Instead, you can edit issue and pull request bodies to remove unwanted content. +**Observação:** o comentário inicial (ou texto) de um problema ou pull request não pode ser excluído. Entretanto, você pode editar textos de problemas e pull requests para remover conteúdo indesejável. {% endnote %} -1. Navigate to the comment you'd like to delete. -2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. - ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png) -3. Optionally, write a comment noting that you deleted a comment and why. +1. Navegue até o comentário que deseja excluir. +2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Delete** (Excluir). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, hide, delete e report (editar, ocultar, excluir e denunciar)](/assets/images/help/repository/comment-menu.png) +3. Opcionalmente, escreva um comentário informando que você deletou o comentário e por quê. diff --git a/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index 8c01d2c253..fc4f36b06c 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -39,8 +39,12 @@ assignees: octocat {% endif %} +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + {% data reusables.repositories.default-issue-templates %} +{% endif %} + ### Adicionar um modelo de problema {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/pt-BR/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md b/translations/pt-BR/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md index 09f4208039..1600460033 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md +++ b/translations/pt-BR/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md @@ -20,7 +20,11 @@ Para contribuidores, as diretrizes ajudam a verificar se eles estão enviando pu Para proprietários e contribuidores, as diretrizes de contribuição economizam tempo e evitam aborrecimentos causados por pull requests ou problemas incorretos que precisam ser rejeitados e enviados novamente. -You can create default contribution guidelines for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Você pode criar diretrizes de contribuição padrão para a organização{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} ou conta de usuário{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} {% tip %} @@ -53,5 +57,5 @@ Caso tenha dúvidas, estes são alguns bons exemplos de diretrizes de contribui ### Leia mais - A seção "Guias de código aberto"[Iniciar um projeto de código aberto](https://opensource.guide/starting-a-project/)"{% if currentVersion == "free-pro-team@latest" %} -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} -- "[Adicionar uma licença a um repositório](/articles/adding-a-license-to-a-repository)" +- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index f17a2643ef..50bda0bf5d 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -23,9 +23,9 @@ Você deve ter acesso de gravação em um repositório para criar um branch, abr ### Sobre o branch-padrão -{% data reusables.branches.new-repo-default-branch %} O branch-padrão é o branch que {% data variables.product.prodname_dotcom %} exibe quando alguém visita o seu repositório. O branch-padrão é também o branch inicial que o Git verifica localmente quando alguém clona o repositório. {% data reusables.branches.default-branch-automatically-base-branch %} +{% data reusables.branches.new-repo-default-branch %} O branch-padrão é o branch que {% data variables.product.prodname_dotcom %} exibe quando alguém visita o seu repositório. The default branch is also the initial branch that Git checks out locally when someone clones the repository. {% data reusables.branches.default-branch-automatically-base-branch %} -By default, {% data variables.product.product_name %} names the default branch {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %} in any new repository. +Por padrão, {% data variables.product.product_name %} nomeia o branch padrão {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" or currentVersion == "github-ae@latest" %}`principal`{% else %}`master`{% endif %} em qualquer novo repositório. {% data reusables.branches.change-default-branch %} @@ -74,8 +74,8 @@ Quando um branch estiver protegido: - Se as verificações de status obrigatórias forem habilitadas no branch, não será possível fazer merge das alterações no branch até que todos os testes de CI obrigatórios sejam aprovados. Para obter mais informações, consulte "[Sobre verificações de status](/articles/about-status-checks)". - Se as revisões obrigatórias de pull request forem habilitadas no branch, não será possível fazer merge de alterações no branch até que todos os requisitos na política da revisão de pull request tenham sido atendidos. Para obter mais informações, consulte "[Fazer merge de uma pull request](/articles/merging-a-pull-request)". - Se a revisão obrigatória de um proprietário do código for habilitada em um branch, e uma pull request modificar o código que tem um proprietário, um proprietário do código deverá aprovar a pull request para que ela possa passar por merge. Para obter mais informações, consulte "[Sobre proprietários do código](/articles/about-code-owners)". -- Se a assinatura de commit obrigatória for habilitada em um branch, não será possível fazer push de qualquer commit no branch que não esteja assinado e verificado. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About required commit signing](/articles/about-required-commit-signing)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -- Se você usar o editor de conflitos do {% data variables.product.prodname_dotcom %} para corrigir conflitos para uma pull request que você criou de um branch protegido, o {% data variables.product.prodname_dotcom %} ajuda você a criar um branch alternativo para o pull request, para que sua resolução de conflitos possa ser mesclada. Para obter mais informações, consulte "[Resolvendo um conflito de merge no {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)".{% endif %} +- Se a assinatura de commit obrigatória for habilitada em um branch, não será possível fazer push de qualquer commit no branch que não esteja assinado e verificado. Para obter mais informações, consulte "[Sobre verificação de assinatura de commit](/articles/about-commit-signature-verification)" e "[Sobre a assinatura de commit obrigatória](/articles/about-required-commit-signing). {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +- If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %} helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. Para obter mais informações, consulte "[Resolvendo um conflito de merge no {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)".{% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index a6d5d3d1e0..026a64938e 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -20,7 +20,7 @@ Os problemas são úteis para discutir detalhes específicos de um projeto, como ### Reagir às ideias nos comentários -Você pode concordar ou discordar de uma ideia em uma conversa. Quando você adiciona uma reação a um comentário ou ao texto de uma discussão de equipe, de um problema ou de uma pull request, as pessoas inscritas na conversa não receberão uma notificação. For more information about subscriptions, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}." +Você pode concordar ou discordar de uma ideia em uma conversa. Quando você adiciona uma reação a um comentário ou ao texto de uma discussão de equipe, de um problema ou de uma pull request, as pessoas inscritas na conversa não receberão uma notificação. Para obter mais informações sobre assinaturas, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Sobre as notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Assinar e cancelar a assinatura das notificações](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}". ![Exemplo de um problema com reações](/assets/images/help/repository/issue-reactions.png) diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index d3898c1128..ee98e3cd53 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -13,7 +13,7 @@ versions: Após a abertura de uma pull request, qualquer pessoa com acesso *de leitura* pode revisar e comentar nas alterações que ela propõe. Você também pode sugerir alterações específicas às linhas de código, que o autor pode aplicar diretamente a partir da pull request. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". -Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/articles/requesting-a-pull-request-review)". {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} +Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/articles/requesting-a-pull-request-review)". {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Você pode especificar um subconjunto de integrantes da equipe a ser atribuído automaticamente no lugar de toda a equipe. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} As revisões permitem discussão das alterações propostas e ajudam a garantir que as alterações atendam às diretrizes de contribuição do repositório e outros padrões de qualidade. Você pode definir quais indivíduos ou equipes possuem determinados tipos de área de código em um arquivo CODEOWNERS. Quando uma pull request modifica código que tem um proprietário definido, esse indivíduo ou equipe será automaticamente solicitado como um revisor. Para obter mais informações, consulte "[Sobre proprietários de código](/articles/about-code-owners/)". @@ -38,7 +38,7 @@ Você pode exibir todas as revisões que uma pull request recebeu na linha do te {% data reusables.pull_requests.resolving-conversations %} -### Re-requesting a review +### Ressolicitar uma revisão {% data reusables.pull_requests.re-request-review %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md index 51205b4fa8..3b8880b0f1 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md @@ -29,7 +29,7 @@ Há dois tipos de verificação de status no {% data variables.product.product_n _Verificações_ são diferentes de _status_, pois elas fornecem anotações em linha, mensagens mais detalhadas e estão disponíveis apenas para uso com os {% data variables.product.prodname_github_app %}s. -Os proprietários da organização e usuários com acesso push a um repositório podem criar verificações e status com a API do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificações](/v3/checks/)" e "[Status](/v3/repos/statuses/)". +Os proprietários da organização e usuários com acesso push a um repositório podem criar verificações e status com a API do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)" e "[Status](/rest/reference/repos#statuses)". ### Verificações diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md index 4135232bf8..0c5ebefda1 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: Alterar o stage de uma pull request -intro: 'You can mark a draft pull request as ready for review{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} or convert a pull request to a draft{% endif %}.' +intro: 'Você pode marcar um pull request como pronto para a revisão{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %} ou converter um pull request em rascunho{% endif %}.' permissions: Pessoas com permissões de gravação em um repositório e autores de pull request podem alterar o stage de uma pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md index e185d0a0cf..07d9ffda40 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md @@ -1,6 +1,6 @@ --- -title: Collaborating on repositories with code quality features -intro: 'Workflow quality features like statuses, {% if enterpriseServerVersions contains currentVersion %}pre-receive hooks, {% endif %}protected branches, and required status checks help collaborators make contributions that meet conditions set by organization and repository administrators.' +title: Colaborar nos repositórios com recursos de qualidade de código +intro: 'Os recursos de qualidade do fluxo de trabalho, como status, {% if enterpriseServerVersions contains currentVersion %}hooks pre-receive, {% endif %}branches protegidos e verificações de status obrigatórias ajudam os colaboradores a fazer contribuições que atendem às condições definidas pela organização e por administradores de repositório.' mapTopic: true redirect_from: - /articles/collaborating-on-repositories-with-code-quality-features-enabled/ diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md index 81190022aa..ab220e97be 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md @@ -25,7 +25,7 @@ Cada pessoa que sugeriu uma alteração incluída no commit será uma coautora d 4. No campo de mensagem do commit, digite uma mensagem curta e relevante que descreva a alteração que você fez no arquivo ou arquivos. ![Campo Commit message (Mensagem do commit)](/assets/images/help/pull_requests/suggested-change-commit-message-field.png) 5. Clique em **Commit changes** (Fazer commit das alterações). ![Botão Commit changes (Fazer commit de alterações)](/assets/images/help/pull_requests/commit-changes-button.png) -### Re-requesting a review +### Ressolicitar uma revisão {% data reusables.pull_requests.re-request-review %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index fe9595fa3f..4665ca5c18 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -45,7 +45,7 @@ Se decidir que não quer que as alterações em um branch de tópico sofram merg {% note %} - **Note:** The email selector is not available for rebase merges, which do not create a merge commit, or for squash merges, which credit the user who created the pull request as the author of the squashed commit. + **Observação:** O seletor de e-mail não está disponível para merge de rebase, que não cria um commit de merge, ou para merge de combinação por squash, que credita o usuário que criou a pull request como o autor do commit cuja combinação foi feita por squash. {% endnote %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index 7fbcc480e5..6d3f11f190 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -11,7 +11,7 @@ versions: Proprietários e colaboradores de um repositório pertencente a uma conta de usuário podem atribuir revisões de pull requests. Os integrantes da organização com permissões de triagem em um repositório podem atribuir uma revisão de pull request. -Os proprietários e colaboradores podem atribuir uma revisão de pull request a qualquer pessoa que recebeu explicitamente [acesso de leitura](/articles/access-permissions-on-github) em um repositório pertencente a um usuário. Os integrantes da organização podem atribuir uma revisão de pull request para qualquer pessoa ou equipe com acesso de leitura em um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} +Os proprietários e colaboradores podem atribuir uma revisão de pull request a qualquer pessoa que recebeu explicitamente [acesso de leitura](/articles/access-permissions-on-github) em um repositório pertencente a um usuário. Os integrantes da organização podem atribuir uma revisão de pull request para qualquer pessoa ou equipe com acesso de leitura em um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Se você solicitou uma revisão de uma equipe e a atribuição de código estiver habilitada, será solicitado que integrantes específicos e a equipe sejam removidos como revisores. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} {% note %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md index ec47c6933b..9d19503075 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md @@ -1,6 +1,6 @@ --- -title: Resolving a merge conflict on GitHub -intro: 'You can resolve simple merge conflicts that involve competing line changes on GitHub, using the conflict editor.' +title: Resolver um conflito de merge no GitHub +intro: 'Você pode resolver conflitos de merge simples que envolvem alterações concorrentes na linha usando o editor de conflitos.' redirect_from: - /articles/resolving-a-merge-conflict-on-github versions: @@ -9,56 +9,53 @@ versions: github-ae: '*' --- -You can only resolve merge conflicts on {% data variables.product.product_name %} that are caused by competing line changes, such as when people make different changes to the same line of the same file on different branches in your Git repository. For all other types of merge conflicts, you must resolve the conflict locally on the command line. For more information, see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line/)." +Você só pode resolver conflitos de merge no {% data variables.product.product_name %} causados por alterações concorrentes na linha, como quando as pessoas fazem alterações diferentes na mesma linha do mesmo arquivo em diferentes branches no seu repositório Git. Para todos os outros tipos de conflito de merge, você deve resolver o conflito localmente na linha de comando. Para obter mais informações, consulte "[Resolver um conflito de merge usando a linha de comando](/articles/resolving-a-merge-conflict-using-the-command-line/)". {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -If a site administrator disables the merge conflict editor for pull requests between repositories, you cannot use the conflict editor on {% data variables.product.product_name %} and must resolve merge conflicts on the command line. For example, if the merge conflict editor is disabled, you cannot use it on a pull request between a fork and upstream repository. +Se um administrador do site desabilitar o editor de conflitos de merge para pull requests entre repositórios, você não poderá usar o editor de conflitos em +{% data variables.product.product_name %} e deverá resolver os conflitos de merge na linha de comando. Por exemplo, se o editor de conflitos de merge estiver desabilitado, você não poderá usá-lo em uma pull request entre uma bifurcação e um repositório upstream. {% endif %} {% warning %} {% if currentVersion ver_lt "enterprise-server@2.22" %} -**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %}, the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch), even if the head branch is the default branch of your repository or a protected branch. Make sure you really want to commit to this branch. +**Aviso:** Ao resolver um conflito de merge em +{% data variables.product.product_name %}, todo o [branch base](/github/getting-started-with-github/github-glossary#base-branch) do seu pull request é mesclado no [branch principal](/github/getting-started-with-github/github-glossary#head-branch), mesmo que o branch principal seja o branch padrão do seu repositório ou um branch protegido. Verifique se você deseja realmente fazer commit para esse branch. {% else %} -**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %}, the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch). Make sure you really want to commit to this branch. If the head branch is the default branch of your repository, you'll be given the option of creating a new branch to serve as the head branch for your pull request. If the head branch is protected you won't be able to merge your conflict resolution into it, so you'll be prompted to create a new head branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +**Aviso:** Ao resolver um conflito de merge em +{% data variables.product.product_name %}, todo o [branch base](/github/getting-started-with-github/github-glossary#base-branch) do seu pull request é mesclado no [branch principal](/github/getting-started-with-github/github-glossary#head-branch). Verifique se você deseja realmente fazer commit para esse branch. Se o branch do cabeçalho for o branch-padrão do seu repositório, você terá a opção de criar um novo branch para servir como o branch do cabeçalho para o seu pull request. Se o branch head estiver protegido, você não será capaz de mesclar sua resolução de conflitos nele, então você será solicitado a criar um novo branch head. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". {% endif %} {% endwarning %} {% data reusables.repositories.sidebar-pr %} -1. In the "Pull Requests" list, click the pull request with a merge conflict that you'd like to resolve. -1. Near the bottom of your pull request, click **Resolve conflicts**. -![Resolve merge conflicts button](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png) +1. Na lista "Pull Requests", clique na pull request que tem um conflito de merge que você deseja resolver. +1. Próximo à parte inferior da pull request, clique em **Resolve conflicts** (Resolver conflitos). ![Botão de resolução de conflitos de merge](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png) {% tip %} - **Tip:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line)." + **Dica:** Se o botão **Resolver conflitos** estiver desativado, significa que o conflito de merge do pull request é muito complexo para ser resolvido em {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} ou o administrador do site desativou o editor de conflitos para pull requests entre repositórios{% endif %}. Você deve resolver o conflito de merge usando um cliente Git alternativo, ou usando o Git na linha de comando. Para obter mais informações, consulte "[Resolver um conflito de merge usando a linha de comando](/articles/resolving-a-merge-conflict-using-the-command-line)". {% endtip %} {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} - ![View merge conflict example with conflict markers](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png) -1. If you have more than one merge conflict in your file, scroll down to the next set of conflict markers and repeat steps four and five to resolve your merge conflict. -1. Once you've resolved all the conflicts in the file, click **Mark as resolved**. - ![Click mark as resolved button](/assets/images/help/pull_requests/mark-as-resolved-button.png) -1. If you have more than one file with a conflict, select the next file you want to edit on the left side of the page under "conflicting files" and repeat steps four through seven until you've resolved all of your pull request's merge conflicts. - ![Select next conflicting file if applicable](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png) -1. Once you've resolved all your merge conflicts, click **Commit merge**. This merges the entire base branch into your head branch. - ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png){% if currentVersion ver_lt "enterprise-server@2.22" %} -1. If prompted, review the branch that you are committing to. If you want to commit to this branch, click **I understand, update _BRANCH_**. -![Merge conflict confirmation window](/assets/images/help/pull_requests/merge-conflict-confirmation.png){% else %} -1. If prompted, review the branch that you are committing to. + ![Exemplo de exibição de conflito de merge com marcadores de conflito](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png) +1. Se houver mais de um conflito de merge no arquivo, role para baixo até o próximo conjunto de marcadores de conflito e repita as etapas quatro e cinco para resolver o conflito de merge. +1. Depois de resolver todos os conflitos do arquivo, clique em **Mark as resolved** (Marcar como resolvido). ![Clique no botão marcar como resolvido](/assets/images/help/pull_requests/mark-as-resolved-button.png) +1. Se você tiver mais de um arquivo com um conflito, selecione o próximo arquivo que deseja editar no lado esquerdo da página abaixo de "conflicting files" (arquivos conflitantes) e repita as etapas de quatro a sete até resolver todos os conflitos de merge da pull request. ![Selecione o próximo arquivo conflitante, se aplicável](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png) +1. Depois de resolver todos os conflitos de merge, clique em **Commit merge** (Fazer commit do merge). Isso incorpora todo o branch base ao branch head. ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png){% if currentVersion ver_lt "enterprise-server@2.22" %} +1. Se solicitado, revise o branch presente no commit. Se desejar fazer commit desse branch, clique em **I understand, update _BRANCH_** (Eu entendo, atualizar BRANCH). ![Janela de confirmação do conflito de merge](/assets/images/help/pull_requests/merge-conflict-confirmation.png){% else %} +1. Se solicitado, revise o branch presente no commit. - If the head branch is the default branch of the repository, you can choose either to update this branch with the changes you made to resolve the conflict, or to create a new branch and use this as the head branch of the pull request. - ![Prompt to review the branch that will be updated](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png) - - If you choose to create a new branch, enter a name for the branch. - - If the head branch of your pull request is protected you must create a new branch. You won't get the option to update the protected branch. - - Click **Create branch and update my pull request** or **I understand, continue updating _BRANCH_**. The button text corresponds to the action you are performing. + Se o branch head for o branch padrão do repositório, você pode escolher atualizar este branch com as mudanças que você fez para resolver o conflito, ou criar um novo branch e usar isso como o branch head da pull request. ![Solicitar a revisão do branch que será atualizado](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png) + + Se você escolher criar um novo branch, digite um nome para o branch. + + Se o branch head de sua pull request estiver protegido, você deve criar um novo branch. Você não terá a opção de atualizar o branch protegido. + + Clique em **Criar branch e atualizar meu pull request** ou **Eu entendi, continuar atualizando _BRANCH_**. O texto do botão corresponde à ação que você está executando. {% endif %} -1. To merge your pull request, click **Merge pull request**. For more information about other pull request merge options, see "[Merging a pull request](/articles/merging-a-pull-request/)." +1. Para fazer merge da pull request, clique em **Merge pull request** (Fazer merge da pull request). Para obter mais informações sobre outras opções de merge da pull request, consulte "[Fazer merge de uma pull request](/articles/merging-a-pull-request/)". -### Further reading +### Leia mais -- "[About pull request merges](/articles/about-pull-request-merges)" +- "[Sobre merges de pull request](/articles/about-pull-request-merges)" diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md index 1aca29abb9..2919a55ec4 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md @@ -13,7 +13,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. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +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. @@ -23,12 +23,12 @@ 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. Check out your fork's local default branch - in this case, we use `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. 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. +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/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index 3ffd8881e0..cd90849609 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -16,14 +16,20 @@ versions: Quando você exclui um repositório privado, todas as bifurcações privadas dele também são excluídas. +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + #### Excluir um repositório público Quando você exclui um repositório público, uma das bifurcações públicas existentes é escolhida para ser o novo repositório principal. Todos os outros repositórios são bifurcados a partir desse principal e as pull request subsequentes vão para ele também. +{% endif %} + #### Permissões e bifurcações privadas {% data reusables.repositories.private_forks_inherit_permissions %} +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + #### Mudar de repositório público para repositório privado Se um repositório público passa a ser privado, as bifurcações públicas dele são divididas em uma nova rede. Assim como na exclusão de um repositório público, uma das bifurcações públicas existentes é escolhida para ser o novo repositório principal, todos os outros repositórios são bifurcados a partir dele e as pull requests subsequentes vão para esse repositório também. @@ -46,9 +52,30 @@ Se um repositório privado passa a ser público, cada uma das bifurcações priv Se um repositório privado passa a ser público e depois é excluído, as bifurcações privadas dele continuam existindo como repositórios privados autônomos em redes separadas. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} + +#### Changing the visibility of an internal repository + +{% note %} + +**Observação:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private. + +##### Deleting the internal repository + +If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network. + +{% endif %} + ### Leia mais - "[Definir a visibilidade de um repositório](/articles/setting-repository-visibility)" - "[Sobre bifurcações](/articles/about-forks)" - "[Gerenciando a política de bifurcação de seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" - "[Gerenciar a política de bifurcação para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" +- "{% if currentVersion == "free-pro-team@latest" %}[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}" diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/comparing-commits.md b/translations/pt-BR/content/github/committing-changes-to-your-project/comparing-commits.md index 1132eca9d9..256b11e73b 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/comparing-commits.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/comparing-commits.md @@ -27,9 +27,9 @@ Veja a seguir um exemplo de uma [comparação entre dois branches](https://githu ### Comparar tags -A comparação de tags de versão irá mostrar alterações no seu repositório desde a última versão. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)."{% endif %} +A comparação de tags de versão irá mostrar alterações no seu repositório desde a última versão. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %} Para obter mais informações, consulte "[Comparar versos](/github/administering-a-repository/comparing-releases)".{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page.{% else %} Instead of typing a branch name, type the name of your tag in the `compare` drop down menu.{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}Para comparar tags, você pode selecionar o nome de uma tag no menu suspenso `comparar` na parte superior da página.{% else %} Em vez de digitar o nome de um branch, digite o nome da sua tag no menu suspenso `comparar`.{% endif %} Veja a seguir o exemplo de uma [comparação entre duas tags](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3). diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index e0e23bf580..06b1572e0e 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -1,6 +1,6 @@ --- -title: Creating a commit with multiple authors -intro: 'You can attribute a commit to more than one author by adding one or more `Co-authored-by` trailers to the commit''s message. Co-authored commits are visible on {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.' +title: Criar um commit com vários autores +intro: 'Você pode atribuir um commit a mais de um autor adicionando um ou mais trailers "Co-authored-by" à mensagem do commit. Os commits de autoria conjunta são visíveis em {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} e podem ser incluídos no gráfico de contribuições do perfil e nas estatísticas do repositório{% endif %}.' redirect_from: - /articles/creating-a-commit-with-multiple-authors versions: @@ -9,41 +9,41 @@ versions: github-ae: '*' --- -### Required co-author information +### Informações obrigatórias do coautor -Before you can add a co-author to a commit, you must know the appropriate email to use for each co-author. For the co-author's commit to count as a contribution, you must use the email associated with their {% data variables.product.product_name %} account. +Para poder adicionar um coautor a um commit, você deve saber o e-mail adequado a ser usado para cada coautor. Para que o commit do coautor conte como uma contribuição, você deve usar o e-mail associado à conta do {% data variables.product.product_name %} dele. {% if currentVersion == "free-pro-team@latest" %} -If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy. Otherwise, the co-author's email will be available to the public in the commit message. If you want to keep your email private, you can choose to use a {% data variables.product.product_name %}-provided `no-reply` email for Git operations and ask other co-authors to list your `no-reply` email in commit trailers. +Se uma pessoa optar por manter o respectivo endereço de e-mail privado, você deverá usar o e-mail `no-reply` dela fornecido pelo {% data variables.product.product_name %} para proteger a privacidade. Caso contrário, o e-mail do coautor estará disponível para o público na mensagem do commit. Se desejar manter seu e-mail privado, você poderá usar um e-mail `no-reply` fornecido pelo {% data variables.product.product_name %} para operações de Git e pedir que outros coautores listem seu e-mail `no-reply` nos trailers de commit. -For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +Para obter mais informações, consulte "[Setting your commit email address](/articles/setting-your-commit-email-address)." {% tip %} - **Tip:** You can help a co-author find their preferred email address by sharing this information: - - To find your {% data variables.product.product_name %}-provided `no-reply` email, navigate to your email settings page under "Keep my email address private." - - To find the email you used to configure Git on your computer, run `git config user.email` on the command line. + **Dica:** você pode ajudar um coautor a encontrar o endereço de e-mail de preferência dele compartilhando essas informações: + - Para encontrar o e-mail `no-reply` fornecido pelo {% data variables.product.product_name %}, navegue até a página de configurações do e-mail em "Keep my email address private" (Manter meu endereço de e-mail privado). + - Para encontrar o e-mail usado para configurar o Git no seu computador, execute `git config user.email` na linha de comando. {% endtip %} {% endif %} -### Creating co-authored commits using {% data variables.product.prodname_desktop %} +### Criar commits coautorados usando o {% data variables.product.prodname_desktop %} -You can use {% data variables.product.prodname_desktop %} to create a commit with a co-author. For more information, see "[Write a commit message and push your changes](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)" and [{% data variables.product.prodname_desktop %}](https://desktop.github.com). +Você pode usar o {% data variables.product.prodname_desktop %} para criar um commit com um coautor. Para obter mais informações, consulte "[Escrever uma mensagem do commit e fazer push das alterações](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" e [{% data variables.product.prodname_desktop %}](https://desktop.github.com). -![Add a co-author to the commit message](/assets/images/help/desktop/co-authors-demo-hq.gif) +![Adicionar um coautor à mensagem do commit](/assets/images/help/desktop/co-authors-demo-hq.gif) -### Creating co-authored commits on the command line +### Criar commits coautorados na linha de comando {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} {% data reusables.pull_requests.commit-message-with-trailer-beginning %} -3. On the next line of the commit message, type `Co-authored-by: name ` with specific information for each co-author. After the co-author information, add a closing quotation mark. +3. Na próxima linha da mensagem do commit, digite `Co-authored-by: name ` com informações específicas para cada coautor. Depois das informações do coautor, adicione aspas de fechamento. - If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. + Se estiver adicionando vários coautores, dê a cada um a própria linha e o trailer de commit `Co-authored-by:`. ```shell $ git commit -m "Refactor usability tests. > @@ -52,27 +52,26 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit Co-authored-by: another-name <another-name@example.com>" ``` -The new commit and message will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/articles/pushing-commits-to-a-remote-repository/)." +O novo commit e a mensagem aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push. Para obter mais informações, consulte "[Fazer push das alterações em um repositório remoto](/articles/pushing-commits-to-a-remote-repository/)". -### Creating co-authored commits on {% data variables.product.product_name %} +### Criar commits coautorados no {% data variables.product.product_name %} -After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message. +Depois que fizer alterações em um arquivo usando o editor web no {% data variables.product.product_name %}, você poderá criar um commit coautorado adicionando um trailer `Co-authored-by:` à mensagem do commit. {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made. - ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png) -3. In the text box below your commit message, add `Co-authored-by: name ` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. +2. Depois de fazer as alterações juntos, na parte inferior da página, digite uma mensagem de commit curta e significativa que descreve as alterações feitas. ![Mensagem do commit para sua alteração](/assets/images/help/repository/write-commit-message-quick-pull.png) +3. Na caixa de texto abaixo da mensagem do commit, adicione `Co-authored-by: name ` com informações específicas para cada coautor. Se estiver adicionando vários coautores, dê a cada um a própria linha e o trailer de commit `Co-authored-by:`. - ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png) -4. Click **Commit changes** or **Propose changes**. + ![Exemplo de trailer de coautor da mensagem do commit na segunda caixa de texto da mensagem do commit](/assets/images/help/repository/write-commit-message-co-author-trailer.png) +4. Clique em **Commit changes** (Fazer commit de alterações) ou **Propose changes** (Propor alterações). -The new commit and message will appear on {% data variables.product.product_location %}. +O novo commit e a mensagem aparecerão no {% data variables.product.product_location %}. -### Further reading +### Leia mais {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" -- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} -- "[Viewing a summary of repository activity](/articles/viewing-a-summary-of-repository-activity)" -- "[Viewing a project's contributors](/articles/viewing-a-projects-contributors)" -- "[Changing a commit message](/articles/changing-a-commit-message)" -- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation +- "[Exibir contribuições no perfil](/articles/viewing-contributions-on-your-profile)" +- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} +- "[Exibir um resumo da atividade do repositório](/articles/viewing-a-summary-of-repository-activity)" +- "[Exibir contribuidores de um projeto](/articles/viewing-a-projects-contributors)" +- "[Alterar uma mensagem do commit](/articles/changing-a-commit-message)" +- "[Fazer commit e revisar alterações no seu projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" na documentação do {% data variables.product.prodname_desktop %} diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md b/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md index bfaea6e1b9..970af981ef 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md @@ -3,7 +3,7 @@ title: Por que meus commits estão vinculados ao usuário errado? redirect_from: - /articles/how-do-i-get-my-commits-to-link-to-my-github-account/ - /articles/why-are-my-commits-linked-to-the-wrong-user -intro: 'O {% data variables.product.product_name %} usa o endereço de e-mail no header do commit para vincular o commit a um usuário do GitHub. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% if currentVersion != "github-ae@latest" %}, add an email address to your account email settings, or do both{% endif %}.' +intro: 'O {% data variables.product.product_name %} usa o endereço de e-mail no header do commit para vincular o commit a um usuário do GitHub. Se seus commits estão sendo vinculados a outro usuário, ou não vinculados a um usuário, você pode precisar alterar suas configurações locais de configuração do Git, {% if currentVersion ! "github-ae@latest" %}, adicionar um endereço de e-mail nas configurações de e-mail da sua conta ou fazer ambas as coisas{% endif %}.' versions: free-pro-team: '*' enterprise-server: '*' @@ -19,10 +19,10 @@ versions: ### Commits vinculados a outro usuário -If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% if currentVersion == "github-ae@latest" %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Os commits antigos não serão vinculados. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your {% data variables.product.product_name %} account to link future commits to your account. +Se seus commits estiverem vinculados a outro usuário, isso significa que o endereço de e-mail nas configurações locais do Git está conectado à conta desse usuário em {% data variables.product.product_name %}. Neste caso, você pode alterar o e-mail nas configurações locais do Git, {% if currentVersion == "github-ae@latest" %} ao endereço associado à sua conta em {% data variables.product.product_name %} para vincular seus commits futuros. Os commits antigos não serão vinculados. Para obter mais informações, consulte "[Definir o seu endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git).{% else %} E adicione o novo endereço de e-mail à sua conta de {% data variables.product.product_name %} para vincular futuros commits à sua conta. -1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". Se você trabalha em várias máquinas, precisa alterar essa configuração em cada uma deles. -2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %} +1. Para alterar o endereço de e-mail na sua configuração Git local, siga os passos em "[Definir o seu endereço de e-mail de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". Se você trabalha em várias máquinas, precisa alterar essa configuração em cada uma deles. +2. Adicione o endereço de e-mail da etapa 2 às configurações da sua conta seguindo os passos em "[Adicionar um endereço de e-mail à sua conta GitHub](/articles/adding-an-email-address-to-your-github-account)".{% endif %} Os commits criados a partir daí serão vinculados à sua conta. @@ -35,12 +35,12 @@ Para verificar o endereço de e-mail usado para esses commits e conectar commits 1. Navegue até o commit clicando no link da mensagem do commit. ![Link da mensagem do commit](/assets/images/help/commits/commit-msg-link.png) 2. Para ler uma mensagem sobre o motivo do commit não estar vinculado, passe o mouse sobre o {% octicon "question" aria-label="Question mark" %} azul à direita do nome de usuário. ![Mensagem do commit exibida ao passar o mouse](/assets/images/help/commits/commit-hover-msg.png) - - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat. - - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} - - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} + - **Autor não reconhecido (com endereço de e-mail)** Se você vir esta mensagem com um endereço de e-mail, o endereço que você usou para criar o commit não estará conectado à sua conta em {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}Para vincular seus commits, [adicione o endereço de e-mail às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account).{% endif %} Se o endereço de e-mail tiver um Gravatar associado, o Gravatar será exibido ao lado do commit, em vez do Octoact cinza padrão. + - **Autor não reconhecido (sem endereço de e-mail)** Se você vir esta mensagem sem um endereço de e-mail, significa que você usou um endereço de e-mail genérico que não pode ser conectado à sua conta em {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} Você precisará [definir seu endereço de e-mail do commit no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %} + - **E-mail inválido** O endereço de e-mail nas configurações locais do Git está em branco ou não está formatado como um endereço de e-mail.{% if currentVersion != "github-ae@latest" %} Você precisará [definir seu endereço de e-mail de commit no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de email do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %} {% if currentVersion == "github-ae@latest" %} -You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Os commits antigos não serão vinculados. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)." +Você pode alterar o e-mail nas configurações locais do Git para o endereço associado à sua conta para vincular seus futuros commits. Os commits antigos não serão vinculados. Para obter mais informações, consulte "[Configurar o endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". {% endif %} {% warning %} diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index c6687d8c1e..0c1307f2a5 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -21,7 +21,7 @@ Solicita-se automaticamente que os proprietários do código revisem quando algu Quando alguém com permissões de administrador ou proprietário tiver habilitado revisões obrigatórias, se desejar, ele também poderá exigir aprovação de um proprietário do código para que o autor possa fazer merge de uma pull request no repositório. Para obter mais informações, consulte "[Habilitar revisões obrigatórias para pull requests](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)". -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Se uma equipe habilitou as atribuições de revisão de código, as aprovações individuais não vão atender ao requisito para a aprovação do proprietário do código em um branch protegido. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} Se um arquivo tiver um proprietário do código, você poderá ver quem é o proprietário do código antes de abrir um pull request. No repositório, é possível pesquisar o arquivo e passar o mouse sobre diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md index 8af95a7a89..83db816a29 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md @@ -1,6 +1,6 @@ --- -title: Sobre LEIAMEs -intro: 'Você pode adicionar um arquivo LEIAME ao seu repositório para informar outras pessoas por que seu projeto é útil, o que elas podem fazer com o projeto e como elas podem usá-lo.' +title: Sobre READMEs +intro: 'Você pode adicionar um arquivo README ao seu repositório para informar outras pessoas por que seu projeto é útil, o que elas podem fazer com o projeto e como elas podem usá-lo.' redirect_from: - /articles/section-links-on-readmes-and-blob-pages/ - /articles/relative-links-in-readmes/ @@ -11,36 +11,44 @@ versions: github-ae: '*' --- -Um arquivo LEIAME, junto com {% if currentVersion == "free-pro-team@latest" %}a [licença de repositório](/articles/licensing-a-repository), [diretrizes de contribuição](/articles/setting-guidelines-for-repository-contributors) e um [código de conduta](/articles/adding-a-code-of-conduct-to-your-project){% else %}uma [licença de repositório](/articles/licensing-a-repository) e diretrizes de contribuição [](/articles/setting-guidelines-for-repository-contributors){% endif %} ajudam você a comunicar as expectativas e gerenciar contribuições para o seu projeto. +### Sobre READMEs -Um LEIAME, muitas vezes, é o primeiro item que um visitante verá ao visitar seu repositório. Os arquivos LEIAME geralmente incluem informações sobre: +You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% if currentVersion == "free-pro-team@latest" %}, contribution guidelines, and a code of conduct{% elsif enterpriseServerVersions contains currentVersion %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions. + +For more information about providing guidelines for your project, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +Um README, muitas vezes, é o primeiro item que um visitante verá ao visitar seu repositório. Os arquivos README geralmente incluem informações sobre: - O que o projeto faz - Por que o projeto é útil - Como os usuários podem começar a usar o projeto - Onde os usuários podem obter ajuda com seu projeto - Quem mantém e contribui com o projeto -Se você colocar o arquivo LEIAME na raiz do repositório, `docs`, ou no diretório `.github` oculto, o {% data variables.product.product_name %} reconhecerá e apresentará automaticamente o LEIAME aos visitantes do repositório. +Se você colocar o arquivo README na raiz do repositório, `docs`, ou no diretório `.github` oculto, o {% data variables.product.product_name %} reconhecerá e apresentará automaticamente o README aos visitantes do repositório. -![Página principal do repositório github/scientist e seu arquivo LEIAME](/assets/images/help/repository/repo-with-readme.png) +![Página principal do repositório github/scientist e seu arquivo README](/assets/images/help/repository/repo-with-readme.png) {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.profile.profile-readme %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21"%} -![Arquivo LEIAME no nome de usuário/repositório do nome de usuário](/assets/images/help/repository/username-repo-with-readme.png) +{% data reusables.profile.profile-readme %} {% endif %} -### Links de seção nos arquivos LEIAME e páginas blob +![Arquivo README no nome de usuário/repositório do nome de usuário](/assets/images/help/repository/username-repo-with-readme.png) + +{% endif %} + +### Links de seção nos arquivos README e páginas blob Muitos projetos usam uma tabela de conteúdo no início de um LEIAME para direcionar usuários para diferentes seções do arquivo. {% data reusables.repositories.section-links %} -### Links relativos e caminhos de imagem em arquivos LEIAME +### Links relativos e caminhos de imagem em arquivos README {% data reusables.repositories.relative-links %} ### Leia mais - "[Adicionar um arquivo a um repositório](/articles/adding-a-file-to-a-repository)" -- "[Tornar LEIAMEs legíveis](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" da 18F +- "[Tornar READMEs legíveis](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" da 18F diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index 9e2fc6a4ec..e8d17c53d5 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -1,42 +1,43 @@ --- -title: About repository visibility -intro: 'You can restrict who has access to a repository by choosing a repository''s visibility: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}public, internal, or private{% elsif currentVersion == "github-ae@latest" %}private or internal{% else %} public or private{% endif %}.' +title: Sobre a visibilidade do repositório +intro: 'Você pode restringir quem tem acesso a um repositório escolhendo a visibilidade de um repositório: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}público, interno ou privado{% elsif currentVersion == "github-ae@latest" %}privado ou interno{% else %} público ou privado{% endif %}.' versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### About repository visibility +### Sobre a visibilidade do repositório -{% if currentVersion == "github-ae@latest" %}When you create a repository owned by your user account, the repository is always private. When you create a repository owned by an organization, you can choose to make the repository private or internal.{% else %}When you create a repository, you can choose to make the repository public or private.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} If you're creating the repository in an organization{% if currentVersion == "free-pro-team@latest" %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %} +{% if currentVersion == "github-ae@latest" %}Ao criar um repositório pertencente à sua conta de usuário, o repositório é sempre privado. Ao criar um repositório pertencente a uma organização, você pode optar por tornar o repositório privado ou interno.{% else %}Ao criar um repositório, você pode escolher tornar o repositório público ou privado.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} Se você estiver criando o repositório em uma organização{% if currentVersion == "free-pro-team@latest" %} pertencente a uma conta corporativa{% endif %}, você também poderá optar por tornar o repositório interno.{% endif %}{% endif %} {% if enterpriseServerVersions contains currentVersion %} -If {% data variables.product.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.product.product_location %}, including outside collaborators. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. {% if currentVersion ver_gt "enterprise-server@2.19" %} Internal repositories are accessible to enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)."{% endif %} +Se +{% data variables.product.product_location %} não está em modo privado ou por trás de um firewall, repositórios públicos podem ser acessados por todos na internet. Caso contrário, os repositórios públicos estarão disponíveis para todos usando {% data variables.product.product_location %}, incluindo colaboradores externos. Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização. {% if currentVersion ver_gt "enterprise-server@2.19" %} Repositórios internos podem ser acessados pelo integrantes da empresa. Para obter mais informações, consulte "[Sobre repositórios internos](#about-internal-repositories)."{% endif %} {% elsif currentVersion == "github-ae@latest" %} -Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." +Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização. Repositórios internos podem ser acessados por todos os integrantes da empresa. Para obter mais informações, consulte "[Sobre repositórios internos](#about-internal-repositories)." {% else %} -Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." +Os repositórios públicos podem ser acessados por todos na internet. Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização. Os repositórios internos podem ser acessados por todos os integrantes da empresa. Para obter mais informações, consulte "[Sobre repositórios internos](#about-internal-repositories)." {% endif %} -Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +Os proprietários da organização sempre têm acesso a todos os repositórios criados em uma organização. Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". -People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." +As pessoas com permissões de administrador para um repositório podem alterar a visibilidade de um repositório existente. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)". {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### About internal repositories +### Sobre repositórios internos {% note %} -**Note:** {% data reusables.gated-features.internal-repos %} +**Observação:** {% data reusables.gated-features.internal-repos %} {% endnote %} -{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." +{% data reusables.repositories.about-internal-repos %} Para obter mais informações sobre o innersource, consulte a documentação técnica do {% data variables.product.prodname_dotcom %}"[Uma introdução ao innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)". -All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% if currentVersion == "free-pro-team@latest" %}outside of the enterprise{% else %}who are not members of an organization{% endif %}, including outside collaborators on organization repositories. For more information, see {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and {% endif %}"[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." +Todos os integrantes da empresa têm permissões de leitura no repositório interno, mas os repositórios internos não são visíveis para pessoas {% if currentVersion == "free-pro-team@latest" %}que estão fora da empresa{% else %}que não são integrantes de uma organização{% endif %}, incluindo colaboradores externos em repositórios da organização. Para mais informações, consulte {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" e {% endif %}"[Níveis de permissão do repositório](/articles/repository-permission-levels-for-an-organization) da organização. {% data reusables.repositories.internal-repo-default %} -If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. +Se um usuário for removido de todas as organizações pertencentes à empresa, essas bifurcações do usuário dos repositórios internos do usuário serão removidas automaticamente. {% endif %} diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index f7fc86c5ee..e7de902eee 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -1,42 +1,44 @@ --- -title: Backing up a repository -intro: 'You can use{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Git and{% endif %} the API {% if currentVersion == "free-pro-team@latest" %}or a third-party tool {% endif %}to back up your repository.' +title: Fazer backup de um repositório +intro: 'Você pode usar{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} o Git e{% endif %} a API {% if currentVersion == "free-pro-team@latest" %}ou uma ferramenta de terceiros {% endif %}para fazer backup do seu repositório.' redirect_from: - - /articles/backing-up-a-repository + - Backing up a repository versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- + {% if currentVersion == "free-pro-team@latest" %} -To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/v3/migrations/)." +Para baixar um arquivo do seu repositório, você pode usar a API para usuário ou migrações da organização. Para obter mais informações, consulte "[Migrações](/rest/reference/migrations)". {% else %} -You can download and back up your repositories manually: +Você pode baixar e fazer backup dos repositórios manualmente: -- To download a repository's Git data to your local machine, you'll need to clone the repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -- You can also download your repository's wiki. For more information, see "[Adding or editing wiki pages](/articles/adding-or-editing-wiki-pages)." +- Para baixar os dados Git de um repositório no computador local, é preciso clonar o repositório. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)". +- Também é possível baixar o wiki do repositório. Para obter mais informações, consulte "[Adicionar ou editar páginas wiki](/articles/adding-or-editing-wiki-pages)". -When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your {% data variables.product.product_name %} repository to your local machine: +Quando você clona um repositório ou wiki, somente os dados Git, como arquivos e histórico de commits do projeto, são baixados. Você pode usar nossa API para exportar outros elementos do seu repositório do {% data variables.product.product_name %} para o computador local: -- [Issues](/v3/issues/#list-issues-for-a-repository) -- [Pull requests](/v3/pulls/#list-pull-requests) -- [Forks](/rest/reference/repos#list-forks) -- [Comments](/rest/reference/issues#list-issue-comments-for-a-repository) -- [Milestones](/rest/reference/issues#list-milestones) -- [Labels](/rest/reference/issues#list-labels-for-a-repository) -- [Watchers](/rest/reference/activity#list-watchers) -- [Stargazers](/rest/reference/activity#list-stargazers) -- [Projects](/v3/projects/#list-repository-projects) +- [Problemas](/rest/reference/issues#list-issues-for-a-repository) +- [Pull requests](/rest/reference/pulls#list-pull-requests) +- [Bifurcações](/rest/reference/repos#list-forks) +- [Comentários](/rest/reference/issues#list-issue-comments-for-a-repository) +- [Marcos](/rest/reference/issues#list-milestones) +- [Etiquetas](/rest/reference/issues#list-labels-for-a-repository) +- [Inspetores](/rest/reference/activity#list-watchers) +- [observador](/rest/reference/activity#list-stargazers) +- [Projetos](/rest/reference/projects#list-repository-projects) {% endif %} -Once you have {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). +Depois de ter {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}uma versão local de todo o conteúdo do qual você deseja fazer backup, você pode criar um arquivo zip e, {% else %} após baixar o seu arquivo, você pode {% endif %}copiá-lo para um disco rígido externo e/ou enviá-lo para um serviço de backup baseado em nuvem como o [Google Drive](https://www.google.com/drive/) ou [Dropbox](https://www.dropbox.com/). {% if currentVersion == "free-pro-team@latest" %} -### Third-party backup tools +### Ferramentas de backup de terceiros -A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." +Existem várias ferramentas de autoatendimento que automatizam backups de repositórios. Ao contrário de projetos arquivados, que arquivam _todos_ os repositórios públicos em {% data variables.product.product_name %} que não tenham optado por não participar e tornam os dados acessíveis para todos, as ferramentas de backup irão fazer o download dos dados de repositórios _específicos_ e organizá-los em um novo branch ou diretório. Para obter mais informações sobre projetos de arquivamento, consulte "[Sobre arquivamento de conteúdo e dados no {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". +Você pode fazer backup de todos os dados de um repositório Git (como arquivos de projeto e histórico de commit), bem como da quantidade de dados de -You can back up all of a repository's Git data (such as project files and commit history), as well as much data from {% data variables.product.product_name %} (such as issues and pull requests), with [BackHub](https://github.com/marketplace/backhub), which creates daily recurring backups of your repositories with snapshots up to 30 days back in time. BackHub is available in {% data variables.product.prodname_marketplace %}. +{% data variables.product.product_name %} (como problemas e pull requests), com [BackHub](https://github.com/marketplace/backhub), que cria backups recorrentes diários dos seus repositórios com instantâneos de até 30 dias no tempo. O BackHub está disponível no {% data variables.product.prodname_marketplace %}. {% endif %} diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md index 39778d159c..9533cf884f 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md @@ -1,7 +1,7 @@ --- -title: Creating a template repository -intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}, branches,{% endif %} and files.' -permissions: Anyone with admin permissions to a repository can make the repository a template. +title: Criar um repositório de modelos +intro: 'Você pode fazer um repositório existente um modelo, assim você e outros podem gerar novos repositórios com a mesma estrutura de diretório{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}, branches,{% endif %} e arquivos.' +permissions: Qualquer pessoa com permissões de administrador em um repositório pode transformar o repositório em um modelo. redirect_from: - /articles/creating-a-template-repository versions: @@ -12,15 +12,14 @@ versions: {% note %} -**Note**: Your template repository cannot include files stored using {% data variables.large_files.product_name_short %}. +**Observação**: Seu repositório de modelo não pode incluir arquivos armazenados usando {% data variables.large_files.product_name_short %}. {% endnote %} -To create a template repository, you must create a repository, then make the repository a template. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." +Para criar um repositório de modelos, é preciso criar um repositório e, em seguida, torná-lo um modelo. Para obter mais informações sobre como criar um repositório, consulte "[Criar um repositório](/articles/creating-a-new-repository)". -After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." +Depois de fazer o seu repositório um modelo, qualquer pessoa com acesso ao repositório pode gerar um novo repositório com a mesma estrutura de diretório e arquivos, assim como o branch padrão. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Eles também podem optar por incluir todos os outros branches no seu repositório.{% endif %} Para obter mais informações, consulte "[Criar um repositório de um modelo](/articles/creating-a-repository-from-a-template)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Select **Template repository**. - ![Checkbox to make a repository a template](/assets/images/help/repository/template-repository-checkbox.png) +1. Selecione **Template repository** (Repositório de modelos). ![Caixa de seleção para transformar um repositório em modelo](/assets/images/help/repository/template-repository-checkbox.png) diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index b84b840535..3b571dd4fc 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -1,6 +1,6 @@ --- title: 'Erro: repositório não encontrado' -intro: '{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}If you see this error when cloning a repository, it means that the repository does not exist or you do not have permission to access it.{% else %}If you see this error when cloning a repository, it means that the repository does not exist, you do not have permission to access it, or {% data variables.product.product_location %} is in private mode.{% endif %} There are a few solutions to this error, depending on the cause.' +intro: '{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}Se você vir este erro ao clonar um repositório, significa que o repositório não existe ou que você não tem permissão para acessá-lo.{% else %}Se você vir este erro ao clonar um repositório, significa que o repositório não existe, você não tem permissão para acessá-lo ou {% data variables.product.product_location %} está em modo privado.{% endif %} Existem algumas soluções para este erro, dependendo da causa.' redirect_from: - /articles/error-repository-not-found versions: diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 400b26f9ba..6d96daa92f 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -7,7 +7,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '*' - github-ae: '*' --- ### Escolher a licença ideal @@ -18,7 +17,7 @@ Você não tem qualquer obrigação de escolher uma licença. Entretanto, sem um {% note %} -**Observação:** Se você publicar seu código-fonte em um repositório público no GitHub, {% if currentVersion == "free-pro-team@latest" %}de acordo com os [termos de serviço](/articles/github-terms-of-service), {% endif %}outros usuários do GitHub terão o direito de visualizar e bifurcar o seu repositório no site do GitHub. Se você já criou um repositório público e não quer mais que os usuários tenham acesso a ele, você pode transformar seu repositório em privado. Ao converter um repositório público em repositório privado, as bifurcações ou cópias locais criadas por outros usuários continuam existindo. Para obter mais informações, consulte "[Converter um repositório público em privado](/articles/making-a-public-repository-private)". +**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% if currentVersion == "free-pro-team@latest" %}according to the [Terms of Service](/articles/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)". {% endnote %} @@ -75,7 +74,7 @@ Quando você pesquisar uma família de licenças, os resultados incluirão todas ### Identificar uma licença -[A licenciada de código aberto Ruby gem ](https://github.com/benbalter/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/v3/licenses/) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](http://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[A licenciada de código aberto Ruby gem ](https://github.com/benbalter/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](http://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). Caso o seu repositório use uma licença listada no site Choose a License que não aparece na parte superior da página do repositório, ele pode conter licenças múltiplas ou outras complexidades. Para que sua licença seja detectada, simplifique o arquivo *LICENSE* e anote a complexidade em algum outro local, como no arquivo *LEIAME* do repositório. diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md index a7db1b9342..d1ba863b8f 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- title: Usar espaços de código no Visual Studio Code -intro: 'Você pode desenvolver seu codespace diretamente em {% data variables.product.prodname_vscode %}, conectando a extensão de {% data variables.product.prodname_vs_codespaces %} à sua conta no {% data variables.product.product_name %}.' +intro: 'Você pode desenvolver seu codespace diretamente em {% data variables.product.prodname_vscode %}, conectando a extensão de {% data variables.product.prodname_github_codespaces %} à sua conta no {% data variables.product.product_name %}.' product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code @@ -12,17 +12,16 @@ versions: ### Pré-requisitos -Antes de poder desenvolver em um código diretamente em {% data variables.product.prodname_vscode %}, você deverá configurar a extensão {% data variables.product.prodname_vs_codespaces %} para conectar-se à sua conta do {% data variables.product.product_name %}. +Para desenvolver em um código diretamente em {% data variables.product.prodname_vscode %}, você deve inscrever-se na extensão de {% data variables.product.prodname_github_codespaces %}. A extensão de {% data variables.product.prodname_github_codespaces %} exige a versão de outubro de 2020 1.51 ou posterior de {% data variables.product.prodname_vscode %}. -1. Use o {% data variables.product.prodname_vs %} Marketplace para instalar a extensão [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode %}. -2. Clique no ícone Extensões na barra lateral esquerda do {% data variables.product.prodname_vscode %}. ![O ícone das extensões em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-extensions-icon-vscode.png) -3. Abaixo do {% data variables.product.prodname_vs_codespaces %}, clique no ícone Gerenciar e, em seguida, clique em **Configurações de extensão**. ![A opção Configurações de extensão](/assets/images/help/codespaces/select-extension-settings.png) -4. Use o menu suspenso "Vsonline: Provedor de Conta", e selecione {% data variables.product.prodname_dotcom %}. ![Definir o provedor de conta para {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/select-account-provider-vscode.png) +1. Use o + +Marketplace de {% data variables.product.prodname_vs %} para instalar a [extensão de {% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -6. Se {% data variables.product.prodname_codespaces %} não estiver selecionado no cabeçalho, clique em **{% data variables.product.prodname_codespaces %}**. ![Cabeçalho do {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png) -7. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_codespaces %}...**. ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -8. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. -9. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. +2. Utilize o menu suspenso "EXPLORADOR REMOTO" e clique em **{% data variables.product.prodname_github_codespaces %}**. ![Cabeçalho do {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png) +3. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_codespaces %}...**. ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) +4. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. +5. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. ### Criar um codespace em {% data variables.product.prodname_vscode %} @@ -31,8 +30,8 @@ Depois de conectar sua conta de {% data variables.product.product_name %} à ext {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Clique no ícone Adicionar e, em seguida, clique em **Criar novo codespace**. ![A opção "Criar novo codespace" em {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) 3. Digite e, em seguida, clique no nome do repositório no qual você deseja desenvolver. ![Pesquisar um repositório para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Clique na branch no qual você deseja desenvolver. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) - +4. Clique no branch que você deseja desenvolver. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) +5. Clique no tipo de instância que você deseja desenvolver. ![Tipos de instância para um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) ### Abrir um codespace em {% data variables.product.prodname_vscode %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md index c6db8c6e28..bac5176dd9 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -46,8 +46,12 @@ A conexão ao {% data variables.product.prodname_github_codespaces %} com a pré ### Configurar um codespace para {% data variables.product.prodname_vs %} -O ambiente de codespace padrão criado pelo {% data variables.product.prodname_vs %} inclui estruturas e ferramentas populares como .NET Core, Microsoft SQL Server, Python e Windows SDK. O {% data variables.product.prodname_github_codespaces %} criado com {% data variables.product.prodname_vs %} pode ser personalizado por meio de um subconjunto de propriedades do `devcontainers.json` e uma nova ferramenta denominada devinit, incluída com o {% data variables.product.prodname_vs %}. +A codespace, created with {% data variables.product.prodname_vs %}, can be customized through a new tool called devinit, a command line tool included with {% data variables.product.prodname_vs %}. #### devinit -A ferramenta de linha de comando [devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) permite que você instale estruturas adicionais e ferramentas em seus códigos de desenvolvimento do Windows, além de executar scripts de PowerShell ou modificar variáveis de ambiente. A devinit é compatível com um arquivo de configuração denominado [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json), que pode ser adicionado ao seu projeto para criar ambientes de desenvolvimento personalizados e repetíveis. Para obter mais informações sobre a configuração do codespace do Windows e sobre a devinit, consulte [Personalizar um codespace](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces) na documentação do {% data variables.product.prodname_vs %}. +[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) lets you install additional frameworks and tools into your Windows development codespaces, modify environment variables, and more. + +devinit supports a configuration file called [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). You can add this file to your project if you want to create a customized and repeatable development environment. When you use devinit with a [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) file, your codespaces will be automatically configured on creation. + +Para obter mais informações sobre a configuração do codespace do Windows e sobre a devinit, consulte [Personalizar um codespace](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces) na documentação do {% data variables.product.prodname_vs %}. For more information about devinit, see [Getting started with devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit). diff --git a/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md index 1287fb6be5..22f48c00a9 100644 --- a/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -43,4 +43,4 @@ Para evitar esses alertas, você pode usar o cache de senhas do Git. Para obter ### Leia mais -- "[Autorizando aplicativos OAuth](/v3/oauth/)" +- "[Autorizando aplicativos OAuth](/developers/apps/authorizing-oauth-apps)" diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index ff27712b49..c562deae1a 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -1,6 +1,6 @@ --- -title: About code scanning -intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' +title: Sobre a varredura de código +intro: 'Você pode usar {% data variables.product.prodname_code_scanning %} para encontrar vulnerabilidades e erros de segurança no código do seu projeto no {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/about-automated-code-scanning @@ -12,40 +12,39 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About {% data variables.product.prodname_code_scanning %} +### Sobre o {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.about-code-scanning %} -You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. +Você pode usar {% data variables.product.prodname_code_scanning %} para encontrar, triar e priorizar correções de problemas existentes em seu código. {% data variables.product.prodname_code_scanning_capc %} também impede que os desenvolvedores apresentem novos problemas. É possível programar verificações para dias e horários específicos ou acionar varreduras quando ocorre um evento específico no repositório, como, por exemplo, um push. -If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." +Se {% data variables.product.prodname_code_scanning %} encontrar uma vulnerabilidade potencial ou erro no seu código, {% data variables.product.prodname_dotcom %} exibirá um alerta no repositório. Depois de corrigir o código que desencadeou o alerta, {% data variables.product.prodname_dotcom %} fechará o alerta. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. -For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/v3/code-scanning)." +{% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}. Para mais informações sobre endpoints de API, consulte "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." -To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +Para começar com {% data variables.product.prodname_code_scanning %}, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)." -### About {% data variables.product.prodname_codeql %} +### Sobre o {% data variables.product.prodname_codeql %} -You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +Você pode visualizar e contribuir para as consultas do {% data variables.product.prodname_code_scanning %} no repositório [`github/codeql`](https://github.com/github/codeql). O {% data variables.product.prodname_codeql %} trata o código como dados, permitindo que você encontre possíveis vulnerabilidades em seu código com maior confiança do que os analisadores estáticos tradicionais. -{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. +{% data variables.product.prodname_ql %} é a linguagem de consulta que move {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} é uma linguagem de programação lógica voltada para objetos. {% data variables.product.company_short %}, especialistas em idiomas e pesquisadores de segurança criam as consultas usadas para {% data variables.product.prodname_code_scanning %} e as consultas são de código aberto. A comunidade mantém e atualiza as consultas para melhorar a análise e reduzir falsos positivos. Para obter mais informações, consulte [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) no site do GitHub Security Lab. -{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. +Para obter mais informações sobre os pontos de extremidade da API para {% data variables.product.prodname_code_scanning %}, consulte "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)". {% data reusables.code-scanning.supported-languages %} -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. +Você pode visualizar e contribuir para as consultas do {% data variables.product.prodname_code_scanning %} no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %} consultas](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) na documentação do {% data variables.product.prodname_codeql %}. {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### Sobre a cobrança do {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}, e cada execução de um fluxo de trabalho de {% data variables.product.prodname_code_scanning %} consome minutos para {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". {% endif %} -### About third-party code scanning tools +### Ferramentas de varredura de código de terceiros {% data reusables.code-scanning.you-can-upload-third-party-analysis %} @@ -53,9 +52,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### Further reading +### Leia mais {% if currentVersion == "free-pro-team@latest" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} - [{% data variables.product.prodname_security %}](https://securitylab.github.com/) -- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website +- [Formato de Intercâmbio de Resultados de Análise Estática OASIS (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) no site do Comitê OASIS diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 0cc08d5b3c..9e982a020e 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -1,8 +1,8 @@ --- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' +title: Configurar a varredura do código +intro: 'Você pode configurar como o {% data variables.product.prodname_dotcom %} faz a varredura do código no seu projeto com relação a vulnerabilidades e erros.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' +permissions: 'Pessoas com permissões de gravação para um repositório podem configurar {% data variables.product.prodname_code_scanning %} para o repositório.' miniTocMaxHeadingLevel: 4 versions: free-pro-team: '*' @@ -12,59 +12,47 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### About {% data variables.product.prodname_code_scanning %} configuration +### Sobre a configuração do {% data variables.product.prodname_code_scanning %} -You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. 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)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." +Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}, usando {% data variables.product.prodname_actions %} ou a partir do seu sistema de integração contínua (CI), usando o {% data variables.product.prodname_codeql_runner %}. Para obter 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)." Para obter mais informações sobre o {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". -This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +Este artigo é sobre executar {% data variables.product.prodname_code_scanning %} dentro de {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +Antes de poder configurar o {% data variables.product.prodname_code_scanning %} para um repositório, você deve habilitar o {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho do {% data variables.product.prodname_actions %} ao repositório. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). {% data reusables.code-scanning.edit-workflow %} -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. +A análise de {% data variables.product.prodname_codeql %} é apenas um tipo de {% data variables.product.prodname_code_scanning %} que você pode fazer em {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} em {% data variables.product.prodname_dotcom_the_website %}{% endif %} contém outros fluxos de trabalho de {% data variables.product.prodname_code_scanning %} que você pode usar. {% if currentVersion == "free-pro-team@latest" %}Você pode encontrar uma seleção destes na página "Começar com {% data variables.product.prodname_code_scanning %}" que você pode acessar na aba **{% octicon "shield" aria-label="The shield symbol" %} Segurança** .{% endif %} Os exemplos específicos apresentados neste artigo estão relacionados ao arquivo de {% data variables.product.prodname_codeql_workflow %}. -### Editing a {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +O {% data variables.product.prodname_dotcom %} salva arquivos de fluxo de trabalho no diretório _.github/workflows_ do seu repositório. You can find the workflow by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. No seu repositório, pesquise o arquivo do fluxo de trabalho que você deseja editar. +1. No canto superior direito da vista do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %} para abrir o editor do fluxo de trabalho. ![Edite o botão do arquivo do fluxo de trabalho](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. Depois de ter editado o arquivo, clique em **Iniciar commit** e preencha o formulário "Alterações do commit". Você pode escolher o "commit" diretamente no branch atual ou criar um novo branch e iniciar um pull request. ![Atualização do commit para o fluxo de trabalho do codeql.yml](/assets/images/help/repository/code-scanning-workflow-update.png) -For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +Para obter mais informações sobre a edição de arquivos do fluxo de trabalho, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". -### Configuring frequency +### Configurar a frequência -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +Você pode fazer a varredura de código de forma pré-programada ou quando ocorrerem eventos específicos em um repositório. -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +A varredura do código a cada push para o repositório, e toda vez que um pull request é criado, isso impede que os desenvolvedores introduzam novas vulnerabilidades e erros no código. A varredura do código de forma pré-programada informa as últimas vulnerabilidades e erros de {% data variables.product.company_short %}, que os pesquisadores de segurança e da comunidade, mesmo quando desenvolvedores não estão mantendo o repositório de forma ativa. -#### Scanning on push +#### Fazer a varredura no push -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +Se você usar o fluxo de trabalho padrão, o {% data variables.product.prodname_code_scanning %} fará a varredura do código no repositório uma vez por semana, além das varreduras acionadas pelos eventos. Para ajustar essa programação, edite o valor `CRON` no fluxo de trabalho. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)". -#### Scanning pull requests +#### Fazer a varredura de pull requests -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. {% if currentVersion ver_gt "enterprise-server@2.21" %}O evento `pull_request` não será acionado se o pull request foi aberto através de uma bifurcação privada.{% else %}Se um pull request for de um fork privado, o evento `pull_request` só será acionado se você tiver selecionado a opção "Executar fluxos de trabalho a partir de pull requests" nas configurações do repositório. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."{% endif %} -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +Para obter mais informações sobre o evento `pull_request` , consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". -#### Scanning on a schedule +#### Avoiding unnecessary scans of pull requests -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." - -{% note %} - -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. - -{% endnote %} - -#### Example - -The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. +You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. ``` yaml on: @@ -72,20 +60,54 @@ on: branches: [main, protected] pull_request: branches: [main] + paths-ignore: + - '**/*.md' + - '**/*.txt' +``` + +{% note %} + +**Observações** + +* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." +* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. + +{% endnote %} + +For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." + +#### Fazer a varredura de forma pré-programada + +O fluxo de trabalho padrão do {% data variables.product.prodname_code_scanning %} usa o evento `on.push` para acionar uma varredura de código em cada push para qualquer branch que contém o arquivo de fluxo de trabalho. Para ajustar essa programação, edite o valor `CRON` no fluxo de trabalho. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)". + +{% note %} + +**Observação**: {% data variables.product.prodname_dotcom %} executa apenas trabalhos programados que estão em fluxos de trabalho no branch-padrão. Alterar a programação de um fluxo de trabalho em qualquer outro branch não terá efeito até que você mescle o branch com o branch-padrão. + +{% endnote %} + +#### Exemplo + +O exemplo a seguir mostra um {% data variables.product.prodname_codeql_workflow %} para um repositório em particular que possui um branch-padrão denominado `principal` e um branch protegido denominado `protegido`. + +``` yaml +on: + push: + pull_request: schedule: - cron: '0 15 * * 0' ``` -This workflow scans: -* Every push to the default branch and the protected branch -* Every pull request to the default branch -* The default branch at 3 P.M. every Sunday +Este fluxo de trabalho faz a varredura: +* Cada push para o branch-padrão e o branch protegido +* Cada pull request para o branch-padrão +* O branch-padrão às 15h. todo domingo -### Specifying an operating system +### Especificar um sistema operacional -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} +Se seu código exigir um sistema operacional específico para compilar, você poderá configurar o sistema operacional em seu {% data variables.product.prodname_codeql_workflow %}. Edite o valor de `jobs.analyze.runs-on` para especificar o sistema operacional para a máquina que executa suas ações de {% data variables.product.prodname_code_scanning %}. {% if currentVersion ver_gt "enterprise-server@2. 1" %}Você especifica o sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos após `auto-hospedado`.{% else %} -If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} +Se você optar por usar um executor auto-hospedado para varredura de código, você pode especificar um sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos, após `auto-hospedado`.{% endif %} ``` yaml jobs: @@ -94,23 +116,23 @@ jobs: runs-on: [self-hosted, ubuntu-latest] ``` -{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +O {% data variables.product.prodname_code_scanning_capc %} é compatível com as versões mais recentes do macOS, Ubuntu, e Windows. Portanto, os valores típicos para essa configuração são `ubuntu-latest`, `windows-latest` e `macos-latest`. Para obter mais informações, consulte {% if currentVersion ver_gt "enterprise-server@2. 1" %}"[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" e "[Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxe de fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." -{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}Você deve garantir que o Git esteja na variável do PATH em seus executores auto-hospedados.{% else %}Se você usa um executor auto-hospedado, você deve garantir que o Git esteja na variável de PATH.{% endif %} -### Changing the languages that are analyzed +### Alterar as linguagens que são analisadas -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages. +O {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} detecta automaticamente código escrito nas linguagens compatíveis. {% data reusables.code-scanning.supported-languages %} -The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +O arquivo padrão do {% data variables.product.prodname_codeql_workflow %} contém uma matriz de criação denominada `linguagem` que lista as linguagens no seu repositório que são analisadas. O {% data variables.product.prodname_codeql %} preenche automaticamente esta matriz quando você adiciona o {% data variables.product.prodname_code_scanning %} a um repositório. Usar a matriz de `linguagem` otimiza {% data variables.product.prodname_codeql %} para executar cada análise em paralelo. Recomendamos que todos os fluxos de trabalho adotem esta configuração devido aos benefícios de desempenho de criações paralelas. Para obter mais informações sobre matrizes de criação, consulte "[Gerenciar fluxos de trabalho complexos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)". {% data reusables.code-scanning.specify-language-to-analyze %} -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix. +Se o seu fluxo de trabalho usar a matriz de linguagem `, o {% data variables.product.prodname_codeql %} será codificado para analisar apenas as linguagens da matriz. Para alterar as linguagens que você deseja analisar, edite o valor da variável da matriz. Você pode remover uma linguagem para evitar que ele seja analisado ou adicionar uma linguagem que não estava presente no repositório quando o {% data variables.product.prodname_code_scanning %} estava habilitado. Por exemplo, se o repositório inicialmente continha apenas JavaScript quando {% data variables.product.prodname_code_scanning %} foi habilitado e, posteriormente, você adicionou o código Python, você precisará adicionar o python` à matriz. ```yaml jobs: @@ -122,24 +144,24 @@ jobs: matrix: language: ['javascript', 'python'] ``` - -If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. + +Se o seu fluxo de trabalho não contiver uma matriz denominada `linguagem`, o {% data variables.product.prodname_codeql %} será configurado para executar a análise sequencialmente. Se você não especificar as linguagens no fluxo de trabalho, o {% data variables.product.prodname_codeql %} irá detectar automaticamente e tentará analisar quaisquer linguagens compatíveis no repositório. Se você quiser escolher quais linguagens analisar sem usar uma matriz, você poderá usar o parâmetro `linguagens` na ação `init`. ```yaml - uses: github/codeql-action/init@v1 with: languages: cpp, csharp, python -``` +``` {% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies +### Analisar as dependências do Python -For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: +Para executores hospedados no GitHub, que usam apenas Linux, o {% data variables.product.prodname_codeql_workflow %} tentará instalar automaticamente as dependências do Python para dar mais resultados para a análise do CodeQL. Você pode controlar este comportamento especificando o parâmetro `setup-python-dependencies` para a ação chamada pela etapa "Initialize CodeQL". Por padrão, esse parâmetro é definido como `verdadeiro`: -- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies. +- Se o repositório contiver código escrito em Python, a etapa "Initialize CodeQL" instalará as dependências necessárias no executor hospedado pelo GitHub. Se a instalação automática for bem-sucedida, a ação também definirá a variável de ambiente `CODEQL_PYTHON` para o arquivo Python executável que inclui as dependências. -- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete. +- Se o repositório não tiver dependências do Python ou se as dependências forem especificadas de forma inesperada, você receberá um aviso e a ação continuará com os trabalhos restantes. A ação pode ser executada com sucesso, mesmo quando houver problemas de interpretação de dependências, mas os resultados podem estar incompletos. -Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract: +Alternativamente, você pode instalar as dependências do Python manualmente em qualquer sistema operacional. Você precisará adicionar as `setup-python-dependencies` e definir como `falso`, além de definir `CODEQL_PYTHON` como o executável do Python que inclui as dependências, conforme mostrado neste trecho do fluxo de trabalho: ```yaml jobs: @@ -170,14 +192,14 @@ jobs: # Override the default behavior so that the action doesn't attempt # to auto-install Python dependencies setup-python-dependencies: false -``` +``` {% endif %} -### Running additional queries +### Executar consultas adicionais {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. +Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. ``` yaml - uses: github/codeql-action/init@v1 @@ -185,13 +207,13 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu queries: COMMA-SEPARATED LIST OF PATHS ``` -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +Você também pode executar suítes de consultas adicionais especificando-os em um arquivo de configuração. Os suítes de consulta são coleções de consultas, geralmente agrupados por finalidade ou linguagem. {% data reusables.code-scanning.codeql-query-suites %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +Você pode executar consultas adicionais especificando-as em um arquivo de configuração. Se você desejar executar o conjunto combinado de consultas adicionais especificadas aqui e no arquivo de configuração, determine previamente o valor de `consultas` no fluxo de trabalho com o símbolo `+`. Para obter exemplos de arquivos de configuração, consulte "[Exemplo de arquivos de configuração](#example-configuration-files)". -In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. +Para incluir um ou mais suites de consulta, adicione uma seção `consultas` ao seu arquivo de configuração. ``` yaml - uses: github/codeql-action/init@v1 @@ -200,11 +222,11 @@ In the following example, the `+` symbol ensures that the specified additional q queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main ``` -### Using a custom configuration file +### Usar uma ferramenta de varredura de código de terceiros -As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. +Como alternativa à especificação de quais consultas executar no arquivo de fluxo de trabalho, você poderá fazer isso em um arquivo de configuração separado. Você também pode usar um arquivo de configuração para desativar as consultas-padrão e especificar quais diretórios escanear durante a análise. -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. +No arquivo de workflow use o parâmetro `config-file` da ação `init` para especificar o caminho para o arquivo de configuração que você deseja usar. Este exemplo carrega o arquivo de configuração _./.github/codeql/codeql-config.yml_. ``` yaml - uses: github/codeql-action/init@v1 @@ -212,11 +234,11 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp config-file: ./.github/codeql/codeql-config.yml ``` -The configuration file can be located within the local repository, or in a public, remote repository. For remote repositories, you can use the _owner/repository/file.yml@branch_ syntax. The settings in the file are written in YAML format. - -#### Specifying additional queries +O arquivo de configuração pode ser localizado no repositório local ou em um repositório remoto público. Para repositórios remotos, você pode usar a sintaxe _owner/repository/file.yml@branch_. As configurações no arquivo são escritas no formato YAML. -You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file. +#### Especificar consultas adicionais + +Você especifica consultas adicionais em um array de `consultas`. Cada elemento do array contém um parâmetro de `uso` com um valor que identifica um único arquivo de consulta, um diretório que contém arquivos de consulta ou um arquivo de definição do conjunto de consulta. ``` yaml queries: @@ -225,59 +247,59 @@ queries: - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls ``` -Optionally, you can give each array element a name, as shown in the example configuration files below. +Opcionalmente, você pode dar um nome a cada elemento do array, conforme mostrado nos exemplos de arquivos de configuração abaixo. -For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. +Para obter mais informações sobre consultas adicionais, consulte "[Executar consultas adicionais](#running-additional-queries) acima. -#### Disabling the default queries +#### Desativar as consultas-padrão -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +Se você desejar apenas executar consultas personalizadas, você poderá desabilitar as consultas de segurança padrão adicionando `disable-default-queries: true` ao seu arquivo de configuração. -#### Specifying directories to scan +#### Especificar diretórios para serem varridos -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from scans by adding a `paths-ignore` array. +Para as linguagens interpretadas com as quais {% data variables.product.prodname_codeql %} é compatível (Python e JavaScript/TypeScript), você pode restringir {% data variables.product.prodname_code_scanning %} para arquivos em diretórios específicos adicionando um array de `caminhos` para o arquivo de configuração. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. ``` yaml -paths: +paths: - src paths-ignore: - - node_modules + - src/node_modules - '**/*.test.js' ``` {% note %} -**Note**: +**Observação**: -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* As palavras-chave `caminhos` e `paths-ignore`, usados no contexto do arquivo de configuração do {% data variables.product.prodname_code_scanning %}, não deve ser confundido com as mesmas palavras-chave usadas para `on..paths` em um fluxo de trabalho. Quando estão acostumados a modificar `on.` em um fluxo de trabalho, eles determinam se as ações serão executadas quando alguém modifica o código nos diretórios especificados. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". +* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. Por exemplo, `foo/**`, `**/foo` e `foo/**/bar` são todos de sintaxe permitida, mas `**foo` não é. No entanto, você pode usar estrelas únicas junto com outros caracteres, conforme mostrado no exemplo. Você precisará colocar entre aspas qualquer coisa que contenha um caractere `*`. {% endnote %} -For C/C++, C#, and Java, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. Os comandos que você precisa usar para excluir um diretório da criação dependerão do seu sistema de criação. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o código em diretórios específicos. Você deverá excluir diretórios nas suas etapas de criação e usar as palavras-chave `paths-ignore` e `caminhos` para [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) no seu arquivo de fluxo de trabalho. -#### Example configuration files +#### Exemplo de arquivo de configuração {% data reusables.code-scanning.example-configuration-files %} -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages +### Configurar o {% data variables.product.prodname_code_scanning %} para linguagens compiladas {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} -{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)." +{% data reusables.code-scanning.autobuild-add-build-steps %} Para obter mais informações sobre como configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} para linguagens compiladas, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)". -### Accessing private repositories +### Acessar repositórios privados -If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs..steps.env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." +Se o seu fluxo de trabalho para {% data variables.product.prodname_code_scanning %} acessar repositórios privados no {% data variables.product.prodname_dotcom %}, você deverá configurar o Git para efetuar a autenticação com um token de acesso pessoal. Defina o segredo no ambiente do executor usando `jobs..steps.env` no seu fluxo de trabalho antes de qualquer ação do {% data variables.product.prodname_codeql %}. Para mais informações consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" e "[Criar e armazenar segredos criptografados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". -For example, the following configuration has Git replace the full URLs to the `github/foo`, `github/bar`, and `github/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. +Por exemplo, a configuração a seguir faz com que o Git substitua todas as URLs para os repositórios `github/foo`, `github/bar` e `github/baz` em {% data variables.product.prodname_dotcom_the_website %} por URLs que incluem o token de acesso pessoal que você armazena na variável de ambiente `ACCESS_TOKEN`. {% raw %} ```yaml steps: -- name: Configure access to private repositories +- name: Configure access to private repository on GitHub.com env: TOKEN: ${{ secrets.ACCESS_TOKEN }} run: | @@ -287,6 +309,6 @@ steps: ``` {% endraw %} -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} +### {% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}. -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." +Você pode exibir análise de código de uma ferramenta de terceiros em {% data variables.product.prodname_dotcom %}, adicionando a ação de `upload-sarif` ao seu fluxo de trabalho. Você pode fazer o upload de dados de análise de código com a ação `upload-sarif`. Para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF para o GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 907b1cd3d9..ce18e7150f 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -94,7 +94,7 @@ Se o comando `autobuild` não puder criar o seu código, você poderá executar Por padrão, o {% data variables.product.prodname_codeql_runner %} faz o upload dos resultados a partir de {% data variables.product.prodname_code_scanning %} quando você executa o comando de `análise`. Você também pode carregar arquivos do SARIF separadamente, usando o comando `upload`. -Depois de enviar os dados, o {% data variables.product.prodname_dotcom %} exibirá os alertas no seu repositório. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-an-alert)". +Depois de enviar os dados, o {% data variables.product.prodname_dotcom %} exibirá os alertas no seu repositório. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". ### Comando de referência de {% data variables.product.prodname_codeql_runner %} diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index ef76c6ead1..62eccbbbb5 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -3,7 +3,7 @@ title: Configurar o fluxo de trabalho do CodeQL para linguagens compiladas shortTitle: Configurar para linguagens compiladas intro: 'Você pode configurar como o {% data variables.product.prodname_dotcom %} usa o {% data variables.product.prodname_codeql_workflow %} para varrer o código escrito em linguagens compiladas para obter vulnerabilidades e erros.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.' +permissions: 'Caso tenha permissões de gravação em um repositório, você poderá configurar {% data variables.product.prodname_code_scanning %} para esse repositório.' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index d44cd2e445..39c41a2402 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -1,9 +1,9 @@ --- -title: Enabling code scanning for a repository -shortTitle: Enabling code scanning -intro: 'You can enable {% data variables.product.prodname_code_scanning %} for your project''s repository.' +title: Habilitar a varredura de código para um repositório +shortTitle: Habilitar a varredura de código +intro: 'Você pode habilitar o {% data variables.product.prodname_code_scanning %} para o repositório do seu projeto.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permissions to a repository, you can enable {% data variables.product.prodname_code_scanning %} for that repository.' +permissions: 'Caso tenha permissões de escrita em um repositório, você pode habilitar {% data variables.product.prodname_code_scanning %} para esse repositório.' redirect_from: - /github/managing-security-vulnerabilities/configuring-automated-code-scanning - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning @@ -15,103 +15,99 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### Options for enabling {% data variables.product.prodname_code_scanning %} +### Opções para habilitar {% data variables.product.prodname_code_scanning %} -You decide how you generate {% data variables.product.prodname_code_scanning %} alerts, and which tools you use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. For more information, see "[About {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)." +Você decide como gerar alertas do {% data variables.product.prodname_code_scanning %} e quais ferramentas você usa no nível de um repositório. O {% data variables.product.product_name %} fornece suporte totalmente integrado para a análise do {% data variables.product.prodname_codeql %} e também é compatível com ferramentas de análise usando ferramentas de terceiros. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)". {% data reusables.code-scanning.enabling-options %} -### Enabling {% data variables.product.prodname_code_scanning %} using actions +### Habilitar {% data variables.product.prodname_code_scanning %} usando ações -{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Usar ações para executar {% data variables.product.prodname_code_scanning %} levará minutos. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %}", click **Set up {% data variables.product.prodname_code_scanning %}**. - !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. - !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) -5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. +3. À direita de "{% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Em "Começar com {% data variables.product.prodname_code_scanning %}", clique em **Configurar este fluxo de trabalho** no {% data variables.product.prodname_codeql_workflow %} ou em um fluxo de trabalho de terceiros. ![Botão "Configurar este fluxo de trabalho" em "Começar com cabeçalho de {% data variables.product.prodname_code_scanning %}"](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) +5. Para personalizar como {% data variables.product.prodname_code_scanning %} faz a varredura do seu código, edite o fluxo de trabalho. - Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. + Geralmente, você pode fazer commit do {% data variables.product.prodname_codeql_workflow %} sem fazer nenhuma alteração nele. No entanto, muitos dos fluxos de trabalho de terceiros exigem uma configuração adicional. Portanto, leia os comentários no fluxo de trabalho antes de fazer o commit. - For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." -6. Use the **Start commit** drop-down, and type a commit message. - ![Start commit](/assets/images/help/repository/start-commit-commit-new-file.png) -7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request. - ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) -8. Click **Commit new file** or **Propose new file**. + Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." +6. Use o menu suspenso **Iniciar commit** e digite uma mensagem de commit. ![Iniciar commit](/assets/images/help/repository/start-commit-commit-new-file.png) +7. Escolha se você gostaria de fazer commit diretamente no branch-padrão ou criar um novo branch e iniciar um pull request. ![Escolher onde fazer commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. Clique em **Fazer commit do novo arquivo** ou **Propor novo arquivo**. -In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. +No {% data variables.product.prodname_codeql_workflow %} padrão, {% data variables.product.prodname_code_scanning %} está configurado para analisar o seu código cada vez que você fizer push de uma alteração no branch-padrão ou em qualquer branch protegido, ou criar um pull request contra o branch padrão. Como resultado, {% data variables.product.prodname_code_scanning %} vai começar agora. -### Viewing the logging output from {% data variables.product.prodname_code_scanning %} +### Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %} -After enabling {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. +Depois de habilitar o {% data variables.product.prodname_code_scanning %} para o seu repositório, você poderá inspecionar a saída das ações conforme forem executadas. {% data reusables.repositories.actions-tab %} - You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. + Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. - ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) + ![Lista de ações que mostram o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-actions-list.png) -1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. +1. Clique na entrada para o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. -1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. +1. Clique no nome do trabalho à esquerda. Por exemplo, **Analise (LANGUAGE)**. - ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + ![Saída do log do fluxo de trabalho de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-logging-analyze-action.png) -1. Review the logging output from the actions in this workflow as they run. +1. Revise a saída de log das ações deste fluxo de trabalho enquanto elas são executadas. -1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-an-alert)." +1. Depois que todos os trabalhos forem concluídos, você poderá visualizar os as informações dos alertas de {% data variables.product.prodname_code_scanning %} que foram identificados. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". {% note %} -**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. +**Observação:** Se você criou um pull request para adicionar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %} ao repositório, os alertas desse pull request não serão exibidos diretamente na página de {% data variables.product.prodname_code_scanning_capc %} até que o pull request seja mesclado. Se algum alerta for encontrado, você poderá visualizá-los, antes do merge do pull request, clicando no link dos **_n_ alertas encontrados** no banner na página de {% data variables.product.prodname_code_scanning_capc %}. - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Clique no link "n alertas encontrados"](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% endnote %} -### Understanding the pull request checks +### Entendendo as verificações de pull request -Each {% data variables.product.prodname_code_scanning %} workflow you enable to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. +Cada fluxo de trabalho de {% data variables.product.prodname_code_scanning %} que você habilitar para serem executados em pull requests sempre tem pelo menos duas entradas listadas na seção de verificações de um pull request. Há uma entrada para cada um dos trabalhos de análise no fluxo de trabalho e uma entrada final para os resultados da análise. -The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code. +Os nomes das verificações de análise de {% data variables.product.prodname_code_scanning %} assumem a forma: "TOOL NAME / JOB NAME (TRIGGER)." Por exemplo, para {% data variables.product.prodname_codeql %}, a análise do código C++ tem a entrada "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." Você pode clicar em **Detalhes** em uma entrada de análise de {% data variables.product.prodname_code_scanning %} para ver os dados de registro. Isso permite que você corrija um problema caso ocorra uma falha no trabalho de análise. Por exemplo, para a análise de {% data variables.product.prodname_code_scanning %} de linguagens compiladas, isto pode acontecer se a ação não puder criar o código. - ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) + ![Verificações de pull request de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +Quando os trabalhos de {% data variables.product.prodname_code_scanning %} forem concluídos, {% data variables.product.prodname_dotcom %} calcula se quaisquer alertas foram adicionados pelo pull request e adiciona a entrada "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" à lista de verificações. Depois de {% data variables.product.prodname_code_scanning %} ser executado pelo menos uma vez, você poderá clicar em **Detalhes** para visualizar os resultados da análise. Se você usou um pull request para adicionar {% data variables.product.prodname_code_scanning %} ao repositório, você verá inicialmente uma mensagem de "Análise ausente" ao clicar em **Detalhes** na verificação de resultados de "{% data variables.product.prodname_code_scanning_capc %} / NOME DA FERRAMENTA". - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) + ![Análise ausente para mensagem de commit](/assets/images/help/repository/code-scanning-missing-analysis.png) -#### Reasons for the "missing analysis" message +#### Motivos da mensagem "faltando ausente" -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Missing analysis for base commit SHA-HASH" message. +Depois que {% data variables.product.prodname_code_scanning %} analisou o código em um pull request, ele precisa comparar a análise do branch de tópico (o branch que você usou para criar o pull request) com a análise do branch de base (o branch no qual você deseja mesclar o pull request). Isso permite que {% data variables.product.prodname_code_scanning %} calcule quais alertas foram recém-introduzidos pelo pull request, que alertas já estavam presentes no branch de base e se alguns alertas existentes são corrigidos pelas alterações no pull request. Inicialmente, se você usar um pull request para adicionar {% data variables.product.prodname_code_scanning %} a um repositório, o branch de base ainda não foi analisado. Portanto, não é possível computar esses detalhes. Neste caso, ao clicar na verificação de resultados no pull request você verá a mensagem "Análise ausente para o commit de base SHA-HASH". -There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: +Há outras situações em que não pode haver análise para o último commit do branch de base para um pull request. Isso inclui: -* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed. +* O pull request foi levantado contra um branch diferente do branch padrão, e este branch não foi analisado. - To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. + Para verificar se um branch foi verificado, acesse a página {% data variables.product.prodname_code_scanning_capc %}, clique no menu suspenso **Branch** e selecione o branch relevante. - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Escolha um branch no menu suspenso Branch](/assets/images/help/repository/code-scanning-branch-dropdown.png) - The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. + A solução nesta situação é adicionar o nome do branch de base para a especificação `on:push` e `on:pull_request` no fluxo de trabalho de {% data variables.product.prodname_code_scanning %} nesse branch e, em seguida, fazer uma alteração que atualize o pull request aberto que você deseja escanear. -* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available. +* O último commit no branch de base para o pull request está atualmente sendo analisado e a análise ainda não está disponível. - Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. + Aguarde alguns minutos e depois faça push de uma alteração no pull request para acionar o recurso de {% data variables.product.prodname_code_scanning %}. -* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available. +* Ocorreu um erro ao analisar o último commit no branch base e a análise para esse commit não está disponível. - Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. + Faça merge uma mudança trivial no branch de base para acionar {% data variables.product.prodname_code_scanning %} neste commit mais recente e, em seguida, faça push de uma alteração para o pull request reiniciar {% data variables.product.prodname_code_scanning %}. -### Next steps +### Próximas etapas -After enabling {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: +Depois de habilitar a opção {% data variables.product.prodname_code_scanning %}, e permitir que suas ações sejam concluídas, você pode: -- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -- View any alerts generated for a pull request submitted after you enabled {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." -- Set up notifications for completed runs. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." -- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)." -- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." +- Visualizar todos os alertas de {% data variables.product.prodname_code_scanning %} gerados para este repositório. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". +- Visualizar todos os alertas gerados para um pull request enviado depois habilitar {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". +- Configurar notificações para execuções concluídas. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)". +- Investigue todos os problemas que ocorrerem com a configuração inicial de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Solucionar problemas no fluxo de trabalho de {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)". +- Personalize como {% data variables.product.prodname_code_scanning %} faz a varredura de código no seu repositório. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 876423b274..ba573e5bf4 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -1,9 +1,9 @@ --- title: Gerenciar alertas de verificação de código para o seu repositório shortTitle: Gerenciando alertas -intro: 'You can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.' +intro: 'Da vista da segurança, você pode visualizar, corrigir, {% if currentVersion == "enterprise-server@2. 2" %}ou fechar{% else %}ignorar ou excluir{% endif %} alertas de potenciais vulnerabilidades ou erros no código do seu projeto.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' +permissions: 'Se você tiver permissão de gravação em um repositório, você poderá gerenciar alertas de {% data variables.product.prodname_code_scanning %} para esse repositório.' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -30,9 +30,11 @@ Se você habilitar o {% data variables.product.prodname_code_scanning %} usando Quando {% data variables.product.prodname_code_scanning %} relata alertas de fluxo de dados, {% data variables.product.prodname_dotcom %} mostra como os dados se movem através do código. {% data variables.product.prodname_code_scanning_capc %} permite que você identifique as áreas do seu código que vazam informações confidenciais que poderia ser o ponto de entrada para ataques de usuários maliciosos. -### Visualizar um alerta +### Visualizar os alertas de um repositório -Qualquer pessoa com permissão de leitura para um repositório pode ver alertas de {% data variables.product.prodname_code_scanning %} em pull requests. No entanto, você precisa de permissão de gravação para ver um resumo de alertas de repositório na aba **Segurança**. Por padrão, os alertas são exibidos para o branch-padrão. +Qualquer pessoa com permissão de leitura para um repositório pode ver anotações de {% data variables.product.prodname_code_scanning %} em pull requests. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". + +Você precisa de permissão de gravação para visualizar um resumo de todos os alertas para um repositório na aba **Segurança**. Por padrão, os alertas são exibidos para o branch-padrão. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -45,7 +47,7 @@ Qualquer pessoa com permissão de leitura para um repositório pode ver alertas Qualquer pessoa com permissão de gravação para um repositório pode corrigir um alerta, fazendo o commit de uma correção do código. Se o repositório tiver {% data variables.product.prodname_code_scanning %} agendado para ser executado em pull requests, recomenda-se registrar um pull request com sua correção. Isso ativará a análise de {% data variables.product.prodname_code_scanning %} referente às alterações e irá testar se sua correção não apresenta nenhum problema novo. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" e " "[Testar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". -Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar um alerta](#viewing-an-alert). The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. +Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra os alertas corrigidos e aqueles que os usuários têm {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico. @@ -61,7 +63,7 @@ Fechar um alerta é uma maneira de resolver um alerta que você considera que n ### Ignorar ou excluir alertas -Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Alternatively, if you have admin permissions for the repository, you can delete alerts. Excluir alertas é útil em situações em que você habilitou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você habilitou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**. +Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Excluir alertas é útil em situações em que você habilitou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você habilitou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**. Ignorar um alerta é uma maneira de fechar um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Você pode ignorar alertas de anotações de {% data variables.product.prodname_code_scanning %} no código ou da lista de resumo dentro na aba **Segurança**. @@ -89,14 +91,14 @@ Para ignorar ou excluir alertas: {% data reusables.repositories.sidebar-code-scanning-alerts %} {% if currentVersion == "enterprise-server@2.22" %} {% data reusables.code-scanning.click-alert-in-list %} -1. Select the **Close** drop-down menu and click a reason for closing the alert. +1. Selecione o menu suspenso **Fechar** e clique em um motivo para fechar o alerta. ![Escolher o motivo para fechar o alerta no menu suspenso Fechar](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.false-positive-fix-codeql %} {% else %} -1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**. +1. Se você tem permissões de administrador para o repositório e deseja excluir alertas para esta ferramenta de {% data variables.product.prodname_code_scanning %}, selecione algumas ou todas as caixas de seleção e clique em **Excluir**. ![Excluir alertas](/assets/images/help/repository/code-scanning-delete-alerts.png) diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 30b3bdd81f..c30dbe8c30 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: Running CodeQL code scanning in your CI system -shortTitle: Running in your CI -intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.' +title: Executar varredura de código CodeQL no seu sistema de CI +shortTitle: Executar na sua CI +intro: 'Você pode usar {% data variables.product.prodname_codeql_runner %} para executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} em um sistema de integração contínua de terceiros.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system @@ -9,96 +9,98 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' --- + {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system +### Usar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} com o seu sistema CI existente -If you use a continuous integration or continuous delivery/deployment (CI/CD) system other than {% data variables.product.prodname_actions %}, you can use your existing system to run {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql %} analysis and upload the results to {% data variables.product.prodname_dotcom %}. To do this, use the {% data variables.product.prodname_codeql_runner %}. +Se você usar um sistema de integração contínua ou de entrega/implantação contínua (CI/CD) diferente de {% data variables.product.prodname_actions %}, você pode usar o seu sistema existente para executar a análise {% data variables.product.prodname_codeql %} de {% data variables.product.prodname_dotcom %} e enviar os resultados para {% data variables.product.prodname_dotcom %}. Para fazer isso, use {% data variables.product.prodname_codeql_runner %}. -### About the {% data variables.product.prodname_codeql_runner %} +### Sobre o {% data variables.product.prodname_codeql_runner %} -{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." +{% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning). -You can use the {% data variables.product.prodname_codeql_runner %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_location %}. For information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +Você pode usar {% data variables.product.prodname_codeql_runner %} para executar o {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua (CI) de terceiros. Como alternativa, você pode usar {% data variables.product.prodname_actions %} para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}. Para obter informações, consulte "[Habilitar {% data variables.product.prodname_code_scanning %} para um repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)". -The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. +O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que executa a análise de {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Você adiciona o executor ao seu sistema de terceiros e, em seguida, chama o executor para analisar o código e fazer o upload dos resultados para o {% data variables.product.product_location %}. Estes resultados são exibidos como alertas do {% data variables.product.prodname_code_scanning %} no repositório. {% data reusables.code-scanning.codeql-runner-license %} -### Downloading the {% data variables.product.prodname_codeql_runner %} +### Fazer o download do {% data variables.product.prodname_codeql_runner %} -You can download the {% data variables.product.prodname_codeql_runner %} from https://github.com/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it. +Você pode fazer o download do {% data variables.product.prodname_codeql_runner %} em https://github.com/github/codeql-action/releases. Em alguns sistemas operacionais, talvez você precise alterar as permissões para o arquivo baixado antes de executá-lo. -On Linux: +No Linux: ```shell chmod +x codeql-runner-linux ``` -On MacOS: +No MacOS: ```shell chmod +x codeql-runner-macos sudo xattr -d com.apple.quarantine codeql-runner-macos ``` -On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions. +No Windows, o arquivo `codeql-runner-win.exe` normalmente não exige alteração de permissões. -### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system +### Adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de CI -Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example: +Após concluído o download do {% data variables.product.prodname_codeql_runner %} e verificado que pode ser executado, você deve disponibilizar o executor para cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %}. É importante notar que cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %} deve ter o {% data variables.product.prodname_codeql_runner %}. Você pode configurar cada servidor para copiar o executor a partir de um local central interno ou você pode usar a API REST para obter o executor direto do GitHub, por exemplo: ```shell wget https://github.com/github/codeql-action/releases/download/codeql-bundle-20200826/codeql-runner-linux chmod +x codeql-runner-linux ``` -In addition to this, each CI server also needs: +Além disso, cada servidor de CI também precisa: -- A {% data variables.product.prodname_github_apps %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. For private repositories the token must have the `repo` scope. For public the token needs only the `public_repo` and `repo:security_events` scopes. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains the {% data variables.product.prodname_codeql %} CLI, queries, and libraries needed for {% data variables.product.prodname_codeql %} analysis. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." +- Um {% data variables.product.prodname_github_apps %} ou um token de acesso pessoal para {% data variables.product.prodname_codeql_runner %} usar. Para repositórios privados, o token deve ter o escopo do `repositório`. Para público, o token precisa apenas dos escopos `public_repo` e `repo:security_events`. Para obter informações, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +- Acesso ao pacote de {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.product.prodname_codeql_runner %}. Este pacote contém CLI de {% data variables.product.prodname_codeql %}, consultas e bibliotecas necessárias para a análise de {% data variables.product.prodname_codeql %}. Para obter informações, consulte "[CLI de {% data variables.product.prodname_codeql %}](https://help.semmle.com/codeql/codeql-cli.html)". -The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: +As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são: -1. Allow the CI servers access to {% data variables.product.prodname_dotcom_the_website %} so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically. -1. Manually download/extract the bundle, store it with other central resources, and use the `--codeql-path` flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}. +1. Permitir o acesso dos servidores de CI ao {% data variables.product.prodname_dotcom_the_website %} para que o {% data variables.product.prodname_codeql_runner %} possa fazer o download do pacote automaticamente. +1. Fazer o download/extrair manualmente o pacote, armazená-lo com outros recursos centrais e usar o sinalizador `--codeql-path` para especificar a localização do pacote nas chamadas para inicializar o +{% data variables.product.prodname_codeql_runner %}. {% if enterpriseServerVersions contains currentVersion %} -1. You can mirror the `github/codeql-action` repository on {% data variables.product.product_location %}. Unless you specify the `--codeql-path` flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} +1. Você pode espelhar o repositório `github/codeql-action` no {% data variables.product.product_location %}. A menos que você especifique o sinalizador `--codeql-path` , o executor verifica automaticamente o pacote neste local e no {% data variables.product.prodname_dotcom_the_website %}.{% endif %} -### Calling the {% data variables.product.prodname_codeql_runner %} +### Chamar {% data variables.product.prodname_codeql_runner %} -You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are: +Você deve chamar {% data variables.product.prodname_codeql_runner %} no local de checkout do repositório que deseja analisar. Os dois comandos principais são: -1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands. -1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_location %}. +1. `init` necessário para inicializar o executor e criar um banco de dados de {% data variables.product.prodname_codeql %} para que cada linguagem seja analisada. Estas bases de dados são preenchidas e analisadas por comandos subsequentes. +1. `análise` necessário para preencher os bancos de dados {% data variables.product.prodname_codeql %}, analisá-los e fazer o upload dos resultados para {% data variables.product.product_location %}. -For both commands, you must specify the URL of {% data variables.product.product_location %}, the repository *OWNER/NAME*, and the GitHub Apps or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle unless the CI server has access to download it directly from the `github/codeql-action` repository on {% data variables.product.prodname_dotcom_the_website %}{% if enterpriseServerVersions contains currentVersion %} or mirrored on {% data variables.product.product_location %}{% endif %}. +Para ambos os comandos, você deve especificar a URL de {% data variables.product.product_location %}, o repositório *OWNER/NAME* e os aplicativos GitHub ou o token de acesso pessoal para usar na autenticação. Você também precisa especificar a localização do pacote do CodeQL, a menos que o servidor de CI tenha acesso para baixá-lo diretamente do repositório `github/codeql-action` em {% data variables.product.prodname_dotcom_the_website %}{% if enterpriseServerVersions contains currentVersion %} ou espelhado em {% data variables.product.product_location %}{% endif %}. -You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the `--tools-dir` flag and where it stores temporary files during analysis using `--temp-dir`. +Você pode configurar o local onde o {% data variables.product.prodname_codeql_runner %} armazena o pacote do CodeQL para futuras análises em um servidor usando o sinalizador `--tools-dir` e onde armazena arquivos temporários durante a análise usando `--temp-dir`. -To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)." +Para visualizar a referência de linha de comando para o executor, use o sinalizador `-h`. Por exemplo, para listar todos os comandos executados: `codeql-runner-OS -h` ou para listar todos os sinalizadores disponíveis para o comando `init` executado: `codeql-runner-OS init -h` (em que `OS` varia de acordo com o executável que você está usando). Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)". -#### Basic example +#### Exemplo básico -This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). +Este exemplo executa a análise do {% data variables.product.prodname_codeql %} em um servidor de Linux CI para o repositório `octo-org/example-repo` hospedado em `{% data variables.command_line.git_url_example %}`. O processo é muito simples porque o repositório contém apenas linguagens que podem ser analisadas diretamente pelo {% data variables.product.prodname_codeql %}, sem ser criado (ou seja, Go, JavaScript, Python e TypeScript). -1. Check out the repository to analyze. -1. Move into the directory where the repository is checked out. -1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. +1. Confira o repositório a ser analisado. +1. Mova para o diretório para o local onde o repositório está reservado. +1. Inicialize {% data variables.product.prodname_codeql_runner %} e crie banco de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas. ```shell $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN > Cleaning temp directory /srv/checkout/example-repo/codeql-runner > ... - > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript. + > Banco de dados do CodeQL criado em /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript. ``` -1. Populate the {% data variables.product.prodname_codeql_runner %} databases, analyze them, and upload the results to {% data variables.product.product_name %}. +1. Preencha os bancos de dados de {% data variables.product.prodname_codeql_runner %}, analise-os e faça o upload dos resultados para {% data variables.product.product_name %}. ```shell $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo @@ -110,15 +112,15 @@ This example runs {% data variables.product.prodname_codeql %} analysis on a Lin > Successfully uploaded results ``` -The server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository on {% data variables.product.prodname_dotcom_the_website %}{% if enterpriseServerVersions contains currentVersion %} or mirrored on {% data variables.product.product_location %}{% endif %}, so there is no need to use the `--codeql-path` flag. When the analysis is complete, the {% data variables.product.prodname_codeql_runner %} uploads the results to the {% data variables.product.prodname_code_scanning %} view. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." +O servidor tem acesso para fazer o download do pacote de {% data variables.product.prodname_codeql %} diretamente do repositório `github/codeql-action` no {% data variables.product.prodname_dotcom_the_website %}{% if enterpriseServerVersions contains currentVersion %} ou espelhado no {% data variables.product.product_location %}{% endif %}. Portanto, não há necessidade de usar o sinalizador `--codeql-path`. Quando a análise for concluída, o {% data variables.product.prodname_codeql_runner %} faz o upload dos resultados para a visualização de {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". -#### Compiled language example +#### Exemplo de linguagem compilada -This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command. +Este exemplo é semelhante ao exemplo anterior. No entanto, desta vez, o repositório tem o código em C/C++, C# ou Java. Para criar um banco de dados de {% data variables.product.prodname_codeql %} para essas linguagens, o CLI precisa monitorar a criação. No final do processo de inicialização, o executor informa o comando que você precisa configurar o ambiente antes de criar o código. Você precisa executar esse comando antes de chamar o processo de criação normal da CI e, em seguida, executar o comando `analisar`. -1. Check out the repository to analyze. -1. Move into the directory where the repository is checked out. -1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. +1. Confira o repositório a ser analisado. +1. Mova para o diretório para o local onde o repositório está reservado. +1. Inicialize {% data variables.product.prodname_codeql_runner %} e crie banco de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas. ```shell $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 @@ -127,18 +129,18 @@ This example is similar to the previous example, however this time the repositor > ... > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json" and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". - Please export these variables to future processes so the build can be traced, for example by running " + Exporte essas variáveis para processos futuros para que a criação possa ser rastreada, por exemplo, executando " . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". ``` -1. Run the script generated by the `init` action to set up the environment to monitor the build. +1. Execute o script gerado pela ação `init` para configurar o ambiente para monitorar a criação. ```shell $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh ``` -1. Build the code. -1. Populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload the results to GitHub. +1. Crie o código. +1. Preencha os bancos de dados de {% data variables.product.prodname_codeql %}, analise-os e faça o upload dos resultados para o GitHub. ```shell $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo-2 @@ -152,11 +154,11 @@ This example is similar to the previous example, however this time the repositor {% note %} -**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place. +**Observação:** Se você usar uma criação conteinerizada, você deverá executar o {% data variables.product.prodname_codeql_runner %} no contêiner em que ocorre a tarefa de criação. {% endnote %} -### Further reading +### Leia mais -- "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)" -- "[Troubleshooting {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system)" +- "[Configurar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)" +- "[Solução de problemas de {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system)" diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index b51fe36706..ab553d6878 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -3,7 +3,7 @@ title: Alertas de varredura de código de triagem em pull requests shortTitle: Alertas de triagem em pull requests intro: 'Quando {% data variables.product.prodname_code_scanning %} identifica um problema em um pull request, você poderá revisar o código destacado e resolver o alerta.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permission to a repository, you can resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.' +permissions: 'Se você tiver permissão de leitura em um repositório, você poderá ver anotações em pull requests. Com permissão de gravação, você poderá ver informações detalhadas e resolver alertas de {% data variables.product.prodname_code_scanning %} para esse repositório.' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -13,9 +13,9 @@ versions: ### Sobre os resultados de {% data variables.product.prodname_code_scanning %} em pull requests -Em repositórios onde {% data variables.product.prodname_code_scanning %} está configurado como uma verificação de pull request, {% data variables.product.prodname_code_scanning %} verifica o código no pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. Se o merge das alterações introduziria novos alertas de {% data variables.product.prodname_code_scanning %} no branch de destino, estes serão relatados como resultados de verificação no pull request. Os alertas também são exibidos como anotações na aba **Arquivos alterados** do pull request. Se você tiver permissão de gravação no repositório, você poderá ver qualquer alerta de {% data variables.product.prodname_code_scanning %} existente na aba **Segurança**. Para obter informações sobre os alertas do repositório, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} do repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". +Em repositórios onde {% data variables.product.prodname_code_scanning %} está configurado como uma verificação de pull request, {% data variables.product.prodname_code_scanning %} verifica o código no pull request. Por padrão, isso é limitado a pull requests que visam o branch-padrão ou branches protegidos, mas você pode alterar esta configuração em {% data variables.product.prodname_actions %} ou em um sistema de CI/CD de terceiros. Se o merge das alterações introduziria novos alertas de {% data variables.product.prodname_code_scanning %} no branch de destino, estes serão relatados como resultados de verificação no pull request. Os alertas também são exibidos como anotações na aba **Arquivos alterados** do pull request. Se você tiver permissão de gravação no repositório, você poderá ver qualquer alerta de {% data variables.product.prodname_code_scanning %} existente na aba **Segurança**. Para obter informações sobre os alertas do repositório, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} do repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". -Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. If your pull request targets a protected branch that has been enabled for {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Para obter mais informações, consulte "[Sobre verificações de status obrigatórias](/github/administering-a-repository/about-required-status-checks)". +Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request tem como alvo um branch protegido que foi habilitado por {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório configurou as verificações de status obrigatórias, você deverá corrigir ou {% if currentVersion == "enterprise-server@2. 2" %}fechar{% else %}dismiss{% endif %} todos os erros alertas antes que o pull request possa ser mesclado. Para obter mais informações, consulte "[Sobre verificações de status obrigatórias](/github/administering-a-repository/about-required-status-checks)". ![Ocorreu uma falha na verificação de {% data variables.product.prodname_code_scanning %} em um pull request](/assets/images/help/repository/code-scanning-check-failure.png) @@ -31,21 +31,21 @@ Quando você olha para a aba **Arquivos alterados** para um pull request, você ![Alerta de anotação em um diff de pull request](/assets/images/help/repository/code-scanning-pr-annotation.png) -Algumas anotações contêm links com contexto extra para o alerta. No exemplo acima, da análise de {% data variables.product.prodname_codeql %}, você pode clicar em **valor fornecido pelo usuário** para ver onde os dados não confiáveis entram no fluxo de dados (isso é referido como a fonte). Neste caso, você pode visualizar o caminho completo da fonte até o código que usa os dados (o destino), clicando em **Mostrar caminhos**. Isto faz com que seja fácil verificar se os dados não são confiáveis ou se a análise não reconheceu uma etapa de sanitização de dados entre a fonte e o destino. Para obter informações sobre a análise do fluxo de dados usando {% data variables.product.prodname_codeql %}, consulte "[Sobre a análise do fluxo de dados](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)". +Se você tiver permissão de gravação para o repositório, algumas anotações conterão links com contexto adicional para o alerta. No exemplo acima, da análise de {% data variables.product.prodname_codeql %}, você pode clicar em **valor fornecido pelo usuário** para ver onde os dados não confiáveis entram no fluxo de dados (isso é referido como a fonte). Neste caso, você também pode ver o caminho completo desde a fonte até o código que usa os dados (o sumidouro), clicando em **Mostrar caminhos**. Isto faz com que seja fácil verificar se os dados não são confiáveis ou se a análise não reconheceu uma etapa de sanitização de dados entre a fonte e o destino. Para obter informações sobre a análise do fluxo de dados usando {% data variables.product.prodname_codeql %}, consulte "[Sobre a análise do fluxo de dados](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)". -Para obter mais informações sobre um alerta, clique em **Mostrar mais informações** na anotação. Isso permite que você veja todos os contextos e metadados fornecidos pela ferramenta em uma exibição de alerta. No exemplo abaixo, você pode ver tags que mostram a gravidade, o tipo e as enumerações de fraquezas comuns relevantes (CWEs) para o problema. A vista mostra também quais commits introduziram o problema. +Para ver mais informações sobre um alerta, os usuários com permissão de gravação podem clicar no link **Mostrar mais detalhes**, exibido na anotação. Isso permite que você veja todos os contextos e metadados fornecidos pela ferramenta em uma exibição de alerta. No exemplo abaixo, você pode ver tags que mostram a gravidade, o tipo e as enumerações de fraquezas comuns relevantes (CWEs) para o problema. A vista mostra também quais commits introduziram o problema. Na visualização detalhada de um alerta, algumas ferramentas de {% data variables.product.prodname_code_scanning %}, como a análise de {% data variables.product.prodname_codeql %} também incluem uma descrição do problema e um link **Mostrar mais** para obter orientações sobre como corrigir seu código. ![Descrição do alerta e link para mostrar mais informações](/assets/images/help/repository/code-scanning-pr-alert.png) -### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request +### {% if currentVersion == "enterprise-server@2.22" %}Resolvendo{% else %}Corrigindo{% endif %} um alerta no seu pull request -Qualquer pessoa com permissão de gravação em um repositório pode corrigir um alerta de {% data variables.product.prodname_code_scanning %} identificado em um pull request. Se você fizer commit de alterações na solicitação do pull request, isto acionará uma nova execução das verificações do pull request. Se suas alterações corrigirem o problema, o alerta será fechado e a anotação removida. +Qualquer pessoa com acesso push a um pull request pode corrigir um alerta de {% data variables.product.prodname_code_scanning %} que seja identificado nesse pull request. Se você fizer commit de alterações na solicitação do pull request, isto acionará uma nova execução das verificações do pull request. Se suas alterações corrigirem o problema, o alerta será fechado e a anotação removida. {% if currentVersion == "enterprise-server@2.22" %} -Se você não considerar que um alerta deve ser corrigido, você poderá fechar o alerta manualmente. {% data reusables.code-scanning.close-alert-examples %} O botão **Fechar** está disponível nas anotações e no modo de exibição de alertas se você tiver permissão de gravação no repositório. +Se você não considera que um alerta deve ser corrigido, os usuários com permissão de gravação podem fechar o alerta manualmente. {% data reusables.code-scanning.close-alert-examples %} O botão **Fechar** está disponível nas anotações e no modo de exibição de alertas se você tiver permissão de gravação no repositório. {% data reusables.code-scanning.false-positive-fix-codeql %} @@ -63,4 +63,4 @@ Uma forma alternativa de fechar um alerta é ignorá-lo. Você pode descartar um Para obter mais informações sobre alertas ignorados, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)". -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index 3ddc1056fa..0b9026a06a 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -64,7 +64,7 @@ Para obter mais informações, consulte a extração de fluxo de trabalho em "[C * Criar usando um sistema de compilação distribuído externo às Ações GitHub, usando um processo de daemon. * {% data variables.product.prodname_codeql %} não está ciente do compilador específico que você está usando. - Para projetos de C# usando `dotnet build` ou `msbuild` qual abordam .NET Core 2, você deverá especificar `/p:UseSharedCompilation=false` na sua etapa de `execução` do fluxo de trabalho ao criar o seu código. O sinalizador `UseSharedCompilation` não é necessário para o .NET Core 3.0 ou versão superior. + Para projetos de .NET Framework, e para projetos de C# que usam `dotnet build` ou `msbuild` que miram .NET Core 2, você deve especificar `/p:UseSharedCompilation=false` na etapa de `executar` do seu fluxo de trabalho quando você construir seu código. O sinalizador `UseSharedCompilation` não é necessário para o .NET Core 3.0 ou versão superior. Por exemplo, a seguinte configuração para C# irá passar o sinalizador durante a primeira etapa de criação. diff --git a/translations/pt-BR/content/github/getting-started-with-github/access-permissions-on-github.md b/translations/pt-BR/content/github/getting-started-with-github/access-permissions-on-github.md index 02df049430..76fba71719 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/access-permissions-on-github.md +++ b/translations/pt-BR/content/github/getting-started-with-github/access-permissions-on-github.md @@ -28,7 +28,7 @@ Os integrantes da organização podem ter funções de *proprietário*{% if curr ### Contas corporativas -Os *proprietários de empresa* têm poder absoluto sobre a conta corporativa e podem realizar todas as ações nela. Os *gerentes de cobrança* podem gerenciar as configurações de cobrança da sua conta corporativa. Os integrantes e colaboradores externos das organizações pertencentes à sua conta corporativa são automaticamente integrantes da conta corporativa, embora eles não tenham acesso à conta corporativa em si nem às configurações dela. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +Os *proprietários de empresa* têm poder absoluto sobre a conta corporativa e podem realizar todas as ações nela. Os *gerentes de cobrança* podem gerenciar as configurações de cobrança da sua conta corporativa. Os integrantes e colaboradores externos das organizações pertencentes à sua conta corporativa são automaticamente integrantes da conta corporativa, embora eles não tenham acesso à conta corporativa em si nem às configurações dela. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". {% data reusables.gated-features.enterprise-accounts %} diff --git a/translations/pt-BR/content/github/getting-started-with-github/be-social.md b/translations/pt-BR/content/github/getting-started-with-github/be-social.md index 4ba6040e83..5ee6398965 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/be-social.md +++ b/translations/pt-BR/content/github/getting-started-with-github/be-social.md @@ -22,7 +22,7 @@ Clique em **Follow** (Seguir) na página do perfil de uma pessoa para segui-la. ### Inspecionar um repositório -Você pode inspecionar um repositório para receber notificações de novos problemas e pull requests. Quando o proprietário atualiza o repositório, você vê as alterações no seu painel pessoal. For more information see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}." +Você pode inspecionar um repositório para receber notificações de novos problemas e pull requests. Quando o proprietário atualiza o repositório, você vê as alterações no seu painel pessoal. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Visualizar suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Inspecionar e não inspecionar repositórios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}." Clique em **Watch** (Inspecionar) no topo de um repositório para inspecioná-lo. diff --git a/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md b/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md index 3678ac375c..c5ec080b0f 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md +++ b/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md @@ -10,14 +10,26 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" %} + Você pode armazenar vários projetos nos repositórios do {% data variables.product.product_name %}, incluindo projetos de código aberto. Com os [projetos de código aberto](http://opensource.org/about), é possível compartilhar código para criar softwares melhores e mais confiáveis. +{% elsif enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + +You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + {% note %} **Observação:** você pode criar repositórios públicos para um projeto de código aberto. Ao criar um repositório público, certifique-se de incluir um [arquivo de licença](http://choosealicense.com/) que determina como deseja que seu projeto seja compartilhado com outras pessoas. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} {% endnote %} +{% endif %} + {% data reusables.repositories.create_new %} 2. Digite um nome curto e fácil de memorizar para seu repositório. Por exemplo, "olá mundo". ![Campo para inserir um nome de repositório](/assets/images/help/repository/create-repository-name.png) 3. Se desejar, adicione uma descrição do repositório. Por exemplo, "Meu primeiro repositório no diff --git a/translations/pt-BR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md b/translations/pt-BR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md index 25eff360ee..9898486782 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md +++ b/translations/pt-BR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md @@ -21,5 +21,5 @@ Os produtos e recursos do {% data variables.product.product_name %} podem passar Você pode ver uma lista de recursos disponíveis na versão beta e uma breve descrição de cada um deles. Cada recurso inclui um link para dar feedback. -1. No canto superior direito de qualquer página, clique na sua foto do perfil e depois em **Feature preview** (Visualização de recursos). ![Botão Feature preview (Visualização de recursos)](/assets/images/help/settings/feature-preview-button.png) +{% data reusables.feature-preview.feature-preview-setting %} 2. Outra opção é clicar em **Enable** (Habilitar) ou **Disable** (Desabilitar) à direita de um recurso. ![Botão Enable (Habilitar) na visualização de recursos](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/pt-BR/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/pt-BR/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md index 6b6b7b6062..ca95887da7 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/pt-BR/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -32,7 +32,7 @@ Alguns projetos de código aberto oferecem espelhos em {% data variables.product Seguem aqui alguns repositórios de destaque espelhados em {% data variables.product.prodname_dotcom_the_website %}: -- [Android Open Source Project](https://github.com/aosp-mirror) +- [Projeto Open Source Android](https://github.com/aosp-mirror) - [The Apache Software Foundation](https://github.com/apache) - [The Chromium Project](https://github.com/chromium) - [Eclipse Foundation](https://github.com/eclipse) diff --git a/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md b/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md index 76d5051565..6005c371c7 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md +++ b/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md @@ -25,10 +25,16 @@ Por exemplo, você pode usar bifurcações para propor alterações relacionadas O software de código aberto baseia-se na ideia de que ao compartilhar códigos, podemos criar softwares melhores e mais confiáveis. Para obter mais informações, consulte "[Sobre a Iniciativa Open Source](http://opensource.org/about)" em Iniciativa Open Source. +For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + Ao criar um repositório público a partir de uma bifurcação do projeto de outra pessoa, confirme que incluiu um arquivo de licença que estabelece como você quer que seu projeto seja compartilhado com outros. Para obter mais informações, consulte [Escolha uma licença de código aberto](http://choosealicense.com/)" em choosealicense. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} +{% endif %} + {% note %} **Observação**: {% data reusables.repositories.desktop-fork %} diff --git a/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md b/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md index 4bd1e7e9de..f8e64d3dc5 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md @@ -43,9 +43,9 @@ Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data va ### Compartilhando feedback -If you find a bug in {% data variables.product.prodname_mobile %}, you can email us at mobilefeedback@github.com. +Se você encontrar um erro em {% data variables.product.prodname_mobile %}, você pode nos enviar um e-mail para mobilefeedback@github.com. -You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} [on GitHub Discussions](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). +Você pode enviar solicitações de recursos ou outros comentários para {% data variables.product.prodname_mobile %} [nas discussões do GitHub](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). ### Desativando versões beta para iOS diff --git a/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md index fd5d1481e5..b615238f22 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -21,22 +21,22 @@ Veja abaixo uma lista dos atalhos de teclado disponíveis. ### Atalhos para o site -| Atalho | Descrição | -| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s or / | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/articles/about-searching-on-github)". | -| g n | Vai para suas notificações. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." | -| esc | Quando direcionado a um hovercard de usuário, problema ou pull request, fecha o hovercard e redireciona para o elemento no qual o hovercard está | +| Atalho | Descrição | +| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| s or / | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/articles/about-searching-on-github)". | +| g n | Vai para suas notificações. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." | +| esc | Quando direcionado a um hovercard de usuário, problema ou pull request, fecha o hovercard e redireciona para o elemento no qual o hovercard está | ### Repositórios -| Atalho | Descrição | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | Vai para a aba **Code** (Código) | -| g i | Vai para a aba **Issues** (Problemas). Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues)". | -| g p | Vai para a aba **Pull requests**. For more information, see "[About pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| Atalho | Descrição | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| g c | Vai para a aba **Code** (Código) | +| g i | Vai para a aba **Issues** (Problemas). Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues)". | +| g p | Vai para a aba **Pull requests**. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} | g a | Acesse a aba de **Ações**. Para obter mais informações, consulte "[Sobre ações](/actions/getting-started-with-github-actions/about-github-actions)".{% endif %} -| g b | Vai para a aba **Projects** (Projetos). Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". | -| g w | Vai para a aba **Wiki**. Para obter mais informações, consulte "[Sobre wikis](/articles/about-wikis)". | +| g b | Vai para a aba **Projects** (Projetos). Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". | +| g w | Vai para a aba **Wiki**. Para obter mais informações, consulte "[Sobre wikis](/articles/about-wikis)". | ### Edição de código-fonte @@ -110,7 +110,7 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod | j | Move a seleção para baixo na lista | | k | Move a seleção para cima na lista | | cmd + shift + enter | Adiciona um comentário único no diff da pull request | -| alt e clique | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| alt e clique | Alterna entre recolhimento e expansão de todos os comentários de revisão desatualizados em um pull request, mantendo pressionada a tecla `alt` e clicando em **Mostrar desatualizados** ou **Ocultar desatualizados**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | Clique, em seguida shift e clique | Comente em várias linhas de uma pull request clicando em um número de linha, mantendo pressionado shift, depois clique em outro número de linha. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} ### Quadros de projeto diff --git a/translations/pt-BR/content/github/getting-started-with-github/saving-repositories-with-stars.md b/translations/pt-BR/content/github/getting-started-with-github/saving-repositories-with-stars.md index 74264a4930..447f1f01a8 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/saving-repositories-with-stars.md +++ b/translations/pt-BR/content/github/getting-started-with-github/saving-repositories-with-stars.md @@ -1,6 +1,6 @@ --- title: Salvar repositórios com estrelas -intro: 'You can star repositories and topics to keep track of projects you find interesting{% if currentVersion == "free-pro-team@latest" %} and discover related content in your news feed{% endif %}.' +intro: 'Você pode favoritar repositórios e tópicos para acompanhar projetos que você considera interessantes{% if currentVersion == "free-pro-team@latest" %} e descobrir conteúdo relacionado no seu feed de notícias{% endif %}.' redirect_from: - /articles/stars/ - /articles/about-stars/ diff --git a/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md b/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md index fb2221f15e..432693b58b 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md +++ b/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md @@ -17,7 +17,7 @@ versions: github-ae: '*' --- -Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. Para obter mais informações sobre {% data variables.product.prodname_cli %}, consulte a documentação de [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) .{% endif %} +Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} Você também pode instalar {% data variables.product.prodname_cli %} para usar {% data variables.product.product_name %} na linha de comando. Para obter mais informações sobre {% data variables.product.prodname_cli %}, consulte a documentação de [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) .{% endif %} Se quiser trabalhar com o Git, mas não quiser usar a linha de comando, você poderá baixar e instalar o cliente do [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}). Para obter mais informações, consulte "[Instalar e configurar o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". diff --git a/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md index 5f77beef3f..3b3b625750 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md @@ -36,7 +36,7 @@ Siga estas etapas para aproveitar ao máximo a versão de avaliação: - Webcast [Guia de início rápido do {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) - [Entender o fluxo do {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow/) nos guias do {% data variables.product.prodname_dotcom %} - [Hello World](https://guides.github.com/activities/hello-world/) nos guias do {% data variables.product.prodname_dotcom %} -3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." +3. Para configurar a sua instância para atender as necessidades da sua organização, consulte "[Configurar sua empresa](/enterprise/admin/configuration/configuring-your-enterprise)". 4. Para integrar o {% data variables.product.prodname_ghe_server %} ao seu provedor de identidade, consulte "[Usar SAML](/enterprise/admin/user-management/using-saml)" e "[Usar LDAP](/enterprise/admin/authentication/using-ldap)". 5. Convite o número desejado de pessoas (sem limite) para fazer parte da versão de avaliação. - Adicione os usuários à sua instância do {% data variables.product.prodname_ghe_server %} usando autenticação integrada ou seu provedor de identidade configurado. Para obter mais informações, consulte "[Usar autenticação integrada](/enterprise/admin/user-management/using-built-in-authentication)". diff --git a/translations/pt-BR/content/github/index.md b/translations/pt-BR/content/github/index.md index 768349e16a..038d3fea24 100644 --- a/translations/pt-BR/content/github/index.md +++ b/translations/pt-BR/content/github/index.md @@ -20,24 +20,14 @@ versions: {% link_in_list /authenticating-to-github %} - {% link_in_list /managing-subscriptions-and-notifications-on-github %} - - {% link_in_list /receiving-notifications-about-activity-on-github %} - {% link_in_list /setting-up-and-managing-organizations-and-teams %} - - {% link_in_list /setting-up-and-managing-your-enterprise %} - - - {% link_in_list /setting-up-and-managing-billing-and-payments-on-github %} - {% link_in_list /writing-on-github %} @@ -50,10 +40,7 @@ versions: {% link_in_list /collaborating-with-issues-and-pull-requests %} {% link_in_list /managing-your-work-on-github %} - - {% link_in_list /developing-online-with-codespaces %} - {% link_in_list /building-a-strong-community %} @@ -64,45 +51,21 @@ versions: {% link_in_list /administering-a-repository %} {% link_in_list /visualizing-repository-data-with-graphs %} - - {% link_in_list /managing-security-vulnerabilities %} - {% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} {% link_in_list /managing-files-in-a-repository %} {% link_in_list /managing-large-files %} - - {% link_in_list /customizing-your-github-workflow %} - {% link_in_list /extending-github %} {% link_in_list /working-with-github-pages %} - - {% link_in_list /supporting-the-open-source-community-with-github-sponsors %} - - - {% link_in_list /teaching-and-learning-with-github-education %} - - - {% link_in_list /finding-talent-with-github-jobs %} - - - {% link_in_list /working-with-github-support %} - - - {% link_in_list /understanding-how-github-uses-and-protects-your-data %} - - - {% link_in_list /site-policy %} - diff --git a/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md b/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md index f803ba426f..d0e00cc297 100644 --- a/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md +++ b/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md @@ -17,4 +17,4 @@ Se você tentar adicionar ou atualizar um arquivo maior do que {% data variables ### Pushes bloqueados para arquivos grandes -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. Para obter mais informações, consulte "[Definir limites de push do Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %} +{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}Por padrão, {% endif %}{% data variables.product.product_name %} bloqueia pushes que excedem {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}No entanto, um administrador do site pode configurar um limite diferente para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Definir limites de push do Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %} diff --git a/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md index 2d663bba88..f97112a867 100644 --- a/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -18,7 +18,7 @@ Se houver arquivos no seu repositório com os quais deseja usar o {% data variab {% tip %} -**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. Para obter mais informações, consulte "[Configurar o Git Large File Storage no GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)". +**Observação:** antes de tentar fazer push de um arquivo grande no {% data variables.product.product_name %}, certifique-se de que habilitou o {% data variables.large_files.product_name_short %} no seu aplicativo. Para obter mais informações, consulte "[Configurar o Git Large File Storage no GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)". {% endtip %} @@ -59,5 +59,5 @@ Se houver arquivos no seu repositório com os quais deseja usar o {% data variab ### Leia mais -- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- "[Colaboração com {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} - "[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md index c90bdd36df..6c6aacf77b 100644 --- a/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md +++ b/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md @@ -1,6 +1,6 @@ --- -title: Removing files from Git Large File Storage -intro: 'If you''ve set up {% data variables.large_files.product_name_short %} for your repository, you can remove all files or a subset of files from {% data variables.large_files.product_name_short %}.' +title: Remover arquivos do Git Large File Storage +intro: 'Se o {% data variables.large_files.product_name_short %} estiver configurado no repositório, você poderá remover todos os arquivos ou um subconjunto de arquivos do {% data variables.large_files.product_name_short %}.' redirect_from: - /articles/removing-files-from-git-large-file-storage versions: @@ -9,45 +9,45 @@ versions: github-ae: '*' --- -### Removing a single file +### Remover um único arquivo -1. Remove the file from the repository's Git history using either the `filter-branch` command or BFG Repo-Cleaner. For detailed information on using these, see "[Removing sensitive data from a repository](/articles/removing-sensitive-data-from-a-repository)." -2. Navigate to your *.gitattributes* file. +1. Remova o arquivo do histórico do repositório do Git usando o comando `filter-branch` ou o BFG Repo Cleaner. Para obter mais informações, consulte "[Remover dados confidenciais do repositório](/articles/removing-sensitive-data-from-a-repository)". +2. Acesse o arquivo *.gitattributes* . {% note %} - **Note:** Your *.gitattributes* file is generally saved within your local repository. In some cases, you may have created a global *.gitattributes* file that contains all of your {% data variables.large_files.product_name_short %} associations. + **Observação:** o arquivo *.gitattributes* geralmente é salvo no repositório local. Em alguns casos, você pode ter criado um arquivo *.gitattributes* glocal que contém todas as associações do {% data variables.large_files.product_name_short %}. {% endnote %} -3. Find and remove the associated {% data variables.large_files.product_name_short %} tracking rule within the *.gitattributes* file. -4. Save and exit the *.gitattributes* file. +3. Encontre e remova a regra de acompanhamento associada do {% data variables.large_files.product_name_short %} no arquivo *.gitattributes*. +4. Salve e feche o arquivo *.gitattributes*. -### Removing all files within a {% data variables.large_files.product_name_short %} repository +### Remover todos os arquivos de um repositório do {% data variables.large_files.product_name_short %} -1. Remove the files from the repository's Git history using either the `filter-branch` command or BFG Repo-Cleaner. For detailed information on using these, see "[Removing sensitive data from a repository](/articles/removing-sensitive-data-from-a-repository)." -2. Optionally, to uninstall {% data variables.large_files.product_name_short %} in the repository, run: +1. Remova os arquivos do histórico do Git no repositório usando o comando `filter-branch` ou o BFG Repo-Cleaner. Para obter mais informações, consulte "[Remover dados confidenciais do repositório](/articles/removing-sensitive-data-from-a-repository)". +2. Como opção, para desinstalar o {% data variables.large_files.product_name_short %} do repositório, execute: ```shell $ git lfs uninstall ``` - For {% data variables.large_files.product_name_short %} versions below 1.1.0, run: + Para versões do {% data variables.large_files.product_name_short %} inferiores à 1.1.0, execute: ```shell $ git lfs uninit ``` -### {% data variables.large_files.product_name_short %} objects in your repository +### Objetos do {% data variables.large_files.product_name_short %} no repositório -After you remove files from {% data variables.large_files.product_name_short %}, the {% data variables.large_files.product_name_short %} objects still exist on the remote storage{% if currentVersion == "free-pro-team@latest" %} and will continue to count toward your {% data variables.large_files.product_name_short %} storage quota{% endif %}. +Depois de remover arquivos de {% data variables.large_files.product_name_short %}, os objetos de {% data variables.large_files.product_name_short %} ainda existem no armazenamento remoto {% if currentVersion == "free-pro-team@latest" %} e continuarão a contar para a sua cota de armazenamento de {% data variables.large_files.product_name_short %}{% endif %}. -To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. When you delete a repository, any associated issues, stars, and forks are also deleted. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)."{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Archived objects are purged after three months.{% endif %} +Para remover objetos de {% data variables.large_files.product_name_short %} de um repositório, {% if currentVersion == "free-pro-team@latest" %}, apague e recrie o repositório. Ao excluir um repositório, todos os problemas associados, estrelas e bifurcações também serão excluídos. Para obter mais informações, consulte "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)".{% else %}entre em contato com o administrador do {% data variables.product.prodname_enterprise %} para arquivar os objetos. Os objetos arquivados são excluídos após três meses.{% endif %} {% note %} -**Note:** If you removed a single file and have other {% data variables.large_files.product_name_short %} objects that you'd like to keep in your repository, after deleting and recreating your repository, reconfigure your {% data variables.large_files.product_name_short %}-associated files. For more information, see "[Removing a single file](#removing-a-single-file)" and "[Configuring {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)." +**Observação:** se você removeu um único arquivo e tem outros objetos do {% data variables.large_files.product_name_short %} que deseja manter no repositório, reconfigure os arquivos associados do {% data variables.large_files.product_name_short %} depois de excluir e recriar o repositório. Para obter mais informações, consulte "[Remover um único arquivo](#removing-a-single-file)" e "[Configurar {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)". {% endnote %} -### Further reading +### Leia mais -- "[About {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" -- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)" -- "[Installing {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" +- "[Sobre o {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" +- "[Colaboração com o {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)" +- "[Instalar o {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index c0f46c3657..f6b1b8f0f0 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -1,6 +1,6 @@ --- -title: About alerts for vulnerable dependencies -intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.' +title: Sobre alertas para dependências vulneráveis +intro: '{% data variables.product.product_name %} envia {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} quando detectarmos vulnerabilidades que afetam o repositório.' redirect_from: - /articles/about-security-alerts-for-vulnerable-dependencies - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies @@ -9,80 +9,85 @@ versions: enterprise-server: '*' --- -### About vulnerable dependencies +### Sobre as dependências vulneráveis {% data reusables.repositories.a-vulnerability-is %} -When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it. +Quando o seu código depende de um pacote que tenha uma vulnerabilidade de segurança, essa dependência vulnerável pode causar uma série de problemas para o seu projeto ou para as pessoas que o usam. -### Detection of vulnerable dependencies +### Detecção de dependências vulneráveis - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %} detecta dependências vulneráveis e envia {% data variables.product.prodname_dependabot_alerts %} alertas{% else %}{% data variables.product.product_name %} detecta dependências vulneráveis e envia alertas de segurança{% endif %} quando: {% if currentVersion == "free-pro-team@latest" %} -- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)." -- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %} -- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}."{% endif %} -- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +- Uma nova vulnerabilidade foi adicionada ao {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)". +- São processados dados de nova vulnerabilidade retirados de [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database).{% else %} +- São sincronizados novos dados de consultoria com {% data variables.product.prodname_ghe_server %} a cada hora a partir de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre dados de consultoria, consulte "Procurar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}{% endif %} +- O gráfico de dependências para alterações de repositório. Por exemplo, quando um colaborador faz push de um commit para alterar os pacotes ou versões de que depende{% if currentVersion == "free-pro-team@latest" %} ou quando o código de uma das dependências muda{% endif %}. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". -For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +Para obter uma lista dos ecossistemas para os quais o {% data variables.product.product_name %} pode detectar vulnerabilidades e dependências, consulte "[Ecossistemas de pacotes compatíveis](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". {% note %} -**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use. +**Observação:** É importante manter seus manifestos atualizados e seu arquivos bloqueados. Se o gráfico de dependências não refletir corretamente suas dependências e versões atuais, você poderá perder alertas para dependências vulneráveis que você usar. Você também pode receber alertas de dependências que você já não usa. {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %} -### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies +### Alertas do {% data variables.product.prodname_dependabot %} para dependências vulneráveis {% else %} -### Security alerts for vulnerable dependencies +### Alertas de segurança para dependências vulneráveis {% endif %} {% data reusables.repositories.enable-security-alerts %} -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detecta dependências vulneráveis em repositórios _públicos_ e gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios pertencentes à sua conta de usuário ou organização. Para mais informações consulte "[Gerenciar as configurações de segurança e análise da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". -{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." +{% data variables.product.product_name %} começa a gerar o gráfico de dependências imediatamente e gera alertas para quaisquer dependências vulneráveis assim que forem identificadas. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Para obter mais informações, consulte "[Gerenciando configurações do uso de dados de seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +Quando +{% data variables.product.product_name %} identifica uma dependência vulnerável, geramos um alerta {% data variables.product.prodname_dependabot %} e o exibimos na aba Segurança do repositório. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. {% data variables.product.product_name %} também notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} -For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +Para repositórios onde +{% data variables.product.prodname_dependabot_security_updates %} estão ativados, o alerta também pode conter um link para uma pull request para atualizar o manifesto ou arquivo de lock para a versão mínima que resolve a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. +Quando +{% data variables.product.product_name %} identifica uma dependência vulnerável, enviamos um alerta de segurança aos mantenedores dos repositórios afetados, com informações sobre a vulnerabilidade, um link para o arquivo afetado no projeto e informações sobre uma versão corrigida. {% endif %} {% warning %} -**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary. +**Observação**: Os recursos de segurança de {% data variables.product.product_name %} não reivindicam garantem que todas as vulnerabilidades sejam detectadas. Embora estejamos sempre tentando atualizar nosso banco de dados de vulnerabilidades e gerar alertas com nossas informações mais atualizadas. não seremos capazes de pegar tudo ou falar sobre vulnerabilidades conhecidas dentro de um período de tempo garantido. Esses recursos não substituem a revisão humana de cada dependência em busca de possíveis vulnerabilidades ou algum outro problema, e nossa sugestão é consultar um serviço de segurança ou realizar uma revisão completa de vulnerabilidade quando necessário. {% endwarning %} -### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts +### Acesso a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %} -You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +É possível ver todos os alertas que afetam um determinado projeto{% if currentVersion == "free-pro-team@latest" %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository){% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-dependabot-alerts)." +Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre novos +{% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. +Enviamos alertas de segurança para as pessoas com permissões de administrador nos repositórios afetados por padrão. +O {% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. {% endif %} -{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2. 1" %} Para mais informações, consulte "[Escolher o método de entrega para suas notificações](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" %} Para mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leia mais -- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} +- "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" +- "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index a645e9ae21..45a9faeff0 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -1,7 +1,7 @@ --- -title: About Dependabot security updates -intro: '{% data variables.product.prodname_dependabot %} can fix vulnerable dependencies for you by raising pull requests with security updates.' -shortTitle: About Dependabot security updates +title: Sobre as atualizações de segurança do Dependabot +intro: '{% data variables.product.prodname_dependabot %} pode corrigir dependências vulneráveis para você, levantando pull requests com atualizações de segurança.' +shortTitle: Sobre as atualizações de segurança do Dependabot redirect_from: - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates versions: @@ -10,26 +10,26 @@ versions: ### Sobre o {% data variables.product.prodname_dependabot_security_updates %} -{% data variables.product.prodname_dependabot_security_updates %} make it easier for you to fix vulnerable dependencies in your repository. If you enable this feature, when a {% data variables.product.prodname_dependabot %} alert is raised for a vulnerable dependency in the dependency graph of your repository, {% data variables.product.prodname_dependabot %} automatically tries to fix it. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +{% data variables.product.prodname_dependabot_security_updates %} torna mais fácil para você corrigir dependências vulneráveis no seu repositório. Se você habilitar este recurso, quando um alerta de {% data variables.product.prodname_dependabot %} for criado para uma dependência vulnerável no gráfico de dependências do seu repositório, {% data variables.product.prodname_dependabot %} tenta corrigir isso automaticamente. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis de](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" e "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". -{% data variables.product.prodname_dependabot %} checks whether it's possible to upgrade the vulnerable dependency to a fixed version without disrupting the dependency graph for the repository. Then {% data variables.product.prodname_dependabot %} raises a pull request to update the dependency to the minimum version that includes the patch and links the pull request to the {% data variables.product.prodname_dependabot %} alert, or reports an error on the alert. For more information, see "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." +{% data variables.product.prodname_dependabot %} verifica se é possível atualizar a dependência vulnerável para uma versão fixa sem comprometer o gráfico de dependências para o repositório. Em seguida, {% data variables.product.prodname_dependabot %} levanta um pull request para atualizar a dependência para a versão mínima que inclui o patch e os links do pull request para o alerta de {% data variables.product.prodname_dependabot %} ou relata um erro no alerta. Para obter mais informações, consulte "[Solução de problemas de erros de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". {% note %} **Observação** -The {% data variables.product.prodname_dependabot_security_updates %} feature is available for repositories where you have enabled the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. You will see a {% data variables.product.prodname_dependabot %} alert for every vulnerable dependency identified in your full dependency graph. However, security updates are triggered only for dependencies that are specified in a manifest or lock file. {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency that is not explicitly defined. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)". +O recurso de {% data variables.product.prodname_dependabot_security_updates %} está disponível para repositórios nos quais você habilitou o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Você verá um alerta de {% data variables.product.prodname_dependabot %} para cada dependência vulnerável identificada no seu gráfico de dependências completas. No entanto, atualizações de segurança são acionadas apenas para dependências especificadas em um manifesto ou arquivo de bloqueio. {% data variables.product.prodname_dependabot %} não consegue atualizar uma dependência indireta ou transitória que não esteja explicitamente definida. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)". {% endnote %} -### About pull requests for security updates +### Sobre os pull requests para atualizações de segurança -Each pull request contains everything you need to quickly and safely review and merge a proposed fix into your project. Isto inclui informações sobre a vulnerabilidade como, por exemplo, notas de lançamento, entradas de registros de mudanças e detalhes do commit. Details of which vulnerability a pull request resolves are hidden from anyone who does not have access to {% data variables.product.prodname_dependabot_alerts %} for the repository. +Cada pull request contém tudo o que você precisa para revisar mesclar, de forma rápida e segura, uma correção proposta em seu projeto. Isto inclui informações sobre a vulnerabilidade como, por exemplo, notas de lançamento, entradas de registros de mudanças e detalhes do commit. Detalhes de quais vulnerabilidades são resolvidas por um pull request de qualquer pessoa que não tem acesso a {% data variables.product.prodname_dependabot_alerts %} para o repositório. -When you merge a pull request that contains a security update, the corresponding {% data variables.product.prodname_dependabot %} alert is marked as resolved for your repository. For more information about {% data variables.product.prodname_dependabot %} pull requests, see "[Managing pull requests for dependency updates](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)." +Ao fazer merge de um pull request que contém uma atualização de segurança, o alerta de {% data variables.product.prodname_dependabot %} correspondente é marcado como resolvido no seu repositório. Para obter mais informações sobre pull requests de {% data variables.product.prodname_dependabot %}, consulte "[Gerenciar pull requests para atualizações de dependências](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)". {% data reusables.dependabot.automated-tests-note %} ### Sobre pontuações de compatibilidade -{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a vulnerability could cause breaking changes to your project. These are calculated from CI tests in other public repositories where the same security update has been generated. An update's compatibility score is the percentage of CI runs that passed when updating between specific versions of the dependency. +O {% data variables.product.prodname_dependabot_security_updates %} pode inclui uma pontuação de compatibilidade para que você saiba se atualizar uma vulnerabilidade pode causar alterações significativas no seu projeto. Estes são calculados a partir de testes de CI em outros repositórios públicos onde a mesma atualização de segurança foi gerada. Uma pontuação de compatibilidade da atualização é a porcentagem de execuções de CI que foram aprovadas durante a atualização entre versões específicas da dependência. diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-github-security-advisories.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-github-security-advisories.md index 73d18e4072..913431ac63 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-github-security-advisories.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-github-security-advisories.md @@ -1,5 +1,5 @@ --- -title: Sobre a consultoria de segurança do GitHub +title: Sobre os avisos de segurança do GitHub intro: 'Você pode usar o {% data variables.product.prodname_security_advisories %} para discutir, corrigir e publicar informações sobre vulnerabilidades de segurança no seu repositório.' redirect_from: - /articles/about-maintainer-security-advisories @@ -14,19 +14,19 @@ versions: ### Sobre o {% data variables.product.prodname_security_advisories %} -O {% data variables.product.prodname_security_advisories %} permite que os mantenedores de repositório discutam e corrijam uma vulnerabilidade de segurança em um projeto. Após colaborar em uma correção, os mantenedores dos repositórios podem publicar a consultoria de segurança para divulgar publicamente a vulnerabilidade de segurança da comunidade do projeto. Ao publicar a consultoria de segurança, os mantenedores de repositórios facilitam para a sua comunidade a atualização de dependências do pacote e a pesquisa do impacto das vulnerabilidades de segurança. +O {% data variables.product.prodname_security_advisories %} permite que os mantenedores de repositório discutam e corrijam uma vulnerabilidade de segurança em um projeto. Após colaborar em uma correção, os mantenedores dos repositórios podem publicar o aviso de segurança para divulgar publicamente a vulnerabilidade de segurança da comunidade do projeto. Ao publicar a consultoria de segurança, os mantenedores de repositórios facilitam para a sua comunidade a atualização de dependências do pacote e a pesquisa do impacto das vulnerabilidades de segurança. Com {% data variables.product.prodname_security_advisories %}, você pode: -1. Criar um projeto de consultoria de segurança e usar o rascunho para discutir em particular o impacto da vulnerabilidade no seu projeto. +1. Criar um aviso de segurança rascunho e usar o rascunho para discutir em particular o impacto da vulnerabilidade no seu projeto. 2. Colaborar de modo particular com a correção da vulnerabilidade em uma bifurcação privada temporária. -3. Publicar a consultoria de segurança para alertar a sua comunidade sobre a vulnerabilidade. +3. Publicar o aviso de segurança para alertar a sua comunidade sobre a vulnerabilidade. {% data reusables.repositories.security-advisories-republishing %} -Para começar, consulte "[Criar uma consultoria de segurança](/github/managing-security-vulnerabilities/creating-a-security-advisory)". +Para começar, consulte "[Criar um aviso de segurança](/github/managing-security-vulnerabilities/creating-a-security-advisory)." -Você pode dar crédito a indivíduos que contribuíram para uma consultora de segurança. Para obter mais informações, consulte "[Editar um consultor de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)". +Você pode dar crédito a indivíduos que contribuíram para um aviso de segurança. Para obter mais informações, consulte "[Editar um aviso de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)." {% data reusables.repositories.security-guidelines %} @@ -36,10 +36,10 @@ Você pode dar crédito a indivíduos que contribuíram para uma consultora de s {% data variables.product.prodname_security_advisories %} baseia-se na base da lista de Vulnerabilidades e Exposições Comuns (CVE). {% data variables.product.prodname_dotcom %} é uma Autoridade de Numeração CVE (CNA) e está autorizada a atribuir números de identificação CVE. Para obter mais informações, consulte "[Sobre CVE](https://cve.mitre.org/about/index.html)" e "[Autoridades de Numeração CVE](https://cve.mitre.org/cve/cna.html)" no site da CVE. -Ao criar uma consultoria de segurança para um repositório público no {% data variables.product.prodname_dotcom %}, você tem a opção de fornecer um número de identificação CVE existente para a vulnerabilidade de segurança. {% data reusables.repositories.request-security-advisory-cve-id %} +Ao criar um aviso de segurança para um repositório público no {% data variables.product.prodname_dotcom %}, você tem a opção de fornecer um número de identificação CVE existente para a vulnerabilidade de segurança. {% data reusables.repositories.request-security-advisory-cve-id %} -Uma que você publicou a consultoria de segurança e o {% data variables.product.prodname_dotcom %} atribuiu um número de identificação CVE para a vulnerabilidade, o {% data variables.product.prodname_dotcom %} irá publicar o CVE no banco de dados do MITRE. Para obter mais informações, consulte "[Publicar uma consultoria de segurança](/github/managing-security-vulnerabilities/publishing-a-security-advisory#requesting-a-cve-identification-number)". +Uma vez que você publicou o aviso de segurança e o {% data variables.product.prodname_dotcom %} atribuiu um número de identificação CVE para a vulnerabilidade, o {% data variables.product.prodname_dotcom %} irá publicar o CVE no banco de dados do MITRE. Para obter mais informações, consulte "[Publicar um aviso de segurança](/github/managing-security-vulnerabilities/publishing-a-security-advisory#requesting-a-cve-identification-number)." -### {% data variables.product.prodname_dependabot_alerts %} para consultoria de segurança publicada +### {% data variables.product.prodname_dependabot_alerts %} para o aviso de segurança publicado {% data reusables.repositories.github-reviews-security-advisories %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 235627fcba..2654037db9 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -1,7 +1,7 @@ --- title: Pesquisar vulnerabilidades de segurança no banco de dados de consultoria do GitHub intro: 'O {% data variables.product.prodname_advisory_database %} permite que você pesquise vulnerabilidades que afetam projetos de código aberto no {% data variables.product.company_short %}.' -shortTitle: Browsing the Advisory Database +shortTitle: Navegar no banco de dados da consultoria versions: free-pro-team: '*' --- diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index 860d7784a1..528e4bfc9a 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -1,7 +1,7 @@ --- -title: Configuring Dependabot security updates +title: Configurar atualizações de segurança do Dependabot intro: 'Você pode usar {% data variables.product.prodname_dependabot_security_updates %} ou pull requests manuais para atualizar facilmente dependências vulneráveis.' -shortTitle: Configuring Dependabot security updates +shortTitle: Configurar atualizações de segurança do Dependabot redirect_from: - /articles/configuring-automated-security-fixes - /github/managing-security-vulnerabilities/configuring-automated-security-fixes @@ -11,9 +11,9 @@ versions: free-pro-team: '*' --- -### About configuring {% data variables.product.prodname_dependabot_security_updates %} +### Sobre a configuração de {% data variables.product.prodname_dependabot_security_updates %} -You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +É possível habilitar o {% data variables.product.prodname_dependabot_security_updates %} para qualquer repositório que use {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." Você pode desativar as {% data variables.product.prodname_dependabot_security_updates %} em um repositório individual ou para todos os repositórios que pertencem à sua conta de usuário ou organização. Para obter mais informações, consulte "[Gerenciar o {% data variables.product.prodname_dependabot_security_updates %} para seus repositórios](#managing-dependabot-security-updates-for-your-repositories) abaixo". diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/creating-a-security-advisory.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/creating-a-security-advisory.md index 846c799628..b225e4c70a 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/creating-a-security-advisory.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/creating-a-security-advisory.md @@ -28,5 +28,5 @@ Qualquer pessoa com permissões de administrador em um repositório pode criar u - Faça um comentário sobre o rascunho da consultoria de segurança para discutir a vulnerabilidade com sua equipe. - Adicione colaboradores à consultora de segurança. Para obter mais informações, consulte "[Adicionar um colaborador a uma consultoria de segurança](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory)". - Colaborar de modo particular com a correção da vulnerabilidade em uma bifurcação privada temporária. Para obter mais informações, consulte "[Colaborar em uma bifurcação privada temporária para resolver uma vulnerabilidade de segurança](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)". -- Adicione indivíduos que deveriam receber crédito por contribuírem para a consultoria de segurança. Para obter mais informações, consulte "[Editar um consultor de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)". +- Adicione indivíduos que deveriam receber crédito por contribuírem para a consultoria de segurança. Para obter mais informações, consulte "[Editar um aviso de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)." - Publicar a consultoria de segurança para notificar a sua comunidade sobre a vulnerabilidade de segurança. Para obter mais informações, consulte "[Publicar uma consultoria de segurança](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index 6c6165d70e..bb789818c0 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -62,7 +62,7 @@ A publicação de uma consultor de segurança elimina a bifurcação privada tem 4. Na lista "consultoria de segurança", clique na consultoria de segurança que deseja publicar. ![Consultoria de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) 5. Na parte inferior da página, clique em **Publicar consultoria**. ![Botão Publish advisory (Publicar consultoria)](/assets/images/help/security/publish-advisory-button.png) -### {% data variables.product.prodname_dependabot_alerts %} para consultoria de segurança publicada +### {% data variables.product.prodname_dependabot_alerts %} para o aviso de segurança publicado {% data reusables.repositories.github-reviews-security-advisories %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index f1b3af4c35..5d56a02585 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -1,6 +1,6 @@ --- -title: Troubleshooting Dependabot errors -intro: 'Sometimes {% data variables.product.prodname_dependabot %} is unable to raise a pull request to update your dependencies. You can review the error and unblock {% data variables.product.prodname_dependabot %}.' +title: Solução de problemas do Dependabot +intro: 'Às vezes, {% data variables.product.prodname_dependabot %} não consegue criar um pull request para atualizar suas dependências. Você pode revisar o erro e desbloquear {% data variables.product.prodname_dependabot %}.' shortTitle: Solução de erros redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-github-dependabot-errors @@ -10,75 +10,75 @@ versions: {% data reusables.dependabot.beta-note %} -### About {% data variables.product.prodname_dependabot %} errors +### Sobre os erros do {% data variables.product.prodname_dependabot %} {% data reusables.dependabot.pull-request-introduction %} -If anything prevents {% data variables.product.prodname_dependabot %} from raising a pull request, this is reported as an error. +Se algo impedir o {% data variables.product.prodname_dependabot %} de criar um pull request, este será relatado como erro. -### Investigating errors with {% data variables.product.prodname_dependabot_security_updates %} +### Investigar erros com {% data variables.product.prodname_dependabot_security_updates %} -When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to fix a {% data variables.product.prodname_dependabot %} alert, it posts the error message on the alert. The {% data variables.product.prodname_dependabot_alerts %} view shows a list of any alerts that have not been resolved yet. To access the alerts view, click **{% data variables.product.prodname_dependabot_alerts %}** on the **Security** tab for the repository. Where a pull request that will fix the vulnerable dependency has been generated, the alert includes a link to that pull request. +Quando {% data variables.product.prodname_dependabot %} está impedido de criar um pull request para corrigir um alerta de {% data variables.product.prodname_dependabot %}, ele publica a mensagem de erro no alerta. A exibição do {% data variables.product.prodname_dependabot_alerts %} mostra uma lista de todos os alertas que ainda não foram resolvidos. Para acessar a vista de alertas, clique em **{% data variables.product.prodname_dependabot_alerts %}** na aba **Segurança** para o repositório. Quando um pull request que corrigirá a dependência vulnerável foi gerado, o alerta inclui um link para esse pull request. -![{% data variables.product.prodname_dependabot_alerts %} view showing a pull request link](/assets/images/help/dependabot/dependabot-alert-pr-link.png) +![Vista de {% data variables.product.prodname_dependabot_alerts %} que mostra um link do pull request](/assets/images/help/dependabot/dependabot-alert-pr-link.png) -There are three reasons why an alert may have no pull request link: +Há três razões pelas quais um alerta pode não ter link de um pull request: -1. {% data variables.product.prodname_dependabot_security_updates %} are not enabled for the repository. -1. The alert is for an indirect or transitive dependency that is not explicitly defined in a lock file. -1. An error blocked {% data variables.product.prodname_dependabot %} from creating a pull request. +1. {% data variables.product.prodname_dependabot_security_updates %} não estão habilitadas para o repositório. +1. O alerta é para uma dependência indireta ou transitória que não está explicitamente definida em um arquivo de bloqueio. +1. Um erro impediu {% data variables.product.prodname_dependabot %} de criar um pull request. -If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert. +Se um erro impediu que {% data variables.product.prodname_dependabot %} criasse um pull request, você pode exibir os detalhes do erro clicando no alerta. -![{% data variables.product.prodname_dependabot %} alert showing the error that blocked the creation of a pull request](/assets/images/help/dependabot/dependabot-security-update-error.png) +![O alerta do {% data variables.product.prodname_dependabot %} que mostra que o erro que bloqueou a criação de um pull request](/assets/images/help/dependabot/dependabot-security-update-error.png) -### Investigating errors with {% data variables.product.prodname_dependabot_version_updates %} +### Investigar erros com {% data variables.product.prodname_dependabot_version_updates %} -When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab. +Quando {% data variables.product.prodname_dependabot %} está impedido de criar um pull request para atualizar uma dependência em um ecossistema, ele posta o ícone de erro no arquivo de manifesto. Os arquivos de manifesto gerenciados por {% data variables.product.prodname_dependabot %} estão listados na aba {% data variables.product.prodname_dependabot %}. Para acessar essa aba, na aba **Insights** para o repositório, clique no **Gráfico de Dependências**, e, em seguida, clique na aba **{% data variables.product.prodname_dependabot %}**. -![{% data variables.product.prodname_dependabot %} view showing an error](/assets/images/help/dependabot/dependabot-tab-view-error-beta.png) +![vista de {% data variables.product.prodname_dependabot %} que mostra um erro](/assets/images/help/dependabot/dependabot-tab-view-error-beta.png) -To see the log file for any manifest file, click the **Last checked TIME ago** link. When you display the log file for a manifest that's shown with an error symbol (for example, Maven in the screenshot above), any errors are also displayed. +Para visualizar o arquivo de registro para qualquer arquivo de manifesto, clique no link **HORA da última verificação**. Ao exibir o arquivo de registro para um manifesto mostrado com um símbolo de erro (por exemplo, Maven, na captura de tela acima), todos os erros também serão exibidos. -![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png) +![Erro e registro de uma atualização de versão de {% data variables.product.prodname_dependabot %} ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png) -### Understanding {% data variables.product.prodname_dependabot %} errors +### Entender os erros de {% data variables.product.prodname_dependabot %} -Pull requests for security updates act to upgrade a vulnerable dependency to the minimum version that includes a fix for the vulnerability. In contrast, pull requests for version updates act to upgrade a dependency to the latest version allowed by the package manifest and {% data variables.product.prodname_dependabot %} configuration files. Consequently, some errors are specific to one type of update. +Pull requests para atualizações de segurança atuam para atualizar uma dependência vulnerável à versão mínima que inclui uma correção para a vulnerabilidade. Em contrapartida, os pull requests para atualizações de versão agem para atualizar uma dependência da versão mais recente permitida pelo manifesto do pacote e pelos arquivos de configuração de {% data variables.product.prodname_dependabot %}. Consequentemente, alguns erros são específicos para um tipo de atualização. -#### {% data variables.product.prodname_dependabot %} cannot update DEPENDENCY to a non-vulnerable version +#### {% data variables.product.prodname_dependabot %} não pode atualizar a DEPENDÊNCIA para uma versão não vulnerável -**Security updates only.** {% data variables.product.prodname_dependabot %} cannot create a pull request to update the vulnerable dependency to a secure version without breaking other dependencies in the dependency graph for this repository. +**Apenas atualizações de segurança.** {% data variables.product.prodname_dependabot %} não consegue criar um pull request para atualizar a dependência vulnerável para uma versão segura sem afetar outras dependências no gráfico de dependências para este repositório. -Every application that has dependencies has a dependency graph, that is, a directed acyclic graph of every package version that the application directly or indirectly depends on. Every time a dependency is updated, this graph must resolve otherwise the application won't build. When an ecosystem has a deep and complex dependency graph, for example, npm and RubyGems, it is often impossible to upgrade a single dependency without upgrading the whole ecosystem. +Cada aplicativo com dependências tem um gráfico de dependências, ou seja, um gráfico direcionado acíclico de cada versão de pacote da qual o aplicativo depende direta ou indiretamente. Toda vez que uma dependência é atualizada, este gráfico deve ser resolvido. Caso contrário, o aplicativo não será criado. Quando um ecossistema tem um gráfico de dependência profundo e complexo, por exemplo, npm e RubyGems, geralmente é impossível atualizar uma única dependência sem atualizar todo o ecossistema. -The best way to avoid this problem is to stay up to date with the most recently released versions, for example, by enabling version updates. This increases the likelihood that a vulnerability in one dependency can be resolved by a simple upgrade that doesn't break the dependency graph. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)." +A melhor maneira de evitar esse problema é manter-se atualizado com as versões mais recentes, habilitando, por exemplo, as atualizações de versões. Isso aumenta a probabilidade de que uma vulnerabilidade em uma dependência possa ser resolvida por meio de uma atualização simples que não afete o gráfico de dependência. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)." -#### {% data variables.product.prodname_dependabot %} cannot update to the required version as there is already an open pull request for the latest version +#### {% data variables.product.prodname_dependabot %} não consegue atualizar para a versão necessária, pois já existe um pull request aberto para a última versão -**Security updates only.** {% data variables.product.prodname_dependabot %} will not create a pull request to update the vulnerable dependency to a secure version because there is already an open pull request to update this dependency. You will see this error when a vulnerability is detected in a single dependency and there's already an open pull request to update the dependency to the latest version. +**Apenas atualizações de segurança.** {% data variables.product.prodname_dependabot %} não criará um pull request para atualizar a dependência vulnerável para uma versão segura, pois já existe um pull request aberto para atualizar esta dependência. Você verá este erro quando uma vulnerabilidade for detectada em uma única dependência e já houver um pull request aberto para atualizar a dependência para a última versão. -There are two options: you can review the open pull request and merge it as soon as you are confident that the change is safe, or close that pull request and trigger a new security update pull request. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)." +Existem duas opções: você pode revisar o pull request aberto e fazer o merge assim que estiver confiante de que a mudança é segura, ou fechar o pull request e acionar um novo pull request de atualização de segurança. Para obter mais informações, consulte "[Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". -#### {% data variables.product.prodname_dependabot %} timed out during its update +#### O {% data variables.product.prodname_dependabot %} esgotou o tempo durante esta atualização -{% data variables.product.prodname_dependabot %} took longer than the maximum time allowed to assess the update required and prepare a pull request. This error is usually seen only for large repositories with many manifest files, for example, npm or yarn monorepo projects with hundreds of *package.json* files. Updates to the Composer ecosystem also take longer to assess and may time out. +{% data variables.product.prodname_dependabot %} demorou mais do que o tempo máximo permitido para avaliar a atualização necessária e preparar um pull request. Este erro é geralmente visto apenas para repositórios grandes com muitos arquivos de manifesto, por exemplo, projetos do npm ou yarn monorepo com centenas de arquivos *package.json*. As atualizações no ecossistema do Composer também levam mais tempo para ser avaliadas e podem expirar. -This error is difficult to address. If a version update times out, you could specify the most important dependencies to update using the `allow` parameter or, alternatively, use the `ignore` parameter to exclude some dependencies from updates. Updating your configuration might allow {% data variables.product.prodname_dependabot %} to review the version update and generate the pull request in the time available. +Este erro é difícil de ser corrigido. Se a atualização de uma versão expirar, você poderá especificar as dependências mais importantes para atualizar usando o parâmetro `permitir` ou, como alternativa, você pode usar o parâmetro `ignorar` para excluir algumas dependências de atualizações. Atualizar sua configuração pode permitir que {% data variables.product.prodname_dependabot %} revise a atualização da versão e gere o pull request no tempo disponível. -If a security update times out, you can reduce the chances of this happening by keeping the dependencies updated, for example, by enabling version updates. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)." +Se uma atualização de segurança expirar, você pode reduzir as chances de isso acontecer mantendo as dependências atualizadas, por exemplo, habilitando atualizações de versão. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)." -#### {% data variables.product.prodname_dependabot %} cannot open any more pull requests +#### {% data variables.product.prodname_dependabot %} não consegue abrir mais nenhum pull request -There's a limit on the number of open pull requests {% data variables.product.prodname_dependabot %} will generate. When this limit is reached, no new pull requests are opened and this error is reported. The best way to resolve this error is to review and merge some of the open pull requests. +Há um limite no número de pull requests abertos que {% data variables.product.prodname_dependabot %} irá gerar. Quando este limite é atingido, nenhum pull request novo será aberto e este erro será relatado. A melhor maneira de resolver este erro é revisar e fazer merge alguns dos pull requests abertos. -There are separate limits for security and version update pull requests, so that open version update pull requests cannot block the creation of a security update pull request. The limit for security update pull requests is 10. By default, the limit for version updates is 5 but you can change this using the `open-pull-requests-limit` parameter in the configuration file. Para obter mais informações, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)". +Existem limites separados para solicitações de atualização de versões e segurança, para que os pull requests de atualização de versão aberta não possam bloquear a criação de uma solicitação de atualização de segurança. O limite para pull requests de atualização de segurança é 10. Por padrão, o limite para atualizações de versão é 5, mas você pode alterá-lo usando o parâmetro `open-pull-requests-limit` no arquivo de configuração. Para obter mais informações, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)". -The best way to resolve this error is to merge or close some of the existing pull requests and trigger a new pull request manually. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)." +A melhor maneira de resolver este erro é fazer o merge ou fechar alguns dos pull requests existentes e acionar um novo pull request manualmente. Para obter mais informações, consulte "[Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". -### Triggering a {% data variables.product.prodname_dependabot %} pull request manually +### Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente -If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. +Se você desbloquear {% data variables.product.prodname_dependabot %}, você poderá iniciar manualmente uma nova tentativa de criar um pull request. -- **Security updates**—display the {% data variables.product.prodname_dependabot %} alert that shows the error you have fixed and click **Create {% data variables.product.prodname_dependabot %} security update**. -- **Version updates**—display the log file for the manifest that shows the error that you have fixed and click **Check for updates**. +- **Atualizações de segurança**—exibe o alerta de {% data variables.product.prodname_dependabot %}, que mostra o erro que você corrigiu e clique em **Criar atualização de segurança de {% data variables.product.prodname_dependabot %}**. +- **Atualizações da versão**— exibir o arquivo de log para o manifesto que mostra o erro que você corrigiu e clique em **Verificar se há atualizações**. diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md index 878d09d6c1..7bfddce59e 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -1,7 +1,7 @@ --- title: Solução de problemas de detecção de dependências vulneráveis intro: 'Se as informações sobre dependências relatadas por {% data variables.product.product_name %} não são o que você esperava, há uma série de pontos a considerar, e várias coisas que você pode verificar.' -shortTitle: Troubleshooting detection +shortTitle: Solução de problemas versions: free-pro-team: '*' --- @@ -14,14 +14,14 @@ O {% data variables.product.prodname_dotcom %} gera e exibe dados de dependênci * {% data variables.product.prodname_advisory_database %} é uma das fontes de dados que {% data variables.product.prodname_dotcom %} usa para identificar dependências vulneráveis. É um banco de dados gratuito e curado com informações sobre vulnerabilidade para ecossistemas de pacote comum em {% data variables.product.prodname_dotcom %}. Inclui tanto dados relatados diretamente para {% data variables.product.prodname_dotcom %} de {% data variables.product.prodname_security_advisories %} quanto os feeds oficiais e as fontes comunitárias. Estes dados são revisados e curados por {% data variables.product.prodname_dotcom %} para garantir que informações falsas ou não acionáveis não sejam compartilhadas com a comunidade de desenvolvimento. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" e "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". * O gráfico de dependências analisa todos os arquivos conhecidos de manifesto de pacote no repositório de um usuário. Por exemplo, para o npm, ele irá analisar o arquivo _package-lock.json_. Ele constrói um gráfico de todas as dependências do repositório e dependências públicas. Isso acontece quando você habilita o gráfico de dependências e quando alguém faz push para o branch-padrão, e inclui commits que fazem alterações em um formato de manifesto compatível. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". -* {% data variables.product.prodname_dependabot %} verifica qualquer push, para o branch-padrão, que contém um arquivo de manifesto. Quando um novo registro de vulnerabilidade é adicionado, ele verifica todos os repositórios existentes e gera um alerta para cada repositório vulnerável. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" -* {% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." +* {% data variables.product.prodname_dependabot %} verifica qualquer push, para o branch-padrão, que contém um arquivo de manifesto. Quando um novo registro de vulnerabilidade é adicionado, ele verifica todos os repositórios existentes e gera um alerta para cada repositório vulnerável. {% data variables.product.prodname_dependabot_alerts %} são agregados ao nível do repositório, em vez de criar um alerta por vulnerabilidade. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" +* {% data variables.product.prodname_dependabot_security_updates %} são acionados quando você recebe um alerta sobre uma dependência vulnerável em seu repositório. Sempre que possível, {% data variables.product.prodname_dependabot %} cria um pull request no repositório para atualizar a dependência vulnerável à versão mínima segura necessária para evitar a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" e "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". - {% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. Por exemplo, uma varredura é acionada quando uma nova dependência é adicionada ({% data variables.product.prodname_dotcom %} verifica isso em cada push), ou quando uma nova vulnerabilidade é descoberta e adicionada ao banco de dados consultivo. + {% data variables.product.prodname_dependabot %} não faz a varredura de repositórios de dependências vulneráveis em uma programação, mas o faz quando algo muda. Por exemplo, uma varredura é acionada quando uma nova dependência é adicionada ({% data variables.product.prodname_dotcom %} verifica isso em cada push), ou quando uma nova vulnerabilidade é descoberta e adicionada ao banco de dados consultivo. ### Por que não recebo alertas de vulnerabilidade em alguns ecossistemas? -O {% data variables.product.prodname_dotcom %} limita seu suporte a alertas de vulnerabilidade a um conjunto de ecossistemas onde podemos fornecer dados de alta qualidade e relevantes. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot %} security updates are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. Nós continuaremos a adicionar suporte para mais ecossistemas ao longo do tempo. Para uma visão geral dos ecossistemas de pacotes suportados por nós, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +O {% data variables.product.prodname_dotcom %} limita seu suporte a alertas de vulnerabilidade a um conjunto de ecossistemas onde podemos fornecer dados de alta qualidade e relevantes. Vulnerabilidades organizadas em {% data variables.product.prodname_advisory_database %}, o gráfico de dependências, {% data variables.product.prodname_dependabot_alerts %} e as atualizações de segurança de {% data variables.product.prodname_dependabot %} são fornecidas para vários ecossistemas, incluindo o Maven do Java, npm e Yarn do JavaScript, ,NET's NuGet, Pip Python, RubyGems e Compositor do PHP. Nós continuaremos a adicionar suporte para mais ecossistemas ao longo do tempo. Para uma visão geral dos ecossistemas de pacotes suportados por nós, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". Vale a pena notar que a [{% data variables.product.prodname_dotcom %} Consultoria de Segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) pode existir para outros ecossistemas. As informações em uma consultoria de segurança são fornecidas pelos mantenedores de um determinado repositório. Estes dados não são curados da mesma forma que as informações relativas aos ecossistemas suportados. @@ -31,7 +31,7 @@ Vale a pena notar que a [{% data variables.product.prodname_dotcom %} Consultori O gráfico de dependências inclui informações sobre dependências explicitamente declaradas em seu ambiente. Ou seja, dependências que são especificadas em um manifesto ou um arquivo de bloqueio. O gráfico de dependências, geralmente, também inclui dependências transitivas, mesmo quando não são especificadas em um arquivo de travamento analisando as dependências das dependências em um arquivo de manifesto. -{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. As atualizações de segurança {% data variables.product.prodname_dependabot %} apenas sugerem uma mudança onde ela pode "corrigir" diretamente a dependência, ou seja, quando estas são: +Os {% data variables.product.prodname_dependabot_alerts %} aconselham você com relação a dependências que você deve atualizar, incluindo dependências transitivas, em que a versão pode ser determinada a partir de um manifesto ou de um arquivo de bloqueio. As atualizações de segurança {% data variables.product.prodname_dependabot %} apenas sugerem uma mudança onde ela pode "corrigir" diretamente a dependência, ou seja, quando estas são: * Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio * Dependências transitórias declaradas em um arquivo de bloqueio @@ -51,17 +51,17 @@ Sim, o gráfico de dependências tem duas categorias de limites: 1. **Limites de processamento** - These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created. + Eles afetam o gráfico de dependências exibido dentro de {% data variables.product.prodname_dotcom %} e também impedem que sejam criados {% data variables.product.prodname_dependabot_alerts %}. - Manifestos com tamanho superior a 0.5 MB são processados apenas para contas corporativas. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}. + Manifestos com tamanho superior a 0.5 MB são processados apenas para contas corporativas. Para outras contas, manifestos acima de 0,5 MB são ignorados e não criarão {% data variables.product.prodname_dependabot_alerts %}. - Por padrão, o {% data variables.product.prodname_dotcom %} não processará mais de 20 manifestos por repositório. {% data variables.product.prodname_dependabot_alerts %} are not be created for manifests beyond this limit. Se você precisar aumentar o limite, entre em contato com {% data variables.contact.contact_support %}. + Por padrão, o {% data variables.product.prodname_dotcom %} não processará mais de 20 manifestos por repositório. Não são criados {% data variables.product.prodname_dependabot_alerts %} para manifestos acima deste limite. Se você precisar aumentar o limite, entre em contato com {% data variables.contact.contact_support %}. 2. **Limites de visualização** - Eles afetam o que é exibido no gráfico de dependências dentro de {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created. + Eles afetam o que é exibido no gráfico de dependências dentro de {% data variables.product.prodname_dotcom %}. No entanto, eles não afetam {% data variables.product.prodname_dependabot_alerts %} que foram criados. - A exibição de dependências do gráfico de dependências em um repositório só exibe 100 manifestos. De modo geral, isso é adequado, já que é significativamente maior do que o limite de processamento descrito acima. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}. + A exibição de dependências do gráfico de dependências em um repositório só exibe 100 manifestos. De modo geral, isso é adequado, já que é significativamente maior do que o limite de processamento descrito acima. Em situações em que o limite de processamento é superior a 100, os {% data variables.product.prodname_dependabot_alerts %} são criados para quaisquer manifestos que não são mostrados dentro de {% data variables.product.prodname_dotcom %}. **Verifique**: A dependência que falta está em um arquivo de manifesto superior a 0,5 MB ou em um repositório com um grande número de manifestos? @@ -83,9 +83,9 @@ Uma vez que {% data variables.product.prodname_dependabot %} usa dados curados e Quando uma dependência tem várias vulnerabilidades, apenas um alerta agregado é gerado para essa dependência, em vez de um alerta por vulnerabilidade. -The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities. +A contagem de {% data variables.product.prodname_dependabot_alerts %} em {% data variables.product.prodname_dotcom %} mostra um total para o número de alertas, ou seja, o número de dependências com vulnerabilidades, não o número de vulnerabilidades. -![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png) +![Vista de {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-view.png) Ao clicar para exibir os detalhes de alerta, você pode ver quantas vulnerabilidades são incluídas no alerta. @@ -98,4 +98,4 @@ Ao clicar para exibir os detalhes de alerta, você pode ver quantas vulnerabilid - "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" - "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" -- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)" +- "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)" diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index a1e4114a7a..1a8935eb50 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -11,11 +11,11 @@ versions: A aba de alertas do {% data variables.product.prodname_dependabot %} do seu repositório lista todos {% data variables.product.prodname_dependabot_alerts %} e as {% data variables.product.prodname_dependabot_security_updates %} correspondente. Você pode classificar a lista de alertas usando o menu suspenso e clicar em determinados alertas para ver mais detalhes. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" -É possível habilitar atualizações de segurança automáticas para qualquer repositório que usa o {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +É possível habilitar atualizações de segurança automáticas para qualquer repositório que usa o {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." ### Sobre atualizações para dependências vulneráveis no seu repositório -{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository. Para repositórios em que o {% data variables.product.prodname_dependabot_security_updates %} está ativado, quando {% data variables.product.product_name %} detecta uma dependência vulnerável, {% data variables.product.prodname_dependabot %} cria um pull request para corrigi-la. O pull request irá atualizar a dependência para a versão minimamente segura possível, o que é necessário para evitar a vulnerabilidade. +O {% data variables.product.product_name %} gera {% data variables.product.prodname_dependabot_alerts %} quando detectamos vulnerabilidades que afetam o seu repositório. Para repositórios em que o {% data variables.product.prodname_dependabot_security_updates %} está ativado, quando {% data variables.product.product_name %} detecta uma dependência vulnerável, {% data variables.product.prodname_dependabot %} cria um pull request para corrigi-la. O pull request irá atualizar a dependência para a versão minimamente segura possível, o que é necessário para evitar a vulnerabilidade. ### Visualizar e atualizar dependências vulneráveis @@ -34,4 +34,4 @@ A aba de alertas do {% data variables.product.prodname_dependabot %} do seu repo - "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)" - "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" -- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)" +- "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)" diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index dfd63bc638..27ee1d9b3c 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -21,7 +21,12 @@ Você pode optar por assinar notificações para: - Uma conversa em um problema específico, pull request ou gist. - Todas as atividades em um repositório ou em uma discussão em equipe. - Atividade CI, como o status de fluxos de trabalho nos repositórios configurados com {% data variables.product.prodname_actions %}. +{% if currentVersion == "free-pro-team@latest" %} +- Issues, pulls requests, releases and discussions (if enabled) in a repository. +{% endif %} +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - Lançamentos em um repositório. +{% endif %} Você também pode optar por assistir automaticamente todos os repositórios aos quais você tem acesso de push, exceto as bifurcações. É possível assistir qualquer outro repositório ao qual você tenha acesso manualmente clicando em **Watch** (Assistir). diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index a41f92ef02..21b59a6445 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -21,16 +21,17 @@ versions: ### Opções de entrega de notificação -Você tem três opções básicas para a entrega de notificação: - - a caixa de entrada de notificações em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} - - a caixa de entrada de notificações em {% data variables.product.prodname_mobile %}, que sincroniza com a caixa de entrada em {% data variables.product.product_name %}{% endif %} - - um cliente de e-mail que usa um endereço de e-mail verificado, que também pode sincronizar com a caixa de entrada de {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% endif %} +You can receive notifications for activity on {% data variables.product.product_name %} in the following locations. + + - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" %} + - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_name %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} {% if currentVersion == "free-pro-team@latest" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obter mais informações, consulte "[Escolhendo suas configurações de notificação](#choosing-your-notification-settings)". {% endif %} -{% data reusables.notifications-v2.tip-for-syncing-email-and-your-inbox-on-github %} +{% data reusables.notifications.shared_state %} #### Benefícios da caixa de entrada de notificações @@ -59,8 +60,21 @@ As notificações de e-mail também permitem flexibilidade com os tipos de notif ### Sobre notificações de participação e inspeção -Quando você inspeciona um repositório, você assina atualizações de atividade nesse repositório. Da mesma forma, quando você inspeciona as discussões de uma equipe específica, você está inscrito em todas as atualizações de conversa na página daquela equipe. Para ver os repositórios que você está inspecionando, consulte [https://github.com/watching](https://github.com/watching). Para obter mais informações, consulte "[Gerenciando assinaturas e notificações do GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". +Quando você inspeciona um repositório, você assina atualizações de atividade nesse repositório. Da mesma forma, quando você inspeciona as discussões de uma equipe específica, você está inscrito em todas as atualizações de conversa na página daquela equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/github/building-a-strong-community/about-team-discussions)". +To see repositories that you're watching, go to your [watching page](https://github.com/watching). Para obter mais informações, consulte "[Gerenciando assinaturas e notificações do GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +#### Configurar notificações +{% endif %} +You can configure notifications for a repository on the repository page, or on your watching page. +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}{% if currentVersion == "free-pro-team@latest" %} + +#### About custom notifications +{% data reusables.notifications-v2.custom-notifications-beta %} +You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository. +{% endif %} For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)." + +#### Participating in conversations A qualquer momento que você comentar em uma conversa ou quando alguém @mencionar seu nome de usuário, você estará _participando_ de uma conversa. Por padrão, você é inscrito automaticamente em uma conversa ao participar dela. Você pode cancelar manualmente a inscrição de uma conversa que você participou, clicando em **Cancelar inscrição** no problema ou na pull request ou através da opção **Cancelar inscrição** na caixa de entrada de notificações. Para conversas que você está inspecionando ou participando, você pode escolher se deseja receber notificações por e-mail ou através da caixa de entrada em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% endif %}. @@ -95,7 +109,9 @@ Escolha um endereço de e-mail padrão para enviar atualizações de conversas q - Pushes de pull request. - Suas próprias atualizações, como quando você abre, comenta ou encerra um problema ou uma pull request. -Dependendo da organização proprietária do repositório, também é possível enviar notificações para diferentes endereços de e-mail para repositórios específicos. Por exemplo, você pode enviar notificações para um repositório público específico para um endereço de e-mail pessoal verificado. Sua organização pode exigir que o endereço de e-mail seja verificado para um domínio específico. Para obter mais informações, consulte “[Escolhendo para onde as notificações de e-mail de sua organização serão enviadas](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)". +Depending on the organization that owns the repository, you can also send notifications to different email addresses. Sua organização pode exigir que o endereço de e-mail seja verificado para um domínio específico. For more information, see "[Choosing where your organization’s email notifications are sent](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)." + +You can also send notifications for a specific repository to an email address. Para obter mais informações, consulte "[Sobre notificações de email para push no seu repositório](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)". {% data reusables.notifications-v2.email-notification-caveats %} @@ -110,7 +126,7 @@ As notificações de e-mail do {% data variables.product.product_name %} contêm | Header | Informações | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Endereço do `remetente` | Este endereço será sempre {% if currentVersion == "free-pro-team@latest" %}'`notifications@github. om`'{% else %}'endereço de e-mail de não responda configurado pelo administrador do site'{% endif %}. | -| Campo `To` | This field connects directly to the thread.{% if currentVersion != "github-ae@latest" %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} +| Campo `To` | Este campo conecta-se diretamente à corrente.{% if currentVersion != "github-ae@latest" %} Se você responder ao e-mail, você adicionará um novo comentário na conversa.{% endif %} | Endereço de `Cc` | O {% data variables.product.product_name %} colocará você em cópia (`Cc`) se você estiver inscrito para uma conversa. O segundo endereço de e-mail de `Cc` corresponde ao motivo da notificação. O sufixo para esses motivos de notificação é {% data variables.notifications.cc_address %}. Os possíveis motivos de notificação são:
  • 'assign': você foi atribuído a um problema ou uma pull request.
  • 'author': você criou um problema ou uma pull request.
  • 'comment': você comentou um problema ou uma pull request.
  • 'manual': houve uma atualização em um problema ou uma pull request para o(a) qual você assinou manualmente.
  • 'mention': você foi mencionado em um problema ou uma pull request.
  • 'push': alguém fez commit em uma pull request que você assinou.
  • 'review_requested': você ou uma equipe da qual faz você faz parte foi solicitado para revisar uma pull request.
    • {% if currentVersion != "github-ae@latest" %}
  • 'security_alert': o {% data variables.product.prodname_dotcom %} detectou uma vulnerabilidade em um repositório para o qual você recebe alertas de segurança.
    • {% endif %}
  • 'state_change': um problema ou uma pull request que você assinou foi fechado(a) ou aberto(a).
  • 'subscribed': houve uma atualização em um repositório que você está inspecionando.
  • 'team_mention': uma equipe a qual você pertence foi mencionada em um problema ou uma pull request.
  • 'your_activity': você abriu, comentou ou fechou um problema ou uma pull request.
| | campo `mailing list` | Esse campo identifica o nome do repositório e seu proprietário. O formato desse endereço é sempre `..{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} | campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Os níveis possíveis de gravidade são:
  • `low`
  • `moderate`
  • `high`
  • `critical`
Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %} @@ -167,9 +183,9 @@ Se você for integrante de mais de uma organização, você poderá configurar c {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} {% data reusables.notifications.vulnerable-dependency-notification-options %} -For more information about the notification delivery methods available to you, and advice on optimizing your notifications for +Para obter mais informações sobre os métodos de entrega de notificações disponíveis para você e conselhos sobre otimização de suas notificações -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} @@ -188,14 +204,14 @@ Quando você instalar {% data variables.product.prodname_mobile %}, você será Você só pode receber notificações de pushes para repositórios no {% data variables.product.prodname_mobile %} neste momento. -#### Habilitando notificações push com {% data variables.product.prodname_ios %} +#### Habilitar notificações de push com {% data variables.product.prodname_ios %} 1. Acima de "Home", clique na foto do seu perfil. 2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}. ![Ícone de configurações para GitHub para iOS](/assets/images/help/mobile/ios-settings-icon.png) 3. Para atualizar suas configurações de notificação, clique em **Notificações push**. 4. Para ativar as notificações push para menções diretas, use a alternância **Menções Diretas**. -#### Habilitando notificações push com {% data variables.product.prodname_android %} +#### Habilitar notificações de push com {% data variables.product.prodname_android %} 1. Acima de "Home", clique na foto do seu perfil. 2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}. ![Ícone de configurações para GitHub para iOS](/assets/images/help/mobile/android-settings-icon.png) diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 253908d3c6..1e87b53721 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -82,7 +82,7 @@ Filtros personalizados atualmente não suportam: - Distinguindo entre filtros de consulta `is:issue`, `is:pr` e `is:pull-request`. Essas consultas retornarão problemas e pull requests. - Criando mais de 15 filtros personalizados. - Alterando os filtros padrão ou sua ordenação. - - Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`. + - Pesquise a [exclusão](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) usando `NÃO` ou `-QUALIFICADOR`. ### Consultas suportadas para filtros personalizados @@ -106,15 +106,15 @@ Para filtrar notificações por motivos pelos quais recebeu uma atualização, v | `reason:invitation` | Quando você for convidado para uma equipe, organização ou repositório. | | `reason:manual` | Quando você clicar em **Assinar** em um problema ou uma pull request que você ainda não estava inscrito. | | `reason:mention` | Você foi @mencionado diretamente. | -| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% if currentVersion != "github-ae@latest" %} -| `reason:security-alert` | When a security alert is issued for a repository.{% endif %} +| `reason:review-requested` | Foi solicitado que você ou uma equipe revise um um pull request.{% if currentVersion != "github-ae@latest" %} +| `reason:security-alert` | Quando um alerta de segurança é emitido para um repositório.{% endif %} | `reason:state-change` | Quando o estado de uma pull request ou um problema é alterado. Por exemplo, um problema é fechado ou uma pull request é mesclada. | | `reason:team-mention` | Quando uma equipe da qual você é integrante é @mencionada. | | `reason:ci-activity` | Quando um repositório tem uma atualização de CI, como um novo status de execução de fluxo de trabalho. | #### Consultas suportadas `is:` -Para filtrar notificações para uma atividade específica no {% data variables.product.product_name %}, você pode usar a consulta `is`. For example, to only see repository invitation updates, use `is:repository-invitation`{% if currentVersion != "github-ae@latest" %}, and to only see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts, use `is:repository-vulnerability-alert`.{% endif %} +Para filtrar notificações para uma atividade específica no {% data variables.product.product_name %}, você pode usar a consulta `is`. Por exemplo, para ver apenas atualizações de convite do repositório, use `is:repository-invitation`{% if currentVersion ! "github-ae@latest" %}, e para ver somente {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %}{% else %} alertas de {% endif %} segurança, use `is:repository-vulnerability-alert`.{% endif %} - `is:check-suite` - `is:commit` @@ -127,8 +127,8 @@ Para filtrar notificações para uma atividade específica no {% data variables. - `is:team-discussion` {% if currentVersion != "github-ae@latest" %} -For information about reducing noise from notifications for -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +Para informações sobre a redução de ruído de notificações para +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". {% endif %} Você também pode usar a consulta `is:` para descrever como a notificação passou pela triagem. diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 274369b044..f3689ccbf9 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -55,6 +55,13 @@ Quando você deixa de inspecionar um repositório, você cancela sua assinatura {% data reusables.notifications.access_notifications %} 1. Na barra lateral esquerda, na lista de repositórios, use o menu suspenso "Gerenciar notificações" para clicar em **Inspecionar repositórios**. ![Gerenciar as opções do menu suspenso notificações](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Na página de repositórios inspecionados, depois de ter avaliado os repositórios que você está inspecionando, escolha se deseja: +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - deixar de inspecionar um repositório - inspecionar somente versões em um repositório - ignorar todas as notificações de um repositório +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} + - deixar de inspecionar um repositório + - ignorar todas as notificações de um repositório + - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled) +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index 104b627a85..f1026b06e7 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -32,7 +32,16 @@ Quando sua caixa de entrada tiver muitas notificações para gerenciar, consider Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)". -Para ter uma visão geral das assinaturas de seu repositório, consulte "[Revisando repositórios que você está inspecionando](#reviewing-repositories-that-youre-watching). Muitas pessoas esquecem os repositórios que eles escolheram inspecionar no passado. Na página "Repositórios inspecionados" você pode rapidamente deixar de acompanhar repositórios. Para obter mais informações sobre suas opções para cancelamento de assinatura, consulte "[Gerenciando assinaturas](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." +Para ter uma visão geral das assinaturas de seu repositório, consulte "[Revisando repositórios que você está inspecionando](#reviewing-repositories-that-youre-watching). +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. + +{% endtip %} +{% endif %} + +Muitas pessoas esquecem os repositórios que eles escolheram inspecionar no passado. Na página "Repositórios inspecionados" você pode rapidamente deixar de acompanhar repositórios. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### Revisando todas as suas assinaturas @@ -55,20 +64,38 @@ Para ter uma visão geral das assinaturas de seu repositório, consulte "[Revisa ### Revisando repositórios que você está inspecionando 1. Na barra lateral esquerda, na lista de repositórios, use o menu suspenso "Gerenciar notificações" e clique em **Repositórios inspecionados**. ![Gerenciar as opções do menu suspenso notificações](/assets/images/help/notifications-v2/manage-notifications-options.png) - -3. Avalie os repositórios que você está inspecionando e decida se suas atualizações ainda são relevantes e úteis. Quando você inspeciona um repositório, você será notificado de todas as conversas desse repositório. - +2. Avalie os repositórios que você está inspecionando e decida se suas atualizações ainda são relevantes e úteis. Quando você inspeciona um repositório, você será notificado de todas as conversas desse repositório. +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} + ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% endif %} {% tip %} - **Dica:** Em vez de inspecionar um repositório, considere apenas inspecionar versões de um repositório ou desacompanhar completamente um repositório. Quando você deixa de inspecionar um repositório, você ainda pode ser notificado quando for @mencionado ou estiver participando de um thread. Quando você acompanha apenas versões para um repositório, você só é notificado quando há uma nova versão, quando está participando de um thread, ou quando você ou uma equipe do qual participa forem @mencionados. + **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" %}when there are updates to issues, pull requests, releases or discussions (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository. + + Quando você deixa de inspecionar um repositório, você ainda pode ser notificado quando for @mencionado ou estiver participando de um thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned. {% endtip %} ### Configurando as configurações de inspeção para um repositório individual -É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. Você também pode optar por ser notificado apenas sobre novas versões ou ignorar um repositório individual. +É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository. {% data reusables.repositories.navigate-to-repo %} -2. No canto superior direito, clique no menu suspenso "Inspecionar" para selecionar uma opção de inspeção. ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options.png) +2. No canto superior direito, clique no menu suspenso "Inspecionar" para selecionar uma opção de inspeção. +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} + ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options-custom.png) +{% data reusables.notifications-v2.custom-notifications-beta %} +The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. + + ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2.png) + +If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. + +{% endif %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md b/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md index 39b73088df..5e9c3695ce 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md @@ -14,7 +14,7 @@ Você pode coletar feedback, reportar erros de software e organizar tarefas que {% data reusables.pull_requests.close-issues-using-keywords %} -Para se manter atualizado sobre os comentários mais recentes em um problema, você pode inspecionar um problema a fim de recebe notificações sobre os últimos comentários. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +Para se manter atualizado sobre os comentários mais recentes em um problema, você pode inspecionar um problema a fim de recebe notificações sobre os últimos comentários. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)". diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/creating-an-issue.md b/translations/pt-BR/content/github/managing-your-work-on-github/creating-an-issue.md index 18ae4f592a..2696b3ff1f 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/creating-an-issue.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/creating-an-issue.md @@ -1,6 +1,7 @@ --- title: Criar um problema intro: 'Os problemas podem ser usados para acompanhar erros, aprimoramentos ou outras solicitações.' +permissions: 'People with read permissions can create an issue in a repository where issues are enabled.' redirect_from: - /articles/creating-an-issue versions: @@ -9,8 +10,6 @@ versions: github-ae: '*' --- -{% data reusables.repositories.create-issue-in-public-repository %} - Você pode abrir um novo problema com base no código de uma pull request existente. Para obter mais informações, consulte "[Abrir um problema a partir de código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Você pode abrir um novo problema diretamente de um comentário em um problema ou uma revisão de pull request. Para obter mais informações, consulte "[Abrir um problema a partir de um comentário](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md index 892032e8c3..568cddd84b 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md @@ -1,6 +1,6 @@ --- -title: File attachments on issues and pull requests -intro: 'When you open issue or update a pull request, you can use issue attachments to upload images of proposed features or screenshots of bugs.' +title: Anexar arquivos em problemas e pull requests +intro: 'Ao abrir um problema ou atualizar uma pull request, é possível usar a publicação de anexos para fazer upload de imagens de recursos propostos ou capturas de tela de erros.' redirect_from: - /articles/issue-attachments/ - /articles/file-attachments-on-issues-and-pull-requests @@ -9,33 +9,34 @@ versions: enterprise-server: '*' github-ae: '*' --- + {% warning %} -**Warning:** If you add an image to a pull request or issue comment, anyone can view the anonymized image URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive images private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized image URLs](/articles/about-anonymized-image-urls)".{% endif %} +**Aviso:** caso você inclua uma imagem para uma pull request ou comentário de problemas, qualquer pessoa poderá ver a URL anônima de imagem sem autenticação, mesmo se a pull request estiver em um repositório privado{% if enterpriseServerVersions contains currentVersion %} ou se o modo privado estiver habilitado{% endif %}. Para manter imagens confidenciais privadas, use uma rede privada ou um servidor que requer autenticação. {% if currentVersion == "free-pro-team@latest" %}Para mais informações sobre URLs anônimas, consulte "[Sobre URLs de imagem anônima](/articles/about-anonymized-image-urls)".{% endif %} {% endwarning %} -To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer. +Para anexar um arquivo a uma conversa sobre um problema ou pull request, arraste-o e solte-o dentro da caixa de comentários. Como alternativa, você pode clicar na barra na parte inferior da caixa de comentários para navegar, selecionar e adicionar um arquivo do seu computador. -![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png) +![Selecionar anexos do computador](/assets/images/help/pull_requests/select-bar.png) {% tip %} -**Tip:** In many browsers, you can copy-and-paste images directly into the box. +**Dica:** Em muitos navegadores, você pode copiar e colar imagens diretamente na caixa. {% endtip %} -The maximum size for files is 25MB and the maximum size for images is 10MB. +O tamanho máximo é de 25MB para arquivos e 10MB para imagens. -We support these files: +Arquivos compatíveis: * PNG (*.png*) * GIF (*.gif*) * JPEG (*.jpg*) -* Log files (*.log*) -* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents -* Text files (*.txt*) +* Arquivos log (*.log*) +* Documentos do Microsoft Word (*.docx*), Powerpoint (*.pptx*), e Excel (*.xlsx*) +* Arquivos de texto (*.txt*) * PDFs (*.pdf*) * ZIP (*.zip*, *.gz*) -![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif) +![Anexos GIF animados](/assets/images/help/pull_requests/dragging_images.gif) diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md b/translations/pt-BR/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md index 0b90cf40f6..756d98806e 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md @@ -22,7 +22,7 @@ Também é possível usar a barra de pesquisa "Filter cards" (Fitrar cartões) q - Filtrar cartões por status de verificação com `status:pending`, `status:success` ou `status:failure` - Filtrar cartões por tipo com `type:issue`, `type:pr` ou `type:note` - Filtrar cartões por estado e tipo com `is:open`, `is:closed` ou `is:merged`; e `is:issue`, `is:pr` ou `is:note` -- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- Filtrar cartões por problemas vinculados a um pull request por uma referência de fechamento usando `linkado:pr`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou versão atual == "github-ae@latest" %} - Filtrar cartões por repositório em um quadro de projetos de toda a organização usando `repo:ORGANIZATION/REPOSITORY`{% endif %} 1. Navegue até o quadro de projetos que contém os cartões que você deseja filtrar. diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/index.md b/translations/pt-BR/content/github/managing-your-work-on-github/index.md index cd00627213..6cdef8cdcd 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/index.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/index.md @@ -14,7 +14,7 @@ versions: ### Índice -{% topic_link_in_list /managing-your-work-with-issues %} +{% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} @@ -27,6 +27,7 @@ versions: {% link_in_list /pinning-an-issue-to-your-repository %} {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} + {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} {% link_in_list /about-automation-for-issues-and-pull-requests-with-query-parameters %} {% link_in_list /file-attachments-on-issues-and-pull-requests %} @@ -35,12 +36,6 @@ versions: {% link_in_list /disabling-issues %} {% link_in_list /linking-a-pull-request-to-an-issue %} {% link_in_list /about-duplicate-issues-and-pull-requests %} -{% topic_link_in_list /labeling-issues-and-pull-requests %} - {% link_in_list /about-labels %} - {% link_in_list /creating-a-label %} - {% link_in_list /applying-labels-to-issues-and-pull-requests %} - {% link_in_list /editing-a-label %} - {% link_in_list /deleting-a-label %} {% topic_link_in_list /managing-project-boards %} {% link_in_list /about-project-boards %} {% link_in_list /creating-a-project-board %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md index 72b27d8618..acc92b2f0f 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md @@ -1,6 +1,6 @@ --- title: Vinculando uma pull request a um problema -intro: 'You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when the pull request is merged.' +intro: 'Você pode vincular um pull request a um problema para mostrar que uma correção está em andamento e para fechar automaticamente o problema quando o pull request for mesclado.' redirect_from: - /articles/closing-issues-via-commit-message/ - /articles/closing-issues-via-commit-messages/ @@ -20,7 +20,7 @@ versions: ### Sobre problemas e pull requests vinculados -You can link an issue to a pull request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}manually or {% endif %}using a supported keyword in the pull request description. +Você pode vincular um problema a um pull request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}manualmente ou {% endif %}usando uma palavra-chave compatível na descrição do pull request. Quando você vincula uma pull request ao problema que a pull request tem de lidar, os colaboradores poderão ver que alguém está trabalhando no problema. {% if currentVersion ver_lt "enterprise-server@2. 1" %}Se o pull request e o problema estiverem em repositórios diferentes, {% data variables.product.product_name %} mostrará o link após o merge do pull request, se a pessoa que mescla o pull request também tiver permissão para fechar o problema.{% endif %} @@ -50,7 +50,7 @@ Você pode vincular uma solicitação de pull a um problema usando uma palavra-c * fix * fixes * fixed -* resolver +* resolve * resolve * resolved @@ -62,7 +62,7 @@ A sintaxe para fechar palavras-chave depende se o problema está no mesmo reposi | Problema em um repositório diferente | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | | Múltiplos problemas | Usar sintaxe completa para cada problema | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}Only manually linked pull requests can be manually unlinked. Para desvincular um problema que você vinculou usando uma palavra-chave, você deve editar a descrição da pull request para remover a palavra-chave.{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}Apenas pull requests vinculados manualmente podem ser desvinculados. Para desvincular um problema que você vinculou usando uma palavra-chave, você deve editar a descrição da pull request para remover a palavra-chave.{% endif %} Você também pode usar palavras-chave de fechamento em uma mensagem de commit. O problema será encerrado quando você mesclar o commit no branch padrão, mas o pull request que contém o commit não será listado como um pull request vinculado. diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/managing-labels.md b/translations/pt-BR/content/github/managing-your-work-on-github/managing-labels.md new file mode 100644 index 0000000000..82cae55e2a --- /dev/null +++ b/translations/pt-BR/content/github/managing-your-work-on-github/managing-labels.md @@ -0,0 +1,97 @@ +--- +title: Managing labels +intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +redirect_from: + - /articles/managing-Labels + - /articles/labeling-issues-and-pull-requests + - /github/managing-your-work-on-github/labeling-issues-and-pull-requests + - /articles/about-labels + - /github/managing-your-work-on-github/about-labels + - /articles/creating-and-editing-labels-for-issues-and-pull-requests + - /articles/creating-a-label + - /github/managing-your-work-on-github/creating-a-label + - /articles/customizing-issue-labels/ + - /articles/applying-labels-to-issues-and-pull-requests + - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests + - /articles/editing-a-label + - /github/managing-your-work-on-github/editing-a-label + - /articles/deleting-a-label + - /github/managing-your-work-on-github/deleting-a-label +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Sobre etiquetas + +Você pode gerenciar seu trabalho no {% data variables.product.product_name %} criando etiquetas para classificar problemas e pull requests. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. + +Qualquer pessoa com acesso de leitura a um repositório pode exibir e pesquisar etiquetas do repositório. Para criar, editar, aplicar ou excluir uma etiqueta, é preciso ter acesso de gravação ao repositório. + +### About default labels + +O {% data variables.product.product_name %} fornece etiquetas padrão para todos os repositórios novos. Você pode usar essas etiquetas padrão para ajudar com a criação de um fluxo de trabalho padronizado em um repositório. + +| Etiqueta | Descrição | +| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `documentation` | Indica a necessidade de aprimoramentos ou adições à documentação{% endif %} +| `duplicate` | Indica problemas ou pull requests semelhantes | +| `enhancement` | Indica novas solicitações de recurso | +| `good first issue` | Indica um bom problema para contribuidores principiantes | +| `help wanted` | Indica que um mantenedor deseja ajudar em um problema ou uma pull request | +| `invalid` | Indica que um problema ou uma pull request não é mais relevante | +| `question` | Indica que um problema ou uma pull request precisa de mais informações | +| `wontfix` | Indica que o trabalho não continuará em um problema ou uma pull request | + +Etiquetas padrão são incluídas em todos os novos repositórios quando criados, mas você pode editar ou excluir as etiquetas posteriormente. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +Os proprietários da organização podem personalizar as etiquetas padrão para repositórios na organização. Para obter mais informações, consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)". +{% endif %} + +### Criar uma etiqueta + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. À direita do campo de pesquisa, clique em **New label** (Nova etiqueta). +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### Aplicar etiquetas a problemas e pull requests + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. No canto superior direito, clique em **Label** (Etiqueta) e comece a digitar o nome de uma etiqueta existente. Clique no nome da etiqueta para associá-la aos itens selecionados. ![Menu suspenso atribuição Marco Problemas](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### Editar uma etiqueta + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### Excluir uma etiqueta +Deleting a label will remove the label from issues and pull requests. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.delete-label %} + +### Leia mais +- "[Sobre etiquetas](/articles/about-labels)" +- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md new file mode 100644 index 0000000000..487e1155e1 --- /dev/null +++ b/translations/pt-BR/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Managing your work with issues and pull requests +intro: 'Você pode gerenciar seu trabalho no {% data variables.product.product_name %} criando problemas para rastrear ideias, melhorias, tarefas ou erros.' +mapTopic: true +redirect_from: + - /github/managing-your-work-on-github/managing-your-work-with-issues + - /articles/managing-your-work-with-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md b/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md index f7d5f05ccf..509bc78875 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md @@ -1,6 +1,7 @@ --- title: Abrindo um problema a partir de um comentário intro: É possível abrir um problema novo a partir de um comentário específico em um problema ou uma pull request. +permissions: 'People with read permissions can create an issue in a repository where issues are enabled.' versions: free-pro-team: '*' enterprise-server: '*' @@ -9,6 +10,8 @@ versions: Quando você abre um problema a partir de um comentário, o problema contém um trecho mostrando onde o comentário foi originalmente publicado. +{% data reusables.repositories.administrators-can-disable-issues %} + 1. Navegue até o comentário no qual deseja abrir um problema. 2. No comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.![Botão de kebab no comentário de revisão de pull request](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png) diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-code.md b/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-code.md index ec00134067..22514def85 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-code.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/opening-an-issue-from-code.md @@ -1,6 +1,7 @@ --- title: Abrir um problema a partir de código intro: É possível abrir um problema novo a partir de uma linha ou linhas específicas de código em um arquivo ou pull request. +permissions: 'People with read permissions can create an issue in a repository where issues are enabled.' redirect_from: - /articles/opening-an-issue-from-code versions: @@ -13,7 +14,7 @@ Quando você abre um problema de código, o problema contém um trecho mostrando ![Trecho de código fornecido em um problema aberto de código](/assets/images/help/repository/issue-opened-from-code.png) -{% data reusables.repositories.create-issue-in-public-repository %} +{% data reusables.repositories.administrators-can-disable-issues %} {% data reusables.repositories.navigate-to-repo %} 2. Localize o código que deseja referenciar em um problema: diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 5ce3c0d281..295806bb42 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,7 +11,7 @@ versions: Para transferir um problema aberto para outro repositório, é preciso ter permissões de gravação no repositório em que o problema está e no repositório para onde você está transferindo o problema. Para obter mais informações, consulte "[Níveis de permissão do repositório para organizações](/articles/repository-permission-levels-for-an-organization)". -Você somente pode transferir problemas entre repositórios pertencentes à mesma conta de usuário ou organização. É possível transferir um problema de um repositório privado para um repositório público. +You can only transfer issues between repositories owned by the same user or organization account.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} Quando você transfere um problema, os comentários e responsáveis são mantidos. As etiquetas e os marcos do problema não são retidos. Esse problema permanecerá em qualquer quadro de projeto pertencente ao usuário ou à organização e será removido dos quadros de projeto de todos os repositórios. Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 44850bd665..d394bcb1bb 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -40,7 +40,7 @@ Para pull requests, você também pode usar a pesquisa para: - Filtrar pull requests nas quais um revisor tenha solicitado alterações: `state:open type:pr review:changes_requested` - Filtrar pull requests por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` - Filtrar pull requests pelo usuário específico [solicitado para revisão](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat` -- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- Filtre os pull requests pela equipe solicitada para revisão: `state:open type:pr team-review-requested:github/atom`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou versão atual == "github-ae@latest" %} - Filtro por pull requests que estão vinculadas a um problema que a pull request pode concluir: `linked:issue`{% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md index 625f69695c..a862624e1d 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md @@ -16,4 +16,4 @@ Os painéis de problemas e pull requests estão disponíveis na parte superior d ### Leia mais -- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}”[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}”[Listing the repositories you're watching](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" +- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[Visualizar as suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listar os repositórios que você está inspecionando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md index 4994d250db..b217de6f11 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -14,7 +14,7 @@ versions: github-ae: '*' --- -Você pode pesquisar globalmente em todo o {% data variables.product.product_name %} ou definir o escopo da sua pesquisa para uma organização ou um repositório específico. +{% data reusables.search.you-can-search-globally %} - Para pesquisar globalmente em todo o {% data variables.product.product_name %}, digite o que está procurando no campo de pesquisa que fica na parte superior de qualquer página e escolha "All {% data variables.product.prodname_dotcom %}" (Em todo o GitHub) no menu suspenso da pesquisa. - Para pesquisar em uma organização ou um repositório específico, navegue até a página da organização ou do repositório, digite o que está procurando no campo de pesquisa que fica na parte superior da página e pressione **Enter**. @@ -23,7 +23,8 @@ Você pode pesquisar globalmente em todo o {% data variables.product.product_nam **Notas:** -- {% data reusables.search.required_login %} +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- {% data reusables.search.required_login %}{% endif %} - Os sites do {% data variables.product.prodname_pages %} não são pesquisáveis no {% data variables.product.product_name %}. No entanto, você pode pesquisar o conteúdo da fonte, se ele existir no branch padrão de um repositório, usando a pesquisa de código. Para obter mais informações, consulte "[Pesquisar código](/articles/searching-code)". Para obter mais informações sobre o {% data variables.product.prodname_pages %}, consulte "[O que é o GitHub Pages?](/articles/what-is-github-pages/)" - Atualmente, a nossa pesquisa não é compatível com correspondência exata. - Sempre que você estiver pesquisando em arquivos de código, serão retornados apenas os dois primeiros resultados de cada arquivo. @@ -36,7 +37,7 @@ A pesquisa do {% data variables.product.product_name %} usa um cluster do Elasti ### Tipos de pesquisa no {% data variables.product.prodname_dotcom %} -Você pode pesquisar os seguintes tipos de informação em todos os repositórios públicos do {% data variables.product.product_name %} e em todos os repositórios privados do {% data variables.product.product_name %} aos quais você tem acesso: +You can search for the following information across all repositories you can access on {% data variables.product.product_location %}. - [Repositórios](/articles/searching-for-repositories) - [Tópicos](/articles/searching-topics) @@ -63,9 +64,9 @@ Se você usar o {% data variables.product.prodname_enterprise %} e for integrant É possível pesquisar em ambos os ambientes apenas no {% data variables.product.prodname_enterprise %}. Para definir o escopo da pesquisa por ambiente, você pode usar uma opção de filtro na {% data variables.search.advanced_url %} ou pode usar o prefixo de pesquisa `environment:`. Para pesquisar apenas por conteúdo no {% data variables.product.prodname_enterprise %}, use a sintaxe de pesquisa `environment:local`. Para pesquisar apenas por conteúdo no {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. O administrador do site do {% data variables.product.prodname_enterprise %} pode habilitar a {% data variables.product.prodname_unified_search %} para todos os repositórios públicos, todos os repositórios privados ou apenas determinados repositórios privados na organização do {% data variables.product.prodname_ghe_cloud %} conectado. -If your site administrator enables +Se o administrador do seu site habilitar -{% data variables.product.prodname_unified_search %} in private repositories, you can only search in the private repositories that the administrator enabled {% data variables.product.prodname_unified_search %} for and that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Os administradores do {% data variables.product.prodname_enterprise %} e os proprietários da organização no {% data variables.product.prodname_dotcom_the_website %} não podem pesquisar repositórios privados que pertencem à sua conta. Para pesquisar repositórios privados aplicáveis, você deve habilitar a pesquisa de repositório privado para suas contas pessoais no {% data variables.product.prodname_dotcom_the_website %} e no {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte "[Habilitar pesquisa de repositório privado do {% data variables.product.prodname_dotcom_the_website %} na sua conta do {% data variables.product.prodname_enterprise %}](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)". +{% data variables.product.prodname_unified_search %} em repositórios privados, você só poderá pesquisar nos repositórios privados para os quais o administrador habilitou {% data variables.product.prodname_unified_search %} e aos quais você tem acesso na organização de {% data variables.product.prodname_dotcom_the_website %} conectada. Os administradores do {% data variables.product.prodname_enterprise %} e os proprietários da organização no {% data variables.product.prodname_dotcom_the_website %} não podem pesquisar repositórios privados que pertencem à sua conta. Para pesquisar repositórios privados aplicáveis, você deve habilitar a pesquisa de repositório privado para suas contas pessoais no {% data variables.product.prodname_dotcom_the_website %} e no {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte "[Habilitar pesquisa de repositório privado do {% data variables.product.prodname_dotcom_the_website %} na sua conta do {% data variables.product.prodname_enterprise %}](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)". {% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md index 7e869b84a8..10df7d995c 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -Você pode pesquisar códigos globalmente no {% data variables.product.product_name %} ou pesquisar em uma organização ou um repositório específico. Para pesquisar códigos em todos os repositórios públicos, é necessário ter iniciado a sessão em uma conta do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre a pesquisa no GitHub](/articles/about-searching-on-github)". +{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/articles/about-searching-on-github)." Você pode pesquisar códigos usando somente estes qualificadores de pesquisa de código. Qualificadores de pesquisa específicos para repositórios, usuários ou commits não funcionarão com a pesquisa de códigos. @@ -21,13 +21,13 @@ Você pode pesquisar códigos usando somente estes qualificadores de pesquisa de Devido à complexidade da pesquisa de códigos, a execução das pesquisas apresenta algumas restrições: -- {% data reusables.search.required_login %} +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- {% data reusables.search.required_login %}{% endif %} - O código em [bifurcações](/articles/about-forks) só poderá ser pesquisado se a bifurcação tiver mais estrelas do que o repositório principal. Bifurcações com menos estrelas do que o repositório principal **não** são indexadas para pesquisa de códigos. Para incluir bifurcações com mais estrelas que o repositório principal delas nos resultados da pesquisa, você precisará adicionar `fork:true` ou `fork:only` à sua consulta. Para obter mais informações, consulte "[Pesquisar em bifurcações](/articles/searching-in-forks)". - Apenas o _branch-padrão_ é indexado para pesquisa de código.{% if currentVersion == "free-pro-team@latest" %} - Somente arquivos com menos de 384 KB são pesquisados.{% else %}* Somente arquivos com menos de 5 MB são pesquisados. - Somente os primeiros 500 KB de cada arquivo são pesquisados.{% endif %} - Somente repositórios com menos de 500.000 arquivos são pesquisados. -- Os usuários que fizeram login podem pesquisar em todos os repositórios públicos. - Com exceção das pesquisas por [`filename`](#search-by-filename), é necessário incluir pelo menos um termo da pesquisa ao pesquisar o código-fonte. Por exemplo, pesquisar [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) não é válido, enquanto pesquisar [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) é. - Os resultados da pesquisa exibem no máximo dois fragmentos do mesmo arquivo, mas o arquivo pode ter mais resultados. - Não é possível usar os seguintes caracteres-curinga na consulta de pesquisa: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ]. A pesquisa simplesmente ignora esses símbolos. diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md index 77c10cc93b..abc6977400 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md @@ -96,14 +96,11 @@ Para pesquisar commits em todos os repositórios de um determinado usuário ou o | org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) identifica as mensagens do commit com a palavra "test" nos repositórios de @github. | | repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) identifica as mensagens do commit com a palavra "language" no repositório "gibberish" de @defunkt. | -### Filtrar repositórios públicos ou privados +### Filter by repository visibility -O qualificador `is` identifica commits públicos ou privados. +The `is` qualifier matches commits from repositories with the specified visibility. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility). -| Qualifier | Exemplo | -| ------------ | ------------------------------------------------------------------------------------------------------- | -| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) identifica os commits públicos. | -| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) identifica os commits privados. | +| Qualifier | Example | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories. ### Leia mais diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-for-repositories.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-for-repositories.md index 03da189133..6b22e9c55b 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-for-repositories.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-for-repositories.md @@ -10,7 +10,7 @@ versions: github-ae: '*' --- -Você pode pesquisar repositórios globalmente no {% data variables.product.product_name %} ou pesquisar em uma organização específica. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/articles/about-searching-on-github)". +Você pode pesquisar repositórios globalmente no {% data variables.product.product_location %} ou pesquisar em uma organização específica. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/articles/about-searching-on-github)". Para incluir bifurcações nos resultados da pesquisa, você precisará adicionar `fork:true` ou `fork:only` à sua consulta. Para obter mais informações, consulte "[Pesquisar em bifurcações](/articles/searching-in-forks)". @@ -20,22 +20,22 @@ Para incluir bifurcações nos resultados da pesquisa, você precisará adiciona Com o qualificador `in`, você pode restringir a pesquisa ao nome do repositório, descrição do repositório, conteúdo do arquivo README ou qualquer combinação desses itens. Quando você omite esse qualificador, somente o nome e a descrição do repositório são pesquisados. -| Qualifier | Exemplo | -| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) identifica os repositórios com "jquery" no nome. | -| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) identifica repositórios com "jquery" no nome ou na descrição. | -| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) identifica os repositórios que mencionam "jquery" no arquivo README. | -| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) identifica um nome de repositório específico. | +| Qualifier | Exemplo | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name. | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description. | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file. | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) identifica um nome de repositório específico. | ### Pesquisar com base no conteúdo do repositório -Você pode enconar um repositório pesquisando o conteúdo em seu arquivo README usando o qualificador `in:readme`. +You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. Para obter mais informações, consulte "[Sobre LEIAME](/github/creating-cloning-and-archiving-repositories/about-readmes)". Além de usar o `in:readme`, não é possível encontrar repositórios pesquisando um conteúdo específico no repositório. Para pesquisar um arquivo ou conteúdo específico em um repositório, você pode usar o localizador de arquivos os qualificadores de pesquisa específicos para código. Para obter mais informações, consulte "[Localizar arquivos no {% data variables.product.prodname_dotcom %}](/articles/finding-files-on-github)" e "[Pesquisar códigos](/articles/searching-code)". -| Qualifier | Exemplo | -| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) identifica repositórios que mencionam "octocat" no arquivo README. | +| Qualifier | Exemplo | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file. | ### Pesquisar nos repositórios de um usuário ou uma organização @@ -48,7 +48,7 @@ Para pesquisar em todos os repositórios de um determinado usuário ou organiza ### Pesquisar por tamanho do repositório -O qualificador `size` procura repositórios que têm um tamanho específico (em kilobytes) usando os [qualificadores maior que, menor que e intervalo](/articles/understanding-the-search-syntax). +The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." | Qualifier | Exemplo | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -59,7 +59,7 @@ O qualificador `size` procura repositórios que têm um tamanho específico (em ### Pesquisar por número de seguidores -Você pode filtrar repositórios com base no número de seguidores usando o qualificador `followers` com os [qualificadores maior que, menor que e intervalo](/articles/understanding-the-search-syntax). +You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." | Qualifier | Exemplo | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | @@ -68,7 +68,7 @@ Você pode filtrar repositórios com base no número de seguidores usando o qual ### Pesquisar por número de bifurcações -O qualificador `forks` especifica o número de bifurcações que um repositório deve ter usando os [qualificadores maior que, menor que e intervalo](/articles/understanding-the-search-syntax). +The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." | Qualifier | Exemplo | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -79,7 +79,7 @@ O qualificador `forks` especifica o número de bifurcações que um repositório ### Pesquisar por número de estrelas -Você pode pesquisar repositórios com base no número de [estrelas](/articles/saving-repositories-with-stars) do repositório usando os [qualificadores maior que, menor que e intervalo](/articles/understanding-the-search-syntax). +You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." | Qualifier | Exemplo | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -103,7 +103,7 @@ Os dois usam uma data como parâmetro. {% data reusables.time_date.date_format % ### Pesquisar por linguagem -Você pode pesquisar repositórios com base na linguagem em que eles foram escritos. +You can search repositories based on the language of the code in the repositories. | Qualifier | Exemplo | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -111,7 +111,7 @@ Você pode pesquisar repositórios com base na linguagem em que eles foram escri ### Pesquisar por tópico -Você pode encontrar todos os repositórios que estão classificados com um determinado [tópico](/articles/classifying-your-repository-with-topics). +You can find all of the repositories that are classified with a particular topic. Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)". | Qualifier | Exemplo | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -119,53 +119,55 @@ Você pode encontrar todos os repositórios que estão classificados com um dete ### Pesquisar por número de tópicos -Você pode pesquisar repositórios pelo número de [tópicos](/articles/classifying-your-repository-with-topics) que foram aplicados usando o qualificador `topics` e os [qualificadores maior que, menor que e intervalo](/articles/understanding-the-search-syntax). +You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." | Qualifier | Exemplo | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) identifica os repositórios com cinco tópicos. | | | [**tópicos:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) correspondem a repositórios com mais de três tópicos. | +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + ### Pesquisar por licença -Você pode pesquisar repositórios pela [licença](/articles/licensing-a-repository). Você deve usar uma [palavra-chave de licença](/articles/licensing-a-repository/#searching-github-by-license-type) para filtrar repositórios por uma licença específica ou por uma família de licenças. +You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. Para obter mais informações, consulte "[Licenciar um repositório](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)". | Qualifier | Exemplo | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) identifica os repositórios que são licenciados com a Licença Apache 2.0. | -### Pesquisar por repositório público ou privado +{% endif %} -Você pode filtrar a pesquisa para identificar somente repositórios públicos ou privados. +### Search by repository visibility -| Qualifier | Exemplo | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories&utf8=%E2%9C%93) identifica os repositórios do GitHub que são públicos. | -| `is:private` | [**is:private pages**](https://github.com/search?utf8=%E2%9C%93&q=pages+is%3Aprivate&type=Repositories) identifica os repositórios privados aos quais você tem acesso e contêm a palavra "pages". | +You can filter your search based on the visibility of the repositories. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." {% if currentVersion == "free-pro-team@latest" %} ### Pesquisar com base no fato de o repositório ser um espelho -Você pode pesquisar os repositórios com base no critério de que são um espelho ou não e se estão hospedados em outro lugar. Para obter mais informações, consulte "[Encontrar maneiras de contribuir para o código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." +You can search repositories based on whether the repositories are mirrors and hosted elsewhere. Para obter mais informações, consulte "[Encontrar maneiras de contribuir para o código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." -| Qualifier | Exemplo | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) identifica os repositórios que são espelhos e contêm a palavra "GNOME". | -| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) identifica os repositórios que não são espelhos e contêm a palavra "GNOME". | +| Qualifier | Exemplo | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) identifica os repositórios que são espelhos e contêm a palavra "GNOME". | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME." | {% endif %} ### Pesquisar com base no fato de o repositório estar arquivado -Você pode pesquisar repositórios com base no fato dele estar ou não [arquivado](/articles/about-archiving-repositories). +You can search repositories based on whether or not the repositories are archived. For more information, see "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)." -| Qualifier | Exemplo | -| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) identifica os repositórios que estão arquivados e contêm a palavra "GNOME". | -| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) identifica os repositórios que não estão arquivados e contêm a palavra "GNOME". | +| Qualifier | Exemplo | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) identifica os repositórios que estão arquivados e contêm a palavra "GNOME". | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME." | {% if currentVersion == "free-pro-team@latest" %} + ### Pesquisar com base no número de problemas com as etiquetas `good first issue` (um bom primeiro problema) ou `help wanted` (procura-se ajuda) Você pode pesquisar repositórios que têm um número mínimo de problemas com as etiquetas `help-wanted` (procura-se ajuda) ou `good-first-issue` (um bom primeiro problema) com os qualificadores `help-wanted-issues:>n` e `good-first-issues:>n`. Para obter mais informações, consulte "[Incentivar contribuições úteis para o seu projeto com etiquetas](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)". @@ -174,6 +176,7 @@ Você pode pesquisar repositórios que têm um número mínimo de problemas com | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) identifica os repositórios com mais de dois problemas com a etiqueta `good-first-issue` e que contêm a palavra "javascript". | | `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) identifica os repositórios com mais de quatro problemas com a etiqueta `help-wanted` e que contêm a palavra "React". | + {% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 74ec0b1461..a392df187c 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -14,7 +14,7 @@ Você pode pesquisar problemas e pull requests globalmente no {% data variables. {% tip %} -**Tips:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +**Dicas:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - Este artigo tem exemplos de pesquisa no site {% data variables.product.prodname_dotcom %}.com, mas você pode usar os mesmos filtros de pesquisa na {% data variables.product.product_location %}.{% endif %} - Para obter uma lista de sintaxes de pesquisa que podem ser adicionadas a qualquer qualificador de pesquisa para melhorar ainda mais os resultados, consulte "[Entender a sintaxe de pesquisa](/articles/understanding-the-search-syntax)". - Use aspas em termos de pesquisa com várias palavras. Por exemplo, se quiser pesquisar problemas com a etiqueta "In progress," pesquise `label:"in progress"`. A pesquisa não faz distinção entre maiúsculas e minúsculas. @@ -64,66 +64,63 @@ Você pode filtrar somente problemas e pull requests abertos ou fechados usando | `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) identifica os problemas abertos com a palavra "performance". | | `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) identifica os problemas e as pull requests fechados com a palavra "android". | -### Pesquisar por repositório público ou privado +### Filter by repository visibility -Ao [pesquisar em todo o {% data variables.product.product_name %}](https://github.com/search), pode ser útil restringir os resultados aos repositórios públicos ou privados. Você pode fazer isso com os qualificadores `is:public` e `is:private`. +You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." -| Qualifier | Exemplo | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) identifica os problemas e as pull requests em todos os repositórios públicos. | -| `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate&type=Issues) identifica os problemas e as pull requests que contêm a palavra "cupcake" em repositórios privados aos quais você tem acesso. | +| Qualifier | Example | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. ### Pesquisar por autor O qualificador `author` encontra problemas e pull requests criados por determinado usuário ou conta de integração. -| Qualifier | Exemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) identifica os problemas e as pull requests com a palavra "cool" que foram criados por @gjtorikian. | -| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) identifica os problemas escritos por @mdo que contêm a palavra "bootstrap" no texto. | -| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) identifica os problemas criados pela conta de integração com nome "robot". | +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian. | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body. | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot." | ### Pesquisar por responsável -O qualificador `assignee` encontra problemas e pull requests que foram atribuídos a um determinado usuário. Não é possível pesquisar problemas e pull requests que têm _qualquer_ responsável, mas é possível pesquisar [problemas e pull requests que não tem nenhum responsável](#search-by-missing-metadata). +O qualificador `assignee` encontra problemas e pull requests que foram atribuídos a um determinado usuário. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata). -| Qualifier | Exemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) identifica os problemas e as pull requests no libgit2 de libgit2 que foram atribuídos a @vmg. | +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg. | ### Pesquisar por menção O qualificador `mentions` encontra problemas que mencionam um usuário específico. Para obter mais informações, consulte "[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)". -| Qualifier | Exemplo | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) identifica os problemas com a palavra "resque" que mencionam @defunkt. | +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. | ### Pesquisar por menção da equipe Para organizações e equipes das quais você faz parte, você pode usar o qualificador `team` para encontrar problemas ou pull requests que fazem @menção a uma equipe específica na organização. Substitua os nomes de exemplo pelos nome da organização e da equipe para fazer uma pesquisa. -| Qualifier | Exemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------- | -| team:ORGNAME/TEAMNAME | **team:jekyll/owners** identifica os problemas em que a equipe `@jekyll/owners` é mencionada. | -| | **team:myorg/ops is:open is:pr** identifica as pull requests abertas em que a equipe `@myorg/ops` é mencionada. | +| Qualifier | Exemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned. | +| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned. | ### Pesquisar por autor do comentário O qualificador `commenter` encontra problemas que contêm um comentário de um usuário específico. -| Qualifier | Exemplo | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) identifica os problemas nos repositórios do GitHub que contêm a palavra "github" e têm um comentário de @defunkt. | +| Qualifier | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt. | ### Pesquisar por um usuário envolvido em um problema ou uma pull request Você pode usar o qualificador `involves` para encontrar problemas que envolvem de alguma forma um usuário específico. O qualificador `involves` é uma expressão lógica OR entre os qualificadores `author`, `assignee`, `mentions` e `commenter` para um único usuário. Em outras palavras, esse qualificador encontra problemas e pull requests que foram criados por um usuário, atribuídos a ele, que o mencionam ou que foram comentados por ele. -| Qualifier | Exemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** identifica os problemas que envolvem @defunkt ou @jlord. | -| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) identifica os problemas que envolvem @mdo e não contêm a palavra "bootstrap" no texto. | +| Qualifier | Exemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in. | +| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body. | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### Procurar problema e pull requests vinculados @@ -166,7 +163,7 @@ Você pode usar o qualificador `project` para encontrar problemas associados a u ### Pesquisar por status do commit -Você pode filtrar pull requests com base no status dos commits. Isso é especialmente útil ao usar [a API de status](/v3/repos/statuses/) ou um serviço CI. +Você pode filtrar pull requests com base no status dos commits. Isso é especialmente útil ao usar [a API de status](/rest/reference/repos#statuses) ou um serviço CI. | Qualifier | Exemplo | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 58a10ab88f..cec29aa9ed 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -51,7 +51,7 @@ O número de trabalhos que você pode executar simultaneamente em todos os repos No final do mês, {% data variables.product.prodname_dotcom %} calcula o custo de minutos e armazenamento usado sobre o valor incluído em sua conta. Por exemplo, se sua organização usa {% data variables.product.prodname_team %} e permite gastos ilimitados, usando 15.000 minutos, poderia ter um custo total de armazenamento e custo médio de minuto de $56, dependendo dos sistemas operacionais usados para executar trabalhos. - 5.000 (3.000 Linux e 2.000 Windows) minutos = $56 ($24 + $32). - - 3,000 Linux minutes at $0.008 per minute = $24. + - 3.000 minutos Linux a $0,008 por minuto = $ 24. - 2.000 minutos do Windows a $0,016 por minuto = $32. No final do mês, {% data variables.product.prodname_dotcom %} arredonda sua transferência de dados para o GB mais próximo. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 2696f92227..93e44adb09 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -40,7 +40,7 @@ Alguns IdPs suportam acesso de provisionamento a uma organização do {% data va ### Adicionar integrantes a uma organização usando SAML SSO -Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adicionar novos integrantes à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, consulte "[Convidar usuários para juntar-se à sua organização](/articles/inviting-users-to-join-your-organization)" e "[Integrantes](/v3/orgs/members/#add-or-update-organization-membership)". +Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adicionar novos integrantes à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, consulte "[Convidar usuários para juntar-se à sua organização](/articles/inviting-users-to-join-your-organization)" e "[Integrantes](/rest/reference/orgs#add-or-update-organization-membership)". {% data reusables.organizations.team-synchronization %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index f0bd86f273..8205802885 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -12,7 +12,7 @@ Se você usa [SAML SSO](/articles/about-identity-and-access-management-with-saml Se o SAML SSO for usado sem implementação do SCIM, você não terá desprovisionamento automático. Quando as sessões dos integrantes da organização expiram depois que o acesso deles é removido do IdP, eles não podem ser removidos automaticamente da organização. Os tokens autorizados concedem acesso à organização mesmo depois que as respectivas sessões expiram. Para remover o acesso, os administradores da organização podem remover o token autorizado manualmente da organização ou automatizar a remoção com o SCIM. -Estes provedores de identidade são compatíveis com a API de SCIM de {% data variables.product.product_name %} para organizações. Para obter mais informações, consulte [SCIM](/v3/scim/) na documentação de API do {% data variables.product.product_name %}. +Estes provedores de identidade são compatíveis com a API de SCIM de {% data variables.product.product_name %} para organizações. Para obter mais informações, consulte [SCIM](/rest/reference/scim) na documentação de API do {% data variables.product.product_name %}. - Azure AD - Okta - OneLogin diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md index 068c6f3f7a..9e1b5bbc1b 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md @@ -29,7 +29,7 @@ Na barra lateral esquerda do painel, é possível acessar os principais reposit Na seção "All activity" (Todas as atividades) do seu feed de notícias, você pode ver atualizações de outras equipes e repositórios em sua organização. -A seção "All activity" (Todas as atividades) mostra todas as últimas atividades na organização, inclusive atividades em repositórios que você não assina e de pessoas que você não está seguindo. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" and "[Following people](/articles/following-people)." +A seção "All activity" (Todas as atividades) mostra todas as últimas atividades na organização, inclusive atividades em repositórios que você não assina e de pessoas que você não está seguindo. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Inspecionar e não inspecionar repositórios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" e "[Seguindo pessoas](/articles/following-people)." Por exemplo, o feed de notícias da organização mostra atualizações quando alguém na organização: - Cria um branch. @@ -37,8 +37,8 @@ Por exemplo, o feed de notícias da organização mostra atualizações quando a - Envia um comentário de revisão de pull request. - Bifurca um repositório. - Cria uma página wiki. - - Faz push de commits. - - Cria um repositório público. + - Pushes commits.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - Creates a public repository.{% endif %} ### Outras informações diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md index 95eaedc296..43ab8f2afa 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md @@ -1,6 +1,6 @@ --- -title: Adding organization members to a team -intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% if currentVersion == "free-pro-team@latest" %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.' +title: Adicionar integrantes da organização a uma equipe +intro: 'As pessoas com permissões de proprietário ou mantenedor de equipe podem adicionar integrantes da organização às equipes. Pessoas com permissões de proprietário também podem {% if currentVersion == "free-pro-team@latest" %}convidar os não integrantes a juntar-se a {% else %}adicionar não integrantes a {% endif %} uma equipe e à organização.' redirect_from: - /articles/adding-organization-members-to-a-team-early-access-program/ - /articles/adding-organization-members-to-a-team @@ -16,14 +16,13 @@ versions: {% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_members_tab %} -6. Above the list of team members, click **Add a member**. -![Add member button](/assets/images/help/teams/add-member-button.png) +6. Acima da lista de integrantes da equipe, clique em **Adicionar um integrante**. ![Botão Add member (Adicionar integrante)](/assets/images/help/teams/add-member-button.png) {% data reusables.organizations.invite_to_team %} {% data reusables.organizations.review-team-repository-access %} {% if currentVersion == "free-pro-team@latest" %}{% data reusables.organizations.cancel_org_invite %}{% endif %} -### Further reading +### Leia mais -- "[About teams](/articles/about-teams)" -- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" +- "[Sobre equipes](/articles/about-teams)" +- "[Gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md index b89b5fecce..5e6a4b2f68 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md @@ -6,7 +6,7 @@ redirect_from: versions: enterprise-server: '*' github-ae: '*' -permissions: 'Organization owners can add people to an organization.' +permissions: 'Os proprietários da organização podem adicionar pessoas a uma organização.' --- {% if currentVersion != "github-ae@latest" %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md index 55a11392c5..01b0f1aacf 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md @@ -1,19 +1,22 @@ --- -title: Converting an outside collaborator to an organization member -intro: 'If you would like to give an outside collaborator on your organization''s repositories broader permissions within your organization, you can {% if currentVersion == "free-pro-team@latest" %}invite them to become a member of{% else %}make them a member of{% endif %} the organization.' +title: Remover um colaborador externo em integrante da organização +intro: 'Se você quiser conceder a um colaborador externo permissões mais amplas nos repositórios da sua organização dentro de sua organização, você pode {% if currentVersion == "free-pro-team@latest" %} convidá-los a tornar-se um integrante de{% else %}torná-los um integrante da{% endif %} organização.' redirect_from: - /articles/converting-an-outside-collaborator-to-an-organization-member versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: Organization owners can {% if currentVersion == "free-pro-team@latest" %}invite users to join{% else %}add users to{% endif %} an organization. +permissions: Proprietários da organização podem {% if currentVersion == "free-pro-team@latest" %}convidar usuários para juntar-se a{% else %}adicionar usuários a{% endif %} uma organização. --- + {% if currentVersion == "free-pro-team@latest" %} -If your organization is on a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}{% endif %} +Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". +{% data reusables.organizations.org-invite-expiration %}{% endif %} {% if currentVersion != "github-ae@latest" %} -If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users {% if currentVersion == "free-pro-team@latest" %}you invite must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before they can accept the invitation.{% else %}must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization.{% endif %} +Se sua organização [requer integrantes para usar a autenticação em duas etapas](/articles/requiring-two-factor-authentication-in-your-organization), usuários +{% if currentVersion == "free-pro-team@latest" %}você convida deve [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes que eles possam aceitar o convite.{% else %}deve [ativar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de adicioná-la à organização.{% endif %} {% endif %} {% data reusables.profile.access_profile %} @@ -21,9 +24,10 @@ If your organization [requires members to use two-factor authentication](/articl {% data reusables.organizations.people %} {% data reusables.organizations.people_tab_outside_collaborators %} {% if currentVersion == "free-pro-team@latest" %} -5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) +5. À direita do nome do colaborador externo que você deseja que se torne um membro, use o +{% octicon "gear" aria-label="The gear icon" %} menu suspenso e clique em **Convidar para a organização**.![Convidar colaboradores externos para a organização](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) {% else %} -5. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png) +5. À direita do nome do colaborador externo que você deseja que se torne integrante, clique em **Invite to organization** (Convidar para a organização).![Convidar colaboradores externos para a organização](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png) {% endif %} {% data reusables.organizations.choose-to-restore-privileges %} {% data reusables.organizations.choose-user-role-send-invitation %} @@ -31,6 +35,6 @@ If your organization [requires members to use two-factor authentication](/articl {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} {% endif %} -### Further reading +### Leia mais -- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md index 6f7319a611..f753d60535 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md @@ -59,7 +59,7 @@ Você pode desabilitar todos os fluxos de trabalho para uma organização ou def {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png) 1. Clique em **Salvar**. {% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md index 02818ad3ab..542e500331 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md @@ -1,7 +1,7 @@ --- -title: Disabling publication of GitHub Pages sites for your organization -intro: 'You can prevent members of your organization from publishing {% data variables.product.prodname_pages %} sites from repositories in the organization.' -permissions: 'Organization owners can disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +title: Desabilitar a publicação de sites do GitHub Pages para sua organização +intro: 'É possível impedir que os integrantes da sua organização publiquem sites do {% data variables.product.prodname_pages %} em repositórios na organização.' +permissions: 'Os proprietários da organização podem desabilitar a publicação de sites do {% data variables.product.prodname_pages %} em repositórios na organização.' product: '{% data reusables.gated-features.pages %}' versions: free-pro-team: '*' @@ -9,21 +9,19 @@ versions: github-ae: '*' --- -### About restrictions on publication of {% data variables.product.prodname_pages %} sites +### Sobre as restrições na publicação de sites do {% data variables.product.prodname_pages %} -You can control whether members of your organization can publish websites from repositories in your organization using {% data variables.product.prodname_pages %}. For more information about {% data variables.product.prodname_pages %}, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." +Você pode controlar se os integrantes da sua organização podem publicar sites de repositórios na sua organização usando o {% data variables.product.prodname_pages %}. Para obter mais informações sobre {% data variables.product.prodname_pages %}, consulte "[Sobre {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %}. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}Se o administrador do site tiver habilitado Páginas Públicas, os sites de {% endif %}{% data variables.product.prodname_pages %} ficarão disponíveis publicamente na internet, mesmo que o repositório do site seja privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou{% endif %} interno. Para mais informações, consulte {% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}[Configurar {% data variables.product.prodname_pages %} para a sua empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" e{% endif %} "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." -### Disabling publication of {% data variables.product.prodname_pages %} sites +### Desabilitar publicação de sites do {% data variables.product.prodname_pages %} -After you disable publication of {% data variables.product.prodname_pages %} sites, any published site will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/unpublishing-a-github-pages-site)." +Depois de desabilitar a publicação de sites do {% data variables.product.prodname_pages %} , qualquer site publicado permanecerá publicado. Você pode remover manualmente a publicação do site. Para obter mais informações, consulte "[Cancelar a publicação de um site do {% data variables.product.prodname_pages %}](/github/working-with-github-pages/unpublishing-a-github-pages-site)". {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.member-privileges %} -1. Under "Pages creation", unselect **Allow members to publish sites**. - ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png) -1. Click **Save**. - !["Save" button for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png) +1. Em "Criação de páginas", desmarque **Permitir que os integrantes publiquem sites**. ![Caixa de seleção não marcada para a opção "Permitir que os membros publiquem sites"](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png) +1. Clique em **Salvar**. ![Botão "Salvar" para a opção "Permitir que os integrantes publiquem sites"](/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md index e173bbd03a..28819a41c2 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md @@ -3,7 +3,7 @@ title: Proteger sua organização redirect_from: - /articles/preventing-unauthorized-access-to-organization-information/ - /articles/keeping-your-organization-secure -intro: 'Os proprietários de organizações têm vários recursos disponíveis para ajudá-los a proteger seus projetos e dados. If you''re the owner of an organization, you should regularly review your organization''s audit log{% if currentVersion != "github-ae@latest" %}, member 2FA status,{% endif %} and application settings to ensure that no unauthorized or malicious activity has occurred.' +intro: 'Os proprietários de organizações têm vários recursos disponíveis para ajudá-los a proteger seus projetos e dados. Se você for o proprietário de uma organização, você deverá revisar regularmente o log de auditoria da sua organização{% if currentVersion ! "github-ae@latest" %}, status de 2FA do integrante{% endif %} e as configurações do aplicativo para garantir que não ocorra nenhuma atividade não autorizada ou maliciosa.' mapTopic: true versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md index e49e67f95f..6e1d554369 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md @@ -18,7 +18,7 @@ Quando se solicita automaticamente que os proprietários de códigos façam uma ### Encaminhar algoritmos -Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. +Escolha as atribuições de revisão de código e atribua os revisores automaticamente com base em um dos dois algoritmos possíveis. O algoritmo round robin (rotativo) escolhe os revisores com base em quem recebeu a solicitação de revisão menos recente e tem o foco em alternar entre todos os integrantes da equipe, independentemente do número de avaliações pendentes que possuem atualmente. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md index e5a98a15fe..8e41a504ae 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md @@ -1,6 +1,7 @@ --- title: Gerenciar a varredura de segredos para sua organização intro: 'Você pode controlar quais repositórios no {% data variables.product.product_name %} da organização fará a varredura dos segredos.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'Os proprietários da organização podem gerenciar {% data variables.product.prodname_secret_scanning %} para os repositórios na organização.' versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md index 02987a0fd4..684f92dbba 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -14,7 +14,7 @@ Quando um integrante da sua organização cria um novo repositório na sua organ {% data reusables.branches.change-default-branch %} -If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +Se um proprietário da empresa tiver aplicado uma política para o nome do branch padrão para sua empresa, você não poderá definir um nome do branch padrão para sua organização. Em vez disso, você pode alterar o branch padrão para repositórios individuais. Para mais informações, consulte {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de gerenciamento do repositório na sua empresa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)"{% else %}[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)"{% endif %} e "[Alterar o branch padrão](/github/administering-a-repository/changing-the-default-branch)". ### Definir o nome do branch-padrão diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md index 511d676ff7..1a56221145 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md @@ -1,10 +1,10 @@ --- -title: Gerenciar a política de bifurcação da sua organização +title: Managing the forking policy for your organization intro: 'You can can allow or prevent the forking of any private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories owned by your organization.' redirect_from: - /articles/allowing-people-to-fork-private-repositories-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization -permissions: Os proprietários da organização podem gerenciar a política de bifurcação de uma organização. +permissions: Organization owners can manage the forking policy for an organization. versions: free-pro-team: '*' enterprise-server: '*' @@ -13,7 +13,7 @@ versions: By default, new organizations are configured to disallow the forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories. -If you allow forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository. Para obter mais informações, consulte "[Gerenciar a política de bifurcação do seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". +If you allow forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% data reusables.organizations.internal-repos-enterprise %} @@ -21,10 +21,11 @@ If you allow forking of private{% if currentVersion == "free-pro-team@latest" or {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.member-privileges %} -5. Em "Bifurcação do repositório", selecione **Permitir bifurcação de repositórios privados** ou **Permitir bifurcação de repositórios internos e privados**. ![Caixa de seleção para permitir ou proibir a bifurcação na organização](/assets/images/help/repository/allow-disable-forking-organization.png) -6. Clique em **Salvar**. +5. Under "Repository forking", select **Allow forking of private repositories** or **Allow forking of private and internal repositories**. + ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png) +6. Click **Save**. -### Leia mais +### Further reading -- "[Sobre bifurcações](/articles/about-forks)" -- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" +- "[About forks](/articles/about-forks)" +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 56be0018d7..df986ffaf5 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -64,7 +64,7 @@ Os integrantes da organização podem ter funções de *proprietário*{% if curr | Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %} | **X** | | | | Listar aplicativos no {% data variables.product.prodname_marketplace %} | **X** | | |{% if currentVersion != "github-ae@latest" %} | Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização | **X** | | | -| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | |{% endif %} +| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | |{% endif %} | [Gerenciar a política de bifurcação](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | | [Limitar a atividade em repositórios públicos na organização](/articles/limiting-interactions-in-your-organization) | **X** | | | | Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | | diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md index 8824fc5faf..b878a56111 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: 'Organization owners can reinstate a former member of an organization.' +permissions: 'Os proprietários da organização podem restabelecer um antigo integrante de uma organização.' --- -### About member reinstatement +### Sobre a reintegração de integrantes -If you [remove a user from your organization](/articles/removing-a-member-from-your-organization){% if currentVersion == "github-ae@latest" %} or{% else %},{% endif %} [convert an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator){% if currentVersion != "github-ae@latest" %}, or a user is removed from your organization because you've [required members and outside collaborators to enable two-factor authentication (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, the user's access privileges and settings are saved for three months. Você pode restaurar os privilégios do usuário se você {% if currentVersion =="free-pro-team@latest" %}convidá-los{% else %}adicioná-los{% endif %} à organização nesse período de tempo. +Se você [remover um usuário da sua organização](/articles/removing-a-member-from-your-organization){% if currentVersion == "github-ae@latest" %} ou{% else %},{% endif %} [converter um integrante da organização em um colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator){% if currentVersion ! "github-ae@latest" %}, ou um usuário foi removido da sua organização porque você [exigiu que os integrantes e colaboradores externos habilitassem a autenticação de dois fatores (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, os privilégios e configurações do usuário ficarão salvos por três meses. Você pode restaurar os privilégios do usuário se você {% if currentVersion =="free-pro-team@latest" %}convidá-los{% else %}adicioná-los{% endif %} à organização nesse período de tempo. {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md index 3608669ae5..7e7b23dfe8 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -1,6 +1,6 @@ --- -title: Reinstating a former outside collaborator's access to your organization -intro: "You can reinstate a former outside collaborator's access permissions for organization repositories, forks, and settings." +title: Restabelecer o acesso de um ex-colaborador externo à organização +intro: "É possível restabelecer as permissões de acesso de um ex-colaborador externo para repositórios, forks e configurações da organização." redirect_from: - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization @@ -10,25 +10,25 @@ versions: github-ae: '*' --- -When an outside collaborator's access to your organization's private repositories is removed, the user's access privileges and settings are saved for three months. You can restore the user's privileges if you {% if currentVersion == "free-pro-team@latest" %}invite{% else %}add{% endif %} them back to the organization within that time frame. +Quando o acesso de um colaborador externo aos repositórios privados da sua organização é removido, os privilégios e configurações de acesso do usuário são salvos por três meses. Você pode restaurar os privilégios do usuário se você {% if currentVersion == "free-pro-team@latest" %}convidá-los{% else %}add{% endif %} para a organização nesse período de tempo. {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} -When you reinstate a former outside collaborator, you can restore: - - The user's former access to organization repositories - - Any private forks of repositories owned by the organization - - Membership in the organization's teams - - Previous access and permissions for the organization's repositories - - Stars for organization repositories - - Issue assignments in the organization - - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity) +Ao restabelecer um ex-colaborador externo, você pode restaurar: + - O acesso anterior do usuário aos repositórios da organização + - As bifurcações privadas de repositórios de propriedade da organização + - A associação nas equipes da organização + - Os acessos e permissões anteriores nos repositórios da organização + - As estrelas dos repositórios da organização + - As atribuições de problemas na organização + - As assinaturas do repositório (configurações de notificação para inspecionar, não inspecionar ou ignorar as atividades de um repositório) {% tip %} -**Tips**: - - Only organization owners can reinstate outside collaborators' access to an organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." - - The reinstating a member flow on {% data variables.product.product_location %} may use the term "member" to describe reinstating an outside collaborator but if you reinstate this person and keep their previous privileges, they will only have their previous [outside collaborator permissions](/articles/permission-levels-for-an-organization/#outside-collaborators).{% if currentVersion == "free-pro-team@latest" %} - - If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."{% endif %} +**Dicas**: + - Somente proprietários da organização podem restabelecer o acesso de um colaborador externo à organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization)". + - O restabelecimento de um fluxo de integrante em {% data variables.product.product_location %} pode usar o termo "integrante" para descrever o restabelecimento de um colaborador externo. No entanto, se você restabelecer esta pessoa e mantiver seus privilégios anteriores, ela terá apenas suas [permissões de colaborador externo](/articles/permission-levels-for-an-organization/#outside-collaborators). {% if currentVersion == "free-pro-team@latest" %} + - Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)."{% endif %} {% endtip %} @@ -38,37 +38,35 @@ When you reinstate a former outside collaborator, you can restore: {% data reusables.organizations.invite_member_from_people_tab %} {% data reusables.organizations.reinstate-user-type-username %} {% if currentVersion == "free-pro-team@latest" %} -6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Invite and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Invite and start fresh**. +6. Escolha restaurar os privilégios anteriores do colaborador externo na organização clicando em **Invite and reinstate** (Convidar e restabelecer) ou escolha apagar os privilégios anteriores e definir novas permissões de acesso clicando em **Invite and start fresh** (Convidar e começar do zero). {% warning %} - **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Invite and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Invite and reinstate** instead. Once this person accepts the invitation, you can convert them to an organization member by [inviting them to join the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). + **Aviso:** se quiser converter um colaborador externo em um integrante da organização, selecione **Invite and start fresh** (Convidar e começar do zero) e escolha uma nova função para a pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para converter o ex-colaborador externo em um integrante da organização *e* manter as bifurcações privadas dele, selecione **Invite and reinstate** (Convidar e restabelecer). Quando a pessoa aceitar o convite, você poderá fazer a conversão [convidando a pessoa para participar da organização como um integrante](/articles/converting-an-outside-collaborator-to-an-organization-member). {% endwarning %} - ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) + ![Escolher se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) {% else %} -6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Add and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Add and start fresh**. +6. Escolha restaurar os privilégios anteriores do colaborador externo na organização clicando em **Add and reinstate** (Adicionar e restabelecer) ou escolha apagar os privilégios anteriores e definir novas permissões de acesso clicando em **Add and start fresh** (Adicionar e começar do zero). {% warning %} - **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Add and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Add and reinstate** instead. Then, you can convert them to an organization member by [adding them to the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). + **Aviso:** se quiser converter um colaborador externo em um integrante da organização, selecione **Add and start fresh** (Adicionar e começar do zero) e escolha uma nova função para a pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para converter o ex-colaborador externo em um integrante da organização *e* manter as bifurcações privadas dele, selecione **Add and reinstate** (Adicionar e restabelecer). Em seguida, converta-o em integrante da organização [adicionando ele à organização como um integrante](/articles/converting-an-outside-collaborator-to-an-organization-member). {% endwarning %} - ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) + ![Escolher se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Send invitation**. - ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png) +7. Se você apagou os privilégios anteriores de um ex-colaborador externo, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Send invitation** (Enviar convite). ![Opções Role and team (Função e equipe) e botão send invitation (enviar convite)](/assets/images/help/organizations/add-role-send-invitation.png) {% else %} -7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Add member**. - ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png) +7. Se você apagou os privilégios anteriores de um ex-colaborador externo, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Add member** (Adicionar integrante). ![Opções Role and team (Função e equipe) e botão add member (adicionar integrante)](/assets/images/help/organizations/add-role-add-member.png) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -8. The invited person will receive an email inviting them to the organization. They will need to accept the invitation before becoming an outside collaborator in the organization. {% data reusables.organizations.cancel_org_invite %} +8. A pessoa convidada receberá um e-mail com um convite para participar da organização. Ela precisará aceitar o convite antes de se tornar um colaborador externo na organização. {% data reusables.organizations.cancel_org_invite %} {% endif %} -### Further Reading +### Leia mais -- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" +- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 5addfe9716..0eec265fd8 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -43,74 +43,78 @@ Além de gerenciar as configurações da organização, os proprietários da org ### Acesso ao repositório de cada nível de permissão -| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:| -| Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | -| Bifurcar os repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | -| Editar e excluir seus próprios comentários | **X** | **X** | **X** | **X** | **X** | -| Criar problemas | **X** | **X** | **X** | **X** | **X** | -| Fechar os problemas que eles criaram | **X** | **X** | **X** | **X** | **X** | -| Reabrir problemas que eles fecharam | **X** | **X** | **X** | **X** | **X** | -| Ter um problema atribuído a eles | **X** | **X** | **X** | **X** | **X** | -| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **X** | **X** | **X** | **X** | **X** | -| Enviar revisões em pull requests | **X** | **X** | **X** | **X** | **X** | -| Exibir as versões publicadas | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Editar wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Denunciar conteúdo abusivo ou spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Aplicar etiquetas | | **X** | **X** | **X** | **X** | -| Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** | -| Aplicar marcos | | **X** | **X** | **X** | **X** | -| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Solicitar [revisões de pull requests](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe | | | **X** | **X** | **X** | -| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas | | | **X** | **X** | **X** | -| [Ocultar comentários de qualquer usuário](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Bloquear conversas](/articles/locking-conversations) | | | **X** | **X** | **X** | -| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **X** | **X** | **X** | -| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Marcar uma pull request de rascunho como pronta para revisão](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [Converter um pull request em rascunho](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| Enviar revisões que afetam a capacidade de merge de uma pull request | | | **X** | **X** | **X** | -| [Aplicar alterações sugeridas](/articles/incorporating-feedback-in-your-pull-request) a pull requests | | | **X** | **X** | **X** | -| Criar [verificações de status](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| Criar e editar versões | | | **X** | **X** | **X** | -| Exibir versões de rascunho | | | **X** | **X** | **X** | -| Editar a descrição de um repositório | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Excluir pacotes](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Habilitar wikis e restringir editores de wiki | | | | **X** | **X** | -| Habilitar quadros de projeto | | | | **X** | **X** | -| Configurar [merges de pull request](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **X** | **X** | -| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Limitar [interações em um repositório](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} -| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **X** | -| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **X** | -| [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **X** | -| Adicionar um repositório a uma equipe (consulte "[Gerenciar o acesso da equipe ao repositório de uma organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obter informações) | | | | | **X** | -| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **X** | -| Alterar as configurações do repositório | | | | | **X** | -| Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **X** | -| Editar o branch padrão do repositório | | | | | **X** | -| Gerenciar webhooks e chaves de implantação | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Habilitar o gráfico de dependências](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) em um repositório privado | | | | | **X** | -| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | -| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designar outras pessoas ou equipes para receber {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) para as dependências vulneráveis | | | | | **X** | -| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}| Crie [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %} -| [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Arquivar repositórios](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} -| Criar referências de link automático para recursos externos, como JIRA ou Zendesk (consulte "[Configurar links automáticos para apontar para recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | +| Bifurcar os repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | +| Editar e excluir seus próprios comentários | **X** | **X** | **X** | **X** | **X** | +| Criar problemas | **X** | **X** | **X** | **X** | **X** | +| Fechar os problemas que eles criaram | **X** | **X** | **X** | **X** | **X** | +| Reabrir problemas que eles fecharam | **X** | **X** | **X** | **X** | **X** | +| Ter um problema atribuído a eles | **X** | **X** | **X** | **X** | **X** | +| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **X** | **X** | **X** | **X** | **X** | +| Enviar revisões em pull requests | **X** | **X** | **X** | **X** | **X** | +| Exibir as versões publicadas | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| Editar wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Denunciar conteúdo abusivo ou spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| Aplicar etiquetas | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** | +| Aplicar marcos | | **X** | **X** | **X** | **X** | +| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Solicitar [revisões de pull requests](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe | | | **X** | **X** | **X** | +| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas | | | **X** | **X** | **X** | +| [Ocultar comentários de qualquer usuário](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Bloquear conversas](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **X** | **X** | **X** | +| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Marcar uma pull request de rascunho como pronta para revisão](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [Converter um pull request em rascunho](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| Enviar revisões que afetam a capacidade de merge de uma pull request | | | **X** | **X** | **X** | +| [Aplicar alterações sugeridas](/articles/incorporating-feedback-in-your-pull-request) a pull requests | | | **X** | **X** | **X** | +| Criar [verificações de status](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| Criar e editar versões | | | **X** | **X** | **X** | +| Exibir versões de rascunho | | | **X** | **X** | **X** | +| Editar a descrição de um repositório | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Excluir pacotes](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Habilitar wikis e restringir editores de wiki | | | | **X** | **X** | +| Habilitar quadros de projeto | | | | **X** | **X** | +| Configurar [merges de pull request](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **X** | **X** | +| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Limitar [interações em um repositório](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} +| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **X** | +| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **X** | +| [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **X** | +| Adicionar um repositório a uma equipe (consulte "[Gerenciar o acesso da equipe ao repositório de uma organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obter informações) | | | | | **X** | +| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **X** | +| Alterar as configurações do repositório | | | | | **X** | +| Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **X** | +| Editar o branch padrão do repositório | | | | | **X** | +| Gerenciar webhooks e chaves de implantação | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Habilitar o gráfico de dependências](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) em um repositório privado | | | | | **X** | +| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | +| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designar outras pessoas ou equipes para receber {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) para as dependências vulneráveis | | | | | **X** | +| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | +| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [Lista, descarta e exclui alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %} +| [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Arquivar repositórios](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} +| Criar referências de link automático para recursos externos, como JIRA ou Zendesk (consulte "[Configurar links automáticos para apontar para recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md index 92ff459f40..fe8b27ba67 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md @@ -13,7 +13,7 @@ Você pode escolher se os integrantes podem criar repositórios na sua organiza Os proprietários da organização sempre podem criar qualquer tipo de repositório. -{% if currentVersion == "free-pro-team@latest" %}Os proprietários da empresa{% else %}administradores do site{% endif %} podem restringir as opções disponíveis para você para a política de criação de repositório da sua organização. For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account)."{% else %}"[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Os proprietários da empresa{% else %}administradores do site{% endif %} podem restringir as opções disponíveis para você para a política de criação de repositório da sua organização. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de gerenciamento do repositório na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account).{% else %}"[Restringir a criação do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %} {% warning %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md index bc2c3ceed2..15f6e26b56 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -Você pode restringir a capacidade de alterar a visibilidade do repositório aos proprietários da organização ou permitir que integrantes com privilégios de administrador em um repositório também alterem a visibilidade do repositório. +You can restrict the ability to change repository visibility to organization owners only, or allow members with admin privileges for a repository to also change visibility. {% warning %} @@ -24,3 +24,7 @@ Você pode restringir a capacidade de alterar a visibilidade do repositório aos {% data reusables.organizations.member-privileges %} 5. Em "Repository visibility change" (Alteração da visibilidade do repositório), desmarque a opção **Allow members to change repository visibilities for this organization** (Permitir que os integrantes alterem a visibilidade dos repositórios nesta organização). ![Caixa de seleção para permitir que os integrantes alterem a visibilidade dos repositórios](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) 6. Clique em **Salvar**. + +### Leia mais + +- "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 61497be9a9..1c3a69af50 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -1,6 +1,7 @@ --- title: Reviewing the audit log for your organization intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/reviewing-the-audit-log-for-your-organization versions: @@ -11,7 +12,7 @@ versions: ### Accessing the audit log -The audit log lists actions performed within the last 90 days. Only owners can access an organization's audit log. +The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} @@ -26,73 +27,110 @@ The audit log lists actions performed within the last 90 days. Only owners can a To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories: -| Category Name | Description +| Category name | Description |------------------|-------------------{% if currentVersion == "free-pro-team@latest" %} -| `account` | Contains all activities related to your organization account.{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `billing` | Contains all activities related to your organization's billing.{% endif %} -| `discussion_post` | Contains all activities related to discussions posted to a team page. -| `discussion_post_reply` | Contains all activities related to replies to discussions posted to a team page. -| `hook` | Contains all activities related to webhooks. -| `integration_installation_request` | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% if currentVersion == "free-pro-team@latest" %} -| `marketplace_agreement_signature` | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. -| `marketplace_listing` | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `members_can_create_pages` | Contains all activities related to disabling the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." | {% endif %} -| `org` | Contains all activities related to organization membership{% if currentVersion == "free-pro-team@latest" %} -| `org_credential_authorization` | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| `organization_label` | Contains all activities related to default labels for repositories in your organization.{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `payment_method` | Contains all activities related to how your organization pays for GitHub.{% endif %} -| `profile_picture` | Contains all activities related to your organization's profile picture. -| `project` | Contains all activities related to project boards. -| `protected_branch` | Contains all activities related to protected branches. -| `repo` | Contains all activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %} -| `repository_content_analysis` | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). -| `repository_dependency_graph` | Contains all activities related to [enabling or disabling the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository).{% endif %}{% if currentVersion != "github-ae@latest" %} -| `repository_vulnerability_alert` | Contains all activities related to [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `sponsors` | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `team` | Contains all activities related to teams in your organization.{% endif %} -| `team_discussions` | Contains activities related to managing team discussions for an organization. +| [`account`](#account-category-actions) | Contains all activities related to your organization account. +| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization. +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. +| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page. +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page. +| [`hook`](#hook-category-actions) | Contains all activities related to webhooks. +| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | +| [`issue`](#issue-category-actions) | Contains activities related to deleting an issue. {% if currentVersion == "free-pro-team@latest" %} +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to disabling the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." | {% endif %} +| [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. {% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. +| [`project`](#project-category-actions) | Contains all activities related to project boards. +| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. +| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| [`team`](#team-category-actions) | Contains all activities related to teams in your organization.{% endif %} +| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization. You can search for specific sets of actions using these terms. For example: * `action:team` finds all events grouped within the team category. * `-action:hook` excludes all events in the webhook category. -Each category has a set of associated events that you can filter on. For example: +Each category has a set of associated actions that you can filter on. For example: * `action:team.create` finds all events where a team was created. * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered. -This list describes the available categories and associated events: +#### Search based on time of action -{% if currentVersion == "free-pro-team@latest" %}- [The `account` category](#the-account-category) -- [The `billing` category](#the-billing-category){% endif %} -- [The `discussion_post` category](#the-discussion_post-category) -- [The `discussion_post_reply` category](#the-discussion_post_reply-category) -- [The `hook` category](#the-hook-category) -- [The `integration_installation_request` category](#the-integration_installation_request-category) -- [The `issue` category](#the-issue-category){% if currentVersion == "free-pro-team@latest" %} -- [The `marketplace_agreement_signature` category](#the-marketplace_agreement_signature-category) -- [The `marketplace_listing` category](#the-marketplace_listing-category){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -- [The `members_can_create_pages` category](#the-members_can_create_pages-category){% endif %} -- [The `org` category](#the-org-category){% if currentVersion == "free-pro-team@latest" %} -- [The `org_credential_authorization` category](#the-org_credential_authorization-category){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -- [The `organization_label` category](#the-organization_label-category){% endif %} -- [The `oauth_application` category](#the-oauth_application-category){% if currentVersion == "free-pro-team@latest" %} -- [The `payment_method` category](#the-payment_method-category){% endif %} -- [The `profile_picture` category](#the-profile_picture-category) -- [The `project` category](#the-project-category) -- [The `protected_branch` category](#the-protected_branch-category) -- [The `repo` category](#the-repo-category){% if currentVersion == "free-pro-team@latest" %} -- [The `repository_content_analysis` category](#the-repository_content_analysis-category) -- [The `repository_dependency_graph` category](#the-repository_dependency_graph-category){% endif %}{% if currentVersion != "github-ae@latest" %} -- [The `repository_vulnerability_alert` category](#the-repository_vulnerability_alert-category){% endif %}{% if currentVersion == "free-pro-team@latest" %} -- [The `sponsors` category](#the-sponsors-category){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -- [The `team` category](#the-team-category){% endif %} -- [The `team_discussions` category](#the-team_discussions-category) +Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} For example: + + * `created:2014-07-08` finds all events that occurred on July 8th, 2014. + * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. + * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. + * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. + +The audit log contains data for the past 90 days, but you can use the `created` qualifier to search for events earlier than that. + +#### Search based on location + +Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example: + + * `country:de` finds all events that occurred in Germany. + * `country:Mexico` finds all events that occurred in Mexico. + * `country:"United States"` all finds events that occurred in the United States. + +{% if currentVersion == "free-pro-team@latest" %} +### Exporting the audit log + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### Using the Audit log API + +{% note %} + +**Note**: The Audit log API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +To ensure a secure IP and maintain compliance for your organization, you can use the Audit log API to keep copies of your audit log data and monitor: +* Access to your organization or repository settings. +* Changes in permissions. +* Added or removed users in an organization, repository, or team. +* Users being promoted to admin. +* Changes to permissions of a GitHub App. + +The GraphQL response can include data for up to 90 to 120 days. + +For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)." + +### Audit log actions + +An overview of some of the most common actions that are recorded as events in the audit log. {% if currentVersion == "free-pro-team@latest" %} -##### The `account` category +#### `account` category actions | Action | Description |------------------|------------------- @@ -101,30 +139,81 @@ This list describes the available categories and associated events: | `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). | `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/). -##### The `billing` category +#### `advisory_credit` category actions + +| Action | Description +|------------------|------------------- +| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." +| `create` | Triggered when the administrator of a security advisory adds someone to the credit section. +| `decline` | Triggered when someone declines credit for a security advisory. +| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. + +#### `billing` category actions | Action | Description |------------------|------------------- | `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). | `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes. +#### `dependabot_alerts` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. + +#### `dependabot_alerts_new_repos` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enbles {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. + +#### `dependabot_security_updates` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. + +#### `dependabot_security_updates_new_repos` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. + +#### `dependency_graph` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables the dependency graph for all existing repositories. + +#### `dependency_graph_new_repos` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories. + {% endif %} -##### The `discussion_post` category +#### `discussion_post` category actions | Action | Description |------------------|------------------- | `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). -##### The `discussion_post_reply` category +#### `discussion_post_reply` category actions | Action | Description |------------------|------------------- | `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). -##### The `hook` category +#### `hook` category actions | Action | Description |------------------|------------------- @@ -133,14 +222,14 @@ This list describes the available categories and associated events: | `destroy` | Triggered when an existing hook was removed from a repository. | `events_changed` | Triggered when the events on a hook have been altered. -##### The `integration_installation_request` category +#### `integration_installation_request` category actions | Action | Description |------------------|------------------- | `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. | `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. -##### The `issue` category +#### `issue` category actions | Action | Description |------------------|------------------- @@ -148,13 +237,13 @@ This list describes the available categories and associated events: {% if currentVersion == "free-pro-team@latest" %} -##### The `marketplace_agreement_signature` category +#### `marketplace_agreement_signature` category actions | Action | Description |------------------|------------------- | `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. -##### The `marketplace_listing` category +#### `marketplace_listing` category actions | Action | Description |------------------|------------------- @@ -168,7 +257,7 @@ This list describes the available categories and associated events: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -##### The `members_can_create_pages` category +#### `members_can_create_pages` category actions For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." @@ -179,7 +268,7 @@ For more information, see "[Restricting publication of {% data variables.product {% endif %} -##### The `org` category +#### `org` category actions | Action | Description |------------------|-------------------{% if currentVersion == "free-pro-team@latest"%} @@ -222,7 +311,7 @@ For more information, see "[Restricting publication of {% data variables.product | `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### The `org_credential_authorization` category +#### `org_credential_authorization` category actions | Action | Description |------------------|------------------- @@ -233,7 +322,7 @@ For more information, see "[Restricting publication of {% data variables.product {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -##### The `organization_label` category +#### `organization_label` category actions | Action | Description |------------------|------------------- @@ -243,7 +332,7 @@ For more information, see "[Restricting publication of {% data variables.product {% endif %} -##### The `oauth_application` category +#### `oauth_application` category actions | Action | Description |------------------|------------------- @@ -255,7 +344,7 @@ For more information, see "[Restricting publication of {% data variables.product {% if currentVersion == "free-pro-team@latest" %} -##### The `payment_method` category +#### `payment_method` category actions | Action | Description |------------------|------------------- @@ -265,12 +354,12 @@ For more information, see "[Restricting publication of {% data variables.product {% endif %} -##### The `profile_picture` category +#### `profile_picture` category actions | Action | Description |------------------|------------------- | update | Triggered when you set or update your organization's profile picture. -##### The `project` category +#### `project` category actions | Action | Description |--------------------|--------------------- @@ -284,7 +373,7 @@ For more information, see "[Restricting publication of {% data variables.product | `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. | | `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.| -##### The `protected_branch` category +#### `protected_branch` category actions | Action | Description |--------------------|--------------------- @@ -304,14 +393,14 @@ For more information, see "[Restricting publication of {% data variables.product | `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. {% endif %} -##### The `repo` category +#### `repo` category actions | Action | Description |------------------|------------------- -| `access` | Triggered when a repository owned by an organization is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa). +| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). | `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. -| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} | `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). @@ -334,34 +423,80 @@ For more information, see "[Restricting publication of {% data variables.product {% if currentVersion == "free-pro-team@latest" %} -##### The `repository_content_analysis` category +#### `repository_advisory` category actions + +| Action | Description +|------------------|------------------- +| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. +| `open` | Triggered when someone opens a draft security advisory. +| `publish` | Triggered when someone publishes a security advisory. +| `reopen` | Triggered when someone reopens as draft security advisory. +| `update` | Triggered when someone edits a draft or published security advisory. + +#### `repository_content_analysis` category actions | Action | Description |------------------|------------------- | `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). -##### The `repository_dependency_graph` category +{% endif %}{% if currentVersion != "github-ae@latest" %} + +#### `repository_dependency_graph` category actions | Action | Description |------------------|------------------- -| `enable` | Triggered when a repository owner or person with admin access to the repository [enables the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository). -| `disable` | Triggered when a repository owner or person with admin access to the repository [disables the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository). +| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. -{% endif %} -{% if currentVersion != "github-ae@latest" %} -##### The `repository_vulnerability_alert` category +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### `repository_secret_scanning` category actions | Action | Description |------------------|------------------- -| `create` | Triggered when {% data variables.product.product_name %} creates a [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a vulnerable dependency](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a particular repository. -| `resolve` | Triggered when someone with write access to a repository [pushes changes to update and resolve a vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a project dependency. -| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency.{% if currentVersion == "free-pro-team@latest" %} -| `authorized_users_teams` | Triggered when an organization owner or a member with admin permissions to the repository [updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-dependabot-alerts) for vulnerable dependencies in the repository.{% endif %} +| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### `repository_vulnerability_alert` category actions + +| Action | Description +|------------------|------------------- +| `create` | Triggered when {% data variables.product.product_name %} creates a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. +| `resolve` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### `repository_vulnerability_alerts` category actions + +| Action | Description +|------------------|------------------- +| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. +| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}. + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### `secret_scanning` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when an organization owner enables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. + +#### `secret_scanning_new_repos` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when an organization owner enables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. + {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### The `sponsors` category +#### `sponsors` category actions | Action | Description |------------------|------------------- @@ -370,7 +505,7 @@ For more information, see "[Restricting publication of {% data variables.product {% endif %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -##### The `team` category +#### `team` category actions | Action | Description |------------------|------------------- @@ -384,60 +519,13 @@ For more information, see "[Restricting publication of {% data variables.product | `remove_repository` | Triggered when a repository is no longer under a team's control. {% endif %} -##### The `team_discussions` category +#### `team_discussions` category actions | Action | Description |---|---| | `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." | `enable` | Triggered when an organization owner enables team discussions for an organization. -#### Search based on time of action - -Use the `created` qualifier to filter actions in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} - -{% data reusables.search.date_gt_lt %} For example: - - * `created:2014-07-08` finds all events that occurred on July 8th, 2014. - * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. - * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. - * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. - -The audit log contains data for the past 90 days, but you can use the `created` qualifier to search for events earlier than that. - -#### Search based on location - -Using the qualifier `country`, you can filter actions in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example: - - * `country:de` finds all events that occurred in Germany. - * `country:Mexico` finds all events that occurred in Mexico. - * `country:"United States"` all finds events that occurred in the United States. - -{% if currentVersion == "free-pro-team@latest" %} -### Exporting the audit log - -{% data reusables.audit_log.export-log %} -{% data reusables.audit_log.exported-log-keys-and-values %} -{% endif %} - -### Using the Audit log API - -{% note %} - -**Note**: The Audit log API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} - -{% endnote %} - -To ensure a secure IP and maintain compliance for your organization, you can use the Audit log API to keep copies of your audit log data and monitor: -* Access to your organization or repository settings. -* Changes in permissions. -* Added or removed users in an organization, repository, or team. -* Users being promoted to admin. -* Changes to permissions of a GitHub App. - -The GraphQL response can include data for up to 90 to 120 days. - -For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)." - ### Further reading - "[Keeping your organization secure](/articles/keeping-your-organization-secure)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations.md index ac62de20d3..e7e526062a 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations.md @@ -1,6 +1,6 @@ --- -title: Reviewing your organization's installed integrations -intro: You can review the permission levels for your organization's installed integrations and configure each integration's access to organization repositories. +title: Revisar as integrações instaladas da organização +intro: Você pode revisar os níveis de permissão das integrações instaladas da organização e configurar o acesso de cada integração aos repositórios da organização. redirect_from: - /articles/reviewing-your-organization-s-installed-integrations - /articles/reviewing-your-organizations-installed-integrations @@ -13,12 +13,9 @@ versions: {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} -4. In the left sidebar, click **Installed {% data variables.product.prodname_github_app %}s**. - ![Installed {% data variables.product.prodname_github_app %}s tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png) -5. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. - ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png) -6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. - ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png) - - To give the {% data variables.product.prodname_github_app %} access to all of your organization's repositories, select **All repositories**. - - To choose specific repositories to give the application access to, select **Only select repositories**, then type a repository name. -7. Click **Save**. +4. Na barra lateral esquerda, clique em **Installed {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s instalados). ![Guia Installed {% data variables.product.prodname_github_app %}s ({% data variables.product.prodname_github_app %}s instalados) na barra lateral de configurações da organização](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. Próximo do {% data variables.product.prodname_github_app %} que deseja revisar, clique em **Configure** (Configurar). ![Botão Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png) +6. Revise o acesso ao repositório e as permissões de {% data variables.product.prodname_github_app %}. ![Opção para fornecer ao {% data variables.product.prodname_github_app %} acesso a todos os repositórios ou a repositórios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png) + - Para fornecer acesso ao {% data variables.product.prodname_github_app %} em todos os repositórios da organização, selecione **All repositories** (Todos os repositórios). + - Para selecionar repositórios específicos para fornecer acesso ao aplicativo, selecione **Only select repositories** (Somente os repositórios selecionados) e insira o nome do repositório. +7. Clique em **Salvar**. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md index e70f55bc64..dcd4cbd05b 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md @@ -1,6 +1,6 @@ --- -title: Setting permissions for adding outside collaborators -intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.' +title: Configurar permissões para adicionar colaboradores externos +intro: 'Para proteger os dados da organização e o o número de licenças pagas usadas, você pode permitir que somente proprietários convidem colaboradores externos para os repositórios da organização.' product: '{% data reusables.gated-features.restict-add-collaborator %}' redirect_from: - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories/ @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -Organization owners, and members with admin privileges for a repository, can invite outside collaborators to work on the repository. You can also restrict outside collaborator invite permissions to only organization owners. +Os proprietários da organização e integrantes com privilégios de administrador para um repositório podem convidar colaboradores externos para trabalhar no repositório. Você também pode restringir as permissões de convites de colaboradores externos para apenas proprietários de organizações. {% data reusables.organizations.outside-collaborators-use-seats %} @@ -19,7 +19,6 @@ Organization owners, and members with admin privileges for a repository, can inv {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.member-privileges %} -5. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} - ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %} - ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %} -6. Click **Save**. +5. Em "Convites para o repositório", selecione **Permitir que os integrantes convidem colaboradores externos para repositórios desta organização**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %} +![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %} +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 5346d5e1e0..424cab5098 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -23,7 +23,7 @@ As equipes principais não podem sincronizar com grupos de IdP. Se a equipe que Para gerenciar o acesso ao repositório de qualquer equipe do {% data variables.product.prodname_dotcom %} incluindo equipes conectadas a um grupo de IdP, você deve fazer alterações com o {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)" e "[Gerenciar o acesso da equipe ao repositório de uma organização](/articles/managing-team-access-to-an-organization-repository)". -Você também pode gerenciar a sincronização de equipe com a API. Para obter mais informações, consulte "[Sincronização de equipe](/v3/teams/team_sync/)". +Você também pode gerenciar a sincronização de equipe com a API. Para obter mais informações, consulte "[Sincronização de equipe](/rest/reference/teams#team-sync)". ### Requisitos para integrantes de equipes sincronizadas diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md index 2b0bdf7542..b2362a95c5 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md @@ -36,7 +36,7 @@ Com as informações de dependência, é possível visualizar vulnerabilidades, 3. No nome da organização, clique em {% octicon "graph" aria-label="The bar graph icon" %} **Insights** (Informações). ![Guia Insights (Informações) na principal barra de navegação da organização](/assets/images/help/organizations/org-nav-insights-tab.png) 4. Clique em **Dependencies** (Dependências) para exibir as que pertencem a esta organização. ![Guia Dependencies (Dependências) na principal barra de navegação da organização](/assets/images/help/organizations/org-insights-dependencies-tab.png) 5. Para exibir informações de dependência para todas as suas organizações do {% data variables.product.prodname_ghe_cloud %}, clique em **My organizations** (Minhas organizações). ![Botão My organizations (Minhas organizações) na guia Dependencies (Dependências)](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) -6. Você pode clicar nos resultados dos gráficos **Consultorias de segurança abertas** e **Licenças** para filtrar por um status de vulnerabilidade, uma licença ou uma combinação dos dois. ![My organizations vulnerabilities and licenses graphs](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +6. Você pode clicar nos resultados dos gráficos **Consultorias de segurança abertas** e **Licenças** para filtrar por um status de vulnerabilidade, uma licença ou uma combinação dos dois. ![Gráficos de "vulnerabilidades das minhas organizações"](/assets/images/help/organizations/org-insights-dependencies-graphs.png) 7. Também pode clicar em {% octicon "package" aria-label="The package icon" %} **Dependents** (Dependentes) ao lado de cada vulnerabilidade para ver quais dependentes na organização estão usando cada biblioteca. ![Dependentes vulneráveis em My organizations (Minhas organizações)](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md index 4855d718d6..279c02212a 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -20,13 +20,13 @@ Uma conta corporativa permite que você gerencie múltiplas organizações {% da - Segurança (logon único, autenticação de dois fatores) - Solicitações e compartilhamento de pacote de suporte com {% data variables.contact.enterprise_support %} -{% data reusables.enterprise-accounts.enterprise-accounts-billing %} +{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." Para obter mais informações sobre como gerenciar suas configurações de cobrança de {% data variables.product.prodname_ghe_server %}, consulte "[Gerenciar cobrança para sua empresa](/admin/overview/managing-billing-for-your-enterprise)". Para obter mais informações sobre o {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}, consulte "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)". Para atualizar para {% data variables.product.prodname_enterprise %} ou para começar com uma conta corporativa, entre em contato com {% data variables.contact.contact_enterprise_sales %}. -For more information about member access and management, see "{% if currentVersion == "free-pro-team@latest" %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}." +Para obter mais informações sobre acesso e gerenciamento de integrantes, consulte "{% if currentVersion == "free-pro-team@latest" %}[Gerenciar usuários na sua empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Gerenciar usuários, organizações e repositórios](/admin/user-management){% endif %}." -Para obter mais informações sobre o gerenciamento de contas corporativas usando a API GraphQL, consulte "[Contas corporativas](/v4/guides/managing-enterprise-accounts)". +Para obter mais informações sobre o gerenciamento de contas corporativas usando a API GraphQL, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)". {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account.md index 2bd1d3b766..c2187fe3a9 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: Configuring the retention period for GitHub Actions artifacts and logs in your enterprise account -intro: 'Enterprise owners can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in an enterprise account.' +title: Configurar o período de retenção para artefatos e registros do GitHub Actions na sua conta corporativa +intro: 'Os proprietários de empresas podem configurar o período de retenção para artefatos e registros de {% data variables.product.prodname_actions %} de uma conta corporativa.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account @@ -12,7 +12,7 @@ versions: {% data reusables.actions.about-artifact-log-retention %} -## Setting the retention period for an enterprise +## Definir o período de retenção para uma empresa {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.business %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md index dcb5400a30..6ff1ec7816 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -34,7 +34,7 @@ Você pode desabilitar todos os fluxos de trabalho para uma empresa ou definir u {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Adicionar ações para permitir lista](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) +1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. ![Adicionar ações para permitir lista](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) ### Habilitar fluxos de trabalho para bifurcações privadas do repositório diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md index 3374f119cd..6749343d5c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md @@ -49,7 +49,7 @@ Em todas as organizações pertencentes à conta corporativa, é possível permi {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 3. Na guia **Repository policies** (Políticas de repositório), em "Repository invitations" (Convites para repositórios), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -4. Under "Repository invitations", use the drop-down menu and choose a policy. ![Menu suspenso com opções de políticas de convite de colaboradores externos](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png) +4. Em "Convites para repositórios, use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de convite de colaboradores externos](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png) ### Aplicar política sobre como alterar a visibilidade do repositório diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md index f6b634d619..72035f7b2c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: Setting up and managing your enterprise -shortTitle: Your enterprise +title: Configurar e gerenciar sua empresa +shortTitle: Sua empresa product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md index b45da0bc2e..249ecea3cb 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Inviting people to manage your enterprise +title: Convidar pessoas para gerenciar sua empresa intro: É possível convidar pessoas para se tornarem proprietários ou gerentes de cobrança em sua conta corporativa. Também é possível remover proprietários ou gerentes de cobrança corporativos que não precisam mais acessar a conta corporativa. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: @@ -13,7 +13,7 @@ versions: ### Sobre convidar pessoas para gerenciar sua conta corporativa -{% data reusables.enterprise-accounts.enterprise-administrators %} For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise). +{% data reusables.enterprise-accounts.enterprise-administrators %} Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise). {% tip %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index 2912c3987a..f71e6b4e4b 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -3,6 +3,7 @@ title: Gerenciar licenças para a assinatura do Visual Studio com o GitHub Enter intro: 'Você pode gerenciar o licenciamento de {% data variables.product.prodname_enterprise %} para {% data variables.product.prodname_vss_ghe %}.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle + - /github/setting-up-and-managing-your-enterprise-account/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle - /github/articles/about-the-github-and-visual-studio-bundle - /articles/about-the-github-and-visual-studio-bundle - /github/setting-up-and-managing-your-enterprise-account/managing-licenses-for-visual-studio-subscription-with-github-enterprise @@ -36,7 +37,7 @@ Para usar a parte de {% data variables.product.prodname_enterprise %} da licenç Depois de atribuir uma licença para {% data variables.product.prodname_vss_ghe %} em {% data variables.product.prodname_vss_admin_portal_with_url %}, você pode visualizar o número de licenças de {% data variables.product.prodname_enterprise %} disponíveis para a sua conta corporativa. Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account)". -Você também pode ver convites pendentes de {% data variables.product.prodname_enterprise %} para inscritos em {% data variables.product.prodname_vss_admin_portal_with_url %}. A lista de convites pendentes inclui assinantes que ainda não são integrantes de pelo menos uma organização na sua conta corporativa. For more information, see "[Viewing people in your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)." +Você também pode ver convites pendentes de {% data variables.product.prodname_enterprise %} para inscritos em {% data variables.product.prodname_vss_admin_portal_with_url %}. A lista de convites pendentes inclui assinantes que ainda não são integrantes de pelo menos uma organização na sua conta corporativa. Para obter mais informações, consulte "[Visualizar pessoas na sua empresa](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)". ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 2651dc1ee2..8672d1d928 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -1,6 +1,6 @@ --- -title: Roles in an enterprise -intro: 'Everyone in an enterprise is a member of the enterprise. To control access to your enterprise''s settings and data, you can assign different roles to members of your enterprise.' +title: Funções em uma empresa +intro: 'Todas as pessoas em uma empresa são integrantes da empresa. Para controlar o acesso às configurações e dados da sua empresa, você pode atribuir diferentes funções aos integrantes da sua empresa.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account @@ -12,47 +12,47 @@ versions: github-ae: '*' --- -### About roles in an enterprise +### Sobre funções em uma empresa -Everyone in an enterprise is a member of the enterprise. You can also assign administrative roles to members of your enterprise. Each administrator role maps to business functions and provides permissions to do specific tasks within the enterprise. +Todas as pessoas em uma empresa são integrantes da empresa. Você também pode atribuir funções administrativas aos integrantes da sua empresa. Cada função de administrador está associada a uma função empresarial e fornece permissão para a execução de tarefas específicas na empresa. {% data reusables.enterprise-accounts.enterprise-administrators %} -For more information about adding people to your enterprise, see "{% if currentVersion == "free-pro-team@latest" %}[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Authentication](/admin/authentication){% endif %}". +Para mais informações sobre como adicionar pessoas à sua empresa, consulte "{% if currentVersion == "free-pro-team@latest" %}[Convidar pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Autenticação](/admin/authentication){% endif %}". ### Proprietário corporativo -Enterprise owners have complete control over the enterprise and can take every action, including: +Os proprietários corporativos têm controle total da empresa e podem executar todas as ações, incluindo: - Gerenciar os administradores -- {% if currentVersion == "free-pro-team@latest" %}Adding and removing {% elsif currentVersion == "github-ae@latest" %}Managing{% endif %} organizations {% if currentVersion == "free-pro-team@latest" %}to and from {% elsif currentVersion == "github-ae@latest" %} in{% endif %} the enterprise +- {% if currentVersion == "free-pro-team@latest" %}Adicionar e remover {% elsif currentVersion == "github-ae@latest" %}Managing{% endif %} organizações{% if currentVersion == "free-pro-team@latest" %}para e de {% elsif currentVersion == "github-ae@latest" %} na{% endif %} empresa - Gerenciar as configurações da empresa - Aplicar a política nas organizações {% if currentVersion == "free-pro-team@latest" %}- Managing billing settings{% endif %} -Os proprietários corporativos não podem acessar as configurações ou o conteúdo da organização, a menos que sejam incluídos como proprietário da organização ou recebam acesso direto a um repositório de propriedade da organização. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. +Os proprietários corporativos não podem acessar as configurações ou o conteúdo da organização, a menos que sejam incluídos como proprietário da organização ou recebam acesso direto a um repositório de propriedade da organização. Da mesma forma, os proprietários de organizações na sua empresa não têm acesso à empresa propriamente dita, a não ser que você os torne proprietários da empresa. -You can add as many enterprise owners as you'd like to your enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. +Você pode adicionar quantos proprietários corporativos desejar na sua empresa. {% if currentVersion == "free-pro-team@latest" %}Os proprietários de empresas devem ter uma conta pessoal em {% data variables.product.prodname_dotcom %}.{% endif %} Como prática recomendada, sugerimos que você converta apenas algumas pessoas da sua empresa em proprietários para reduzir o risco para a sua empresa. ### Integrantes da empresa -Members of organizations owned by your enterprise are also automatically members of the enterprise. Members can collaborate in organizations and may be organization owners, but members cannot access or configure enterprise settings{% if currentVersion == "free-pro-team@latest" %}, including billing settings{% endif %}. +Os integrantes das organizações pertencentes à sua empresa também são automaticamente integrantes da empresa. Os integrantes podem colaborar em organizações e podem ser proprietários de organizações, mas os integrantes não podem acessar ou definir as configurações corporativas{% if currentVersion == "free-pro-team@latest" %}, incluindo as configurações de cobrança{% endif %}. -People in your enterprise may have different levels of access to the various organizations owned by your enterprise and to repositories within those organizations. Você pode ver os recursos aos quais cada pessoa tem acesso. For more information, see "[Viewing people in your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)." +As pessoas na sua empresa podem ter diferentes níveis de acesso às várias organizações pertencentes à sua empresa e aos repositórios dessas organizações. Você pode ver os recursos aos quais cada pessoa tem acesso. Para obter mais informações, consulte "[Visualizar pessoas na sua empresa](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)". Para obter mais informações sobre as permissões da organização, consulte "[Níveis de permissão da organização](/articles/permission-levels-for-an-organization)". -People with outside collaborator access to repositories owned by your organization are also listed in your enterprise's People tab, but are not enterprise members and do not have any access to the enterprise. Para obter mais informações sobre colaboradores externos, consulte "[Níveis de permissão da organização](/articles/permission-levels-for-an-organization#outside-collaborators)". +Pessoas com acesso de colaborador externo aos repositórios pertencentes à sua organização também estão listadas na aba Pessoas da sua empresa, mas não são integrantes da empresa e não têm qualquer acesso à mesma. Para obter mais informações sobre colaboradores externos, consulte "[Níveis de permissão da organização](/articles/permission-levels-for-an-organization#outside-collaborators)". {% if currentVersion == "free-pro-team@latest" %} ### Gerente de cobrança -Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can: +Os gerentes de cobrança só têm acesso às configurações de cobrança da sua empresa. Gerentes de cobrança para a sua empresa podem: - Visualizar e gerenciar licenças de usuário, pacotes do {% data variables.large_files.product_name_short %} e outras configurações de cobrança - Exibir uma lista dos gerentes de cobrança - Adicionar ou remover outros gerentes de cobrança -Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Os gerentes de cobrança devem ter uma conta pessoal no {% data variables.product.prodname_dotcom %}. +Os gerentes de cobrança não têm acesso a organizações ou repositórios na sua empresa e não podem adicionar ou remover os proprietários da empresa. Os gerentes de cobrança devem ter uma conta pessoal no {% data variables.product.prodname_dotcom %}. ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index fab65dabc9..a1ab984a6e 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Viewing and managing a user's SAML access to your enterprise +title: Visualizar e gerenciar o acesso SAML de um usuário à sua empresa intro: 'Você pode visualizar e revogar a identidade vinculada de um integrante da empresa, as sessões ativas e as credenciais autorizadas.' permissions: Os proprietários das empresas podem visualizar e gerenciar o acesso de SAML de um integrante na organização. product: '{% data reusables.gated-features.enterprise-accounts %}' diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md index ffbd449481..d0a6e2ea7b 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Viewing people in your enterprise -intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.' +title: Visualizar pessoas na sua empresa +intro: 'Para auditar o acesso à utilização de licença de usuário ou de recursos pertencentes à empresa, os proprietários corporativos podem exibir todos os administradores e integrantes da empresa.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account @@ -11,9 +11,9 @@ versions: github-ae: '*' --- -### Viewing enterprise owners{% if currentVersion == "free-pro-team@latest" %} and billing managers{% endif %} +### Visualizar proprietários corporativos{% if currentVersion == "free-pro-team@latest" %} e gerentes de cobrança{% endif %} -You can view enterprise owners {% if currentVersion == "free-pro-team@latest" %} and billing managers, {% endif %}as well as a list of pending invitations to become owners{% if currentVersion == "free-pro-team@latest" %} and billing managers. You can filter the list of enterprise administrators by role{% endif %}. ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome completo dela. +Você pode ver os proprietários corporativos {% if currentVersion == "free-pro-team@latest" %} e gerentes de cobrança, {% endif %}bem como uma lista de convites pendentes para se tornarem proprietários{% if currentVersion == "free-pro-team@latest" %} e gerentes de cobrança. Você pode filtrar a lista de administradores corporativos por função{% endif %}. ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome completo dela. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} @@ -23,9 +23,9 @@ You can view enterprise owners {% if currentVersion == "free-pro-team@latest" %} ### Exibir integrantes e colaboradores externos -Você pode ver o número de integrantes ou colaboradores externos pendentes. You can filter the list of members by {% if currentVersion == "free-pro-team@latest" %}deployment ({% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}),{% endif %}role {% if currentVersion == "free-pro-team@latest" %}, and{% elsif currentVersion == "github-ae@latest" %}or {% endif %}organization. Também é possível filtrar a lista de colaboradores externos pela visibilidade dos repositórios aos quais o colaborador tem acesso. Ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome de exibição dela. +Você pode ver o número de integrantes ou colaboradores externos pendentes. Você pode filtrar a lista de integrantes por {% if currentVersion == "free-pro-team@latest" %}deploy ({% data variables.product.prodname_ghe_cloud %} ou {% data variables.product.prodname_ghe_server %}),{% endif %}função{% if currentVersion == "free-pro-team@latest" %} e {% elsif currentVersion == "github-ae@latest" %}ou {% endif %}organização. Também é possível filtrar a lista de colaboradores externos pela visibilidade dos repositórios aos quais o colaborador tem acesso. Ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome de exibição dela. -You can view {% if currentVersion == "free-pro-team@latest" %}all the {% data variables.product.prodname_ghe_cloud %} organizations and {% data variables.product.prodname_ghe_server %} instances that a member belongs to, and {% endif %}which repositories an outside collaborator has access to{% if currentVersion == "free-pro-team@latest" %}, {% endif %} by clicking on the person's name. +Você pode visualizar {% if currentVersion == "free-pro-team@latest" %}todas as organizações de {% data variables.product.prodname_ghe_cloud %} e as instâncias de {% data variables.product.prodname_ghe_server %} às quais um membro pertence e {% endif %}quais repositórios um colaborador externo tem acesso a{% if currentVersion == "free-pro-team@latest" %}, {% endif %} clicando no nome da pessoa. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} @@ -35,4 +35,4 @@ You can view {% if currentVersion == "free-pro-team@latest" %}all the {% data va ### Leia mais -- "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)" +- "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 3ff0ad16fd..d93885da2f 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,15 +15,15 @@ versions: As contas corporativas atualmente estão disponíveis para clientes do {% data variables.product.prodname_enterprise %} que pagam com fatura. A cobrança de todas as organizações e instâncias {% data variables.product.prodname_ghe_server %} conectadas à sua conta corporativa é agregada em uma única fatura para todos os seus serviços pagos do {% data variables.product.prodname_dotcom_the_website %} (incluindo licenças pagas nas organizações, pacotes de dados do {% data variables.large_files.product_name_long %} e assinaturas de apps do {% data variables.product.prodname_marketplace %}). -For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +Para obter mais informações sobre como administrar gerentes de cobrança, consulte "[Convidar pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". ### Exibir assinatura e uso da conta corporativa {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -4. Under "User -{% if currentVersion == "free-pro-team@latest" %}Licenses{% else %}licenses{% endif %}", view your total licenses, number of consumed licenses, and your subscription expiration date. +4. Em +{% if currentVersion == "free-pro-team@latest" %}Licenças{% else %}licenças{% endif %} do usuário", visualize o seu total de licenças, o número de licenças consumidas e a data de expiração da assinatura. {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Informações de assinaturas e licenças nas configurações de cobrança da empresa](/assets/images/enterprise/enterprises/enterprise-server-billing-license-info.png){% endif %} -5. To view details of the user licenses currently in use, click **View {% if currentVersion == "free-pro-team@latest" %}details{% else %}users{% endif %}**. +5. Para ver os detalhes das licenças dos usuários em uso atualmente, clique em **Ver {% if currentVersion == "free-pro-team@latest" %}detalhes{% else %}de usuários{% endif %}**. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md index 22ad8fb851..4e5a892d38 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md @@ -13,7 +13,7 @@ versions: Você pode adicionar informações pessoais sobre si mesmo na bio, como locais em que trabalhou anteriormente, os projetos com os quais contribuiu ou interesses que você tem que outras pessoas talvez gostem de saber. Para obter mais informações, consulte "[Adicionar uma bio ao seu perfil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)". -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} {% data reusables.profile.profile-readme %} @@ -23,19 +23,17 @@ Você pode adicionar informações pessoais sobre si mesmo na bio, como locais e As pessoas que visitam seu perfil veem uma linha do tempo da sua atividade de contribuição, como problemas e pull requests que abriu, commits que fez e pull requests que revisou. Você pode optar por exibir apenas contribuições públicas ou também incluir contribuições privadas e anônimas. Para obter mais informações, consulte "[Exibir contribuições na sua página de perfil](/articles/viewing-contributions-on-your-profile-page)" ou "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". -Elas também podem ver: +People who visit your profile can also see the following information. -- Repositórios e gists que você possui ou com os quais contribui. Você pode exibir seu melhor trabalho fixando repositórios e gists no seu perfil. Para obter mais informações, consulte "[Fixar itens no seu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)". -- Repositórios que você salvou com estrela. Para obter mais informações, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)" -- Uma visão geral da sua atividade em organizações, repositórios e equipes nos quais você está mais ativo. Para obter mais informações, consulte "[Exibir uma visão geral da sua atividade no seu perfil.](/articles/showing-an-overview-of-your-activity-on-your-profile){% if currentVersion == "free-pro-team@latest" %} -- Selos que anunciam sua participação em programas como {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %} ou o no programa de desenvolvedor de {% data variables.product.company_short %}. -- Se você está usando o {% data variables.product.prodname_pro %}. Para obter mais informações, consulte "[Personalizar seu perfil](/articles/personalizing-your-profile)".{% endif %} +- Repositórios e gists que você possui ou com os quais contribui. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can showcase your best work by pinning repositories and gists to your profile. Para obter mais informações, consulte "[Fixar itens no seu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)".{% endif %} +- Repositórios que você salvou com estrela. Para obter mais informações, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)." +- Uma visão geral da sua atividade em organizações, repositórios e equipes nos quais você está mais ativo. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% if currentVersion == "free-pro-team@latest" %} +- Badges that show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. Para obter mais informações, consulte "[Personalizar seu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)".{% endif %} Você também pode definir um status no seu perfil para fornecer informações sobre a sua disponibilidade. Para obter mais informações, consulte "[Configurar um status](/articles/personalizing-your-profile/#setting-a-status)". ### Leia mais - "[Como configurar minha foto de perfil?](/articles/how-do-i-set-up-my-profile-picture)" -- "[Fixar repositórios em seu perfil](/articles/pinning-repositories-to-your-profile)" - "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" - "[Exibir contribuições no perfil](/articles/viewing-contributions-on-your-profile)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 5f0cf00fac..4dea21b893 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -4,7 +4,6 @@ intro: 'Você pode adicionar um LEIAME ao seu perfil de{% data variables.product versions: free-pro-team: '*' enterprise-server: '>=2.22' - github-ae: '*' --- ### Sobre o LEIAME do seu perfil @@ -62,4 +61,4 @@ The method you choose is dependant upon your needs, but if you're unsure, we rec ### Leia mais -- [Sobre LEIAMEs](/github/creating-cloning-and-archiving-repositories/about-readmes) +- [Sobre READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md index 6d5de6a807..9370ca2eeb 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md @@ -50,9 +50,9 @@ Você pode alterar o nome que é exbido em seu perfil. Este nome também pode se Adicione uma bio em seu perfil para compartilhar informações sobre si mesmo com outros usuários {% data variables.product.product_name %}. Com a ajuda de [@menções](/articles/basic-writing-and-formatting-syntax) e emojis, você pode incluir informações sobre onde está trabalhando agora ou já trabalhou, que tipo de trabalho faz ou mesmo que tipo de café toma. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -Para um formulário mais longo e uma maneira mais proeminente de exibir informações personalizadas sobre você, também é possível usar um LEIAME do perfil. Para obter mais informações sobre o LEIAME do perfil, consulte "[Gerenciar o LEIAME do seu perfil](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)". +Para um formulário mais longo e uma maneira mais proeminente de exibir informações personalizadas sobre você, também é possível usar um LEIAME do perfil. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." {% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md index 6cdf3eb780..ef89755716 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md @@ -1,13 +1,12 @@ --- title: Fixar itens no seu perfil -intro: 'You can pin gists and repositories to your profile so other people can quickly see your best work.' +intro: 'Você pode fixar gists e repositórios no seu perfil para que outras pessoas possam ver seu melhor trabalho rapidamente.' redirect_from: - /articles/pinning-repositories-to-your-profile/ - /articles/pinning-items-to-your-profile versions: free-pro-team: '*' enterprise-server: '*' - github-ae: '*' --- É possível fixar um repositório público se você detém o repositório ou se fez contribuições ao repositório. Os commits em bifurcações não contam como contribuições e não é possível fixar uma bifurcação que não pertence a você. Para obter mais informações, consulte "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index cfd5f2b65b..7cfff2ab85 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- title: Mostrar ou ocultar contribuições privadas no perfil -intro: 'Seu perfil do {% data variables.product.product_name %} mostra um gráfico de contribuições no seu repositório no último ano. É possível escolher mostrar atividades anônimas em repositórios privados além da atividade mostrada em repositórios públicos.' +intro: 'Seu perfil do {% data variables.product.product_name %} mostra um gráfico de contribuições no seu repositório no último ano. You can choose to show anonymized activity from {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}private and internal{% else %}private{% endif %} repositories{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} in addition to the activity from public repositories{% endif %}.' redirect_from: - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile versions: diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 35613400de..839d95ba87 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- title: Exibir contribuições no perfil -intro: 'Seu perfil do {% data variables.product.product_name %} mostra os repositórios fixos e um gráfico de contribuições no seu repositório no último ano.' +intro: 'Your {% data variables.product.product_name %} profile shows off {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.' redirect_from: - /articles/viewing-contributions/ - /articles/viewing-contributions-on-your-profile-page/ @@ -11,11 +11,11 @@ versions: github-ae: '*' --- -O gráfico de contribuição mostra a atividade em repositórios públicos. Você pode optar por mostrar a atividade de repositórios públicos e privados, com detalhes específicos da sua atividade em repositórios privados anônimos. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and{% endif %}private repositories, with specific details of your activity in private repositories anonymized. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". {% note %} -**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. Para obter mais informações, consulte "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" +**Observação:** Os commits só aparecerão no seu gráfico de contribuições se o endereço de e-mail que você usou para criar das submissões estiver conectado à sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" {% endnote %} @@ -26,23 +26,27 @@ Na sua página de perfil, determinadas ações contam como contribuições: - Fazer commit no branch `gh-pages` ou no branch padrão de um repositório - Abrir um problema - Propor uma pull request -- Submitting a pull request review{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- Enviar uma revisão de pull request{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - Fazer coautoria de commits no branch `gh-pages` ou no branch padrão do repositório{% endif %} {% data reusables.pull_requests.pull_request_merges_and_contributions %} ### Repositórios populares -Esta seção exibe os repositórios com a maioria dos inspetores. Depois que você [fixar os repositórios no seu perfil](/articles/pinning-repositories-to-your-profile), esta seção será alterada para "Repositórios fixos". +Esta seção exibe os repositórios com a maioria dos inspetores. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %} ![Repositórios populares](/assets/images/help/profile/profile_popular_repositories.png) +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + ### Repositórios fixos Esta seção exibe até seis repositórios públicos e pode incluir tanto repositórios pertencentes a você como aqueles com os quais você contribuiu. Para ver detalhes importantes sobre os repositórios que você escolheu retratar, cada repositório nesta seção inclui um resumo do trabalho que está sendo feito, o número de [estrelas](/articles/saving-repositories-with-stars/) que ele recebeu e a principal linguagem de programação usada nele. Para obter mais informações, consulte "[Fixar repositórios no seu perfil](/articles/pinning-repositories-to-your-profile)". ![Repositórios fixos](/assets/images/help/profile/profile_pinned_repositories.png) +{% endif %} + ### Calendário de contribuições O calendário de contribuições mostra sua atividade de contribuição. @@ -82,9 +86,9 @@ A seção de atividade de contribuição contém uma linha do tempo detalhada do {% if currentVersion != "github-ae@latest" %} ### Exibir contribuições da {% data variables.product.product_location_enterprise %} no {% data variables.product.prodname_dotcom_the_website %} -If your site administrator has enabled +Se o administrador do site habilitou -{% data variables.product.prodname_unified_contributions %}, you can send {% data variables.product.prodname_enterprise %} contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile. Para obter mais informações, consulte "[Enviar suas contribuições do {% data variables.product.prodname_ghe_server %} para o {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)". +{% data variables.product.prodname_unified_contributions %}, você pode enviar contagens de contribuição de {% data variables.product.prodname_enterprise %} para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Enviar suas contribuições do {% data variables.product.prodname_ghe_server %} para o {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)". {% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index d8a1685427..c061614021 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -39,9 +39,9 @@ Além disso, **pelo menos uma** das seguintes afirmativas devem ser verdadeiras: Depois de fazer um commit que atenda aos requisitos para ser contabilizado como contribuição, talvez você precise aguardar até 24 horas para que a contribuição seja exibida no gráfico de contribuições. -#### Your local Git commit email isn't connected to your account +#### Seu e-mail de confirmação do Git local não está conectado à sua conta -Commits must be made with an email address that is connected to your account on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}, or the {% data variables.product.product_name %}-provided `noreply` email address provided to you in your email settings,{% endif %} in order to appear on your contributions graph.{% if currentVersion == "free-pro-team@latest" %} For more information about `noreply` email addresses, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)."{% endif %} +Os commits devem ser feitos com um endereço de e-mail conectado à sua conta em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} ou ao endereço de e-mail do tipo `noreply` fornecido por {% data variables.product.product_name %} a você nas suas configurações de e-mail{% endif %} para aparecer no seu gráfico de contribuições.{% if currentVersion == "free-pro-team@latest" %} Para mais informações sobre endereços de e-mail do tipo `noreply`, consulte "[Definir o seu endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses).{% endif %} Você pode verificar o endereço de e-mail usado para um commit adicionando `.patch` ao final de uma URL de commit; por exemplo, https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: @@ -54,7 +54,7 @@ Subject: [PATCH] updated index for better welcome message O endereço de e-mail no campo `From:` é o que foi definido nas [configurações locais do Git](/articles/set-up-git). Neste exemplo, o endereço de e-mail usado para o commit é `octocat@nowhere.com`. -If the email address used for the commit is not connected to your account on {% data variables.product.product_name %}, {% if currentVersion == "github-ae@latest" %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your {% data variables.product.product_name %} account. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %} +Se o endereço de e-mail usado para o commit não estiver conectado à sua conta em {% data variables.product.product_name %}, {% if currentVersion == "github-ae@latest" %}altere o endereço de e-mail usado para criar commits no Git. Para obter mais informações, consulte "[Definir o seu endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git).{% else %}você deve [adicionar o endereço de e-mail](/articles/adding-an-email-address-to-your-github-account) à sua conta de {% data variables.product.product_name %}. Seu gráfico de contribuições será reconstruído automaticamente quando você adicionar o novo endereço.{% endif %} {% warning %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md index c3bdf530cd..d47726d72a 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md @@ -15,7 +15,7 @@ versions: Seu quadro pessoal é a primeira página que você verá quando entrar no {% data variables.product.product_name %}. -Para acessar seu quadro pessoal assim que se conectar, clique no {% octicon "mark-github" aria-label="The github octocat logo" %} no canto superior esquerdo de qualquer página em {% data variables.product.product_url %}. +Para acessar seu quadro pessoal assim que se conectar, clique no {% octicon "mark-github" aria-label="The github octocat logo" %} no canto superior esquerdo de qualquer página em {% data variables.product.product_name %}. ### Encontrar sua atividade recente @@ -29,7 +29,7 @@ Na barra lateral esquerda do painel, é possível acessar os repositórios e equ ![lista de repositórios e equipes de diferentes organizações](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png) -The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list 4 months after you last interacted with them. +A lista dos principais repositórios é gerada automaticamente e pode incluir qualquer repositório com o qual você interagiu, independentemente de pertencer diretamente à sua conta. As interações incluem criação commits, abrir ou comentar em problemas e pull requests. A lista dos principais repositórios não pode ser editada, mas os repositórios serão excluídos da lista 4 meses após a última vez que você interagir com eles. Também é possível encontrar uma lista de seus repositórios, equipes e quadros de projeto recentemente visitados quando você clica na barra de pesquisa no topo de qualquer página do {% data variables.product.product_name %}. @@ -39,11 +39,11 @@ Na seção "All activity" (Todas as atividades) do feed de notícias, você pode Atualizações serão exibidas no feed de notícias quando um usuário que você segue: - Marcar um repositório com estrelas. -- Seguir outro usuário. -- Cria um repositório público. +- Follows another user.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- Creates a public repository.{% endif %} - Abrir um problema ou uma pull request com a etiqueta "help wanted" ou "good first issue" em um repositório que você está inspecionando. -- Fizer push de commits em um repositório que você inspeciona. -- Bifurcar um repositório público. +- Pushes commits to a repository you watch.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- Forks a public repository.{% endif %} Para obter mais informações sobre como atribuir estrelas a repositórios e seguir pessoas, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)" e "[Seguir pessoas](/articles/following-people)". diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md index 8140f49101..b498d312f6 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md @@ -1,6 +1,6 @@ --- -title: Changing your GitHub username -intro: 'You can change your {% data variables.product.product_name %} username at any time.' +title: Alterar seu nome de usuário do GitHub +intro: 'Você pode alterar seu nome de usuário do {% data variables.product.product_name %} a qualquer momento.' redirect_from: - /articles/how-to-change-your-username/ - /articles/changing-your-github-user-name/ @@ -12,50 +12,46 @@ versions: enterprise-server: '*' --- -### About username changes +### Sobre alterações no nome de usuário -You can change your username to another username that is not currently in use.{% if currentVersion == "free-pro-team@latest" %} If the username you want is not available, you'll see information about whether you can request the username to be released when you type in the desired username. +Você pode alterar oseu nome de usuário para outro nome de usuário que não está atualmente em uso.{% if currentVersion == "free-pro-team@latest" %} Se o nome de usuário que você deseja não estiver disponível, você verá informações sobre se pode solicitar a liberação do nome de usuário ao digitar o nome de usuário desejado. -If the username is not eligible for release and you don't hold a trademark for the username, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %} +Se o nome de usuário não estiver qualificado para liberação e você não detém uma marca comercial para este nome de usuário, é possível escolher outro ou manter o atual. O {% data variables.contact.github_support %} não pode liberar o nome de usuário indisponível para você. Para obter mais informações, consulte "[Alterar nome de usuário](#changing-your-username)".{% endif %} -After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect. +Depois de alterar seu nome de usuário, o nome antigo será disponibilizado para reivindicação por qualquer pessoa. A maioria das referências aos seus repositórios sob o nome de usuário antigo muda automaticamente para o novo nome de usuário. No entanto, alguns links para seu perfil não são redirecionados automaticamente. -{% data variables.product.product_name %} cannot set up redirects for: -- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username -- Links to [gists](/articles/creating-gists) that include your old username +O {% data variables.product.product_name %} não pode configurar redirecionamentos para: +- [@menções](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) usando o nome de usuário antigo +- Links para [gists](/articles/creating-gists) que incluem o nome de usuário antigo -### Repository references +### Referências de repositório -After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories. -- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change. -- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work. +Após alteração do nome de usuário, o {% data variables.product.product_name %} redirecionará automaticamente as referências para os repositórios. +- Os links da web para repositórios existentes continuarão funcionando. Esse processo pode demorar alguns minutos para ser concluído após a alteração. +- A linha de comando que faz push dos clones do repositório local para as URLs de controle do remote continuarão funcionando. -If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Changing a remote's URL](/articles/changing-a-remote-s-url)." +Se o novo proprietário do seu antigo nome de usuário criar um repositório com o mesmo nome do seu repositório, isso substituirá a entrada de redirecionamento e o seu redirecionamento para de funcionar. Por conta dessa possibilidade, é recomendável atualizar todas as URLs existentes do repositório remote após alteração do seu nome de usuário. Para obter mais informações, consulte "[Alterar o URL de um remote](/articles/changing-a-remote-s-url)". -### Links to your previous profile page +### Links para a página de perfil anterior -After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your {% data variables.product.product_name %} account from elsewhere{% if currentVersion == "free-pro-team@latest" %}, such as your LinkedIn or Twitter profile{% endif %}. +Após alteração do nome de usuário, os links para sua página de perfil anterior, como `https://{% data variables.command_line.backticks %}/previoususername`, retornarão um erro 404. Recomendamos atualizar todos os links para a sua conta de {% data variables.product.product_name %} de outro lugar{% if currentVersion == "free-pro-team@latest" %}, como, por exemplo, o seu perfil do LinkedIn ou do Twitter{% endif %}. -### Your Git commits +### Seus commits no Git -{% if currentVersion == "free-pro-team@latest"%}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% if currentVersion == "free-pro-team@latest"%}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +{% if currentVersion == "free-pro-team@latest"%}commits do Git associados ao seu endereço de e-mail `noreply` fornecido por {% data variables.product.product_name %} não serão atribuídos ao seu novo nome de usuário e não aparecerão no seu gráfico de contribuições.{% endif %} Se seus commits Git estiverem associados a outro endereço de e-mail que você [adicionou à sua conta do GitHub](/articles/adding-an-email-address-to-your-github-account), {% if currentVersion == "free-pro-team@latest"%}incluindo o endereço de e-mail `noreply` baseado em ID fornecido por {% data variables.product.product_name %}, {% endif %} ele continuará a ser atribuído a você e aparecerá no gráfico de contribuições depois de mudar o seu nome de usuário. Para obter mais informações sobre como configurar o endereço de e-mail, consulte "[Configurar o endereço de e-mail do commit](/articles/setting-your-commit-email-address)". -### Changing your username +### Alterar nome de usuário {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.account_settings %} -3. In the "Change username" section, click **Change username**. - ![Change Username button](/assets/images/help/settings/settings-change-username.png){% if currentVersion == "free-pro-team@latest" %} -4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**. - ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png) -5. Type a new username. - ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see. - ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png) +3. Na seção "Change username" (Alterar nome de usuário), clique em **Change username** (Alterar nome de usuário). ![Change Username button](/assets/images/help/settings/settings-change-username.png){% if currentVersion == "free-pro-team@latest" %} +4. Leia os avisos sobre a mudança de seu nome de usuário. Se você ainda quiser alterar seu nome de usuário, clique em **I understand, let's change my username** (Compreendo, vamos alterar meu nome de usuário). ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-username-warning-button.png) +5. Digite um novo nome de usuário. ![Campo New Username (Novo nome de usuário)](/assets/images/help/settings/settings-change-username-enter-new-username.png) +6. Se o nome que você escolheu estiver disponível, clique em **Change my username** (Alterar meu nome de usuário). Se o nome que você escolheu estiver indisponível, tente um nome de usuário diferente ou uma das sugestões que aparecem. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-my-username-button.png) {% endif %} -### Further reading +### Leia mais -- "[Changing a remote's URL](/articles/changing-a-remote-s-url)" -- "[Why are my commits linked to the wrong user?](/articles/why-are-my-commits-linked-to-the-wrong-user)"{% if currentVersion == "free-pro-team@latest" %} -- "[{% data variables.product.prodname_dotcom %} Username Policy](/articles/github-username-policy)"{% endif %} +- "[Alterar o URL de um remote](/articles/changing-a-remote-s-url)" +- "[Por que os meus commits estão vinculados ao usuário incorreto?](/articles/why-are-my-commits-linked-to-the-wrong-user)"{% if currentVersion == "free-pro-team@latest" %} +- "[{% data variables.product.prodname_dotcom %} Política de nome de usuário](/articles/github-username-policy)"{% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md index 821652eb73..6ce7743d9f 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -1,6 +1,6 @@ --- -title: Configurar e gerenciar sua conta de usuário do GitHub -shortTitle: Contas de usuário +title: Setting up and managing your GitHub user account +shortTitle: User accounts redirect_from: - /categories/setting-up-and-managing-your-github-user-account versions: @@ -10,45 +10,31 @@ versions: --- -### Índice +### Table of Contents {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} {% link_in_list /changing-your-github-username %} - {% link_in_list /merging-multiple-user-accounts %} {% link_in_list /converting-a-user-into-an-organization %} - {% link_in_list /deleting-your-user-account %} {% link_in_list /permission-levels-for-a-user-account-repository %} {% link_in_list /permission-levels-for-user-owned-project-boards %} {% link_in_list /managing-the-default-branch-name-for-your-repositories %} {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %} {% link_in_list /managing-access-to-your-user-accounts-project-boards %} - {% link_in_list /integrating-jira-with-your-personal-projects %} - - {% link_in_list /best-practices-for-leaving-your-company %} - - {% link_in_list /what-does-the-available-for-hire-checkbox-do %} - {% topic_link_in_list /managing-email-preferences %} {% link_in_list /adding-an-email-address-to-your-github-account %} {% link_in_list /changing-your-primary-email-address %} {% link_in_list /setting-a-backup-email-address %} {% link_in_list /setting-your-commit-email-address %} - {% link_in_list /blocking-command-line-pushes-that-expose-your-personal-email-address %} - {% link_in_list /remembering-your-github-username-or-email %} - {% link_in_list /types-of-emails-github-sends %} - - {% link_in_list /managing-marketing-emails-from-github %} - {% topic_link_in_list /managing-access-to-your-personal-repositories %} {% link_in_list /inviting-collaborators-to-a-personal-repository %} {% link_in_list /removing-a-collaborator-from-a-personal-repository %} @@ -58,9 +44,7 @@ versions: {% link_in_list /about-organization-membership %} {% link_in_list /accessing-an-organization %} {% link_in_list /viewing-peoples-roles-in-an-organization %} - {% link_in_list /requesting-organization-approval-for-oauth-apps %} - {% link_in_list /publicizing-or-hiding-organization-membership %} {% link_in_list /managing-your-scheduled-reminders %} {% link_in_list /removing-yourself-from-an-organization %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 0cf6aad5db..b15e839e49 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -10,7 +10,7 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} -3. Na barra lateral esquerda, clique em **{% data variables.product.prodname_oauth_app %}s**. ![{ site.data.variables.product.prodname_oauth_app }}s aba na barra lateral esquerda](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. Na barra lateral esquerda, clique em **{% data variables.product.prodname_oauth_app %}s**. ![{% data variables.product.prodname_oauth_app %}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) 3. Clique em **Register a new application** (Registrar novo aplicativo). 4. Em **Application name** (Nome do aplicativo), digite "Jira". 5. Em **Homepage URL** (URL da página inicial), digite a URL completa da sua instância do JIRA. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index b2a109b456..9b3701fc0e 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -50,7 +50,7 @@ Os repositórios de propriedade de uma organização podem conceder mais acesso ### Leia mais -- "[Níveis de permissão para um repositório de uma conta de usuário](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-on-a-repository-owned-by-a-user-account)" +- "[Níveis de permissão para um repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)" - "[Remover um colaborador de um repositório pessoal](/articles/removing-a-collaborator-from-a-personal-repository)" - "[Remover a si mesmo de um repositório de colaborador](/articles/removing-yourself-from-a-collaborator-s-repository)" - "[Organizar integrantes em equipes](/articles/organizing-members-into-teams)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 22b6f45afc..e489eba672 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -1,6 +1,6 @@ --- -title: Permission levels for a user account repository -intro: 'A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*.' +title: Níveis de permissão para um repositório de conta de usuário +intro: 'A repository owned by a user account has two permission levels: the repository owner and collaborators.' redirect_from: - /articles/permission-levels-for-a-user-account-repository versions: @@ -9,66 +9,75 @@ versions: github-ae: '*' --- +### About permissions levels for a user account repository + +Repositories owned by user accounts have one owner. Ownership permissions can't be shared with another user account. + +You can also {% if currentVersion == "free-pro-team@latest" %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)." + {% tip %} -**Tip:** If you require more granular read/write access to a repository owned by your user account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/articles/transferring-a-repository)." +**Tip:** If you require more granular access to a repository owned by your user account, consider transferring the repository to an organization. Para obter mais informações, consulte "[Transferir um repositório](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)". {% endtip %} -#### Owner access on a repository owned by a user account +### Owner access for a repository owned by a user account -The repository owner has full control of the repository. In addition to all the permissions allowed by repository collaborators, the repository owner can: +O proprietário do repositório tem controle total do repositório. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions. -- {% if currentVersion == "free-pro-team@latest" %}[Invite collaborators](/articles/inviting-collaborators-to-a-personal-repository){% else %}[Add collaborators](/articles/inviting-collaborators-to-a-personal-repository){% endif %} -- Change the visibility of the repository (from [public to private](/articles/making-a-public-repository-private), or from [private to public](/articles/making-a-private-repository-public)){% if currentVersion == "free-pro-team@latest" %} -- [Limit interactions with a repository](/articles/limiting-interactions-with-your-repository){% endif %} -- Merge a pull request on a protected branch, even if there are no approving reviews -- [Delete the repository](/articles/deleting-a-repository) -- [Manage a repository's topics](/articles/classifying-your-repository-with-topics){% if currentVersion == "free-pro-team@latest" %} -- Manage security and analysis settings. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -- [Enable the dependency graph](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) for a private repository{% endif %}{% if currentVersion == "free-pro-team@latest" %} -- Delete packages. For more information, see "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)."{% endif %} -- Create and edit repository social cards. For more information, see "[Customizing your repository's social media preview](/articles/customizing-your-repositorys-social-media-preview)." -- Make the repository a template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."{% if currentVersion != "github-ae@latest" %} -- Receive [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository.{% endif %}{% if currentVersion == "free-pro-team@latest" %} -- Dismiss {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." -- [Manage data usage for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository){% endif %} -- [Define code owners for the repository](/articles/about-code-owners) -- [Archive repositories](/articles/about-archiving-repositories){% if currentVersion == "free-pro-team@latest" %} -- Create security advisories. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)." -- Display a sponsor button. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %} +| Ação | Mais informações | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | +| "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | +| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %} +| Fazer merge de uma pull request em um branch protegido, mesmo sem revisões de aprovação | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)" | +| Excluir o repositório | "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)" | +| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} +| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Excluir pacotes | "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} +| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | +| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +| Receive | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| Manage data use for a private repository | "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"|{% endif %} +| Definir os proprietários do código do repositório | "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} +| Criar consultorias de segurança | "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| Exibir um botão de patrocinador | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %} -There is only **one owner** of a repository owned by a user account; this permission cannot be shared with another user account. To transfer ownership of a repository to another user, see "[How to transfer a repository](/articles/how-to-transfer-a-repository)." +### Collaborator access for a repository owned by a user account -#### Collaborator access on a repository owned by a user account +Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository. {% note %} -**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a user account. +**Observação:** Em um repositório privado, proprietários de repositórios podem conceder somente acesso de gravação aos colaboradores. Os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta de usuário. {% endnote %} -Collaborators on a personal repository can: +Collaborators can also perform the following actions. -- Push to (write), pull from (read), and fork (copy) the repository -- Create, apply, and delete labels and milestones -- Open, close, re-open, and assign issues -- Edit and delete comments on commits, pull requests, and issues -- Mark an issue or pull request as a duplicate. For more information, see "[About duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)." -- Open, merge and close pull requests -- Apply suggested changes to pull requests. For more information, see "[Incorporating feedback in your pull request](/articles/incorporating-feedback-in-your-pull-request)." -- Send pull requests from forks of the repository{% if currentVersion == "free-pro-team@latest" %} -- Publish, view, and install packages. For more information, see "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)."{% endif %} -- Create and edit Wikis -- Create and edit releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository). -- Remove themselves as collaborators on the repository -- Submit a review on a pull request that will affect its mergeability -- Act as a designated code owner for the repository. For more information, see "[About code owners](/articles/about-code-owners)." -- Lock a conversation. For more information, see "[Locking conversations](/articles/locking-conversations)."{% if currentVersion == "free-pro-team@latest" %} -- Report abusive content to {% data variables.contact.contact_support %}. For more information, see "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)."{% endif %} -- Transfer an issue to a different repository. For more information, see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)." +| Ação | Mais informações | +|:----------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Bifurcar o repositório | "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)" | +| Create, edit, and delete comments on commits, pull requests, and issues in the repository |
  • "[About issues](/github/managing-your-work-on-github/about-issues)"
  • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
| +| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| Manage milestones for issues and pull requests in the repository | "[Criar e editar marcos para problemas e pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" | +| Apply suggested changes to pull requests in the repository | "[Incorporating feedback in your pull request](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | +| Create a pull request from a fork of the repository | "[Criar uma pull request de uma bifurcação](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| Submit a review on a pull request that affects the mergeability of the pull request | "[Revisando alterações propostas em uma pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| Create and edit a wiki for the repository | "[Sobre wikis](/github/building-a-strong-community/about-wikis)" | +| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" | +| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" %} +| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| Remover a si mesmos como colaboradores do repositório | "[Remover a si mesmo de um repositório de colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | -### Further reading +### Leia mais -- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)" -- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" +- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md index d0f7e5e2ca..d16cee6434 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md @@ -1,6 +1,6 @@ --- title: Configurar endereço de e-mail de backup -intro: Use a backup email address as an additional destination for security-relevant account notifications{% if currentVersion != "github-ae@latest" %} and to securely reset your password if you can no longer access your primary email address{% endif %}. +intro: Use um endereço de e-mail de backup como um destino adicional para notificações de conta relevantes para segurança{% if currentVersion ! "github-ae@latest" %} e para redefinir sua senha de forma segura, se não puder mais acessar seu endereço de e-mail principal{% endif %}. redirect_from: - /articles/setting-a-backup-email-address versions: diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md index 62d475e2aa..8b82895678 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md @@ -1,6 +1,6 @@ --- title: Configurar o endereço de e-mail do commit -intro: 'You can set the email address that is used to author commits on {% data variables.product.product_name %} and on your computer.' +intro: 'Você pode definir o endereço de e-mail que é usado para criar commits em {% data variables.product.product_name %} e no seu computador.' redirect_from: - /articles/keeping-your-email-address-private/ - /articles/setting-your-commit-email-address-on-github/ @@ -38,7 +38,7 @@ Para operações do Git baseadas na web, você pode configurar o endereço de e- Você também pode optar por bloquear os commits cujo push é feito usando a linha de comando que expõem seu endereço de e-mail pessoal. Para obter mais informações, consulte "[Bloquear pushes de linha de comando que mostrem endereços de e-mail pessoais](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)".{% endif %} -To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your {% data variables.product.product_name %} account{% if currentVersion == "free-pro-team@latest" %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% if currentVersion != "github-ae@latest" %}For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."{% endif %} +Para garantir que os commits sejam atribuídos a você e que apareçam no gráfico de contribuições, use um endereço de e-mail que esteja conectado à sua conta de {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %}, ou o endereço de e-mail `noreply` fornecido a você nas configurações de email{% endif %}. {% if currentVersion != "github-ae@latest" %}Para obter mais informações, consulte "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account){% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/pt-BR/content/github/site-policy/github-acceptable-use-policies.md b/translations/pt-BR/content/github/site-policy/github-acceptable-use-policies.md index 7751adda5d..f9d3ff0641 100644 --- a/translations/pt-BR/content/github/site-policy/github-acceptable-use-policies.md +++ b/translations/pt-BR/content/github/site-policy/github-acceptable-use-policies.md @@ -37,6 +37,8 @@ Ao usar o Serviço, em nenhuma circunstância você irá: - assediar, abusar, ameaçar ou incitar a violência contra qualquer indivíduo ou grupo, incluindo nossos funcionários, dirigentes e agentes ou outros usuários; +- postar conteúdo que fuja ao tópico ou interagir com os recursos da plataforma de forma que interrompe de forma significativa ou repetidamente a experiência de outros usuários; + - usar nossos servidores para qualquer forma de atividade em massa automatizada excessiva (por exemplo, envio de spams ou mineração de criptomoeda), sobrecarregar indevidamente nossos servidores por meios automatizados, ou transmitir qualquer outra forma de publicidade ou demanda não solicitada por meio de nossos servidores, como esquemas do tipo enriqueça rápido; - usar nossos servidores para interromper ou tentar interromper, ou ganhar ou tentar ganhar acesso não autorizado a qualquer serviço, dispositivo, dados, conta ou rede (a menos que autorizado pelo [programa GitHub Bug Bounty](https://bounty.github.com)); @@ -48,15 +50,17 @@ Ao usar o Serviço, em nenhuma circunstância você irá: ### 4. Limites de uso dos serviços Você não reproduzirá, duplicará, copiará, venderá, revenderá ou explorará qualquer parte do Serviço, uso do Serviço ou acesso ao Serviço sem nossa permissão expressa por escrito. -### 5. Restrições de scraping (raspagem) e uso da API -Scraping refere-se à extração de dados de nosso Serviço por meio de um processo automatizado, como um bot ou rastreador web (webcrawler). Não se refere à coleta de informações por meio de nossa API. Por favor, consulte a Seção H de nossos [Termos de Serviço](/articles/github-terms-of-service#h-api-terms) para nossos Termos da API. Você pode raspar o site pelos seguintes motivos: +### 5. Restrições de uso de informações +Você pode usar as informações do nosso Serviço pelos motivos a seguir, independentemente de as informações terem sido processadas, coletadas pela nossa API ou obtidas de outra forma: -- Pesquisadores podem raspar informações públicas e não pessoais do Serviço para fins de pesquisa, somente se quaisquer publicações resultantes da pesquisa forem de acesso aberto. -- Arquivistas podem raspar o Serviço para dados públicos com fins de arquivo. +- Os pesquisadores podem utilizar informações públicas e não pessoais do Serviço para fins de pesquisa, se todas as publicações resultantes dessa pesquisa forem de [acesso público](https://en.wikipedia.org/wiki/Open_access). +- Os Arquivadores podem utilizar informações públicas do Serviço para fins de arquivamento. -Você não poderá raspar o Serviço para fins de envio de spams, inclusive com propósito de vender Informações Pessoais do Usuário (como definido na [Declaração de privacidade do GitHub](/articles/github-privacy-statement)) para, por exemplo, recrutadores, headhunters e anúncios de empregos. +Scraping refere-se à extração de informações do nosso Serviço por meio de um processo automatizado, como um bot ou webcrawler. Scraping não se refere à coleta de informações por meio de nossa API. Por favor, consulte a Seção H de nossos [Termos de Serviço](/articles/github-terms-of-service#h-api-terms) para nossos Termos da API. -Todo uso de dados coletados por meio de scraping (raspagem) devem estar de acordo com a [Declaração de privacidade do GitHub](/articles/github-privacy-statement). +Você não pode usar as informações do Serviço (quer seja por meio de raspagem, coletadas através da nossa API ou obtidas de outra forma) para spam, incluindo para fins de envio de e-mails não solicitados a usuários ou venda de Informações Pessoais do Usuário (conforme definido na [Declaração de Privacidade do GitHub](/github/site-policy/github-privacy-statement)), tais como recrutadores, headhunters e quadros de emprego. + +Seu uso de informações do Serviço deve estar em conformidade com a [Declaração de Privacidade do GitHub](/github/site-policy/github-privacy-statement). ### 6. Privacidade Uso indevido de Informações Pessoais é proibido. diff --git a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md index dda56088e1..4321e8fb88 100644 --- a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md +++ b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md @@ -4,13 +4,13 @@ versions: free-pro-team: '*' --- -Entrada em vigor desta versão: 1 de novembro de 2020 +Entrada em vigor desta versão: 13 de novembro de 2020 -Quando você cria uma Conta, tem acesso a vários recursos e produtos diferentes que fazem parte do Serviço. Como muitos desses recursos e produtos oferecem diferentes funcionalidades, eles podem exigir termos e condições adicionais específicos para esse recurso ou produto. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. +Quando você cria uma Conta, tem acesso a vários recursos e produtos diferentes que fazem parte do Serviço. Como muitos desses recursos e produtos oferecem diferentes funcionalidades, eles podem exigir termos e condições adicionais específicos para esse recurso ou produto. Abaixo, listamos esses recursos e produtos, juntamente com os termos adicionais correspondentes que se aplicam ao uso deles. -Your use of the Service is subject to your applicable terms (the "Agreement"). By using additional products and features, you also agree to these Additional Product Terms. Any violation of the Additional Product Terms is a violation of the Agreement. Capitalized terms not defined in the Additional Product Terms will have the meaning given to them in the Agreement. +Sua utilização do Serviço está sujeita a seus termos aplicáveis (o "Contrato"). Ao usar produtos e recursos adicionais, você também concorda com estes Termos de Produtos Adicionais. Qualquer violação dos Termos de Produtos Adicionais significa uma violação do Contrato. Os termos em maiúscula não definidos nos Termos de Produtos Adicionais terão o significado que lhes é atribuído no Contrato. -If you are using GitHub AE, then you may only access the following features and products: Third Party Integrations, Git LFS Support, Pages. +Se você estiver usando o GitHub AE, você só poderá acessar os seguintes recursos e produtos: Integrações de Terceiros, Suporte LFS do Git, Páginas. ### 1. Marketplace @@ -39,14 +39,14 @@ Se você ativar o Git Large File Storage ("Git LFS") em sua Conta, poderá busca ### 4. Pages -Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). Este serviço de hospedagem destina-se a hospedar páginas da web estáticas para todos os Usuários, mas principalmente, como uma vitrine para projetos pessoais e organizacionais. Alguns esforços de monetização são permitidos no Pages, como botões de doação e links para crowdfunding. +Cada Conta vem com acesso a [serviços de hospedagem estática do GitHub Pages](/github/working-with-github-pages/about-github-pages). Este serviço de hospedagem destina-se a hospedar páginas da web estáticas para todos os Usuários, mas principalmente, como uma vitrine para projetos pessoais e organizacionais. Alguns esforços de monetização são permitidos no Pages, como botões de doação e links para crowdfunding. O GitHub Pages está sujeito a limites específicos de uso e largura de banda e pode não ser apropriado para alguns usos elevados de largura de banda ou outros usos proibidos. Consulte nossas [diretrizes do GitHub Pages](/github/working-with-github-pages/about-github-pages) para obter mais informações. O GitHub se reserva o direito de recuperar qualquer subdomínio GitHub sem responsabilidade. ### 5. Ações e Pacotes #### a. Uso das Ações -As Ações GitHub permitem criar fluxos de trabalho personalizados do ciclo de vida de desenvolvimento de softwares diretamente no seu repositório GitHub. Cada Conta vem com quantidades de computação e armazenamento incluídas para uso com Ações, dependendo do seu plano de conta, que podem ser encontradas na [documentação de Ações](/actions). Your Actions compute usage is displayed within [your account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. Se você deseja usar ações além das quantidades incluídas, poderá [permitir excedentes](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions). +As Ações GitHub permitem criar fluxos de trabalho personalizados do ciclo de vida de desenvolvimento de softwares diretamente no seu repositório GitHub. Cada Conta vem com quantidades de computação e armazenamento incluídas para uso com Ações, dependendo do seu plano de conta, que podem ser encontradas na [documentação de Ações](/actions). O uso de computação de suas Ações está disponível em [suas configurações da sua Conta](https://github.com/settings/billing), e você será notificado por e-mail antes de atingir o limite das quantidades incluídas. Se você deseja usar ações além das quantidades incluídas, poderá [permitir excedentes](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions). O uso da computação para quantidades incluídas e pagas é calculado em minutos, com base no tipo de Ações que você executa (por exemplo, Linux, Windows, macOS). Os minutos usados ​​para cada trabalho ou tarefa da Ação serão arredondados para o minuto mais próximo. Para quantidades incluídas e dependendo do tipo de Ação, um multiplicador pode ser aplicado à quantidade de tempo usada para executar cada tarefa ou trabalho, antes de ser arredondada para o minuto mais próximo. Minutos excedentes são cobrados na [base de preço por minuto](https://github.com/features/actions) nos tipos de Ações que você executa. Ações e Pacotes compartilham armazenamento e seu uso de armazenamento é mostrado nas [configurações de conta](https://github.com/settings/billing). Para obter informações adicionais sobre os cálculos de uso de quantidade incluída, consulte a [documentação de Ações](/actions). @@ -62,9 +62,9 @@ Para evitar violações dessas limitações e abuso de Ações do GitHub, o GitH #### b. Uso do pacotes Os Pacotes GitHub podem ser usados ​​para baixar, publicar e gerenciar pacotes de Conteúdo. Cada plano de Conta vem com uma largura de banda e quantidade de armazenamento incluídos para o uso com Pacotes, que podem ser encontrados na [documentação dos Pacotes](/github/managing-packages-with-github-package-registry/about-github-package-registry). Ações e Pacotes compartilham o armazenamento entre dois recursos de Serviço. O armazenamento e o uso da largura de banda são exibidos dentro de suas [configurações de conta](https://github.com/settings/billing), e você será notificado por e-mail antes de atingir o limite de suas quantidades incluídas. Se você quiser usar Pacotes além de suas quantidades de largura de banda e armazenamento incluídos, então você pode [permitir excedentes](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages). -O uso da largura de banda é calculado com base na quantidade de dados transferidos de seus repositórios por meio de Pacotes, mas as transferências de pacote por meio de Ações não contarão para suas quantidades incluídas ou pagas. Packages bandwidth usage is limited by the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), and included bandwidth quantities are determined by your [account plan](https://github.com/pricing). +O uso da largura de banda é calculado com base na quantidade de dados transferidos de seus repositórios por meio de Pacotes, mas as transferências de pacote por meio de Ações não contarão para suas quantidades incluídas ou pagas. O uso da largura de banda dos pacotes é limitado pela [Política de Uso Aceitável](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), e a quantidade de largura de banda incluída é determinada por seu [plano de Conta](https://github.com/pricing). -O uso de armazenamento pelas Ações e Pacotes é compartilhado entre os dois recursos de Serviço. O uso do armazenamento é calculado como uma média ponderada ao longo do mês e não é redefinido a cada mês. Public and private repositories have different included storage quantities, and the included quantities for private repositories depend on your [account plan](https://github.com/pricing). +O uso de armazenamento pelas Ações e Pacotes é compartilhado entre os dois recursos de Serviço. O uso do armazenamento é calculado como uma média ponderada ao longo do mês e não é redefinido a cada mês. Os repositórios públicos e privados têm diferentes quantidades de armazenamento incluídas, e as quantidades incluídas para repositórios privados dependem de seu [plano de Conta](https://github.com/pricing). #### c. Pagamento e Faturamento para Ações e Pacotes O faturamento de Ações e Pacotes é baseado no uso. Quantidades adicionais de Ações ou Pacotes não podem ser adquiridos separadamente. Para clientes com cobrança mensal, é necessário ter um método de pagamento registrado para optar por pagar por quantidades adicionais desses recursos do Serviço. Você será cobrado mensalmente, com base no seu uso no mês anterior, a menos que seja cobrado por fatura. Para clientes faturados, você deve pagar as taxas no prazo de trinta (30) dias a contar da data da fatura do GitHub. Para os clientes que pagam antecipadamente os excedentes dos recursos de Serviço, os minutos pré-pagos não utilizados não serão transferidos para o próximo período de cobrança e não serão reembolsados. @@ -81,7 +81,7 @@ Você pode definir um limite mensal de gastos em suas [configurações de conta] ### 7. Connect -In order to access GitHub Connect, Customer must have at least one (1) Account on GitHub.com and one (1) licensed instance of the Software. Customer's access to and use of github.com through Connect is governed by its Agreement applicable to its use of the Service. O GitHub Connect pode ser usado para executar tarefas automatizadas. Além disso, vários Usuários podem direcionar determinadas ações com o GitHub Connect. Customer is responsible for actions that are performed on or through its Accounts. O GitHub pode coletar informações sobre o modo como o Cliente usa o GitHub Connect para fornecer e aprimorar o recurso. By using GitHub Connect, Customer authorizes GitHub to collect protected data, which includes Private Repository data and User Personal Information (as defined in the GitHub Privacy Statement), from Customer’s Accounts. O Cliente também autoriza a transferência de informações de instância de identificação para o GitHub por meio do GitHub Connect, cujas informações são regidas pela Declaração de privacidade do GitHub. +Para acessar o GitHub Connect, o Cliente deve ter pelo menos 1 (uma) conta no GitHub.com e 1 (uma) instância licenciada do Software. O acesso e uso do cliente ao github.com através do Connect é regido pelo seu Contrato aplicável ao uso do Serviço. O GitHub Connect pode ser usado para executar tarefas automatizadas. Além disso, vários Usuários podem direcionar determinadas ações com o GitHub Connect. O Cliente é responsável pelas ações realizadas em suas contas ou por meio delas. O GitHub pode coletar informações sobre o modo como o Cliente usa o GitHub Connect para fornecer e aprimorar o recurso. Ao usar o GitHub Connect, o Cliente autoriza o GitHub a coletar dados protegidos, que incluem dados de Repositório privado e Informações Pessoais do usuário (conforme definido na Declaração de Privacidade do GitHub), nas contas do Cliente. O Cliente também autoriza a transferência de informações de instância de identificação para o GitHub por meio do GitHub Connect, cujas informações são regidas pela Declaração de privacidade do GitHub. ### 8. Programa Sponsors @@ -89,7 +89,7 @@ Para se tornar um Desenvolvedor Patrocinado, você deve concordar com os [Termos ### 9. Segurança Avançada GitHub -A Segurança Avançada GitHub permite identificar vulnerabilidades de segurança por meio de análise de código semântica personalizável e automatizada. A Segurança Avançada GitHub é licenciada na base por usuário. Se você está usando a Segurança Avançada GitHub como parte do GitHub Enterprise Cloud, muitos recursos da Segurança Avançada GitHub, incluindo a varredura automatizada de códigos de repositórios privados, também exigem o uso das GitHub Actions. O faturamento para o uso das GitHub Actions é baseado no uso e está sujeito aos [Termos das GitHub Actions](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages). +O GitHub Advanced Security é licenciado com base em "Committer único". Um "Committer único" é um usuário licenciado do GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, ou GitHub AE, que criou um commit de código nos últimos 90 dias para qualquer repositório que tivesse qualquer recurso de Advanced Security do GitHub ativado. Você deve adquirir uma licença de Usuário GitHub Advanced Security para cada um dos seus Commiters únicos. Você só pode usar o GitHub Advanced Security em códigos desenvolvidos por ou para você. Se você está usando a Segurança Avançada GitHub como parte do GitHub Enterprise Cloud, muitos recursos da Segurança Avançada GitHub, incluindo a varredura automatizada de códigos de repositórios privados, também exigem o uso das GitHub Actions. ### 10. Dependabot Preview @@ -108,4 +108,3 @@ Precisamos do direito de submeter suas contribuições para o Banco de Dados Con #### b. Licença para o Banco de Dados Consultivo GitHub O Banco de Dados Consultivo GitHub está licenciado sob a [licença 4.0 Creative Commons Attribution](https://creativecommons.org/licenses/by/4.0/). O termo de atribuição pode ser cumprido linkando para o Banco de Dados Consultivo do GitHub em ou para registros individuais do Banco de Dados Consultivo do GitHub usado e prefixado por . - diff --git a/translations/pt-BR/content/github/site-policy/github-ae-data-protection-agreement.md b/translations/pt-BR/content/github/site-policy/github-ae-data-protection-agreement.md index 09a7580278..77b0431692 100644 --- a/translations/pt-BR/content/github/site-policy/github-ae-data-protection-agreement.md +++ b/translations/pt-BR/content/github/site-policy/github-ae-data-protection-agreement.md @@ -1,5 +1,5 @@ --- -title: GitHub AE Data Protection Agreement +title: Contrato de Proteção de Dados do GitHub AE versions: free-pro-team: '*' redirect_from: @@ -10,57 +10,57 @@ Entrada em vigor desta versão: 1 de novembro de 2020 ## INTRODUÇÃO -The parties agree that the GitHub AE Data Protection Agreement and Security Exhibit (together, the “**Data Protection Agreement**” or “**DPA**”) set forth obligations with respect to the processing and security of Customer Personal Data in connection with GitHub AE (the “**Online Service**”). GitHub makes the commitments in this DPA to all customers using the Online Service. +As partes concordam que o Acordo de Proteção de Dados e Anexo de Segurança (coletivamente, o **"Contrato de Proteção de Dados"** ou **"DPA"**) define obrigações no que diz respeito ao processamento e segurança dos Dados Pessoais do Cliente em conexão ao GitHub AE (o **"Serviço Online"**). O GitHub assume compromissos neste DPA perante todos os clientes que usam o Serviço On-line. -In the event of any conflict or inconsistency between the DPA and any other terms in Customer’s agreements with GitHub (“Agreement”), the DPA shall prevail. Para clareza, consistente com a Cláusula 10 das Cláusulas Contratuais Padrão no Anexo 1, as Cláusulas Contratuais Padrão prevalecem sobre quaisquer outros termos no DPA. +Na hipótese de qualquer conflito ou inconsistência entre o DPA e quaisquer outros termos nos acordos do Cliente com o GitHub ("Contrat"), prevalecerá o DPA. Para clareza, consistente com a Cláusula 10 das Cláusulas Contratuais Padrão no Anexo 1, as Cláusulas Contratuais Padrão prevalecem sobre quaisquer outros termos no DPA. -## GITHUB DATA PROTECTION AGREEMENT +## CONTRATO DE PROTEÇÃO DE DADOS DO GITHUB ### 1. Definições. -1.1 “**Applicable Data Protection Laws**” means certain laws, regulations, regulatory frameworks, or other legislations relating to the processing and use of Customer Personal Data, as applicable to Customer’s use of the Online Services, including: +1.1 "**Leis de Proteção de Dados Aplicáveis**" significa determinadas leis, regulamentações, marcos regulatórios ou outras legislações relacionadas ao processamento e uso de Dados Pessoais do Cliente, conforme aplicável ao uso dos Serviços Online pelo Cliente, incluindo: - a. The EU General Data Protection Regulation 2016/679 (“**GDPR**”), along with any implementing or corresponding equivalent national laws or regulations; and + a. O Regulamento Geral sobre a Proteção de Dados da UE 2016/679 (**“GDPR”**), junto com quaisquer leis ou regulamentos nacionais equivalentes ou em implementação; e b. A Lei de Privacidade do Consumidor da Califórnia de 2018, Cal. Civ. Código §§1798.100 et seq. ("**CCPA**"). -1.2 “**Controller**,” “**Data Subject**,” “**Member State**,” “**Personal Data**,” “**Personal Data Breach**,” “**Processing**,” “**Processor**,” and “**Supervisory Authority**” have the meanings given to them in the Applicable Data Protection Laws. Em caso de conflito, os significados atribuídos no GDPR serão substituídos. +1.2 Os termos "**Controlador**", "**Titular de dados**", "**Estado-membro**", "**Dados pessoais**", "**Violação de dados pessoais**", "**Processamento**", "**Processador**" e "**Autoridade de supervisão**" têm os significados atribuídos a eles nas Leis de Proteção de Dados aplicáveis. Em caso de conflito, os significados atribuídos no GDPR serão substituídos. -1.3 “**Customer Personal Data**” means any Personal Data for which Customer is a Controller, whether supplied by Customer for processing by GitHub or generated by GitHub in the course of performing its obligations under the Agreement. Inclui dados como informações de cobrança, endereços IP, endereços de e-mail corporativos e quaisquer outros Dados pessoais dos quais o Cliente seja Controlador. +1.3 O termo "**Dados Pessoais do Cliente**" significa quaisquer Dados Pessoais dos quais o Cliente seja Controlador, independentemente de serem fornecidos pelo Cliente para processamento pelo GitHub ou gerados pelo GitHub durante a execução de suas obrigações previstas no Contrato. Inclui dados como informações de cobrança, endereços IP, endereços de e-mail corporativos e quaisquer outros Dados pessoais dos quais o Cliente seja Controlador. -1.4 “**Customer Repository Data**” means any data or information that is uploaded or created by Customer into any of its Private Repositories. +1.4 O termo "**Dados de Repositório do Cliente**" significa quaisquer dados ou informações que sejam carregados ou criados pelo Cliente em qualquer um dos seus Repositórios Privados. -1.5 “**Data Breach**” means a Personal Data Breach or any other confirmed or reasonably suspected breach of Customer’s Protected Data. +1.5 "**Violação de dados**" significa uma Violação de Dados Pessoais ou qualquer outra violação confirmada ou razoavelmente suspeita dos Dados Protegidos do Cliente. -1.6 “**GitHub Legitimate Business Operations**” consist of the following, each as incident to delivery of the Service to Customer: (1) internal reporting and business modeling; (2) combating fraud, cybercrime, or cyber-attacks that may affect GitHub; (3) improving the core functionality of accessibility or privacy; and (4) financial reporting and compliance with legal obligations. +1.6 O termo “**Operações Comerciais Legítimas GitHub**” consiste no seguinte, cada uma como incidente na entrega do Serviço ao Cliente: (1) relatório interno e modelagem de negócios; (2) combate à fraude, crime cibernético ou ataques cibernéticos que podem afetar o GitHub; (3) melhoria da funcionalidade principal da acessibilidade ou privacidade; e (4) relatórios financeiros e de conformidade com obrigações legais. -1.7 “**End User**” means the Customers’ End Users such as employees, contractors, or collaborators. +1.7 “**Usuário Final**significa os usuários finais do cliente, tais como funcionários, contratantes ou colaboradores. -1.8 “**Permitted Purposes**” for data processing are those limited and specific purposes of providing the Online Service as set forth in the Agreement and this DPA, or the purposes for which a Data Subject has authorized the use of Customer Personal Data. +1.8 "**Finalidades permitidas**" para processamento de dados são aquelas finalidades limitadas e específicas para o fornecimento do Serviço Online, conforme estabelecido no Contrato e nesta DPA, ou as finalidades para as quais um Titular de Dados autorizou o uso de Dados Pessoais do Cliente. -1.9 “**Protected Data**” includes any Customer Personal Data and any Customer Repository Data processed by GitHub on behalf of Customer under the Agreement. +1.9 O termo "**Dados Protegidos**" inclui quaisquer Dados Pessoais do Cliente e Dados de Repositório do Cliente processados pelo GitHub em nome do Cliente sob este Contrato. -1.10 “**Sensitive Data**” means any Personal Data revealing racial or ethnic origin; political opinions, religious or philosophical beliefs or trade union membership; processing of genetic data or biometric data for the purposes of uniquely identifying a natural person; data concerning health, a natural person’s sex life or sexual orientation; and data relating to offences, criminal convictions, or security measures. +1.10 O termo "**Dados Sensíveis**" significa quaisquer Dados Pessoais que revelem origem racial ou étnica; opiniões políticas, crenças religiosas ou filosóficas ou filiação sindical; processamento de dados genéticos ou biométricos para identificar uma pessoa natural de forma inequívoca; dados relativos à saúde, à orientação ou à vida sexual de uma pessoa física e dados relativos a infrações, condenações penais ou medidas de segurança. ## 2. Status e conformidade. #### 2.1 Processamento de dados. -GitHub acts as a Processor in regard to any Customer Personal Data it receives in connection with the Agreement, except where Customers acts as a Processor (in which case GitHub is a subprocessor). GitHub will process Customer Personal Data only for Permitted Purposes in accordance with Customer’s instructions as represented by the Agreement and other written communications. In the event that GitHub is unable to comply with Customer’s instructions, such as due to conflicts with the Applicable Data Protection Laws, or where processing is required by the Applicable Data Protection Laws or other legal requirements, GitHub will notify Customer to the extent permissible. GitHub processes all Customer Personal Data in the United States or in the European Union; however, GitHub’s subprocessors may process data outside of the United States or the European Union. Além disso, o GitHub atua como Processador para Dados de repositório do cliente. +O GitHub atua como um Processador em relação a quaisquer Dados Pessoais do Cliente que recebe relativos ao Contrato, exceto onde os Clientes atuam como Processadores (caso em que o GitHub é um subprocessador). O GitHub processará os Dados Pessoais do Cliente somente para fins permitidos, de acordo com as instruções do Cliente, conforme o Contrato e outras comunicações escritas. Caso o GitHub não consiga cumprir as instruções do Cliente (por exemplo, devido a conflitos com as Leis de Proteção de Dados aplicáveis ou quando o processamento é exigido pelas Leis de Proteção de Dados aplicáveis ou outros requisitos legais), o GitHub notificará o Cliente desde que permitido. Embora o GitHub processe todos os Dados Pessoais do Cliente nos Estados Unidos ou na União Europeia, os subprocessadores do GitHub podem processar dados fora dos Estados Unidos ou da União Europeia. Além disso, o GitHub atua como Processador para Dados de repositório do cliente. #### 2.2 Controladores de dados. -Customer is a Controller only for the Customer Personal Data it transfers directly to GitHub or through the use of the Online Service except: (a) when Customer acts as a Processor of Customer Personal Data (in which case GitHub is a subprocessor); or (b) to the extent GitHub uses or otherwise processes Customer Personal Data for GitHub’s Legitimate Business Operations. In which case, GitHub will comply with the obligation of an independent data controller under GDPR for such use. +O Cliente é um Controlador somente para os Dados Pessoais do Cliente que transfere diretamente para o GitHub ou por meio do uso do Serviço On-line, exceto: (a) quando o Cliente age como Processador de Dados Pessoais do Cliente (nesse caso, o GitHub é um subprocessador); ou (b) na medida em que o GitHub usa ou de outra forma processa Dados Pessoais do Cliente para as Operações Comerciais Legítimas do GitHub. Nesse caso, o GitHub irá cumprir com as obrigações de um controlador de dados independente conforme a GDPR as define para esse fim. #### 2.3 Conformidade do GitHub; transferências de dados. O GitHub cumprirá as Leis de proteção de dados aplicáveis em relação ao processamento de Dados pessoais. -All transfers of Customer Personal Data out of the European Union, European Economic Area, United Kingdom, and Switzerland to provide the Online Service shall be governed by the Standard Contractual Clauses in Attachment 1 (Standard Contractual Clauses). +Todas as transferências de dados pessoais do cliente para fora da União Europeia, Espaço Econômico Europeu, Reino Unido e a Suíça para fornecer o Serviço On-line serão regidas pelas Cláusulas Contratuais Padrão no Anexo 1 (Cláusulas Contratuais Padrão). -GitHub will abide by the requirements of European Economic Area and Swiss data protection law regarding the collection, use, transfer, retention, and other processing of Personal Data from the European Economic Area, United Kingdom, and Switzerland. All transfers of Personal Data to a third country or an international organization will be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. +O GitHub cumprirá os requisitos do Espaço Econômico Europeu e da legislação suíça de proteção de dados referente à coleta, uso, transferência, retenção e outro tipo de processamento de Dados Pessoais do Espaço Econômico Europeu, Reino Unido e Suíça. Todas as transferências de Dados Pessoais para um país terceiro ou uma organização internacional estarão sujeitas às salvaguardas apropriadas, conforme descrito no Artigo 46 do RGPD e tais transferências e salvaguardas serão documentadas de acordo com o Artigo 30(2) do RGPD. Além disso, o GitHub é certificado na relação entre UE e EUA. e entre a Suíça e os EUA. Estruturas de Escudo de Privacidade e os compromissos que elas implicam, embora o GitHub não dependa da relação entre a UE e os EUA. Estrutura do Escudo de Privacidade como base jurídica para transferências de Dados Pessoais à luz do acórdão do Tribunal de Justiça da UE no processo C-311/18. O GitHub concorda em notificar o Cliente se determinar que não pode mais cumprir sua obrigação de fornecer o mesmo nível de proteção exigido pelos princípios do Escudo de Privacidade. -#### 2.4 Data Subject Rights; Assistance with Requests. -GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Customer Personal Data, the ability to fulfill data subject requests to exercise their rights under the Applicable Data Protection Laws, such as GDPR and CCPA. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights in connection with the Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality or documentation provided by the Online Service. GitHub shall comply with reasonable requests by Customer to assist with Customer’s response to such a data subject request. +#### 2.4 Direitos do Titular de Dados; Assistência com Solicitações. +O GitHub vai disponibilizar ao Cliente, de forma consistente com a funcionalidade do Serviço Online e com o papel do GitHub como processador de Dados Pessoais do Cliente, a possibilidade de atender aos pedidos do titular de dados que desejem exercer seus direitos sob as leis de proteção de dados aplicáveis, como a GDPR e o CCPA. Se o GitHub recebe uma solicitação do titular dos dados do Cliente para o exercício de um ou mais direitos relacionados ao Serviço Online para o qual o GitHub é um processador de dados ou subprocessador, o GitHub irá redirecionar o titular de dados para que sua solicitação seja feita diretamente ao Cliente. O Cliente será responsável por responder a qualquer solicitação, incluindo, quando necessário, a utilização da funcionalidade ou da documentação fornecida pelo Serviço On-line. O GitHub atenderá às solicitações justas do Cliente para auxiliar na resposta do Cliente a tal solicitação do titular de dados. ### 3. Proteção de dados. @@ -68,72 +68,72 @@ GitHub will make available to Customer, in a manner consistent with the function O GitHub processará e comunicará os Dados Protegidos apenas para as Finalidades Permitidas, a menos que as Partes concordem, por escrito, com uma finalidade expandida. #### 3.2 Qualidade de Dados e Proporcionalidade. -O GitHub manterá os dados pessoais do Cliente precisos e atualizados, ou habilitará o Cliente a fazê-lo. GitHub will take commercially reasonable steps to ensure that any Protected Data it collects on Customer’s behalf is adequate, relevant, and not excessive in relation to the purposes for which it is transferred and processed. In no event will GitHub intentionally collect Sensitive Data on Customer’s behalf. Customer agrees that the Online Service are not intended for the storage of Sensitive Data; if Customer chooses to upload Sensitive Data to the Online Service, Customer must comply with Article 9 of the GDPR, or equivalent provisions in the Applicable Data Protection Laws. +O GitHub manterá os dados pessoais do Cliente precisos e atualizados, ou habilitará o Cliente a fazê-lo. O GitHub tomará medidas comercialmente razoáveis para garantir que os Dados protegidos que ele colete em nome do Cliente sejam adequados, relevantes e não excessivos em relação às finalidades para as quais são transferidos e processados. Em nenhuma hipótese, o GitHub coletará intencionalmente Dados confidenciais em nome do Cliente. O Cliente concorda que o Serviço Online não se destina ao armazenamento de Dados Confidenciais. Se o Cliente optar por fazer upload de Dados Confidenciais ao Serviço Online, o Cliente deverá cumprir o Artigo 9 da GDPR ou disposições equivalentes nas Leis de Proteção de Dados aplicáveis. #### 3.3 Retenção e Exclusão de Dados. -Upon Customer’s reasonable request, unless prohibited by law, GitHub will return, destroy, or deidentify all Customer Personal Data and related data at all locations where it is stored after it is no longer needed for the Permitted Purposes within thirty days of request. O GitHub pode reter Dados pessoais do cliente e dados relacionados, apenas na medida exigida pelas Leis de proteção de dados aplicáveis e durante o período estipulado por elas, desde que assegure que os Dados pessoais do cliente serão processados somente conforme necessário para a finalidade especificada nas Leis de proteção de dados aplicáveis e que os Dados pessoais do cliente permaneçam protegidos pelas Leis de proteção de dados aplicáveis. +Mediante solicitação razoável do Cliente, a menos que proibido por lei, o GitHub devolverá, destruirá ou desidentificará todos os Dados pessoais do cliente e dados relacionados em todos os locais onde estejam armazenados, depois que não forem mais necessários para as finalidades permitidas, no prazo de 30 (trinta) dias após a solicitação. O GitHub pode reter Dados pessoais do cliente e dados relacionados, apenas na medida exigida pelas Leis de proteção de dados aplicáveis e durante o período estipulado por elas, desde que assegure que os Dados pessoais do cliente serão processados somente conforme necessário para a finalidade especificada nas Leis de proteção de dados aplicáveis e que os Dados pessoais do cliente permaneçam protegidos pelas Leis de proteção de dados aplicáveis. #### 3.4 Processamento de dados. -GitHub provides the following information, required by Article 28(3) of the GDPR, regarding its processing of Customer’s Protected Data: +No que diz respeito ao processamento de Dados Protegidos do Cliente, o GitHub fornece as informações a seguir, exigidas pelo artigo 28(3) do GPDR: -a. *The subject matter and duration of the processing* of Customer Personal Data are set out in the Agreement and the DPA. +a. *O assunto e a duração do processamento* de Dados Pessoais do Cliente estão definidos no Contrato e na DPA. -b. *The nature and purpose of the processing* of Customer Personal Data is described in Section 3.1 of the DPA. +b. *A natureza e a finalidade do processamento* de Dados Pessoais do Cliente estão descritos na Seção 3.1 da DPA. -c. *The types of Customer Personal Data to be processed* are described in the Agreement, and include Customer Personal Data; or any type of Personal Data that Customer elects to include in Customer Personal Data. Customer may choose to supply GitHub with additional Customer Personal Data, such as in Customer’s profile settings or by uploading Customer Personal Data to its GitHub repositories. +c. *Os tipos de Dados Pessoais do Cliente a serem processados* são descritos no Contrato e incluem os Dados Pessoais do Cliente; ou qualquer tipo de Dados Pessoais que o Cliente escolha incluir nos Dados Pessoais do Cliente. O Cliente pode optar por fornecer ao GitHub outros Dados Pessoais do Cliente; por exemplo, nas configurações de perfil do Cliente ou ao fazer upload de Dados Pessoais do Cliente para os repositórios do GitHub. d. *As categorias de Titular de dados aos quais estão relacionados os Dados pessoais do cliente* são o próprio Cliente e seus Usuários finais. -e. *The obligations and rights of Customer* are set out in the Agreement and the DPA. +e. *As obrigações e os direitos do Cliente* estão previstos no Contrato e na DPA. ### 4. Obrigações de auditoria e segurança. #### 4.1 medidas de segurança técnicas e organizacionais. -Levando em consideração o que há de mais moderno, os custos de implementação e a natureza, o escopo, o contexto e as finalidades do processamento, bem como o risco de probabilidade e gravidade variadas para direitos e liberdades fundamentais das pessoas físicas, o GitHub implementará medidas técnicas e organizacionais para garantir um nível de segurança adequado contra os riscos (como destruição acidental ou ilegal, perda, alteração, divulgação ou acesso não autorizado) que se apresentam ao processar Dados Protegidos. O GitHub monitorará regularmente o cumprimento dessas medidas e continuará a tomar as providências apropriadas ao longo da vigência do Contrato. Please see Section 1.1 of the Security Exhibit (below) regarding GitHub’s responsibilities in relation to security safeguards. +Levando em consideração o que há de mais moderno, os custos de implementação e a natureza, o escopo, o contexto e as finalidades do processamento, bem como o risco de probabilidade e gravidade variadas para direitos e liberdades fundamentais das pessoas físicas, o GitHub implementará medidas técnicas e organizacionais para garantir um nível de segurança adequado contra os riscos (como destruição acidental ou ilegal, perda, alteração, divulgação ou acesso não autorizado) que se apresentam ao processar Dados Protegidos. O GitHub monitorará regularmente o cumprimento dessas medidas e continuará a tomar as providências apropriadas ao longo da vigência do Contrato. Consulte a Seção 1.1 do Anexo de Segurança (abaixo) relativa às responsabilidades do GitHub relacionadas a proteções de segurança. #### 4.2 - Resposta de incidente e notificação de violação. -GitHub will comply with the Information Security obligations in the Security Exhibit and the Applicable Data Protection Laws, including Data Breach notification obligations. Please see Section 1.2 of the Security Exhibit regarding GitHub’s responsibilities in relation to Data Breach response and notification. +O GitHub cumprirá as obrigações de Segurança da Informação no Anexo sobre Segurança e nas Leis de Proteção de Dados aplicáveis, incluindo obrigações sobre notificação de Violação de Dados. Consulte a Seção 1.2 do Anexo sobre Segurança para ler a respeito das responsabilidades do GitHub relacionadas a notificação e resposta à Violação de Dados. #### 4.3 Equipe do GitHub. -GitHub represents and warrants that it will take reasonable steps to ensure that all GitHub personnel processing Protected Data have agreed to keep the Protected Data confidential and have received adequate training on compliance with the DPA and the Applicable Data Protection Laws. +O GitHub declara e garante que tomará medidas razoáveis para assegurar que todos os funcionários do GitHub que processam Dados Protegidos concordem em manter a confidencialidade dos Dados Protegidos e recebam treinamento adequado sobre o cumprimento da DPA e das Leis de Proteção de Dados aplicáveis. #### 4.4 Registros. -O GitHub manterá registros escritos completos, precisos e atualizados de todas as categorias de atividades de processamento realizadas em nome do Cliente que contenham as informações exigidas nas Leis de Proteção de Dados aplicáveis. Desde que a assistência não arrisque a segurança do GitHub ou os direitos de privacidade de Titulares de dados individuais, o GitHub disponibilizará esses registros ao Cliente mediante solicitação conforme a necessidade; por exemplo, para ajudar o cliente a demonstrar conformidade com as Leis de proteção de dados aplicáveis. To learn more about GitHub’s requirements to provide assistance in the event of a security incident, please see Section 1.2 of the Security Exhibit. +O GitHub manterá registros escritos completos, precisos e atualizados de todas as categorias de atividades de processamento realizadas em nome do Cliente que contenham as informações exigidas nas Leis de Proteção de Dados aplicáveis. Desde que a assistência não arrisque a segurança do GitHub ou os direitos de privacidade de Titulares de dados individuais, o GitHub disponibilizará esses registros ao Cliente mediante solicitação conforme a necessidade; por exemplo, para ajudar o cliente a demonstrar conformidade com as Leis de proteção de dados aplicáveis. Para saber mais sobre os requisitos do GitHub para oferecer assistência no caso de um incidente de segurança, consulte a Seção 1.2 do Anexo sobre Segurança. #### 4.5 Relatório de conformidade. -GitHub will provide security compliance reporting in accordance with Section 2.3 of the Security Exhibit. Customer agrees that any information and audit rights granted by the Applicable Data Protection Laws (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will only arise to the extent that GitHub’s provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or Supervisory Authority audit. Section 3.1 of the Security Exhibit describes the Parties’ responsibilities in relation to a regulatory or Supervisory Authority audit. +O GitHub fornecerá relatórios de conformidade de segurança conforme a Seção 2.3 do Anexo de Segurança. O Cliente concorda que quaisquer informações e direitos de auditoria concedidos pelas Leis de Proteção de Dados aplicáveis (inclusive, quando aplicável, o Artigo 28(3)(h) da GDPR) serão satisfeitos por esses relatórios de conformidade e só surgirão na medida em que o provisionamento de um relatório de conformidade pelo GitHub não forneça informações suficientes ou na medida em que o Cliente precise responder a uma auditoria de Autoridade Supervisora ou regulatória. A Seção 3.1 do Anexo de Segurança descreve as responsabilidades das Partes em relação a uma auditoria da Autoridade Supervisora ou regulatória. #### 4.6 Assistência. -GitHub will provide reasonable assistance to Customer with concerns such as data privacy impact assessments, Data Subject rights requests, consultations with Supervisory Authorities, and other similar matters, in each case solely in relation to the processing of Customer’s Personal Data and taking into account the nature of processing. +O GitHub fornecerá a assistência cabível ao Cliente com preocupações como avaliações de impacto na privacidade de dados, solicitações de direitos de Titular de Dados, consultas com Autoridades de Supervisão e outros assuntos semelhantes, em todos os casos exclusivamente em relação ao processamento de Dados Pessoais do Cliente e levando em consideração a natureza do processamento. ### 5. Uso e divulgação de dados protegidos. -No Use in Marketing and CCPA. GitHub will not use the Protected Data for the purposes of advertising third-party content. If GitHub is processing Customer Personal Data within the scope of the CCPA, GitHub will not retain, use, or disclose that data for any purpose other than for the purposes set out in the DPA and as permitted under the CCPA, including under any “sale” exemption. In no event will GitHub sell any such data. +Sem uso em Marketing e CCPA. O GitHub não usará os Dados Protegidos para fins de publicidade de conteúdo de terceiros. Se o GitHub estiver processando os Dados Pessoais do Cliente dentro do escopo do CCPA, o GitHub não irá manter, usar, ou divulgar esses dados para qualquer finalidade que não seja para os fins definidos na DPA e permitidos sob o CCPA, incluindo qualquer isenção de "venda". Em nenhum caso, o GitHub venderá qualquer dado desse tipo. ### 6. Transferência progressiva e subprocessamento. #### 6.1 Proteção de Dados. -O GitHub é responsável por transferências progressivas de Dados Protegidos para seus subprocessadores, como o processador de pagamentos a terceiros. In the event that GitHub does transfer the Protected Data to a third-party subprocessor, or GitHub installs, uses, or enables a third party or third-party services to process the Protected Data on GitHub’s behalf, GitHub will ensure that the third-party subprocessor is bound by written agreement that requires them to provide at least the same level of confidentiality, security, and privacy protection as is required of GitHub by this DPA and the Applicable Data Protection Laws. +O GitHub é responsável por transferências progressivas de Dados Protegidos para seus subprocessadores, como o processador de pagamentos a terceiros. Na hipótese de o GitHub transferir os Dados Protegidos para um terceiro subprocessador ou na hipótese de o GitHub instalar, usar, ou permitir que terceiros ou serviços de terceiros processem os Dados Protegidos em nome do GitHub, o GitHub garantirá que o terceiro subprocessador seja vinculado por acordo escrito que exige que eles forneçam, pelo menos, o mesmo nível de confidencialidade, proteção de privacidade e segurança, conforme exigido do GitHub por esta DPA e pelas Leis de Proteção de Dados aplicáveis. #### 6.2 - Aceitação de Subprocessadores do GitHub. -Customer authorizes GitHub and its subprocesors to appoint and use subprocessors in accordance with this Section 6 and the Agreement. +O Cliente autoriza o GitHub e seus subprocessadores a designar e utilizar subprocessadores, de acordo com a Seção 6 e o Contrato. #### 6.3 Consentimento Geral para Subprocessamento progressivo. -Customer provides a general consent for GitHub to engage onward subprocessors, conditional on GitHub’s compliance with the following requirements: +O Cliente concede consentimento geral para que o GitHub utilize subprocessadores avançados, desde que haja conformidade do GitHub com os seguintes requisitos: -a. Any onward subprocessor must agree in writing to only process data in a country that the European Commission has declared to have an “adequate” level of protection; or to only process data on terms equivalent to the Standard Contractual Clauses, or pursuant to a Binding Corporate Rules approval granted by competent European data protection authorities, or pursuant to compliant and valid EU-US Privacy Shield and Swiss-U.S. Certificações do Escudo de Privacidade; e +a. Qualquer subprocessador avançado deve concordar por escrito em somente processar dados em países para os quais a Comissão Europeia tenha declarado como tendo um nível "adequado" de proteção ou somente processar dados em termos equivalentes às Cláusulas Contratuais Padrão, ou de acordo com uma autorização das Regras Corporativas Vinculativas concedidas pelas autoridades europeias de proteção de dados competentes ou conforme certificação válida do Privacy Shield entre a UE e os EUA e entre a Suíça e os EUA. Certificações do Escudo de Privacidade; e -b. GitHub will restrict the onward subprocessor’s access to Customer Personal Data only to what is strictly necessary to perform its services, and GitHub will prohibit the subprocessor from processing the Customer Personal Data for any other purpose. +b. O GitHub restringirá o acesso do subprocessador avançado a Dados Pessoais do Cliente apenas ao estritamente necessário para executar seus serviços e o GitHub proibirá o subprocessador de processar os Dados Pessoais do Cliente para qualquer outra finalidade. #### 6.4 - Divulgação de Acordos de Subprocessador. -GitHub maintains a list of onward subprocessors it has engaged to process Customer Personal Data on its website, including the categories of Customer Personal Data processed, a description of the type of processing the subprocessor performs, and the location of its processing. GitHub will, upon Customer’s written request, provide Customer with this list of subprocessors and the terms under which they process the Customer Personal Data. De acordo com as restrições de confidencialidade de subprocessadores, o GitHub pode remover informações confidenciais ou comercialmente confidenciais antes de fornecer a lista e os termos ao Cliente. Caso o GitHub não possa divulgar informações confidenciais ao Cliente, as Partes concordam que o GitHub fornecerá todas as informações razoavelmente possíveis relacionadas aos contratos de subprocessamento. +O GitHub mantém uma lista de subprocessadores avançados que utilizou para processar Dados Pessoais do Cliente em seu website, incluindo as categorias de Dados Pessoais do Cliente processados, uma descrição do tipo de processamento que o subprocessador executa e a localização do seu processamento. Mediante solicitação por escrito do Cliente, o GitHub fornecerá a ele esta lista de subprocessadores e os termos em que eles processarão os Dados Pessoais do Cliente. De acordo com as restrições de confidencialidade de subprocessadores, o GitHub pode remover informações confidenciais ou comercialmente confidenciais antes de fornecer a lista e os termos ao Cliente. Caso o GitHub não possa divulgar informações confidenciais ao Cliente, as Partes concordam que o GitHub fornecerá todas as informações razoavelmente possíveis relacionadas aos contratos de subprocessamento. #### 6.5 Objeção para subprocessadores. -GitHub will provide thirty days’ prior written notice of the addition or removal of any subprocessor, including the categories listed in Section 6.4, by announcing changes on its website. If Customer has a reasonable objection to GitHub’s engagement of a new subprocessor, Customer must notify GitHub promptly in writing. Where possible, GitHub will use commercially reasonable efforts to provide an alternative solution to the Online Services to avoid processing of data by the objectionable subprocessor. Caso o GitHub não consiga oferecer uma solução alternativa e as Partes não resolvam o conflito em 90 (noventa) dias, o Cliente poderá rescindir o Contrato. +O GitHub fornecerá aviso por escrito trinta dias antes da adição ou remoção de qualquer subprocessador, incluindo as categorias listadas na Seção 6.4 , anunciando mudanças no seu website. Se o Cliente tiver uma objeção razoável à utilização de um novo subprocessador pelo GitHub, o Cliente deverá notificar o GitHub prontamente por escrito. Sempre que possível, o GitHub envidará esforços comercialmente razoáveis para fornecer uma solução alternativa aos Serviços Online para evitar o processamento de dados pelo subprocessador questionável. Caso o GitHub não consiga oferecer uma solução alternativa e as Partes não resolvam o conflito em 90 (noventa) dias, o Cliente poderá rescindir o Contrato. ### 7. Rescisão. #### 7.1 Suspensão. -In the event that GitHub is in breach of its obligations to maintain an adequate level of security or privacy protection, Customer may temporarily suspend the transfer of all Customer Personal Data or prohibit collection and processing of Customer Personal Data on Customer’s behalf until the breach is repaired or the Agreement is terminated. +Na hipótese de o GitHub violar suas obrigações de manter um nível adequado de proteção de segurança ou privacidade, o Cliente poderá suspender temporariamente a transferência de todos os Dados Pessoais do Cliente ou proibir a coleta e o processamento dos seus Dados Pessoais em nome do Cliente até que a violação seja reparada ou o Contrato seja encerrado. #### 7.2 - Rescisão com motivo. Além dos direitos de rescisão que o Cliente tem previsto no Contrato, o Cliente poderá rescindir o Contrato sem prejuízo de qualquer outra reivindicação na lei ou na justiça caso: @@ -142,44 +142,44 @@ a. o GitHub notifique o cliente de que não pode mais cumprir suas obrigações b. a transferência, a coleta ou o processamento de todos os Dados pessoais do cliente tenha sido temporariamente suspenso por mais de um mês, de acordo com a Seção 7.1; -c. GitHub is in substantial or persistent breach of any warranties or representations under the DPA; +c. O GitHub esteja em violação substancial ou persistente de quaisquer garantias ou representações nesta DPA; d. o GitHub não esteja mais em atividade, seja dissolvido, entre em liquidação ou tenha uma ordem de liquidação feita em seu nome; ou e. o Cliente faça objeção a um subprocessador de acordo com a Seção 6.5, e o GitHub não tenha conseguido fornecer uma solução alternativa em até 90 (noventa) dias. #### 7.3 Violação. -Failure to comply with the material provisions of the DPA is considered a material breach under the Agreement. +A não observância das disposições materiais desta DPA é considerada uma violação material ao disposto no Contrato. #### 7.4 Não cumprimento. -In the event that changes in law or regulation render performance of the DPA impossible or commercially unreasonable, the Parties may renegotiate the DPA in good faith. Se a renegociação não corrigir a impossibilidade ou se as Partes não conseguirem chegar a um acordo, elas poderão rescindir o Contrato após 30 (trinta) dias. +Na hipótese de mudanças na lei ou na regulamentação tornarem o cumprimento da DPA impossível ou comercialmente impraticável, as Partes poderão renegociar a DPA de boa-fé. Se a renegociação não corrigir a impossibilidade ou se as Partes não conseguirem chegar a um acordo, elas poderão rescindir o Contrato após 30 (trinta) dias. #### 7.5 Notificação. -In the event that GitHub determines that it can no longer meet its privacy obligations under the DPA, GitHub will notify Customer in writing immediately. +Caso o GitHub determine que não pode mais cumprir as obrigações de privacidade previstas na DPA, o GitHub notificará o Cliente por escrito imediatamente. #### 7.6 Modificações. -GitHub may modify the DPA from time to time as required by the Applicable Data Protection Laws, with thirty days’ notice to Customer. +O GitHub pode modificar a DPA de tempos em tempos, conforme exigido pelas Leis de Proteção de Dados aplicáveis, com aviso prévio de 30 (trinta) dias ao Cliente. #### 7.7 Requisitos de rescisão. Após a rescisão, o GitHub deverá: a. tomar medidas razoáveis e apropriadas para interromper o processamento dos Dados pessoais do cliente; -b. within ninety days of termination, delete or deidentify any Customer Personal Data GitHub stores on Customer’s behalf pursuant to Section 3.3; and +b. dentro de 90 (noventa) dias após a rescisão, excluir ou desidentificar Dados Pessoais do Cliente que o GitHub armazene em nome do Cliente, de acordo com a Seção 3.3; e c. fornecer ao Cliente garantia razoável de que o GitHub cumpriu suas obrigações na Seção 7.7. ### 8. Responsabilidade pelo processamento de dados. #### 8.1 Limitações. -Except as limited by the Applicable Data Protection Laws, any claims brought under the DPA will be subject to the terms of the Agreement regarding Limitations of Liability. +Exceto quando limitado pelas Leis de Proteção de Dados aplicáveis, quaisquer reivindicações referentes à DPA estarão sujeitas aos termos do Contrato sobre Limitações de Responsabilidade. ## Anexo 1 – Cláusulas Contratuais Padrão (Processadores) -Execution of the Agreement by Customer includes execution of this Attachment 1 to the GitHub Data Protection Addendum, which is countersigned by GitHub, Inc. +A execução do Contrato pelo Cliente inclui a execução deste Anexo 1 referente ao Adendo de Proteção de Dados GitHub ratificado pelo GitHub, Inc. Em países onde a aprovação regulatória é necessária para o uso das Cláusulas Contratuais Padrão, estas não podem ser confiadas à Comissão Europeia 2010/87/UE (de fevereiro de 2010) para legitimar a exportação de dados do país, a menos que o Cliente tenha a aprovação regulatória necessária. -For the purposes of Article 46 (2) of the General Data Protection Regulation (EU 2016/679) for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub (as data importer, whose signature appears below), each a “party,” together “the parties”, have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. +Para efeitos do Artigo 46(2) do Regulamento Geral de Proteção de Dados (UE 2016/679) referente à transferência de dados pessoais para processadores estabelecidos em países terceiros que não garantem um nível adequado de proteção de dados, o Cliente (como exportador de dados) e o GitHub (como importador de dados, cuja assinatura aparece abaixo), cada um sendo a "parte" ou, coletivamente "as partes", concordaram com as seguintes Cláusulas Contratuais (as “Cláusulas” ou “Cláusulas Contratuais Padrão”) a fim de adjudicar salvaguardas adequadas no que diz respeito à proteção da privacidade e dos direitos e liberdades fundamentais dos indivíduos para a transferência por parte do exportador para o importador de dados pessoais especificados no Apêndice 1. #### Cláusula 1: Definições (a) "dados pessoais", "categorias especiais de dados", "processo/processamento", "controlador", "processador", "titular dos dados" e "autoridade de supervisão" terão o mesmo significado do Regulamento Geral sobre a Proteção de Dados (UE 2016/679) referente à proteção dos indivíduos no que se refere ao tratamento de dados pessoais e à livre circulação desses dados; @@ -281,7 +281,7 @@ O importador de dados não pode apoiar-se no descumprimento por um subprocessado 2. As partes concordam que a autoridade de supervisão tem o direito de realizar auditorias no importador de dados ou a qualquer subprocessador, que tenha o mesmo escopo e as mesmas condições das auditorias executadas no exportador de dados, em conformidade com a legislação de proteção de dados aplicável. -3. O importador de dados deve prontamente informar o exportador de dados sobre a existência de legislação aplicável sobre tal ato, e de qualquer subprocessador que previna a condução de uma auditoria ao importador de dados, ou qualquer subprocessador, em conformidade com o parágrafo 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5 (b). +3. O importador de dados deve prontamente informar o exportador de dados sobre a existência de legislação aplicável sobre tal ato, e de qualquer subprocessador que previna a condução de uma auditoria ao importador de dados, ou qualquer subprocessador, em conformidade com o parágrafo 2. Neste caso, o exportador de dados terá o direito de tomar as medidas previstas na Cláusula 5(b). #### Cláusula 9: Lei regente. As Cláusulas devem ser regidas pela lei do Estado-Membro onde o exportador de dados estiver estabelecido. @@ -308,7 +308,7 @@ Exportador de dados: Cliente é o exportador de dados. **Importador de dados:** O importador de dados é o GitHub, Inc., produtor global de software e serviços. -**Titulares dos dados:** Os titulares de dados incluem os representantes e usuários finais do exportador, incluindo funcionários, contratados, colaboradores e clientes do exportador de dados. Os titulares de dados também podem incluir indivíduos que tentam comunicar-se ou transferir informações pessoais aos usuários dos serviços fornecidos pelo importador de dados. GitHub acknowledges that, depending on Customer’s use of the Online Service, Customer may elect to include personal data from any of the following types of data subjects in the Customer Personal Data: +**Titulares dos dados:** Os titulares de dados incluem os representantes e usuários finais do exportador, incluindo funcionários, contratados, colaboradores e clientes do exportador de dados. Os titulares de dados também podem incluir indivíduos que tentam comunicar-se ou transferir informações pessoais aos usuários dos serviços fornecidos pelo importador de dados. O GitHub reconhece que, dependendo do uso do Serviço Online pelo Cliente, este pode optar por incluir dados pessoais de qualquer um dos tipos a seguir de titulares de dados nos Dados Pessoais do Cliente: - Empregados, contratados e trabalhadores temporários (atual, anterior, potencial) do exportador de dados; - Dependentes do acima; @@ -318,7 +318,7 @@ Exportador de dados: Cliente é o exportador de dados. - Partes interessadas ou indivíduos que interagem passivamente com o exportador de dados (por exemplo, porque são objeto de investigação, investigação ou mencionada em documentos ou correspondência de ou para o exportador de dados); ou - Profissionais com prestígio profissional (por exemplo, médicos, advogados, notários, trabalhadores religiosos, etc.). -**Categories of data:** The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Service. GitHub acknowledges that, depending on Customer’s use of the Online Service, Customer may elect to include personal data from any of the following categories in the Customer Personal Data: +**Categorias de dados:** Os dados pessoais transferidos incluídos em e-mails, documentos e outros dados de forma eletrônica no âmbito do Serviço Online. O GitHub reconhece que, dependendo do uso do Serviço Online pelo Cliente, este pode optar por incluir dados pessoais de qualquer uma das seguintes categorias nos Dados Pessoais do Cliente: - Dados de autenticação (por exemplo, nome de usuário, e-mail, senha); - Informações de contato (por exemplo, e-mail); - Números de identificação únicos e assinaturas (endereços IP, identificador único em cookies de rastreamento ou tecnologia similar). @@ -328,22 +328,22 @@ Exportador de dados: Cliente é o exportador de dados. No entanto, uma vez que o importador de dados fornece serviços de armazenamento e não controla as categorias de dados que armazena, o exportador de dados pode optar por transferir as categorias especiais de dados. Consequentemente, o exportador de dados é o único responsável por assegurar que cumpre todas as obrigações impostas por leis e regulamentos aplicáveis relativos à coleta e processamento de quaisquer categorias especiais de dados, incluindo a obtenção do consentimento explícito dos dados sujeitos antes de processar dados pessoais confidenciais. -**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at https://help.github.com/articles/github-privacy-statement/, and the “Data Processing” section of the DPA. +**Processamento de operações:** Os dados pessoais transferidos estarão sujeitos às seguintes atividades básicas de processamento: O GitHub usa dados pessoais para fins limitados definidos na Declaração de Privacidade do GitHub, disponível em https://help.github.com/articles/github-privacy-statement/, e a seção "Processamento de Dados" da DPA. -**Subcontractors:** In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Esses subcontratantes terão a permissão de obter Dados Pessoais do Cliente apenas para fornecer os serviços que o importador de dados os manteve para fornecer, e são proibidos de usar os Dados Pessoais do Cliente para qualquer outra finalidade. +**Subcontratantes:** De acordo com a DPA, o importador de dados pode contratar outras empresas para prestar serviços limitados em nome do importador de dados, tais como fornecer suporte ao cliente. Esses subcontratantes terão a permissão de obter Dados Pessoais do Cliente apenas para fornecer os serviços que o importador de dados os manteve para fornecer, e são proibidos de usar os Dados Pessoais do Cliente para qualquer outra finalidade. ### Apêndice 2 das Cláusulas Contratuais Padrão Descrição das medidas de segurança técnicas e organizacionais implementadas pelo importador de dados, de acordo com as Cláusulas 4(d) e 5(c): **1. Equipe.** A equipe do importador de dados não processará os Dados Pessoais do Cliente sem autorização. A equipe é obrigada a manter a confidencialidade de quaisquer Dados Pessoais do Cliente e essa obrigação permanece mesmo após o fim do compromisso. -**2. Data Privacy Contact.** The data privacy officer of the data importer can be reached at the following address: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA +**2. Contato de Privacidade de Dados.** Você pode entrar em contato com o encarregado da privacidade de dados do importador de dados no endereço abaixo: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA **3. Medidas técnicas e organizacionais.** O importador de dados implementou e manterá as medidas técnicas e organizacionais apropriadas, controles internos, rotinas de segurança de informações destinadas a proteger os Dados Pessoais do Cliente, conforme definido no Anexo de Segurança de segurança do GitHub, contra perdas acidentais, destruição ou alteração, divulgação ou acesso não autorizado; ou destruição ilegal da seguinte forma: medidas técnicas e organizacionais, controles internos, e as rotinas de segurança da informação estabelecidas no Anexo de Segurança do GitHub são incorporadas neste Apêndice 2 do presente documento a título de referência e são vinculadas ao importador de dados como se fossem definidas em inteiro teor neste Apêndice 2. A assinatura do GitHub, Inc. aparece abaixo. Assinatura das Cláusulas Contratuais Padrão, Apêndice 1 e Apêndice 2 em nome do importador de dados -![Screen Shot 2020-10-29 at 10 21 08 AM](https://user-images.githubusercontent.com/42984983/97613325-c93eda00-19d5-11eb-82e8-563267d1d738.png) +![Captura de tela 2020-10-29 às 10 21 08 AM](https://user-images.githubusercontent.com/42984983/97613325-c93eda00-19d5-11eb-82e8-563267d1d738.png) Lynn Hashimoto, Chefe da área de Produtos & Departamento jurídico regulatório @@ -354,18 +354,18 @@ GitHub, Inc. ### 1. Programa de segurança das informações. #### 1.1 Gerenciamento da segurança. -GitHub will implement and maintain appropriate technical and organizational measures to protect Customer Content and Protected Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, personal data transmitted, stored or otherwise processed (“**Security Program**”). Those measures shall be set forth in a GitHub Security Policy. GitHub will provide written descriptions of the security controls and other information reasonably requested by Customer regarding GitHub’s security practices and policies for the Online Service. +O GitHub implementará e manterá medidas técnicas e organizacionais apropriadas para proteger o Conteúdo do Cliente e Dados Protegidos contra destruição acidental ou ilegal, perda, alteração, divulgação não autorizada ou acesso a dados pessoais transmitidos, armazenados ou processados de outra forma (“**Programa de Segurança**”). Essas medidas serão definidas numa Política de Segurança do GitHub. O GitHub fornecerá descrições por escrito dos controles de segurança e outras informações razoavelmente solicitadas pelo Cliente sobre as práticas e políticas de segurança do GitHub para o Serviço Online. -a. Operational Policy. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Content and Protected Data. +a. Política Operacional. O GitHub mantém documentos de segurança descrevendo suas medidas de segurança e os procedimentos e responsabilidades relevantes de seus funcionários que têm acesso ao Conteúdo do Cliente e Dados Protegidos. -b. Security Training. GitHub informs its personnel about relevant security procedures and their respective roles. GitHub also informs its personnel of possible consequences of breaching the security rules and procedures. GitHub will only use anonymous data in training. +b. Treinamento de Segurança. O GitHub informa seus funcionários sobre os procedimentos de segurança relevantes e suas respectivas funções. O GitHub também informa seu pessoal sobre possíveis consequências de violação das regras e procedimentos de segurança. O GitHub só usará dados anônimos no treinamento. #### 1.2 Gerenciamento de incidentes de segurança. -GitHub will provide a Security incident management program for the Online Service as follows: +O GitHub fornecerá um programa de gestão de incidentes de Segurança para o Serviço Online da seguinte forma: a. a. Escalonamento e disponibilidade de segurança. O GitHub manterá os processos apropriados de escalonamento e contato de Segurança 24 horas por dia, 7 dias por semana, para garantir que clientes e funcionários possam enviar problemas para a equipe de Segurança do GitHub. -b. Resposta a incidentes. If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. +b. Resposta a incidentes. Se o GitHub tomar conhecimento de uma violação de segurança que leve a destruição acidental ou ilegal, perda, alteração, divulgação não autorizada ou acesso a Dados do Cliente ou Dados Pessoais (considerados individualmente como "Incidente de Segurança"), o GitHub irá, prontamente e sem demora indevida, (1) notificar o Cliente sobre o Incidente de Segurança; (2) investigar o Incidente de Segurança e fornecer ao Cliente informações detalhadas sobre o incidente; (3) tomar medidas razoáveis para atenuar os efeitos e minimizar os danos resultantes do Incidente de Segurança. c. Notificação. As notificações de Incidentes de segurança serão entregues a um ou mais administradores do Cliente por qualquer meio que o GitHub selecionar. É responsabilidade exclusiva do Cliente garantir que os administradores do Cliente monitorem e respondam a quaisquer notificações. O Cliente é o único responsável pelo cumprimento de suas obrigações perante as leis de notificação de incidentes aplicáveis ao Cliente e pelo cumprimento das obrigações de notificação de terceiros relacionadas a qualquer Incidente de segurança. @@ -374,14 +374,14 @@ d. Assistência razoável. O GitHub fará tudo o que for possível comercialmen #### 1.3 Devida diligência dos subcontratados e fornecedores. O GitHub manterá a devida diligência apropriada ao utilizar subcontratados e fornecedores. O GitHub guardará os relatórios de avaliação de fornecedores e qualquer trabalho de avaliação por um período mínimo de três anos. -#### 1.4 Physical and Environmental Safeguards. -a. Physical Access to Facilities. GitHub limits access to facilities where information systems that process Customer Content and Protected Data are located to identified authorized individuals. +#### 1.4 Salvaguardas Físicas e Ambientais. +a. Acesso físico às instalações. O GitHub limita o acesso a instalações onde os sistemas de informações que processam Conteúdo do Cliente e Dados Protegidos estão localizados a indivíduos autorizados identificados. -b. Physical Access to Components. GitHub maintains records of the incoming and outgoing media containing Customer Content and Protected Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Content and Protected Data they contain. +b. Acesso Físico aos Componentes. O GitHub mantém registros das mídias de entrada e de saída contendo Conteúdo do Cliente e Dados Protegidos, incluindo o tipo de mídia, os remetentes/destinatários autorizados, a data e a hora, o número de mídias e os tipos de Conteúdo do Cliente e Dados Protegidos que eles contêm. -c. Protection from Disruptions. GitHub uses industry standard systems to protect against loss of data due to power supply failure or line interference. +c. Proteção contra interferências. O GitHub usa sistemas padrão da indústria para proteger contra perda de dados devido à falha de fornecimento de energia ou interferência de linha. -#### 2. Requests for Information. +#### 2. Pedidos de informação. Mediante solicitação por escrito do Cliente e não mais de uma vez por ano, o GitHub responderá a um pedido de informação para avaliar as informações relacionadas ao risco de segurança e conformidade. A resposta será fornecida por escrito no prazo de 30 (trinta) dias a partir do recebimento do pedido, à espera dos esclarecimentos necessários sobre qualquer solicitação. #### 3. Cooperação com auditorias regulatórias. @@ -391,7 +391,7 @@ a. O Cliente deve garantir o uso de um terceiro independente (ou seja, o regulad b. A notificação de tal auditoria deve ser por escrito e fornecida ao GitHub em tempo hábil, aguardando notificação do regulador e de maneira a permitir que o pessoal adequado seja disponibilizado para ajudar. Quando os reguladores não avisarem com antecedência ao Cliente sobre a auditoria ou a investigação, o GitHub responderá no momento adequado, conforme exigido pelos reguladores. -c. Any third party auditor must disclose to GitHub any findings and recommended actions where allowed by the regulator. +c. Qualquer auditor terceirizado deve divulgar ao GitHub os resultados e as ações recomendadas, quando permitido pelo regulador. d. No caso de auditoria regulamentar, o acesso será permitido apenas durante o horário comercial normal (Hora do Pacífico). diff --git a/translations/pt-BR/content/github/site-policy/github-ae-product-specific-terms.md b/translations/pt-BR/content/github/site-policy/github-ae-product-specific-terms.md index d77bb8a78b..2d09d9f584 100644 --- a/translations/pt-BR/content/github/site-policy/github-ae-product-specific-terms.md +++ b/translations/pt-BR/content/github/site-policy/github-ae-product-specific-terms.md @@ -1,5 +1,5 @@ --- -title: GitHub AE Product Specific Terms +title: Termos específicos do produto do GitHub AE versions: free-pro-team: '*' redirect_from: @@ -8,51 +8,51 @@ redirect_from: Entrada em vigor desta versão: 1 de novembro de 2020 -The Agreement consists of these GitHub AE Product Specific Terms, the General Terms that Customer accepted, and any additional terms GitHub or its Affiliates present when an order is placed. +O Contrato é composto pelos presentes Termos Específicos de Produto do GitHub AE, pelos Termos Gerais que o Cliente aceitou e por quaisquer termos adicionais que o GitHub ou seus Afiliados apresentem quando um pedido é feito. -### 1. Accounts. +### 1. Contas. -**Account Responsibility.** Customer controls and is responsible for End User accounts and Content. +**Responsabilidade da Conta.** O cliente controla e é responsável pelas contas do usuário final e pelo conteúdo. -**Account Security.** Customer is responsible for maintaining the security of its account login credentials. +**Segurança da conta.** O cliente é responsável por manter a segurança de sua credenciais de login da conta. -**Use Policies.** Customer’s End Users must comply with the Acceptable Use Policy. +**Use Políticas.** Os usuários finais do cliente devem cumprir a Política de Uso Aceitável. -**Suspension.** GitHub may suspend use of the Online Service during any period of Customer’s material breach. +**Suspensão.** O GitHub pode suspender o uso do Serviço Online durante qualquer período de violação de material do cliente. -**Access.** GitHub does not access Customer Content unless required for support matters or security purposes. +**Acesso.** O GitHub não acessa o conteúdo do Cliente a menos que seja necessário para apoiar assuntos ou fins de segurança. -**DMCA.** GitHub has a Digital Millennium Copyright Act (DMCA) Takedown Policy which applies to copyright infringement claims. +**DMCA.** O GitHub possui uma Digital Millennium Copyright Act (DMCA) praticada como política relacionada a violações de direitos autorais. ### 2. Conteúdo. -**Ownership of Content.** Customer owns Content it creates and will fully comply with any third-party licenses relating to Content that Customer posts. +**Propriedade de Conteúdo.** O Cliente é dono do Conteúdo que cria e estará totalmente em conformidade com as licenças de terceiros relacionadas ao Conteúdo que o Cliente postar. -**License Grant to GitHub.** Unless Customer Content comes with a separate license granting GitHub the rights it needs to run the Online Service, Customer grants to GitHub the right to use Customer Content and make incidental copies as necessary to provide the Online Service or support, or for security reasons. In addition, GitHub may be compelled by law to disclose Customer Content. +**Concessão de Licença ao GitHub.** A menos que o Conteúdo do Cliente venha com uma licença separada que conceda ao GitHub os direitos que ele precisa para executar o Serviço Online, o Cliente concede ao GitHub o direito de utilizar o Conteúdo do Cliente e fazer cópias eventuais, conforme necessário, para fornecer o suporte ou Serviço Online, ou por razões de segurança. Além disso, o GitHub pode ser obrigado por lei a divulgar o Conteúdo do Cliente. -### 3. Non-GitHub Products. -GitHub may make non-GitHub products available through the Online Service. If Customer uses any non-GitHub products with the Online Service, Customer may not do so in any way that would subject GitHub’s intellectual property to obligations beyond those expressly included in the Agreement. GitHub assumes no responsibility or liability for any non-GitHub products. Customer’s use of non-GitHub products is governed by the terms between Customer and the publisher of the non-GitHub products (if any). +### 3. Produtos não-GitHub. +O GitHub pode tornar produtos não-GitHub disponíveis através do Serviço Online. Se o Cliente usar qualquer produto não-GitHub com o Serviço Online, o Cliente não pode fazê-lo de forma que sujeitaria a propriedade intelectual do GitHub a obrigações além das expressamente incluídas no Contrato. O GitHub não assume nenhuma responsabilidade ou responsabilidade por quaisquer produtos que não sejam da GitHub. O uso de produtos não-GitHub pelo Cliente é regido pelos termos entre o Cliente e o editor dos produtos não-GitHub (se houver). -### 4. Support and SLA. -The Online Service includes Support and the SLA. +### 4. Suporte e SLA. +O Serviço Online inclui suporte e SLA. -### 5. Data Protection and Security. -The terms of the Data Protection Agreement apply to the Online Service. +### 5. Proteção de Dados e Segurança. +Os termos do Contrato de Proteção de Dados se aplicam ao Serviço Online. -### 6. Notices. -Notices to GitHub must be sent to: GitHub, Inc. Attn: Legal Dept., 88 Colin P. Kelly St, San Francisco, CA 94107 USA. +### 6. Aviso. +Os avisos para o GitHub devem ser enviados para: GitHub, Inc. Attn: Legal Dept., 88 Colin P. Kelly St, San Francisco, CA 94107 USA. ### 7. Definições. -“**Acceptable Use Policy**” means, when purchasing from GitHub, the Acceptable Use Policy available on Site-Policy and when purchasing from Microsoft, the Acceptable Use Policy in the Microsoft Online Services Terms. +“**Política de Uso Aceitável**" significa, ao comprar no GitHub, a Política de Uso Aceitável disponível na Política do Site e ao comprar na Microsoft, a Política de Uso Aceitável nos Termos de Serviços Online da Microsoft. -“**Content**” means text, data, software, images and any other materials that are displayed or otherwise made available through the Online Service. +“**Conteúdo**” significa texto, dados, software, imagens e quaisquer outros materiais que sejam exibidos ou disponibilizados através do Serviço Online. -“**Customer Content**” means Content that Customer creates, owns, or to which Customer holds the rights. +“**"Conteúdo do Cliente"** significa Conteúdo que o Cliente cria, possui ou para o qual o Cliente detém os direitos. -“**Data Protection Agreement**” means the GitHub AE Data Protection Agreement, available on https://docs.github.com/github/site-policy. +“**Contrato de Proteção de Dados**significa o Contrato de Proteção de Dados da GitHub AE, disponível em https://docs.github.com/github/site-policy. -“**Digital Millennium Copyright Act Takedown Policy**” means GitHub’s process for handling notices of copyright infringement, available on https://docs.github.com/github/site-policy. +“**Digital Millennium Copyright Act Takedown Policy (Política de Retirada da Lei dos Direitos Autorais do Milênio Digital) **” significa o processo do GitHub para lidar com avisos de violação de direitos autorais, disponível em https://docs.github.com/github/site-policy. -“**SLA**” means GitHub’s uptime commitment for the Online Service, available on https://docs.github.com/github/site-policy. +“**SLA**” significa o compromisso de tempo de atividade do GitHub para o Serviço Online, disponível em https://docs.github.com/github/site-policy. -“**Support**” means GitHub’s Premium Plus Support program, further described on https://docs.github.com/github/site-policy. +“**Suporte**” significa o programa de Suporte Premium Plus do GitHub, descrito com mais detalhes em https://docs.github.com/github/site-policy. diff --git a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md index 7994545428..b6de152158 100644 --- a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md +++ b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md @@ -11,7 +11,7 @@ Milhões de desenvolvedores hospedam milhões de projetos no GitHub — tanto c Usuários do GitHub em todo o mundo trazem perspectivas, ideias e experiências extremamente diferentes, abrangendo desde pessoas que criaram seu primeiro projeto "Olá Mundo" na semana passada até os mais conhecidos desenvolvedores de software do mundo. Estamos empenhados em fazer do GitHub um ambiente acolhedor para todas as diferentes vozes e perspectivas da nossa comunidade, mantendo um espaço onde as pessoas são livres para se expressarem. -Contamos com os membros de nossa comunidade para comunicar expectativas, [moderar](#what-if-something-or-someone-offends-you) seus projetos e {% data variables.contact.report_abuse %} ou {% data variables.contact.report_content %}. Não procuramos ativamente conteúdo para moderar. Explicando o que esperamos ver em nossa comunidade, esperamos ajudá-lo a compreender como colaborar no GitHub, e que tipo de ações ou conteúdo podem violar nossos [Termos de Serviço](#legal-notices). Investigaremos quaisquer denúncias de abuso e podemos moderar o conteúdo público em nosso site que definirmos como violador de nossos Termos de Serviço. +Contamos com os membros de nossa comunidade para comunicar expectativas, [moderar](#what-if-something-or-someone-offends-you) seus projetos e {% data variables.contact.report_abuse %} ou {% data variables.contact.report_content %}. Ao definir o que esperamos ver em nossa comunidade, esperamos ajudá-lo a entender a melhora forma para colaborar no GitHub e que tipo de ações ou conteúdo podem violar nossos [Termos de Serviço](#legal-notices), que incluem nossas [Políticas de Uso Aceitáveis](/github/site-policy/github-acceptable-use-policies). Investigaremos quaisquer denúncias de abuso e podemos moderar o conteúdo público em nosso site que definirmos como violador de nossos Termos de Serviço. ### Criar uma comunidade integrada @@ -47,23 +47,25 @@ Claro, você sempre pode entrar em contato conosco em {% data variables.contact. Estamos comprometidos em manter uma comunidade onde os usuários são livres para se expressarem e desafiarem as ideias uns dos outros, tanto ideias técnicas como outras. No entanto, essas discussões não promovem diálogos frutíferos quando as ideias são silenciadas porque membros da comunidade estão sendo constrangidos ou têm medo de falar. Isso significa que devemos ser sempre respeitosos e cordiais, e evitarmos atacar os outros com base no que eles são. Não toleramos comportamentos que cruzam os seguintes limites: -* **Ameaças de violência** - Você não pode ameaçar terceiros ou usar o site para organizar, promover ou incitar atos de violência ou terrorismo no mundo real. Pense cuidadosamente sobre as palavras que você usa, as imagens que você publica, e até mesmo o software que você escreve, e como podem ser interpretados pelos outros. Mesmo que pretenda fazer uma piada, isso poderá ser interpretado de outra forma. Se você acha que outra pessoa *pode* interpretar o conteúdo que você postou como uma ameaça, ou como uma promoção da violência ou como terrorismo, pare. Não publique isso no GitHub. Em casos excepcionais, podemos relatar ameaças de violência às autoridades competentes, se acreditarmos que pode haver um risco genuíno de danos físicos ou uma ameaça à segurança pública. +- #### Ameaças de violência Você não pode ameaçar terceiros ou usar o site para organizar, promover ou incitar atos de violência ou terrorismo no mundo real. Pense cuidadosamente sobre as palavras que você usa, as imagens que você publica, e até mesmo o software que você escreve, e como podem ser interpretados pelos outros. Mesmo que pretenda fazer uma piada, isso poderá ser interpretado de outra forma. Se você acha que outra pessoa *pode* interpretar o conteúdo que você postou como uma ameaça, ou como uma promoção da violência ou como terrorismo, pare. Não publique isso no GitHub. Em casos excepcionais, podemos relatar ameaças de violência às autoridades competentes, se acreditarmos que pode haver um risco genuíno de danos físicos ou uma ameaça à segurança pública. -* **Discurso de ódio e discriminação** - embora não seja proibido abordar tópicos como idade, tamanho do corpo, deficiência física, etnia, identidade e expressão de gênero, nível de experiência, nacionalidade, aparência pessoal, raça, religião ou identidade e orientação sexual, não toleramos discursos que ataquem uma pessoa ou um grupo de pessoas com base em quem elas são. Perceba que quando abordados de forma agressiva ou insultante, estes (e outros) tópicos sensíveis podem fazer com que terceiros se sintam indesejados, ou até mesmo vulneráveis. Embora haja sempre o potencial para mal-entendidos, esperamos que os membros da nossa comunidade permaneçam respeitosos e cordiais quando discutirem temas sensíveis. +- #### Discurso de ódio e discriminação Embora não seja proibido abordar tópicos como idade, tamanho do corpo, deficiência física, etnia, identidade e expressão de gênero, nível de experiência, nacionalidade, aparência pessoal, raça, religião ou identidade e orientação sexual, não toleramos discursos que ataquem uma pessoa ou um grupo de pessoas com base em quem elas são. Perceba que quando abordados de forma agressiva ou insultante, estes (e outros) tópicos sensíveis podem fazer com que terceiros se sintam indesejados, ou até mesmo vulneráveis. Embora haja sempre o potencial para mal-entendidos, esperamos que os membros da nossa comunidade permaneçam respeitosos e cordiais quando discutirem temas sensíveis. -* **Bullying e assédio** - Não toleramos bullying ou assédio. Isto significa qualquer tipo de insulto ou intimidação habitual dirigida a uma pessoa ou grupo específico de pessoas. Em geral, se suas ações são indesejadas e você continua com o mesmo comportamento, há uma boa chance de você estar praticando bullying ou assédio. +- #### Bullying e assédio Não toleramos bullying ou assédio. Isto significa qualquer tipo de insulto ou intimidação habitual dirigida a uma pessoa ou grupo específico de pessoas. Em geral, se suas ações são indesejadas e você continua com o mesmo comportamento, há uma boa chance de você estar praticando bullying ou assédio. -* **Falsidade ideológica** - Você não pode tentar enganar terceiros mentindo sobre sua identidade copiando o avatar de outra pessoa, postando conteúdo com endereço de e-mail de terceiros, usando um nome de usuário semelhante ou apresentando-se como outra pessoa. A falsidade ideológica é uma forma de assédio. +- #### Interromper a experiência de outros usuários Ser parte de uma comunidade inclui reconhecer como seu comportamento afeta os outros e envolver-se em interações significativas e produtivas com as pessoas e a plataforma de que dependem. Não são permitidos comportamentos como postar repetidamente comentários que fogem ao tópico, abrir problemas ou pull requests vazios ou sem sentido ou usar qualquer recurso de outra plataforma de uma forma que perturbe continuamente a experiência de outros usuários. Embora incentivemos os mantenedores a moderar os seus próprios projetos individualmente, a equipe do GitHub pode ter uma ação restritiva contra contas que estão se envolvendo com esses tipos de comportamento. -* **Doxxing e invasão de privacidade** - Não publique informações pessoais de outras pessoas, como números de telefone, endereços de e-mail privados, endereços físicos, números de cartão de crédito, números de seguro social/identidade nacional ou senhas. Dependendo do contexto, como no caso de intimidação ou assédio, podemos considerar que outras informações, como fotos ou vídeos que foram tirados ou distribuídos sem o consentimento do indivíduo, constituem invasão da privacidade, especialmente quando esse material representa um risco para a segurança do indivíduo. +- #### Falsidade ideológica Você não pode tentar enganar terceiros mentindo sobre sua identidade copiando o avatar de outra pessoa, postando conteúdo com endereço de e-mail de terceiros, usando um nome de usuário semelhante ou apresentando-se como outra pessoa. A falsidade ideológica é uma forma de assédio. -* **Conteúdo sexualmente obsceno** - Não publique conteúdo pornográfico. Isto não significa que seja proibida qualquer nudez, ou qualquer código ou conteúdo relacionados com sexualidade. Reconhecemos que a sexualidade faz parte da vida e que o conteúdo sexual não pornográfico pode fazer parte do seu projeto, ou que possa ser apresentado para fins educacionais ou artísticos. Não permitimos conteúdos sexuais obscenos ou conteúdos que possam envolver a exploração ou a sexualização de menores. +- #### Doxxing e invasão de privacidade Não poste informações pessoais de outras pessoas, como endereços de e-mail pessoais e privados, números de telefone, endereços físicos, números de cartão de crédito, números de previdência social/identidade nacional ou senhas. Dependendo do contexto, como no caso de intimidação ou assédio, podemos considerar que outras informações, como fotos ou vídeos que foram tirados ou distribuídos sem o consentimento do indivíduo, constituem invasão da privacidade, especialmente quando esse material representa um risco para a segurança do indivíduo. -* **Conteúdo gratuitamente violento** - Não publique imagens, texto ou outro conteúdo violento sem um contexto razoável ou avisos. Embora muitas vezes não haja problema em incluir conteúdo violento em videogames, boletins e descrições de eventos históricos, não permitimos conteúdos violentos que sejam publicados indiscriminadamente, ou que sejam postados de uma forma que seja difícil evitar ter acesso a eles (como um avatar de perfil ou um comentário de problema). Um aviso claro ou uma declaração em outros contextos ajudam os usuários a tomarem uma decisão sobre se querem ou não se envolver com tal conteúdo. +- #### Conteúdo sexualmente obsceno Não publique conteúdo pornográfico. Isto não significa que seja proibida qualquer nudez, ou qualquer código ou conteúdo relacionados com sexualidade. Reconhecemos que a sexualidade faz parte da vida e que o conteúdo sexual não pornográfico pode fazer parte do seu projeto, ou que possa ser apresentado para fins educacionais ou artísticos. Não permitimos conteúdos sexuais obscenos ou conteúdos que possam envolver a exploração ou a sexualização de menores. -* **Informação errada e desinformação** - Você não pode postar conteúdo que apresente uma visão distorcida da realidade, seja ela imprecisa ou falsa (informação errada) ou intencionalmente enganosa (desinformação) porque esse conteúdo provavelmente resultará em danos ao público ou interferirá em oportunidades justas e iguais para todos participarem da vida pública. Por exemplo, não permitimos conteúdo que possa colocar o bem-estar de grupos de pessoas em risco ou limitar sua capacidade de participar de uma sociedade livre e aberta. Incentivamos a participação ativa na expressão de ideias, perspectivas e experiências e não se pode estar em posição de disputar contas ou observações pessoais. Geralmente, permitimos paródias e sátiras alinhadas com nossas Políticas de Uso Aceitável, e consideramos o contexto importante na forma como as informações são recebidas e compreendidas; portanto, pode ser apropriado esclarecer suas intenções através de isenções de responsabilidade ou outros meios, bem como a fonte(s) de suas informações. +- #### Conteúdo gratuitamente violento Não publique imagens, texto ou outro conteúdo violento sem um contexto razoável ou avisos. Embora muitas vezes não haja problema em incluir conteúdo violento em videogames, boletins e descrições de eventos históricos, não permitimos conteúdos violentos que sejam publicados indiscriminadamente, ou que sejam postados de uma forma que seja difícil evitar ter acesso a eles (como um avatar de perfil ou um comentário de problema). Um aviso claro ou uma declaração em outros contextos ajudam os usuários a tomarem uma decisão sobre se querem ou não se envolver com tal conteúdo. -* **Malware ativo ou exploits** - Fazer parte de uma comunidade inclui não tirar proveito de outros integrantes dela. Não permitimos que ninguém use nossa plataforma para explorar entrega, como por exemplo, usando o GitHub como meio de fornecer maliciosos executáveis, ou como infraestrutura de ataques, ou ainda, organizando ataques de negação de serviço ou gerenciando servidores de comando e controle. No entanto, não proibimos a publicação de código-fonte que poderia ser utilizado para desenvolver malware ou exploits, já que a publicação e distribuição de tal código-fonte tem valor educacional e fornece benefícios para a comunidade de segurança. +- #### Informação errada e desinformação Você não pode postar conteúdo que apresente uma visão distorcida da realidade, seja ela imprecisa ou falsa (informação errada) ou intencionalmente enganosa (desinformação) porque esse conteúdo provavelmente resultará em danos ao público ou interferirá em oportunidades justas e iguais para todos participarem da vida pública. Por exemplo, não permitimos conteúdo que possa colocar o bem-estar de grupos de pessoas em risco ou limitar sua capacidade de participar de uma sociedade livre e aberta. Incentivamos a participação ativa na expressão de ideias, perspectivas e experiências e não se pode estar em posição de disputar contas ou observações pessoais. Geralmente, permitimos paródias e sátiras alinhadas com nossas Políticas de Uso Aceitável, e consideramos o contexto importante na forma como as informações são recebidas e compreendidas; portanto, pode ser apropriado esclarecer suas intenções através de isenções de responsabilidade ou outros meios, bem como a fonte(s) de suas informações. + +- #### Malware ativo ou exploits Fazer parte de uma comunidade inclui não tirar proveito de outros integrantes dela. Não permitimos que ninguém use nossa plataforma para explorar entrega, como por exemplo, usando o GitHub como meio de fornecer maliciosos executáveis, ou como infraestrutura de ataques, ou ainda, organizando ataques de negação de serviço ou gerenciando servidores de comando e controle. No entanto, não proibimos a publicação de código-fonte que poderia ser utilizado para desenvolver malware ou exploits, já que a publicação e distribuição de tal código-fonte tem valor educacional e fornece benefícios para a comunidade de segurança. ### O que acontece se alguém violar as regras? diff --git a/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md index 1c8491c84e..4d9b5211e7 100644 --- a/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md @@ -1,5 +1,5 @@ --- -title: Termos de serviço corporativos do GitHub +title: Termos de Serviço Corporativos do GitHub redirect_from: - /articles/github-corporate-terms-of-service versions: @@ -8,8 +8,8 @@ versions: OBRIGADO POR ESCOLHER O GITHUB PARA AS NECESSIDADES COMERCIAIS DE SUA EMPRESA. LEIA ESTES TERMOS ATENTAMENTE, POIS ELES REGEM O USO DOS PRODUTOS (CONFORME DEFINIDO ABAIXO), A MENOS QUE O GITHUB TENHA FIRMADO COM VOCÊ UM CONTRATO A PARTE, POR ESCRITO, COM ESSE OBJETIVO. AO CLICAR NO BOTÃO "CONCORDO" OU SEMELHANTE OU ACESSAR OS PRODUTOS, O CLIENTE ACEITA TODOS OS TERMOS E CONDIÇÕES DESTE CONTRATO. SE VOCÊ ESTIVER CELEBRANDO ESTE CONTRATO EM NOME DE UMA EMPRESA OU OUTRA ENTIDADE JURÍDICA, O CLIENTE DECLARA QUE TEM OS PODERES LEGAIS DE VINCULAR A EMPRESA OU OUTRA ENTIDADE JURÍDICA A ESTE CONTRATO. -### Termos de serviço corporativos do GitHub -Data efetiva da versão: 20 de julho de 2020 +### Termos de Serviço Corporativos do GitHub +Entrada em vigor desta versão: 16 de novembro de 2020 Este Contrato aplica-se às seguintes ofertas do GitHub, conforme definido a seguir (ofertas coletivamente chamadas de **"Produtos"**): - O Serviço; @@ -133,13 +133,13 @@ O Cliente pode criar ou fazer upload do Conteúdo gerado pelo usuário ao usar o O Cliente mantém a propriedade do Conteúdo que o Cliente cria ou possui. O Cliente reconhece que: (a) é responsável pelo Conteúdo do cliente, (b) só enviará o Conteúdo que o Cliente tem direito de postar (como Conteúdo de terceiros ou gerados pelo Usuário), e (c) o Cliente cumprirá integralmente todas as licenças de terceiros relacionadas ao Conteúdo que o Cliente posta. O Cliente concede os direitos estabelecidos nas Seções D.3 a D.6, gratuitamente, e para as finalidades identificadas nessas seções até ao momento em que o Cliente remover o Conteúdo dos servidores do GitHub, exceto para Conteúdo que o Cliente tenha postado publicamente e que os Usuários Externos tenham bifurcado. Nesse caso, a licença será perpétua até que todas as Bifurcações do Conteúdo do Cliente tenham sido removidas dos servidores do GitHub. Se o Cliente fizer upload do Conteúdo do cliente que já vem com uma licença que concede ao GitHub as permissões necessárias para executar o Serviço, nenhuma licença adicional será necessária. #### 3. Concessão de licença para nós -O Cliente concede ao GitHub o direito de armazenar, analisar e exibir o Conteúdo do cliente e fazer cópias acessórias somente conforme necessário para fornecer o Serviço. Isso inclui o direito de copiar o Conteúdo do cliente para o banco de dados do GitHub e fazer backups; exibir o Conteúdo do cliente para ele e para quem o Cliente resolver mostrá-lo; analisar o Conteúdo do cliente em um índice de pesquisa ou analisá-lo nos servidores do GitHub; compartilhar o Conteúdo do cliente com Usuários externos com os quais o Cliente opte por compartilhá-lo; e executar o Conteúdo do cliente caso seja algo como música ou vídeo. Esses direitos se aplicam a Repositórios públicos e privados. Esta licença não concede ao GitHub o direito de vender o Conteúdo do cliente, distribuí-lo ou utilizá-lo fora do Serviço. O Cliente concede ao GitHub os direitos de que precisa para usar o Conteúdo do cliente sem atribuição e fazer adaptações razoáveis dele, conforme necessário, para fornecer o Serviço. +Cliente concede ao GitHub o direito de armazenar, arquivar, analisar e exibir Conteúdo do Cliente, e fazer cópias incidentais, apenas conforme necessário para prestar o Serviço, incluindo a melhoria do Serviço ao longo do tempo. Essa licença inclui o direito de copiar o Conteúdo do cliente para o banco de dados do GitHub e fazer backups; exibir o Conteúdo do cliente para ele e para quem o Cliente resolver mostrá-lo; analisar o Conteúdo do cliente em um índice de pesquisa ou analisá-lo nos servidores do GitHub; compartilhar o Conteúdo do cliente com Usuários externos com os quais o Cliente opte por compartilhá-lo; e executar o Conteúdo do cliente caso seja algo como música ou vídeo. Esses direitos se aplicam a Repositórios públicos e privados. Esta licença não concede ao GitHub o direito de vender Conteúdo do Cliente. Isso também não concede ao GitHub o direito de distribuir ou utilizar o Conteúdo do Cliente fora da nossa prestação do Serviço, salvo como parte do direito de arquivar o conteúdo do cliente, O GitHub pode permitir que nossos parceiros armazenem e arquivem conteúdo do cliente em repositórios públicos, relacionados ao GitHub Code Vault e o GitHub Archive Program. O Cliente concede ao GitHub os direitos de que precisa para usar o Conteúdo do cliente sem atribuição e fazer adaptações razoáveis dele, conforme necessário, para fornecer o Serviço. #### 4. Concessão de licença a usuários externos Qualquer Conteúdo que o Cliente posta publicamente, como problemas, comentários e contribuições a repositórios de Usuários Externos, pode ser visualizado por outras pessoas. Ao definir quais repositórios serão visualizados publicamente, o Cliente concorda em permitir que Usuários externos visualizem e bifurquem os repositórios do Cliente. Se o Cliente define páginas e repositórios para serem visualizados publicamente, ele concede a Usuários Externos uma licença mundial e não exclusiva para usar, exibir e executar o Conteúdo do Cliente por meio do Serviço e reproduzi-lo exclusivamente no Serviço conforme permitido através da funcionalidade fornecida pelo GitHub (por exemplo, através de Bifurcação). O Cliente pode conceder mais direitos ao Conteúdo do Cliente se o Cliente adotar uma licença. Se o cliente estiver fazendo upload de um Conteúdo do cliente que ele não criou nem possuiu, será responsável por garantir que o Conteúdo do cliente carregado seja licenciado sob os termos que concedem essas permissões a Usuários externos #### 5. Contribuições na licença de repositório -Sempre que o Cliente faz uma contribuição a um repositório que contém notificação de uma licença, o Cliente licencia essa contribuição nos mesmos termos e concorda que tem o direito de licenciá-la nesses termos. Se o Cliente tiver um contrato separado para licenciar as contribuições em termos diferentes, como um contrato de licença de colaborador, esse contrato será substituído. +Sempre que o Cliente adiciona Conteúdo a um repositório que contém notificação de uma licença, ele licencia essa contribuição nos mesmos termos e concorda que tem o direito de licenciá-la nesses termos. Se o Cliente tiver um contrato separado para licenciar o Conteúdo em termos diferentes, como um contrato de licença de colaborador, esse contrato será substituído. #### 6. Direitos Morais O Cliente detém todos os direitos morais ao Conteúdo do cliente que ele carrega, publica ou envia para qualquer parte do Serviço, inclusive os direitos de integridade e atribuição. No entanto, o Cliente renuncia a esses direitos e concorda em não fazê-los valer contra o GitHub somente no intuito de permitir que o GitHub exerça razoavelmente os direitos concedidos na Seção D, mas não de outra forma. @@ -153,10 +153,13 @@ O Cliente é responsável por gerenciar o acesso a seus Repositórios Privados, O GitHub considera o Conteúdo do cliente nos Repositórios privados do Cliente como Informações confidenciais do Cliente. O GitHub protegerá e manterá estritamente confidencial o Conteúdo do Cliente em Repositórios Privados, conforme descrito na Seção P. #### 3. Access -Os funcionários do GitHub só podem acessar os Repositórios Privados do Cliente (i) com o consentimento e o conhecimento do Cliente, para fins de suporte, ou (ii) quando o acesso for exigido por motivos de segurança. O Cliente pode optar por permitir o acesso adicional a seus Repositórios privados. Por exemplo, o Cliente pode habilitar vários serviços ou recursos do GitHub que exigem direitos adicionais ao Conteúdo do cliente em Repositórios privados. Esses direitos podem variar de acordo com o serviço ou recurso, mas o GitHub continuará a tratar o Conteúdo do cliente nos Repositórios privados do Cliente como Informações confidenciais do Cliente. Se esses serviços ou recursos exigirem direitos além dos necessários para oferecer o Serviço, o GitHub apresentará uma explicação sobre esses direitos. +O pessoal do GitHub só pode acessar os Repositórios Privados do Cliente nas situações descritas em nossa [Declaração de Privacidade](/github/site-policy/github-privacy-statement#repository-contents). -#### 4. Exclusões -Se o GitHub tiver motivos para acreditar que o Conteúdo de um Repositório privado viola a lei ou o presente Contrato, o GitHub tem o direito de acessar, analisar e remover esse Conteúdo. Além disso, o GitHub pode ser [obrigado, por lei,](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar o Conteúdo dos Repositórios Privados do Cliente. A menos que estipulado de outra forma por requisitos dispostos na lei ou em resposta a uma ameaça à segurança ou outro risco para a segurança, o GitHub avisará sobre tais ações. +O Cliente pode optar por permitir o acesso adicional a seus Repositórios privados. Por exemplo, o Cliente pode habilitar vários serviços ou recursos do GitHub que exigem direitos adicionais ao Conteúdo do cliente em Repositórios privados. Esses direitos podem variar de acordo com o serviço ou recurso, mas o GitHub continuará a tratar o Conteúdo do cliente nos Repositórios privados do Cliente como Informações confidenciais do Cliente. Se esses serviços ou recursos exigirem direitos além dos necessários para oferecer o Serviço, o GitHub apresentará uma explicação sobre esses direitos. + +Além disso, podemos ser [obrigados, por lei,](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar o conteúdo de seus repositórios privados. + +O GitHub fornecerá avisos sobre nosso acesso ao conteúdo do repositório privado, a menos que [para divulgação legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumprir nossas obrigações legais, ou onde de outra forma estiver vinculado por requisitos legais, para verificação automatizada ou se em resposta a uma ameaça de segurança ou outro risco à segurança. ### F. Avisos de Propriedade Intelectual @@ -270,7 +273,7 @@ Nenhuma das Partes usará as Informações confidenciais da outra Parte, exceto O GitHub fornecerá uma SOW detalhando os Serviços profissionais que tenham sido solicitados pelo Cliente. O GitHub executará os Serviços profissionais descritos em cada SOW. O GitHub controlará a forma e os meios pelos quais os Serviços Profissionais são executados e reserva-se o direito de determinar os funcionários designados. O GitHub pode usar terceiros para executar os Serviços profissionais, desde que o GitHub permaneça responsável pelos atos e omissões deles. O Cliente reconhece e concorda que o GitHub detém todos os direitos, títulos e interesses referentes a tudo o que for usado ou desenvolvido em relação à execução dos Serviços profissionais, inclusive software, ferramentas, especificações, ideias, conceitos, invenções, processos, técnicas e know-how. Na medida em que o GitHub oferece qualquer coisa ao Cliente ao realizar os Serviços Profissionais, o GitHub concede ao Cliente uma licença não exclusiva, não transferível, mundial, sem direitos de autor e com prazo limitado para usar as entregas disponíveis durante o termo deste Contrato, apenas em conjunto com o uso do Serviço pelo Cliente. ### R. Alterações no Serviço ou Termos -O GitHub se reserva o direito de, a seu exclusivo critério, modificar este Contrato a qualquer momento e o atualizará nesse caso. O GitHub publicará um aviso no Serviço para notificar o cliente sobre mudanças concretas feitas neste Contrato, como alterações de preço, pelo menos 30 dias antes de sua entrada em vigor. Em relação a modificações não materiais, o uso continuado do Serviço pelo cliente constitui a concordância de nossas revisões deste Contrato. O Cliente pode ver todas as alterações feitas neste Contrato em nosso repositório [Política do site](https://github.com/github/site-policy). +O GitHub se reserva o direito de, a seu exclusivo critério, modificar este Contrato a qualquer momento e o atualizará nesse caso. O GitHub notificará o Cliente sobre mudanças neste Contrato, tais como aumentos de preço, pelo menos 30 dias antes das alterações entrarem em vigor, postando uma notificação no Serviço ou enviando um e-mail para o endereço de e-mail principal especificado em sua conta do GitHub. O uso contínuo do Serviço pelo Cliente após esses 30 dias constitui concordância com essas revisões deste Contrato. Em relação a quaisquer outras modificações, o uso continuado do Serviço pelo Cliente constitui a concordância de nossas revisões a este Contrato. O Cliente pode ver todas as alterações feitas neste Contrato em nosso repositório [Política do site](https://github.com/github/site-policy). O GitHub altera o Serviço através de Atualizações e adição de novos recursos. Apesar do acima exposto, o GitHub reserva-se o direito de modificar ou suspender, a qualquer momento, com ou sem aviso prévio, o Serviço (ou qualquer parte dele). diff --git a/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md index 1a0e285482..5bef77e454 100644 --- a/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -26,6 +26,6 @@ Para definições de cada recurso de serviço (“**Recurso de serviço**”) e São excluídos do Cálculo de Tempo de Atividade as falhas de recursos de serviço resultantes de (i) atos, omissões ou abuso do Serviço, incluindo violações do Contrato; (ii) falha na conexão à internet do Cliente; (iii) fatores fora do controle razoável do GitHub, incluindo eventos de força maior; ou (iv) equipamento do Cliente, serviços ou outra tecnologia. ## Serviço de resgate de crédito -Se o GitHub não atender a este SLA, O cliente só poderá resgatar Créditos de Serviço mediante solicitação por escrito ao GitHub no prazo de 30 (trinta) dias a partir do final do trimestre do calendário. As solicitações por escrito do resgate de Créditos de Serviço devem ser enviadas para o [Suporte GitHub](https://support.github.com/contact). +Se o GitHub não atender a este SLA, O cliente só poderá resgatar Créditos de Serviço mediante solicitação por escrito ao GitHub no prazo de 30 (trinta) dias a partir do final do trimestre do calendário. Solicitações por escrito de resgate de Créditos de serviço e Relatórios personalizados mensais ou trimestrais do GitHub Enterprise Cloud devem ser enviados para o [Suporte do GitHub](https://support.github.com/contact). Os Créditos de Serviço podem assumir a forma de reembolso ou crédito para a conta do cliente, não podem ser trocados por um valor em dinheiro, estão limitados a um máximo de 90 (noventa) dias de serviço pago por trimestre do calendário, exigem que o cliente tenha pago qualquer fatura pendente e que expiram após a rescisão do acordo do Cliente com o GitHub. Os Serviço Créditos são o remédio único e exclusivo para qualquer falha do GitHub em cumprir quaisquer obrigações neste SLA. diff --git a/translations/pt-BR/content/github/site-policy/github-enterprise-subscription-agreement.md b/translations/pt-BR/content/github/site-policy/github-enterprise-subscription-agreement.md index 133d214dda..57f5549912 100644 --- a/translations/pt-BR/content/github/site-policy/github-enterprise-subscription-agreement.md +++ b/translations/pt-BR/content/github/site-policy/github-enterprise-subscription-agreement.md @@ -7,7 +7,7 @@ versions: free-pro-team: '*' --- -Data efetiva da versão: 20 de julho de 2020 +Entrada em vigor desta versão: 16 de novembro de 2020 AO CLICAR NO BOTÃO "CONCORDO" OU SEMELHANTE OU USAR QUALQUER UM DOS PRODUTOS (DEFINIDOS ABAIXO), O CLIENTE ACEITA OS TERMOS E CONDIÇÕES DESTE CONTRATO. SE O CLIENTE ESTÁ FIRMANDO ESTE CONTRATO EM NOME DE UMA ENTIDADE LEGAL, O CLIENTE CONFIRMA QUE TEM AUTORIDADE LEGAL PARA VINCULAR A ENTIDADE LEGAL A ESTE CONTRATO. @@ -197,7 +197,7 @@ Juntamente com os Anexos e cada Formulário de pedido e SOW, este Contrato const #### 1.13.11 Modificações; Ordem de precedência. -O GitHub se reserva o direito de, a seu exclusivo critério, modificar este Contrato a qualquer momento e o atualizará nesse caso. O GitHub publicará um aviso no Serviço para notificar o cliente sobre mudanças concretas feitas neste Contrato, como alterações de preço, pelo menos 30 dias antes de sua entrada em vigor. Em relação a modificações não materiais, o uso continuado do Serviço pelo cliente constitui a concordância de nossas revisões deste Contrato. O Cliente pode ver todas as alterações feitas neste Contrato em nosso repositório [Política do site](https://github.com/github/site-policy). No caso de conflito entre os termos deste Contrato e qualquer Formulário de pedido ou SOW, os termos do Formulário de pedido ou da SOW devem vigorar apenas em relação a esse Formulário de pedido ou essa SOW. +O GitHub se reserva o direito de, a seu exclusivo critério, modificar este Contrato a qualquer momento e o atualizará nesse caso. O GitHub notificará o Cliente sobre mudanças neste Contrato, tais como aumentos de preço, pelo menos 30 dias antes das alterações entrarem em vigor, postando uma notificação no Serviço ou enviando um e-mail para o endereço de e-mail principal especificado em sua conta do GitHub. O uso contínuo do Serviço pelo Cliente após esses 30 dias constitui concordância com essas revisões deste Contrato. Em relação a quaisquer outras modificações, o uso continuado do Serviço pelo Cliente constitui a concordância de nossas revisões a este Contrato. O Cliente pode ver todas as alterações feitas neste Contrato em nosso repositório [Política do site](https://github.com/github/site-policy). No caso de conflito entre os termos deste Contrato e qualquer Formulário de pedido ou SOW, os termos do Formulário de pedido ou da SOW devem vigorar apenas em relação a esse Formulário de pedido ou essa SOW. #### 1.13.12 Independência das disposições contratuais. @@ -296,7 +296,7 @@ O Cliente pode criar ou fazer upload do Conteúdo gerado pelo usuário ao usar o **(ii)** O Cliente concede os direitos estabelecidos nas Seções 3.3.3 a 3.3.6 gratuitamente e para as finalidades identificadas nessas seções até ao momento em que o Cliente remove o Conteúdo do cliente dos servidores do GitHub, exceto para Conteúdo que o Cliente tenha postado publicamente e que os Usuários externos tenham bifurcado. Nesse caso, a licença será perpétua até que todas as Bifurcações do Conteúdo do cliente tenham sido removidas dos servidores do GitHub. Se o Cliente fizer upload do Conteúdo do cliente que já vem com uma licença que concede ao GitHub as permissões necessárias para executar o Serviço, nenhuma licença adicional será necessária. #### 3.3.3 Concessão de licença ao GitHub. -O Cliente concede ao GitHub o direito de armazenar, analisar e exibir o Conteúdo do cliente e fazer cópias acessórias somente conforme necessário para fornecer o Serviço. Isso inclui o direito de copiar o Conteúdo do cliente para o banco de dados do GitHub e fazer backups; exibir o Conteúdo do cliente para ele e para quem o Cliente resolver mostrá-lo; analisar o Conteúdo do cliente em um índice de pesquisa ou analisá-lo nos servidores do GitHub; compartilhar o Conteúdo do cliente com Usuários externos com os quais o Cliente opte por compartilhá-lo; e executar o Conteúdo do cliente caso seja algo como música ou vídeo. Esses direitos se aplicam a Repositórios públicos e privados. Esta licença não concede ao GitHub o direito de vender o Conteúdo do cliente, distribuí-lo ou utilizá-lo fora do Serviço. O Cliente concede ao GitHub os direitos de que precisa para usar o Conteúdo do cliente sem atribuição e fazer adaptações razoáveis dele, conforme necessário, para fornecer o Serviço. +O Cliente concede ao GitHub o direito de armazenar, analisar e exibir o Conteúdo do Cliente e fazer cópias eventuais somente conforme necessário para fornecer o Serviço. Isso inclui o direito de copiar o Conteúdo do cliente para o banco de dados do GitHub e fazer backups; exibir o Conteúdo do cliente para ele e para quem o Cliente resolver mostrá-lo; analisar o Conteúdo do cliente em um índice de pesquisa ou analisá-lo nos servidores do GitHub; compartilhar o Conteúdo do cliente com Usuários externos com os quais o Cliente opte por compartilhá-lo; e executar o Conteúdo do cliente caso seja algo como música ou vídeo. Esses direitos se aplicam a Repositórios públicos e privados. Esta licença não concede ao GitHub o direito de vender o Conteúdo do cliente, distribuí-lo ou utilizá-lo fora do Serviço. O Cliente concede ao GitHub os direitos de que precisa para usar o Conteúdo do cliente sem atribuição e fazer adaptações razoáveis dele, conforme necessário, para fornecer o Serviço. #### 3.3.4 Concessão de licença a usuários externos. **(i)** Qualquer Conteúdo que o Cliente posta publicamente, como problemas, comentários e contribuições a repositórios de Usuários externos, pode ser visualizado por outras pessoas. Ao definir quais repositórios serão visualizados publicamente, o Cliente concorda em permitir que Usuários externos visualizem e bifurquem os repositórios do Cliente. @@ -318,10 +318,13 @@ O Cliente é responsável por gerenciar o acesso a seus Repositórios privados, O GitHub considera o Conteúdo do cliente nos Repositórios privados do Cliente como Informações confidenciais do Cliente. O GitHub protegerá e manterá estritamente confidencial o Conteúdo do cliente em Repositórios privados, conforme descrito na Seção 1.4. #### 3.4.3 Acesso. -O GitHub só pode acessar os Repositórios privados do Cliente (i) com o consentimento e o conhecimento do Cliente, para fins de suporte, ou (ii) quando o acesso for exigido por motivos de segurança. O Cliente pode optar por permitir o acesso adicional a seus Repositórios privados. Por exemplo, o Cliente pode habilitar vários serviços ou recursos do GitHub que exigem direitos adicionais ao Conteúdo do cliente em Repositórios privados. Esses direitos podem variar de acordo com o serviço ou recurso, mas o GitHub continuará a tratar o Conteúdo do cliente nos Repositórios privados do Cliente como Informações confidenciais do Cliente. Se esses serviços ou recursos exigirem direitos além dos necessários para oferecer o Serviço, o GitHub apresentará uma explicação sobre esses direitos. +O pessoal do GitHub só pode acessar os Repositórios Privados do Cliente nas situações descritas em nossa [Declaração de Privacidade](/github/site-policy/github-privacy-statement#repository-contents). -#### 3.4.4 Exclusões. -Se o GitHub tiver motivos para acreditar que o Conteúdo de um Repositório privado viola a lei ou o presente Contrato, o GitHub tem o direito de acessar, analisar e remover esse Conteúdo. Além disso, o GitHub pode ser obrigado por lei a divulgar o Conteúdo de Repositórios privados do Cliente. A menos que estipulado de outra forma por requisitos dispostos na lei ou em resposta a uma ameaça à segurança ou outro risco para a segurança, o GitHub avisará sobre tais ações. +O Cliente pode optar por permitir o acesso adicional a seus Repositórios privados. Por exemplo, o Cliente pode habilitar vários serviços ou recursos do GitHub que exigem direitos adicionais ao Conteúdo do cliente em Repositórios privados. Esses direitos podem variar de acordo com o serviço ou recurso, mas o GitHub continuará a tratar o Conteúdo do cliente nos Repositórios privados do Cliente como Informações confidenciais do Cliente. Se esses serviços ou recursos exigirem direitos além dos necessários para oferecer o Serviço, o GitHub apresentará uma explicação sobre esses direitos. + +Além disso, podemos ser [obrigados, por lei,](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar o conteúdo de seus repositórios privados. + +O GitHub fornecerá avisos sobre nosso acesso ao conteúdo do repositório privado, a menos que [para divulgação legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumprir nossas obrigações legais, ou onde de outra forma estiver vinculado por requisitos legais, para verificação automatizada ou se em resposta a uma ameaça de segurança ou outro risco à segurança. ### 3.5. Avisos de propriedade intelectual. @@ -330,7 +333,7 @@ A aparência do Serviço é Copyright © GitHub, Inc. Todos os direitos reservad #### 3.5.2 Violação de direitos autorais e política DMCA. -If Customer is a copyright owner and believes that Content on the Service violates Customer’s copyright, Customer may contact GitHub in accordance with GitHub's [Digital Millennium Copyright Act Policy](https://github.com/contact/dmca) by notifying GitHub via its [DMCA Form](https://github.com/contact/dmca-notice) or by emailing copyright@github.com. +Se o Cliente for proprietário de direitos autorais e acreditar que o Conteúdo no Serviço viola seus direitos autorais, ele poderá notificar o GitHub de acordo com a [Lei dos Direitos Autorais do Milênio Digital](https://github.com/contact/dmca) (DMCA – Digital Millennium Copyright Act Policy) usando o [Formulário DMCA](https://github.com/contact/dmca-notice) ou pelo e-mail copyright@github.com. #### 3.5.3 Logotipos e marcas registradas do GitHub. diff --git a/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md index ae0600d0db..14fad06191 100644 --- a/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md +++ b/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' --- -Bem-vindo ao GitHub Marketplace ("Marketplace")! Estamos felizes por você estar aqui. Por favor, leia estes Termos de Serviço ("Termos do Marketplace") com cuidado antes de acessar ou usar o GitHub Marketplace. GitHub Marketplace é uma plataforma que permite que você compre produtos de desenvolvedores (gratuitamente ou mediante pagamento de uma taxa) que podem ser usados com sua conta GitHub.com ("Produtos de Desenvolvedor"). Embora vendidos pela GitHub, Inc. ("GitHub", "nós", "nossos"), os produtos de desenvolvedores podem ser desenvolvidos e mantidos pelo GitHub ou por provedores de software terceiros, e podem exigir que você concorde com um termo de serviço separado. O uso e/ou compra de Produtos de Desenvolvedor está sujeito a estes Termos de Marketplace e às taxas aplicáveis, e também pode estar sujeito a termos adicionais, conforme fornecido pelo terceiro licenciador desse Produto do Desenvolvedor (o "Fornecedor de Produto"). +Bem-vindo ao GitHub Marketplace ("Marketplace")! Estamos felizes por você estar aqui. Por favor, leia estes Termos de Serviço ("Termos do Marketplace") com cuidado antes de acessar ou usar o GitHub Marketplace. GitHub Marketplace é uma plataforma que permite que você selecione apps de desenvolvedores ou ações (gratuitamente ou mediante pagamento de uma taxa) que podem ser usados com sua conta GitHub.com ("Produtos de Desenvolvedor"). Embora oferecido pelo GitHub, Inc. ("GitHub", "nós", "nosso"), Produtos de Desenvolvedor podem ser desenvolvidos e mantidos pelo GitHub ou por provedores de software de terceiros. Sua seleção ou uso de Produtos para Desenvolvedores está sujeito a estes Termos do Marketplace e a quaisquer taxas aplicáveis, e pode exigir que você concorde com termos adicionais, conforme fornecido pelo licenciador de terceiros daquele Produto do Desenvolvedor (o "Fornecedor do Produto"). Ao usar o Marketplace, você está concordando em estar vinculado a estes Termos de Marketplace. -Entrada em vigor: 11 de outubro de 2017 +Data de vigência: 20 de novembro de 2020 ### A. Termos de serviço do GitHub.com @@ -40,11 +40,11 @@ Se você tiver uma pergunta, preocupação ou dúvidas sobre sua fatura, por fav ### E. Seus Dados e a Política de Privacidade do GitHub -**Privacidade.** Quando você comprar ou assinar um Produto de Desenvolvedor, o GitHub precisará compartilhar certas Informações Pessoais (conforme definido na [Declaração de Privacidade do GitHub](/articles/github-privacy-statement/)) com o Fornecedor de Produto para lhe fornecer o Produto de Desenvolvedor, independente de suas configurações de privacidade. Dependendo dos requisitos do Produto de Desenvolvedor escolhido, o GitHub pode compartilhar minimamente o nome do seu usuário, ID e o endereço de e-mail principal ou até mesmo ter acesso ao conteúdo dos repositórios, incluindo a capacidade de ler e modificar seus dados privados. Você conseguirá ver o escopo das permissões que o Produto do Desenvolvedor está solicitando, e aceitar ou negá-lo, ao conceder sua autorização via OAuth. Em linha com a [Declaração de Privacidade do GitHub](/articles/github-privacy-statement/), nós apenas forneceremos ao Fornecedor de Produto a quantidade mínima de informações necessárias para a finalidade da transação. +**Privacidade.** Quando você selecionar ou usar um Produto de Desenvolvedor, o GitHub precisará compartilhar certas Informações Pessoais (conforme definido na [Declaração de Privacidade do GitHub](/articles/github-privacy-statement/)) com o Fornecedor de Produto (se tais Informações Pessoais forem recebidas de você) para lhe fornecer o Produto de Desenvolvedor, independente de suas configurações de privacidade. Dependendo dos requisitos do Produto de Desenvolvedor escolhido, o GitHub pode compartilhar minimamente o nome do seu usuário, ID e o endereço de e-mail principal ou até mesmo ter acesso ao conteúdo dos repositórios, incluindo a capacidade de ler e modificar seus dados privados. Você conseguirá ver o escopo das permissões que o Produto do Desenvolvedor está solicitando, e aceitar ou negá-lo, ao conceder sua autorização via OAuth. Se você cancelar seus serviços de Produto de Desenvolvedor e revogar o acesso através das configurações de sua conta, o Fornecedor de Produto não poderá mais acessar sua conta. O Fornecedor de Produto é responsável por excluir suas Informações Pessoais de seus sistemas dentro de sua janela definida. Entre em contato com o Fornecedor do Produto para garantir que sua conta tenha sido encerrada corretamente. -**Isenção de Responsabilidade pela Segurança de Dados.** Quando você comprar ou assinar um Produto de Desenvolvedor, a segurança do Produto do Desenvolvedor e a custódia dos seus dados é de responsabilidade do Fornecedor do Produto. Você é responsável por compreender as considerações de segurança da compra e do uso do Produto do Desenvolvedor para suas próprias considerações de segurança, risco e conformidade. +**Isenção de Responsabilidade pela Segurança e Privacidade de Dados.** Quando você selecionar ou usar um Produto de Desenvolvedor, a segurança do Produto do Desenvolvedor e a custódia dos seus dados, incluindo suas Informações Pessoais (se houver), são de responsabilidade do Fornecedor do Produto. Você é responsável por compreender as considerações de segurança e privacidade da seleção ou uso do Produto do Desenvolvedor para suas próprias considerações de segurança, risco e conformidade. ### F. Direitos para os Produtos de Desenvolvedor diff --git a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md index fb1d5d2eb5..30cc600abf 100644 --- a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md +++ b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Data de vigência: 2 de outubro de 2020 +Data de vigência: 16 de novembro de 2020 Agradecemos por confiar seu código-fonte, seus projetos e suas informações pessoais à GitHub Inc. (“GitHub” ou “nós”). Manter suas informações pessoais em segurança é uma responsabilidade que levamos a sério, e queremos mostrar como fazemos esse trabalho. @@ -150,23 +150,39 @@ Nós **não** vendemos suas Informações Pessoais de Usuário para obtenção d Observação: a Lei de Privacidade do Consumidor da Califórnia de 2018 (“CCPA”) exige que as empresas informem em suas respectivas políticas de privacidade se divulgam ou não informações pessoais para obtenção de lucro ou considerações afins. Enquanto a CCPA cobre apenas residentes da Califórnia, nós voluntariamente estendemos seus principais direitos para as pessoas controlarem seus dados a _todos_ os nossos usuários e não apenas àqueles que residem na Califórnia. Saiba mais sobre a CCPA e sobre como a cumprimos [aqui](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act). -### Outras informações importantes +### Conteúdo do repositório -#### Conteúdo do repositório +#### Acesso a repositórios privados -Funcionários do GitHub [não acessam repositórios privados, a menos que haja solicitação](/github/site-policy/github-terms-of-service#e-private-repositories) por questões de segurança, para fins de suporte ao proprietário do repositório com um problema, para manter a integridade do Serviço ou para cumprirmos com nossas obrigações legais. No entanto, embora geralmente não procuremos conteúdo em seus repositórios, podemos varrer nossos servidores e conteúdo para detectar determinados tokens ou assinaturas de segurança, malware ativo conhecido ou outro conteúdo conhecido por violar nossos Termos, como conteúdo extremista violento ou terrorista ou imagens de exploração infantil, com base em técnicas algorítmicas de impressão digital. Nossos Termos de Serviço fornecem [mais detalhes](/github/site-policy/github-terms-of-service#e-private-repositories). +Se seu repositório for privado, você controla o acesso ao seu Conteúdo. Se você incluir Informações Pessoais do Usuário ou Informações Pessoais Confidenciais, essas informações só poderão ser acessadas pelo GitHub em conformidade com esta Declaração de Privacidade. Os funcionários do GitHub [não acessam o conteúdo privado do repositório](/github/site-policy/github-terms-of-service#e-private-repositories) exceto +- motivos de segurança +- para auxiliar o proprietário do repositório com uma questão de suporte +- para manter a integridade do Serviço +- para cumprir com nossas obrigações legais +- se tivermos motivos para acreditar que o conteúdo viola a lei, ou +- com o seu consentimento. -Se o seu repositório for público, qualquer pessoa poderá ver o conteúdo do repositório em questão. Se você incluiu informações privadas ou [Informações Pessoais Confidenciais](https://gdpr-info.eu/art-9-gdpr/) no seu repositório público, como endereços de e-mail ou senhas, tais informações poderão ser indexadas por mecanismos de pesquisa ou usadas por terceiros. +No entanto, embora, de modo geral, não pesquisemos conteúdo nos seus repositórios, podemos escanear nossos servidores e conteúdo para detectar certos tokens ou assinaturas de segurança, malware ativo conhecido, vulnerabilidades conhecidas em dependências ou outro conteúdo conhecido por violar nossos Termos de Serviço, como extremistas violentos ou conteúdo terrorista ou imagem de exploração infantil, baseado em técnicas de impressão digital algorítmica (coletivamente denominados, "escaneamento automatizado"). Nossos Termos de Serviço fornecem mais detalhes em [repositórios privados](/github/site-policy/github-terms-of-service#e-private-repositories). + +Tenha em mente que você pode optar por desabilitar determinados acessos aos seus repositórios privados que são ativados por padrão como parte do fornecimento de Serviço (por exemplo, varredura automatizada necessária para habilitar alertas de Dependência de gráfico e do Dependabot). + +O GitHub fornecerá avisos sobre nosso acesso ao conteúdo do repositório privado, a menos que [para divulgação legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumprir nossas obrigações legais, ou onde de outra forma estiver vinculado por requisitos legais, para verificação automatizada ou se em resposta a uma ameaça de segurança ou outro risco à segurança. + +#### Repositórios públicos + +Se o seu repositório for público, qualquer pessoa poderá ver o conteúdo do repositório em questão. Se você incluir informações pessoais do usuário, [Informações Pessoais Confidenciais](https://gdpr-info.eu/art-9-gdpr/)ou informações confidenciais, como endereços de e-mail ou senhas, no seu repositório público, essas informações podem ser indexadas por mecanismos de busca ou usadas por terceiros. Saiba mais sobre [Informações Pessoais de Usuário em repositórios públicos](/github/site-policy/github-privacy-statement#public-information-on-github). +### Outras informações importantes + #### Informações públicas no GitHub Vários recursos e serviços do GitHub são voltados para o público. Se o seu conteúdo for voltado para o público, ele poderá ser acessado e usado por terceiros em conformidade com nossos Termos de Serviço. Por exemplo, os terceiros podem visualizar seu perfil ou repositórios, ou fazer pull de dados pela nossa API. Não vendemos esse conteúdo; ele é seu. Entretanto, permitimos que terceiros (como organizações de pesquisa ou arquivos) compilem as informações públicas do GitHub. Outros terceiros, como agentes de dados, são conhecidos também por fazer scraping do GitHub e compilar dados. Suas Informações Pessoais de Usuário, associadas ao seu conteúdo, podem ser coletadas por terceiros nessas compilações de dados do GitHub. Se você não quiser que suas Informações Pessoais de Usuário apareçam em compilações de dados do GitHub de terceiros, não disponibilize as Informações Pessoais de Usuário publicamente e certifique-se de [configurar seu endereço de e-mail como privado no seu perfil de usuário](https://github.com/settings/emails) e em suas [configurações de commit do Git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Definimos o endereço de e-mail dos Usuários como privado por padrão, mas alguns Usuários do GitHub podem ter que atualizar suas configurações. -Se quiser compilar dados do GitHub, você deverá aceitar nossos Termos de Serviço quanto a [scraping](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions) e [privacidade](/github/site-policy/github-acceptable-use-policies#6-privacy), e poderá usar apenas as Informações Pessoais de Usuário públicas que coletar para os fins autorizados pelos nossos usuários. Por exemplo, se o usuário do GitHub deixou um endereço de e-mail público para fins de identificação e atribuição, não use o endereço de e-mail para fins de publicidade comercial. Esperamos que você proteja, de forma razoável, qualquer Informação Pessoal de Usuário que coletar do GitHub e que responda prontamente a reclamações, solicitações de remoção e solicitações de "não contatar" de nossa parte e de outros usuários. +Se você desejar compilar os dados do GitHub, você deverá cumprir os nossos Termos de Serviço com relação ao [uso da informação](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) e [privacidade](/github/site-policy/github-acceptable-use-policies#6-privacy), e você só poderá usar qualquer Informação Pessoal do Usuário pública que você coletar para o propósito autorizado pelo nosso usuário. Por exemplo, quando um usuário do GitHub criou um endereço de e-mail voltado para o público para fins de identificação e atribuição, não use esse endereço de e-mail para fins de envio de e-mails não solicitados aos usuários ou de venda de informações pessoais do usuário, tais como recrutadores, headhunters e job boards ou para publicidade comercial. Esperamos que você proteja, de forma razoável, qualquer Informação Pessoal de Usuário que coletar do GitHub e que responda prontamente a reclamações, solicitações de remoção e solicitações de "não contatar" de nossa parte e de outros usuários. De modo semelhante, os projetos no GitHub podem incluir Informações Pessoais de Usuário publicamente disponíveis e coletadas como parte do processo colaborativo. Em caso de problemas relacionados a quaisquer Informações Pessoais de Usuário no GitHub, consulte nossa seção sobre [resolução de conflitos](/github/site-policy/github-privacy-statement#resolving-complaints). @@ -185,7 +201,7 @@ Entre em contato com os proprietários da conta para obter mais informações so #### Aplicativos de terceiros -Você pode habilitar ou adicionar aplicativos de terceiros, conhecidos como "Produtos de Desenvolvedor", na sua Conta. Esses Produtos de Desenvolvedor não são necessários para o uso do GitHub. Compartilharemos suas Informações Pessoais de Usuário com terceiros quando você nos solicitar, por exemplo, ao comprar um Produto de Desenvolvedor no Marketplace. No entanto, você será responsável pelo uso do Produto de Desenvolvedor de terceiro e pela quantidade de Informações Pessoais de Usuário que decidir compartilhar. Consulte nossa [documentação de API](/v3/users/) para saber quais informações são fornecidas quando você se autentica em um Produto de Desenvolvedor usando seu perfil no GitHub. +Você pode habilitar ou adicionar aplicativos de terceiros, conhecidos como "Produtos de Desenvolvedor", na sua Conta. Esses Produtos de Desenvolvedor não são necessários para o uso do GitHub. Compartilharemos suas Informações Pessoais de Usuário com terceiros quando você nos solicitar, por exemplo, ao comprar um Produto de Desenvolvedor no Marketplace. No entanto, você será responsável pelo uso do Produto de Desenvolvedor de terceiro e pela quantidade de Informações Pessoais de Usuário que decidir compartilhar. Consulte nossa [documentação de API](/rest/reference/users) para saber quais informações são fornecidas quando você se autentica em um Produto de Desenvolvedor usando seu perfil no GitHub. #### GitHub Pages @@ -219,7 +235,7 @@ Com isso, o endereço de e-mail que você informou [nas suas configurações de #### Cookies -O GitHub usa cookies e tecnologias similares (coletivamente, denominados “cookies”) para tornar as interações com nosso serviço fáceis e significativas. Cookies são pequenos arquivos de texto que os sites costumam armazenar nos discos rígidos de computadores ou dispositivos móveis de visitantes. Usamos cookies para fornecer nossos serviços como, por exemplo, para manter você conectado, para lembrar as suas preferências, identificar o seu dispositivo para fins de segurança e fornecer informações para o desenvolvimento futuro do GitHub. Ao usar o nosso Site, você concorda que podemos inserir esses tipos de cookies no seu computador ou dispositivo. Se você desativar o navegador ou a capacidade de o seu dispositivo aceitar cookies, não será possível fazer login nem usar os serviços do GitHub. +O GitHub usa cookies e tecnologias similares (por exemplo, HTML5 localStorage) para tornar as interações com o nosso serviço fáceis e significativas. Cookies são pequenos arquivos de texto que os sites costumam armazenar nos discos rígidos de computadores ou dispositivos móveis de visitantes. Usamos cookies e tecnologias semelhantes (doravante denominadas, coletivamente, "cookies") para prestar nossos serviços como, por exemplo, manter você conectado, lembrar as suas preferências, identificar o seu dispositivo para fins de segurança e fornecer informações para o desenvolvimento futuro do GitHub. Ao usar o nosso Site, você concorda que podemos inserir esses tipos de cookies no seu computador ou dispositivo. Se você desativar o navegador ou a capacidade de o seu dispositivo aceitar cookies, não será possível fazer login nem usar os serviços do GitHub. Fornecemos mais informações sobre [cookies no GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) na nossa página [Subprocessadores e Cookies do GitHub](/github/site-policy/github-subprocessors-and-cookies) que descreve os cookies que definimos, a necessidade que temos para esses cookies e a expiração desses cookies. Ele também lista nossos provedores terceiros de análise e como você pode controlar suas configurações de preferência de cookies para esses cookies. @@ -300,7 +316,7 @@ No caso improvável de conflito entre você e o GitHub sobre a manipulação das ### Mudanças nesta Declaração de Privacidade -Embora grande parte das alterações sejam secundárias, o GitHub pode alterar esta Declaração de Privacidade ocasionalmente. Publicaremos uma notificação para os usuários no site sobre mudanças concretas feitas nesta Declaração de Privacidade pelo menos 30 dias antes de sua entrada em vigor. A notificação será exibida em nossa página inicial ou enviada por e-mail para o endereço de e-mail principal especificado na sua conta do GitHub. Também atualizaremos nosso [repositório da Política do Site](https://github.com/github/site-policy/), que registra e monitora todas as alterações feitas a esta política. Para consultar as alterações a esta Declaração de Privacidade que não configuram mudanças concretas nem afetam seus direitos, recomendamos que os visitantes verifiquem frequentemente o nosso repositório da Política do Site. +Embora grande parte das alterações sejam secundárias, o GitHub pode alterar esta Declaração de Privacidade ocasionalmente. Publicaremos uma notificação para os usuários no site sobre mudanças concretas feitas nesta Declaração de Privacidade pelo menos 30 dias antes de sua entrada em vigor. A notificação será exibida em nossa página inicial ou enviada por e-mail para o endereço de e-mail principal especificado na sua conta do GitHub. Também atualizaremos nosso [repositório da Política do Site](https://github.com/github/site-policy/), que registra e monitora todas as alterações feitas a esta política. Para outras mudanças nesta Declaração de Privacidade, incentivamos os usuários a [observar](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) ou verificar o nosso repositório de Política de Site com frequência. ### Licença diff --git a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md index 05b1c7f992..7b1e842e7d 100644 --- a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **October 2, 2020** +Data de vigência: **2 de outubro de 2020** O GitHub fornece um grande acordo de transparência em relação à forma como usamos seus dados, como os coletamos e com quem compartilhamos. Para tanto, nós fornecemos esta página, que detalha [nossos subprocessadores](#github-subprocessors), como usamos [cookies](#cookies-on-github), e onde e como executamos qualquer [rastreamento no GitHub](#tracking-on-github). @@ -28,7 +28,7 @@ Quando compartilhamos suas informações com terceiros subprocessadores, tais co | DiscoverOrg | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | | Eloqua | Automatização da campanha marketing | Estados Unidos | Estados Unidos | | Google Apps | Infraestrutura interna da empresa | Estados Unidos | Estados Unidos | -| Google Analytics | Analytics and performance | Estados Unidos | Estados Unidos | +| Google Analytics | Análise e desempenho | Estados Unidos | Estados Unidos | | LinkedIn Navigator | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | | Magic Robot | Relatórios de campanha (Complemento para Vendas) | Estados Unidos | Estados Unidos | | MailChimp | Fornecedor de serviços de correio para emissão de bilhetes a clientes | Estados Unidos | Estados Unidos | @@ -49,49 +49,49 @@ Quando trouxermos um novo subprocessador que lida com as Informações Pessoais ### Cookies no GitHub -GitHub uses cookies and similar technologies (collectively, “cookies”) to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. +O GitHub usa cookies e tecnologias semelhantes (coletivamente denominados “cookies”) para fornecer e proteger nossos sites, bem como analisar o uso dos nossos sites, para oferecer a você uma ótima experiência de usuário. Consulte nossa [Declaração de privacidade](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) se você quiser saber mais informações sobre cookies e sobre como e por que os usamos. -Since the number and names of cookies may change,the table below may be updated from time to time. +Como o número e os nomes dos cookies podem mudar, a tabela abaixo pode ser atualizada de vez em quando. -| Service Provider | Cookie Name | Descrição | Expiration* | -|:------------------ |:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------ |:------------------------------------------------------------- | -| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes | -| GitHub | `cookie-preferences` | This cookie is used to track user cookie preferences. | one year | -| GitHub | `_device_id` | This cookie is used to track recognized devices. | one year | -| GitHub | `dotcom_user` | This cookie is used to signal to us that the user is already logged in. | one year | -| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks | -| GitHub | `_gh_sess` | This cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form. | sessão | -| GitHub | `gist_oauth_csrf` | This cookie is set by Gist to ensure the user that started the oauth flow is the same user that completes it. | deleted when oauth state is validated | -| GitHub | `gist_user_session` | This cookie is used by Gist when running on a separate host. | two weeks | -| GitHub | `has_recent_activity` | This cookie is used to prevent showing the security interstitial to users that have visited the app recently. | one hour | -| GitHub | `__Host-gist_user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | -| GitHub | `__Host-user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | -| GitHub | `logged_in` | This cookie is used to signal to us that the user is already logged in. | one year | -| GitHub | `marketplace_repository_ids` | This cookie is used for the marketplace installation flow. | one hour | -| GitHub | `marketplace_suggested_target_id` | This cookie is used for the marketplace installation flow. | one hour | -| GitHub | `_octo` | This cookie is used by our internal analytics service to distinguish unique users and clients. | one year | -| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour | -| GitHub | `private_mode_user_session` | This cookie is used for Enterprise authentication requests. | two weeks | -| GitHub | `saml_csrf_token` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request | -| GitHub | `saml_csrf_token_legacy` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request | -| GitHub | `saml_return_to` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request | -| GitHub | `saml_return_to_legacy` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request | -| GitHub | `tz` | This cookie allows your browser to tell us what time zone you're in. | sessão | -| GitHub | `user_session` | This cookie is used to log you in. | two weeks | -| Google Analytics** | `_ga` | This cookie is used by Google Analytics. | two years | -| Google Analytics** | `_gat` | This cookie is used by Google Analytics. | one minute | -| Google Analytics** | `_gid` | This cookie is used by Google Analytics. | one day | +| Provedor de serviço | Nome do cookie | Descrição | Vencimento* | +|:------------------- |:------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- | +| GitHub | `app_manifest_token` | Este cookie é usado durante o fluxo do manifesto do aplicativo para manter o estado do fluxo durante o redirecionamento para buscar uma sessão do usuário. | cinco minutos | +| GitHub | `cookie-preferences` | Este cookie é usado para rastrear preferências de cookie do usuário. | um ano | +| GitHub | `_device_id` | Este cookie é usado para rastrear dispositivos reconhecidos. | um ano | +| GitHub | `dotcom_user` | Este cookie é usado para sinalizar que o usuário já está conectado. | um ano | +| GitHub | `_gh_ent` | Este cookie é usado para aplicação temporária e para o estado da estrutura entre páginas, como em que etapa o cliente se encontra em um processo de várias etapas. | duas semanas | +| GitHub | `_gh_sess` | Este cookie é usado para aplicação temporária e para o estado do framework entre páginas, como por exemplo, em qual etapa o usuário está em um formulário de várias etapas. | sessão | +| GitHub | `gist_oauth_csrf` | Este cookie é definido pelo Gist para garantir que o usuário que iniciou o fluxo de autenticação seja o mesmo usuário que o completa. | excluído quando o estado do oauth é validado | +| GitHub | `gist_user_session` | Este cookie é usado pelo Gist ao ser executado em um host separado. | duas semanas | +| GitHub | `has_recent_activity` | Este cookie é usado para impedir a exibição de intersticial de segurança para usuários que visitaram o aplicativo recentemente. | uma hora | +| GitHub | `__Host-gist_user_session_same_site` | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub. | duas semanas | +| GitHub | `__Host-user_session_same_site` | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub. | duas semanas | +| GitHub | `logged_in` | Este cookie é usado para sinalizar que o usuário já está conectado. | um ano | +| GitHub | `marketplace_repository_ids` | Este cookie é usado para o fluxo de instalação do marketplace. | uma hora | +| GitHub | `marketplace_suggested_target_id` | Este cookie é usado para o fluxo de instalação do marketplace. | uma hora | +| GitHub | `_octo` | Este cookie é usado pelo nosso serviço interno de análise para distinguir usuários e clientes únicos. | um ano | +| GitHub | `org_transform_notice` | Este cookie é usado para fornecer aviso durante a transformação da organização. | uma hora | +| GitHub | `private_mode_user_session` | Este cookie é usado para solicitações de autenticação da empresa. | duas semanas | +| GitHub | `saml_csrf_token` | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `saml_csrf_token_legacy` | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `saml_return_to` | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `saml_return_to_legacy` | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `tz` | Este cookie permite que seu navegador nos diga em que fuso horário você está. | sessão | +| GitHub | `user_session` | Este cookie é usado para fazer seu login. | duas semanas | +| Google Analytics** | `_ga` | Este cookie é usado pelo Google Analytics. | dois anos | +| Google Analytics** | `_gat` | Este cookie é usado pelo Google Analytics. | um minuto | +| Google Analytics** | `_gid` | Este cookie é usado pelo Google Analytics. | um dia | -_*_ The **expiration** dates for the cookies listed below generally apply on a rolling basis. +_*_ A data de **expiração** para os cookies listados abaixo geralmente se aplicam em uma base contínua. -_**_ We use **Google Analytics** as a third party analytics service to collect information about how our website performs and how our users, in general, navigate through and use GitHub. This helps us evaluate our users' use of GitHub, compile statistical reports on activity, and improve our content and website performance. +_**_ Utilizamos o **Google Analytics** como um serviço de análise de terceiros para coletar informações sobre o desempenho do nosso site e como nossos usuários navegam e usam o GitHub de modo geral. Isso nos ajuda a avaliar o uso do GitHub pelos nossos usuários, compilar relatórios estatísticos sobre atividades e melhorar nosso conteúdo e desempenho do site. -You can control your Google Analytics cookie preferences through our cookie preference link located at the footer of our website. In addition, Google provides further information about its own privacy practices and [offers a browser add-on to opt out of Google Analytics tracking](https://tools.google.com/dlpage/gaoptout). +Você pode controlar suas preferências de cookie do Google Analytics através do nosso link de preferência de cookie, localizado no rodapé do nosso site. Além disso, o Google fornece mais informações sobre suas próprias práticas de privacidade e [oferece um complemento do navegador para desativar o acompanhamento do Google Analytics](https://tools.google.com/dlpage/gaoptout). -(!) Please note certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets. +(!) Observe que certas páginas do nosso site podem definir outros cookies de terceiros. Por exemplo, podemos incorporar conteúdo, como vídeos, de outro site que define um cookie. Embora tentemos minimizar esses cookies de terceiros, nem sempre podemos controlar quais cookies esse conteúdo de terceiros define. ### Rastreamento no GitHub -"[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. O GitHub responde aos sinais de DNT dos navegadores e segue o [padrão do W3C de resposta aos sinais de DNT](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://www.eff.org/privacybadger). +"[Não rastrear](https://www.eff.org/issues/do-not-track)" (DNT) é uma preferência de privacidade que você pode definir no seu navegador se não quiser que os serviços on-line coletem e compartilhem certos tipos de informações sobre a sua atividade on-line de serviços de rastreamento de terceiros. O GitHub responde aos sinais de DNT dos navegadores e segue o [padrão do W3C de resposta aos sinais de DNT](https://www.w3.org/TR/tracking-dnt/). Se você deseja configurar seu navegador para sinalizar que não gostaria de ser rastreado, verifique a documentação do seu navegador para saber como habilitar essa sinalização. Há também bons aplicativos que bloqueiam o rastreamento on-line, como [Badger de Privacidade](https://www.eff.org/privacybadger). -If you have not enabled DNT on a browser that supports it, cookies on some parts of our website will track your online browsing activity on other online services over time, though we do not permit third parties other than our analytics and service providers to track GitHub users' activity over time on GitHub. We have agreements with certain vendors, such as analytics providers, who help us track visitors' movements on certain pages on our website. Only our vendors, who are collecting personal information on our behalf, may collect data on our pages, and we have signed data protection agreements with every vendor who collects this data on our behalf. We use the data we receive from these vendors to better understand our visitors' interests, to understand our website's performance, and to improve our content. Any analytics vendor will be listed in our [subprocessor list](#github-subprocessors), and you may see a list of every page where we collect this kind of data below. +Caso você não tenha habilitado o DNT em um navegador compatível com esse recurso, os cookies de algumas partes do nosso site rastrearão sua atividade de navegação online em outros serviços online ao longo do tempo, embora não permitamos que terceiros além de nossos provedores de análise e serviços monitorem a atividade dos usuários do GitHub ao longo do tempo no GitHub. Temos acordos com certos fornecedores, como fornecedores de análise, que nos ajudam a rastrear os movimentos dos visitantes em determinadas páginas no nosso site. Apenas nossos fornecedores, que estão coletando informações pessoais em nosso nome, podem coletar dados em nossas páginas, e assinamos contratos de proteção de dados com cada fornecedor que recolhe esses dados em nosso nome. Usamos os dados que recebemos desses fornecedores para entender melhor os interesses de nossos visitantes, entender o desempenho de nosso site e melhorar nosso conteúdo. Qualquer fornecedor de análise será listado na nossa [lista de subprocessadores](#github-subprocessors), e você pode ver uma lista de cada página em que coletamos esse tipo de dados abaixo. diff --git a/translations/pt-BR/content/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing.md b/translations/pt-BR/content/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing.md index 6ee1de86eb..f46c443b31 100644 --- a/translations/pt-BR/content/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing.md +++ b/translations/pt-BR/content/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing.md @@ -175,7 +175,7 @@ A aparência do Serviço é Copyright © GitHub, Inc. Todos os direitos reservad #### 2.5.2 Violação de direitos autorais e política DMCA. -If Customer is a copyright owner and believes that Content on the Service violates Customer’s copyright, Customer may contact GitHub in accordance with GitHub's [Digital Millennium Copyright Act Policy](https://github.com/contact/dmca) by notifying GitHub via its [DMCA Form](https://github.com/contact/dmca-notice) or by emailing copyright@github.com. +Se o Cliente for proprietário de direitos autorais e acreditar que o Conteúdo no Serviço viola seus direitos autorais, ele poderá notificar o GitHub de acordo com a [Lei dos Direitos Autorais do Milênio Digital](https://github.com/contact/dmca) (DMCA – Digital Millennium Copyright Act Policy) usando o [Formulário DMCA](https://github.com/contact/dmca-notice) ou pelo e-mail copyright@github.com. #### 2.5.3 Logotipos e marcas registradas do GitHub. diff --git a/translations/pt-BR/content/github/site-policy/github-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-terms-of-service.md index 8c1f4a791f..3b86b90b8f 100644 --- a/translations/pt-BR/content/github/site-policy/github-terms-of-service.md +++ b/translations/pt-BR/content/github/site-policy/github-terms-of-service.md @@ -32,11 +32,11 @@ Obrigado por usar o GitHub! Estamos felizes por você estar aqui. Por favor, lei | [N. Isenção de Garantias](#n-disclaimer-of-warranties) | Fornecemos nosso serviço tal como está, e não fazemos promessas nem damos garantias sobre este serviço. **Por favor, leia esta seção cuidadosamente; você deve entender o que esperar.** | | [O. Limitação de responsabilidade](#o-limitation-of-liability) | Não seremos responsáveis por danos ou prejuízos resultantes da sua utilização ou incapacidade de utilizar o serviço ou de outra forma decorrente deste contrato. **Por favor, leia esta seção cuidadosamente; ela limita nossas obrigações para com você.** | | [P. Versão e Indenização](#p-release-and-indemnification) | Você é totalmente responsável pelo uso do serviço. | -| [Q. Eu concordo com estes Termos de Serviço](#q-changes-to-these-terms) | Podemos modificar este contrato, mas vamos dar a você um aviso de 30 dias sobre as alterações que afetem seus direitos. | +| [Q. Eu concordo com estes Termos de Serviço](#q-changes-to-these-terms) | Podemos modificar este contrato, mas vamos dar a você um aviso de 30 dias sobre as alterações materiais. | | [R. Disposições Gerais](#r-miscellaneous) | Por favor, veja esta seção para detalhes legais, incluindo a nossa escolha de legislação. | ### Termos de Serviço do GitHub -Data de vigência: 2 de abril de 2020 +Data de vigência: 16 de novembro de 2020 ### A. Definições @@ -98,7 +98,7 @@ Você concorda que, em nenhuma circunstância, violará nossas [Políticas de Us Você pode criar ou fazer upload do conteúdo gerado pelo usuário usando o Serviço. Você é o único responsável pelo conteúdo e por qualquer dano resultante de qualquer conteúdo gerado pelo usuário que você publicar, fizer upload, linkar para ou deixar disponível através do Serviço, independentemente da forma desse Conteúdo. Não somos responsáveis por nenhuma exibição pública ou uso indevido do seu Conteúdo Gerado pelo Usuário. #### 2. O GitHub pode remover conteúdo -Não pré-avaliamos o Conteúdo Gerado pelo Usuário, mas temos o direito (embora não tenhamos a obrigação) de recusar ou remover qualquer Conteúdo Gerado pelo Usuário que, em nosso exclusivo critério, viole quaisquer [termos ou políticas no GitHub](/github/site-policy). +Temos o direito de recusar ou remover qualquer Conteúdo Gerado por Usuário que, a nosso exclusivo critério, viole quaisquer leis ou [termos ou políticas do GitHub](/github/site-policy). Conteúdo Gerado pelo Usuário disposto no GitHub para dispositivos móveis pode estar sujeito aos termos adicionais de aplicativos móveis. #### 3. Propriedade do conteúdo, Direito de postar; Concessões de licença Você mantém a propriedade e a responsabilidade pelo seu conteúdo. Se você está postando qualquer coisa que você não criou ou não possui os direitos, você concorda que é responsável por qualquer conteúdo que você publique; que você só enviará Conteúdo que você tem o direito de publicar; e que você esteja em total conformidade com licenças de terceiros relacionadas ao Conteúdo que você publicar. @@ -106,9 +106,9 @@ Você mantém a propriedade e a responsabilidade pelo seu conteúdo. Se você es Porque você retem a propriedade e a responsabilidade do seu conteúdo, precisamos que você nos conceda — e outros usuários do GitHub — certas permissões legais, listadas nas Seções D.4 — D.7. Estas concessões de licença se aplicam ao Seu Conteúdo. Se você fizer upload de Conteúdo que já vem com uma licença que concede ao GitHub as permissões que precisamos para executar nosso Serviço, nenhuma licença adicional é necessária. Você compreende que não receberá nenhum pagamento por qualquer um dos direitos concedidos nas Seções D.4 — D.7. As licenças que você nos concede terminarão quando você remover Seu Conteúdo de nossos servidores, a menos que outros Usuários o tenham bifurcado. #### 4. Concessão de licença para nós -Precisamos do direito legal para fazer coisas como hospedar Seu Conteúdo, publicá-lo, e compartilhá-lo. Você concede a nós e aos nossos sucessores legais o direito de armazenar, analisar e exibir Seu Conteúdo, e fazer cópias acessórias conforme necessário para renderizar o Site e fornecer o Serviço. Isto inclui o direito de fazer coisas como copiá-lo para a nossa base de dados e fazer backups; mostrá-lo para você e para outros usuários; analisá-lo em um índice de pesquisa ou analisá-lo em nossos servidores; compartilhá-lo com outros usuários; e executá-lo, no caso de Seu Conteúdo ser algo como música ou vídeo. +Precisamos do direito legal para fazer coisas como hospedar Seu Conteúdo, publicá-lo, e compartilhá-lo. Você concede a nós e aos nossos sucessores legais o direito de armazenar, arquivar, analisar e exibir Seu Conteúdo, e fazer cópias eventuais, conforme necessário, para fornecer o Serviço, incluindo o melhoramento do Serviço ao longo do tempo. Esta licença inclui o direito de fazer coisas como copiá-lo para a nossa base de dados e fazer backups; mostrá-lo para você e para outros usuários; analisá-lo em um índice de pesquisa ou analisá-lo em nossos servidores; compartilhá-lo com outros usuários; e executá-lo, no caso de Seu Conteúdo ser algo como música ou vídeo. -Esta licença não concede ao GitHub o direito de vender Seu Conteúdo ou, de outra forma, distribuí-lo ou usá-lo fora de nossa provisão do Serviço. +Esta licença não concede ao GitHub o direito de vender Seu Conteúdo. Isso também não concede ao GitHub o direito de distribuir ou utilizar o Seu Conteúdo fora da nossa prestação do Serviço, salvo como parte do direito de arquivar o Seu Conteúdo, o GitHub pode permitir que nossos parceiros armazenem e arquivem Seu Conteúdo em repositórios públicos, relacionados ao [GitHub Arctic Code Vault e o GitHub Archive Program](https://archiveprogram.github.com/). #### 5. Concessão de licença a outros usuários Qualquer Conteúdo gerado pelo Usuário que você publicar publicamente, incluindo problemas, comentários e contribuições para repositórios de outros Usuários, pode ser visto por outros. Definindo seus repositórios para serem vistos publicamente, você concorda em permitir que outros vejam e "bifurquem" seus repositórios (isso significa que outros podem fazer suas próprias cópias do Conteúdo de seus repositórios em repositórios que eles controlam). @@ -116,7 +116,7 @@ Qualquer Conteúdo gerado pelo Usuário que você publicar publicamente, incluin Se você definir suas páginas e repositórios para serem vistos publicamente, você concede a cada Usuário do GitHub uma licença mundial não exclusiva para uso, exibição e execução de Seu Conteúdo através do Serviço GitHub e para reproduzir Seu Conteúdo exclusivamente no GitHub, conforme permitido através da funcionalidade do GitHub (por exemplo, através da bifurcação). Você poderá conceder direitos adicionais se [adotar uma licença](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Se você está fazendo upload do Conteúdo que você não criou ou possui, você é responsável por garantir que o Conteúdo que você faz o upload é licenciado em termos que concedem essas permissões a outros Usuários do GitHub. #### 6. Contribuições na licença de repositório -Sempre que você fizer uma contribuição a um repositório que contém notificação de uma licença, você licencia sua contribuição nos mesmos termos e concorda que tem o direito de licenciar sua contribuição nesses termos. Se possui um contrato separado para licenciar suas contribuições em termos diferentes, como um contrato de licença de colaborador, esse contrato será substituído. +Sempre que você adicionar Conteúdo a um repositório que contém notificação de uma licença, você licencia esse Conteúdo nos mesmos termos e concorda que tem o direito de licenciar o Conteúdo nesses termos. Se você tiver um contrato separado para licenciar esse Conteúdo em termos diferentes, como um contrato de licença de colaborador, aquele contrato será substituído. Não é assim que as coisas já funcionam? Sim. Isso é amplamente aceito como a norma na comunidade de código aberto; é comumente referido pela abreviatura "entrada=saída". Estamos apenas tornando isso explícito. @@ -126,7 +126,7 @@ Você mantém todos os direitos morais do Seu Conteúdo que você faz upload, pu Na medida em que este contrato não é aplicável pela legislação aplicável, você concede ao GitHub os direitos que precisamos para usar Seu Conteúdo sem atribuição e fazer adaptações razoáveis do Seu Conteúdo conforme necessário para renderizar o Site e fornecer o Serviço. ### E. Repositórios privados -**Versão curta:** *Você pode ter acesso a repositórios privados. Nós tratamos o conteúdo de repositórios privados como confidencial, e só acessamos por razões de suporte, com seu consentimento, ou se necessário, por razões de segurança.* +**Versão curta:** *Tratamos o conteúdo de repositórios privados como confidencial, e só o acessamos conforme descrito na nossa Declaração de Privacidade — para fins de segurança, para auxiliar o proprietário do repositório com uma questão de suporte, para manter a integridade do Serviço, cumprir as nossas obrigações legais, se tivermos motivos para acreditar que o conteúdo está em violação da lei, ou com o seu consentimento.* #### 1. Controle de Repositórios Privados Algumas Contas podem ter repositórios privados, que permitem ao Usuário controlar o acesso ao Conteúdo. @@ -135,15 +135,14 @@ Algumas Contas podem ter repositórios privados, que permitem ao Usuário contro O GitHub considera o conteúdo de repositórios privados como confidencial para você. O GitHub protegerá o conteúdo de repositórios privados de uso, acesso ou divulgação não autorizados da mesma forma que utilizaríamos para proteger nossas próprias informações confidenciais de natureza semelhante e, em todo caso, com um grau de cuidado razoável. #### 3. Access -Os funcionários do GitHub somente podem acessar o conteúdo de seus repositórios privados nas seguintes situações: -- Com o seu consentimento e conhecimento, por motivo de suporte. Se o GitHub acessar um repositório privado por motivo de suporte, nós faremos isso somente com o consentimento e conhecimento do proprietário. -- Quando o acesso é necessário por razões de segurança, incluindo quando o acesso é necessário para manter a confidencialidade, integridade, disponibilidade e resiliência contínuas dos sistemas e Serviço do GitHub. +O pessoal do GitHub só pode acessar o conteúdo dos seus repositórios privados nas situações descritas em nossa [Declaração de Privacidade](/github/site-policy/github-privacy-statement#repository-contents). Você pode optar por habilitar acesso adicional a seus repositórios privados. Por exemplo: - Você pode habilitar vários serviços do GitHub ou recursos que requerem direitos adicionais ao Seu Conteúdo em repositórios privados. Estes direitos podem variar, dependendo do serviço ou recurso, mas o GitHub continuará a tratar seu Conteúdo do repositório privado como confidencial. Se esses serviços ou recursos exigem direitos além daqueles que precisamos fornecer no Serviço GitHub, forneceremos uma explicação desses direitos. -#### 4. Exclusões -Se tivermos razões para acreditar que os conteúdos de um repositório privado estão violando a lei ou estes Termos, temos o direito de acessar, revisar e removê-los. Além disso, podemos ser [obrigados, por lei,](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar o conteúdo de seus repositórios privados. +Além disso, podemos ser [obrigados, por lei,](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar o conteúdo de seus repositórios privados. + +O GitHub fornecerá avisos sobre nosso acesso ao conteúdo do repositório privado, a menos que [para divulgação legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumprir nossas obrigações legais, ou onde de outra forma estiver vinculado por requisitos legais, para verificação automatizada ou se em resposta a uma ameaça de segurança ou outro risco à segurança. ### F. Violação de direitos autorais e política DMCA Se você acredita que o conteúdo em nosso site viola seus direitos autorais, por favor, entre em contato conosco de acordo com nossa [Política Digital Millennium Copyright Act](/articles/dmca-takedown-policy/). Se você é um proprietário de direitos autorais e acredita que o conteúdo no GitHub viola seus direitos, por favor, entre em contato conosco via [formulário DMCA](https://github.com/contact/dmca) ou envie e-mail para copyright@github.com. Poderá haver consequências jurídicas para o envio de um aviso de remoção falso ou leviano. Antes de enviar uma solicitação de remoção, você deve considerar usos legais, tais como uso justo e usos licenciados. @@ -288,7 +287,7 @@ Você concorda em nos indenizar, defender-nos e nos manter a parte de e contra q ### Q. Alterações nestes termos **Versão curta:** *Queremos que nossos usuários sejam informados de alterações importantes em nossos termos, mas algumas alterações não são tão importantes — não queremos lhe incomodar toda vez que consertamos um erro de digitação. Portanto, embora possamos modificar este contrato a qualquer momento, notificaremos os usuários de quaisquer alterações que afetem seus direitos e lhe daremos tempo para se ajustar a elas.* -Nós nos reservamos o direito, a nosso exclusivo critério, de alterar estes Termos de Serviço a qualquer momento e atualizar estes Termos de Serviço no caso de tais alterações. Nós notificaremos nossos Usuários sobre mudanças materiais neste Contrato, como alterações de preços, pelo menos 30 dias antes da mudança ter efeito, publicando um aviso em nosso Site. Para modificações não materiais, seu uso contínuo do Site constitui acordo para nossas revisões destes Termos de Serviço. Você pode ver todas as alterações nestes Termos Adicionais em nosso repositório [Política do Site](https://github.com/github/site-policy). +Nós nos reservamos o direito, a nosso exclusivo critério, de alterar estes Termos de Serviço a qualquer momento e atualizar estes Termos de Serviço no caso de tais alterações. Notificaremos nossos Usuários sobre alterações materiais neste Contrato, tais como aumentos de preço, pelo menos 30 dias antes das alterações entrarem em vigor, postando uma notificação em nosso Website ou enviando um e-mail para o endereço de e-mail principal especificado em sua conta do GitHub. O uso contínuo do Serviço pelo Cliente após esses 30 dias constitui concordância com essas revisões deste Contrato. Para quaisquer outras modificações, seu uso contínuo do Website constitui acordo com nossas revisões destes Termos de Serviço. Você pode ver todas as alterações nestes Termos Adicionais em nosso repositório [Política do Site](https://github.com/github/site-policy). Nós nos reservamos o direito de, a qualquer momento e de vez em quando, modificar ou descontinuar, temporariamente ou permanentemente, o Site (ou qualquer parte dele) com ou sem aviso prévio. diff --git a/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index 2710f560c7..0d9c953679 100644 --- a/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -28,7 +28,7 @@ Com relação às suas informações pessoais, os residentes da Califórnia pode Os residentes da Califórnia têm o direito de solicitar uma divulgação comercial das categorias e partes específicas das suas informações pessoais recolhidas nos 12 meses anteriores, as categorias de fontes a partir das quais tais informações pessoais são coletadas, a empresa ou o fim comercial para os quais foram realizadas a coleta ou a venda dessas informações pessoais, e as categorias de terceiros com quem a empresa compartilha informações pessoais. -Se você solicitar que uma empresa divulgue categorias e partes específicas de informações pessoais coletadas sobre você, você tem o direito de receber essas informações, gratuitamente, duas vezes por ano. As informações podem ser entregues por correio ou eletronicamente e, se fornecidas eletronicamente, devem estar em um formato portátil e, na medida do possível tecnicamente, facilmente utilizável de forma a permitir ao residente da Califórnia transmitir de forma relativamente fácil essas informações para outra entidade. Você pode usar a [API de Migração do Usuário](/v3/migrations/users/) GitHub para acessar e baixar seus dados. Saiba Mais [aqui](https://github.blog/2018-12-19-download-your-data/). +Se você solicitar que uma empresa divulgue categorias e partes específicas de informações pessoais coletadas sobre você, você tem o direito de receber essas informações, gratuitamente, duas vezes por ano. As informações podem ser entregues por correio ou eletronicamente e, se fornecidas eletronicamente, devem estar em um formato portátil e, na medida do possível tecnicamente, facilmente utilizável de forma a permitir ao residente da Califórnia transmitir de forma relativamente fácil essas informações para outra entidade. Você pode usar o [API de Migração de Usuário](/rest/reference/migrations#users) do GitHub para acessar e baixar seus dados. Saiba Mais [aqui](https://github.blog/2018-12-19-download-your-data/). ### 2. Direito de saber se suas informações pessoais são vendidas ou divulgadas para fins comerciais e para quem diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index 47e5bc7534..abf574972b 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -54,8 +54,6 @@ Se você vive em uma região aceita, você pode seguir essas instruções para e {% data reusables.sponsors.double-check-stripe-info %} -Se você vive em uma região não suportada e é aceito na versão beta de {% data variables.product.prodname_sponsors %}, você receberá um e-mail com instruções para fornecer seus dados bancários para que possa receber pagamentos via transferência ACH ou bancária. - {% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} diff --git a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index 966c6b68b9..301577ca6b 100644 --- a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -10,7 +10,7 @@ versions: ### Sobre o uso de dados para seu repositório privado -When you enable data use for your private repository, you'll be able to access the dependency graph, where you can track your repository's dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)" +Ao habilitar o uso de dados para seu repositório privado, poderá acessar o gráfico de dependências, em que você pode acompanhar as dependências do repositório e receber {% data variables.product.prodname_dependabot_alerts %} quando o {% data variables.product.product_name %} detectar dependências vulneráveis. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)" ### Habilitar ou desabilitar os recursos de uso de dados diff --git a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md index fec89c85c4..f044b8e78c 100644 --- a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md +++ b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md @@ -10,7 +10,7 @@ versions: O {% data variables.product.product_name %} os metadados de repositório e de perfil da atividade da conta pessoal. Você pode exportar os dados da conta pessoal por meio das configurações do {% data variables.product.prodname_dotcom_the_website %} ou com a API de migração de usuários. -Para obter mais informações sobre os dados que {% data variables.product.product_name %} armazena e que estão disponíveis para exportação, consulte "[Fazer download do arquivo de migração de usuário](/v3/migrations/users/#download-a-user-migration-archive)" e "[Sobre o uso dos seus dados pelo {% data variables.product.product_name %}](/articles/about-github-s-use-of-your-data). +Para obter mais informações sobre os dados que {% data variables.product.product_name %} armazena e que estão disponíveis para exportação, consulte "[Fazer download do arquivo de migração de usuário](/rest/reference/migrations#download-a-user-migration-archive)" e "[Sobre o uso dos seus dados pelo {% data variables.product.product_name %}](/articles/about-github-s-use-of-your-data). Quando você solicita a exportação dos seus dados pessoais por meio das configurações do {% data variables.product.prodname_dotcom_the_website %}, o {% data variables.product.product_name %} empacota seus dados pessoais em um arquivo `tar.gz` e envia um e-mail para seu endereço de e-mail principal com um link para download. diff --git a/translations/pt-BR/content/github/using-git/about-git-subtree-merges.md b/translations/pt-BR/content/github/using-git/about-git-subtree-merges.md index c81c4fda1a..3c0d319be8 100644 --- a/translations/pt-BR/content/github/using-git/about-git-subtree-merges.md +++ b/translations/pt-BR/content/github/using-git/about-git-subtree-merges.md @@ -105,5 +105,5 @@ $ git pull -s subtree spoon-knife main ### Leia mais -- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) +- [O capítulo "Mesclagem avançada" do livro _Pro Git_](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) - "[Como usar a estratégia de merge de subárvore](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)" diff --git a/translations/pt-BR/content/github/using-git/changing-a-remotes-url.md b/translations/pt-BR/content/github/using-git/changing-a-remotes-url.md index 59d389793e..fa56e279dc 100644 --- a/translations/pt-BR/content/github/using-git/changing-a-remotes-url.md +++ b/translations/pt-BR/content/github/using-git/changing-a-remotes-url.md @@ -53,7 +53,7 @@ git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY Na próxima vez que você aplicar `git fetch`, `git pull` ou `git push` no repositório remote, precisará fornecer seu nome de usuário e a senha do GitHub. {% data reusables.user_settings.password-authentication-deprecation %} -You can [use a credential helper](/github/using-git/caching-your-github-credentials-in-git) so Git will remember your GitHub username and personal access token every time it talks to GitHub. +Você pode [usar um auxiliar de credenciais](/github/using-git/caching-your-github-credentials-in-git) para que o Git lembre seu nome de usuário e token de acesso pessoal toda vez que conversar com o GitHub. ### Mudar as URLs remotas de HTTPS para SSH diff --git a/translations/pt-BR/content/github/using-git/pushing-commits-to-a-remote-repository.md b/translations/pt-BR/content/github/using-git/pushing-commits-to-a-remote-repository.md index fabbb7bfc4..9478da8f4d 100644 --- a/translations/pt-BR/content/github/using-git/pushing-commits-to-a-remote-repository.md +++ b/translations/pt-BR/content/github/using-git/pushing-commits-to-a-remote-repository.md @@ -98,4 +98,4 @@ Para obter mais informações sobre como trabalhar com bifurcações, consulte " - [Página do manual `git remote`](https://git-scm.com/docs/git-remote.html) - "[Folha de consultas Git](/articles/git-cheatsheet)" - "[Fluxos de trabalho Git](/articles/git-workflows)" -- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" +- "[Manual do Git](https://guides.github.com/introduction/git-handbook/)" diff --git a/translations/pt-BR/content/github/using-git/setting-your-username-in-git.md b/translations/pt-BR/content/github/using-git/setting-your-username-in-git.md index 2ecb537f4f..e20ea41f96 100644 --- a/translations/pt-BR/content/github/using-git/setting-your-username-in-git.md +++ b/translations/pt-BR/content/github/using-git/setting-your-username-in-git.md @@ -20,13 +20,13 @@ Alterar o nome associado aos commits do Git usando o `git config` afeta somente 2. {% data reusables.user_settings.set_your_git_username %} ```shell $ git config --global user.name "Mona Lisa" - ``` + ``` 3. {% data reusables.user_settings.confirm_git_username_correct %} ```shell $ git config --global user.name > Mona Lisa - ``` + ``` ### Configurar o nome de usuário do Git para um repositório específico @@ -37,13 +37,13 @@ Alterar o nome associado aos commits do Git usando o `git config` afeta somente 3. {% data reusables.user_settings.set_your_git_username %} ```shell $ git config user.name "Mona Lisa" - ``` + ``` 3. {% data reusables.user_settings.confirm_git_username_correct %} ```shell $ git config user.name > Mona Lisa - ``` + ``` ### Leia mais diff --git a/translations/pt-BR/content/github/using-git/updating-credentials-from-the-macos-keychain.md b/translations/pt-BR/content/github/using-git/updating-credentials-from-the-macos-keychain.md index fa12971044..ebc0d000f3 100644 --- a/translations/pt-BR/content/github/using-git/updating-credentials-from-the-macos-keychain.md +++ b/translations/pt-BR/content/github/using-git/updating-credentials-from-the-macos-keychain.md @@ -1,6 +1,6 @@ --- title: Atualizar credenciais da keychain OSX -intro: 'You''ll need to update your saved credentials in the `git-credential-osxkeychain` helper if you change your{% if currentVersion != "github-ae@latest" %} username, password, or{% endif %} personal access token on {% data variables.product.product_name %}.' +intro: 'Você precisará atualizar suas credenciais salvas no auxiliar `git-credential-osxkeychain` se você alterar o seu {% if currentVersion ! "github-ae@latest" %} nome de usuário, senha ou{% endif %} token de acesso pessoal em {% data variables.product.product_name %}.' redirect_from: - /articles/updating-credentials-from-the-osx-keychain - Entrada de senha do GitHub na keychain @@ -21,7 +21,7 @@ versions: ### Excluir credenciais pela linha de comando -Through the command line, you can use the credential helper directly to erase the keychain entry. +Através da linha de comando, você pode usar o auxiliar de credenciais diretamente para apagar a entrada de keychain. ```shell $ git credential-osxkeychain erase @@ -30,7 +30,7 @@ protocol=https > [Pressione Return] ``` -Se a ação for bem-sucedida, nada será impresso. To test that it works, try and clone a repository from {% data variables.product.product_location %}. If you are prompted for a password, the keychain entry was deleted. +Se a ação for bem-sucedida, nada será impresso. Para testar se funcionou, experimente clonar um repositório do {% data variables.product.product_location %}. Se for solicitada uma senha, significa que a entrada da keychain foi excluída. ### Leia mais diff --git a/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md b/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md index d3af5d4197..73bbd36def 100644 --- a/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md @@ -3,7 +3,7 @@ title: Qual URL remote eu devo usar? redirect_from: - /articles/which-url-should-i-use/ - /articles/which-remote-url-should-i-use -intro: 'Existem várias maneiras de clonar repositórios disponíveis no {% data variables.product.prodname_dotcom %}.' +intro: 'Existem várias maneiras de clonar repositórios disponíveis no {% data variables.product.product_location %}.' versions: free-pro-team: '*' enterprise-server: '*' @@ -16,7 +16,7 @@ Para obter informações sobre como configurar ou alterar URL remota, consulte " ### Clonando com as URLs de HTTPS -As URLs de clone de `https://` estão disponíveis em todos os repositórios, públicos e privados. Essas URLs funcionam mesmo se você estiver atrás de um firewall ou proxy. +The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy. Quando você aplicar `git clone`, `git fetch`, `git pull` ou `git push` a um repositório remote usando URLS de HTTPS na linha de comando, o Git solicitará o seu nome de usuário e sua senha do {% data variables.product.product_name %}. {% data reusables.user_settings.password-authentication-deprecation %} @@ -44,7 +44,7 @@ Quando você aplicar `git clone`, `git fetch`, `git pull` ou `git push` a um rep {% tip %} -**Dica**: Você pode usar uma URL com SSH para clonar um repositório para o seu computador ou como uma forma segura de implantar seu código nos servidores de produção. Você também pode usar o encaminhamento de agente SSH com o seu script de implantação para evitar o gerenciamento de chaves no servidor. Para obter mais informações, consulte "[Usar o encaminhamento do agente SSH](/v3/guides/using-ssh-agent-forwarding/)." +**Dica**: Você pode usar uma URL com SSH para clonar um repositório para o seu computador ou como uma forma segura de implantar seu código nos servidores de produção. Você também pode usar o encaminhamento de agente SSH com o seu script de implantação para evitar o gerenciamento de chaves no servidor. Para obter mais informações, consulte "[Usar o encaminhamento do agente SSH](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} @@ -60,9 +60,9 @@ Você também pode instalar o {% data variables.product.prodname_cli %} para usa ### Clonar com o Subversion Você também pode usar um cliente de [Subversion](https://subversion.apache.org/) para acessar qualquer repositório no {% data variables.product.prodname_dotcom %}. O Subversion oferece um conjunto de recursos diferente do Git. Para obter mais informações, consulte "[Quais são as diferenças entre Subversion e Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" -You can also access repositories on +Você também pode acessar repositórios em -{% data variables.product.prodname_dotcom %} from Subversion clients. Para obter mais informações, consulte "[Suporte para clientes do Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)". +{% data variables.product.prodname_dotcom %} dos clientes de Subversion. Para obter mais informações, consulte "[Suporte para clientes do Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)". {% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/using-git/why-is-git-always-asking-for-my-password.md b/translations/pt-BR/content/github/using-git/why-is-git-always-asking-for-my-password.md index cb06bb75de..11dc1412fd 100644 --- a/translations/pt-BR/content/github/using-git/why-is-git-always-asking-for-my-password.md +++ b/translations/pt-BR/content/github/using-git/why-is-git-always-asking-for-my-password.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -Usar uma URL remota do tipo HTTPS tem algumas vantagens em comparação com o uso de SSH. É mais fácil configurar do que SSH e geralmente funciona por meio de firewalls e proxies rigorosos. However, it also prompts you to enter your {% data variables.product.product_name %} credentials every time you pull or push a repository. +Usar uma URL remota do tipo HTTPS tem algumas vantagens em comparação com o uso de SSH. É mais fácil configurar do que SSH e geralmente funciona por meio de firewalls e proxies rigorosos. No entanto, ele também pede que você insira suas credenciais de {% data variables.product.product_name %} sempre que você fizer pull ou push de um repositório. {% data reusables.user_settings.password-authentication-deprecation %} -Você pode evitar que seja solicitada a sua senha ao configurar o Git para [armazenar suas credenciais](/github/using-git/caching-your-github-credentials-in-git) para você. Once you've configured credential caching, Git automatically uses your cached personal access token when you pull or push a repository using HTTPS. +Você pode evitar que seja solicitada a sua senha ao configurar o Git para [armazenar suas credenciais](/github/using-git/caching-your-github-credentials-in-git) para você. Uma vez que você configurado o armazenamento de credenciais, o Git usa automaticamente seu token de acesso pessoal armazenado quando você extrai ou faz push de um repositório usando HTTPS. ### Leia mais diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index ee6e10f5bc..34f7b339a3 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -1,84 +1,84 @@ --- -title: About the dependency graph -intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' +title: Sobre o gráfico de dependências +intro: 'Informações detalhadas sobre o gráfico de dependência, os ecossistemas que apoia e como determina quais pacotes um repositório depende.' versions: free-pro-team: '*' enterprise-server: '*' --- -### Dependency graph availability +### Disponibilidade do gráfico de dependências -The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} +O gráfico de dependências está disponível para todos{% if currentVersion == "free-pro-team@latest" %} os repositórios públicos{% endif %} que definem dependências em um ecossistema de pacote suportado usando um formato de arquivo suportado. {% if currentVersion == "free-pro-team@latest" %} Os administradores do repositório também podem configurar o gráfico de dependências para repositórios privados.{% endif %} {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### Sobre o gráfico de dependências -The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: +O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Para cada repositório, é exibido{% if currentVersion == "free-pro-team@latest" %}: -- Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} +- As dependências, os ecossistemas e os pacotes do qual depende +- Dependentes, os repositórios e pacotes que dependem dele{% else %} dependências, isto é, os ecossistemas e pacotes de que ele depende. O {% data variables.product.prodname_ghe_server %} não calcula informações sobre dependentes, repositórios e pacotes que dependem de um repositório.{% endif %} -When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. +Ao fazer push de um commit para {% data variables.product.product_name %} que altera ou adiciona um manifesto compatível ou um arquivo de bloqueio para o branch-padrão, o gráfico de dependências é atualizado automaticamente.{% if currentVersion == "free-pro-team@latest" %} Além disso, o gráfico é atualizado quando alguém faz push de uma alteração no repositório de uma de suas dependências.{% endif %} Para informações sobre os ecossistemas compatíveis e arquivos de manifesto, consulte "[ecossistemas de pacote compatíveis](#supported-package-ecosystems)" abaixo. -### Dependencies included +### Dependências incluídas -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +O gráfico de dependências inclui todas as dependências de um repositório detalhadas nos arquivos de manifesto e de bloqueio ou seu equivalente para ecossistemas compatíveis. Isto inclui: -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio +- Dependências indiretas dessas dependências diretas, também conhecidas como dependências transitórias ou subdependências -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +O gráfico de dependências identifica dependências indiretas{% if currentVersion == "free-pro-team@latest" %} explicitamente a partir de um arquivo de bloqueio ou verificando as dependências de suas dependências diretas. Para o gráfico mais confiável, você deve usar os arquivos de bloqueio (ou o equivalente deles), pois definem exatamente quais versões das dependências diretas e indiretas você usa atualmente. Se você usar arquivos de bloqueio, você também terá certeza de que todos os contribuidores do repositório usarão as mesmas versões, o que facilitará para você testar e depurar o código{% else %} dos arquivos de bloqueio{% endif %}. {% if currentVersion == "free-pro-team@latest" %} -### Dependents included +### Dependentes incluídos -For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} +Para repositórios públicos, apenas repositórios públicos que dependem dele ou de pacotes que publica são relatados. Essas informações não foram relatadas para repositórios privados.{% endif %} -### Using the dependency graph +### Usar o gráfico de dependências -You can use the dependency graph to: +Você pode usar o gráfico de dependências para: -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +- Explore os repositórios dos quais o seu código depende {% if currentVersion == "free-pro-team@latest" %} e aqueles que dependem dele {% endif %}. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)". {% if currentVersion == "free-pro-team@latest" %} +- Visualizar um resumo das dependências usadas nos repositórios da sua organização em um único painel. Para obter mais informações, consulte "[Visualizar informações na organização](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %} +- Ver e atualizar dependências vulneráveis no seu repositório. O gráfico de dependências lista dependências vulneráveis antes de outras dependências. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" -### Enabling the dependency graph +### Habilitar o gráfico de dependências -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Para gerar um gráfico dependente, {% data variables.product.product_name %} precisa de acesso somente-leitura ao manifesto dependência e aos arquivos de bloqueios de um repositório. O gráfico de dependências é gerado automaticamente para todos os repositórios públicos e você pode optar por habilitá-lo para repositórios privados. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if enterpriseServerVersions contém currentVersion and currentVersion ver_gt "enterprise-server@2. 1" %}Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server){% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e os alertas de segurança. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". {% endif %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +Quando o gráfico de dependências é ativado pela primeira vez, todos manifesto e arquivos de bloqueio para ecossistemas suportados são analisados imediatamente. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Uma vez habilitado, o gráfico é atualizado automaticamente a cada push para o repositório{% if currentVersion == "free-pro-team@latest" %} e cada push para outros repositórios no gráfico{% endif %}. -### Supported package ecosystems +### Ecossistemas de pacote compatíveis -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +Os formatos recomendados definem explicitamente quais versões são usadas para todas as dependências diretas e indiretas. Se você usar esses formatos, seu gráfico de dependências será mais preciso. Ele também reflete a configuração da criação atual e permite que o gráfico de dependências relate vulnerabilidades em dependências diretas e indiretas.{% if currentVersion == "free-pro-team@latest" %} As dependências indiretas que são inferidas a partir de um arquivo de manifesto (ou equivalente) são excluídas das verificações de dependências vulneráveis.{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| Gerenciador de pacotes | Linguagem | Formatos recomendados | Todos os formatos compatíveis | +| ---------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | +| Maven | Java, Scala | `pom.xml` | `pom.xml` | +| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json` | +| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**Observação:** se você listar suas dependências de Python em um arquivo `setup.py`, será provável que não possamos analisar e listar cada dependência no seu projeto. {% endnote %} -### Further reading +### Leia mais -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia -- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} +- "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia +- "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} +- "[Visualizar ideias para sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index 4642bc9b4b..372a9f9dcc 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -14,7 +14,7 @@ versions: ### Sobre contribuidores -You can view the top 100 contributors to a repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, including commit co-authors,{% endif %} in the contributors graph. Commits de merge e commits vazios não são contabilizados como contribuições para este gráfico. +Você pode ver os 100 principais colaboradores de um repositório{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, incluindo os coautores do commit,{% endif %} no gráfico de contribuidores. Commits de merge e commits vazios não são contabilizados como contribuições para este gráfico. {% if currentVersion == "free-pro-team@latest" %} Você também pode ver uma lista de pessoas que contribuíram para as dependências Python do projeto. Para acessar essa lista de contribuidores da comunidade, visite `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. @@ -32,14 +32,14 @@ Você também pode ver uma lista de pessoas que contribuíram para as dependênc Se você não aparecer no gráfico de contribuidores de um repositório, pode ser que: - Você não seja um dos 100 principais contribuidores. - Não tenha sido feito merge dos seus commits no branch padrão. -- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}. +- O endereço de e-mail que você usou para criar os commits não está conectado à sua conta em {% data variables.product.product_name %}. {% tip %} -**Dica:** para listar todos os contribuidores de commit em um repositório, consulte "[Repositórios](/v3/repos/#list-contributors)". +**Dica:** para listar todos os contribuidores de commit em um repositório, consulte "[Repositórios](/rest/reference/repos#list-contributors)". {% endtip %} Se todos os seus commits no repositório estiverem em branches não padrão, você não estará no gráfico de contribuidores. Por exemplo, os commits no branch `gh-pages` só serão incluídos no gráfico se `gh-pages` for o branch padrão do repositório. Para que seja feito merge dos seus commits no branch padrão, você precisa criar uma pull request. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)". -If the email address you used to author the commits is not connected to your account on {% data variables.product.product_name %}, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address){% if currentVersion != "github-ae@latest" %}" and "[Adding an email address to your {% data variables.product.product_name %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}." +Se o endereço de e-mail que você usou para criar os commits não estiver conectado à sua conta em {% data variables.product.product_name %}, seus commits não serão vinculados à sua conta e você não aparecerá no gráfico de contribuidores. Para obter mais informações, consulte "[Definir o seu endereço de e-mail de commit](/articles/setting-your-commit-email-address){% if currentVersion ! "github-ae@latest" %}" e "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.product_name %} ](/articles/adding-an-email-address-to-your-github-account){% endif %}". diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md index 5597ba9682..a5ad17ab36 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md @@ -1,28 +1,27 @@ --- -title: Viewing traffic to a repository -intro: 'Anyone with push access to a repository can view its traffic, including full clones (not fetches), visitors from the past 14 days, referring sites, and popular content in the traffic graph.' -product: 'This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[About repository graphs](/articles/about-repository-graphs)" and "[{% data variables.product.prodname_dotcom %}''s products](/articles/github-s-products)."{% endif %}' +title: Exibir tráfego para um repositório +intro: 'No gráfico de tráfego, qualquer pessoa com acesso push a um repositório pode visualizar o tráfego dele, inclusive clones completos (e não fetches), visitantes nos últimos 14 dias, sites de referência e conteúdo popular.' +product: 'Este gráfico de informações do repositório está disponível em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} e {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Sobre gráficos do repositório](/articles/about-repository-graphs)" e "[produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)."{% endif %}' redirect_from: - /articles/viewing-traffic-to-a-repository versions: free-pro-team: '*' --- -You can navigate to referring sites, excluding search engines and {% data variables.product.product_name %} itself, from the links the specific paths were referred from. The popular content links to the specific content that generated traffic. +A partir dos links indicados nos caminhos especificados, é possível navegar para sites de referência, exceto mecanismos de pesquisa e o {% data variables.product.product_name %} em si. O conteúdo popular tem links para o conteúdo específico que gerou o tráfego. -Referring sites and popular content are ordered by views and unique visitors. Full clones and visitor information update hourly, while referring sites and popular content sections update daily. All data in the traffic graph uses the UTC+0 timezone, regardless of your location. +Os sites de referência e o conteúdo popular são ordenados por exibições e visitantes exclusivos. As informações sobre visitantes e clones completos são atualizadas a cada hora, enquanto que as seções de conteúdo popular e sites de referência são atualizadas diariamente. Todos os dados no gráfico de tráfego usam o fuso horário UTC+0, independentemente de onde você está localizado. {% tip %} -**Tip:** You can hover over a specific day in the traffic graph to view the exact data for that day. +**Dica:** passe o mouse sobre um dia específico no gráfico de tráfego para visualizar os dados exatos desse dia. {% endtip %} -![Repository traffic graphs with tooltip](/assets/images/help/graphs/repo_traffic_graphs_tooltip_dotcom.png) +![Gráficos de tráfego do repositório com dica de ferramenta](/assets/images/help/graphs/repo_traffic_graphs_tooltip_dotcom.png) -### Accessing the traffic graph +### Acessar o gráfico de tráfego {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} -3. In the left sidebar, click **Traffic**. -![Traffic tab](/assets/images/help/graphs/traffic_tab.png) +3. Na barra lateral esquerda, clique em **Tráfego**. ![Guia Traffic (Tráfego)](/assets/images/help/graphs/traffic_tab.png) diff --git a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index 70bf122614..df4c0cf6a5 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -28,7 +28,7 @@ versions: O Jekyll é um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %} e um processo de compilação simplificado. O Jekyll usa arquivos Markdown e HTML, além de criar um site estático completo com base na sua escolha de layouts. O Jekyll aceita Markdown e Liquid, uma linguagem de modelagem que carrega conteúdo dinâmico no site. Para obter mais informações, consulte [Jekyll](https://jekyllrb.com/). -O Jekyll não é oficialmente compatível com o Windows. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation. +O Jekyll não é oficialmente compatível com o Windows. Para obter mais informações, consulte "[Jekyll no Windows](http://jekyllrb.com/docs/windows/#installation)" na documentação do Jekyll. É recomendável usar o Jekyll com o {% data variables.product.prodname_pages %}. Se preferir, você pode usar outros geradores de site estáticos ou personalizar seu próprio processo de compilação localmente ou em outro servidor. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)". diff --git a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md index aed2ddd6d9..a4b5098601 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md @@ -36,15 +36,15 @@ sites de {% data variables.product.prodname_pages %} nos repositórios da organi Há três tipos de site do {% data variables.product.prodname_pages %}: projeto, usuário e organização. Os sites de projeto são conectados a um projeto específico hospedado no {% data variables.product.product_name %}, como uma biblioteca do JavaScript ou um conjunto de receitas. Os sites de usuário e organização são conectados a uma conta específica do {% data variables.product.product_name %}. -To publish a user site, you must create a repository owned by your user account that's named {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. Para publicar um site da organização, você deve criar um repositório pertencente a uma organização denominada {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, user and organization sites are available at `http(s)://.github.io` or `http(s)://.github.io`.{% elsif currentVersion == "github-ae@latest" %}User and organization sites are available at `http(s)://pages./` or `http(s)://pages./`.{% endif %} +Para publicar um site de usuário, você deve criar um repositório pertencente à sua conta de usuário denominada {% if currentVersion == "free-pro-team@latest" %}`. ithub.io`{% else %}`.`{% endif %}. Para publicar um site da organização, você deve criar um repositório pertencente a uma organização denominada {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}A menos que você esteja usando um domínio personalizado, os sites de usuário e organização estarão disponíveis em `http(s)://.github.io` ou `http(s)://.github.io`.{% elsif currentVersion == "github-ae@latest" %}Sites de usuário e organização estão disponíveis em `http(s)://pages./` ou `http(s)://pages./`.{% endif %} -Os arquivos de origem de um site de projeto são armazenados no mesmo repositório que o respectivo projeto. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} +Os arquivos de origem de um site de projeto são armazenados no mesmo repositório que o respectivo projeto. {% if currentVersion == "free-pro-team@latest" %}A menos que você esteja usando um domínio personalizado, os sites de projeto estão disponíveis em `http(s)://.github.io/` ou `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Os sites de projeto estão disponíveis em `http(s)://pages.///` ou `http(s)://pages.///`.{% endif %} {% if currentVersion == "free-pro-team@latest" %} Para obter mais informações sobre como os domínios personalizados afetam o URL do seu site, consulte "[Sobre domínios personalizados e {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". {% endif %} -You can only create one user or organization site for each account on {% data variables.product.product_name %}. Os sites de projeto, sejam eles de uma conta de organização ou de usuário, são ilimitados. +Você só pode criar um site de usuário ou organização para cada conta em {% data variables.product.product_name %}. Os sites de projeto, sejam eles de uma conta de organização ou de usuário, são ilimitados. {% if enterpriseServerVersions contains currentVersion %} A URL em que o site está disponível depende da habilitação do isolamento de subdomínio para @@ -53,9 +53,9 @@ A URL em que o site está disponível depende da habilitação do isolamento de | Tipo de site | Isolamento de subdomínio habilitado | Isolamento de subdomínio desabilitado | | ------------ | ----------------------------------- | ------------------------------------- | | | | | - User | + Usuário | -`http(s)://pages./` | `http(s):///pages/` | Organization | `http(s)://pages./` | `http(s):///pages/` | Project site owned by user account | `http(s)://pages.///` | `http(s):///pages///` Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` +`http(s)://pages./` | `http(s):///pages/` | Organization | `http(s)://pages./` | `http(s):///pages/` | Site do projeto pertencente a uma conta do usuário | `http(s)://pages.///` | `http(s):///pages///` Site do projeto pertencente a uma conta da organização | `http(s)://pages.///` | `http(s):///pages///` Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" ou contate o administrador do site. {% endif %} @@ -63,7 +63,7 @@ Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** Repositories using the legacy `.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://.github.com` to `http(s)://.github.io`. If both a `.github.com` and `.github.io` repository exist, only the `.github.io` repository will be published. +**Observação:** os repositórios que usam o esquema de nomenclatura `.github.com` herdado ainda são publicados, mas os visitantes serão redirecionados de `http(s)://.github.com` para `http(s)://.github.io`. Se ambos os repositórios, `.github.com` e `.github.io` existirem, somente o repositório `.github.io` será publicado. {% endnote %} {% endif %} @@ -150,4 +150,4 @@ Embora não seja possível especificar tipos de MIME personalizados por arquivo ### Leia mais - [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) em {% data variables.product.prodname_learning %} -- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)" +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index eac5c83972..9412801a23 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -16,7 +16,7 @@ versions: Às vezes, {% data variables.product.prodname_pages %} não tentará criar seu site depois que você fizer push das alterações na fonte de publicação do site.{% if currentVersion == "free-pro-team@latest" %} - A pessoa que fez push das alterações não verificou o endereço de e-mail dela. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)".{% endif %} -- Você está fazendo push com uma chave de implantação. Se desejar automatizar pushes para o repositório do seu site, você poderá configurar um usuário de máquina. Para obter mais informações, consulte "[Gerenciar chaves de implantação](/v3/guides/managing-deploy-keys/#machine-users)". +- Você está fazendo push com uma chave de implantação. Se desejar automatizar pushes para o repositório do seu site, você poderá configurar um usuário de máquina. Para obter mais informações, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys#machine-users)". - Você está usando um serviço de CI que não está configurado para criar sua fonte de publicação. Por exemplo, Travis CI não criará o branch `gh-pages`, a menos que você adicione o branch a uma lista segura. Para obter mais informações, consulte "[Personalizar a criação](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" em Travis CI ou na documentação do seu serviço de CI. {% note %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index c02beb7e31..ca8a742080 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -1,25 +1,25 @@ --- -title: Creating a GitHub Pages site with Jekyll -intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.' +title: Criar um site do GitHub Pages com o Jekyll +intro: 'É possível usar o Jekyll para criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou existente.' product: '{% data reusables.gated-features.pages %}' redirect_from: - /articles/creating-a-github-pages-site-with-jekyll -permissions: 'People with admin permissions for a repository can create a {% data variables.product.prodname_pages %} site with Jekyll.' +permissions: 'Pessoas com permissões de administrador para um repositório podem criar um site do {% data variables.product.prodname_pages %} com o Jekyll.' versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### Prerequisites +### Pré-requisitos -Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." +Antes de poder usar o Jekyll para criar um site do {% data variables.product.prodname_pages %}, você precisa instalar o Jekyll e o Git. Para obter mais informações, consulte [Instalação](https://jekyllrb.com/docs/installation/) na documentação do Jekyll e "[Configurar o Git](/articles/set-up-git)". {% data reusables.pages.recommend-bundler %} {% data reusables.pages.jekyll-install-troubleshooting %} -### Creating a repository for your site +### Criar um repositório para seu site {% data reusables.pages.new-or-existing-repo %} @@ -30,59 +30,58 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages % {% data reusables.pages.create-repo-name %} {% data reusables.repositories.choose-repo-visibility %} -### Creating your site +### Criar seu site {% data reusables.pages.must-have-repo-first %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository. +2. Se você ainda não tem uma cópia do seu repositório, navegue até o local onde deseja armazenar os arquivos de origem do seu site, substituindo _PARENT-FOLDER_ pela pasta que deverá conter a pasta do repositório. ```shell $ cd PARENT-FOLDER ``` -3. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository. +3. Caso você ainda não o tenha feito, inicialize um repositório Git local, substituindo _REPOSITORY-NAME_ pelo nome do seu repositório. ```shell $ git init REPOSITORY-NAME > Initialized empty Git repository in /Users/octocat/my-site/.git/ - # Creates a new folder on your computer, initialized as a Git repository - ``` - 4. Change directories to the repository. + # Cria uma nova pasta no seu computador, inicializada como um repositório Git + ``` + 4. Altere os diretórios no repositório. ```shell $ cd REPOSITORY-NAME - # Changes the working directory + # Altera o diretório de trabalho ``` {% data reusables.pages.decide-publishing-source %} {% data reusables.pages.navigate-publishing-source %} - For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. + Por exemplo, se você escolheu publicar o seu site a partir da pasta `documentação` no branch-padrão, crie e altere os diretórios na pasta `documentação`. ```shell $ mkdir docs - # Creates a new folder called docs + # Cria uma nova pasta chamada docs $ cd docs ``` - If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch. + Se você optou por publicar seu site a partir do branch `gh-pages`, crie e faça checkout do branch `gh-pages`. ```shell $ git checkout --orphan gh-pages - # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch + # Cria um novo branch, sem histórico ou conteúdo, chamado gh-pages e alterna para o branch gh-pages ``` - 7. To create a new Jekyll site, use the `jekyll new` command, replacing _VERSION_ with the current dependency version for Jekyll. For more information, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. - - If you installed Bundler: + 7. Para criar um novo site do Jekyll, use o comando `jekyll new`, substituindo _VERSION_ pela versão atual de dependências do Jekyll. Para obter mais informações, consulte "[Versões de dependências](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}. + - Se você instalou o bundler: ```shell $ bundle exec jekyll VERSION new . - # Creates a Jekyll site in the current directory + # Cria um site do Jekyll no diretório atual ``` - - If you don't have Bundler installed: + - Se você não tem o bundler instalado: ```shell $ jekyll VERSION new . - # Creates a Jekyll site in the current directory + # Cria um site do Jekyll no diretório atual ``` -8. Open the Gemfile that was created and follow the instructions in the Gemfile's comments to use {% data variables.product.prodname_pages %}. - ![Instructions for updating Gemfile](/assets/images/help/pages/gemfile-instructions.png) -9. Update the `gem "github-pages"` line so that the line looks like this, replacing _VERSION_ with the current dependency version for `github-pages`. For more information, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. +8. Abra o Gemfile que foi criado e siga as instruções nos comentários do Gemfile para usar o {% data variables.product.prodname_pages %}. ![Instruções para atualizar o Gemfile](/assets/images/help/pages/gemfile-instructions.png) +9. Para que a linha `gem "github-pages"` fique com a aparência mostrada a seguir, atualize-a substituindo _VERSION_ pela versão atual de dependências para `github-pages`. Para obter mais informações, consulte "[Versões de dependências](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}. ```shell gem "github-pages", "~> VERSION", group: :jekyll_plugins ``` -10. Save and close the Gemfile. -11. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." -12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository. +10. Salve e feche o Gemfile. +11. Como alternativa, teste seu site localmente. Para obter mais informações, consulte "[Testar seu site do {% data variables.product.prodname_pages %} localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". +12. Adicione seu repositório {% data variables.product.product_name %} como um remoto, substituindo {% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}_HOSTNAME_ pelo nome de host da sua empresa,{% endif %} _USUÁRIO_ pela conta proprietária do repositório{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} e _REPOSITÓRIO_ pelo nome do repositório. ```shell {% if currentVersion == "free-pro-team@latest" %} $ git remote add origin https://github.com/USER/REPOSITORY.git @@ -90,7 +89,7 @@ $ git remote add origin https://github.com/USER/REPOSITORY.git $ git remote add origin https://HOSTNAME/USER/REPOSITORY.git {% endif %} ``` -13. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on. +13. Faça push no repositório para o {% data variables.product.product_name %}, substituindo _BRANCH_ pelo nome do branch em que você está trabalhando. ```shell $ git push -u origin BRANCH ``` @@ -101,8 +100,8 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORYtoken" -X POST -d " \ #### Sobre consultas e operações de mutação -Os dois tipos de operações permitidas na API do GraphQL do GitHub são _consultas_ e _mutações_. Comparando o GraphQL com a REST, as consultas funcionam como solicitações do `GET`, enquanto as mutações funcionam como `POST`/`PATCH`/`EXCLUIR`. O [nome da mutação](/v4/mutation/) determina qual modificação é executada. +Os dois tipos de operações permitidas na API do GraphQL do GitHub são _consultas_ e _mutações_. Comparando o GraphQL com a REST, as consultas funcionam como solicitações do `GET`, enquanto as mutações funcionam como `POST`/`PATCH`/`EXCLUIR`. O [nome da mutação](/graphql/reference/mutations) determina qual modificação é executada. -Para obter informações sobre limite de taxas, consulte "[limitações de recursos do GraphQL](/v4/guides/resource-limitations/)". +Para obter informações sobre limite de taxas, consulte "[limitações de recursos do GraphQL](/graphql/overview/resource-limitations)". As consultas e mutações compartilham formas semelhantes, com algumas diferenças importantes. #### Sobre as consultas -As consultas do GraphQL retornam apenas os dados especificados. Para gerar uma consulta, você deve especificar os [campos dentro dos campos](/v4/guides/intro-to-graphql#field) (também conhecidos como _subcampos aninhados_) até que retorne apenas [escalares](/v4/scalar/). +As consultas do GraphQL retornam apenas os dados especificados. Para gerar uma consulta, você deve especificar os [campos dentro dos campos](/graphql/guides/introduction-to-graphql#field) (também conhecidos como _subcampos aninhados_) até que retorne apenas [escalares](/graphql/reference/scalars). As consultas estão estruturadas da seguinte forma: @@ -107,7 +107,7 @@ As mutações são estruturadas da seguinte forma: Neste exemplo, o objeto de entrada é `MutationNameInput` e o objeto de carga é `MutationNamePayload`. -Na referência [mutações](/v4/mutation/), os _campos de entrada_ listados são o que você passa como o objeto de entrada. Os _campos de retorno_ listados são o que você passa como objeto de carga. +Na referência [mutações](/graphql/reference/mutations), os _campos de entrada_ listados são o que você passa como o objeto de entrada. Os _campos de retorno_ listados são o que você passa como objeto de carga. Para obter um exemplo real, consulte "[Exemplo de mutação](#example-mutation)." @@ -117,7 +117,7 @@ As [Variáveis](https://graphql.github.io/learn/queries/#variables) podem tornar {% note %} -**Observação**: se você estiver usando o Explorador, certifique-se de inserir as variáveis no painel separado das [Variáveis de consulta](/v4/guides/using-the-explorer/#using-the-variable-pane), e não inclua a palavra `variáveis` antes do objeto do JSON. +**Observação**: se você estiver usando o Explorador, certifique-se de inserir as variáveis no painel separado das [Variáveis de consulta](/graphql/guides/using-the-explorer#using-the-variable-pane), e não inclua a palavra `variáveis` antes do objeto do JSON. {% endnote %} @@ -207,7 +207,7 @@ Observando a composição linha por linha: * `repository(owner:"octocat", name:"Hello-World") {` - Para começar a consulta, queremos encontrar um objeto do [`repositório`](/v4/object/repository/). A validação do esquema indica que este objeto requer um `proprietário` e um argumento do `nome`. + Para começar a consulta, queremos encontrar um objeto do [`repositório`](/graphql/reference/objects#repository). A validação do esquema indica que este objeto requer um `proprietário` e um argumento do `nome`. * `issues(last:20, states:CLOSED) {` @@ -215,9 +215,9 @@ Observando a composição linha por linha: Alguns detalhes sobre o objeto `problemas`: - - A [documentação](/v4/object/repository/) nos informa que esse objeto tem o tipo `IssueConnection`. + - A [documentação](/graphql/reference/objects#repository) nos informa que esse objeto tem o tipo `IssueConnection`. - A validação de esquema indica que este objeto exige o `último` ou `primeiro` número dos resultados como argumento. Portanto, fornecemos `20`. - - A [documentação](/v4/object/repository/) também nos informa que esse objeto aceita um argumento `estados`, que é um enum [`IssueState`](/v4/enum/issuestate/), que aceita os valores `ABERTO` ou `FECHADO`. Para encontrar apenas problemas fechados, conferimos à chave `estados` um valor de `FECHADO`. + - A [documentação](/graphql/reference/objects#repository) também nos informa que esse objeto aceita um argumento `estados`, que é um enum [`IssueState`](/graphql/reference/enums#issuestate), que aceita os valores `ABERTO` ou `FECHADO`. Para encontrar apenas problemas fechados, conferimos à chave `estados` um valor de `FECHADO`. * `edges {` @@ -225,9 +225,9 @@ Observando a composição linha por linha: * `node {` - Aqui, recuperamos o nó no fim da borda. A [documentação da`IssueConnection`](/v4/object/issueconnection) indica se o nó no final do tipo `IssueConnection` é um objeto `problema`. + Aqui, recuperamos o nó no fim da borda. A [documentação da`IssueConnection`](/graphql/reference/objects#issueconnection) indica se o nó no final do tipo `IssueConnection` é um objeto `problema`. -* Agora que sabemos que estamos recuperando um objeto `problema`, podemos ver a [documentação](/v4/object/issue) e especificar os campos que desejamos retornar: +* Agora que sabemos que estamos recuperando um objeto `problema`, podemos ver a [documentação](/graphql/reference/objects#issue) e especificar os campos que desejamos retornar: ```graphql title @@ -243,7 +243,7 @@ Observando a composição linha por linha: Aqui, especificamos os campos `título`, `url` e `etiquetas` do objeto `problema`. - O campo `etiquetas` tem o tipo [`LabelConnection`](/v4/object/labelconnection/). Assim como no objeto `problemas`, porque `etiquetas` é uma conexão, devemos percorrer suas bordas para um nó conectado: o objeto `etiqueta`. No nó, podemos especificar os campos de objeto `etiqueta` que desejamos retornar, neste caso, o `nome`. + O campo `etiquetas` tem o tipo [`LabelConnection`](/graphql/reference/objects#labelconnection). Assim como no objeto `problemas`, porque `etiquetas` é uma conexão, devemos percorrer suas bordas para um nó conectado: o objeto `etiqueta`. No nó, podemos especificar os campos de objeto `etiqueta` que desejamos retornar, neste caso, o `nome`. Você pode notar que executar essa consulta no repositório público do Octocat `Hello-World` não retornará muitas etiquetas. Tente executá-la em um dos seus próprios repositórios que usam etiquetas, e provavelmente você verá uma diferença. @@ -285,7 +285,7 @@ Vamos analisar o exemplo. A tarefa parece simples: adicione uma reação emoji a Então, como é que sabemos começar com uma consulta? Ainda não sabemos. -Uma vez que desejamos modificar os dados no servidor (anexar um emoji a um problema), começamos procurando uma mutação útil no esquema. A documentação de referência mostra a mutação [`addReaction`](/v4/mutation/addreaction) com esta descrição: `Adiciona uma reação a um assunto.` Perfeito! +Uma vez que desejamos modificar os dados no servidor (anexar um emoji a um problema), começamos procurando uma mutação útil no esquema. A documentação de referência mostra a mutação [`addReaction`](/graphql/reference/mutations#addreaction) com esta descrição: `Adiciona uma reação a um assunto.` Perfeito! A documentação para a lista de mutação lista três campos de entrada: @@ -337,13 +337,13 @@ Com a identificação conhecida, podemos prosseguir com a mutação: - `addReaction` é o nome da mutação. - `entrada` é a chave de argumento obrigatória. Isso sempre será `entrada` para uma mutação. - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` é o valor do argumento obrigatório. Este sempre será um [objeto de entrada](/v4/input_object/) (daí as chaves) compostas de campos de entrada (`subjectId` e `conteúdo`, neste caso) para uma mutação. + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` é o valor do argumento obrigatório. Este sempre será um [objeto de entrada](/graphql/reference/input-objects) (daí as chaves) compostas de campos de entrada (`subjectId` e `conteúdo`, neste caso) para uma mutação. - Como sabemos qual o valor usar para o conteúdo? Os documentos [`addReaction`](/v4/mutation/addreaction/) nos dizem que o campo do `conteúdo` tem o tipo [`ReactionContent`](/v4/enum/reactioncontent/), que é um [enum](/v4/enum), porque apenas algumas reações de emojis são compatíveis com em problemas no GitHub. Estes são os valores permitidos para reações (observe que alguns valores diferem de seus nomes de emojis correspondentes): + Como sabemos qual o valor usar para o conteúdo? Os documentos [`addReaction`](/graphql/reference/mutations#addreaction) nos dizem que o campo do `conteúdo` tem o tipo [`ReactionContent`](/graphql/reference/enums#reactioncontent), que é um [enum](/graphql/reference/enums), porque apenas algumas reações de emojis são compatíveis com em problemas no GitHub. Estes são os valores permitidos para reações (observe que alguns valores diferem de seus nomes de emojis correspondentes): {% data reusables.repositories.reaction_list %} -* O resto da chamada é composto pelo objeto da carga. Aqui é onde especificamos os dados que desejamos que o servidor retorne depois de termos efetuado a mutação. Estas linhas vêm dos documentos [`addReaction`](/v4/mutation/addreaction), que são três possíveis campos de retorno: +* O resto da chamada é composto pelo objeto da carga. Aqui é onde especificamos os dados que desejamos que o servidor retorne depois de termos efetuado a mutação. Estas linhas vêm dos documentos [`addReaction`](/graphql/reference/mutations#addreaction), que são três possíveis campos de retorno: - `clientMutationId` (`String`) - `reação` (`Reação!`) @@ -390,7 +390,7 @@ mutation($myVar:AddReactionInput!) { {% note %} Você pode notar que o valor do campo `conteúdo` no exemplo anterior (onde é usado diretamente na mutação) não tem aspas em torno de `HORAY`, mas tem aspas quando usado na variável. Há um motivo para isso: -* Ao usar `conteúdo` diretamente na mutação, o esquema espera que o valor seja do tipo [`ReactionContent`](/v4/enum/reactioncontent/), que é um _enum_, não uma string. A validação de esquema causará um erro se você adicionar aspas no valor do enum, já que as aspas são reservadas para strings. +* Ao usar `conteúdo` diretamente na mutação, o esquema espera que o valor seja do tipo [`ReactionContent`](/graphql/reference/enums#reactioncontent), que é um _enum_, não uma string. A validação de esquema causará um erro se você adicionar aspas no valor do enum, já que as aspas são reservadas para strings. * Ao usar `conteúdo` em uma variável, a seção de variáveis deve ser um JSON válido. Portanto, as aspas são necessárias. A validação de esquema interpreta corretamente o tipo `ReactionContent` quando a variável é passada para a mutação durante a execução. Para obter mais informações sobre a diferença entre enums e strings, consulte as [Especificações oficiais do GraphQL](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). diff --git a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md index 8c8ab7749b..c04c3c2d45 100644 --- a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md +++ b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md @@ -12,7 +12,7 @@ versions: ### Terminologia do GraphQL -A API do GraphQL do GitHub representa uma mudança estrutural e conceitual API REST do GitHub. Você provavelmente encontrará uma nova terminologia na [documentação de referência](/v4/) da API do GraphQL. +A API do GraphQL do GitHub representa uma mudança estrutural e conceitual API REST do GitHub. Você provavelmente encontrará uma nova terminologia na [documentação de referência](/graphql) da API do GraphQL. ### Esquema @@ -30,11 +30,11 @@ Isso significa que se você tentar retornar um campo que não é escalar, a vali ### Argumento -Um argumento é um conjunto de pares de chave-valor anexados a um campo específico. Alguns campos exigem um argumento. As [Mutações](/v4/guides/forming-calls#about-mutations) exigem um objeto de entrada como argumento. +Um argumento é um conjunto de pares de chave-valor anexados a um campo específico. Alguns campos exigem um argumento. As [Mutações](/graphql/guides/forming-calls-with-graphql#about-mutations) exigem um objeto de entrada como argumento. ### Implementação -Um esquema do GraphQL pode usar o termo _implementos_ para definir como um objeto herda de uma [interface](/v4/interface). +Um esquema do GraphQL pode usar o termo _implementos_ para definir como um objeto herda de uma [interface](/graphql/reference/interfaces). Aqui está um exemplo criado de um esquema que define a interface `X` e o objeto `Y`: @@ -55,13 +55,13 @@ Este significa que o objeto `Y` exige os mesmos mesmos tipos de campo/argumento/ Na documentação de referência, você descobrirá que: -* Cada [objeto](/v4/object) lista a(s) interface(s) _das quais herda_ em **Implementos**. +* Cada [objeto](/graphql/reference/objects) lista a(s) interface(s) _das quais herda_ em **Implementos**. -* Cada [interface](/v4/interface) lista os objetos _dos quais herdam _ em **Implementações**. +* Cada [interface](/graphql/reference/interfaces) lista os objetos _dos quais herdam _ em **Implementações**. ### Conexão -As conexões permitem que você consulte objetos relacionados às consultas como parte da mesma chamada. Com as conexões, você pode usar uma única chamada do GraphQL quando você teria que usar várias chamadas para uma API REST. Para obter mais informações, consulte "[Migrando da REST para o GraphQL](/v4/guides/migrating-from-rest)". +As conexões permitem que você consulte objetos relacionados às consultas como parte da mesma chamada. Com as conexões, você pode usar uma única chamada do GraphQL quando você teria que usar várias chamadas para uma API REST. Para obter mais informações, consulte "[Migrando da REST para o GraphQL](/graphql/guides/migrating-from-rest-to-graphql)". É útil imaginar um gráfico: pontos conectados por linhas. Os pontos são nós e as linhas são bordas. Uma conexão define uma relação entre os nós. @@ -71,7 +71,7 @@ As bordas representam conexões entre os nós. Quando você consulta uma conexã ### Nó -_Nó_ é um termo genérico para um objeto. Você pode procurar um nó diretamente pode acessar nós relacionados através de uma conexão. Se você especificar um `nó` que não retorna um [escalar](/v4/scalar), você deverá incluir subcampos até que todos os campos retornem escalares. Para obter informações sobre acesso a IDs de nó através da API REST e usá-los em consultas do GraphQL, consulte "[Usando IDs globais de nó](/v4/guides/using-global-node-ids)". +_Nó_ é um termo genérico para um objeto. Você pode procurar um nó diretamente pode acessar nós relacionados através de uma conexão. Se você especificar um `nó` que não retorna um [escalar](/graphql/reference/scalars), você deverá incluir subcampos até que todos os campos retornem escalares. Para obter informações sobre acesso a IDs de nó através da API REST e usá-los em consultas do GraphQL, consulte "[Usando IDs globais de nó](/graphql/guides/using-global-node-ids)". ## Descobrindo a API do GraphQL @@ -130,4 +130,4 @@ query { {% endnote %} - Para obter mais informações sobre como realizar consultas, consulte "[Formando de chamadas com o GraphQL](/v4/guides/forming-calls)". + Para obter mais informações sobre como realizar consultas, consulte "[Formando de chamadas com o GraphQL](/graphql/guides/forming-calls-with-graphql)". diff --git a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md index bacc1c48ab..fe63df55d1 100644 --- a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md @@ -33,7 +33,7 @@ Com a API de Contas corporativas, você pode: - Convidar os administradores para a sua conta corporativa. - Criar novas organizações na sua conta corporativa. -Para obter uma lista dos campos disponíveis da API de Contas corprativas, consulte "[campos e tipos do GraphQL para a API de Conta corporativa](/v4/guides/managing-enterprise-accounts/#graphql-fields-and-types-for-the-enterprise-accounts-api)". +Para obter uma lista dos campos disponíveis da API de Contas corprativas, consulte "[campos e tipos do GraphQL para a API de Conta corporativa](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)". ### Primeiros passos usando o GraphQL para contas corporativas @@ -187,12 +187,12 @@ Esta consulta do GraphQL solicita as últimas 5 entradas de registro para uma or } ``` -Para obter mais informações sobre como começar com GraphQL, consulte "[Introdução ao GraphQL](/v4/guides/intro-to-graphql/)" e "[Formando chamadas com o GraphQL](/v4/guides/forming-calls/)". +Para obter mais informações sobre como começar com GraphQL, consulte "[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql)" e "[Formando chamadas com o GraphQL](/graphql/guides/forming-calls-with-graphql)". ### Campos e tipos do GraphQL para a API de Contas corporativas Aqui está uma visão geral das novas consultas, mutações e tipos definidos por esquema disponíveis para uso com a API de Contas corporativas. -For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/v4/). +Para obter mais detalhes sobre as novas consultas, mutações e tipos definidos por esquema disponíveis para uso com a API de Contas corporativas, consulte a barra lateral com definições detalhadas do GraphQL a partir de qualquer [Página de referência do GraphQL](/graphql). -Você pode acessar a documentação de referência de no explorador do GraphQL no GitHub. Para obter mais informações, consulte "[Usando o explorador](/v4/guides/using-the-explorer#accessing-the-sidebar-docs). Para obter outras informações, como detalhes de autenticação e limite de taxa, confira os [guias](/v4/guides). +Você pode acessar a documentação de referência de no explorador do GraphQL no GitHub. Para obter mais informações, consulte "[Usando o explorador](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Para obter outras informações, como detalhes de autenticação e limite de taxa, confira os [guias](/graphql/guides). diff --git a/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md index ffde1fec9d..d6bd50ae2b 100644 --- a/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: Fazer a migração da REST para o GraphQL representa uma mudança significativa na lógica da API. As diferenças entre a REST como um estilo e o GraphQL como uma especificação tornam difícil —e, muitas vezes indesejável—substituir as chamadas da API REST por consultas da API do GraphQL individualmente. Incluímos abaixo exemplos específicos de migração. -Para fazer a migração do seu código da [API REST](/v3) para a API do GraphQL: +To migrate your code from the [REST API](/rest) to the GraphQL API: - Revise a [especificação do GraphQL](https://graphql.github.io/graphql-spec/June2018/) -- Revise o [esquema do GraphQL](/v4/reference/) do GitHub +- Review GitHub's [GraphQL schema](/graphql/reference) - Considere como qualquer código existente que você tem atualmente interage com a API REST do GitHub -- Use [IDs dos nó global](/v4/guides/using-global-node-ids) para fazer referência a objetos entre as versões da API +- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions As vantagens significativas do GraphQL incluem: @@ -53,12 +53,12 @@ query { } ``` -Considere outro exemplo: recuperar uma lista de pull requests e verificar se cada um é mesclável. Uma chamada para a API REST recupera uma lista de pull requests e suas [representações resumidas](/v3/#summary-representations): +Considere outro exemplo: recuperar uma lista de pull requests e verificar se cada um é mesclável. A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -Determinar se um pull request pode ser mesclado demanda recuperar cada pull request individualmente para sua [representação detalhada](/v3/#detailed-representations) (uma grande carga), bem como verificar seu atributo `mesclável` é verdadeiro ou falso: +Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ Ao usar a **API do GraphQL**, você pode recuperar os dados com uma única consu } ``` -Você também pode estender o poder dessa consulta se [substitui uma variável](/v4/guides/forming-calls/#working-with-variables) para o número do pull request. +You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. ## Exemplo: Digitação não flexível Os esquemas do GraphQL são digitados de modo rígido, o que torna o gerenciamento dos dados mais seguro. -Considere um exemplo de adição de um comentário a um problema ou pull request usando uma [mutação ](/v4/mutation) do GraphQL e especificando por engano um número inteiro em vez de uma string para o valor de [`clientMutationId`](/v4/mutation/addcomment/): +Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): ```graphql mutation { diff --git a/translations/pt-BR/content/graphql/guides/using-global-node-ids.md b/translations/pt-BR/content/graphql/guides/using-global-node-ids.md index a78da6a2d6..e0af494556 100644 --- a/translations/pt-BR/content/graphql/guides/using-global-node-ids.md +++ b/translations/pt-BR/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ Você pode acessar a maioria dos objetos do GitHub (usuários, problemas, pull r {% note %} -**Observação:** Na REST, o campo de ID do nó global é chamado `node_id`. No GraphQL, é um campo `id` na interface do `nó`. Para relembrar o que significa "nó" no GraphQL, consulte"[Introdução ao GraphQL](/v4/guides/intro-to-graphql/#node)". +**Observação:** Na REST, o campo de ID do nó global é chamado `node_id`. No GraphQL, é um campo `id` na interface do `nó`. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." {% endnote %} @@ -29,7 +29,7 @@ Vamos analisar um exemplo. ### 1. Chame um ponto final da REST que retorna o ID do nó de um objeto -Se você [solicitar o usuário autenticado](/v3/users/#get-the-authenticated-user): +If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { Este tipo de consulta—ou seja, encontrar o nó pelo ID—é conhecida como "consulta direta de nó". -Ao executar esta consulta, você verá que `__typename` é [`Usuário`](/v4/object/user/). +When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). ### 3. Faça uma pesquisa direta de nó no GraphQL @@ -122,4 +122,4 @@ Este tipo de consulta é a abordagem-padrão para consultar um objeto pelo seu I ### Usando IDs de nó global em migrações -Ao construir integrações que usam a API REST ou a API do GraphQL, considera-se uma prática recomendada persistir no ID de nó global para que você possa facilmente fazer referência a objetos entre nas versões da API. Para obter mais informações sobre como lidar com a transição entre a REST e o GraphQL, consulte "[Migrando da REST para o GraphQL](/v4/guides/migrating-from-rest/)". +Ao construir integrações que usam a API REST ou a API do GraphQL, considera-se uma prática recomendada persistir no ID de nó global para que você possa facilmente fazer referência a objetos entre nas versões da API. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." diff --git a/translations/pt-BR/content/graphql/guides/using-the-explorer.md b/translations/pt-BR/content/graphql/guides/using-the-explorer.md index bb9964c076..8be5632d54 100644 --- a/translations/pt-BR/content/graphql/guides/using-the-explorer.md +++ b/translations/pt-BR/content/graphql/guides/using-the-explorer.md @@ -13,11 +13,11 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -O [Explorador do GraphQL](/v4/explorer) é uma instância do [GraphiQL](https://github.com/graphql/graphiql), que é um "IDE do GraphiQL gráfica e interativa no mesmo navegador". +O [Explorador do GraphQL](/graphql/overview/explorer) é uma instância do [GraphiQL](https://github.com/graphql/graphiql), que é um "IDE do GraphiQL gráfica e interativa no mesmo navegador". {% note %} -**Nota**: {% data variables.product.prodname_dotcom %} desabilitou as [mutações](/v4/mutation/) no Explorador, mas você pode usá-las em sua própria instância do GraphiQL. +**Nota**: {% data variables.product.prodname_dotcom %} desabilitou as [mutações](/graphql/reference/mutations) no Explorador, mas você pode usá-las em sua própria instância do GraphiQL. {% endnote %} @@ -33,7 +33,7 @@ Para usar o aplicativo GraphiQL, faça o download e instale-o em https://github. #### Configurar GraphiQL -1. Obtenha um [token do OAuth](/v4/guides/forming-calls#authenticating-with-graphql). +1. Obtenha um [token do OAuth](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql). 1. Iniciar GraphiQL. 1. No canto superior direito do GraphiQL, clique em **Editar cabeçalhos de HTTP**. 1. No campo **chave**, insira `autorização`. No campo **Valor**, insira `Bearer `, em que `` é o seu token do OAuth gerado. ![cabeçalhos do grafiql](/assets/images/developer/graphiql-headers.png) @@ -44,7 +44,7 @@ Para usar o aplicativo GraphiQL, faça o download e instale-o em https://github. {% note %} -**Observação**: Para obter mais informações sobre o motivo de `POST` ser o método, consulte "[Comunicar-se com GraphQL](/v4/guides/forming-calls#communicating-with-graphql)". +**Observação**: Para obter mais informações sobre o motivo de `POST` ser o método, consulte "[Comunicar-se com GraphQL](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)". {% endnote %} @@ -66,13 +66,13 @@ Todos os tipos em esquema do GraphQL incluem um campo `descrição` compilado na {% note %} -A barra lateral **Documentação** contém o mesmo conteúdo gerado automaticamente a partir do esquema sob "[Referência](/v4/), embora esteja formatada de forma diferente em alguns lugares. +A barra lateral **Documentação** contém o mesmo conteúdo gerado automaticamente a partir do esquema sob "[Referência](/graphql), embora esteja formatada de forma diferente em alguns lugares. {% endnote %} ### Usar o painel de variáveis -Algumas chamadas de exemplo incluem [variáveis](/v4/guides/forming-calls#working-with-variables) escritas como esta: +Algumas chamadas de exemplo incluem [variáveis](/graphql/guides/forming-calls-with-graphql#working-with-variables) escritas como esta: ```graphql query($number_of_repos:Int!){ @@ -90,7 +90,7 @@ variables { } ``` -Este é o formato correto para enviar a chamada por meio de `POST` em cURL (contanto que [escape das novas linhas](/v4/guides/forming-calls#communicating-with-graphql)). +Este é o formato correto para enviar a chamada por meio de `POST` em cURL (contanto que [escape das novas linhas](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)). Se você desejar executar a chamada no Explorador, insira o segmento `da consulta` no painel principal e as variáveis no painel **Variáveis de consulta** abaixo dele. Omita a palavra `variáveis` no Explorador: @@ -106,12 +106,12 @@ Se você desejar executar a chamada no Explorador, insira o segmento `da consult ### Solução de erros -Já que o GraphQL é [introspectivo](/v4/guides/intro-to-graphql#discovering-the-graphql-api), o Explorador suporta: +Já que o GraphQL é [introspectivo](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), o Explorador suporta: * Preenchimento automático inteligente do esquema atual * Pré-visualizações de erros durante a digitação -Se você informar uma consulta que não é bem formada ou não passa um [esquema de validação](/v4/guides/intro-to-graphql#schema), uma janela de pop-up alertará um erro. Se você executar a consulta, o erro será retornado no painel de resposta. +Se você informar uma consulta que não é bem formada ou não passa um [esquema de validação](/graphql/guides/introduction-to-graphql#schema), uma janela de pop-up alertará um erro. Se você executar a consulta, o erro será retornado no painel de resposta. Uma resposta do GraphQL contém várias chaves: um hash de `dados` um array de `erros`. diff --git a/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md b/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md index 8019e1ca82..c544ed4589 100644 --- a/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md +++ b/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md @@ -11,25 +11,25 @@ versions: Aqui estão alguns links rápidos para ajudá-lo colocar em funcionamento a API v4 do GraphQL: -* [Autenticação](/v4/guides/forming-calls/#authenticating-with-graphql) -* [Ponto de extremidade raiz](/v4/guides/forming-calls/#the-graphql-endpoint) -* [Inspeção do esquema](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) -* [Limites de taxa](/v4/guides/resource-limitations/) -* [Fazer a migração de REST](/v4/guides/migrating-from-rest) +* [Autenticação](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) +* [Ponto de extremidade raiz](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) +* [Inspeção do esquema](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) +* [Limites de taxa](/graphql/overview/resource-limitations) +* [Fazer a migração de REST](/graphql/guides/migrating-from-rest-to-graphql) ### Sobre o GraphQL A linguagem de consulta de dados do [GraphQL](https://graphql.github.io/) é: -* **Uma [especificação](https://graphql.github.io/graphql-spec/June2018/).** A especificação determina a validade do esquema [](/v4/guides/intro-to-graphql#schema) no servidor da API. O esquema determina a validade das chamadas dos clientes. +* **Uma [especificação](https://graphql.github.io/graphql-spec/June2018/).** A especificação determina a validade do esquema [](/graphql/guides/introduction-to-graphql#schema) no servidor da API. O esquema determina a validade das chamadas dos clientes. * **[Linguagem inflexível](#about-the-graphql-schema-reference).** O esquema define o sistema de tipos de uma API e todas as relações de objetos. -* **[Introspectivo](/v4/guides/intro-to-graphql#discovering-the-graphql-api).** Um cliente pode consultar o esquema para obter informações sobre o esquema. +* **[Introspectivo](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api).** Um cliente pode consultar o esquema para obter informações sobre o esquema. -* **[Hierárquico](/v4/guides/forming-calls).** A forma de uma chamada do GraphQL espelha a forma dos dados do JSON que ela retorna. Os [Campos aninhados](/v4/guides/migrating-from-rest/#example-nesting) permitem que você consulte e receba apenas os dados que você especificar em uma única transação. +* **[Hierárquico](/graphql/guides/forming-calls-with-graphql).** A forma de uma chamada do GraphQL espelha a forma dos dados do JSON que ela retorna. Os [Campos aninhados](/graphql/guides/migrating-from-rest-to-graphql#example-nesting) permitem que você consulte e receba apenas os dados que você especificar em uma única transação. -* **Uma camada do aplicativo** O GraphQL não é um modelo de armazenamento ou um linguagem de consulta de banco de dados. O _gráfico_ refere-se a estruturas gráficas definidas no esquema, em que [nós](/v4/guides/intro-to-graphql#node) definem os objetos e [bordas](/v4/guides/intro-to-graphql#edge) definem as relações entre os objetos. A API percorre e retorna dados do aplicativo com base nas definições do esquema, independentemente de como os dados são armazenados. +* **Uma camada do aplicativo** O GraphQL não é um modelo de armazenamento ou um linguagem de consulta de banco de dados. O _gráfico_ refere-se a estruturas gráficas definidas no esquema, em que [nós](/graphql/guides/introduction-to-graphql#node) definem os objetos e [bordas](/graphql/guides/introduction-to-graphql#edge) definem as relações entre os objetos. A API percorre e retorna dados do aplicativo com base nas definições do esquema, independentemente de como os dados são armazenados. ### Por que o GitHub está usando GraphQL @@ -39,15 +39,15 @@ Para obter mais informações sobre por que o GitHub fez a migração para o Gra ### Sobre a referência do esquema do GraphQL -A documentação na barra lateral é gerada a partir do [esquema](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) de do GraphQL de {% data variables.product.prodname_dotcom %}. Todas as chamadas são validadas e executadas contra o esquema. Use estes documentos para descobrir quais dados você pode chamar: +A documentação na barra lateral é gerada a partir do [esquema](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) de do GraphQL de {% data variables.product.prodname_dotcom %}. Todas as chamadas são validadas e executadas contra o esquema. Use estes documentos para descobrir quais dados você pode chamar: -* Operações permitidas: [consultas](/v4/query) e [mutações](/v4/mutation). +* Operações permitidas: [consultas](/graphql/reference/queries) e [mutações](/graphql/reference/mutations). -* Esquema dos tipos: [escalares](/v4/scalar), [objetos](/v4/object), [enumeradores](/v4/enum), [interfaces](/v4/interface), [união](/v4/union) e [objetos de entrada](/v4/input_object). +* Esquema dos tipos: [escalares](/graphql/reference/scalars), [objetos](/graphql/reference/objects), [enumeradores](/graphql/reference/enums), [interfaces](/graphql/reference/interfaces), [união](/graphql/reference/unions) e [objetos de entrada](/graphql/reference/input-objects). -Você pode acessar esse mesmo conteúdo através da [Barra lateral de documentos do Explorador](/v4/guides/using-the-explorer#accessing-the-sidebar-docs). Observe que você pode precisar confiar tanto na documentação quanto na validação do esquema para chamar com sucesso a API do GraphQL. +Você pode acessar esse mesmo conteúdo através da [Barra lateral de documentos do Explorador](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Observe que você pode precisar confiar tanto na documentação quanto na validação do esquema para chamar com sucesso a API do GraphQL. -Para obter outras informações, como detalhes de autenticação e limite de taxa, confira os [guias](/v4/guides). +Para obter outras informações, como detalhes de autenticação e limite de taxa, confira os [guias](/graphql/guides). ### Solicitar suporte diff --git a/translations/pt-BR/content/graphql/overview/breaking-changes.md b/translations/pt-BR/content/graphql/overview/breaking-changes.md index 9ba1e16c3c..037f1343c7 100644 --- a/translations/pt-BR/content/graphql/overview/breaking-changes.md +++ b/translations/pt-BR/content/graphql/overview/breaking-changes.md @@ -16,7 +16,7 @@ Alterações significativas são quaisquer mudanças que possam exigir ação do - **Significativas:** As alterações que irão modificar as consultas existentes na API do GraphQL. Por exemplo, a eliminação de um campo seria uma mudança decisiva. - **Perigoso:** Alterações que não modificam as consultas existentes, mas podem afetar o comportamento de tempo de execução dos clientes. Adicionar um valor de enumerador é um exemplo de uma alteração perigosa. -Nós nos esforçamos para fornecer APIs estáveis para os nossos integrantes. Quando um novo recurso ainda está evoluindo, o lançamos atrás de uma [pré-visualização de esquema](/v4/previews/). +Nós nos esforçamos para fornecer APIs estáveis para os nossos integrantes. Quando um novo recurso ainda está evoluindo, o lançamos atrás de uma [pré-visualização de esquema](/graphql/overview/schema-previews). Vamos anunciar as próximas mudanças significativas em andamento pelo menos três meses antes de fazer alterações no esquema do GraphQL para dar tempo aos integradores de fazer os ajustes necessários. As alterações entram em vigor no primeiro dia do trimestre (1 de janeiro, 1 de abril, 1 de julho ou 1 de outubro). Por exemplo, se anunciarmos uma mudança no dia 15 de Janeiro, ela entrará em vigor no dia 1 de julho. diff --git a/translations/pt-BR/content/graphql/overview/changelog.md b/translations/pt-BR/content/graphql/overview/changelog.md index 3eceb4af3b..eebdb58b30 100644 --- a/translations/pt-BR/content/graphql/overview/changelog.md +++ b/translations/pt-BR/content/graphql/overview/changelog.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -As alterações significativas incluem alterações que modificarão as consultas existentes ou podem afetar o comportamento do tempo de execução dos clientes. Para obter uma lista de alterações significativas e quando ocorrerão, consulte o nosso [registro de alterações significativas](/v4/breaking_changes). +As alterações significativas incluem alterações que modificarão as consultas existentes ou podem afetar o comportamento do tempo de execução dos clientes. Para obter uma lista de alterações significativas e quando ocorrerão, consulte o nosso [registro de alterações significativas](/graphql/overview/breaking-changes). {% for entry in graphql.changelog %} ### Alterações de esquema para {{ entry.date }} diff --git a/translations/pt-BR/content/graphql/overview/public-schema.md b/translations/pt-BR/content/graphql/overview/public-schema.md index 32abf5eb52..d27985595b 100644 --- a/translations/pt-BR/content/graphql/overview/public-schema.md +++ b/translations/pt-BR/content/graphql/overview/public-schema.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -Você pode [realizar a introspecção](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) com base na API do GraphQL diretamente. +Você pode [realizar a introspecção](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) com base na API do GraphQL diretamente. Como alternativa, você pode fazer o download da versão mais recente do esquema público aqui: diff --git a/translations/pt-BR/content/graphql/overview/resource-limitations.md b/translations/pt-BR/content/graphql/overview/resource-limitations.md index 5f5dc3939c..8e0614d772 100644 --- a/translations/pt-BR/content/graphql/overview/resource-limitations.md +++ b/translations/pt-BR/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## Limite de nó -Para passar a validação do [esquema](/v4/guides/intro-to-graphql#schema), todas as [chamadas ](/v4/guides/forming-calls) da API v4 do GraphQL devem atender a esses padrões: +To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: -* Os clientes devem fornecer um `primeiro` ou `último` argumento [conexão](/v4/guides/intro-to-graphql#connection). +* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). * Os valores de `primeiro` e `último` devem ser entre 1 e 100. -* As chamadas individuais não podem solicitar mais de 500.000 [nós](/v4/guides/intro-to-graphql#node)no total. +* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). #### Calcular nós em uma chamada @@ -121,7 +121,7 @@ Estes dois exemplos mostram como calcular os nós totais em uma chamada. O [limite de taxas](/rest/overview/resources-in-the-rest-api#rate-limiting) do GraphQL API v4 é diferente dos limites de taxa do REST API v3. -Por que os limites de taxa de API são diferentes? Com o [GraphQL](/v4/), uma chamada do GraphQL pode substituir [várias chamadas de REST](/v4/guides/migrating-from-rest/). Uma chamada única e complexa do GraphQL poderia ser o equivalente a milhares de solicitações de REST. Embora uma única chamada GraphQL fique bem abaixo do limite de taxa de API REST, a consulta pode ser muito cara para os servidores do GitHub calcularem. +Por que os limites de taxa de API são diferentes? With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). Uma chamada única e complexa do GraphQL poderia ser o equivalente a milhares de solicitações de REST. Embora uma única chamada GraphQL fique bem abaixo do limite de taxa de API REST, a consulta pode ser muito cara para os servidores do GitHub calcularem. Para representar com precisão o custo de servidor de uma consulta, a API v4 do GraphQL calcula a **pontuação de um limite de taxa** de uma chamada com base em uma escala normalizada de pontos. Os fatores de pontuação de uma consulta no primeiro e último argumentos em uma conexão principal e suas conexões auxiliares. diff --git a/translations/pt-BR/content/graphql/overview/schema-previews.md b/translations/pt-BR/content/graphql/overview/schema-previews.md index 4e0234697a..3f03789c03 100644 --- a/translations/pt-BR/content/graphql/overview/schema-previews.md +++ b/translations/pt-BR/content/graphql/overview/schema-previews.md @@ -13,7 +13,7 @@ versions: Durante o período de pré-visualização, poderemos alterar alguns recursos com base no feedback do desenvolvedor. Se fizermos alterações, iremos anunciá-las no [blogue do desenvolvedor](https://developer.github.com/changes/) sem aviso prévio. -Para acessar uma pré-visualização de esquema, você deverá fornecer um [tipo de mídia personalizado](/v3/media) no cabeçalho `Aceitar` para as suas solicitações. A documentação dos recursos para cada pré-visualização especifica qual tipo de mídia personalizado deve ser fornecido. +Para acessar uma pré-visualização de esquema, você deverá fornecer um [tipo de mídia personalizado](/rest/overview/media-types) no cabeçalho `Aceitar` para as suas solicitações. A documentação dos recursos para cada pré-visualização especifica qual tipo de mídia personalizado deve ser fornecido. {% note %} diff --git a/translations/pt-BR/content/graphql/reference/enums.md b/translations/pt-BR/content/graphql/reference/enums.md index 138c9e9135..0019aefc70 100644 --- a/translations/pt-BR/content/graphql/reference/enums.md +++ b/translations/pt-BR/content/graphql/reference/enums.md @@ -12,9 +12,9 @@ versions: [Enumeradores](https://graphql.github.io/graphql-spec/June2018/#sec-Enums) representam possíveis conjuntos de valores para um campo. -Por exemplo, o objeto [`problema`](/v4/object/issue) tem um campo denominado `estado`. O estado é um enumerador (especificamente, do tipo [`IssueState`](/v4/enum/issuestate/)), porque pode estar `ABERTO` ou `FECHADO`. +Por exemplo, o objeto [`problema`](/graphql/reference/objects#issue) tem um campo denominado `estado`. O estado é um enumerador (especificamente, do tipo [`IssueState`](/graphql/reference/enums#issuestate)), porque pode estar `ABERTO` ou `FECHADO`. -Para obter mais informações, consulte "[Introdução ao GraphQL](/v4/guides/intro-to-graphql)". +Para obter mais informações, consulte "[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql)". {% for item in graphql.schemaForCurrentVersion.enums %} {% include graphql-enum %} diff --git a/translations/pt-BR/content/graphql/reference/input-objects.md b/translations/pt-BR/content/graphql/reference/input-objects.md index 3d94a64f14..4845c3de1b 100644 --- a/translations/pt-BR/content/graphql/reference/input-objects.md +++ b/translations/pt-BR/content/graphql/reference/input-objects.md @@ -12,9 +12,9 @@ versions: [Objetos de entrada](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects) podem ser descritos como "objetos estruturáveis", pois incluem um conjunto de campos de entrada que definem o objeto. -Por exemplo, [`CommitAuthor`](/v4/input_object/commitauthor/) toma um campo denominado `e-mails`. Fornecer um valor para `e-mails` transforma `CommitAuthor` em uma lista de objetos de `usuário` que contém esse endereço de e-mail. Observe que [objetos](/v4/object) **pode ter** objetos de entrada, enquanto [mutações](/v4/mutation) **exigem** objetos de entrada. +Por exemplo, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) toma um campo denominado `e-mails`. Fornecer um valor para `e-mails` transforma `CommitAuthor` em uma lista de objetos de `usuário` que contém esse endereço de e-mail. Observe que [objetos](/graphql/reference/objects) **pode ter** objetos de entrada, enquanto [mutações](/graphql/reference/mutations) **exigem** objetos de entrada. -Para obter mais informações, consulte "[Sobre mutações](/v4/guides/forming-calls#about-mutations)". +Para obter mais informações, consulte "[Sobre mutações](/graphql/guides/forming-calls-with-graphql#about-mutations)". {% for item in graphql.schemaForCurrentVersion.inputObjects %} {% include graphql-input-object %} diff --git a/translations/pt-BR/content/graphql/reference/interfaces.md b/translations/pt-BR/content/graphql/reference/interfaces.md index 0023348af4..339990ae3c 100644 --- a/translations/pt-BR/content/graphql/reference/interfaces.md +++ b/translations/pt-BR/content/graphql/reference/interfaces.md @@ -12,9 +12,9 @@ versions: As [Interfaces](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces) servem como objetos principais dos quais outros objetos receberão sua herança. -Por exemplo, [`Bloqueável`](/v4/interface/lockable/) é uma interface porque os objetos [`problema`](/v4/object/issue/) e [`PullRequest`](/v4/object/pullrequest/) objetos podem ser bloqueados. Uma interface possui sua própria lista de campos nomeados que são compartilhados mediante os objetos de implementação. +Por exemplo, [`Bloqueável`](/graphql/reference/interfaces#lockable) é uma interface porque os objetos [`problema`](/graphql/reference/objects#issue) e [`PullRequest`](/graphql/reference/objects#pullrequest) objetos podem ser bloqueados. Uma interface possui sua própria lista de campos nomeados que são compartilhados mediante os objetos de implementação. -Para obter mais informações, consulte "[Implementação](/v4/guides/intro-to-graphql#implementation)". +Para obter mais informações, consulte "[Implementação](/graphql/guides/introduction-to-graphql#implementation)". {% for item in graphql.schemaForCurrentVersion.interfaces %} {% include graphql-interface %} diff --git a/translations/pt-BR/content/graphql/reference/mutations.md b/translations/pt-BR/content/graphql/reference/mutations.md index 3fc58a5a46..8365f3caca 100644 --- a/translations/pt-BR/content/graphql/reference/mutations.md +++ b/translations/pt-BR/content/graphql/reference/mutations.md @@ -12,7 +12,7 @@ versions: Cada esquema de GraphQL tem um tipo de raiz para consultas e mutações. O [tipo de mutação](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) define operações do GraphQL que alteram dados no servidor. É análogo a executar verbos HTTP como `POST`, `PATCH` e `DELETE`. -Para obter mais informações, consulte "[Sobre mutações](/v4/guides/forming-calls#about-mutations)". +Para obter mais informações, consulte "[Sobre mutações](/graphql/guides/forming-calls-with-graphql#about-mutations)". {% for item in graphql.schemaForCurrentVersion.mutations %} {% include graphql-mutation %} diff --git a/translations/pt-BR/content/graphql/reference/objects.md b/translations/pt-BR/content/graphql/reference/objects.md index f156dfed45..f228814c6d 100644 --- a/translations/pt-BR/content/graphql/reference/objects.md +++ b/translations/pt-BR/content/graphql/reference/objects.md @@ -14,7 +14,7 @@ Os [Objetos](https://graphql.github.io/graphql-spec/June2018/#sec-Objects) no Gr Por exemplo, o objeto [`Repositório`](/graphql/reference/objects#repository) tem um campo denominado `nome`, que é uma `String`. -Para obter mais informações, consulte "[Introdução ao GraphQL](/v4/guides/intro-to-graphql)". +Para obter mais informações, consulte "[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql)". diff --git a/translations/pt-BR/content/graphql/reference/queries.md b/translations/pt-BR/content/graphql/reference/queries.md index 8ecf2ef0fe..20d32d9d2b 100644 --- a/translations/pt-BR/content/graphql/reference/queries.md +++ b/translations/pt-BR/content/graphql/reference/queries.md @@ -13,11 +13,11 @@ versions: Cada esquema de GraphQL tem um tipo de raiz para consultas e mutações. O [tipo de consulta](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) define operações do GraphQL que recuperam dados do servidor. -Para obter mais informações, consulte "[Sobre consultas](/v4/guides/forming-calls#about-queries)". +Para obter mais informações, consulte "[Sobre consultas](/graphql/guides/forming-calls-with-graphql#about-queries)". {% note %} -**Note:** For [user-to-server](/developers/apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) {% data variables.product.prodname_github_app %} requests, you should use separate queries for issues and pull requests. For example, use the `is:issue` or `is:pull-request` filters and their equivalents. Using the `search` connection to return a combination of issues and pull requests in a single query will result in an empty set of nodes. +**Observação:** Para solicitações de {% data variables.product.prodname_github_app %} do tipo [usuário para servidor](/developers/apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) você deve usar consultas separadas para problemas e pull requests. Por exemplo, use os filtros `is:issue` ou `is:pull-request` e seus equivalentes. Usar a conexão de `pesquisa` para retornar uma combinação de problemas e pull requests em uma única consulta resultará em um conjunto de nós vazio. {% endnote %} diff --git a/translations/pt-BR/content/graphql/reference/scalars.md b/translations/pt-BR/content/graphql/reference/scalars.md index 2b42ac791d..0f23bbe7b4 100644 --- a/translations/pt-BR/content/graphql/reference/scalars.md +++ b/translations/pt-BR/content/graphql/reference/scalars.md @@ -14,7 +14,7 @@ versions: Ao chamar a API do GraphQL, você deve especificar subcampos aninhados até retornar apenas escalares. -Para obter mais informações, consulte "[Introdução ao GraphQL](/v4/guides/intro-to-graphql#field)". +Para obter mais informações, consulte "[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql#field)". {% for item in graphql.schemaForCurrentVersion.scalars %} {% include graphql-scalar %} diff --git a/translations/pt-BR/content/graphql/reference/unions.md b/translations/pt-BR/content/graphql/reference/unions.md index d4511373de..9807979baa 100644 --- a/translations/pt-BR/content/graphql/reference/unions.md +++ b/translations/pt-BR/content/graphql/reference/unions.md @@ -12,9 +12,9 @@ versions: Uma [união](https://graphql.github.io/graphql-spec/June2018/#sec-Unions) é um tipo de objeto que representa muitos objetos. -Por exemplo, um campo marcado como um [`ProjectCardItem`](/v4/union/projectcarditem/) pode ser um [`problema`](/v4/object/issue/) ou um [`PullRequest`](/v4/object/pullrequest/), pois cada um desses objetos pode estar dentro de um cartão de projeto. Usar uma união em vez de um objeto dá flexibilidade. +Por exemplo, um campo marcado como um [`ProjectCardItem`](/graphql/reference/unions#projectcarditem) pode ser um [`problema`](/graphql/reference/objects#issue) ou um [`PullRequest`](/graphql/reference/objects#pullrequest), pois cada um desses objetos pode estar dentro de um cartão de projeto. Usar uma união em vez de um objeto dá flexibilidade. -Para obter mais informações, consulte "[Introdução ao GraphQL](/v4/guides/intro-to-graphql)". +Para obter mais informações, consulte "[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql)". {% for item in graphql.schemaForCurrentVersion.unions %} {% include graphql-union %} diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index e842963cff..2bc4ac1330 100644 --- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: Habilitar um link entre o GitHub Insights e o GitHub Enterprise -intro: 'Você pode habilitar um link que permitirá aos usuários navegar entre {% data variables.product.prodname_ghe_server %} e {{ site.data.variables.product.prodname_insights }}.' +intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' permissions: 'Os administradores do site de {% data variables.product.prodname_ghe_server %} podem habilitar o link entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_insights %}.' redirect_from: diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md index 5e7d5ec3b4..8b2582a913 100644 --- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md +++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md @@ -90,7 +90,7 @@ Você pode criar e gerenciar equipes personalizadas no {% data variables.product {% data reusables.github-insights.settings-tab %} {% data reusables.github-insights.teams-tab %} {% data reusables.github-insights.edit-team %} -3. Em "Contribuidores", use o menu suspenso e selecione um contribuidor. ![Contributors drop-down](/assets/images/help/insights/contributors-drop-down.png) +3. Em "Contribuidores", use o menu suspenso e selecione um contribuidor. ![Menu suspenso de contribuidores](/assets/images/help/insights/contributors-drop-down.png) 4. Clique em **Cpncluído**. #### Remover um contribuidor de uma equipe personalizada diff --git a/translations/pt-BR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md index d6859ecbcc..226a607c70 100644 --- a/translations/pt-BR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md +++ b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md @@ -8,18 +8,26 @@ versions: {% note %} -**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Atualmente, {% data variables.product.prodname_github_container_registry %} é compatível apenas com formatos de imagem do Docker. Durante o beta, o armazenamento e a largura de banda são grátis. +**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. Para usar {% data variables.product.prodname_github_container_registry %}, você deve habilitar o recurso para sua conta. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". {% endnote %} - {% data reusables.package_registry.container-registry-feature-highlights %} Para compartilhar o contexto sobre o uso do seu pacote, você pode vincular um repositório à sua imagem de contêiner no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Conectar um repositório a uma imagem de contêiner](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)". ### Formatos compatíveis -O {% data variables.product.prodname_container_registry %} atualmente é compatível apenas com as imagens do Docker. +O {% data variables.product.prodname_container_registry %} é atualmente compatível com os seguintes formatos de imagem do contêiner: + +* [Docker Image Manifest V2, Modelo 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Especificações de Open Container Initiative (OCI)](https://github.com/opencontainers/image-spec) + +#### Lista de manifestos/Índices de imagens + +{% data variables.product.prodname_github_container_registry %} também é compatível com +formatos das [ Listas de Manifesto do Docker](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[Índice de Imagens de OCI](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) definidos nas especificações do Docker V2, Esquema 2 e na imagem de OCI.

+ ### Visibilidade e permissões de acesso para imagens de contêiner @@ -36,12 +44,17 @@ Para imagens de contêiner publicadas e pertencentes a uma conta de usuário, vo | Gravação | Pode fazer upload e download deste pacote.
Pode ler gravar metadados do pacote. | | Administrador | Pode fazer upload, download, excluir e gerenciar este pacote.
Pode ler gravar metadados do pacote.
Pode conceder permissões de pacote. | + Para obter mais informações, consulte "[Configurar controle de acesso e visibilidade para imagens de contêiner](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)". + + ### Sobre a cobrança do {% data variables.product.prodname_github_container_registry %} {% data reusables.package_registry.billing-for-container-registry %} + + ### Entrar em contato com o suporte Se você tiver feedback ou solicitações de recursos para {% data variables.product.prodname_github_container_registry %}, use o [formulário de feedback](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages). diff --git a/translations/pt-BR/content/packages/getting-started-with-github-container-registry/index.md b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/index.md index 590004babf..82c9d80a8a 100644 --- a/translations/pt-BR/content/packages/getting-started-with-github-container-registry/index.md +++ b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/index.md @@ -8,8 +8,8 @@ versions: {% data reusables.package_registry.container-registry-beta %} {% link_in_list /about-github-container-registry %} +{% link_in_list /enabling-improved-container-support %} {% link_in_list /core-concepts-for-github-container-registry %} {% link_in_list /migrating-to-github-container-registry-for-docker-images %} -{% link_in_list /enabling-github-container-registry-for-your-organization %} Para obter mais informações sobre configuração, exclusão, push ou extração de imagens contêineres, consulte "[Gerenciar imagens de contêiner com {% data variables.product.prodname_github_container_registry %}](/packages/managing-container-images-with-github-container-registry)". diff --git a/translations/pt-BR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md index bf45b9e0e2..d0db4cbcb8 100644 --- a/translations/pt-BR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md +++ b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md @@ -31,6 +31,8 @@ O domínio para o {% data variables.product.prodname_container_registry %} é `g ### Efetuar a autenticação com o registro do contêiner +{% data reusables.package_registry.feature-preview-for-container-registry %} + Você deverá efetuar a autenticação no {% data variables.product.prodname_container_registry %} com a URL de base `ghcr.io`. Recomendamos criar um novo token de acesso para usar o {% data variables.product.prodname_container_registry %}. {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} @@ -72,13 +74,15 @@ Para mover imagens do Docker que você hospeda no registro do Docker do {% data ### Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %} +{% data reusables.package_registry.feature-preview-for-container-registry %} + Se tiver um fluxo de trabalho de {% data variables.product.prodname_actions %} que usa uma imagem do Docker do registro Docker do {% data variables.product.prodname_registry %}, você deverá atualizar seu fluxo de trabalho para {% data variables.product.prodname_container_registry %} para permitir acesso anônimo para imagens públicas de contêiner, permissões de acesso refinado e melhor compatibilidade de armazenamento e largura de banda para contêineres. 1. Migre as suas imagens do Docker para o novo {% data variables.product.prodname_container_registry %} em `ghcr.io`. Por exemplo, consulte "[Migrar uma imagem do Docker usando a CLI do Docker](#migrating-a-docker-image-using-the-docker-cli)". 2. No seu arquivo de fluxo de trabalho do {% data variables.product.prodname_actions %}, atualize a URL do pacote de `https://docker.pkg.github.com` para `ghcr.io`. -3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. {% data variables.product.prodname_github_container_registry %} não é compatível com o uso do `GITHUB_TOKEN` para o seu PAT. Portanto, você deve usar uma variável personalizada diferente, como `CR_PAT`. Para obter mais informações, consulte "[Criar e armazenar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". +3. Adicione seu novo token de acesso de autenticação pessoal (PAT) de {% data variables.product.prodname_container_registry %} como um segredo do GitHub Action. {% data variables.product.prodname_github_container_registry %} não é compatível com o uso do `GITHUB_TOKEN` para o seu PAT. Portanto, você deve usar uma variável personalizada diferente, como `CR_PAT`. Para obter mais informações, consulte "[Criar e armazenar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". 4. No seu arquivo de fluxo de trabalho de {% data variables.product.prodname_actions %} atualize a autenticação do PAT substituindo o seu PAT do registro do Docker ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) por uma nova variável para o seu PAT de {% data variables.product.prodname_container_registry %}, como, por exemplo, {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}. diff --git a/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md b/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md index 51e488f358..5a888af734 100644 --- a/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md +++ b/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md @@ -24,7 +24,7 @@ Se você tiver permissões de administrador para uma imagem de contêiner perten Se o seu pacote pertencer a uma organização e for privado, você só poderá conceder acesso a outros integrantes da organização ou equipes. -Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes antes que você possa definir a visibilidade como pública. Para obter mais informações, consulte "[Habilitar o GitHub Container Registry para sua organização](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)". +Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes antes que você possa definir a visibilidade como pública. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". {% data reusables.package_registry.package-settings-from-org-level %} 1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. Você também pode inserir um nome de equipe da organização para dar acesso a todos os integrantes da equipe. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png) @@ -54,7 +54,7 @@ Ao publicar um pacote, a visibilidade-padrão é privada e só você poderá ver Um pacote público pode ser acessado anonimamente sem autenticação. Uma vez que você torna público o seu pacote, mas você não poderá tornar o seu pacote privado novamente. -Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes públicos antes que você possa definir a visibilidade como pública. Para obter mais informações, consulte "[Habilitar o GitHub Container Registry para sua organização](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)". +Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes públicos antes que você possa definir a visibilidade como pública. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". {% data reusables.package_registry.package-settings-from-org-level %} 5. Em "Zona de Perigo", escolha uma configuração de visibilidade: diff --git a/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md b/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md index 219b181624..ac27aee19a 100644 --- a/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md +++ b/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md @@ -16,12 +16,6 @@ Para excluir uma imagem do contêiner, você deve ter permissões de administrad Ao excluir pacotes públicos, esteja ciente de que você pode quebrar projetos que dependem do seu pacote. - - -### Versões e nomes de pacotes reservados - -{% data reusables.package_registry.package-immutability %} - ### Excluir uma versão de uma imagem de contêiner de usuário em {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-user-level %} diff --git a/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md index 50e25039f0..07cb027cba 100644 --- a/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ b/translations/pt-BR/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md @@ -8,7 +8,7 @@ versions: {% data reusables.package_registry.container-registry-beta %} -Para fazer push e pull das imagens de contêiner pertencentes a uma organização, um administrador da organização deve habilitar o {% data variables.product.prodname_github_container_registry %} para a organização. Para obter mais informações, consulte "[Habilitar o GitHub Container Registry para sua organização](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)". +Para fazer push e pull das imagens de contêiner pertencentes a uma organização, um administrador da organização deve habilitar o {% data variables.product.prodname_github_container_registry %} para a organização. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". ### Autenticar-se no {% data variables.product.prodname_github_container_registry %} diff --git a/translations/pt-BR/content/packages/publishing-and-managing-packages/about-github-packages.md b/translations/pt-BR/content/packages/publishing-and-managing-packages/about-github-packages.md index d02bf8560b..b1ef38dc0a 100644 --- a/translations/pt-BR/content/packages/publishing-and-managing-packages/about-github-packages.md +++ b/translations/pt-BR/content/packages/publishing-and-managing-packages/about-github-packages.md @@ -26,6 +26,8 @@ When you create a {% data variables.product.prodname_actions %} workflow, you ca {% data reusables.package_registry.container-registry-beta %} +![Diagrama que mostra Node, RubyGems, Apache Maven, Gradle, Nuget e o registro do contêiner com suas urls de hospedagem](/assets/images/help/package-registry/packages-overview-diagram.png) + {% endif %} #### Visualizar pacotes @@ -34,17 +36,17 @@ You can configure webhooks to subscribe to package-related events, such as when #### Sobre permissões e visibilidade de pacotes {% if currentVersion == "free-pro-team@latest" %} -| | Registros de pacotes | {% data variables.product.prodname_github_container_registry %} -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Locais de hospedagem | Você pode hospedar vários pacotes em um só repositório. | Você pode hospedar várias imagens de contêiner em uma organização ou conta de usuário. | -| Permissões | {{ site.data.reusables.package_registry.public-or-private-packages }} You can use {{ site.data.variables.product.prodname_dotcom }} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | Para cada imagem de container, você pode escolher o nível de acesso que os outros têm. As permissões para acesso a imagens do contêiner são separadas da sua organização e das permissões do repositório. | +| | Registros de pacotes | {% data variables.product.prodname_github_container_registry %} +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Locais de hospedagem | Você pode hospedar vários pacotes em um só repositório. | Você pode hospedar várias imagens de contêiner em uma organização ou conta de usuário. | +| Permissões | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | Para cada imagem de container, você pode escolher o nível de acesso que os outros têm. As permissões para acesso a imagens do contêiner são separadas da sua organização e das permissões do repositório. | Visibilidade | {% data reusables.package_registry.public-or-private-packages %} | Você pode definir a visibilidade de cada uma de suas imagens de contêiner. Uma imagem privada de contêiner só é visível para pessoas e equipes às quais é fornecido acesso na sua organização. Qualquer pessoa pode ver uma imagem pública de contêiner. | acesso anônimo | N/A | Você pode acessar imagens de contêineres públicas anonimamente. {% else %} -| | Registros de pacotes | -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Locais de hospedagem | Você pode hospedar vários pacotes em um só repositório. | -| Permissões | {{ site.data.reusables.package_registry.public-or-private-packages }} You can use {{ site.data.variables.product.prodname_dotcom }} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | +| | Registros de pacotes | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Locais de hospedagem | Você pode hospedar vários pacotes em um só repositório. | +| Permissões | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | | Visibilidade | {% data reusables.package_registry.public-or-private-packages %} {% endif %} @@ -169,7 +171,7 @@ Por exemplo: | `read:packages` | Faça o download e instale pacotes do {% data variables.product.prodname_registry %} | leitura | | `write:packages` | Faça o upload e publique os pacotes em {% data variables.product.prodname_registry %} | gravação | | `delete:packages` | Excluir versões especificadas de pacotes privados de {% data variables.product.prodname_registry %} | administrador | -| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write, or admin | +| `repo` | Faça o upload e exclua os pacotes (junto com `write:packages` ou `delete:packages`) | gravação ou admin | Ao criar um fluxo de trabalho de {% data variables.product.prodname_actions %}, você pode usar o `GITHUB_TOKEN` para publicar e instalar pacotes no {% data variables.product.prodname_registry %} sem precisar armazenar e gerenciar um token de acesso pessoal. @@ -180,7 +182,7 @@ Para obter mais informações, consulte: ### Gerenciar pacotes -Você pode excluir uma versão de um pacote privado em {% data variables.product.product_name %} ou usar a API do GraphQL. Ao usar a API do GraphQL para consultar e excluir pacotes privados, você deve usar o mesmo token que você usa para efetuar a autenticação no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package)" e "[Formando chamadas com GraphQL](/v4/guides/forming-calls/)". +Você pode excluir uma versão de um pacote privado em {% data variables.product.product_name %} ou usar a API do GraphQL. Ao usar a API do GraphQL para consultar e excluir pacotes privados, você deve usar o mesmo token que você usa para efetuar a autenticação no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package)" e "[Formando chamadas com GraphQL](/graphql/guides/forming-calls-with-graphql)". Você pode configurar webhooks para assinar eventos relacionados aos pacotes, como quando um pacote é publicado ou atualizado. Para obter mais informações, consulte o evento de webhook de "[`pacote`](/webhooks/event-payloads/#package)". diff --git a/translations/pt-BR/content/packages/publishing-and-managing-packages/deleting-a-package.md b/translations/pt-BR/content/packages/publishing-and-managing-packages/deleting-a-package.md index c1ae0b5aa2..6e25c7cfc7 100644 --- a/translations/pt-BR/content/packages/publishing-and-managing-packages/deleting-a-package.md +++ b/translations/pt-BR/content/packages/publishing-and-managing-packages/deleting-a-package.md @@ -31,14 +31,10 @@ Em circunstâncias especiais, como por razões legais ou para estar de acordo co {% else %} -At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages. +No momento, {% data variables.product.prodname_registry %} em {% data variables.product.product_location %} não é compatível com a exclusão de pacotes públicos. {% endif %} -### Versões e nomes de pacotes reservados - -{% data reusables.package_registry.package-immutability %} - ### Excluir uma versão de um pacote privado no {% data variables.product.product_name %} Para excluir uma versão privada, você deve ter permissões de administrador no repositório. diff --git a/translations/pt-BR/content/packages/publishing-and-managing-packages/publishing-a-package.md b/translations/pt-BR/content/packages/publishing-and-managing-packages/publishing-a-package.md index 70caf35ea7..afea579d9b 100644 --- a/translations/pt-BR/content/packages/publishing-and-managing-packages/publishing-a-package.md +++ b/translations/pt-BR/content/packages/publishing-and-managing-packages/publishing-a-package.md @@ -18,11 +18,9 @@ Você pode ajudar as pessoas a entender e usar seu pacote fornecendo uma descri {% data reusables.package_registry.public-or-private-packages %} Um repositório pode conter mais de um pacote. Para evitar confusão, certifique-se de que o LEIAME e a descrição fornecem informações claras sobre cada pacote. -{% data reusables.package_registry.package-immutability %} - {% if currentVersion == "free-pro-team@latest" %} Se uma nova versão de um pacote corrigir uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. -{% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." {% endif %} ### Publicar um pacote diff --git a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md index 0d8c2df1cc..e4847bd86b 100644 --- a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md @@ -1,6 +1,6 @@ --- -title: Configuring Apache Maven for use with GitHub Packages -intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' +title: Configurar o Apache Maven para uso com o GitHub Packages +intro: 'Você pode configurar o Apache Maven para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto Java.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-apache-maven-for-use-with-github-package-registry @@ -13,28 +13,28 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.admins-can-configure-package-types %} +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. -### Authenticating to {% data variables.product.prodname_registry %} +### Autenticar-se no {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -#### Authenticating with a personal access token +#### Efetuando a autenticação com um token de acesso pessoal {% data reusables.package_registry.required-scopes %} -You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist. +Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o Apache Maven editando seu arquivo *~/.m2/settings.xml* para incluir seu token de acesso pessoal. Criar um novo arquivo *~/.m2/settings.xml*, caso não exista um. -In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token. +Na etiqueta `servidores`, adicione uma etiqueta `servidor` secundário com um `Id`, substituindo *USERNAME* pelo o seu nome de usuário {% data variables.product.prodname_dotcom %} e *Token* pelo seu token de acesso pessoal. -In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}*REPOSITORY* with the name of the repository you'd like to publish a package to or install a package from, and *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. +Na etiqueta `repositórios`, configure um repositório mapeando o `id` do repositório com o `id` que você adicionou na etiqueta `servidor` que contém as suas credenciais. Substituir {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* pelo nome do host de sua instância {% data variables.product.prodname_ghe_server %} {% endif %}*REPOSITÓRIO* com o nome do repositório no qual você gostaria de publicar um pacote ou instalar um pacote, e *OWNER* com o nome do usuário ou conta de organização proprietária do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. -If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag. +Se desejar interagir com vários repositórios, você poderá adicionar cada repositório para separar os `repositório` secundários na etiqueta `repositórios`, mapeando o `ID` de cada um com as credenciais na etiqueta `servidores`. {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} {% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation enabled: +Se sua instância tem o isolamento de subdomínio habilitado: {% endif %} ``` @@ -77,7 +77,7 @@ If your instance has subdomain isolation enabled: ``` {% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation disabled: +Se sua instância tem o isolamento de subdomínio desabilitado: ``` ` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository. +Caso queira publicar vários pacotes no mesmo repositório, você poderá incluir a URL do repositório no `` elemento do arquivo *pom.xml*. O {% data variables.product.prodname_dotcom %} fará a correspondência do repositório com base nesse campo. Como o nome do repositório também faz parte do elemento `distributionManagement`, não há etapas adicionais para publicar vários pacotes no mesmo repositório. -For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +Para obter mais informações sobre como criar um pacote, consulte a [documentação maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). -1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. +1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing `OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. + +{% if enterpriseServerVersions contains currentVersion %}*NOME DE HOST* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %} {% endif %}`PROPRIETÁRIO` pelo nome do usuário ou conta da organização proprietária do repositório e `REPOSITÓRIO` pelo nome do repositório que contém o seu projeto. {% if enterpriseServerVersions contains currentVersion %} - If your instance has subdomain isolation enabled: + Se sua instância tem o isolamento de subdomínio habilitado: {% endif %} ``` @@ -145,7 +147,7 @@ For more information on creating a package, see the [maven.apache.org documentat ``` {% if enterpriseServerVersions contains currentVersion %} - If your instance has subdomain isolation disabled: + Se sua instância tem o isolamento de subdomínio desabilitado: ``` @@ -156,7 +158,7 @@ For more information on creating a package, see the [maven.apache.org documentat ``` {% endif %} -2. Publish the package. +2. Publique o pacote. ```shell $ mvn deploy @@ -164,12 +166,12 @@ For more information on creating a package, see the [maven.apache.org documentat {% data reusables.package_registry.viewing-packages %} -### Installing a package +### Instalar um pacote -To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation. +Para instalar um pacote de Apache Maven a partir do {% data variables.product.prodname_registry %}, edite o arquivo *pom.xml* para incluir o pacote como uma dependência. Se você desejar instalar pacotes de mais de um repositório, adicione uma etiqueta de `repositório` para cada um. Para obter mais informações sobre como usar o arquivo *pom.xml* no seu projeto, consulte "[Introdução a POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" na documentação do Apache Maven. {% data reusables.package_registry.authenticate-step %} -2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package. +2. Adicione as dependências do pacote ao elemento `dependências` do arquivo *pom.xml* do seu projeto, substituindo `com.exemplo:test` pelo seu pacote. ``` @@ -180,13 +182,13 @@ To install an Apache Maven package from {% data variables.product.prodname_regis ``` -3. Install the package. +3. Instale o pacote. ```shell $ mvn install ``` -### Further reading +### Leia mais -- "[Configuring Gradle for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages)" -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" +- "[Configurar o Gradle para uso com o {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages)" +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages.md b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages.md index d31c4e2c4a..5b2a495419 100644 --- a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages.md @@ -1,6 +1,6 @@ --- -title: Configuring Docker for use with GitHub Packages -intro: 'You can configure the Docker client to use {% data variables.product.prodname_registry %} to publish and retrieve docker images.' +title: Configurar o Docker para usar com o GitHub Packages +intro: 'Você pode configurar o cliente do Docker para usar o {% data variables.product.prodname_registry %} para publicar e recuperar imagens do Docker.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-docker-for-use-with-github-package-registry @@ -13,33 +13,33 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.admins-can-configure-package-types %} +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. -### About Docker and {% data variables.product.prodname_registry %} +### Autenticar-se no {% data variables.product.prodname_registry %} {% data reusables.package_registry.docker_registry_deprecation_status %} -When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. +Ao instalar ou publicar uma imagem do docker, o {% data variables.product.prodname_registry %} não é compatível camadas externas, como imagens do Windows. {% if enterpriseServerVersions contains currentVersion %} -Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." +Antes de poder usar o registro do Docker no {% data variables.product.prodname_registry %}, o administrador do site para {% data variables.product.product_location %} deve habilitar o suporte do Docker e o isolamento do subdomínio para a sua instância. Para obter mais informações, consulte "[Gerenciar pacotes do GitHub para a sua empresa](/enterprise/admin/packages)". {% endif %} -### Authenticating to {% data variables.product.prodname_registry %} +### Autenticar-se no {% data variables.product.prodname_registry %} {% data reusables.package_registry.docker_registry_deprecation_status %} {% data reusables.package_registry.authenticate-packages %} -#### Authenticating with a personal access token +#### Efetuando a autenticação com um token de acesso pessoal {% data reusables.package_registry.required-scopes %} -You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command. +Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} usando o comando de login do `docker`. -To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file. +Para manter suas credenciais seguras, recomendamos que você salve seu token de acesso pessoal em um arquivo local no seu computador e use o sinalizador `--password-stdin` do Docker que lê o seu token a partir de um arquivo local. {% if currentVersion == "free-pro-team@latest" %} {% raw %} @@ -57,36 +57,37 @@ To keep your credentials secure, we recommend you save your personal access toke {% endraw %} {% endif %} -To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. +Para usar este exemplo de comando de login, substitua `NOME DE USUÁRIO` pelo seu nome de usuário de {% data variables.product.product_name %} {% if enterpriseServerVersions contains currentVersion %}, `NOME DE HOST` pela URL para {% data variables.product.product_location %},{% endif %} e `~/TOKEN. xt` pelo caminho do arquivo para o seu token de acesso pessoal para {% data variables.product.product_name %}. -For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." +Para obter mais informações, consulte "[Login do Docker](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)". -#### Authenticating with the `GITHUB_TOKEN` +#### Efetuando a autenticação com o `GITHUB_TOKEN` {% data reusables.package_registry.package-registry-with-github-tokens %} -### Publishing an image +### Publicar uma imagem {% data reusables.package_registry.docker_registry_deprecation_status %} {% note %} -**Note:** Image names must only use lowercase letters. +**Observação:** Os nomes de imagem devem usar apenas letras minúsculas. {% endnote %} -{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. +O {% data variables.product.prodname_registry %} aceita várias imagens do Docker de nível superior por repositório. Um repositório pode ter qualquer número de tags de imagem. Você poderá conhecer uma publicação de serviço degradada ou instalar imagens do Docker com tamanho superior a 10 GB. As camadas são limitadas em 5 GB cada. Para obter mais informações, consulte "[Tag do Docker](https://docs.docker.com/engine/reference/commandline/tag/)" na documentação Docker. {% data reusables.package_registry.viewing-packages %} -1. Determine the image name and ID for your docker image using `docker images`. +1. Determine o nome da imagem e o ID da sua imagem do docker usando `imagens do docker`. ```shell $ docker images > < > > REPOSITORY TAG IMAGE ID CREATED SIZE > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB ``` -2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time. +2. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, and *PATH* to the image if it isn't in the current working directory. +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* com o nome de host de {% data variables.product.product_location %},{% endif %} e *VERSÃO* com a versão do pacote no momento da criação. {% if currentVersion == "free-pro-team@latest" %} ```shell $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION @@ -96,7 +97,8 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% endif %} -3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. +3. Se você ainda não criou uma imagem do docker para o pacote, crie a imagem, substituindo *PROPRIETÁRIO* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* pelo o nome do repositório que contém o seu projeto, *IMAGE_NAME* pelo o nome do pacote ou imagem, *VERSÃO* com a versão do pacote no momento da criação, +{% if enterpriseServerVersions contains currentVersion %} *NOME DE HOST* pelo o nome de host de {% data variables.product.product_location %},{% endif %} e *PATH* para a imagem se não estiver no diretório de trabalho atual. {% if currentVersion == "free-pro-team@latest" %} ```shell $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH @@ -106,7 +108,8 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% endif %} -4. Publish the image to {% data variables.product.prodname_registry %}. +4. Publicar a imagem em +{% data variables.product.prodname_registry %}. {% if currentVersion == "free-pro-team@latest" %} ```shell $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION @@ -118,15 +121,15 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen {% endif %} {% note %} - **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. + **Observação:** Você deve enviar sua imagem usando `IMAGE_NAME:VERSION` e não `IMAGE_NAME:SHA`. {% endnote %} -#### Example publishing a Docker image +#### Exemplo de publicação de uma imagem do Docker {% data reusables.package_registry.docker_registry_deprecation_status %} -You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. +Você pode publicar a versão 1.0 da imagem de `monalisa` para o repositório `octocat/octo-app` usando um ID de imagem. {% if currentVersion == "free-pro-team@latest" %} ```shell @@ -159,15 +162,16 @@ $ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 {% endif %} -You can publish a new Docker image for the first time and name it `monalisa`. +Você pode publicar uma nova imagem do Docker pela primeira vez e nomeá-la como `monalisa`. {% if currentVersion == "free-pro-team@latest" %} ```shell # Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION # Assumes Dockerfile resides in the current working directory (.) $ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . -# Push the image to {% data variables.product.prodname_registry %} +# Faça push da imagem no {% data variables.product.prodname_registry %} $ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 ``` @@ -182,11 +186,11 @@ $ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 ``` {% endif %} -### Downloading an image +### Fazer o download de uma imagem {% data reusables.package_registry.docker_registry_deprecation_status %} -You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %} and *TAG_NAME* with tag for the image you want to install. +Você pode usar o comando `docker pull` para instalar uma imagem docker a partir de {% data variables.product.prodname_registry %}, substituindo *OWNER* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* com o nome do repositório que contém seu projeto, *IMAGE_NAME* com o nome do pacote ou da imagem,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* com o nome do host da sua {% data variables.product.prodname_ghe_server %} instância {% endif %} e *TAG_NAME* com tag para a imagem que você deseja instalar. {% if currentVersion == "free-pro-team@latest" %} ```shell @@ -200,10 +204,10 @@ $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME {% note %} -**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. +**Nota:** Você deve fazer pull da imagem usando `IMAGE_NAME:VERSION` e não usar `IMAGE_NAME:SHA`. {% endnote %} -### Further reading +### Leia mais -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md index e0683ef902..6d563a046e 100644 --- a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md @@ -29,7 +29,7 @@ Para efetuar a autenticação em {% data variables.product.prodname_registry %} Você deve substituir: - `USUÁRIO` pelo o nome da sua conta de usuário em {% data variables.product.prodname_dotcom %}. - `TOKEN` pelo seu token de acesso pessoal. -- `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} +- `PROPRIETÁRIO` com o nome da conta do usuário ou da organização que é proprietário do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %} - `HOSTNAME` com o nome de host para sua instância de {% data variables.product.prodname_ghe_server %}. Se sua instância tem o isolamento de subdomínio habilitado: @@ -77,7 +77,7 @@ Se sua instância tem o isolamento de subdomínio desabilitado: ### Publicar um pacote -Você pode publicar um pacote no {% data variables.product.prodname_registry %}, efetuando a autenticação com um arquivo *nuget.config*. Ao fazer a publicação, você precisa usar o mesmo valor para `PROPRIETÁRIO` no seu arquivo *csproj* que você usa no seu arquivo de autenticação *nuget.config*. Especifique ou incremente o número da versão no seu *.csproj* e, em seguida, utilize o comando `dotnet pack` para criar um arquivo *.nuspec* para essa versão. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. +Você pode publicar um pacote no {% data variables.product.prodname_registry %}, efetuando a autenticação com um arquivo *nuget.config*. Ao fazer a publicação, você precisa usar o mesmo valor para `PROPRIETÁRIO` no seu arquivo *csproj* que você usa no seu arquivo de autenticação *nuget.config*. Especifique ou incremente o número da versão no seu *.csproj* e, em seguida, utilize o comando `dotnet pack` para criar um arquivo *.nuspec* para essa versão. Para obter mais informações sobre como criar seu pacote, consulte "[Criar e publicar um pacote](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" na documentação da Microsoft. {% data reusables.package_registry.viewing-packages %} @@ -89,7 +89,7 @@ Você pode publicar um pacote no {% data variables.product.prodname_registry %}, 3. Adicione informações específicas do seu projeto ao arquivo do seu projeto, que termina em *.csproj*. Você deve substituir: - `PROPRIETÁRIO` com o nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto. - `REPOSITÓRIO` pelo nome do repositório que contém o pacote que você deseja publicar. - - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion %} + - `1.0.0` com o número da versão do pacote.{% if enterpriseServerVersions contains currentVersion %} - `HOSTNAME` com o nome de host para sua instância de {% data variables.product.prodname_ghe_server %} .{% endif %} ``` xml @@ -159,7 +159,7 @@ Por exemplo, os projetos *OctodogApp* e *OctocatApp* irão publicar no mesmo rep ### Instalar um pacote -Usar pacotes do {% data variables.product.prodname_dotcom %} no seu projeto é semelhante a usar pacotes do *nuget.org*. Adicione suas dependências de pacote ao seu arquivo *.csproj* especificando o nome e a versão do pacote. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. +Usar pacotes do {% data variables.product.prodname_dotcom %} no seu projeto é semelhante a usar pacotes do *nuget.org*. Adicione suas dependências de pacote ao seu arquivo *.csproj* especificando o nome e a versão do pacote. Para obter mais informações sobre como usar um arquivo *.csproj* no seu projeto, consulte "[Trabalhar com pacotes NuGet](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" na documentação da Microsoft. {% data reusables.package_registry.authenticate-step %} diff --git a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md index 90b442cc99..92f6b39515 100644 --- a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md @@ -30,7 +30,7 @@ Substitua *REGISTRY-URL* pela URL do registro do Maven para a sua instância. Se instância de {% data variables.product.prodname_ghe_server %}. {% endif %} -Substitua *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %} *TOKEN* pelo seu token de acesso pessoal, *REPOSITÓRIO* pelo nome do repositório que contém o pacote que você deseja publicar, e *PROPRIETÁRIO* pelo nome do usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. +Substitua *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %} *TOKEN* pelo seu token de acesso pessoal, *REPOSITÓRIO* pelo nome do repositório que contém o pacote que você deseja publicar, e *PROPRIETÁRIO* pelo nome do usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. {% note %} diff --git a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md index 24e8685419..71f91ea7b4 100644 --- a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md @@ -1,6 +1,6 @@ --- -title: Configuring npm for use with GitHub Packages -intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.' +title: Configurar o npm para usar com o GitHub Packages +intro: 'Você pode configurar o npm para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto npm.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-npm-for-use-with-github-package-registry @@ -13,22 +13,22 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.admins-can-configure-package-types %} +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. -### Authenticating to {% data variables.product.prodname_registry %} +### Autenticar-se no {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -#### Authenticating with a personal access token +#### Efetuando a autenticação com um token de acesso pessoal {% data reusables.package_registry.required-scopes %} -You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token. +Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o npm editando seu arquivo *~/.npmrc* por usuário para incluir o seu token de acesso pessoal ou fazer o login no npm na linha de comando usando seu nome de usuário e token de acesso pessoal. -To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist. +Para efetuar a autenticação adicionando seu token de acesso pessoal ao seu arquivo *~/.npmrc*, edite o arquivo *~/.npmrc* para que o seu projeto inclua a linha a seguir substituindo {% if enterpriseServerVersions contains currentVersion %}*NOME DE HOST* pelo nome do host da sua instância {% data variables.product.prodname_ghe_server %} e {% endif %}*TOKEN* pelo seu token de acesso pessoal. Crie um novo arquivo *~/.npmrc* se um não existir. {% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation enabled: +Se sua instância tem o isolamento de subdomínio habilitado: {% endif %} ```shell @@ -36,75 +36,82 @@ If your instance has subdomain isolation enabled: ``` {% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation disabled: +Se sua instância tem o isolamento de subdomínio desabilitado: ```shell -//HOSTNAME/_registry/npm/:_authToken=TOKEN -``` -{% endif %} - -To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address. - -{% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation enabled: -{% endif %} - -```shell -$ npm login --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS -``` - -{% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation disabled: - -```shell -$ npm login --registry=https://HOSTNAME/_registry/npm/ +$ npm login --registry=https://npm.pkg.github.com > Username: USERNAME > Password: TOKEN > Email: PUBLIC-EMAIL-ADDRESS ``` {% endif %} -#### Authenticating with the `GITHUB_TOKEN` +Para efetuar a autenticação conectado no npm, use o comando `npm login` , substituindo o *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}, o *TOKEN* pelo seu token de acesso pessoal e *PUBLIC-EMAIL-ADDRESS* pelo seu endereço de e-mail. + +Se {% data variables.product.prodname_registry %} não é seu registro de pacote padrão para usar npm e você deseja usar o comando `npm audit` , recomendamos que você use o sinalizador `--scope` com o proprietário do pacote quando você efetuar a autenticação no {% data variables.product.prodname_registry %}. + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio desabilitado: + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### Efetuando a autenticação com o `GITHUB_TOKEN` {% data reusables.package_registry.package-registry-with-github-tokens %} -### Publishing a package +### Publicar um pacote {% note %} -**Note:** Package names and scopes must only use lowercase letters. +**Nota:** Os nomes dos pacotes e escopos só devem usar letras minúsculas. {% endnote %} -By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation. +Por padrão, o {% data variables.product.prodname_registry %} publica um pacote no repositório {% data variables.product.prodname_dotcom %} que você especificar no campo nome do arquivo *package.json*. Por exemplo, você publicaria um pacote denominado `@my-org/test` no repositório `my-org/test` do {% data variables.product.prodname_dotcom %}. Você pode adicionar um resumo da página de listagem do pacote incluindo um arquivo *README.md* no diretório do seu pacote. Para obter mais informações, consulte "[Trabalhando com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" e "[Como criar Módulos de Node.js](https://docs.npmjs.com/getting-started/creating-node-modules)" na documentação do npm. -You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)." +Você pode publicar vários pacotes no mesmo repositório do {% data variables.product.prodname_dotcom %} incluindo um campo de `URL` no arquivo *package.json*. Para obter mais informações, consulte "[Publicar vários pacotes no mesmo repositório](#publishing-multiple-packages-to-the-same-repository)". -You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`. +É possível definir o mapeamento do escopo para o seu projeto usando um arquivo local *.npmrc* no projeto ou usando a opção `publishConfig` em *package.json*. {% data variables.product.prodname_registry %} só é compatível com pacotes npm com escopo definido. Pacotes com escopo têm nomes no formato `@owner/name`. Os pacotes com escopo sempre começam pelo símbolo `@`. Talvez seja necessário atualizar o nome no *package.json* para usar o nome com escopo. Por exemplo, `"name": "@codertocat/hello-world-npm"`. {% data reusables.package_registry.viewing-packages %} -#### Publishing a package using a local *.npmrc* file +#### Publicar um pacote usando o arquivo *.npmrc* local -You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}. +Você pode usar um arquivo *.npmrc* para configurar o mapeamento do escopo para o seu projeto. No arquivo *.npmrc*, use a URL e o proprietário da conta de {% data variables.product.prodname_registry %} para que {% data variables.product.prodname_registry %} saiba onde rotear as solicitações de pacotes. O uso de um arquivo *.npmrc* impede que outros desenvolvedores publiquem acidentalmente o pacote no npmjs.org em vez de {% data variables.product.prodname_registry %}. {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} {% data reusables.package_registry.add-npmrc-to-repo-step %} -1. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" {% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`. +1. Verifique o nome do pacote no *package.json* do seu projeto. O campo `name` (nome) deve conter o escopo e o nome do pacote. Por exemplo, se o pacote é denominado de "test" e você está publicando em "My-org" +organização de {% data variables.product.prodname_dotcom %}, o campo `nome` no seu *package.json* deve ser `@my-org/test`. {% data reusables.package_registry.verify_repository_field %} {% data reusables.package_registry.publish_package %} -#### Publishing a package using `publishConfig` in the *package.json* file +#### Publicar um pacote usando o `publishConfig` no arquivo *package.json* -You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation. +Você pode usar o elemento `publishConfig` no arquivo *package.json* para especificar o registro onde você quer o pacote publicado. Para obter mais informações, consulte "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" na documentação npm. -1. Edit the *package.json* file for your package and include a `publishConfig` entry. +1. Edite o arquivo *package.json* do seu pacote e inclua uma entrada `publishConfig`. {% if enterpriseServerVersions contains currentVersion %} - If your instance has subdomain isolation enabled: + Se sua instância tem o isolamento de subdomínio habilitado: {% endif %} ```shell "publishConfig": { @@ -112,7 +119,7 @@ You can use `publishConfig` element in the *package.json* file to specify the re }, ``` {% if enterpriseServerVersions contains currentVersion %} - If your instance has subdomain isolation disabled: + Se sua instância tem o isolamento de subdomínio desabilitado: ```shell "publishConfig": { "registry":"https://HOSTNAME/_registry/npm/" @@ -122,13 +129,13 @@ You can use `publishConfig` element in the *package.json* file to specify the re {% data reusables.package_registry.verify_repository_field %} {% data reusables.package_registry.publish_package %} -### Publishing multiple packages to the same repository +### Publicar vários pacotes no mesmo repositório -To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package. +Para publicar vários pacotes no mesmo repositório, você pode incluir a URL do repositório do {% data variables.product.prodname_dotcom %} no campo `repositório` do arquivo *package.json* para cada pacote. -To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. +Para garantir que a URL do repositório esteja correta, substitua REPOSITÓRIO pelo nome do repositório que contém o pacote que você deseja publicar, e o PROPRIETÁRIO pelo nome de usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. -{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name. If you store the *package.json* file outside the root directory of your repository, you can use the `directory` field to specify the location where {% data variables.product.prodname_registry %} can find the *package.json* files. +O {% data variables.product.prodname_registry %} corresponderá ao repositório baseado na URL, em vez de ser baseado no nome do pacote. Se você armazenar o arquivo *package.json* fora do diretório raiz do seu repositório, você poderá usar o campo `diretório` para especificar o local onde {% data variables.product.prodname_registry %} pode encontrar os arquivos *package.json*. ```shell "repository" : { @@ -138,18 +145,18 @@ To ensure the repository's URL is correct, replace REPOSITORY with the name of t }, ``` -### Installing a package +### Instalar um pacote -You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation. +Você pode instalar pacotes do {% data variables.product.prodname_registry %} adicionando os pacotes como dependências no arquivo *package.json* para o seu projeto. Para obter mais informações sobre como usar um pacote *package.json* no projeto, consulte "[Trabalhar com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" na documentação npm. -By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." +Por padrão, você pode adicionar pacotes a partir de uma organização. Para obter mais informações, consulte [Instalar pacotes de outras organizações](#installing-packages-from-other-organizations)." -You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. +Você também precisa adicionar o arquivo *.npmrc* ao seu projeto para que todas as solicitações de instalação passem pelo {% data variables.product.prodname_registry %}. Ao encaminhar todas as solicitações através de {% data variables.product.prodname_registry %}, você pode usar pacotes com escopo e sem escopo de *npmjs.com*. Para obter mais informações, consulte "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação npm. {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} {% data reusables.package_registry.add-npmrc-to-repo-step %} -4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. +4. Configure *package.json* no seu projeto para usar o pacote que você está instalando. Para adicionar as suas dependências de pacote ao arquivo *package.json* para {% data variables.product.prodname_registry %}, especifique o nome do pacote com escopo completo, como, por exemplo, `@my-org/server`. Para pacotes do *npmjs.com*, especifique o nome completo, como `@babel/core` ou `@lodash`. Por exemplo, o arquivo *package.json* a seguir usa o pacote `@octo-org/octo-app` como uma dependência. ``` { @@ -164,18 +171,18 @@ You also need to add the *.npmrc* file to your project so all requests to instal } } ``` -5. Install the package. +5. Instale o pacote. ```shell $ npm install ``` -#### Installing packages from other organizations +#### Instalar pacotes de outras organizações -By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. +Por padrão, você só pode usar pacotes do {% data variables.product.prodname_registry %} de uma organização. Se você deseja encaminhar solicitações de pacotes para várias organizações e usuários, você pode adicionar linhas ao seu arquivo *.npmrc* substituindo {% if enterpriseServerVersions contains currentVersion %}*NOME DE HOST* pelo nome do host da sua instância de {% data variables.product.prodname_ghe_server %} e {% endif %}*PROPRIETÁRIO* pelo nome do usuário ou organização que possui o repositório que contém o seu projeto. {% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation enabled: +Se sua instância tem o isolamento de subdomínio habilitado: {% endif %} ```shell @@ -185,7 +192,7 @@ registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github ``` {% if enterpriseServerVersions contains currentVersion %} -If your instance has subdomain isolation disabled: +Se sua instância tem o isolamento de subdomínio desabilitado: ```shell registry=https://HOSTNAME/_registry/npm/OWNER @@ -194,6 +201,6 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} -### Further reading +### Leia mais -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages.md b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages.md index b0e21632a8..5e8bed45f9 100644 --- a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages.md @@ -1,6 +1,6 @@ --- -title: Configuring RubyGems for use with GitHub Packages -intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.' +title: Configurar o RubyGems para uso com o GitHub Packages +intro: 'Você pode configurar RubyGems para publicar um pacote em {% data variables.product.prodname_registry %} e usar pacotes armazenados em {% data variables.product.prodname_registry %} como dependências em um projeto Ruby com o Bundler.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-rubygems-for-use-with-github-package-registry @@ -13,55 +13,54 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.admins-can-configure-package-types %} +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. -### Prerequisites +### Pré-requisitos -- You must have rubygems 2.4.1 or higher. To find your rubygems version: +- Você deve ter o rubygems 2.4.1 ou superior. Para encontrar sua versão do rubygems: ```shell $ gem --version ``` - - - You must have bundler 1.6.4 or higher. To find your Bundler version: + + - Você deve ter o bundler 1.6.4 ou superior. Para encontrar sua versão do Bundler: ```shell $ bundle --version Bundler version 1.13.7 ``` - - - Install keycutter to manage multiple credentials. To install keycutter: + + - Instale o keycutter para gerenciar várias credenciais. Para instalar o keycutter: ```shell $ gem install keycutter ``` - -### Authenticating to {% data variables.product.prodname_registry %} - + +### Autenticar-se no {% data variables.product.prodname_registry %} + {% data reusables.package_registry.authenticate-packages %} - -#### Authenticating with a personal access token - + +#### Efetuando a autenticação com um token de acesso pessoal + {% data reusables.package_registry.required-scopes %} - -You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems. - -To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your personal access token. Create a new *~/.gem/credentials* file if this file doesn't exist. - -For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your personal access token. - + +Você pode efetuar a autenticação em {% data variables.product.prodname_registry %} com o RubyGems editando o arquivo *~/.gem/credentials* para publicação de gems, editando o arquivo *~/.gemrc* para instalar um único gem, ou usando o Bundler para rastrear e instalar um ou mais gems. + +Para publicar novos gems, você precisa efetuar a autenticação no {% data variables.product.prodname_registry %} com RubyGems, editando seu arquivo *~/.gem/credentials* para incluir seu token de acesso pessoal. Crie um novo arquivo *~/.gem/credentials* se este arquivo não existir. + +Por exemplo, você criaria ou editaria um arquivo *~/.gem/credentials* para incluir o indicado a seguir, substituindo *TOKEN* pelo seu token de acesso pessoal. + ```shell ---- -:github: Bearer TOKEN +gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" } ``` - -To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace: - - `USERNAME` with your {% data variables.product.prodname_dotcom %} username. - - `TOKEN` with your personal access token. - - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} - - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance. -{% endif %} - -If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example. - + +Para instalar gems, você deve efetuar a autenticação no {% data variables.product.prodname_registry %}, editando o arquivo *~/.gemrc* para o seu projeto incluir `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. Você deve substituir: + - `NOME DE USUÁRIO` pelo seu nome de usuário no {% data variables.product.prodname_dotcom %}. + - `TOKEN` pelo seu token de acesso pessoal. + - `PROPRIETÁRIO` com o nome da conta do usuário ou da organização que é proprietário do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %} + - `URL` com a URL para o registro do Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %}. +{% endif %} + +Se você não tiver um arquivo *~/.gemrc*, crie um arquivo *~/.gemrc* usando este exemplo. + ```shell --- :backtrace: false @@ -73,29 +72,29 @@ If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this exa :verbose: true ``` - -To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - + +Para autenticar com o bundler, configure o Bundler para usar o seu token de acesso pessoal, substituindo *USERNAME* com seu {% data variables.product.prodname_dotcom %} nome de usuário, *TOKEN* com seu token de acesso pessoal, e *OWNER* com o nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %} Substitua `URL REGISTRO` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %} .{% endif %} + ```shell $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN ``` - -#### Authenticating with the `GITHUB_TOKEN` - -{% data reusables.package_registry.package-registry-with-github-tokens %} - -### Publishing a package -{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation. - +#### Efetuando a autenticação com o `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar um pacote + +{% data reusables.package_registry.default-name %} Por exemplo, ao publicar `octo-gem` na organização `octo-org` , {% data variables.product.prodname_registry %} publicará o gem no repositório `octo-org/octo-gem`. Para obter mais informações sobre como criar seu gem, consulte "[Criar seu próprio gem](http://guides.rubygems.org/make-your-own-gem/)" na documentação do RubyGems. + {% data reusables.package_registry.viewing-packages %} - + {% data reusables.package_registry.authenticate-step %} -2. Build the package from the *gemspec* to create the *.gem* package. +2. Crie o pacote da *gemspec* para criar o pacote *.gem*. ```shell gem build OCTO-GEM.gemspec ``` -3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} +3. Publicar um pacote em {% data variables.product.prodname_registry %}, substituindo o `OWNER` pelo nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto e `OCTO-GEM` pelo nome do seu pacote de gemas.{% if enterpriseServerVersions contains currentVersion %} substitui `REGISTRY-URL` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %} .{% endif %} ```shell $ gem push --key github \ @@ -103,20 +102,20 @@ $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygem OCTO-GEM-0.0.1.gem ``` -### Publishing multiple packages to the same repository +### Publicar vários pacotes no mesmo repositório -To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% if enterpriseServerVersions contains currentVersion %} Replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} +Para publicar vários gems no mesmo repositório, você pode incluir a URL no repositório de {% data variables.product.prodname_dotcom %} no campo `github_repo` em `gem.metadata`. Se você incluir este campo, {% data variables.product.prodname_dotcom %} irá corresponde ao repositório baseado neste valor, em vez de usar o nome do gem.{% if enterpriseServerVersions contains currentVersion %} Substitua o *NOME DE HOST* pelo nome do host da sua instância {% data variables.product.prodname_ghe_server %}.{% endif %} ``` gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` -### Installing a package +### Instalar um pacote -You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing you *Gemfile*. +É possível usar gems do {% data variables.product.prodname_registry %} assim como você usa gems de *rubygems.org*. Você precisa efetuar a autenticação no {% data variables.product.prodname_registry %} , adicionando o seu usuário ou organização do {% data variables.product.prodname_dotcom %} como fonte ao arquivo *~/.gemrc* ou usando o Bundler e editando-o *Gemfile*. {% data reusables.package_registry.authenticate-step %} -2. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} +2. Para o Bundler, adicione seu usuário ou organização {% data variables.product.prodname_dotcom %} como uma fonte no seu *Gemfile* para buscar gems a partir desta nova fonte. Por exemplo, você pode adicionar um novo bloco`de fonte`ao seu *Gemfile* que usa {% data variables.product.prodname_registry %} apenas para os pacotes que você especificar, substituindo *GEM NOME* pelo pacote que deseja instalar de {% data variables.product.prodname_registry %} e *OWNER* pelo usuário ou organização que possui o repositório que contém a gema que deseja instalar.{% if enterpriseServerVersions contains currentVersion %} substitua `URL REGISTRY` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %} .{% endif %} ``` source "https://rubygems.org" @@ -128,7 +127,7 @@ You can use gems from {% data variables.product.prodname_registry %} much like y end ``` -3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html). +3. Para versões do Bundler anteriores à 1.7.0, você deve adicionar uma nova `fonte` global. Para obter mais informações sobre como usar o Bundler, consulte a [documentação bundler.io](http://bundler.io/v1.5/gemfile.html). ``` source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" @@ -138,11 +137,11 @@ You can use gems from {% data variables.product.prodname_registry %} much like y gem "GEM NAME" ``` -4. Install the package: +4. Instale o pacote: ```shell $ gem install octo-gem --version "0.1.1" ``` -### Further reading +### Leia mais -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions.md b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions.md index 8875879a16..55b0ca3c71 100644 --- a/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions.md +++ b/translations/pt-BR/content/packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions.md @@ -1,6 +1,6 @@ --- -title: Using GitHub Packages with GitHub Actions -intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.' +title: Usar o GitHub Packages com o GitHub Actions +intro: 'É possível configurar um fluxo de trabalho no {% data variables.product.prodname_actions %} para publicar ou instalar automaticamente um pacote do {% data variables.product.prodname_registry %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions @@ -11,43 +11,44 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} +### Sobre {% data variables.product.prodname_registry %} com {% data variables.product.prodname_actions %} -{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)". -You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. +Você pode estender os recursos de CI e CD do seu repositório publicando ou instalando pacotes como parte do seu fluxo de trabalho. {% if currentVersion == "free-pro-team@latest" %} -#### Authenticating to {% data variables.product.prodname_github_container_registry %} +#### Autenticar-se no {% data variables.product.prodname_github_container_registry %} {% data reusables.package_registry.container-registry-beta %} {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} -For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)." +Para um exemplo de autenticação, consulte "[Efetuar a autenticação com o {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)". {% endif %} -#### Authenticating to package registries on {% data variables.product.prodname_dotcom %} +#### Efetuar a autenticação nos registros do pacote em {% data variables.product.prodname_dotcom %} -{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The `GITHUB_TOKEN` has `read:packages` and `write:packages` scopes to the current repository. For forks, the token also has the `read:packages` scope for the parent repository. +{% if currentVersion == "free-pro-team@latest" %}Se você deseja que o fluxo de trabalho efetue a autenticação em {% data variables.product.prodname_registry %} para acessar um registro de pacotes diferentes do {% data variables.product.prodname_container_registry %} em {% data variables.product.product_name %}, {% else %}Para efetuar a autenticação nos registros de pacotes no {% data variables.product.product_name %},{% endif %} recomendamos usar o `GITHUB_TOKEN` que {% data variables.product.product_name %} cria automaticamente para o seu repositório quando você habilita {% data variables.product.prodname_actions %} em vez de um token de acesso pessoal para autenticação. O `GITHUB_TOKEN` tem escopos `read:packages` e `write:packages` do repositório atual. Para bifurcações, o token também tem o escopo `read:packages` para o repositório principal. -You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." +Você pode fazer referência ao `GITHUB_TOKEN` no seu arquivo de fluxo de trabalho usando o contexto {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %}. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". -### Publishing a package using an action +### Publicar um pacote usando uma ação -You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. +Você pode publicar pacotes como parte do fluxo da sua integração contínua (CI) usando o {% data variables.product.prodname_actions %}. Por exemplo, você pode configurar um fluxo de trabalho para que sempre que um desenvolvedor fizer push do código para o branch-padrão, o fluxo de trabalho executará testes de CI. Se esses testes passarem, o fluxo de trabalho publicará uma nova versão de pacote no {% data variables.product.prodname_registry %}. Este fluxo de trabalho automatiza a criação de novas versões de pacotes somente se o código atender aos seus padrões de qualidade. {% data reusables.package_registry.actions-configuration %} -### Installing a package using an action +### Instalar um pacote usando uma ação -You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. +Você pode instalar pacotes como parte de seu fluxo de CI usando o {% data variables.product.prodname_actions %}. Por exemplo, você poderia configurar um fluxo de trabalho para que sempre que um desenvolvedor fizesse push do código para um pull request, o fluxo de trabalho resolveria as dependências, fazendo o download e instalando pacotes hospedados pelo {% data variables.product.prodname_registry %}. Em seguida, o fluxo de trabalho pode executar testes de CI que exigem as dependências. -Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %} +Instalar pacotes hospedados pelo {% data variables.product.prodname_registry %} através de {% data variables.product.prodname_actions %} exige uma configuração mínima ou autenticação adicional ao usar `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} A transferência de dados também é grátis quando uma ação instala um pacote. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".{% endif %} {% if currentVersion == "free-pro-team@latest" %} -`GITHUB_TOKEN` cannot install packages from any private repository besides the repository where the action runs. You cannot currently use `GITHUB_TOKEN` to authenticate to {% data variables.product.prodname_github_container_registry %}. +`GITHUB_TOKEN` não pode instalar pacotes a partir de qualquer repositório privado além do repositório onde a ação é executada. Atualmente, você não pode usar `GITHUB_TOKEN` para efetuar a autenticação +{% data variables.product.prodname_github_container_registry %}. {% endif %} {% data reusables.package_registry.actions-configuration %} diff --git a/translations/pt-BR/content/rest/guides/basics-of-authentication.md b/translations/pt-BR/content/rest/guides/basics-of-authentication.md index ebbd031289..97ac13a4f7 100644 --- a/translations/pt-BR/content/rest/guides/basics-of-authentication.md +++ b/translations/pt-BR/content/rest/guides/basics-of-authentication.md @@ -22,7 +22,7 @@ Você pode fazer o download do código-fonte completo para este projeto[no repos ### Registrar seu aplicativo -First, you'll need to [register your application][new oauth app]. A cada aplicativo OAuth registrado recebe um ID de Cliente único e um Segredo de Cliente. O Segredo do Cliente não deve ser compartilhado! Isso inclui verificar o string de caracteres no seu repositório. +Primeiro, você precisará [registrar o seu aplicativo][new oauth app]. A cada aplicativo OAuth registrado recebe um ID de Cliente único e um Segredo de Cliente. O Segredo do Cliente não deve ser compartilhado! Isso inclui verificar o string de caracteres no seu repositório. Você pode preencher cada informação da forma que preferir, exceto a **URL de chamada de retorno de autorização**. Esta é facilmente a parte mais importante para configurar o seu aplicativo. É a URL de chamada de retorno que o {% data variables.product.product_name %} retorna ao usuário após a autenticação bem-sucedida. @@ -47,9 +47,9 @@ get '/' do end ``` -Your client ID and client secret keys come from [your application's configuration page][app settings]. -{% if currentVersion == "free-pro-team@latest" %} You should **never, _ever_** store these values in -{% data variables.product.product_name %}--or any other public place, for that matter.{% endif %} We recommend storing them as +O seu ID de cliente e as chaves secretas de cliente vêm da [página de configuração do seu aplicativo][app settings]. +{% if currentVersion == "free-pro-team@latest" %} Você **nunca, __** deve armazenar esses valores em +{% data variables.product.product_name %}--ou qualquer outro lugar público, para essa questão.{% endif %}Recomendamos armazená-los como [Variáveis de ambiente][about env vars]--que é exatamente o que fizemos aqui. Em seguida, em _views/index.erb_, cole este conteúdo: @@ -73,7 +73,7 @@ Em seguida, em _views/index.erb_, cole este conteúdo: ``` -(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra guide].) +(Se você não estiver familiarizado com a forma como Sinatra funciona, recomendamos [a leitura do guia do Sinatra][Sinatra guide].) Observe também que a URL usa o parâmetro da consulta do `escopo` para definir os [escopos][oauth scopes] solicitados pelo aplicativo. Para o nosso aplicativo, estamos solicitando o escopo `user:email` para ler endereços de e-mail privados. @@ -130,7 +130,7 @@ Além disso, uma vez que existe uma relação hierárquica entre os escopos, voc Verificar escopos apenas antes de fazer solicitações não é suficiente, já que é possível que os usuários mudem os escopos entre a sua verificação e a solicitação real. Caso isso aconteça, as chamadas par a API que você espera ter sucesso podem falhar com o status `404` ou `401` ou retornar um subconjunto diferente de informações. -Para ajudá-lo a gerenciar essas situações facilmente, todas as respostas da API para solicitações feitas com tokens válidos também contêm um [`cabeçalho de ` X-OAuth-Scopes][oauth scopes]. Este cabeçalho contém a lista de escopos do token que foi usado para fazer a solicitação. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/v3/apps/oauth_applications/#check-an-authorization\]{% endif %}. Use esta informação para detectar alterações no escopo do token e informar os seus usuários sobre mudanças nas funcionalidades do aplicativo disponível. +Para ajudá-lo a gerenciar essas situações facilmente, todas as respostas da API para solicitações feitas com tokens válidos também contêm um [`cabeçalho de ` X-OAuth-Scopes][oauth scopes]. Este cabeçalho contém a lista de escopos do token que foi usado para fazer a solicitação. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. Use esta informação para detectar alterações no escopo do token e informar os seus usuários sobre mudanças nas funcionalidades do aplicativo disponível. #### Fazer solicitações autenticadas diff --git a/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md b/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md index 75f4e7f7e3..abc9fd00eb 100644 --- a/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md +++ b/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md @@ -20,7 +20,7 @@ Interessado em integrar-se à plataforma do GitHub? [Você está em boas mãos]( Há várias etapas que você pode dar para garantir o recebimento de cargas entregues pelo GitHub: 1. Certifique-se de que seu servidor de recebimento tenha uma conexão HTTPS. Por padrão, o GitHub verificará os certificados SSL ao entregar cargas.{% if currentVersion == "free-pro-team@latest" %} -1. Você pode adicionar [o endereço IP que usamos ao entregar hooks](/github/authenticating-to-github/about-githubs-ip-addresses) à lista de permissões do seu servidor. Para garantir que você esteja sempre verificando o endereço IP correto, você pode [usar o ponto de extremidade `/meta`](/v3/meta/#meta) para encontrar o endereço que utilizamos.{% endif %} +1. Você pode adicionar [o endereço IP que usamos ao entregar hooks](/github/authenticating-to-github/about-githubs-ip-addresses) à lista de permissões do seu servidor. Para garantir que você esteja sempre verificando o endereço IP correto, você pode [usar o ponto de extremidade `/meta`](/rest/reference/meta#meta) para encontrar o endereço que utilizamos.{% endif %} 1. Forneça [um token secreto](/webhooks/securing/) para garantir que as cargas estão definitivamente vindo do GitHub. Ao impor um token secreto, você garantirá que todos os dados recebidos pelo seu servidor estejam absolutamente vindo do GitHub. Idealmente, você deve fornecer um token secreto diferente *por usuário* do seu serviço. Dessa forma, se um token for comprometido, nenhum outro usuário será afetado. ### Favoreça o trabalho assíncrono em detrimento do trabalho síncrono @@ -49,7 +49,7 @@ Os usuários podem entrar nas respostas do servidor que você enviar de volta ao O GitHub é explícito ao informar quando um recurso foi movido, fornecendo um código de estado de redirecionamento. Você deveria seguir estes redirecionamentos. Cada resposta de redirecionamento define o cabeçalho da `Localização` com a nova URI a ser acessada. Se você receber um redirecionamento, é melhor atualizar seu código para seguir a nova URI, caso você esteja solicitando um caminho obsoleto que possamos remover. -Nós fornecemos [uma lista de códigos de status de HTTP](/v3/#http-redirects) que você pode consultar ao projetar o seu aplicativo para seguir redirecionamentos. +Nós fornecemos [uma lista de códigos de status de HTTP](/rest#http-redirects) que você pode consultar ao projetar o seu aplicativo para seguir redirecionamentos. ### Não analise as URLs manualmente diff --git a/translations/pt-BR/content/rest/guides/building-a-ci-server.md b/translations/pt-BR/content/rest/guides/building-a-ci-server.md index 8e2363e499..a89ed0fc6e 100644 --- a/translations/pt-BR/content/rest/guides/building-a-ci-server.md +++ b/translations/pt-BR/content/rest/guides/building-a-ci-server.md @@ -129,7 +129,7 @@ No GitHub, usamos uma versão do [Janky][janky] para gerenciar a nossa CI durant Toda esta comunicação é canalizada de volta para nossas salas de bate-papo. Você não precisa construir sua própria configuração de CI para usar este exemplo. Você sempre pode confiar nas[Integrações do GitHub][integrations]. -[status API]: /v3/repos/statuses/ +[status API]: /rest/reference/repos#statuses [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server diff --git a/translations/pt-BR/content/rest/guides/delivering-deployments.md b/translations/pt-BR/content/rest/guides/delivering-deployments.md index 2be317d5b0..9117b4ce80 100644 --- a/translations/pt-BR/content/rest/guides/delivering-deployments.md +++ b/translations/pt-BR/content/rest/guides/delivering-deployments.md @@ -13,7 +13,7 @@ versions: -A [API de Implantações][deploy API] fornece seus projetos hospedados em {% data variables.product.product_name %} com a capacidade de lançá-los em um servidor do qual você é proprietário. Combinado com [a API de Status][status API], você será capaz de coordenar suas implantações no momento em que seu código chegar ao branch-padrão. +The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with the capability to launch them on a server that you own. Combinado com [a API de Status][status API], você será capaz de coordenar suas implantações no momento em que seu código chegar ao branch-padrão. Este guia usará a API para demonstrar uma configuração que você pode usar. No nosso cenário, iremos: @@ -145,7 +145,7 @@ No GitHub, usamos uma versão do [Heavan][heaven] para gerenciar nossas implanta Pronto! Você não precisa criar sua própria configuração de implantação para usar este exemplo. Você sempre pode confiar nas [Integrações do GitHub][integrations]. -[deploy API]: /v3/repos/deployments/ +[deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok diff --git a/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md b/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md index 2c8919c05b..6852305c15 100644 --- a/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md @@ -93,20 +93,20 @@ Se você leu a documentação do princípio ao fim, é possível que você tenha Como um aplicativo, de modo geral, você quer todas as organizações de usuários (públicas e privadas) que seu aplicativo está autorizado a acessar. O fluxo de trabalho acima fornecerá exatamente isso. -[basics-of-authentication]: /v3/guides/basics-of-authentication/ -[list-public-orgs]: /v3/orgs/#list-organizations-for-a-user -[list-repositories-for-current-user]: /v3/repos/#list-repositories-for-the-authenticated-user -[list-orgs-for-current-user]: /v3/orgs/#list-organizations-for-the-authenticated-user -[list-teams]: /v3/teams/#list-teams -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests +[basics-of-authentication]: /rest/guides/basics-of-authentication +[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user +[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user +[list-teams]: /rest/reference/teams#list-teams +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ [octokit.rb]: https://github.com/octokit/octokit.rb [octokit.rb]: https://github.com/octokit/octokit.rb [octokit.rb]: https://github.com/octokit/octokit.rb -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user -[publicize-membership]: /v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user -[register-oauth-app]: /v3/guides/basics-of-authentication/#registering-your-app +[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user +[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-git-database-api.md index 2ea7b063d4..bace0c57b7 100644 --- a/translations/pt-BR/content/rest/guides/getting-started-with-the-git-database-api.md +++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-git-database-api.md @@ -11,7 +11,7 @@ versions: Isso basicamente permite que você reimplemente uma série de funcionalidades do Git sobre nossa API, criando objetos sem processamento diretamente no banco de dados e atualizando referências de ramificações que você pode fazer tecnicamente sobre qualquer coisa que o Git possa fazer sem tê-lo instalado. -Funções da API do Banco de Dados do Git retornará um `409 Conflict` se o repositório do Git estiver vazio ou indisponível. Um repositório indisponível normalmente significa que o {% data variables.product.product_name %} está no processo de criação do repositório. Para um repositório vazio, você pode usar o ponto de extremidade "[Criar ou atualizar o conteúdo do arquivo](/v3/repos/contents/#create-or-update-file-contents)" para criar conteúdo e inicializar o repositório para que você possa usar a API de banco de dados do Git. Entre em contato com {% data variables.contact.contact_support %} se esse status de resposta persistir. +Funções da API do Banco de Dados do Git retornará um `409 Conflict` se o repositório do Git estiver vazio ou indisponível. Um repositório indisponível normalmente significa que o {% data variables.product.product_name %} está no processo de criação do repositório. Para um repositório vazio, você pode usar o ponto de extremidade "[Criar ou atualizar o conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents)" para criar conteúdo e inicializar o repositório para que você possa usar a API de banco de dados do Git. Entre em contato com {% data variables.contact.contact_support %} se esse status de resposta persistir. ![Visão geral do banco de dados Git](/assets/images/git-database-overview.png) @@ -33,14 +33,14 @@ Pode parecer complexo, mas, na verdade, é bem simples. Ao entender o modelo e e {% warning %} -**Aviso!**Não dependa do uso do Git diretamente ou de [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) para atualizações para fazer `merge` de refs do Git, pois este conteúdo fica desatualizado sem aviso prévio. +**Aviso!**Não dependa do uso do Git diretamente ou de [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) para atualizações para fazer `merge` de refs do Git, pois este conteúdo fica desatualizado sem aviso prévio. {% endwarning %} -Uma API consumível precisa solicitar explicitamente que um pull request crie um commit de merge de _teste_. Um commit de merge de _teste_ é criado quando você visualiza o pull request na interface do usuário e o botão "Merge" é exibido, ou quando [obtém](/v3/pulls/#get-a-pull-request), [cria](/v3/pulls/#create-a-pull-request), ou [edita](/v3/pulls/#update-a-pull-request) um pull request usando a API REST. Sem esta solicitação, as referências de `merge` do Git ficarão desatualizadas até a próxima vez que alguém visualizar o pull request. +Uma API consumível precisa solicitar explicitamente que um pull request crie um commit de merge de _teste_. Um commit de merge de _teste_ é criado quando você visualiza o pull request na interface do usuário e o botão "Merge" é exibido, ou quando [obtém](/rest/reference/pulls#get-a-pull-request), [cria](/rest/reference/pulls#create-a-pull-request), ou [edita](/rest/reference/pulls#update-a-pull-request) um pull request usando a API REST. Sem esta solicitação, as referências de `merge` do Git ficarão desatualizadas até a próxima vez que alguém visualizar o pull request. Se você está usando métodos de sondagem que produzem refs do Git de `merge` obsoletos, o GitHub recomenda usar as etapas a seguir para obter as últimas alterações do branch-padrão: 1. Receber o webhook do pull request. -2. Chame [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) para iniciar um trabalho em segundo plano para criar o candidato de do commit do merge. -3. Faça a sondam do seu repositório usando [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) para ver se o atributo `mesclável` é `verdadeiro` ou `falso`. Você pode usar o Git diretamente ou [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) para atualizações para fazer `merge` das refs do Git apenas após executar as etapas anteriores. +2. Chame [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) para iniciar um trabalho em segundo plano para criar o candidato de do commit do merge. +3. Faça a sondam do seu repositório usando [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) para ver se o atributo `mesclável` é `verdadeiro` ou `falso`. Você pode usar o Git diretamente ou [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) para atualizações para fazer `merge` das refs do Git apenas após executar as etapas anteriores. diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md index d6fa56863b..c789e30d45 100644 --- a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md @@ -370,33 +370,33 @@ Continue aprendendo com o próximo guia da API [Princípios básicos da autentic [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[repos-api]: /v3/repos/ -[repos-api]: /v3/repos/ +[repos-api]: /rest/reference/repos +[repos-api]: /rest/reference/repos [pages]: http://pages.github.com [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore -[issues-api]: /v3/issues/ +[issues-api]: /rest/reference/issues [link-header]: http://www.w3.org/wiki/LinkHeader/ -[conditional-requests]: /v3/#conditional-requests -[rate-limiting]: /v3/#rate-limiting -[rate-limiting]: /v3/#rate-limiting -[users api]: /v3/users/#get-a-user +[conditional-requests]: /rest#conditional-requests +[rate-limiting]: /rest#rate-limiting +[rate-limiting]: /rest#rate-limiting +[users api]: /rest/reference/users#get-a-user [defunkt github]: https://github.com/defunkt [defunkt github]: https://github.com/defunkt [json]: http://en.wikipedia.org/wiki/JSON -[authentication]: /v3/#authentication +[authentication]: /rest#authentication [personal token]: /articles/creating-an-access-token-for-command-line-use [personal token]: /articles/creating-an-access-token-for-command-line-use [tokens settings]: https://github.com/settings/tokens -[pagination]: /v3/#pagination -[get repo]: /v3/repos/#get-a-repository -[create repo]: /v3/repos/#create-a-repository-for-the-authenticated-user -[create issue]: /v3/issues/#create-an-issue +[pagination]: /rest#pagination +[get repo]: /rest/reference/repos#get-a-repository +[create repo]: /rest/reference/repos#create-a-repository-for-the-authenticated-user +[create issue]: /rest/reference/issues#create-an-issue [auth guide]: /guides/basics-of-authentication -[user repos api]: /v3/repos/#list-repositories-for-the-authenticated-user -[other user repos api]: /v3/repos/#list-repositories-for-a-user -[org repos api]: /v3/repos/#list-organization-repositories -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[repo issues api]: /v3/issues/#list-repository-issues +[user repos api]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[other user repos api]: /rest/reference/repos#list-repositories-for-a-user +[org repos api]: /rest/reference/repos#list-organization-repositories +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[repo issues api]: /rest/reference/issues#list-repository-issues [etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md index 01024967d4..352e080728 100644 --- a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md @@ -232,7 +232,7 @@ Vamos combinar algumas chamadas de API para obter uma _verdadeira_ representaç ] ``` -Como já temos uma lista de repositórios acima, vamos inspecionar cada um e chamar o [método da API para listar a linguagem][language API]: +Since we already have a list of repositories above, let's inspect each one, and call [the language listing API method][language API]: ``` ruby repos.each do |repo| @@ -264,7 +264,7 @@ end language_bytes = [ :name => "language_bytes", :elements => language_byte_count] ``` -(Para obter mais informações sobre um mapa de árvore do D3, confira [este tutorial simples][language API].) +(For more information on D3 tree map magic, check out [this simple tutorial][language API].) Para concluir, passamos esta informação JSON para o mesmo modelo de ERB: @@ -333,7 +333,7 @@ Et voila! São lindos retângulos que contém suas linguagens de repositório, c [Octokit]: https://github.com/octokit/octokit.rb [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ [D3 treemap]: http://bl.ocks.org/mbostock/4063582 -[language API]: /v3/repos/#list-repository-languages -[language API]: /v3/repos/#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs [new oauth application]: https://github.com/settings/applications/new diff --git a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md index aca133d682..62f617cdde 100644 --- a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md +++ b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md @@ -20,9 +20,9 @@ Neste guia, vamos fazer algumas chamadas para a API de pesquisa do {% data varia Para começar, é importante conhecer alguns fatos sobre o recebimento de itens paginados: -1. Diferentes chamadas de API respondem com diferentes padrões. Por exemplo, uma chamada para [Listar repositórios públicos](/v3/repos/#list-public-repositories) fornece itens paginados em conjuntos de 30, enquanto uma chamada para a API de Pesquisa do GitHub fornece itens em conjuntos de 100 +1. Diferentes chamadas de API respondem com diferentes padrões. Por exemplo, uma chamada para [Listar repositórios públicos](/rest/reference/repos#list-public-repositories) fornece itens paginados em conjuntos de 30, enquanto uma chamada para a API de Pesquisa do GitHub fornece itens em conjuntos de 100 2. Você pode especificar quantos itens receber (até um máximo de 100); mas -3. Por razões técnicas, nem todos os pontos de referência comportam-se da mesma forma. Por exemplo, os [eventos](/v3/activity/events/) não permitirão que você defina um máximo de itens a receber. Leia a documentação sobre como lidar com resultados paginados para pontos de extremidade específicos. +3. Por razões técnicas, nem todos os pontos de referência comportam-se da mesma forma. Por exemplo, os [eventos](/rest/reference/activity#events) não permitirão que você defina um máximo de itens a receber. Leia a documentação sobre como lidar com resultados paginados para pontos de extremidade específicos. As informações sobre paginação são fornecidas no [cabeçalho do link](http://tools.ietf.org/html/rfc5988) de uma chamada de API. Por exemplo, vamos fazer uma solicitação de curl para a API de pesquisa, para descobrir quantas vezes os projetos da Mozilla usam a frase `addClass`: @@ -201,7 +201,7 @@ puts "The prev page link is #{prev_page_href}" puts "The next page link is #{next_page_href}" ``` -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination [octokit.rb]: https://github.com/octokit/octokit.rb [personal token]: /articles/creating-an-access-token-for-command-line-use diff --git a/translations/pt-BR/content/rest/guides/working-with-comments.md b/translations/pt-BR/content/rest/guides/working-with-comments.md index 5f45b07f18..cdc00528b8 100644 --- a/translations/pt-BR/content/rest/guides/working-with-comments.md +++ b/translations/pt-BR/content/rest/guides/working-with-comments.md @@ -18,7 +18,7 @@ Cada um desses tipos de comentários passa por uma parte diferente da API de {% ### Comentários do Pull Request -Para acessar comentários em um Pull Request, você passará [pela API de Problemas][issues]. A princípio, isso pode parecer contraintuitivo. Mas depois que você entender que um Pull Request é apenas um problema com o código, faz sentido usar a API de problemas para criar comentários em um Pull Request. +To access comments on a Pull Request, you'll go through [the Issues API][issues]. A princípio, isso pode parecer contraintuitivo. Mas depois que você entender que um Pull Request é apenas um problema com o código, faz sentido usar a API de problemas para criar comentários em um Pull Request. Nós demonstraremos como buscar comentários de Pull Request criando um script do Ruby usando [Octokit.rb][octokit.rb]. Você também deverá criar um [token de acesso pessoal][personal token]. @@ -44,7 +44,7 @@ Aqui, estamos especificamente chamando a API de problemas para obter os comentá ### Comentários em uma linha de Pull Request -Na visualização de diferenças, você pode iniciar uma discussão sobre um aspecto específico de uma mudança singular feita dentro do Pull Request. Estes comentários ocorrem nas linhas individuais dentro de um arquivo alterado. A URL do ponto de extremidade para esta discussão vem da [API da revisão de pull request][PR Review API]. +Na visualização de diferenças, você pode iniciar uma discussão sobre um aspecto específico de uma mudança singular feita dentro do Pull Request. Estes comentários ocorrem nas linhas individuais dentro de um arquivo alterado. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API]. O código a seguir busca todos os comentários de pull request feitos em arquivos, dado um único número de pull request: @@ -70,7 +70,7 @@ Você perceberá que ele é incrivelmente semelhante ao exemplo acima. A diferen ### Comentários de commit -O último tipo de comentários ocorre especificamente nos commits individuais. Por esta razão, eles fazem uso de [a API de comentário de commit][commit comment API]. +O último tipo de comentários ocorre especificamente nos commits individuais. For this reason, they make use of [the commit comment API][commit comment API]. Para recuperar os comentários em um commit, você deverá usar o SHA1 do commit. Em outras palavras, você não usará nenhum identificador relacionado ao Pull Request. Aqui está um exemplo: @@ -97,8 +97,8 @@ Observe que esta chamada de API recuperará comentários de linha única, bem co [commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 [sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 [platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments -[issues]: /v3/issues/comments/ +[issues]: /rest/reference/issues#comments [personal token]: /articles/creating-an-access-token-for-command-line-use [octokit.rb]: https://github.com/octokit/octokit.rb -[PR Review API]: /v3/pulls/comments/ -[commit comment API]: /v3/repos/comments/#get-a-commit-comment +[PR Review API]: /rest/reference/pulls#comments +[commit comment API]: /rest/reference/repos#get-a-commit-comment diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md index b07b623809..18e13102ea 100644 --- a/translations/pt-BR/content/rest/overview/api-previews.md +++ b/translations/pt-BR/content/rest/overview/api-previews.md @@ -15,12 +15,12 @@ Pré-visualizações da API permitem que você experimente novas APIs e alteraç Durante o período de pré-visualização, poderemos alterar alguns recursos com base no feedback do desenvolvedor. Se fizermos alterações, iremos anunciá-las no [blogue do desenvolvedor](https://developer.github.com/changes/) sem aviso prévio. -Para acessar uma pré-visualização da API, você precisará fornecer um [tipo de mídia](/v3/media) personalizado no cabeçalho `Aceitar` para suas solicitações. A documentação dos recursos para cada pré-visualização especifica qual tipo de mídia personalizado deve ser fornecido. +Para acessar uma pré-visualização da API, você precisará fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar` para suas solicitações. A documentação dos recursos para cada pré-visualização especifica qual tipo de mídia personalizado deve ser fornecido. {% if currentVersion == "free-pro-team@latest" %} ### Migrações -Permite que você faça o download de repositórios da conta do usuário ou da organização do GitHub para revisar, fazer backup e [fazer a migração dos dados](/v3/migrations/) para {% data variables.product.prodname_ghe_server %}. +Permite que você faça o download de repositórios da conta do usuário ou da organização do GitHub para revisar, fazer backup e [fazer a migração dos dados](/rest/reference/migrations) para {% data variables.product.prodname_ghe_server %}. **Tipo de mídia personalizada:** `wyandotte-preview` **Anunciado em:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) {% endif %} @@ -33,7 +33,7 @@ Exerça um maior controle sobre as [implantações](/rest/reference/repos#deploy ### Reações -Gerencie as [reações](/v3/reactions/) de commits, problemas e comentários. +Gerencie as [reações](/rest/reference/reactions) de commits, problemas e comentários. **Tipo de mídia personalizado:** `squirrel-girl-preview` **Anunciado em:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Atualização em:** [ 2016-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)

@@ -42,7 +42,7 @@ Gerencie as [reações](/v3/reactions/) de commits, problemas e comentários. ### Linha do tempo -Obter uma [lista de eventos](/v3/issues/timeline/) para um problema ou pull request. +Obter uma [lista de eventos](/rest/reference/issues#timeline) para um problema ou pull request. **Tipo de mídia personalizada:** `mockingbird-preview` **Anunciado em:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) @@ -72,7 +72,7 @@ Gerencie as [integrações](/early-access/integrations/) através da API. ### Projetos -Gerencie [projetos](/v3/projects/). +Gerencie [projetos](/rest/reference/projects). **Tipo de mídia personalizada:** `inertia-preview` **Anunciado em:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Atualização em:** [ 2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)

@@ -80,7 +80,7 @@ Gerencie [projetos](/v3/projects/). ### Pesquisa de commit -[Pesquisa commits](/v3/search/). +[Pesquisa commits](/rest/reference/search). **Tipo de mídia personalizada:** `cloak-preview` **Anunciado em:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) @@ -89,7 +89,7 @@ Gerencie [projetos](/v3/projects/). ### Bloqueio de usuário -Os usuários podem [bloquear outros usuários](/v3/users/blocking/). As organizações também podem [bloquear usuários](/v3/orgs/blocking/). +Os usuários podem [bloquear outros usuários](/rest/reference/users#blocking). As organizações também podem [bloquear usuários](/rest/reference/orgs#blocking). **Tipo de mídia personalizado:** `giant-sentry-fist-preview` **Anunciado em:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Atualização 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Atualização 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) @@ -99,7 +99,7 @@ Os usuários podem [bloquear outros usuários](/v3/users/blocking/). As organiza ### Tópicos do repositório -Ver uma lista dos [tópicos do repositório](/articles/about-topics/) em [chamadas](/v3/repos/) que retornam resultados do repositório. +Ver uma lista dos [tópicos do repositório](/articles/about-topics/) em [chamadas](/rest/reference/repos) que retornam resultados do repositório. **Tipo de mídia personalizada:** `mercy-preview` **Anunciado em:** [2017-01-31](https://github.com/blog/2309-introducing-topics) @@ -107,7 +107,7 @@ Ver uma lista dos [tópicos do repositório](/articles/about-topics/) em [chamad ### Códigos de conduta -Veja todos os [códigos de conduta](/v3/codes_of_conduct) ou obtenha qual código de conduta um repositório tem atualmente. +Veja todos os [códigos de conduta](/rest/reference/codes-of-conduct) ou obtenha qual código de conduta um repositório tem atualmente. **Tipo de mídia personalizado:** `scarlet-witch-preview` @@ -116,7 +116,7 @@ Veja todos os [códigos de conduta](/v3/codes_of_conduct) ou obtenha qual códig ### Equipes aninhadas -Inclua o conteúdo aninhado das cargas da [equipe](/v3/teams/). +Inclua o conteúdo aninhado das cargas da [equipe](/rest/reference/teams). **Tipo de mídia personalizada:** `hellcat-preview` **Anunciado em:** [2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) @@ -139,7 +139,7 @@ Habilita [webhooks globais](/rest/reference/enterprise-admin#global-webhooks/) p ### Transferência de repositório -Transfira um [repositório](/v3/repos/) para uma organização ou usuário. +Transfira um [repositório](/rest/reference/repos) para uma organização ou usuário. **Tipo de mídia personalizada:** `nightshade-preview` **Anunciado em:** [2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) @@ -150,7 +150,7 @@ Transfira um [repositório](/v3/repos/) para uma organização ou usuário. ### Adicionar motivo do bloqueio -Agora você pode adicionar um motivo ao[bloquear um problema](/v3/issues/#lock-an-issue). +Agora você pode adicionar um motivo ao[bloquear um problema](/rest/reference/issues#lock-an-issue). **Tipo de mídia personalizada:** `sailor-v-preview` **Anunciado em:** [2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) @@ -160,7 +160,7 @@ Agora você pode adicionar um motivo ao[bloquear um problema](/v3/issues/#lock-a ### Exigir commits assinados -Agora você pode usar a API para gerenciar a configuração para [exigir commits assinados em branches protegidos](/v3/repos/branches). +Agora você pode usar a API para gerenciar a configuração para [exigir commits assinados em branches protegidos](/rest/reference/repos#branches). **Tipo de mídia personalizada:** `zzzax-preview` **Anunciado em:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) @@ -168,7 +168,7 @@ Agora você pode usar a API para gerenciar a configuração para [exigir commits ### Exigir múltiplas revisões de aprovação -Agora você pode [exigir múltiplas revisões de aprovação](/v3/repos/branches) para um pull request usando a API. +Agora você pode [exigir múltiplas revisões de aprovação](/rest/reference/repos#branches) para um pull request usando a API. **Tipo de mídia personalizada:** `luke-cage-preview` **Anunciado em:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) @@ -177,7 +177,7 @@ Agora você pode [exigir múltiplas revisões de aprovação](/v3/repos/branches ### Recuperar informações do hovercard -Recuperar informações do [hovercard de alguém](/v3/users/#get-contextual-information-for-a-user). +Recuperar informações do [hovercard de alguém](/rest/reference/users#get-contextual-information-for-a-user). **Tipo de mídia personalizada:** `hagar-preview` **Anunciado:** [2018-03-21](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) @@ -188,7 +188,7 @@ Recuperar informações do [hovercard de alguém](/v3/users/#get-contextual-info ### Verificar execuções e a API de conjuntos de verificações -Permite que um aplicativo GitHub execute verificações externas no código de um repositório. Veja as [execuções de verificação](/v3/checks/runs/) e [Conjuntos de verificação](/v3/checks/suites/) das APIs para obter mais informações. +Permite que um aplicativo GitHub execute verificações externas no código de um repositório. Veja as [execuções de verificação](/rest/reference/checks#runs) e [Conjuntos de verificação](/rest/reference/checks#suites) das APIs para obter mais informações. **Tipo de mídia personalizada:** `antiope-preview` **Anunciado:** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) @@ -210,7 +210,7 @@ Quando uma instância do {% data variables.product.prodname_ghe_server %} estive ### Detalhes do cartão de projeto -As respostas da API REST para [eventos de problemas](/v3/issues/events/) e [eventos da linha do tempo de problemas](/v3/issues/timeline/) agora retornam o campo `project_card` para eventos relacionados ao projeto. +As respostas da API REST para [eventos de problemas](/rest/reference/issues#events) e [eventos da linha do tempo de problemas](/rest/reference/issues#timeline) agora retornam o campo `project_card` para eventos relacionados ao projeto. **Tipo de mídia personalizada:** `starfox-preview` **Anunciado:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) @@ -238,7 +238,7 @@ Agora você pode atualizar o ambiente `` de um [status de implantação](/rest/r ### Permissões de criação de repositório -Agora você pode configurar se os integrantes da organização podem criar repositórios e que tipos de repositórios podem criar. Consulte "[Atualizar uma organização](/v3/orgs/#update-an-organization)" para obter mais informações. +Agora você pode configurar se os integrantes da organização podem criar repositórios e que tipos de repositórios podem criar. Consulte "[Atualizar uma organização](/rest/reference/orgs#update-an-organization)" para obter mais informações. **Tipos de mídia personalizada:** `surtur-preview` **Anunciado:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) @@ -255,7 +255,7 @@ Agora você pode fornecer mais informações no GitHub para URLs vinculadas a do ### Pull requests de rascunho -Você pode usar a API do Pull Requests de rascunho e seus pontos de extremidade de [pull request](/v3/pulls/) para ver se um pull request está em estado rascunho. Para saber mais sobre pull requests, consulte "[Sobre pull requests](/articles/about-pull-requests/)". +Você pode usar a API do Pull Requests de rascunho e seus pontos de extremidade de [pull request](/rest/reference/pulls) para ver se um pull request está em estado rascunho. Para saber mais sobre pull requests, consulte "[Sobre pull requests](/articles/about-pull-requests/)". **Tipo de mídia personalizada:** `shadow-cat-preview` **Anunciado:** [2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) @@ -273,7 +273,7 @@ Você pode usar os novos pontos de extremidade no [API de páginas](/rest/refere ### Listar branches ou pull requests para um commit -Você pode usar dois novos pontos de extremidade na [API de commits](/v3/repos/commits/) para listar branches ou pull requests para um commit. +Você pode usar dois novos pontos de extremidade na [API de commits](/rest/reference/repos#commits) para listar branches ou pull requests para um commit. **Tipos de mídia personalizada:** `groot-preview` **Anunciado:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) @@ -282,7 +282,7 @@ Você pode usar dois novos pontos de extremidade na [API de commits](/v3/repos/c ### Desinstalar um aplicativo do GitHub -Agora os proprietários dos aplicativos GitHub podem desinstalar um aplicativo usando a [API de aplicativos](/v3/apps/#delete-an-installation-for-the-authenticated-app). +Agora os proprietários dos aplicativos GitHub podem desinstalar um aplicativo usando a [API de aplicativos](/rest/reference/apps#delete-an-installation-for-the-authenticated-app). **Tipos de mídia personalizada:** `gambit-preview` @@ -292,7 +292,7 @@ Agora os proprietários dos aplicativos GitHub podem desinstalar um aplicativo u ### Habilitar ou desabilitar alertas de vulnerabilidade para um repositório -Você pode usar dois novos pontos de extremidade na [API de Repositórios](/v3/repos/) para habilitar ou desabilitar os alertas de vulnerabilidade. +Você pode usar dois novos pontos de extremidade na [API de Repositórios](/rest/reference/repos) para habilitar ou desabilitar os alertas de vulnerabilidade. **Tipos de mídia personalizada:** `dorian-preview` **Anunciado:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) @@ -300,7 +300,7 @@ Você pode usar dois novos pontos de extremidade na [API de Repositórios](/v3/r ### Atualizar um branch de pull request -Você pode usar um novo ponto de extremidade para [atualizar um branch de pull request](/v3/pulls/#update-a-pull-request-branch) com alterações do HEAD do branch upstream. +Você pode usar um novo ponto de extremidade para [atualizar um branch de pull request](/rest/reference/pulls#update-a-pull-request-branch) com alterações do HEAD do branch upstream. **Tipos de mídia personalizada:** `lidian-preview` **Anunciado:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) @@ -309,7 +309,7 @@ Você pode usar um novo ponto de extremidade para [atualizar um branch de pull r ### Habilitar ou desabilitar correções de segurança automatizadas -Você pode usar um novo conjunto de pontos de extremidade para [habilitar e desabilitar as correções de segurança automatizadas](/v3/repos/#enable-automated-security-fixes). +Você pode usar um novo conjunto de pontos de extremidade para [habilitar e desabilitar as correções de segurança automatizadas](/rest/reference/repos#enable-automated-security-fixes). **Tipo de mídia personalizada:** `london-preview` **Anunciado:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) @@ -319,7 +319,7 @@ Você pode usar um novo conjunto de pontos de extremidade para [habilitar e desa ### Criar e usar modelos de repositório -Você pode usar um novo ponto de extremidade para [Criar um repositório usando um modelo](/v3/repos/#create-a-repository-using-a-template) e [Criar um repositório para o usuário autenticado](/v3/repos/#create-a-repository-for-the-authenticated-user) que é um repositório de modelo, definindo o parâmetro `is_template` como `verdadeiro`. [Obter um repositório](/v3/repos/#get-a-repository) para verificar se ele é definido como um repositório de modelo usando a chave `is_template`. +Você pode usar um novo ponto de extremidade para [Criar um repositório usando um modelo](/rest/reference/repos#create-a-repository-using-a-template) e [Criar um repositório para o usuário autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) que é um repositório de modelo, definindo o parâmetro `is_template` como `verdadeiro`. [Obter um repositório](/rest/reference/repos#get-a-repository) para verificar se ele é definido como um repositório de modelo usando a chave `is_template`. **Tipos de mídia personalizada:** `baptiste-preview` **Anunciado:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) @@ -328,7 +328,7 @@ Você pode usar um novo ponto de extremidade para [Criar um repositório usando ### Novos pontos de extremidade da API de aplicativos OAuth -Você pode gerenciar os tokens de forma mais segura para aplicativos OAuth usando os tokens OAuth como parâmetros de entrada em vez dos parâmetros de caminho com os novos pontos de extremidade da [API dos aplicativos OAuth](/v3/apps/oauth_applications/). +Você pode gerenciar os tokens de forma mais segura para aplicativos OAuth usando os tokens OAuth como parâmetros de entrada em vez dos parâmetros de caminho com os novos pontos de extremidade da [API dos aplicativos OAuth](/rest/reference/apps#oauth-applications). **Tipos de mídia personalizada:** `doutor-strange-preview` **Anunciado:** [2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) @@ -339,7 +339,7 @@ Você pode gerenciar os tokens de forma mais segura para aplicativos OAuth usand ### Novo parâmetro de visibilidade para a API de repositórios -Você pode definir e recuperar a visibilidade de um repositório na [API de repositórios](/v3/repos/). +Você pode definir e recuperar a visibilidade de um repositório na [API de repositórios](/rest/reference/repos). **Tipos de mídia personalizada:** `nebula-preview` **Anunciado:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) diff --git a/translations/pt-BR/content/rest/overview/media-types.md b/translations/pt-BR/content/rest/overview/media-types.md index 1d2b6ce905..87ce065372 100644 --- a/translations/pt-BR/content/rest/overview/media-types.md +++ b/translations/pt-BR/content/rest/overview/media-types.md @@ -21,7 +21,7 @@ Os tipos mais básicos de mídia que a API suporta são: application/json application/vnd.github+json -Nenhum desses parâmetros especifica a versão [][versions]. Portanto, você sempre receberá a representação atual do JSON padrão atual de recursos. +Neither of these specify a [version][versions], so you will always get the current default JSON representation of resources. {% note %} @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### Propriedades do texto do comentário -O texto de um comentário pode ser escrito no [Linguagem de Markdown enriquecido][gfm], [problemas](/v3/issues/), [comentários do problema](/v3/issues/comments/), [comentários de pull request](/v3/pulls/comments/) e as APIs dos [comentários de gist](/v3/gists/comments/) aceitam todos esses mesmos tipos de mídia: +The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: #### Sem processar @@ -85,7 +85,7 @@ Retorna as representações de HTML e texto sem processar. A resposta incluirá ### Propriedades do Git blob -Os seguintes tipos de mídia são permitidos ao [receber um blob](/v3/git/blobs/#get-a-blob): +The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): #### JSON @@ -102,7 +102,7 @@ Retorna os dados do blob sem processamento. ### Commits, comparação de commit e pull requests -A [API de commits](/v3/repos/commits/) e [API de pull requests](/v3/pulls/) são compatíveis com os formatos [diff][git-diff] e [patch][git-patch]: +The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: #### diff @@ -147,5 +147,4 @@ O conteúdo do gist é codificado em base64 antes de ser enviado. Isso pode ser [gfm]: http://github.github.com/github-flavored-markdown/ [git-diff]: http://git-scm.com/docs/git-diff [git-patch]: http://git-scm.com/docs/git-format-patch -[versions]: /v3/versions -[versions]: /v3/versions +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/pt-BR/content/rest/overview/other-authentication-methods.md b/translations/pt-BR/content/rest/overview/other-authentication-methods.md index ffab348d3f..c3fa745650 100644 --- a/translations/pt-BR/content/rest/overview/other-authentication-methods.md +++ b/translations/pt-BR/content/rest/overview/other-authentication-methods.md @@ -37,19 +37,29 @@ $ curl -u username:token {% data variables.product.api_url_pre Esta abordagem é útil se suas ferramentas são compatíveis apenas com a Autenticação Básica, mas você quer aproveitar os recursos de segurança do token de acesso do OAuth. -{% if enterpriseServerVersions contains currentVersion %} #### Por meio do nome de usuário e senha -{% data reusables.apps.deprecating_password_auth %} +{% if currentVersion == "free-pro-team@latest" %} -Para usar a Autenticação Básica com a API do {% data variables.product.product_name %}, basta enviar o nome de usuário e senha associados à conta. +{% note %} + +**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% data variables.product.prodname_dotcom %} API with an API token, such as an OAuth access token, GitHub App installation access token, or personal access token, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)." + +{% endnote %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +To use Basic Authentication with the +{% data variables.product.product_name %} API, simply send the username and +password associated with the account. Por exemplo, se você estiver acessando a API via [cURL][curl], o comando a seguir faria a sua autenticação se substituísse `` pelo seu nome de usuário de {% data variables.product.product_name %}. (cURL solicitará que você insira a senha.) ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -Se você tem a autenticação de dois fatores ativada, certifique-se de entender como [funciona com a autenticação de dois fatores](/v3/auth/#working-with-two-factor-authentication). +Se você tem a autenticação de dois fatores ativada, certifique-se de entender como [funciona com a autenticação de dois fatores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). {% endif %} @@ -88,14 +98,13 @@ O valor das `organizações` é uma lista de ID de organizações separada por v {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ### Trabalhar com autenticação de dois fatores -{% data reusables.apps.deprecating_password_auth %} - -Quando você tem a autenticação de dois fatores habilitada, a [Autenticação básica](#basic-authentication) para _a maioria dos_ pontos de extremidade na API REST exige que você use um token de acesso pessoal ou token do OAuth em vez de seu nome de usuário e senha. - -Você pode gerar um novo token de acesso pessoal {% if currentVersion == "free-pro-team@latest" %}com [configurações do desenvolvedor de {% data variables.product.product_name %}](https://github.com/settings/tokens/new){% endif %} ou usar o ponto de extremidade [Criar uma nova autorização][create-access]" na API de Autorização do OAuth para gerar um novo token do OAuth. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Em seguida, você usaria esses tokens para [efetuar a autenticação usando o token do OAuth][oauth-auth] com a API do GitHub. A única vez que você precisa efetuar a autenticação com seu nome de usuário e senha é quando você cria seu token do OAuth ou usa a API de Autorização do OAuth. +When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a personal access token{% if enterpriseServerVersions contains currentVersion %} or OAuth token instead of your username and password{% endif %}. +You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% if enterpriseServerVersions contains currentVersion %} or with the "\[Create a new authorization\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% data variables.product.prodname_dotcom %} API.{% if enterpriseServerVersions contains currentVersion %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} +{% endif %} +{% if enterpriseServerVersions contains currentVersion %} #### Usar a API de Autorização do OAuth com autenticação de dois fatores Ao fazer chamadas para a API de Autorizações do OAuth, Autenticação básica exigirá que você use uma senha única (OTP) e seu nome de usuário e senha em vez de tokens. Ao tentar efetuar a autenticação com a API de Autorizações do OAuth, o servidor irá responder com `401 Unauthorized` e um desses cabeçalhos para informar que você precisa de um código de autenticação de dois fatores: @@ -114,10 +123,9 @@ $ curl --request POST \ ``` {% endif %} -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization [curl]: http://curl.haxx.se/ -[oauth-auth]: /v3/#authentication +[oauth-auth]: /rest#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -[user-issues]: /v3/issues/#list-issues-assigned-to-the-authenticated-user +[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index 0f685dbf91..30cc142a97 100644 --- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md @@ -1,6 +1,6 @@ --- -title: Recursos na API REST -intro: 'Aprenda a navegar nos recursos fornecidos pela API de {% data variables.product.prodname_dotcom %}.' +title: Resources in the REST API +intro: 'Learn how to navigate the resources provided by the {% data variables.product.prodname_dotcom %} API.' redirect_from: - /rest/initialize-the-repo/ versions: @@ -10,24 +10,25 @@ versions: --- -Isso descreve os recursos que formam a API REST oficial de {% data variables.product.product_name %}. Em caso de problema ou solicitação, entre em contato com {% data variables.contact.contact_support %}. +This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}. -### Versão atual +### Current version -Por padrão, todas as solicitações para `{% data variables.product.api_url_code %}` recebem a versão **v3** [](/v3/versions) da API REST. Nós incentivamos que você a [solicite explicitamente esta versão por meio do cabeçalho `Aceitar`](/v3/media/#request-specific-version). +By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API. +We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version). Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -Para obter informações sobre a API do GraphQL do GitHub, consulte a [documentação v4](/v4). Para obter informações sobre migração para o GraphQL, consulte "[Fazendo a migração do REST](/v4/guides/migrating-from-rest/)". +For information about GitHub's GraphQL API, see the [v4 documentation](/graphql). For information about migrating to GraphQL, see "[Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql)." {% endif %} -### Esquema +### Schema -{% if currentVersion == "free-pro-team@latest" %}Todo o acesso à API é feito por meio de HTTPS, e{% else %}A API é{% endif %} acessada a partir de `{% data variables.product.api_url_code %}`. Todos os dados são -enviados e recebidos como JSON. +{% if currentVersion == "free-pro-team@latest" %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`. All data is +sent and received as JSON. ```shell $ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs @@ -48,43 +49,55 @@ $ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs > X-Content-Type-Options: nosniff ``` -Os campos em branco são incluídos como `null` em vez de serem omitidos. +Blank fields are included as `null` instead of being omitted. -Todos os registros de tempo são retornados no formato ISO 8601: +All timestamps return in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ -Para obter mais informações sobre fusos horários nos registros de tempo, consulte [esta seção](#timezones). +For more information about timezones in timestamps, see [this section](#timezones). -#### Apresentações resumidas +#### Summary representations -Ao buscar uma lista de recursos, a resposta inclui um _subconjunto_ dos atributos para esse recurso. Esta é a representação "resumo" do recurso. (Alguns atributos são computacionalmente caros para a API fornecer. Por razões de desempenho, a representação resumida exclui esses atributos. Para obter esses atributos, busque a representação "detalhada".) +When you fetch a list of resources, the response includes a _subset_ of the +attributes for that resource. This is the "summary" representation of the +resource. (Some attributes are computationally expensive for the API to provide. +For performance reasons, the summary representation excludes those attributes. +To obtain those attributes, fetch the "detailed" representation.) -**Exemplo**: ao receber uma lista de repositórios, você recebe a representação resumida de cada repositório. Aqui, buscamos a lista de repositórios pertencentes a à organização do [octokit](https://github.com/octokit): +**Example**: When you get a list of repositories, you get the summary +representation of each repository. Here, we fetch the list of repositories owned +by the [octokit](https://github.com/octokit) organization: GET /orgs/octokit/repos -#### Representações detalhadas +#### Detailed representations -Ao buscar um recurso individual, a resposta normalmente inclui _todos os_ atributos para esse recurso. Esta é a representação "detalhada" do recurso. (Note que a autorização por vezes influencia o valor de detalhes incluído na representação.) +When you fetch an individual resource, the response typically includes _all_ +attributes for that resource. This is the "detailed" representation of the +resource. (Note that authorization sometimes influences the amount of detail +included in the representation.) -**Exemplo**: ao receber um repositório individual, você recebe a representação detalhada do repositório. Aqui, nós buscamos o repositório [octokit/octokit.rb](https://github.com/octokit/octokit.rb): +**Example**: When you get an individual repository, you get the detailed +representation of the repository. Here, we fetch the +[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository: GET /repos/octokit/octokit.rb -A documentação fornece um exemplo de resposta para cada método da API. O exemplo da resposta ilustra todos os atributos retornados por esse método. +The documentation provides an example response for each API method. The example +response illustrates all attributes that are returned by that method. -### Autenticação +### Authentication {% if currentVersion == "github-ae@latest" %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places. This is to prevent the accidental leakage of private repositories to unauthorized users. -#### Autenticação básica +#### Basic authentication ```shell $ curl -u "username" {% data variables.product.api_url_pre %} ``` -#### Token do OAuth2 (enviado em um cabeçalho) +#### OAuth2 token (sent in a header) ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} @@ -92,11 +105,11 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. {% note %} -Observação: O GitHub recomenda enviar tokens do OAuth usando o cabeçalho de autorização. +Note: GitHub recommends sending OAuth tokens using the Authorization header. {% endnote %} -Leia [mais sobre o OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications. +Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} #### OAuth2 key/secret @@ -107,20 +120,20 @@ Leia [mais sobre o OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos' ``` -Usar o seu `client_id` e `client_secret` _ não_ autenticam você como usuário. Isso apenas irá identificar o seu aplicativo OAuth para aumentar o seu limite de taxa. As permissões só são concedidas a usuários, não aplicativos, e você só obterá dados que um usuário não autenticado visualizaria. Por este motivo, você só deve usar a chave/segredo OAuth2 em cenários de servidor para servidor. Não compartilhe o segredo do cliente do aplicativo OAuth com os seus usuários. +Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth application to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth application's client secret to your users. -Você não conseguirá efetuar a autenticação usando sua chave e segredo do OAuth2 enquanto estiver no modo privado e essa tentativa de autenticação irá retornar `401 Unauthorized`. Para obter mais informações, consulte "[Habilitar o modo privado](/enterprise/admin/installation/enabling-private-mode)". +You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/enterprise/admin/installation/enabling-private-mode)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} -Leia [Mais informações sobre limitação da taxa não autenticada](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). {% endif %} -#### Falha no limite de login +#### Failed login limit -A autenticação com credenciais inválidas retornará `401 Unauthorized`: +Authenticating with invalid credentials will return `401 Unauthorized`: ```shell $ curl -i {% data variables.product.api_url_pre %} -u foo:bar @@ -132,204 +145,219 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar > } ``` -Após detectar várias solicitações com credenciais inválidas em um curto período de tempo, a API rejeitará temporariamente todas as tentativas de autenticação para esse usuário (incluindo aquelas com credenciais válidas) com `403 Forbidden`: +After detecting several requests with invalid credentials within a short period, +the API will temporarily reject all authentication attempts for that user +(including ones with valid credentials) with `403 Forbidden`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -u valid_username:valid_password +$ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} +-u valid_username:valid_token {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u valid_username:valid_password {% endif %} > HTTP/1.1 403 Forbidden - > { > "message": "Maximum number of login attempts exceeded. Please try again later.", > "documentation_url": "{% data variables.product.doc_url_pre %}/v3" > } ``` -### Parâmetros +### Parameters -Muitos métodos de API tomam parâmetros opcionais. Para solicitações tipo `GET`, todos os parâmetros não especificados como um segmento no caminho podem ser passados como um parâmetro de string de consulta de HTTP: +Many API methods take optional parameters. For `GET` requests, any parameters not +specified as a segment in the path can be passed as an HTTP query string +parameter: ```shell $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed" ``` -Neste exemplo, os valores 'vmg' e 'redcarpet' são fornecidos para os parâmetros `:owner` e `:repo` no caminho enquanto `:state` é passado na string da consulta. +In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner` +and `:repo` parameters in the path while `:state` is passed in the query +string. -Para solicitações de `POST`, `PATCH`, `PUT`e `EXCLUIR`, os parâmetros não incluídos na URL devem ser codificados como JSON com um Content-Type de 'application/json': +For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON +with a Content-Type of 'application/json': ```shell $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product.api_url_pre %}/authorizations ``` -### Ponto de extremidade raiz +### Root endpoint -Você pode emitir uma solicitação `GET` para o ponto de extremidade de raiz para obter todas as categorias do ponto de extremidade com a qual a API REST é compatível: +You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports: ```shell -$ curl {% if currentVersion == "github-ae@latest" %}-u username:token {% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}-u username:password {% endif %}{% data variables.product.api_url_pre %} +$ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} +-u username:token {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u username:password {% endif %}{% data variables.product.api_url_pre %} ``` -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +### GraphQL global node IDs -{% note %} +See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. -**Observação:** Por {% data variables.product.prodname_ghe_server %}, [como em todos os outros pontos de extremidade](/v3/enterprise-admin/#endpoint-urls), você deverá passar seu nome de usuário e senha. +### Client errors -{% endnote %} +There are three possible types of client errors on API calls that +receive request bodies: -{% endif %} +1. Sending invalid JSON will result in a `400 Bad Request` response. -### IDs de nós globais do GraphQL + HTTP/1.1 400 Bad Request + Content-Length: 35 -Consulte o guia em "[Usar IDs do nó globais ](/v4/guides/using-global-node-ids)" para obter informações detalhadas sobre como encontrar `node_id`s através da API REST e usá-los em operações do GraphQL. + {"message":"Problems parsing JSON"} -### Erros do cliente +2. Sending the wrong type of JSON values will result in a `400 Bad + Request` response. -Há três tipos possíveis de erros de cliente na chamadas da API que recebem textos: + HTTP/1.1 400 Bad Request + Content-Length: 40 -1. O envio de um JSON inválido resultará em uma resposta 400 Bad Request`.

+ {"message":"Body should be a JSON object"} -
 HTTP/1.1 400 Bad Request
- Content-Length: 35
+3. Sending invalid fields will result in a `422 Unprocessable Entity`
+   response.
 
- {"message":"Problems parsing JSON"}
-`
+ HTTP/1.1 422 Unprocessable Entity + Content-Length: 149 -2 + { + "message": "Validation Failed", + "errors": [ + { + "resource": "Issue", + "field": "title", + "code": "missing_field" + } + ] + } -Enviar o tipo incorreto de valores do JSON resultará em uma resposta `400 Bad -Request`. - - HTTP/1.1 400 Bad Request - Content-Length: 40 - - {"message":"Body should be a JSON object"} +All error objects have resource and field properties so that your client +can tell what the problem is. There's also an error code to let you +know what is wrong with the field. These are the possible validation error +codes: -3 +Error code name | Description +-----------|-----------| +`missing` | A resource does not exist. +`missing_field` | A required field on a resource has not been set. +`invalid` | The formatting of a field is invalid. Review the documentation for the for more specific information. +`already_exists` | Another resource has the same value as this field. This can happen in resources that must have some unique key (such as label names). +`unprocessable` | The inputs provided were invalid. -O envio de campos inválidos resultará em uma resposta `422 Unprocessable Entity`. - - HTTP/1.1 422 Unprocessable Entity - Content-Length: 149 - - { - "message": "Validation Failed", - "errors": [ - { - "resource": "Issue", - "field": "title", - "code": "missing_field" - } - ] - } - +Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error. -Todos objetos de erro têm propriedades de recurso e campo para que seu cliente possa dizer qual é o problema. Também há um código de erro para informar o que há de errado com o campo. Estes são os possíveis códigos de validação: +### HTTP redirects -| Nome do código de erro | Descrição | -| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| `missing` | Um recurso não existe. | -| `missing_field` | Não foi definido um campo obrigatório em um recurso. | -| `invalid` | Formatação de um campo é inválida. Revise a documentação para obter informações mais específicas. | -| `already_exists` | Outro recurso tem o mesmo valor que este campo. Isso pode acontecer em recursos que precisam ter alguma chave única (como nomes de etiqueta). | -| `unprocessable` | As entradas fornecidas eram inválidas. | +API v3 uses HTTP redirection where appropriate. Clients should assume that any +request may result in a redirection. Receiving an HTTP redirection is *not* an +error and clients should follow that redirect. Redirect responses will have a +`Location` header field which contains the URI of the resource to which the +client should repeat the requests. -Os recursos também podem enviar erros de validação personalizados (em que o `código` é `personalizado`). Os erros personalizados sempre terão um campo de `mensagem` que descreve o erro e a maioria dos erros também incluirá um campo de `documentation_url` que aponta para algum conteúdo que pode ajudá-lo a resolver o erro. +Status Code | Description +-----------|-----------| +`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI. +`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests. -### Redirecionamentos HTTP +Other redirection status codes may be used in accordance with the HTTP 1.1 spec. -API v3 usa redirecionamento HTTP quando apropriado. Os clientes devem assumir que qualquer solicitação pode resultar em redirecionamento. Receber um redirecionamento de HTTP *não* é um erro e os clientes devem seguir esse redirecionamento. As respostas de redirecionamento terão um campo do cabeçalho do tipo `Localização` que contém o URI do recurso ao qual o cliente deve repetir as solicitações. +### HTTP verbs -| Código de status | Descrição | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `301` | Redirecionamento permanente. O URI que você usou para fazer a solicitação foi substituído pelo especificado no campo do cabeçalho `Localização`. Este e todas as solicitações futuras deste recurso devem ser direcionadas para o novo URI. | -| `302`, `307` | Redirecionamento temporário. A solicitação deve ser repetida literalmente para o URI especificado no campo de cabeçalho `Localização`, mas os clientes devem continuar a usar o URI original para solicitações futuras. | +Where possible, API v3 strives to use appropriate HTTP verbs for each +action. -Outros códigos de status de redirecionamento podem ser usados de acordo com a especificação HTTP 1.1. +Verb | Description +-----|----------- +`HEAD` | Can be issued against any resource to get just the HTTP header info. +`GET` | Used for retrieving resources. +`POST` | Used for creating resources. +`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A PATCH request may accept one or more of the attributes to update the resource. PATCH is a relatively new and uncommon HTTP verb, so resource endpoints also accept `POST` requests. +`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero. +`DELETE` |Used for deleting resources. -### Verbos HTTP +### Hypermedia -Quando possível, a API v3 se esforça para usar verbos HTTP apropriados para cada ação. +All resources may have one or more `*_url` properties linking to other +resources. These are meant to provide explicit URLs so that proper API clients +don't need to construct URLs on their own. It is highly recommended that API +clients use these. Doing so will make future upgrades of the API easier for +developers. All URLs are expected to be proper [RFC 6570][rfc] URI templates. -| Verbo | Descrição | -| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `HEAD` | Pode ser emitido contra qualquer recurso para obter apenas as informações de cabeçalho HTTP. | -| `GET` | Usado para recuperar recursos. | -| `POST` | Usado para criar recursos. | -| `PATCH` | Usado para atualizar recursos com dados parciais do JSON. Por exemplo, um recurso de um problema tem atributos de `título` e `texto`. Uma solicitação de PATCH pode aceitar um ou mais dos atributos para atualizar o recurso. PATCH é um verbo HTTP relativamente novo e incomum. Portanto, os pontos de extremidade de recursos também aceitam solicitações de `POST`. | -| `PUT` | Usado para substituir recursos ou coleções. Para as solicitações de `PUT` sem atributo de `texto`, certifique-se de definir o cabeçalho `Content-Length` como zero. | -| `DELETE` | Usado para excluir recursos. | - -### Hipermídia - -Todos os recursos podem ter uma ou mais propriedades `*_url` vinculando outros recursos. Estes tem o objetivo de fornecer URLs explícitas para que os clientes API apropriados não precisem construir URLs por conta própria. É altamente recomendável que os clientes da API os utilizem. Fazer isso tornará as futuras atualizações da API mais fáceis para os desenvolvedores. Espera-se que todas as URLs sejam modelos de URI [RFC 6570][rfc] adequados. - -Então você pode expandir estes modelos usando algo como o [uri_template][uri] gem: +You can then expand these templates using something like the [uri_template][uri] +gem: >> tmpl = URITemplate.new('/notifications{?since,all,participating}') >> tmpl.expand => "/notifications" - + >> tmpl.expand :all => 1 => "/notifications?all=1" - + >> tmpl.expand :all => 1, :participating => 1 => "/notifications?all=1&participating=1" -### Paginação +[rfc]: http://tools.ietf.org/html/rfc6570 +[uri]: https://github.com/hannesg/uri_template -Pedidos que retornam vários itens serão paginados para 30 itens por padrão. Você pode especificar mais páginas com o parâmetro `?page`. Para alguns recursos, você também pode definir um tamanho de página até 100 com o parâmetro `?per_page`. Observe que, por razões técnicas, nem todos os pontos de extremidade respeitam o parâmetro `?per_page`, veja [eventos](/v3/activity/events/) por exemplo. +### Pagination + +Requests that return multiple items will be paginated to 30 items by +default. You can specify further pages with the `?page` parameter. For some +resources, you can also set a custom page size up to 100 with the `?per_page` parameter. +Note that for technical reasons not all endpoints respect the `?per_page` parameter, +see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Observe que a numeração da página é baseada em 1 e que, ao omitir o parâmetro `?page`, retornará a primeira página. +Note that page numbering is 1-based and that omitting the `?page` +parameter will return the first page. -Para obter mais informações sobre paginação, confira nosso guia sobre [Passar com paginação][pagination-guide]. +For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. -#### Cabeçalho do link +#### Link header {% note %} -**Observação:** É importante formar chamadas com valores de cabeçalho de link, em vez de construir suas próprias URLs. +**Note:** It's important to form calls with Link header values instead of constructing your own URLs. {% endnote %} -O [cabeçalho do link](http://tools.ietf.org/html/rfc5988) inclui informações de paginação: +The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" -_O exemplo inclui uma quebra de linha para legibilidade._ +_The example includes a line break for readability._ -Este `Link` de resposta contém um ou mais links de relações de [hipermídia](/v3/#hypermedia), alguns dos quais podem exigir expansão como [modelos de URI](http://tools.ietf.org/html/rfc6570). +This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). -Os valores de `rel` possíveis são: +The possible `rel` values are: -| Nome | Descrição | -| --------- | ---------------------------------------------------------------- | -| `avançar` | A relação de link para a próxima página de resultados. | -| `last` | A relação de link para a última página de resultados. | -| `first` | A relação de link para a primeira página de resultados. | -| `prev` | A relação de link para a página de resultados anterior imediata. | +Name | Description +-----------|-----------| +`next` |The link relation for the immediate next page of results. +`last` |The link relation for the last page of results. +`first` |The link relation for the first page of results. +`prev` |The link relation for the immediate previous page of results. -### Limite de taxa +### Rate limiting -Para solicitações de API que usam a Autenticação Básica ou OAuth, você pode criar até 5.000 solicitações por hora. As solicitações de autenticação são associadas ao usuário autenticado, independentemente de [Autenticação Básica](#basic-authentication) ou [um token do OAuth](#oauth2-token-sent-in-a-header) ter sido usado. Isto significa que todos os aplicativos OAuth autorizados por um usuário compartilham a mesma cota de 5.000 solicitações por hora quando eles são autenticados com diferentes tokens pertencentes ao mesmo usuário. +For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether [Basic Authentication](#basic-authentication) or [an OAuth token](#oauth2-token-sent-in-a-header) was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user. {% if currentVersion == "free-pro-team@latest" %} -Para usuários que pertencem a uma conta {% data variables.product.prodname_ghe_cloud %}, solicitações feitas usando um token OAuth para recursos pertencentes à mesma conta de {% data variables.product.prodname_ghe_cloud %} têm um aumento de 15.000 solicitações por hora no limite. +For users that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests made using an OAuth token to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 requests per hour. {% endif %} -Para solicitações não autenticadas, o limite de taxa permite até 60 solicitações por hora. Solicitações não autenticadas estão associadas ao endereço IP original, e não ao usuário que faz solicitações. +For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests. {% data reusables.enterprise.rate_limit %} -Observe que [a API de pesquisa tem regras de limite de taxa personalizadas](/v3/search/#rate-limit). +Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). -Os cabeçalhos HTTP retornados de qualquer solicitação de API mostram o seu status atual de limite de taxa: +The returned HTTP headers of any API request show your current rate limit status: ```shell $ curl -i {% data variables.product.api_url_pre %}/users/octocat @@ -341,20 +369,20 @@ $ curl -i {% data variables.product.api_url_pre %}/users/octocat > X-RateLimit-Reset: 1372700873 ``` -| Nome do Cabeçalho | Descrição | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-RateLimit-Limit` | O número máximo de solicitações que você pode fazer por hora. | -| `X-RateLimit-Remaining` | O número de solicitações restantes na janela de limite de taxa atual. | -| `X-RateLimit-Reset` | O tempo em que a janela de limite de taxa atual é redefinida em [segundos no tempo de computação de UTC](http://en.wikipedia.org/wiki/Unix_time). | +Header Name | Description +-----------|-----------| +`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour. +`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window. +`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time). -Se você precisar de outro formato de tempo, qualquer linguagem de programação moderna pode fazer o trabalho. Por exemplo, se você abrir o console em seu navegador, você pode facilmente obter o tempo de redefinição como um objeto de tempo do JavaScript. +If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object. ``` javascript new Date(1372700873 * 1000) // => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT) ``` -Se você exceder o limite de taxa, uma resposta do erro retorna: +If you exceed the rate limit, an error response returns: ```shell > HTTP/1.1 403 Forbidden @@ -370,11 +398,11 @@ Se você exceder o limite de taxa, uma resposta do erro retorna: > } ``` -Você pode [verificar o status do seu limite de taxa](/v3/rate_limit) sem a incorrer em uma consulta da API. +You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. -#### Aumentar o limite de taxa não autenticado para aplicativos OAuth +#### Increasing the unauthenticated rate limit for OAuth applications -Se o seu aplicativo OAuth precisar fazer chamadas não autenticadas com um limite de taxa mais alto, você poderá passar o ID e o segredo do cliente do seu aplicativo antes do encaminhamento de pontos de extremidade. +If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route. ```shell $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos @@ -388,21 +416,21 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %} {% note %} -**Observação:** Nunca compartilhe seu segredo de cliente com alguém ou o inclua no código do navegador do lado do cliente. Use o método mostrado aqui apenas para chamadas de servidor para servidor. +**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls. {% endnote %} -#### Manter-se dentro do limite de taxa +#### Staying within the rate limit -Se você exceder seu limite de taxa usando a Autenticação Básica ou OAuth, você poderá corrigir o problema armazenando respostas da API e usando [solicitações condicionais](#conditional-requests). +If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests). -#### Abusar dos limites de taxa +#### Abuse rate limits -A fim de fornecer serviço de qualidade no {% data variables.product.product_name %}, podem-se aplicar limites de taxa adicionais podem a algumas ações ao usar a API. Por exemplo, usar a API para criar rapidamente conteúdo, fazer sondagem de modo agressivo em vez de usar webhooks, fazer várias solicitações simultâneas ou solicitar repetidamente dados caros do ponto de vista computacional podem resultar na limitação da taxa de abuso. +In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in abuse rate limiting. -O abuso dos limites de taxa não são destinados a interferir no uso legítimo da API. Seus limites de taxa normais devem ser o único limite em que você deve focar. Para garantir que você está agindo como um bom cidadão da API, confira nossas [Diretrizes sobre práticas recomendadas](/guides/best-practices-for-integrators/). +Abuse rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/). -Se seu aplicativo acionar este limite de taxa, você receberá uma resposta informativa: +If your application triggers this rate limit, you'll receive an informative response: ```shell > HTTP/1.1 403 Forbidden @@ -417,17 +445,19 @@ Se seu aplicativo acionar este limite de taxa, você receberá uma resposta info {% if currentVersion == "free-pro-team@latest" %} -### Agente de usuário obrigatório +### User agent required -Todas as solicitações da API DEVEM incluir um cabeçalho válido de `User-Agent`. As requisições sem o cabeçalho do `User-Agent` serão rejeitadas. Pedimos que use seu nome de usuário de {% data variables.product.product_name %} ou o nome de seu aplicativo, para o valor do cabeçalho `User-Agent`. Isso nos permite entrar em contato com você, em caso de problemas. +All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent` +header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your +application, for the `User-Agent` header value. This allows us to contact you if there are problems. -Aqui está um exemplo: +Here's an example: ```shell User-Agent: Awesome-Octocat-App ``` -A cURL envia um cabeçalho válido do `User-Agent` por padrão. Se você fornecer um cabeçalho inválido de `User-Agent` via cURL (ou via um cliente alternativo), você receberá uma resposta `403 Forbidden`: +cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: ```shell $ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta @@ -442,15 +472,20 @@ $ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta {% endif %} -### Solicitações condicionais +### Conditional requests -A maioria das respostas retorna um cabeçalho de Etag`. Muitas respostas também retornam um cabeçalho Last-Modified`. Você pode usar os valores desses cabeçalhos para fazer solicitações subsequentes para esses recursos usando os cabeçalhos `If-None-Match` e `If-Modified-Desde`, respectivamente. Se o recurso não foi alterado, o servidor retornará `304 não modificado`. +Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values +of these headers to make subsequent requests to those resources using the +`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource +has not changed, the server will return a `304 Not Modified`. {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Observação**: Fazer uma solicitação condicional e receber uma resposta 304 não conta para o seu [Limite de Taxa](#rate-limiting). Portanto, recomendamos que você o utilize sempre que possível. +**Note**: Making a conditional request and receiving a 304 response does not +count against your [Rate Limit](#rate-limiting), so we encourage you to use it +whenever possible. {% endtip %} @@ -490,11 +525,16 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T > X-RateLimit-Reset: 1372700873 ``` -### Compartilhamento de recursos de origem cruzada +### Cross origin resource sharing -A API é compatível com Compartilhamento de Recursos de Origens Cruzadas (CORS) para solicitações de AJAX de qualquer origem. You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or [this intro](http://code.google.com/p/html5security/wiki/CrossOriginRequestSecurity) from the HTML 5 Security Guide. +The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from +any origin. +You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or +[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the +HTML 5 Security Guide. -Aqui está uma solicitação de exemplo enviada a partir de uma consulta em `http://exemplo.com`: +Here's a sample request sent from a browser hitting +`http://example.com`: ```shell $ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" @@ -503,7 +543,7 @@ Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval ``` -A solicitação pré-voo de CORS se parece com isso: +This is what the CORS preflight request looks like: ```shell $ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS @@ -515,9 +555,13 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra Access-Control-Max-Age: 86400 ``` -### Chamadas de retorno do JSON-P +### JSON-P callbacks -Você pode enviar um parâmetro `?callback` para qualquer chamada de GET para envolver os resultados em uma função JSON. Isso é normalmente usado quando os navegadores querem que incorporem {% data variables.product.product_name %} conteúdo em páginas da web, contornando problemas de de domínio cruzado. A resposta inclui a mesma saída de dados da API regular, mais as informações relevantes do cabeçalho de HTTP. +You can send a `?callback` parameter to any GET call to have the results +wrapped in a JSON function. This is typically used when browsers want +to embed {% data variables.product.product_name %} content in web pages by getting around cross domain +issues. The response includes the same data output as the regular API, +plus the relevant HTTP Header information. ```shell $ curl {% data variables.product.api_url_pre %}?callback=foo @@ -538,7 +582,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo > }) ``` -Você pode escrever um manipulador do JavaScript para processar o retorno de chamada. Aqui está um exemplo pequeno que você pode experimentar: +You can write a JavaScript handler to process the callback. Here's a minimal example you can try out: @@ -549,26 +593,28 @@ Você pode escrever um manipulador do JavaScript para processar o retorno de cha console.log(meta); console.log(data); } - + var script = document.createElement('script'); script.src = '{% data variables.product.api_url_code %}?callback=foo'; - + document.getElementsByTagName('head')[0].appendChild(script); - +

Open up your browser's console.

-Todos os cabeçalhos têm o mesmo valor d a string que os cabeçalhos de HTTP com uma exceção notável: Link. Cabeçalhos de link são pré-analisados para você e chegam como um array de tuplas de `[url, options]`. +All of the headers are the same String value as the HTTP Headers with one +notable exception: Link. Link headers are pre-parsed for you and come +through as an array of `[url, options]` tuples. -Um link que se parece com isto: +A link that looks like this: Link: ; rel="next", ; rel="foo"; bar="baz" -... será mostrado assim na saída da chamada de retorno: +... will look like this in the Callback output: ```json { @@ -590,40 +636,37 @@ Um link que se parece com isto: } ``` -### Fusos horários +### Timezones -Algumas solicitações que criam novos dados, como a criação de um novo commit, permitem que você forneça informações do fuso horário ao especificar ou marcas de tempo. Aplicamos as seguintes regras, por ordem de prioridade, para determinar as informações do fuso horário para chamadas de API. +Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for API calls. -* [Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) -* [Usar o cabeçalho `Time-Zone`](#using-the-time-zone-header) -* [Usar o último fuso horário conhecido para o usuário](#using-the-last-known-timezone-for-the-user) -* [Definir como padrão UTC sem outras informações de fuso horário](#defaulting-to-utc-without-other-timezone-information) +* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) +* [Using the `Time-Zone` header](#using-the-time-zone-header) +* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user) +* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information) -#### Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário +#### Explicitly providing an ISO 8601 timestamp with timezone information -Para chamadas de API que permitem que uma marca de tempo seja especificada, usamos essa marca de tempo exata. Um exemplo disso é a [API de Commits](/v3/git/commits). +For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits). -Essas marcas de tempo se parecem com `2014-02-27T15:05:06+01:00`. Veja também [este exemplo](/v3/git/commits/#example-input) para saber como essas marcas de tempo podem ser especificadas. +These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. -#### Usar o cabeçalho `Time-Zone` +#### Using the `Time-Zone` header -É possível fornecer um cabeçalho `Time-Zone` que define um fuso horário de acordo com a lista [ de nomes do banco de dados Olson](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). +It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). ```shell $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -Isso significa que geramos uma marca de tempo no momento em que sua chamada de API é feita no fuso horário que este cabeçalho define. Por exemplo, o [API de Conteúdo](/v3/repos/contents/) gera um commit do git para cada adição ou alteração e usa a hora atual como marca de tempo. Este cabeçalho determinará o fuso horário usado para gerar essa marca de tempo atual. +This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. -#### Usar o último fuso horário conhecido para o usuário +#### Using the last known timezone for the user -Se nenhum cabeçalho `Time-Zone` for especificado e você fizer uma chamada autenticada para a API, nós usaremos o último fuso horário conhecido para o usuário autenticado. O último fuso horário conhecido é atualizado sempre que você navegar no site de {% data variables.product.product_name %}. +If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website. -#### Definir como padrão UTC sem outras informações de fuso horário +#### Defaulting to UTC without other timezone information -Se as etapas acima não resultarem em nenhuma informação, usaremos UTC como o fuso horário para criar o commit do git. - -[rfc]: http://tools.ietf.org/html/rfc6570 -[uri]: https://github.com/hannesg/uri_template +If the steps above don't result in any information, we use UTC as the timezone to create the git commit. [pagination-guide]: /guides/traversing-with-pagination diff --git a/translations/pt-BR/content/rest/overview/troubleshooting.md b/translations/pt-BR/content/rest/overview/troubleshooting.md index f0cfcfd6d2..3ae646ccf1 100644 --- a/translations/pt-BR/content/rest/overview/troubleshooting.md +++ b/translations/pt-BR/content/rest/overview/troubleshooting.md @@ -13,16 +13,53 @@ versions: Se você estiver encontrando algumas situações estranhas na API, aqui está uma lista de resoluções de alguns dos problemas que você pode estar enfrentando. -### Por que estou recebendo um erro `404` em um repositório que existe? +### `404` error for an existing repository Normalmente, enviamos um erro `404` quando seu cliente não está autenticado corretamente. Nesses casos, você pode esperar ver um `403 Forbidden`. No entanto, como não queremos fornecer _nenhuma_ informação sobre repositórios privados, a API retorna um erro `404`. Para solucionar o problema, verifique se [você está efetuando a autenticação corretamente](/guides/getting-started/), se [seu token de acesso do OAuth tem os escopos necessários](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) e se as [restrições de aplicativos de terceiros][oap-guide] não estão bloqueando o acesso. -### Por que eu não estou vendo todos os meus resultados? +### Not all results returned A maioria das chamadas da API que acessam uma lista de recursos (_por exemplo,_, usuários, issues, _etc._) é compatível com a paginação. Se você está fazendo solicitações e recebendo um conjunto incompleto de resultados, provavelmente você só está vendo a primeira página. Você precisará solicitar as páginas restantes para obter mais resultados. -É importante *não* tentar adivinhar o formato da URL de paginação. Nem todas as chamadas de API usam a mesma estrutura. Em vez disso, extraia as informações de paginação do [Cabeçalho do link](/v3/#pagination), que é enviado com cada solicitação. +É importante *não* tentar adivinhar o formato da URL de paginação. Nem todas as chamadas de API usam a mesma estrutura. Em vez disso, extraia as informações de paginação do [Cabeçalho do link](/rest#pagination), que é enviado com cada solicitação. + +{% if currentVersion == "free-pro-team@latest" %} +### Basic authentication errors + +On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work. + +#### Using `username`/`password` for basic authentication + +If you're using `username` and `password` for API calls, then they are no longer able to authenticate. Por exemplo: + +```bash +curl -u my_user:my_password https://api.github.com/user/repos +``` + +Instead, use a [personal access token](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development: + +```bash +curl -H 'Authorization: token my_access_token' https://api.github.com/user/repos +``` + +For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header: + +```bash +curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos +``` + +#### Calls to OAuth Authorizations API + +If you're making [OAuth Authorization API](/enterprise-server@2.22/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: + +```bash +curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' +``` + +Then you must switch to the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate access tokens. + +{% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/pt-BR/content/rest/reference/apps.md b/translations/pt-BR/content/rest/reference/apps.md index 3ba2ec641f..715b831b43 100644 --- a/translations/pt-BR/content/rest/reference/apps.md +++ b/translations/pt-BR/content/rest/reference/apps.md @@ -18,7 +18,7 @@ Quando autenticado como um aplicativo GitHub, a API dos aplicativos GitHub permi 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](/v3/apps/installations/) para obter uma lista desses pontos de extremidade. +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 %} @@ -36,7 +36,7 @@ Você pode usar essa API para gerenciar os tokens do OAuth que um aplicativo OAu 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](/v3/orgs/#list-app-installations-for-an-organization)". +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 %} @@ -70,4 +70,4 @@ Certifique-se de substituir pontos de extremidades de amostra pelos pontos de ex {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} 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 817c48ce5e..088c9b0b25 100644 --- a/translations/pt-BR/content/rest/reference/codes-of-conduct.md +++ b/translations/pt-BR/content/rest/reference/codes-of-conduct.md @@ -9,6 +9,6 @@ versions: github-ae: '*' --- -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](/v3/repos/#get-a-repository). +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/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md index 2c87028dda..b8401b873d 100644 --- a/translations/pt-BR/content/rest/reference/enterprise-admin.md +++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md @@ -86,7 +86,7 @@ O IdP deve usar `{% data variables.product.api_url_code %}/scim/v2/enterprises/{ {% note %} -**Nota:** A API corporativa SCIM está disponível apenas para empresas em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SAML SSO](/v3/auth/#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Nota:** A API corporativa SCIM está disponível apenas para empresas em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." {% endnote %} diff --git a/translations/pt-BR/content/rest/reference/git.md b/translations/pt-BR/content/rest/reference/git.md index a9f35e9259..4a2a2d00dc 100644 --- a/translations/pt-BR/content/rest/reference/git.md +++ b/translations/pt-BR/content/rest/reference/git.md @@ -34,7 +34,7 @@ Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media- ## Commits -Um commit do Git é um instantâneo da hierarquia ([árvore do Git](/v3/git/trees)) e o conteúdo dos arquivos ([Blob do Git](/v3/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 %}. +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 %} @@ -50,7 +50,7 @@ Uma referência do Git (`git ref`) é apenas um arquivo que contém um hash SHA- ## Tags -Uma tag do Git é semelhante a uma [Referência do Git](/v3/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. +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 %} diff --git a/translations/pt-BR/content/rest/reference/interactions.md b/translations/pt-BR/content/rest/reference/interactions.md index 38a825112d..39199f965a 100644 --- a/translations/pt-BR/content/rest/reference/interactions.md +++ b/translations/pt-BR/content/rest/reference/interactions.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -Os usuários interagem com repositórios comentando, abrindo problemas e criando pull requests. As APIs de interações permitem que pessoas com acesso de proprietário ou administrador restrinjam temporariamente certos usuários de interagir com repositórios públicos. +Os usuários interagem com repositórios comentando, abrindo problemas e criando pull requests. The Interactions APIs allow people with owner or admin access to temporarily restrict interaction with public repositories to a certain type of user. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -14,24 +14,42 @@ Os usuários interagem com repositórios comentando, abrindo problemas e criando ## organização -A API de Interações da Organização permite que os proprietários da organização restrinjam temporariamente quais usuários 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 grupos de usuários do {% data variables.product.product_name %}: +The Organization Interactions API allows organization owners to temporarily restrict which type of user can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users: * {% 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. +Setting the interaction limit at the organization level will overwrite any interaction limits that are set for individual repositories owned by the organization. To set different interaction limits for individual repositories owned by the organization, use the [Repository](#repository) interactions endpoints instead. + {% 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 quais usuários podem comentar, abrir problemas ou criar pull requests em um repositório público. {% data reusables.interactions.interactions-detail %} Veja mais sobre os grupos de usuários do {% data variables.product.product_name %}: +The Repository Interactions API allows people with owner or admin access to temporarily restrict which type of user can comment, open issues, or create pull requests in a public repository. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users: * {% 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. +If an interaction limit is enabled for the user or organization that owns the repository, the limit cannot be changed for the individual repository. Instead, use the [User](#user) or [Organization](#organization) interactions endpoints to change the interaction limit. + {% for operation in currentRestOperations %} {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %} {% endfor %} + +## 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 %} Here's more about the types of {% data variables.product.product_name %} users: + +* {% 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. + +{% 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 3c646514da..b8a577c93f 100644 --- a/translations/pt-BR/content/rest/reference/issues.md +++ b/translations/pt-BR/content/rest/reference/issues.md @@ -33,7 +33,7 @@ Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de míd 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](/v3/media/). +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 %} diff --git a/translations/pt-BR/content/rest/reference/licenses.md b/translations/pt-BR/content/rest/reference/licenses.md index 0e7d2821ac..f4af3090af 100644 --- a/translations/pt-BR/content/rest/reference/licenses.md +++ b/translations/pt-BR/content/rest/reference/licenses.md @@ -16,12 +16,12 @@ Se uma licença for correspondida, a chave da licença e o nome retornados serã **Observação:** Estes pontos de extremidade também retornarão informações de licença de um repositório: -- [Obter um repositório](/v3/repos/#get-a-repository) -- [Listar repositórios para um usuário](/v3/repos/#list-repositories-for-a-user) -- [Listar repositórios da organização](/v3/repos/#list-organization-repositories) +- [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](/v3/teams/#list-team-repositories) +- [Listar repositórios da equipe](/rest/reference/teams#list-team-repositories) {% warning %} diff --git a/translations/pt-BR/content/rest/reference/oauth-authorizations.md b/translations/pt-BR/content/rest/reference/oauth-authorizations.md index 5c84f6084f..8a9ca5c0da 100644 --- a/translations/pt-BR/content/rest/reference/oauth-authorizations.md +++ b/translations/pt-BR/content/rest/reference/oauth-authorizations.md @@ -4,13 +4,9 @@ redirect_from: - /v3/oauth_authorizations - /v3/oauth-authorizations versions: - free-pro-team: '*' enterprise-server: '*' --- -{% data reusables.apps.deprecating_token_oauth_authorizations %} -{% data reusables.apps.deprecating_password_auth %} - 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). diff --git a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md index 0b32aa026a..627e225519 100644 --- a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md @@ -19,63 +19,63 @@ Os aplicativos GitHub têm a permissão de metadados `Read-only` por padrão. A {% data reusables.apps.metadata-permissions %} -- [`GET /`](/v3/#root-endpoint) -- [`GET /codes_of_conduct`](/v3/codes_of_conduct/#get-all-codes-of-conduct) -- [`GET /codes_of_conduct/:key`](/v3/codes_of_conduct/#get-a-code-of-conduct) -- [`GET /emojis`](/v3/emojis/#emojis) +- [`GET /`](/rest#root-endpoint) +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +- [`GET /emojis`](/rest/reference/emojis#emojis) - [`GET /feeds`](/rest/reference/activity#get-feeds) -- [`GET /licenses`](/v3/licenses/#get-all-commonly-used-licenses) -- [`GET /licenses/:key`](/v3/licenses/#get-a-license) -- [`POST /markdown`](/v3/markdown/#render-a-markdown-document) -- [`POST /markdown/raw`](/v3/markdown/#render-a-markdown-document-in-raw-mode) -- [`GET /meta`](/v3/meta/#meta) -- [`GET /organizations`](/v3/orgs/#list-organizations) -- [`GET /orgs/:org`](/v3/orgs/#get-an-organization) -- [`GET /orgs/:org/projects`](/v3/projects/#list-organization-projects) -- [`GET /orgs/:org/repos`](/v3/repos/#list-organization-repositories) -- [`GET /rate_limit`](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) -- [`GET /repos/:owner/:repo`](/v3/repos/#get-a-repository) +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license) +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +- [`GET /meta`](/rest/reference/meta#meta) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization) +- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects) +- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories) +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/community/profile`](/v3/repos/community/#get-community-profile-metrics) +- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics) {% endif %} -- [`GET /repos/:owner/:repo/contributors`](/v3/repos/#list-repository-contributors) +- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors) - [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks) -- [`GET /repos/:owner/:repo/languages`](/v3/repos/#list-repository-languages) -- [`GET /repos/:owner/:repo/license`](/v3/licenses/#get-the-license-for-a-repository) +- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository) - [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers) -- [`GET /repos/:owner/:repo/stats/code_frequency`](/v3/repos/statistics/#get-the-weekly-commit-activity) -- [`GET /repos/:owner/:repo/stats/commit_activity`](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -- [`GET /repos/:owner/:repo/stats/contributors`](/v3/repos/statistics/#get-all-contributor-commit-activity) -- [`GET /repos/:owner/:repo/stats/participation`](/v3/repos/statistics/#get-the-weekly-commit-count) -- [`GET /repos/:owner/:repo/stats/punch_card`](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity) +- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity) +- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity) +- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count) +- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) - [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers) -- [`GET /repos/:owner/:repo/tags`](/v3/repos/#list-repository-tags) -- [`GET /repos/:owner/:repo/topics`](/v3/repos#get-all-repository-topics) -- [`GET /repositories`](/v3/repos/#list-public-repositories) -- [`GET /user/repos`](/v3/repos/#list-repositories-for-the-authenticated-user) +- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) - [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) - [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) -- [`GET /users`](/v3/users/#list-users) -- [`GET /users/:username`](/v3/users/#get-a-user) -- [`GET /users/:username/followers`](/v3/users/followers/#list-followers-of-a-user) -- [`GET /users/:username/following`](/v3/users/followers/#list-the-people-a-user-follows) -- [`GET /users/:username/following/:target_user`](/v3/users/followers/#check-if-a-user-follows-another-user) -- [`GET /users/:username/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) -- [`GET /users/:username/orgs`](/v3/orgs/#list-organizations-for-a-user) +- [`GET /users`](/rest/reference/users#list-users) +- [`GET /users/:username`](/rest/reference/users#get-a-user) +- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user) - [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) - [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) -- [`GET /users/:username/repos`](/v3/repos/#list-repositories-for-a-user) +- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) _Colaboradores_ -- [`GET /repos/:owner/:repo/collaborators`](/v3/repos/collaborators/#list-repository-collaborators) -- [`GET /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) +- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) +- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) _Comentários de commit_ -- [`GET /repos/:owner/:repo/comments`](/v3/repos/comments/#list-commit-comments-for-a-repository) -- [`GET /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#get-a-commit-comment) -- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-commit-comment) -- [`GET /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#list-commit-comments) +- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) +- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) +- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) _Eventos_ - [`GET /events`](/rest/reference/activity#list-public-events) @@ -86,311 +86,311 @@ _Eventos_ - [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user) _Git_ -- [`GET /gitignore/templates`](/v3/gitignore/#get-all-gitignore-templates) -- [`GET /gitignore/templates/:key`](/v3/gitignore/#get-a-gitignore-template) +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) +- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) _Chaves_ -- [`GET /users/:username/keys`](/v3/users/keys/#list-public-keys-for-a-user) +- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) _Integrantes da organização_ -- [`GET /orgs/:org/members`](/v3/orgs/members/#list-organization-members) -- [`GET /orgs/:org/members/:username`](/v3/orgs/members/#check-organization-membership-for-a-user) -- [`GET /orgs/:org/public_members`](/v3/orgs/members/#list-public-organization-members) -- [`GET /orgs/:org/public_members/:username`](/v3/orgs/members/#check-public-organization-membership-for-a-user) +- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`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) _Pesquisar_ -- [`GET /search/code`](/v3/search/#search-code) -- [`GET /search/commits`](/v3/search/#search-commits) -- [`GET /search/issues`](/v3/search/#search-issues-and-pull-requests) -- [`GET /search/labels`](/v3/search/#search-labels) -- [`GET /search/repositories`](/v3/search/#search-repositories) -- [`GET /search/topics`](/v3/search/#search-topics) -- [`GET /search/users`](/v3/search/#search-users) +- [`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) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) {% if currentVersion == "free-pro-team@latest" %} ### Permissão em "ações" -- [`GET /repos/:owner/:repo/actions/artifacts`](/v3/actions/artifacts/#list-artifacts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} ### Permissão em "administração" -- [`POST /orgs/:org/repos`](/v3/repos/#create-an-organization-repository) (:write) -- [`PATCH /repos/:owner/:repo`](/v3/repos/#update-a-repository) (:write) -- [`DELETE /repos/:owner/:repo`](/v3/repos/#delete-a-repository) (:write) +- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) +- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) +- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) (:read) -- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) (:write)git +- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write)git {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#enable-automated-security-fixes) (:write) +- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#disable-automated-security-fixes) (:write) +- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:write) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write) {% endif %} -- [`PUT /repos/:owner/:repo/topics`](/v3/repos/#replace-all-repository-topics) (:write) -- [`POST /repos/:owner/:repo/transfer`](/v3/repos/#transfer-a-repository) (:write) +- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write) +- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#disable-vulnerability-alerts) (:write) +- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write) {% endif %} -- [`PATCH /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#accept-a-repository-invitation) (:write) -- [`DELETE /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#decline-a-repository-invitation) (:write) +- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write) +- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write) _Branches_ -- [`GET /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#get-branch-protection) (:read) -- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#update-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#delete-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#get-admin-branch-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#set-admin-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#delete-admin-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#get-pull-request-review-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#update-pull-request-review-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#delete-pull-request-review-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#get-commit-signature-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#create-commit-signature-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#delete-commit-signature-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#get-status-checks-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#update-status-check-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#remove-status-check-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#get-all-status-check-contexts) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#add-status-check-contexts) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#set-status-check-contexts) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#remove-status-check-contexts) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#get-access-restrictions) (:read) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#delete-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#add-team-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#set-team-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#remove-team-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#add-user-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#set-user-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read) +- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Colaboradores_ -- [`PUT /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#add-a-repository-collaborator) (:write) -- [`DELETE /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#remove-a-repository-collaborator) (:write) +- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) +- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) _Convites_ -- [`GET /repos/:owner/:repo/invitations`](/v3/repos/invitations/#list-repository-invitations) (:read) -- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#update-a-repository-invitation) (:write) -- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#delete-a-repository-invitation) (:write) +- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) +- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) +- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) _Chaves_ -- [`GET /repos/:owner/:repo/keys`](/v3/repos/keys/#list-deploy-keys) (:read) -- [`POST /repos/:owner/:repo/keys`](/v3/repos/keys/#create-a-deploy-key) (:write) -- [`GET /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#get-a-deploy-key) (:read) -- [`DELETE /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#delete-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) +- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) +- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) _Equipes_ -- [`GET /repos/:owner/:repo/teams`](/v3/repos/#list-repository-teams) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:write) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) +- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) {% if currentVersion == "free-pro-team@latest" %} _Tráfego_ -- [`GET /repos/:owner/:repo/traffic/clones`](/v3/repos/traffic/#get-repository-clones) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/paths`](/v3/repos/traffic/#get-top-referral-paths) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/v3/repos/traffic/#get-top-referral-sources) (:read) -- [`GET /repos/:owner/:repo/traffic/views`](/v3/repos/traffic/#get-page-views) (:read) +- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) +- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permissão em "bloqueio" -- [`GET /user/blocks`](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) (:read) -- [`GET /user/blocks/:username`](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) -- [`PUT /user/blocks/:username`](/v3/users/blocking/#block-a-user) (:write) -- [`DELETE /user/blocks/:username`](/v3/users/blocking/#unblock-a-user) (:write) +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) +- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) +- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (:write) +- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) {% endif %} ### Permissão em "verificações" -- [`POST /repos/:owner/:repo/check-runs`](/v3/checks/runs/#create-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#update-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`POST /repos/:owner/:repo/check-suites`](/v3/checks/suites/#create-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/v3/checks/suites/#update-repository-preferences-for-check-suites) (:write) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) +- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (:write) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) ### Permissão em "conteúdo" -- [`GET /repos/:owner/:repo/:archive_format/:ref`](/v3/repos/contents/#download-a-repository-archive) (:read) +- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:write) +- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#get-a-repository-secret) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) +- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) +- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/commits`](/v3/repos/commits/#list-commits) (:read) -- [`GET /repos/:owner/:repo/commits/:sha`](/v3/repos/commits/#get-a-commit) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/community/code_of_conduct`](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/compare/:base...:head`](/v3/repos/commits/#compare-two-commits) (:read) -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read) +- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`POST /repos/:owner/:repo/dispatches`](/v3/repos/#create-a-repository-dispatch-event) (:write) +- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:read) -- [`POST /repos/:owner/:repo/merges`](/v3/repos/merging/#merge-a-branch) (:write) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#merge-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/v3/repos/contents/#get-a-repository-readme) (:read) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read) +- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read) _Branches_ -- [`GET /repos/:owner/:repo/branches`](/v3/repos/branches/#list-branches) (:read) -- [`GET /repos/:owner/:repo/branches/:branch`](/v3/repos/branches/#get-a-branch) (:read) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#list-apps-with-access-to-the-protected-branch) (:write) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#add-app-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#set-app-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read) +- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Comentários de commit_ -- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#update-a-commit-comment) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#delete-a-commit-comment) (:write) -- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-commit-comment) (:read) -- [`POST /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#create-a-commit-comment) (:read) +- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) +- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) +- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read) _Git_ -- [`POST /repos/:owner/:repo/git/blobs`](/v3/git/blobs/#create-a-blob) (:write) -- [`GET /repos/:owner/:repo/git/blobs/:sha`](/v3/git/blobs/#get-a-blob) (:read) -- [`POST /repos/:owner/:repo/git/commits`](/v3/git/commits/#create-a-commit) (:write) -- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/v3/git/commits/#get-a-commit) (:read) -- [`POST /repos/:owner/:repo/git/refs`](/v3/git/refs/#create-a-reference) (:write) -- [`GET /repos/:owner/:repo/git/ref/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/v3/git/refs/#list-matching-references) (:read) -- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#update-a-reference) (:write) -- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#delete-a-reference) (:write) -- [`POST /repos/:owner/:repo/git/tags`](/v3/git/tags/#create-a-tag-object) (:write) -- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/v3/git/tags/#get-a-tag) (:read) -- [`POST /repos/:owner/:repo/git/trees`](/v3/git/trees/#create-a-tree) (:write) -- [`GET /repos/:owner/:repo/git/trees/:sha`](/v3/git/trees/#get-a-tree) (:read) +- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write) +- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (:read) +- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (:write) +- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (:read) +- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (:write) +- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (:read) +- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (:read) +- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (:write) +- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (:write) +- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (:write) +- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (:read) +- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (:write) +- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) {% if currentVersion == "free-pro-team@latest" %} _importar_ -- [`GET /repos/:owner/:repo/import`](/v3/migrations/source_imports/#get-an-import-status) (:read) -- [`PUT /repos/:owner/:repo/import`](/v3/migrations/source_imports/#start-an-import) (:write) -- [`PATCH /repos/:owner/:repo/import`](/v3/migrations/source_imports/#update-an-import) (:write) -- [`DELETE /repos/:owner/:repo/import`](/v3/migrations/source_imports/#cancel-an-import) (:write) -- [`GET /repos/:owner/:repo/import/authors`](/v3/migrations/source_imports/#get-commit-authors) (:read) -- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/v3/migrations/source_imports/#map-a-commit-author) (:write) -- [`GET /repos/:owner/:repo/import/large_files`](/v3/migrations/source_imports/#get-large-files) (:read) -- [`PATCH /repos/:owner/:repo/import/lfs`](/v3/migrations/source_imports/#update-git-lfs-preference) (:write) +- [`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) +- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (:write) +- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (:read) +- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (:write) +- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (:read) +- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) {% endif %} _Reações_ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% endif %} _Versões_ - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read) @@ -419,195 +419,195 @@ _Versões_ ### Permissão em "e-mails" {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /user/email/visibility`](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) (:write) +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) {% endif %} -- [`GET /user/emails`](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) (:read) -- [`POST /user/emails`](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) (:write) -- [`DELETE /user/emails`](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) (:write) -- [`GET /user/public_emails`](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) (:read) +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (:write) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (:write) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) {% endif %} ### Permissão em "seguidores" -- [`GET /user/followers`](/v3/users/followers/#list-followers-of-a-user) (:read) -- [`GET /user/following`](/v3/users/followers/#list-the-people-a-user-follows) (:read) -- [`GET /user/following/:username`](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) (:read) -- [`PUT /user/following/:username`](/v3/users/followers/#follow-a-user) (:write) -- [`DELETE /user/following/:username`](/v3/users/followers/#unfollow-a-user) (:write) +- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) +- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) +- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (:read) +- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) +- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) ### Permissão em "chaves gpg" -- [`GET /user/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) (:read) -- [`POST /user/gpg_keys`](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) (:write) -- [`GET /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) (:read) -- [`DELETE /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (:read) +- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) ### Permissão em "problemas" -Problemas e pull requests estão estreitamente relacionados. Para obter mais informações, consulte "[Lista de problemas atribuídos ao usuário autenticado](/v3/issues/#list-issues-assigned-to-the-authenticated-user)". Se seu aplicativo GitHub tiver permissões em problemas e não em pull requests, esses pontos de extremidade irão limitar-se a problemas. Pontos de extremidade que retornam problemas e pull requests serão filtrados. Os pontos de extremidade que permitem operações em ambos problemas e pull requests estarão restritos a problemas. +Problemas e pull requests estão estreitamente relacionados. Para obter mais informações, consulte "[Lista de problemas atribuídos ao usuário autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)". Se seu aplicativo GitHub tiver permissões em problemas e não em pull requests, esses pontos de extremidade irão limitar-se a problemas. Pontos de extremidade que retornam problemas e pull requests serão filtrados. Os pontos de extremidade que permitem operações em ambos problemas e pull requests estarão restritos a problemas. -- [`GET /repos/:owner/:repo/issues`](/v3/issues/#list-repository-issues) (:read) -- [`POST /repos/:owner/:repo/issues`](/v3/issues/#create-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#get-an-issue) (:read) -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) +- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (:read) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) _Responsáveis_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _Eventos_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [Get an issue event](/v3/issues/events/#get-an-issue-event) (:read) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [Get an issue event](/rest/reference/issues#get-an-issue-event) (:read) _Etiquetas_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Marcos_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reações_ -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} ### Permissão em "chaves" _Chaves_ -- [`GET /user/keys`](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) (:read) -- [`POST /user/keys`](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) (:write) -- [`GET /user/keys/:key_id`](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) (:read) -- [`DELETE /user/keys/:key_id`](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) +- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) ### Permissão em "integrantes" {% if currentVersion == "free-pro-team@latest" %} -- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#list-idp-groups-for-a-team) (:write) +- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#create-or-update-idp-group-connections) (:write) +- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write) {% endif %} -- [`GET /orgs/:org/outside_collaborators`](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) (:read) -- [`PUT /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) (:write) -- [`DELETE /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) (:write) +- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read) +- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write) +- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/team-sync/groups`](/v3/teams/team_sync/#list-idp-groups-for-an-organization) (:write) +- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write) {% endif %} -- [`GET /orgs/:org/team/:team_id`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users`](/v3/scim/#list-scim-provisioned-identities) (:read) +- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /scim/v2/orgs/:org/Users`](/v3/scim/#provision-and-invite-a-scim-user) (:write) +- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#get-scim-provisioning-information-for-a-user) (:read) +- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#set-scim-information-for-a-provisioned-user) (:write) +- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#update-an-attribute-for-a-scim-user) (:write) +- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#delete-a-scim-user-from-an-organization) (:write) +- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} _Convites_ -- [`GET /orgs/:org/invitations`](/v3/orgs/members/#list-pending-organization-invitations) (:read) -- [`POST /orgs/:org/invitations`](/v3/orgs/members/#create-an-organization-invitation) (:write) -- [`GET /orgs/:org/invitations/:invitation_id/teams`](/v3/orgs/members/#list-organization-invitation-teams) (:read) -- [`GET /teams/:team_id/invitations`](/v3/teams/members/#list-pending-team-invitations) (:read) +- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) +- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) +- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) +- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) {% endif %} _Integrantes da organização_ -- [`DELETE /orgs/:org/members/:username`](/v3/orgs/members/#remove-an-organization-member) (:write) -- [`GET /orgs/:org/memberships/:username`](/v3/orgs/members/#get-organization-membership-for-a-user) (:read) -- [`PUT /orgs/:org/memberships/:username`](/v3/orgs/members/#set-organization-membership-for-a-user) (:write) -- [`DELETE /orgs/:org/memberships/:username`](/v3/orgs/members/#remove-organization-membership-for-a-user) (:write) -- [`PUT /orgs/:org/public_members/:username`](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) (:write) -- [`DELETE /orgs/:org/public_members/:username`](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) (:write) -- [`GET /user/memberships/orgs`](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) (:read) -- [`GET /user/memberships/orgs/:org`](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) (:read) -- [`PATCH /user/memberships/orgs/:org`](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) +- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) +- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) +- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (:write) +- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (:write) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (:read) +- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) +- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) _Integrantes da equipe_ -- [`GET /teams/:team_id/members`](/v3/teams/members/#list-team-members) (:read) -- [`GET /teams/:team_id/memberships/:username`](/v3/teams/members/#get-team-membership-for-a-user) (:read) -- [`PUT /teams/:team_id/memberships/:username`](/v3/teams/members/#add-or-update-team-membership-for-a-user) (:write) -- [`DELETE /teams/:team_id/memberships/:username`](/v3/teams/members/#remove-team-membership-for-a-user) (:write) +- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) +- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) +- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) +- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) _Equipes_ -- [`GET /orgs/:org/teams`](/v3/teams/#list-teams) (:read) -- [`POST /orgs/:org/teams`](/v3/teams/#create-a-team) (:write) -- [`GET /orgs/:org/teams/:team_slug`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) +- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) +- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -- [`GET /teams/:team_id`](/v3/teams/#get-a-team) (:read) +- [`GET /teams/:team_id`](/rest/reference/teams#get-a-team) (:read) {% endif %} -- [`PATCH /teams/:team_id`](/v3/teams/#update-a-team) (:write) -- [`DELETE /teams/:team_id`](/v3/teams/#delete-a-team) (:write) +- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write) +- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`GET /teams/:team_id/projects`](/v3/teams/#list-team-projects) (:read) -- [`GET /teams/:team_id/projects/:project_id`](/v3/teams/#check-team-permissions-for-a-project) (:read) -- [`PUT /teams/:team_id/projects/:project_id`](/v3/teams/#add-or-update-team-project-permissions) (:read) -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read) +- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read) +- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% endif %} -- [`GET /teams/:team_id/repos`](/v3/teams/#list-team-repositories) (:read) -- [`GET /teams/:team_id/repos/:owner/:repo`](/v3/teams/#check-team-permissions-for-a-repository) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:read) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) -- [`GET /teams/:team_id/teams`](/v3/teams/#list-child-teams) (:read) +- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read) +- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) +- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) ### Permissão em "administração da organização" -- [`PATCH /orgs/:org`](/v3/orgs/#update-an-organization) (:write) +- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/interaction-limits`](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) (:read) +- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /orgs/:org/interaction-limits`](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) (:write) +- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /orgs/:org/interaction-limits`](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) (:write) +- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) {% endif %} ### Permissão em "hooks da organização" @@ -620,7 +620,7 @@ _Equipes_ - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write) _Equipes_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permissão em "hooks pre-receive da organização" @@ -633,31 +633,31 @@ _Equipes_ ### Permissão em "projetos da organização" -- [`POST /orgs/:org/projects`](/v3/projects/#create-an-organization-project) (:write) -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) +- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) {% if currentVersion == "free-pro-team@latest" %} ### Permissão em "bloqueio de usuários da organização" -- [`GET /orgs/:org/blocks`](/v3/orgs/blocking/#list-users-blocked-by-an-organization) (:read) -- [`GET /orgs/:org/blocks/:username`](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) (:read) -- [`PUT /orgs/:org/blocks/:username`](/v3/orgs/blocking/#block-a-user-from-an-organization) (:write) -- [`DELETE /orgs/:org/blocks/:username`](/v3/orgs/blocking/#unblock-a-user-from-an-organization) (:write) +- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) +- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) +- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (:write) +- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) {% endif %} ### Permissão em "páginas" @@ -675,99 +675,99 @@ _Equipes_ Pull requests and issues are closely related.. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Os pontos de extremidade que retornam pull requests e problemas serão filtrados. Os pontos de extremidade que permitem operações em pull requests e problemas serão restritos a pull requests. -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls`](/v3/pulls/#list-pull-requests) (:read) -- [`POST /repos/:owner/:repo/pulls`](/v3/pulls/#create-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#get-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#update-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#list-review-comments-on-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/v3/pulls/#list-commits-on-a-pull-request) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/v3/pulls/#list-pull-requests-files) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#check-if-a-pull-request-has-been-merged) (:read) -- [`GET /repos/:owner/:repo/pulls/comments`](/v3/pulls/comments/#list-review-comments-in-a-repository) (:read) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) (:write) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (:read) +- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (:read) +- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (:read) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) _Responsáveis_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _Eventos_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [`GET /repos/:owner/:repo/issues/events/:event_id`](/v3/issues/events/#get-an-issue-event) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) _Etiquetas_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Marcos_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reações_ -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) (:read) -- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) (:write) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read) +- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} _Revisores solicitados_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) _Revisões_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#list-reviews-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#create-a-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#get-a-review-for-a-pull-request) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#update-a-review-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#delete-a-pending-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) ### Permissão em "hooks de repositório" -- [`GET /repos/:owner/:repo/hooks`](/v3/repos/hooks/#list-repository-webhooks) (:read) -- [`POST /repos/:owner/:repo/hooks`](/v3/repos/hooks/#create-a-repository-webhook) (:write) -- [`GET /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#get-a-repository-webhook) (:read) -- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#update-a-repository-webhook) (:write) -- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#delete-a-repository-webhook) (:write) -- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/v3/repos/hooks/#ping-a-repository-webhook) (:read) -- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/v3/repos/hooks/#test-the-push-repository-webhook) (:read) +- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) +- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) +- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read) +- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write) +- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write) +- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read) +- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permission on "repository pre receive hooks" @@ -780,70 +780,70 @@ _Revisões_ ### Permissão em "projetos de repositório" -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) -- [`GET /repos/:owner/:repo/projects`](/v3/projects/#list-repository-projects) (:read) -- [`POST /repos/:owner/:repo/projects`](/v3/projects/#create-a-repository-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) +- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) +- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) _Equipes_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if currentVersion == "free-pro-team@latest" %} ### Permissão em "segredos" -* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:read) -* [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:read) -* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#get-a-repository-secret) (:read) -* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -* [`GET /orgs/:org/actions/secrets/public-key`](/v3/actions/secrets/#get-an-organization-public-key) (:read) -* [`GET /orgs/:org/actions/secrets`](/v3/actions/secrets/#list-organization-secrets) (:read) -* [`GET /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#get-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-an-organization-secret) (:write) -* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) (:write) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-an-organization-secret) (:write) +* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) +* [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) +* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (:read) +* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (:write) +* [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (:read) +* [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (:read) +* [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (:write) +* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (:write) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permissão em "eventos de segurança" -- [`GET /repos/:owner/:repo/code-scanning/alerts`](/v3/code-scanning/#list-code-scanning-alerts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/v3/code-scanning/#get-a-code-scanning-alert) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permissão em "executores auto-hospedados" -- [`GET /orgs/:org/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) (:write) -- [`GET /orgs/:org/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) (:read) -- [`GET /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) (:write) -- [`DELETE /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) +- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) +- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) {% endif %} ### Permissão em "arquivo único" -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -- [`PUT /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#create-or-update-file-contents) (:write) -- [`DELETE /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#delete-a-file) (:write) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) +- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) ### Permissão em "marcar com uma estrela" @@ -853,23 +853,23 @@ _Equipes_ ### Permissão em "status" -- [`GET /repos/:owner/:repo/commits/:ref/status`](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/v3/repos/statuses/#list-commit-statuses-for-a-reference) (:read) -- [`POST /repos/:owner/:repo/statuses/:sha`](/v3/repos/statuses/#create-a-commit-status) (:write) +- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) +- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) ### Permissão em "discussões em equipe" -- [`GET /teams/:team_id/discussions`](/v3/teams/discussions/#list-discussions) (:read) -- [`POST /teams/:team_id/discussions`](/v3/teams/discussions/#create-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#get-a-discussion) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#update-a-discussion) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#delete-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#list-discussion-comments) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#create-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#get-a-discussion-comment) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#update-a-discussion-comment) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#delete-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion-comment) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion) (:write) +- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) +- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/pt-BR/content/rest/reference/pulls.md b/translations/pt-BR/content/rest/reference/pulls.md index 20ba6518ad..7f6daae447 100644 --- a/translations/pt-BR/content/rest/reference/pulls.md +++ b/translations/pt-BR/content/rest/reference/pulls.md @@ -10,7 +10,7 @@ versions: 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](/v3/issues). +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 @@ -33,16 +33,16 @@ Se um diff estiver corrompido, entre em contato com {% data variables.contact.co 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](/v3/issues/) deste Pull Request. | -| `comentários` | O local da API dos [comentários do problema](/v3/issues/comments/) deste Pull Request. | -| `review_comments` | O local da API dos [comentários da revisão](/v3/pulls/comments/) deste Pull Request. | -| `review_comment` | O [modelo de URL](/v3/#hypermedia) para construir o local da API para um [comentário de revisão](/v3/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](/v3/repos/statuses/) deste pull request, que são os status no seu branch `principal`. | +| 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/repos#statuses) deste pull request, que são os status no seu branch `principal`. | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/pt-BR/content/rest/reference/rate-limit.md b/translations/pt-BR/content/rest/reference/rate-limit.md index 885899bd01..475db3b62b 100644 --- a/translations/pt-BR/content/rest/reference/rate-limit.md +++ b/translations/pt-BR/content/rest/reference/rate-limit.md @@ -13,18 +13,18 @@ A documentação geral da API REST descreve as [regras de limite de taxa](/rest/ ### Entender o seu status de limite de taxa -A API de pesquisa tem um [limite de taxa personalizado](/v3/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](/v4/guides/resource-limitations/#rate-limit), que é separado e calculado de forma diferente dos limites de taxa na API REST. +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](/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](/v3/search/). +* 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](/v4/). +* O objeto `graphql` fornece o status do limite de taxa para a [API do GraphQL](/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 do limite de taxa, consulte "[Limitação de taxa](/v3/#rate-limiting)". +Para obter mais informações sobre os cabeçalhos e valores na resposta do limite de taxa, consulte "[Limitação de taxa](/rest#rate-limiting)". {% include rest_operations_at_current_path %} diff --git a/translations/pt-BR/content/rest/reference/repos.md b/translations/pt-BR/content/rest/reference/repos.md index 00b336f3cf..10c1988d33 100644 --- a/translations/pt-BR/content/rest/reference/repos.md +++ b/translations/pt-BR/content/rest/reference/repos.md @@ -29,7 +29,7 @@ versions: ### 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](/v3/media/). +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 @@ -65,7 +65,7 @@ Estes pontos de extremidade da API permitem criar, modificar e excluir conteúdo ### Tipos de mídia personalizados para conteúdo do repositório -Os [LEIAMEs](/v3/repos/contents/#get-a-repository-readme), [arquivos](/v3/repos/contents/#get-repository-content) e [links simbólicos](/v3/repos/contents/#get-repository-content) são compatíveis com os seguintes tipos de mídia personalizados: +Os [LEIAMEs](/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 @@ -74,13 +74,13 @@ 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](/v3/repos/contents/#get-repository-content) são compatíveis com o seguinte tipo de mídia personalizado: +[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. -You can read more about the use of media types in the API [here](/v3/media/). +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 == 'contents' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/rest/reference/scim.md b/translations/pt-BR/content/rest/reference/scim.md index 19a5944fd2..396aa76b48 100644 --- a/translations/pt-BR/content/rest/reference/scim.md +++ b/translations/pt-BR/content/rest/reference/scim.md @@ -12,7 +12,7 @@ A API do SCIM é usada pelos provedores de identidade (IdPs) habilitados pelo SC {% note %} -**Observação:** A API do SCIM está disponível apenas para organizações em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SSO de SAML](/v3/auth/#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Observação:** A API do SCIM está disponível apenas para organizações em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." {% endnote %} diff --git a/translations/pt-BR/content/rest/reference/search.md b/translations/pt-BR/content/rest/reference/search.md index d6abb35ef4..b823f590ca 100644 --- a/translations/pt-BR/content/rest/reference/search.md +++ b/translations/pt-BR/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: 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](/v3/search/#constructing-a-search-query)". +Você pode restringir sua pesquisa usando as consultas. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." ### Resultados da pesquisa de classificação @@ -18,7 +18,7 @@ A menos que outra opção de ordenamento seja fornecida como um parâmetro de co ### Limite de taxa -A API de pesquisa tem um limite de taxa personalizado. Para solicitações que usam a [Autenticação Básica](/v3/#authentication)[OAuth ](/v3/#authentication) ou [ID e segredo do cliente e](/v3/#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. +A API de pesquisa tem um limite de taxa personalizado. For requests using [Basic Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. Para solicitações não autenticadas, o limite de taxa permite que você faça até 10 solicitações por minuto. {% data reusables.enterprise.rate_limit %} @@ -31,13 +31,19 @@ Cada ponto de extremidade na API de Pesquisa usa [parâmetros de consulta](https A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. O formato da consulta de pesquisa é: ``` -q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N +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 LEIAME, você usaria a consulta seguinte com o ponto de extremidade _pesquisar repositórios_: ``` -q=GitHub+Octocat+in:readme+user:defunkt +GitHub Octocat in:readme user:defunkt +``` + +**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. Por exemplo: +```javascript +// JavaScript +const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` Veja "[Pesquisar no GitHub](/articles/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](/articles/understanding-the-search-syntax/)". diff --git a/translations/pt-BR/content/rest/reference/teams.md b/translations/pt-BR/content/rest/reference/teams.md index cf0356f2d9..c1550a7045 100644 --- a/translations/pt-BR/content/rest/reference/teams.md +++ b/translations/pt-BR/content/rest/reference/teams.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -Esta API só está disponível para os integrantes autenticados da [organização](/v3/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. +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 %} @@ -16,7 +16,7 @@ Esta API só está disponível para os integrantes autenticados da [organizaçã ## 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](/v3/orgs) da equipe pode criar e ler posts de discussão públicos. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Esta API só está disponível para os integrantes autenticados da organização da equipe. +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. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. To learn more about commenting on a discussion post, see the [team discussion comments API](/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 %} @@ -24,7 +24,7 @@ A API de discussões de equipe permite que você obtenha, crie, edite e exclua p ## 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](/v3/teams/discussions). Qualquer integrante da organização da [organização](/v3/orgs) da equipe pode criar e ler comentários em uma discussão pública. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. Esta API só está disponível para os integrantes autenticados da organização da equipe. +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. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. 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 %} @@ -58,4 +58,4 @@ Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/pt-BR/data/glossaries/external.yml b/translations/pt-BR/data/glossaries/external.yml index f8bbd5ab3f..9ec9566950 100644 --- a/translations/pt-BR/data/glossaries/external.yml +++ b/translations/pt-BR/data/glossaries/external.yml @@ -61,7 +61,7 @@ - term: branch description: >- - A branch is a parallel version of a repository. It is contained within the repository, but does not affect the primary or main branch allowing you to work freely without disrupting the "live" version. When you've made the changes you want to make, you can merge your branch back into the main branch to publish your changes. + Um branch é uma versão paralela de um repositório. O branch está contido no repositório, mas não afeta o branch principal ou mestre, o que permite trabalhar livremente sem interromper a versão ativa. Após concluir as alterações necessárias, você poderá fazer merge entre o branch alterado e o branch mestre para publicar as alterações. - term: restrição de branch description: >- @@ -390,11 +390,11 @@ - term: main description: >- - The default development branch. Whenever you create a Git repository, a branch named "main" is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. + Branch de desenvolvimento padrão. Sempre que um repositório do Git é criado, um branch "mestre" também é criado e passa a ser o branch ativo. Contém o desenvolvimento local na maioria dos casos, embora isso ocorra meramente por convenção e não seja obrigatório. - term: mestre description: >- - The default branch in many Git repositories. By default, when you create a new Git repository on the command line a branch called `master` is created. Many tools now use an alternative name for the default branch. For example, when you create a new repository on GitHub the default branch is called `main`. + O branch padrão em muitos repositórios do Git. Por padrão, ao criar um novo repositório do Git na linha de comando um branch denominado "mestre" é criado. Muitas ferramentas agora usam um nome alternativo para o branch padrão. Por exemplo, quando você cria um novo repositório no GitHub, a branch padrão é chamada de "principal". - term: gráfico de integrantes description: Gráfico que exibe todas as bifurcações de um repositório. 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 344e4d9d97..65bf5b1ce0 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 @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` será removido. Use `uploadUrl` em vez disso.' reason: '''uploadUrlTemplate'' está sendo removido porque não é uma URL padrão e adiciona um passo extra do usuário.' date: '2019-04-01T00:00:00+00:00' 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 3c2133cdcb..ece0146393 100644 --- a/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` será removido. Use `uploadUrl` em vez disso.' reason: '''uploadUrlTemplate'' está sendo removido porque não é uma URL padrão e adiciona um passo extra do usuário.' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/pt-BR/data/reusables/actions/actions-use-policy-settings.md b/translations/pt-BR/data/reusables/actions/actions-use-policy-settings.md index 4684905f3f..a7881cba44 100644 --- a/translations/pt-BR/data/reusables/actions/actions-use-policy-settings.md +++ b/translations/pt-BR/data/reusables/actions/actions-use-policy-settings.md @@ -1,3 +1,3 @@ -If you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions. Para obter mais informações, consulte "[Permitir que ações específicas sejam executadas](#allowing-specific-actions-to-run)". +Se você escolher **Permitir selecionar ações**, ações locais são permitidas, e há opções adicionais para permitir outras ações específicas. Para obter mais informações, consulte "[Permitir que ações específicas sejam executadas](#allowing-specific-actions-to-run)". Ao permitir apenas ações locais, a política bloqueia todos os acessos a ações criadas por {% data variables.product.prodname_dotcom %}. Por exemplo, as [`ações/check-out`](https://github.com/actions/checkout) não poderiam ser acessadas. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md b/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md index d4a8174fef..4f1566a6ff 100644 --- a/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md @@ -1,4 +1,4 @@ -When you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions: +Quando você escolher **Permitir selecionar ações**, ações locais são permitidas, e há opções adicionais para permitir outras ações específicas: - **Permitir ações criadas por {% data variables.product.prodname_dotcom %}:** Você pode permitir que todas as ações criadas por {% data variables.product.prodname_dotcom %} sejam usadas por fluxos de trabalho. As ações criadas por {% data variables.product.prodname_dotcom %} estão localizadas nas `ações` e nas organizações do `github`. Para obter mais informações, consulte as [`ações`](https://github.com/actions) e as organizações do [`github`](https://github.com/github). - **Permitir ações do Marketplace por criadores verificados:** Você pode permitir que todas as ações de {% data variables.product.prodname_marketplace %} criadas por criadores verificados sejam usadas por fluxos de trabalho. Quando o GitHub verificou o criador da ação como uma organização parceira, o selo de {% octicon "verified" aria-label="The verified badge" %} é exibido ao lado da ação em {% data variables.product.prodname_marketplace %}. diff --git a/translations/pt-BR/data/reusables/apps/app-ruby-guides.md b/translations/pt-BR/data/reusables/apps/app-ruby-guides.md index e90577047d..5af4d0a4ae 100644 --- a/translations/pt-BR/data/reusables/apps/app-ruby-guides.md +++ b/translations/pt-BR/data/reusables/apps/app-ruby-guides.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Esta guia demonstra o processo de desenvolvimento de aplicativos usando a linguagem de programação Ruby. No entanto, existem muitos [flavors of Octokit](/v3/libraries/). Se você preferir o JavaScript, você pode usar [Probot](https://probot.github.io/) e [Node.js](https://octokit.github.io/rest.js/) para desenvolver Aplicativos GitHub. +**Note:** Esta guia demonstra o processo de desenvolvimento de aplicativos usando a linguagem de programação Ruby. No entanto, existem muitos [flavors of Octokit](/rest/overview/libraries). Se você preferir o JavaScript, você pode usar [Probot](https://probot.github.io/) e [Node.js](https://octokit.github.io/rest.js/) para desenvolver Aplicativos GitHub. {% endnote %} diff --git a/translations/pt-BR/data/reusables/apps/checks-availability.md b/translations/pt-BR/data/reusables/apps/checks-availability.md index c88c016702..29ee7e7d68 100644 --- a/translations/pt-BR/data/reusables/apps/checks-availability.md +++ b/translations/pt-BR/data/reusables/apps/checks-availability.md @@ -1 +1 @@ -A permissão de escrita para a API de verificação só está disponível para aplicativos GitHub. Aplicativos OAuth e usuários autenticados podem ver as execuções de verificação e conjunto de verificações, mas eles não são capazes de criá-los. Se você não estiver criando um aplicativo no GitHub, talvez você esteja interessado no [Statuses API](/v3/repos/statuses/). +A permissão de escrita para a API de verificação só está disponível para aplicativos GitHub. Aplicativos OAuth e usuários autenticados podem ver as execuções de verificação e conjunto de verificações, mas eles não são capazes de criá-los. Se você não estiver criando um aplicativo no GitHub, talvez você esteja interessado no [Statuses API](/rest/reference/repos#statuses). diff --git a/translations/pt-BR/data/reusables/apps/deletes_ssh_keys.md b/translations/pt-BR/data/reusables/apps/deletes_ssh_keys.md index 251106b549..9bf8c88a35 100644 --- a/translations/pt-BR/data/reusables/apps/deletes_ssh_keys.md +++ b/translations/pt-BR/data/reusables/apps/deletes_ssh_keys.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: Revogar todas as permissões de um {% data variables.product.prodname_oauth_app %} exclui quaisquer chaves SSH geradas pelo aplicativo em nome do usuário, incluindo [deploy keys](/v3/guides/managing-deploy-keys/#deploy-keys). +**Warning**: Revogar todas as permissões de um {% data variables.product.prodname_oauth_app %} exclui quaisquer chaves SSH geradas pelo aplicativo em nome do usuário, incluindo [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys). {% endwarning %} diff --git a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md index f8089fbc5d..437c1acc2f 100644 --- a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,9 +1,9 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**Aviso de método obsoleto:** {% data variables.product.prodname_dotcom %} irá descontinuar a autenticação para a API usando parâmetros de consulta. A autenticação para a API deve ser feita com a [autenticação básica HTTP](/v3/auth/#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Usar parâmetros de consulta para efetuar a autenticação na API não funcionará mais a partir de 5 de maio de 2021. {% endif %} Para mais informações, incluindo brownouts agendadas, veja [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). +**Aviso de método obsoleto:** {% data variables.product.prodname_dotcom %} irá descontinuar a autenticação para a API usando parâmetros de consulta. A autenticação para a API deve ser feita com a [autenticação básica HTTP](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Usar parâmetros de consulta para efetuar a autenticação na API não funcionará mais a partir de 5 de maio de 2021. {% endif %} Para mais informações, incluindo brownouts agendadas, veja [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Em vez disso, recomendamos que integradores movam seu token de acesso, `client_id`, or `client_secret` no cabeçalho. {% data variables.product.prodname_dotcom %} anunciará a remoção da autenticação por parâmetros de consulta com aviso prévio. {% endif %} +{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %} Autenticação na API usando parâmetros de consulta enquanto disponível não é mais compatível devido a questões de segurança. Em vez disso, recomendamos que integradores movam seu token de acesso, `client_id`, or `client_secret` no cabeçalho. {% data variables.product.prodname_dotcom %} anunciará a remoção da autenticação por parâmetros de consulta com aviso prévio. {% endif %} {% endwarning %} {% endif %} diff --git a/translations/pt-BR/data/reusables/apps/deprecating_github_services_ghe.md b/translations/pt-BR/data/reusables/apps/deprecating_github_services_ghe.md index 6ac8784e41..462b00ff70 100644 --- a/translations/pt-BR/data/reusables/apps/deprecating_github_services_ghe.md +++ b/translations/pt-BR/data/reusables/apps/deprecating_github_services_ghe.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} {% note %} -**Nota:** GitHub Enterprise versão 2. 7 e superiores não permitem mais que os administradores instalem novos Serviços GitHub e os serviços existentes deixarão de funcionar no GitHub Enterprise versão 2.20 ou superior. Você pode usar o [Replacing GitHub Services guide](/v3/guides/replacing-github-services) para ajudá-lo a atualizar seus serviços para webhooks. +**Nota:** GitHub Enterprise versão 2. 7 e superiores não permitem mais que os administradores instalem novos Serviços GitHub e os serviços existentes deixarão de funcionar no GitHub Enterprise versão 2.20 ou superior. Você pode usar o [Replacing GitHub Services guide](/developers/overview/replacing-github-services) para ajudá-lo a atualizar seus serviços para webhooks. {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/branches/set-default-branch.md b/translations/pt-BR/data/reusables/branches/set-default-branch.md index 00512ded87..f080eecba0 100644 --- a/translations/pt-BR/data/reusables/branches/set-default-branch.md +++ b/translations/pt-BR/data/reusables/branches/set-default-branch.md @@ -1 +1 @@ -Você pode definir o nome do branch-padrão para novos repositórios. For more information, see "[Managing the default branch for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)," "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)," and {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)."{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)."{% endif %} +Você pode definir o nome do branch-padrão para novos repositórios. Para obter mais informações, consulte "[Gerenciar a branch padrão para seus repositórios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories), "[Gerenciar o nome do branch padrão para repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)" e {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de gerenciamento do repositório na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name).{% else %}"[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)".{% endif %} diff --git a/translations/pt-BR/data/reusables/code-scanning/about-code-scanning.md b/translations/pt-BR/data/reusables/code-scanning/about-code-scanning.md index 054042ee8c..2a7b1f0ad7 100644 --- a/translations/pt-BR/data/reusables/code-scanning/about-code-scanning.md +++ b/translations/pt-BR/data/reusables/code-scanning/about-code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} is a feature that you use to analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Any problems identified by the analysis are shown in {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +{% data variables.product.prodname_code_scanning_capc %} é um recurso que você usa para analisar o código em um repositório de {% data variables.product.prodname_dotcom %} para localizar vulnerabilidades de segurança e erros de codificação. Todos os problemas identificados pela análise são exibidos em {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. diff --git a/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md b/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md index 600994b354..1a294850ee 100644 --- a/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -O seguinte arquivo de configuração desabilita as consultas-padrão e especifica um conjunto de consultas personalizadas para serem executadas. Ele também configura o {% data variables.product.prodname_codeql %} para fazer a varredura de arquivos no diretório _src_ (relativas à raiz) e para excluir o diretório _node_modules_ (também relativo à raiz), bem como qualquer arquivo cujo nome termina em _.test.js_. +O seguinte arquivo de configuração desabilita as consultas-padrão e especifica um conjunto de consultas personalizadas para serem executadas. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. ``` yaml name: "My {% data variables.product.prodname_codeql %} config" @@ -24,9 +24,9 @@ queries: - name: Use a query suite file (run queries from a query suite in this repo) uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls -paths-ignore: - - node_modules - - '**/*.test.js' paths: - src +paths-ignore: + - src/node_modules + - '**/*.test.js' ``` diff --git a/translations/pt-BR/data/reusables/code-scanning/false-positive-fix-codeql.md b/translations/pt-BR/data/reusables/code-scanning/false-positive-fix-codeql.md index 9204038e05..15e2030111 100644 --- a/translations/pt-BR/data/reusables/code-scanning/false-positive-fix-codeql.md +++ b/translations/pt-BR/data/reusables/code-scanning/false-positive-fix-codeql.md @@ -1 +1 @@ -If you {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} a {% data variables.product.prodname_codeql %} alert as a false positive result, for example because the code uses a sanitization library that isn't supported, consider contributing to the {% data variables.product.prodname_codeql %} repository and improving the analysis. Para obter mais informações sobre {% data variables.product.prodname_codeql %}, consulte "[Contribuir para {% data variables.product.prodname_codeql %}](https://github.com/github/codeql/blob/main/CONTRIBUTING.md)". +Se você{% if currentVersion == "enterprise-server@2. 2" %}fechar{% else %}ignorar{% endif %} um alerta de {% data variables.product.prodname_codeql %} como um resultado falso positivo, por exemplo, porque o código usa uma biblioteca de sanitização que não é compatível, considere contribuir para o repositório de {% data variables.product.prodname_codeql %} e melhorar a análise. Para obter mais informações sobre {% data variables.product.prodname_codeql %}, consulte "[Contribuir para {% data variables.product.prodname_codeql %}](https://github.com/github/codeql/blob/main/CONTRIBUTING.md)". diff --git a/translations/pt-BR/data/reusables/community/interaction-limits-duration.md b/translations/pt-BR/data/reusables/community/interaction-limits-duration.md index fb858accd8..fe69e2730e 100644 --- a/translations/pt-BR/data/reusables/community/interaction-limits-duration.md +++ b/translations/pt-BR/data/reusables/community/interaction-limits-duration.md @@ -1 +1 @@ -When you enable an interaction limit, you can choose a duration for the limit: 24 hours, 3 days, 1 week, 1 month, or 6 months. \ No newline at end of file +Ao habilitar um limite de interação, você pode escolher uma duração para o limite: 24 horas, 3 dias, 1 semana, 1 mês ou 6 meses. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/community/interaction-limits-restrictions.md b/translations/pt-BR/data/reusables/community/interaction-limits-restrictions.md index 1be2648d16..cae683fb44 100644 --- a/translations/pt-BR/data/reusables/community/interaction-limits-restrictions.md +++ b/translations/pt-BR/data/reusables/community/interaction-limits-restrictions.md @@ -1 +1 @@ -Enabling an interaction limit for a repository restricts certain users from commenting, opening issues, creating pull requests, reacting with emojis, editing existing comments, and editing titles of issues and pull requests. \ No newline at end of file +Habilitar um limite de interação para um repositório restringe certos usuários de comentar, abrir problemas, criar pull requests, reagir com emojis, editar comentários existentes e editar títulos de problemas e pull requests. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/community/set-interaction-limit.md b/translations/pt-BR/data/reusables/community/set-interaction-limit.md index 468a068f70..1ee2ae1e85 100644 --- a/translations/pt-BR/data/reusables/community/set-interaction-limit.md +++ b/translations/pt-BR/data/reusables/community/set-interaction-limit.md @@ -1 +1 @@ -5. Under "Temporary interaction limits", to the right of the type of interaction limit you want to set, use the **Enable** drop-down menu, then click the duration you want for your interaction limit. \ No newline at end of file +5. Em "Limites de interação temporária", à direita do tipo de limite de interação que você deseja definir, use o menu suspenso **Habilitar** e, em seguida, clique na duração que você deseja para o seu limite de interação. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/community/types-of-interaction-limits.md b/translations/pt-BR/data/reusables/community/types-of-interaction-limits.md index 4df9215f12..b440b1f2df 100644 --- a/translations/pt-BR/data/reusables/community/types-of-interaction-limits.md +++ b/translations/pt-BR/data/reusables/community/types-of-interaction-limits.md @@ -1,4 +1,4 @@ -There are three types of interaction limits. +Existem três tipos de limites de interação. - **Limit to existing users** (Restringir a usuários existentes): restringe a atividade para usuários com contas que tenham sido criadas há menos de 24 horas, que não tenham contribuições prévias e que não sejam colaboradores. - - **Limit to prior contributors**: Limits activity for users who have not previously contributed to the default branch of the repository and are not collaborators. - - **Limit to repository collaborators**: Limits activity for users who do not have write access to the repository. \ No newline at end of file + - **Limitar os contribuidores anteriores**: Limita a atividade de usuários que não contribuíram anteriormente para o branch padrão do repositório e não são contribuidores. + - **Limitar os colaboradores do repositório**: Limita a atividade de usuários que não têm acesso de gravação ao repositório. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-accounts-billing.md b/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-accounts-billing.md index b7ef65c1d8..6c82020fd0 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-accounts-billing.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-accounts-billing.md @@ -1 +1 @@ -As contas corporativas estão disponíveis com {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %} clientes pagando por fatura. O faturamento para todas as organizações e {% data variables.product.prodname_ghe_server %} instâncias conectadas à sua conta corporativa é agregado em uma única fatura. Para obter mais informações, sobre como gerenciar sua assinatura do {% data variables.product.prodname_ghe_cloud %} consulte "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." For more information about managing your {% data variables.product.prodname_ghe_server %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +As contas corporativas estão disponíveis com {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %} clientes pagando por fatura. O faturamento para todas as organizações e {% data variables.product.prodname_ghe_server %} instâncias conectadas à sua conta corporativa é agregado em uma única fatura. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/options-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/options-tab.md index 447d2147fa..17ff9a93cc 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/options-tab.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/options-tab.md @@ -1 +1 @@ -1. Under {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} {% octicon "law" aria-label="The law icon" %} **Policies**{% else %}"{% octicon "gear" aria-label="The Settings gear" %} Settings"{% endif %}, click **Options**. ![Aba Opções na barra lateral de configurações da conta corporativa](/assets/images/enterprise/business-accounts/settings-options-tab.png) +1. Em {% if currentVersion ver_gt "enterprise-server@2. 1" ou versão atual == "github-ae@latest" %} {% octicon "law" aria-label="The law icon" %} **Políticas**{% else %}"{% octicon "gear" aria-label="The Settings gear" %} Configurações"{% endif %}, clique em **Opções**. ![Aba Opções na barra lateral de configurações da conta corporativa](/assets/images/enterprise/business-accounts/settings-options-tab.png) diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/pages-policies-save.md b/translations/pt-BR/data/reusables/enterprise-accounts/pages-policies-save.md index 2a45283ec5..1a1e935a08 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/pages-policies-save.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/pages-policies-save.md @@ -1 +1 @@ - 6. Clique em **Salvar**. ![Save button](/assets/images/enterprise/business-accounts/pages-policies-save-button.png) + 6. Clique em **Salvar**. ![Botão Salvar](/assets/images/enterprise/business-accounts/pages-policies-save-button.png) diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/pages-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/pages-tab.md index 5d9fb29f64..afb8cb70ae 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/pages-tab.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/pages-tab.md @@ -1 +1 @@ -1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Pages**. ![Pages tab in the enterprise sidebar](/assets/images/enterprise/business-accounts/pages-tab.png) \ No newline at end of file +1. Em "Políticas de {% octicon "law" aria-label="The law icon" %}", clique em **Páginas**. ![Aba de páginas na barra lateral da empresa](/assets/images/enterprise/business-accounts/pages-tab.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-managed/about-billing.md b/translations/pt-BR/data/reusables/enterprise-managed/about-billing.md index 9e7ed843b2..b050287c65 100644 --- a/translations/pt-BR/data/reusables/enterprise-managed/about-billing.md +++ b/translations/pt-BR/data/reusables/enterprise-managed/about-billing.md @@ -1 +1 @@ -You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file +Você receberá uma conta mensal para {% data variables.product.prodname_ghe_managed %}, com taxas calculadas por usuário licenciado por dia. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise/rate_limit.md b/translations/pt-BR/data/reusables/enterprise/rate_limit.md index 270fbdcb89..2aace6cfa0 100644 --- a/translations/pt-BR/data/reusables/enterprise/rate_limit.md +++ b/translations/pt-BR/data/reusables/enterprise/rate_limit.md @@ -1,4 +1,4 @@ {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -Note that the limits mentioned above are the default rate limits for +Observe que os limites mencionados acima são os limites de taxa padrão para {% data variables.product.product_name %}. Entre em contato com o administrador do site para confirmar se os limites de taxa estão habilitados e como eles estão configurados. {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md index 2c5a7a83dd..4029c84072 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,37 @@ -{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance types. For more information, see [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). +{% data variables.product.prodname_ghe_server %} é suportado nos seguintes tipos de instância do EC2. Para obter mais informações, consulte [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). -| EC2 instance type | Model | -| ----------------- | ----- | -| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | ---------------------------------- | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | -| EC2 instance type | Model | -| ----------------- | ----- | -| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | ---------------------------------- | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | -| EC2 instance type | Model | -| ----------------- | ----- | -| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | -------------------------------------------------------------------- | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | -| EC2 instance type | Model | -| ----------------- | ----- | -| M3 | m3.xlarge, m3.2xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | --------------------- | +| M3 | m3.xlarge, m3.2xlarge | -| EC2 instance type | Model | -| ----------------- | ----- | -| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | ----------------------------------------------------------- | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | -| EC2 instance type | Model | -| ----------------- | ----- | -| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | --------------------------------------------------------------------- | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | -| EC2 instance type | Model | -| ----------------- | ----- | -| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | -------------------------------------------------------------------- | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | -| EC2 instance type | Model | -| ----------------- | ----- | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} | +| Tipo de instância EC2 | Modelo | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} -| EC2 instance type | Model | -| ----------------- | ----- | -| X1 | x1.16xlarge, x1.32xlarge | +| Tipo de instância EC2 | Modelo | +| --------------------- | ------------------------ | +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/pt-BR/data/reusables/enterprise_installation/disable-github-pages-warning.md b/translations/pt-BR/data/reusables/enterprise_installation/disable-github-pages-warning.md index ecac6ccacb..86ebb49ed2 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/disable-github-pages-warning.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/disable-github-pages-warning.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion %} {% warning %} -**Warning:** If subdomain isolation is disabled, we recommend also disabling {% data variables.product.prodname_pages %} on your enterprise. There will be no way to isolate user-supplied {% data variables.product.prodname_pages %} content from the rest of your enterprise's data. For more information, see "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/)." +**Aviso:** Se o isolamento de subdomínio estiver desabilitar, recomendamos também desabilitar {% data variables.product.prodname_pages %} na sua empresa. Não haverá forma de isolar o conteúdo {% data variables.product.prodname_pages %} fornecido pelo usuário dos dados da sua empresa. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_pages %} para a sua empresa](/enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/)". {% endwarning %} {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 8be5328b6e..41ce997740 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,4 +1,5 @@ - [Requisitos mínimos](#minimum-requirements) +- [Recursos do beta em {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222) - [Armazenamento](#storage) - [CPU e memória](#cpu-and-memory) @@ -6,23 +7,18 @@ Recomendamos diferentes configurações de hardware, dependendo do número de licenças de usuário para {% data variables.product.product_location %}. Se você fornecer mais recursos do que os requisitos mínimos, sua instância terá um desempenho e uma escala melhores. -{% data reusables.enterprise_installation.hardware-rec-table %} Para obter mais informações sobre o ajuste de recursos para uma instância existente, consulte "[aumentar a capacidade de armazenamento](/enterprise/admin/installation/increasing-storage-capacity)" e "[aumentar recursos de CPU ou memória](/enterprise/admin/installation/increasing-cpu-or-memory-resources)". - -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} - -Se você habilitar o beta para {% data variables.product.prodname_actions %} na sua instância, recomendamos que você planeje uma capacidade adicional. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. - Você deve configurar pelo menos um executor para fluxos de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)." - Você deve configurar o armazenamento externo do blob. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. -Os recursos adicionais de CPU e memória que você precisa fornecer para a sua instância dependem do número de fluxos de trabalho que os seus usuários executam simultaneamente e dos níveis gerais de atividade para usuários, automações, e integrações. - -| Máximo de trabalhos por minuto | vCPUs | Memória | -|:------------------------------ | -----:| -------:| -| Testes rápidos | 4 | 30.5 GB | -| 25 | 8 | 61 GB | -| 35 | 16 | 122 GB | -| 100 | 32 | 244 GB | + | Máximo de trabalhos por minuto | Additional vCPUs | Additional memory | + |:------------------------------ | ----------------:| -----------------:| + | Testes rápidos | 4 | 30.5 GB | + | 25 | 8 | 61 GB | + | 35 | 16 | 122 GB | + | 100 | 32 | 244 GB | {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md index 99ef1b0347..cf565549b2 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,6 +1,12 @@ {% if currentVersion == "enterprise-server@2.22" %} -Os requisitos mínimos para uma instância com recursos beta habilitados estão em **negrito** na tabela a seguir. Para obter mais informações, consulte "[Recursos Beta em {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)". |{% endif %} +{% note %} + +**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Os requisitos mínimos para uma instância com recursos beta habilitados estão em **negrito** na tabela a seguir. For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." + +{% endnote %} +| +{% endif %} | Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | |:---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ------------------:| | Teste, demonstração ou 10 usuários leves | 2{% if currentVersion == "enterprise-server@2.22" %}
ou [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
ou [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
ou [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -9,8 +15,14 @@ Os requisitos mínimos para uma instância com recursos beta habilitados estão | 5000-8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
ou [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8000-10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
ou [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
ou [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | +For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." + {% if currentVersion == "enterprise-server@2.22" %} #### Recursos do beta em {% data variables.product.prodname_ghe_server %} 2.22 -Se você habilitar os recursos beta em {% data variables.product.prodname_ghe_server %} 2.22, a sua instância exigirá recursos adicionais de hardware. Para obter mais informações sobre os recursos beta, consulte as [notas de versão para as séries 2.22](https://enterprise.github.com/releases/series/2.22) no site de {% data variables.product.prodname_enterprise %} .{% endif %} +You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website. + +If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". + +{% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md index fd2e0a2be2..2a26ad6d64 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Aviso:** Se você adicionar um anexo de imagem a uma pull request ou comentário de problema, qualquer um pode ver a URL de imagem anônima sem autenticação, mesmo se a pull request estiver em um repositório privado, ou se o modo privado estiver ativado. Para manter imagens confidenciais privadas, use uma rede privada ou um servidor que requer autenticação. +**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% if enterpriseServerVersions contains currentVersion %}, even if the pull request is in a private repository, or if private mode is enabled. To prevent unauthorized access to the images, ensure that you restrict network access to the systems that serve the images, including {% data variables.product.product_location %}{% endif %}.{% if currentVersion == "github-ae@latest" %} To prevent unauthorized access to image URLs on {% data variables.product.product_name %}, consider restricting network traffic to your enterprise. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."{% endif %} {% endwarning %} diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-code-scanning.md b/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-code-scanning.md index 810fa55aa1..1e053507af 100644 --- a/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-code-scanning.md +++ b/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-code-scanning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: Changing this setting will cause {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} to restart. Você deve programar essa mudança com cuidado para minimizar o tempo de inatividade. +**Aviso**: Alterar essa configuração fará com que {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} seja reiniciado. Você deve programar essa mudança com cuidado para minimizar o tempo de inatividade. {% endwarning %} diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-ssh-access.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-ssh-access.md index 4e1057532c..a20ac048aa 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-ssh-access.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-ssh-access.md @@ -1 +1 @@ -SSH access allows you to run the {% data variables.product.product_name %} command line utilities to troubleshoot, run backups, and configure replication. \ No newline at end of file +O acesso de SSH permite que você execute os utilitários da linha de comando de {% data variables.product.product_name %} para solucionar problemas, executar backups e configurar a replicação. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-management-console.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-management-console.md index 8c622226c6..2f723d3b6c 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-management-console.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-management-console.md @@ -1 +1 @@ -You can use the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL. \ No newline at end of file +Você pode usar {% data variables.enterprise.management_console %} para gerenciar configurações dos aplicativos virtuais, como o domínio, autenticação e SSL. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md index bab0827c40..0a70f217e6 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md @@ -1 +1 @@ -You can use the site admin dashboard to manage users, organizations, and repositories in your enterprise directly in {% data variables.product.product_name %}. \ No newline at end of file +Você pode usar o painel de administração do site para gerenciar usuários, organizações e repositórios diretamente na sua empresa em {% data variables.product.product_name %}. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/access-settings.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/access-settings.md index 3d344da670..ab27b5a3c8 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/access-settings.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/access-settings.md @@ -1 +1 @@ -1. From an administrative account on {% data variables.product.product_name %}, click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. A partir de uma conta administrativa em {% data variables.product.product_name %}, clique em {% octicon "rocket" aria-label="The rocket ship" %} no canto superior direito de qualquer página. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png) diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md index 227f36c0dc..727552ef5d 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md @@ -1 +1 @@ -1. In the left sidebar, click **Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %}**. ![Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %} tab in the Site admin settings](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) +1. Na barra lateral esquerda, clique em **Empresa{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} visão geral{% endif %}**. ![Aba de {% if currentVersion ver_gt "enterprise-server@2.21" ou currentVersion == "github-ae@latest" %} visão geral da empresa{% endif %} nas configurações de administrador do site.](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) diff --git a/translations/pt-BR/data/reusables/gated-features/autolinks.md b/translations/pt-BR/data/reusables/gated-features/autolinks.md index d545d6a5b4..248adcd09b 100644 --- a/translations/pt-BR/data/reusables/gated-features/autolinks.md +++ b/translations/pt-BR/data/reusables/gated-features/autolinks.md @@ -1 +1 @@ -Autolinks are available in repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +Os links automáticos estão disponíveis em repositórios com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/branch-restrictions.md b/translations/pt-BR/data/reusables/gated-features/branch-restrictions.md index 256549fb22..f5dee9b5c6 100644 --- a/translations/pt-BR/data/reusables/gated-features/branch-restrictions.md +++ b/translations/pt-BR/data/reusables/gated-features/branch-restrictions.md @@ -1,3 +1,3 @@ {% data reusables.gated-features.protected-branches %}
-Branch restriction is a type of branch protection that's available for public and private repositories owned by organizations in {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +A restrição de branch é um tipo de proteção de branch disponível para repositórios públicos e privados pertencentes a organizações em {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/code-owners.md b/translations/pt-BR/data/reusables/gated-features/code-owners.md index 3dc4547af8..686007cbd5 100644 --- a/translations/pt-BR/data/reusables/gated-features/code-owners.md +++ b/translations/pt-BR/data/reusables/gated-features/code-owners.md @@ -1 +1 @@ -You can define code owners in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +Você pode definir proprietários de códigos em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/code-review-assignment.md b/translations/pt-BR/data/reusables/gated-features/code-review-assignment.md index 2cf8f15764..c7c93bed33 100644 --- a/translations/pt-BR/data/reusables/gated-features/code-review-assignment.md +++ b/translations/pt-BR/data/reusables/gated-features/code-review-assignment.md @@ -1 +1 @@ -Code review assignment is available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.20+,{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". +O atribuição de revisão do código está disponível com {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.20+{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". diff --git a/translations/pt-BR/data/reusables/gated-features/code-scanning.md b/translations/pt-BR/data/reusables/gated-features/code-scanning.md index 2bcd80c1d4..328f24279e 100644 --- a/translations/pt-BR/data/reusables/gated-features/code-scanning.md +++ b/translations/pt-BR/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_code_scanning_capc %} está disponível {% if currentVersion == "free-pro-team@latest" %}em repositórios públicos, e em repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.gated-features.more-info %} diff --git a/translations/pt-BR/data/reusables/gated-features/display-names.md b/translations/pt-BR/data/reusables/gated-features/display-names.md index e6c3fb57f0..4a741bd450 100644 --- a/translations/pt-BR/data/reusables/gated-features/display-names.md +++ b/translations/pt-BR/data/reusables/gated-features/display-names.md @@ -1 +1 @@ -Allowing members to see comment authors' profile names is available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.18+,{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". +Permitir que os integrantes vejam os nomes de perfis dos autores de comentários está disponível com {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2. {% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". diff --git a/translations/pt-BR/data/reusables/gated-features/draft-prs.md b/translations/pt-BR/data/reusables/gated-features/draft-prs.md index 9c53c6d6c0..440927563c 100644 --- a/translations/pt-BR/data/reusables/gated-features/draft-prs.md +++ b/translations/pt-BR/data/reusables/gated-features/draft-prs.md @@ -1 +1 @@ -Draft pull requests are available in public repositories with {% data variables.product.prodname_free_team %} for organizations and legacy per-repository billing plans, and in public and private repositories with {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.17+,{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +Rascunhos de pull requests estão disponíveis em repositórios públicos com {% data variables.product.prodname_free_team %} para organizações e planos de cobrança de legados por repositório, e em repositórios públicos e privados com {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2. 7+{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md b/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md index 2206582f7c..9810e65e6a 100644 --- a/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md +++ b/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md @@ -1 +1 @@ -Enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}Para obter mais informações, consulte "[Sobre contas corporativas](/articles/about-enterprise-accounts)."{% endif %} +As contas empresariais estão disponíveis com {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}Para obter mais informações, consulte "[Sobre contas corporativas](/articles/about-enterprise-accounts)."{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/internal-repos.md b/translations/pt-BR/data/reusables/gated-features/internal-repos.md index 317442554b..a9a4197a2a 100644 --- a/translations/pt-BR/data/reusables/gated-features/internal-repos.md +++ b/translations/pt-BR/data/reusables/gated-features/internal-repos.md @@ -1 +1 @@ -Internal repositories are available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 2.20+. Para obter mais informações, consulte os "Produtos do GitHub". +Os repositórios internos estão disponíveis com {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %} 2.20+. Para obter mais informações, consulte os "Produtos do GitHub". diff --git a/translations/pt-BR/data/reusables/gated-features/pages.md b/translations/pt-BR/data/reusables/gated-features/pages.md index e24925cc98..31caf392d2 100644 --- a/translations/pt-BR/data/reusables/gated-features/pages.md +++ b/translations/pt-BR/data/reusables/gated-features/pages.md @@ -1 +1 @@ -{% data variables.product.prodname_pages %} is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_pages %} is available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}. {% endif %}{% data variables.product.prodname_pages %} is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/protected-branches.md b/translations/pt-BR/data/reusables/gated-features/protected-branches.md index a9745fcec2..6cbe4e3a9f 100644 --- a/translations/pt-BR/data/reusables/gated-features/protected-branches.md +++ b/translations/pt-BR/data/reusables/gated-features/protected-branches.md @@ -1 +1 @@ -Protected branches are available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +Os branches protegidos estão disponíveis em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/repository-insights.md b/translations/pt-BR/data/reusables/gated-features/repository-insights.md index 71016e9f96..4c9787ab57 100644 --- a/translations/pt-BR/data/reusables/gated-features/repository-insights.md +++ b/translations/pt-BR/data/reusables/gated-features/repository-insights.md @@ -1 +1 @@ -This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[About repository graphs](/articles/about-repository-graphs)" and "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)."{% endif %} +Este gráfico de informações do repositório está disponível em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} Para mais informações, consulte "[Sobre gráficos do repositório](/articles/about-repository-graphs)" e "[ produtos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products).{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/saml-sso.md b/translations/pt-BR/data/reusables/gated-features/saml-sso.md index f46b2116c5..9b457b73d5 100644 --- a/translations/pt-BR/data/reusables/gated-features/saml-sso.md +++ b/translations/pt-BR/data/reusables/gated-features/saml-sso.md @@ -1 +1 @@ -SAML single sign-on is available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} and {% data variables.product.prodname_ghe_managed %}{% endif %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". +O logon único do SAML está disponível com {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} e {% data variables.product.prodname_ghe_managed %}{% endif %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". diff --git a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md index bd279034ee..5f48619eca 100644 --- a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md +++ b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} está disponível em repositórios públicos e em repositórios privados pertencentes a organizações com uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.gated-features.more-info %} diff --git a/translations/pt-BR/data/reusables/gated-features/ssh-certificate-authorities.md b/translations/pt-BR/data/reusables/gated-features/ssh-certificate-authorities.md index a1507d33b0..48c358f167 100644 --- a/translations/pt-BR/data/reusables/gated-features/ssh-certificate-authorities.md +++ b/translations/pt-BR/data/reusables/gated-features/ssh-certificate-authorities.md @@ -1 +1 @@ -Support for SSH certificate authorities is available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 2.19+. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". +O suporte para autoridades certificadas de SSH está disponível com {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %} 2.19+. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". diff --git a/translations/pt-BR/data/reusables/gated-features/wikis.md b/translations/pt-BR/data/reusables/gated-features/wikis.md index 61f560896e..d7611dc363 100644 --- a/translations/pt-BR/data/reusables/gated-features/wikis.md +++ b/translations/pt-BR/data/reusables/gated-features/wikis.md @@ -1 +1 @@ -Wikis are available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}Wikis are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}.{% endif %} Wikis are available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md b/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md index 3d1f2c249f..91a1d50e6c 100644 --- a/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -By default, {% if currentVersion ver_gt "enterprise-server@2.21" %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. Você pode optar por desabilitar {% data variables.product.prodname_actions %} ou limitá-los apenas a ações privadas, o que significa que as pessoas só poderão usar ações que existem no seu repositório. +Por padrão, {% if currentVersion ver_gt "enterprise-server@2. 1" %}depois que {% data variables.product.prodname_actions %} está habilitado em {% data variables.product.product_location %}, ele{% elsif currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_actions %}{% endif %} fica habilitado em todos os repositórios e organizações. Você pode optar por desabilitar {% data variables.product.prodname_actions %} ou limitá-los apenas a ações privadas, o que significa que as pessoas só poderão usar ações que existem no seu repositório. diff --git a/translations/pt-BR/data/reusables/github-actions/enabled-local-github-actions.md b/translations/pt-BR/data/reusables/github-actions/enabled-local-github-actions.md index 0043c8e960..f568f1dfd9 100644 --- a/translations/pt-BR/data/reusables/github-actions/enabled-local-github-actions.md +++ b/translations/pt-BR/data/reusables/github-actions/enabled-local-github-actions.md @@ -1 +1 @@ -When you enable local actions only, workflows can only run actions located in your repository, organization, or enterprise. +Ao habilitar apenas ações locais, os fluxos de trabalho só podem executar ações localizadas em seu repositório, organização ou empresa. diff --git a/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md b/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md index 88a2d482c4..4d2509b3ea 100644 --- a/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The MacOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the MacOS 10.15 virtual environment. +**Nota:** O ambiente virtual do MacOS 11.0 é atualmente fornecido apenas como visualização. A etiqueta do fluxo de trabalho do YAML `macos-latest` ainda usa o ambiente virtual do MacOS 10.15. {% endnote %} diff --git a/translations/pt-BR/data/reusables/github-actions/matrix-variable-example.md b/translations/pt-BR/data/reusables/github-actions/matrix-variable-example.md new file mode 100644 index 0000000000..ce6e9d6d24 --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/matrix-variable-example.md @@ -0,0 +1,26 @@ +In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: + +{% raw %} +```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - node-version: 10.x + site: "prod" + datacenter: "site-a" + - node-version: 12.x + site: "dev" + datacenter: "site-b" + steps: + - name: Echo site details + env: + SITE: ${{ matrix.site }} + DATACENTER: ${{ matrix.datacenter }} + run: echo $SITE $DATACENTER +``` +{% endraw %} diff --git a/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-api.md index 8189a80590..76208aef1b 100644 --- a/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-api.md +++ b/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-api.md @@ -1 +1 @@ -Para criar segredos usando a API REST, você deve ter acesso de gravação ao repositório ou acesso de administrador à organização. Para obter mais informações, consulte "[{% data variables.product.prodname_actions %} secrets API](/v3/actions/secrets/)." +Para criar segredos usando a API REST, você deve ter acesso de gravação ao repositório ou acesso de administrador à organização. Para obter mais informações, consulte "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)." diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 1ab4125c5e..dd19a6a1c0 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,2 +1,12 @@ 1. Na seção **Runners auto-hospedados** da página de configurações, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} ao lado do grupo de runner que deseja configurar, em seguida, clique em **Editar nome e acessar [organização|repositório]**. ![Gerenciar permissões do repositório](/assets/images/help/settings/actions-runner-manage-permissions.png) -1. Selecione uma nova política a partir da lista suspensa ou modifique o nome do grupo de runner. +1. Modify your policy options, or change the runner group name. + + {% warning %} + + **Aviso** + + {% indented_data_reference site.data.reusables.github-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 %} 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 index a292c7c053..9ddc7c7b5c 100644 --- 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 @@ -1,9 +1,9 @@ -A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} enterprise settings on {% 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. +A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} 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. {% if currentVersion == "free-pro-team@latest" %} -- **Conta corporativa**: Você deve ser proprietário de uma empresa. +- **Enterprise account**: You must be an enterprise owner. {% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} -- **Empresa**: Você deve ser um administrador do site de {% data variables.product.prodname_enterprise %} +- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator. {% endif %} 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/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 537d362767..12756c93a0 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -1,12 +1,12 @@ -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**. +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**. * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**: - - 1. No canto superior direito de qualquer página, clique em {% octicon "rocket" aria-label="The rocket ship" %}. - 1. Na barra lateral esquerda, clique em **Visão geral da empresa**. - 1. {% endif %} Na barra lateral da empresa, {% octicon "law" aria-label="The law icon" %} **Políticas**. -1. Navegue até as configurações {% data variables.product.prodname_actions %}: - * **Em uma organização ou um repositório**: clique em **Ações** na barra lateral esquerda. - - ![Configuração de ações](/assets/images/help/settings/settings-sidebar-actions.png) + + 1. In the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}. + 1. In the left sidebar, click **Enterprise overview**. + 1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**. +1. Navigate to the {% data variables.product.prodname_actions %} settings: + * **In an organization or repository**: click **Actions** in the left sidebar. + + ![Actions setting](/assets/images/help/settings/settings-sidebar-actions.png) * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies". diff --git a/translations/pt-BR/data/reusables/github-ae/about-billing.md b/translations/pt-BR/data/reusables/github-ae/about-billing.md index 9e7ed843b2..b050287c65 100644 --- a/translations/pt-BR/data/reusables/github-ae/about-billing.md +++ b/translations/pt-BR/data/reusables/github-ae/about-billing.md @@ -1 +1 @@ -You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file +Você receberá uma conta mensal para {% data variables.product.prodname_ghe_managed %}, com taxas calculadas por usuário licenciado por dia. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/github-ae/github-ae-enables-you.md b/translations/pt-BR/data/reusables/github-ae/github-ae-enables-you.md index dd699d9ad6..e310ffb1cf 100644 --- a/translations/pt-BR/data/reusables/github-ae/github-ae-enables-you.md +++ b/translations/pt-BR/data/reusables/github-ae/github-ae-enables-you.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_managed %} enables you to move your software development to the cloud while meeting the most stringent security and compliance requirements. +{% data variables.product.prodname_ghe_managed %} permite que você mova o desenvolvimento do seu software para a nuvem ao mesmo tempo que satisfaz os requisitos de segurança e conformidade mais rigorosos. diff --git a/translations/pt-BR/data/reusables/github-insights/contributors-tab.md b/translations/pt-BR/data/reusables/github-insights/contributors-tab.md index ec5a09cb99..19ccc2d1e4 100644 --- a/translations/pt-BR/data/reusables/github-insights/contributors-tab.md +++ b/translations/pt-BR/data/reusables/github-insights/contributors-tab.md @@ -1 +1 @@ -1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Contributors**. ![Aba de colaboradores](/assets/images/help/insights/contributors-tab.png) +1. Em **Configurações de {% octicon "gear" aria-label="The gear icon" %}**, clique em **Contribuidores**. ![Aba de colaboradores](/assets/images/help/insights/contributors-tab.png) diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 46650d58b8..2abfe22fcf 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -Depois que você ativar a sincronização de equipe, os mantenedores de equipe e os proprietários da organização poderão conectar uma equipe a um grupo de IdP no {% data variables.product.prodname_dotcom %} ou através da API. Para obter mais informações, consulte "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" e "[Team synchronization](/v3/teams/team_sync/)." +Depois que você ativar a sincronização de equipe, os mantenedores de equipe e os proprietários da organização poderão conectar uma equipe a um grupo de IdP no {% data variables.product.prodname_dotcom %} ou através da API. Para obter mais informações, consulte "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" e "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/pt-BR/data/reusables/interactions/interactions-detail.md b/translations/pt-BR/data/reusables/interactions/interactions-detail.md index 187a3e7307..75fa30b2ac 100644 --- a/translations/pt-BR/data/reusables/interactions/interactions-detail.md +++ b/translations/pt-BR/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -When restrictions are enabled, only the specified type of {% data variables.product.product_name %} user will be able to participate in interactions. Restrictions automatically expire after a defined duration. +Quando as restrições são habilitadas, apenas o tipo especificado de usuário de {% data variables.product.product_name %} poderá participar das interações. As restrições expiram automaticamente após uma duração definida. diff --git a/translations/pt-BR/data/reusables/issue-events/issue-event-common-properties.md b/translations/pt-BR/data/reusables/issue-events/issue-event-common-properties.md index c92fc00381..e4efaa9c21 100644 --- a/translations/pt-BR/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/pt-BR/data/reusables/issue-events/issue-event-common-properties.md @@ -1,7 +1,7 @@ | Nome | Tipo | Descrição | | ------------ | --------- | ---------------------------------------------------------------------- | | `id` | `inteiro` | O identificador exclusivo do evento. | -| `node_id` | `string` | O [ID de nó global](/v4/guides/using-global-node-ids) do evento. | +| `node_id` | `string` | O [Global Node ID](/graphql/guides/using-global-node-ids) do evento. | | `url` | `string` | A URL da API REST para buscar o evento. | | `actor` | `objeto` | A pessoa que gerou o evento. | | `event` | `string` | Identifica o tipo atual do evento que ocorreu. | diff --git a/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md index 2182ad39f7..1bac09c271 100644 --- a/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md @@ -1,6 +1,6 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} Você pode escolher se -{% data variables.large_files.product_name_short %} objects are included in source code archives, such as ZIP files and tarballs, that {% data variables.product.product_name %} creates for your repository. Para obter mais informações, consulte " +Os objetos de {% data variables.large_files.product_name_short %} estão incluídos nos arquivos do código-fonte, como arquivos ZIP e tarballs, que {% data variables.product.product_name %} cria para o seu repositório. Para obter mais informações, consulte " [Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

{% endif %} diff --git a/translations/pt-BR/data/reusables/large_files/rejected_pushes.md b/translations/pt-BR/data/reusables/large_files/rejected_pushes.md index 4d04d4d367..cd3d5bdb68 100644 --- a/translations/pt-BR/data/reusables/large_files/rejected_pushes.md +++ b/translations/pt-BR/data/reusables/large_files/rejected_pushes.md @@ -1 +1 @@ -Users cannot push {% data variables.large_files.product_name_short %} assets to {% data variables.product.product_name %} if {% data variables.large_files.product_name_short %} is disabled on the enterprise or repository. +Os usuários não podem fazer push de ativos de {% data variables.large_files.product_name_short %} para {% data variables.product.product_name %} se {% data variables.large_files.product_name_short %} estiver desabilitado na empresa ou no repositório. diff --git a/translations/pt-BR/data/reusables/large_files/storage_assets_location.md b/translations/pt-BR/data/reusables/large_files/storage_assets_location.md index cb76cf1bcf..baf91ac72b 100644 --- a/translations/pt-BR/data/reusables/large_files/storage_assets_location.md +++ b/translations/pt-BR/data/reusables/large_files/storage_assets_location.md @@ -1,4 +1,4 @@ {% if enterpriseServerVersions contains currentVersion %} -By default, the -{% data variables.large_files.product_name_long %} client stores large assets on the same server that hosts the Git repository. When {% data variables.large_files.product_name_short %} is enabled on {% data variables.product.product_location %}, large assets are stored on the data partition in `/data/user/storage`. +Por padrão, o +cliente de {% data variables.large_files.product_name_long %} armazena grandes ativos no mesmo servidor que hospeda o repositório do Git. Quando {% data variables.large_files.product_name_short %} está habilitado em {% data variables.product.product_location %}, os grandes ativos são armazenados na partição de dados em `/data/user/storage`. {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/marketplace/downgrade-marketplace-only.md b/translations/pt-BR/data/reusables/marketplace/downgrade-marketplace-only.md index 22876b1dab..83777a165c 100644 --- a/translations/pt-BR/data/reusables/marketplace/downgrade-marketplace-only.md +++ b/translations/pt-BR/data/reusables/marketplace/downgrade-marketplace-only.md @@ -1 +1 @@ -Canceling an app or downgrading an app to free does not affect your [other paid subscriptions](/articles/about-billing-on-github) on {% data variables.product.prodname_dotcom %}. Se você quiser cessar todas as assinaturas pagas do {% data variables.product.prodname_dotcom %}, precisa fazer downgrade de cada uma delas separadamente. +Cancelar um aplicativo ou fazer o downgrade de um aplicativo para gratuito não afeta [outras assinaturas pagas](/articles/about-billing-on-github) em {% data variables.product.prodname_dotcom %}. Se você quiser cessar todas as assinaturas pagas do {% data variables.product.prodname_dotcom %}, precisa fazer downgrade de cada uma delas separadamente. diff --git a/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md b/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md index c6ce268450..d03a58ca8c 100644 --- a/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md +++ b/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md @@ -1,7 +1,9 @@ -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - {% tip %} +{% if enterpriseServerVersions contains currentVersion %} - Você só receberá notificações por e-mail se o suporte a e-mails de saída estiver ativado no {% data variables.product.product_location %}. Para mais informações, entre em contato com o administrador do site. +{% note %} + +**Note**: You'll only receive email notifications if outbound email support is enabled on {% data variables.product.product_location %}. Para mais informações, entre em contato com o administrador do site. + +{% endnote %} - {% endtip %} {% endif %} diff --git a/translations/pt-BR/data/reusables/notifications/shared_state.md b/translations/pt-BR/data/reusables/notifications/shared_state.md index 8a3ac4ce0e..23fdfcbd26 100644 --- a/translations/pt-BR/data/reusables/notifications/shared_state.md +++ b/translations/pt-BR/data/reusables/notifications/shared_state.md @@ -1,5 +1,5 @@ {% tip %} -**Dica:** se você receber notificações da web e por e-mail, você pode sincronizar automaticamente o status lido ou não lido da notificação para que as notificações da web sejam automaticamente marcadas como lidas depois de ler a notificação de e-mail correspondente. Para habilitar essa sincronização, o cliente de e-mail deve ser capaz de visualizar imagens de {% if currentVersion == "free-pro-team@latest" %}'`notifications@github. om`'{% else %}'o endereço de e-mail no-reply configurado pelo administrador do site'{% endif %}. +**Dica:** se você receber notificações da web e por e-mail, você pode sincronizar automaticamente o status lido ou não lido da notificação para que as notificações da web sejam automaticamente marcadas como lidas depois de ler a notificação de e-mail correspondente. To enable this sync, your email client must be able to view images from {% if currentVersion == "free-pro-team@latest" %}`notifications@github.com`{% else %}the `no-reply` email address {% if currentVersion == "github-ae@latest" %}for your {% data variables.product.product_name %} hostname{% elsif enterpriseServerVersions contains currentVersion %}for {% data variables.product.product_location %}, which your site administrator configures{% endif %}{% endif %}. {% endtip %} diff --git a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index 6b3de47d4c..ed551f5d2d 100644 --- a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,3 +1,3 @@ -You can choose the delivery method for notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you. +Você pode escolher o método de entrega para notificações sobre {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} em repositórios que você está inspecionando, bem como a frequência na qual as notificações são enviadas para você. diff --git a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md index 03451a3cac..6b1faa9eb5 100644 --- a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,33 +1,33 @@ {% if currentVersion == "free-pro-team@latest" %} -By default, you will receive notification of new +Por padrão, você receberá notificações das novas {% data variables.product.prodname_dependabot_alerts %}: -- by email, an email is sent every time a vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option) -- in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option) -- on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (**Command Line** option) -- in your inbox, as web notifications for new vulnerabilities with a critical or high severity (**Web** option) -You can customize the way you are notified about +- por e-mail, um e-mail é enviado toda vez que uma vulnerabilidade com uma gravidade crítica ou alta é encontrada (opção de **Enviar e-mail toda vez que uma vulnerabilidade for encontrada**) +- na interface do usuário, é exibido um aviso é nos arquivos e visualizações de código do seu repositório se houver quaisquer dependências vulneráveis (opção de **alertas de interface do usuário**) +- na linha de comando, são exibidos avisos como retornos de chamada quando você faz push em repositórios com quaisquer dependências vulneráveis (opção de **Linha de Comando**) +- na caixa de entrada, como notificações da web para novas vulnerabilidades com uma gravidade crítica ou alta (opção**Web**) +Você pode personalizar a forma como você é notificado -{% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the **Email a digest summary of vulnerabilities** and **Weekly security email digest** options. +{% data variables.product.prodname_dependabot_alerts %}. Por exemplo, você pode receber um e-mail semanal com o resumo dos alertas de até 10 de seus repositórios usando as opções **Enviar e-mail com o resumo das vulnerabilidades** e **Resumo semanal por e-mail sobre segurança**. {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} Por padrão, se o administrador do site tiver configurado e-mail para notificações na sua instância, você receberá {% data variables.product.prodname_dependabot_alerts %}: -- by email, an email is sent every time a vulnerability {% if currentVersion ver_gt "enterprise-server@2.23" %}with a critical or high severity {% endif %}is found (**Email each time a vulnerability is found** option) -- in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option) -- on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (**Command Line** option) -- in your inbox, as web notifications {% if currentVersion ver_gt "enterprise-server@2.23" %}for new vulnerabilities with a critical or high severity {% endif %}(**Web** option) -You can customize the way you are notified about +- por e-mail, um e-mail é enviado toda vez que uma vulnerabilidade {% if currentVersion ver_gt "enterprise-server@2. 3" %}com uma gravidade crítica ou alta {% endif %}é encontrada (opção de **Enviar e-mail toda vez que uma vulnerabilidade é encontrada**) +- na interface do usuário, é exibido um aviso é nos arquivos e visualizações de código do seu repositório se houver quaisquer dependências vulneráveis (opção de **alertas de interface do usuário**) +- na linha de comando, são exibidos avisos como retornos de chamada quando você faz push em repositórios com quaisquer dependências vulneráveis (opção de **Linha de Comando**) +- na sua caixa de entrada, como notificações da web {% if currentVersion ver_gt "enterprise-server@2. 3" %}para novas vulnerabilidades com uma gravidade crítica ou alta {% endif %}( opção**Web**) +Você pode personalizar a forma como você é notificado -{% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the **Email a digest summary of vulnerabilities** and **Weekly security email digest** options. +{% data variables.product.prodname_dependabot_alerts %}. Por exemplo, você pode receber um e-mail semanal com o resumo dos alertas de até 10 de seus repositórios usando as opções **Enviar e-mail com o resumo das vulnerabilidades** e **Resumo semanal por e-mail sobre segurança**. {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -By default, if your site administrator has configured email for notifications on your instance, you will receive security alerts: -- by email, an email is sent every time a vulnerability is found (**Email each time a vulnerability is found** option) -- in the user interface, as warnings in your repository's file and code views (**UI alerts** option) -- on the command line, as warnings that are displayed as callbacks when you push to repositories with vulnerabilities (**Command Line** option) -- in your inbox, as web notifications (**Web** option) +Por padrão, se o administrador do site configurou o e-mail para notificações na sua instância, você receberá alertas de segurança: +- por e-mail, um e-mail é enviado toda vez que uma vulnerabilidade é encontrada (opção de **Enviar e-mail toda vez que uma vulnerabilidade é encontrada**) +- na interface do usuário, como avisos nos arquivos e visualizações de código do seu repositório (opção de **alertas da interface do usuário**) +- na linha de comando, como avisos que são exibidos como retornos de chamada quando você faz push para repositórios com vulnerabilidades (opção de **Linha de Comando**) +- na sua caixa de entrada, como notificações da web (opção de **Web**) -You can customize the way you are notified about security alerts. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the **Email a digest summary of vulnerabilities** and **Weekly security email digest** options. +Você pode personalizar a forma como você é notificado sobre alertas de segurança. Por exemplo, você pode receber um e-mail semanal com o resumo dos alertas de até 10 de seus repositórios usando as opções **Enviar e-mail com o resumo das vulnerabilidades** e **Resumo semanal por e-mail sobre segurança**. {% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/organizations_include.md b/translations/pt-BR/data/reusables/organizations/organizations_include.md index b00ab5be7a..a43d34345a 100644 --- a/translations/pt-BR/data/reusables/organizations/organizations_include.md +++ b/translations/pt-BR/data/reusables/organizations/organizations_include.md @@ -3,6 +3,6 @@ As organizações incluem: - A opção de atualizar para {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %} para recursos adicionais, incluindo autenticação e gerenciamento sofisticados do usuário e opções de suporte escaladas. {% data reusables.gated-features.more-info %}{% endif %} - Associação ilimitada com uma variedade de funções que concedem [different levels of access to the organization and its data](/articles/permission-levels-for-an-organization) (diferentes níveis de acesso à organização e aos seus dados) - A capacidade de dar aos membros [a range of access permissions to your organization's repositories](/articles/repository-permission-levels-for-an-organization) (uma série de permissões de acesso aos repositórios da sua organização) -- [Nested teams that reflect your company or group's structure](/articles/about-teams) with cascading access permissions and mentions{% if currentVersion != "github-ae@latest" %} +- [Equipes aninhadas que refletem a estrutura da sua empresa ou grupo](/articles/about-teams) com permissões de acesso em cascata e menções {% if currentVersion != "github-ae@latest" %} - A capacidade para os proprietários da organização verem a autenticação de dois fatores [two-factor authentication (2FA) status](/articles/about-two-factor-authentication) (status de autenticação de dois fatores) -- The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +- A opção de [Exigir que todos os integrantes da organização usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md index 9f07a86efe..727ddc9db2 100644 --- a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md +++ b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ Os membros com permissões de mantenedor da equipe podem: - [Adicionar integrantes da organização à equipe](/articles/adding-organization-members-to-a-team) - [Remover membros da organização da equipe](/articles/removing-organization-members-from-a-team) - [Promover um membro da equipe existente para um mantenedor de equipe](/articles/giving-team-maintainer-permissions-to-an-organization-member) -- Remove the team's access to repositories{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +- Remover o acesso da equipe aos repositórios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} - [Gerencie a atribuição de código de revisão para a equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md b/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md index bbc99f348a..18458e7c76 100644 --- a/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md +++ b/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" and "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. Para usar {% data variables.product.prodname_github_container_registry %}, você precisa habilitar a pré-visualização de recursos. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" e "[Habilitar melhor suporte ao contêiner](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". {% endnote %} diff --git a/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md index 2df9364c31..f513fc27c6 100644 --- a/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" and "[Getting started with {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry)."{% endif %} +**Observação:** O registro do Docker de {% data variables.product.prodname_registry %} será substituído por {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} em uma versão futura de {% data variables.product.product_name %} {% endif %}.{% if currentVersion == "free-pro-team@latest" %} Para aprender como migrar suas imagens Docker existentes e quaisquer fluxos de trabalho usando-as, consulte "[Migrar para {% data variables.product.prodname_github_container_registry %} para imagens do Docker](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" e "[Começar com {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry).{% endif %} {% endwarning %} diff --git a/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md index 175131b3b6..76a2a8bc43 100644 --- a/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". +**Observação:** Antes de poder usar {% data variables.product.prodname_github_container_registry %}, você deve habilitar o recurso para sua conta. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". {% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/decide-publishing-source.md b/translations/pt-BR/data/reusables/pages/decide-publishing-source.md index f753491870..bde5e1718d 100644 --- a/translations/pt-BR/data/reusables/pages/decide-publishing-source.md +++ b/translations/pt-BR/data/reusables/pages/decide-publishing-source.md @@ -1 +1 @@ -1. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}Decide{% else %}If you're creating a project site, decide{% endif %} which publishing source you want to use. {% if currentVersion ver_lt "enterprise-server@2. 3" %}Se você estiver criando um site de usuário ou organização, você deverá armazenar o código-fonte do seu site no branch `mestre`.{% endif %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". +1. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" ou currentVersion == "github-ae@latest" %}Decida{% else %}Se você estiver criando um site de projeto, decida{% endif %} qual fonte de publicação você deseja usar. {% if currentVersion ver_lt "enterprise-server@2. 3" %}Se você estiver criando um site de usuário ou organização, você deverá armazenar o código-fonte do seu site no branch `mestre`.{% endif %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". diff --git a/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md b/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md index d2d3c9c5da..8cdab25f1c 100644 --- a/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md +++ b/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,3 @@ -Se o seu site for um projeto independente, você pode criar um novo repositório para armazenar o código-fonte do seu site. If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project. +Se o seu site for um projeto independente, você pode criar um novo repositório para armazenar o código-fonte do seu site. Se o seu site estiver associado a um projeto existente, você pode adicionar o código-fonte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" or currentVersion == "github-ae@latest" %}a esse repositório do projeto, em uma pasta de `/docs` no branch padrão ou em um branch diferente.{% else %}para o seu site para um branch de `páginas gh-pages` ou uma pasta de `docs` no branch `mestre` no repositório do projeto.{% endif %} Por exemplo, se você estiver criando um site para publicar a documentação de um projeto que já está em {% data variables.product.product_name %}, você deverá armazenar o código-fonte para o site no mesmo repositório do projeto. Se você deseja criar um site em um repositório existente, pule para a seção "[Criar o seu site](#creating-your-site). diff --git a/translations/pt-BR/data/reusables/pre-release-program/corsair-preview.md b/translations/pt-BR/data/reusables/pre-release-program/corsair-preview.md index 837f5b7a27..e595518971 100644 --- a/translations/pt-BR/data/reusables/pre-release-program/corsair-preview.md +++ b/translations/pt-BR/data/reusables/pre-release-program/corsair-preview.md @@ -1,6 +1,6 @@ {% note %} -**Observação:** Para acessar a API do {% data variables.product.prodname_unfurls %} durante o período de pré-visualização, você deve fornecer um [tipo de mídia](/v3/media) personalizado no cabeçalho `Aceitar`: +**Observação:** Para acessar a API do {% data variables.product.prodname_unfurls %} durante o período de pré-visualização, você deve fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar`: ``` application/vnd.github.corsair-preview+json diff --git a/translations/pt-BR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/pt-BR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md index 266a10d815..c141370c25 100644 --- a/translations/pt-BR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md +++ b/translations/pt-BR/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Observação:** Os tokens de usuário com data de vencimento atualmente fazem parte do beta com data de vencimento do token de usuário para servidor e estão sujeitos a alterações. Para optar por participar do recurso beta do token de usuário para servidor com expiração, consulte "[Ativar os recursos beta para aplicativos](/developers/apps/activating-beta-features-for-apps)". Para obter mais informações, consulte "[Tokens com data de vencimento de acesso de usuário para servidor para aplicativos GitHub](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)". diff --git a/translations/pt-BR/data/reusables/pre-release-program/fury-pre-release.md b/translations/pt-BR/data/reusables/pre-release-program/fury-pre-release.md index f105880c14..33d5b4a8d9 100644 --- a/translations/pt-BR/data/reusables/pre-release-program/fury-pre-release.md +++ b/translations/pt-BR/data/reusables/pre-release-program/fury-pre-release.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} {% note %} -**Observação:** Os manifestos de {% data variables.product.prodname_github_app %} estão atualmente disponíveis para pré-visualização dos desenvolvedores. Para acessar essa API durante o período de pré-visualização, você deve fornecer um [tipo de mídia](/v3/media) personalizado no cabeçalho `Aceitar`: +**Observação:** Os manifestos de {% data variables.product.prodname_github_app %} estão atualmente disponíveis para pré-visualização dos desenvolvedores. Para acessar essa API durante o período de pré-visualização, você deve fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar`: ``` application/vnd.github.fury-preview+json diff --git a/translations/pt-BR/data/reusables/pre-release-program/machine-man-preview.md b/translations/pt-BR/data/reusables/pre-release-program/machine-man-preview.md index 0134c2291c..c05e1aa061 100644 --- a/translations/pt-BR/data/reusables/pre-release-program/machine-man-preview.md +++ b/translations/pt-BR/data/reusables/pre-release-program/machine-man-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Observação:** Para acessar a API com o seu aplicativo GitHub, você deve fornecer um [tipo de mídia](/v3/media) personalizado no cabeçalho `Aceitar` para as suas solicitações. +**Observação:** Para acessar a API com o seu aplicativo GitHub, você deve fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar` para as suas solicitações. `application/vnd.github.machine-man-preview+json` diff --git a/translations/pt-BR/data/reusables/pre-release-program/sailor-v-preview.md b/translations/pt-BR/data/reusables/pre-release-program/sailor-v-preview.md index 676c8c9745..3db37ec259 100644 --- a/translations/pt-BR/data/reusables/pre-release-program/sailor-v-preview.md +++ b/translations/pt-BR/data/reusables/pre-release-program/sailor-v-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Observação:** Agora você pode usar a API REST para adicionar um motivo ao bloquear um problema e você verá as razões de bloqueio nas respostas que incluem problemas ou pull requests. Você também verá razões de bloqueio em eventos `bloqueados`. Esse recurso está atualmente disponível para pré-visualização dos desenvolvedores. Consulte o [post do blogue](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) para obter informações completas. Para acessar este recurso, você deve fornecer um [tipo de mídia](/v3/media) personalizado no cabeçalho `Aceitar`: +**Observação:** Agora você pode usar a API REST para adicionar um motivo ao bloquear um problema e você verá as razões de bloqueio nas respostas que incluem problemas ou pull requests. Você também verá razões de bloqueio em eventos `bloqueados`. Esse recurso está atualmente disponível para pré-visualização dos desenvolvedores. Consulte o [post do blogue](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) para obter informações completas. Para acessar este recurso, você deve fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar`: ``` application/vnd.github.sailor-v-preview+json diff --git a/translations/pt-BR/data/reusables/pre-release-program/starfox-preview.md b/translations/pt-BR/data/reusables/pre-release-program/starfox-preview.md index 70d5468e69..52a4c261d2 100644 --- a/translations/pt-BR/data/reusables/pre-release-program/starfox-preview.md +++ b/translations/pt-BR/data/reusables/pre-release-program/starfox-preview.md @@ -2,7 +2,7 @@ **Observação:** Os detalhes do cartão do projeto agora são mostrados em respostas da API REST para eventos relacionados ao projeto e da linha do tempo. Esse recurso agora está disponível para pré-visualização dos desenvolvedores. Para obter informações, consulte o [post do blogue](https://developer.github.com/changes/2018-09-05-project-card-events). -Para receber o atributo `project_card`, os quadros de projeto devem estar [habilitados](/articles/disabling-project-boards-in-a-repository) para um repositório e você deve fornecer um [tipo de mídia](/v3/media) personalizado no cabeçalho `Aceitar`: +Para receber o atributo `project_card`, os quadros de projeto devem estar [habilitados](/articles/disabling-project-boards-in-a-repository) para um repositório e você deve fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar`: ``` application/vnd.github.starfox-preview+json diff --git a/translations/pt-BR/data/reusables/profile/profile-readme.md b/translations/pt-BR/data/reusables/profile/profile-readme.md index bf0faa98fc..891026b40c 100644 --- a/translations/pt-BR/data/reusables/profile/profile-readme.md +++ b/translations/pt-BR/data/reusables/profile/profile-readme.md @@ -1 +1 @@ -Se você adicionar um arquivo LEIAME à raiz de um repositório público com o mesmo nome de usuário, esse LEIAME aparecerá automaticamente na sua página de perfil. Você pode editar seu perfil LEIAME com o markdown em estilo GitHub para criar uma seção personalizada no seu perfil. +Se você adicionar um arquivo LEIAME à raiz de um repositório público com o mesmo nome de usuário, esse LEIAME aparecerá automaticamente na sua página de perfil. You can edit your profile README with {% data variables.product.company_short %} Flavored Markdown to create a personalized section on your profile. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." diff --git a/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md b/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md index 4dd58d8151..c5f8b4e116 100644 --- a/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md +++ b/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md @@ -1 +1 @@ -1. In the left sidebar, under the user's profile picture, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block or report user**. ![Link para bloquear ou relatar usuário](/assets/images/help/profile/profile-block-or-report-button.png) +1. Na barra lateral esquerda, abaixo da imagem de perfil do usuário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Bloquear ou relatar usuário**. ![Link para bloquear ou relatar usuário](/assets/images/help/profile/profile-block-or-report-button.png) diff --git a/translations/pt-BR/data/reusables/project-management/project-progress-locations.md b/translations/pt-BR/data/reusables/project-management/project-progress-locations.md index 9ac6c41be9..cc120596cd 100644 --- a/translations/pt-BR/data/reusables/project-management/project-progress-locations.md +++ b/translations/pt-BR/data/reusables/project-management/project-progress-locations.md @@ -1 +1 @@ -If progress tracking is enabled, a progress bar appears above the project board, on the project listing page, in the issue sidebar, and in references to the project on other project boards. +Se o rastreamento de progresso estiver habilitado, uma barra de progresso aparecerá acima do quadro de projetos, na página de listagem do projeto, na barra lateral de questões e em referências ao projeto em outros quadros de projetos. diff --git a/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md index 769653ae6a..789bda84b5 100644 --- a/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -You can link a pull request to an issue to{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} show that a fix is in progress and to{% endif %} automatically close the issue when someone merges the pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." +Você pode vincular um pull request a um problema para{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %} mostrar que uma correção está em andamento e{% endif %} fechar automaticamente o problema quando alguém faz o merge do pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." diff --git a/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md index fe351c4bc4..bab06a961b 100644 --- a/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md +++ b/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md @@ -1,7 +1,7 @@ {% note %} **Notes:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -- Para aparecer no gráfico de contribuições do seu perfil, os commits de criação conjunta devem atender aos mesmos critérios que os commits com um autor.{% endif %} -- Ao fazer rebase dos commits, os autores originais do commit e a pessoa que fez o rebase dos commits, seja na linha de comando ou em {% data variables.product.product_location %}, receberá o crédito de contribuição. +- To appear on your profile contributions graph, co-authored commits must meet the same criteria as commits with one author.{% endif %} +- When rebasing commits, the original authors of the commit and the person who rebased the commits, whether on the command line or on {% data variables.product.product_location %}, receive contribution credit. {% endnote %} diff --git a/translations/pt-BR/data/reusables/pull_requests/re-request-review.md b/translations/pt-BR/data/reusables/pull_requests/re-request-review.md index b04a7a46ce..29f1f1fde4 100644 --- a/translations/pt-BR/data/reusables/pull_requests/re-request-review.md +++ b/translations/pt-BR/data/reusables/pull_requests/re-request-review.md @@ -1 +1 @@ -You can re-request a review, for example, after you've made substantial changes to your pull request. To request a fresh review from a reviewer, in the sidebar of the **Conversation** tab, click the {% octicon "sync" aria-label="The sync icon" %} icon. +Você pode ressolicitar uma revisão, por exemplo, após fazer alterações substanciais no seu pull request. Para solicitar uma nova revisão de um revisor, na barra lateral da aba **Conversa**, clique no ícone {% octicon "sync" aria-label="The sync icon" %}. diff --git a/translations/pt-BR/data/reusables/repositories/about-internal-repos.md b/translations/pt-BR/data/reusables/repositories/about-internal-repos.md index 61358584cd..38ecaa5561 100644 --- a/translations/pt-BR/data/reusables/repositories/about-internal-repos.md +++ b/translations/pt-BR/data/reusables/repositories/about-internal-repos.md @@ -1 +1 @@ -You can use internal repositories to practice "innersource" within your enterprise. Members of your enterprise can collaborate using open source methodologies without sharing proprietary information publicly{% if enterpriseServerVersions contains currentVersion %}, even with private mode disabled{% endif %}. +Você pode usar repositórios internos para praticar "innersource" dentro da sua empresa. Os integrantes da sua empresa podem colaborar usando metodologias de código aberto sem compartilhar informações proprietárias publicamente{% if enterpriseServerVersions contains currentVersion %}, mesmo com o modo privado desabilitado{% endif %}. diff --git a/translations/pt-BR/data/reusables/repositories/copy-clone-url.md b/translations/pt-BR/data/reusables/repositories/copy-clone-url.md index 126addcd6c..41cf1385a6 100644 --- a/translations/pt-BR/data/reusables/repositories/copy-clone-url.md +++ b/translations/pt-BR/data/reusables/repositories/copy-clone-url.md @@ -8,7 +8,7 @@ Para clonar o repositório usando uma chave SSH que inclui um certificado emitid {% else %} 1. Acima da lista de arquivos, clique em {% octicon "download" aria-label="The download icon" %} **código**. ![Botão de "Código"](/assets/images/help/repository/code-button.png) 1. Para clonar o repositório usando HTTPS, em "Clonar com HTTPS", clique em -{% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **Use SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} To clone a repository using {% data variables.product.prodname_cli %}, click **Use {% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.{% endif %} +{% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar o repositório usando uma chave SSH, incluindo um certificado emitido pela autoridade certificada e SSH da sua organização, clique em **Usar SSH** e, em seguida, clique em {% octicon "clippy" aria-label="The clipboard icon" %}.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} Para clonar um repositório usando {% data variables.product.prodname_cli %}, clique em **Usar {% data variables.product.prodname_cli %}** e, em seguida, clique em {% octicon "clippy" aria-label="The clipboard icon" %}.{% endif %} ![O ícone da área de transferência para copiar a URL para clonar um repositório](/assets/images/help/repository/https-url-clone.png) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ![O ícone da área de transferência para copiar a URL para clonar um repositório com o CLI do GitHub](/assets/images/help/repository/https-url-clone-cli.png){% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/create-repo.md b/translations/pt-BR/data/reusables/repositories/create-repo.md index 59c1040772..b6c5c97177 100644 --- a/translations/pt-BR/data/reusables/repositories/create-repo.md +++ b/translations/pt-BR/data/reusables/repositories/create-repo.md @@ -1 +1 @@ -1. Click **Create repository**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Button to create repository](/assets/images/help/repository/create-repository-button.png){% endif %} +1. Clique **Criar repositório**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Button to create repository](/assets/images/help/repository/create-repository-button.png){% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/default-issue-templates.md b/translations/pt-BR/data/reusables/repositories/default-issue-templates.md index c27ec76f7f..30ff6a7c1c 100644 --- a/translations/pt-BR/data/reusables/repositories/default-issue-templates.md +++ b/translations/pt-BR/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1,2 @@ -You can create default issue templates{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and a default configuration file for issue templates{% endif %} for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or user account{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." +Você pode criar modelos de problemas padrão{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} e um arquivo de configuração padrão para os modelos de problemas{% endif %} para a sua organização{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou conta de usuário{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file)." diff --git a/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index bb17ce0955..f67f87dda3 100644 --- a/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -6,6 +6,6 @@ - When [LDAP Sync is enabled](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync), if you remove a person from a repository, they will lose access but their forks will not be deleted. Se a pessoa for adicionada a uma equipe com acesso ao repositório original da organização dentro de três meses, seu acesso às bifurcações será automaticamente restaurado na próxima sincronização.{% endif %} - Você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual. -- People with admin permissions to a private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository can disallow forking of that repository, and organization owners can disallow forking of any private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository in an organization. Para mais informações, consulte "[Gerenciar a política de bifurcação da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" e "[Gerenciar a política de bifurcação do seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". +- As pessoas com permissões de administrador para um repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou interno{% endif %} podem impedir a bifurcação desse repositório, e os proprietários da organização podem impedir a bifurcação de qualquer repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou interno{% endif %} em uma organização. Para mais informações, consulte "[Gerenciar a política de bifurcação da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" e "[Gerenciar a política de bifurcação do seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". {% endwarning %} diff --git a/translations/pt-BR/data/reusables/repositories/deploy-keys.md b/translations/pt-BR/data/reusables/repositories/deploy-keys.md index df63efce6c..c0036f1727 100644 --- a/translations/pt-BR/data/reusables/repositories/deploy-keys.md +++ b/translations/pt-BR/data/reusables/repositories/deploy-keys.md @@ -1 +1 @@ -Você pode iniciar projetos a partir de um repositório de {% data variables.product.product_name %} para o seu servidor usando uma chave de implantação, que é uma chave SSH que concede acesso a um único repositório. {% data variables.product.product_name %} anexa a parte pública da chave diretamente ao repositório em vez de uma conta de usuário pessoal, e a parte privada da chave permanece no seu servidor. Para obter mais informações, consulte "[Entregar implantações](/v3/guides/delivering-deployments/)". +Você pode iniciar projetos a partir de um repositório de {% data variables.product.product_name %} para o seu servidor usando uma chave de implantação, que é uma chave SSH que concede acesso a um único repositório. {% data variables.product.product_name %} anexa a parte pública da chave diretamente ao repositório em vez de uma conta de usuário pessoal, e a parte privada da chave permanece no seu servidor. Para obter mais informações, consulte "[Entregar implantações](/rest/guides/delivering-deployments)". diff --git a/translations/pt-BR/data/reusables/repositories/desktop-fork.md b/translations/pt-BR/data/reusables/repositories/desktop-fork.md index c67065114f..3a0d638227 100644 --- a/translations/pt-BR/data/reusables/repositories/desktop-fork.md +++ b/translations/pt-BR/data/reusables/repositories/desktop-fork.md @@ -1 +1 @@ -Você pode usar {% data variables.product.prodname_desktop %} para bifurcar um repositório. Para obter mais informações, consulte “[Clonagem e bifurcação de repositórios de {% data variables.product.prodname_desktop %}](/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop)". +Você pode usar {% data variables.product.prodname_desktop %} para bifurcar um repositório. For more information, see "[Cloning and forking repositories from {% data variables.product.prodname_desktop %}](/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop)." diff --git a/translations/pt-BR/data/reusables/repositories/security-alert-delivery-options.md b/translations/pt-BR/data/reusables/repositories/security-alert-delivery-options.md index cbe8361b51..f5ce95aed0 100644 --- a/translations/pt-BR/data/reusables/repositories/security-alert-delivery-options.md +++ b/translations/pt-BR/data/reusables/repositories/security-alert-delivery-options.md @@ -1,4 +1,4 @@ {% if currentVersion != "github-ae@latest" %} -If your repository has a supported dependency manifest -{% if currentVersion == "free-pro-team@latest" %} (and if you've set up the dependency graph if it's a private repository){% endif %}, whenever {% data variables.product.product_name %} detects a vulnerable dependency in your repository, you will receive a weekly digest email. Você também pode configurar os seus alertas de segurança como notificações web, notificações individuais de e-mail, resumo de e-mail diários ou alertas na interface de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" +Se o seu repositório tem um manifesto de dependência compatível +{% if currentVersion == "free-pro-team@latest" %} (e se você configurou o gráfico de dependências se for um repositório privado){% endif %}, sempre que {% data variables.product.product_name %} detectar uma dependência vulnerável no repositório, você receberá um e-mail com o resumo semanal. Você também pode configurar os seus alertas de segurança como notificações web, notificações individuais de e-mail, resumo de e-mail diários ou alertas na interface de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md index eded6450c9..9d1cab75f6 100644 --- a/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md +++ b/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md @@ -1 +1 @@ -1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**. ![Aaba {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-tab.png) +1. Na barra lateral de segurança, clique em **{% data variables.product.prodname_dependabot_alerts %}**. ![Aaba {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-tab.png) diff --git a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index 616b3fbf76..728f80de8a 100644 --- a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. Para obter mais informações, consulte "[Exigindo um histórico de commit linear](/github/administering-a-repository/requiring-a-linear-commit-history)".{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" ou currentVersion == "github-ae@latest" %}Se houver uma regra de branch protegido no repositório que exija um histórico de commit linear. você deve permitir merge de combinação por squash, merge de rebase ou ambos. Para obter mais informações, consulte "[Exigindo um histórico de commit linear](/github/administering-a-repository/requiring-a-linear-commit-history)".{% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/start-line-comment.md b/translations/pt-BR/data/reusables/repositories/start-line-comment.md index 8d09f6c909..613d0f56fb 100644 --- a/translations/pt-BR/data/reusables/repositories/start-line-comment.md +++ b/translations/pt-BR/data/reusables/repositories/start-line-comment.md @@ -1 +1 @@ -1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon.{% endif %} ![Ícone de comentário azul](/assets/images/help/commits/hover-comment-icon.gif) +1. Passe o mouse sobre a linha de código onde você gostaria de adicionar um comentário e clique no ícone de comentário azul.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} Para adicionar um comentário em várias linhas clique e arraste para selecionar o intervalo de linhas e, em seguida, clique no ícone azul de comentário.{% endif %} ![Ícone de comentário azul](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/pt-BR/data/reusables/repositories/suggest-changes.md b/translations/pt-BR/data/reusables/repositories/suggest-changes.md index 7201f019cf..7405d386dd 100644 --- a/translations/pt-BR/data/reusables/repositories/suggest-changes.md +++ b/translations/pt-BR/data/reusables/repositories/suggest-changes.md @@ -1 +1 @@ -1. Optionally, to suggest a specific change to the line{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} or lines{% endif %}, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. ![Bloco de sugestão](/assets/images/help/pull_requests/suggestion-block.png) +1. Opcionalmente, para sugerir uma alteração específica à linha{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %} ou linhas{% endif %}, clique em {% octicon "diff" aria-label="The diff symbol" %} e, em seguida, edite o texto dentro do bloco de sugestão. ![Bloco de sugestão](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md index 954583cc18..6b8c983bf8 100644 --- a/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md +++ b/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -1,5 +1,5 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Any failed steps are automatically expanded to display the results. ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results-updated.png) +1. Todas as etapas com falha são automaticamente expandidas para exibir os resultados. ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results-updated.png) {% else %} 1. Expanda a etapa **Executar Super-Linter** para visualizar os resultados. ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results.png) {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md b/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md index 19b7d831be..5293027a7b 100644 --- a/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md +++ b/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md @@ -1,5 +1,5 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Para obter um link para uma linha específica nos logs, clique no número da linha da etapa. You can then copy the link from the address bar of your web browser. ![Botão para copiar link](/assets/images/help/repository/copy-link-button-updated.png) +1. Para obter um link para uma linha específica nos logs, clique no número da linha da etapa. Em seguida, você pode copiar o link da barra de endereço do seu navegador da web. ![Botão para copiar link](/assets/images/help/repository/copy-link-button-updated.png) {% else %} -1. Para obter um link para uma linha específica nos logs, clique no número da linha da etapa. You can then copy the link from the address bar of your web browser. ![Botão para copiar link](/assets/images/help/repository/copy-link-button.png) +1. Para obter um link para uma linha específica nos logs, clique no número da linha da etapa. Em seguida, você pode copiar o link da barra de endereço do seu navegador da web. ![Botão para copiar link](/assets/images/help/repository/copy-link-button.png) {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/you-can-fork.md b/translations/pt-BR/data/reusables/repositories/you-can-fork.md index 2d290ce6cd..e9617dd1fa 100644 --- a/translations/pt-BR/data/reusables/repositories/you-can-fork.md +++ b/translations/pt-BR/data/reusables/repositories/you-can-fork.md @@ -1,3 +1,7 @@ -You can fork any public repository to your user account or any organization where you have repository creation permissions. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." +{% if currentVersion == "github-ae@latest" %}Se as políticas da empresa permitem a bifurcação de repositórios internos e privados, Você{% else %}Você{% endif %} pode criar um fork de um repositório para a sua conta de usuário ou para qualquer organização onde você tenha permissões de criação de repositório. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization)". -You can fork any private repository you can access to your user account and any organization on {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} where you have repository creation permissions. You cannot fork a private repository to an organization using {% data variables.product.prodname_free_team %}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[GitHub's products](/articles/githubs-products)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Se você tem acesso a um repositório privado e o proprietário permite a bifurcação, você pode criar um fork do repositório para a conta do usuário ou para qualquer organização em {% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %} onde você tem permissões de criação de repositório. {% if currentVersion == "free-pro-team@latest" %}Você não pode criar um repositório privado para uma organização usando {% data variables.product.prodname_free_team %}. Para obter mais informações, consulte "[produtos do GitHub](/articles/githubs-products)."{% endif %} + +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md b/translations/pt-BR/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md index e60bce6013..ea2d4db241 100644 --- a/translations/pt-BR/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md +++ b/translations/pt-BR/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md @@ -1 +1 @@ -You'll configure identity and access management for {% data variables.product.product_name %} by entering the details for your SAML IdP during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise)." +Você configurará identidade e gerenciamento de acesso para {% data variables.product.product_name %}, inserindo os detalhes do seu IdP do SAML durante a inicialização. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise)". diff --git a/translations/pt-BR/data/reusables/saml/ae-uses-saml-sso.md b/translations/pt-BR/data/reusables/saml/ae-uses-saml-sso.md index 08c138d1ba..f9811b8f40 100644 --- a/translations/pt-BR/data/reusables/saml/ae-uses-saml-sso.md +++ b/translations/pt-BR/data/reusables/saml/ae-uses-saml-sso.md @@ -1 +1 @@ -{% data variables.product.product_name %} uses SAML SSO for user authentication. You can centrally manage access to {% data variables.product.prodname_ghe_managed %} from an IdP that supports the SAML 2.0 standard. +{% data variables.product.product_name %} usa o SAML SSO para autenticação de usuário. Você pode gerenciar centralmente o acesso ao {% data variables.product.prodname_ghe_managed %} em um IdP que seja compatível com o padrão SAML 2.0. diff --git a/translations/pt-BR/data/reusables/saml/assert-the-administrator-attribute.md b/translations/pt-BR/data/reusables/saml/assert-the-administrator-attribute.md index ff9e3bc75d..c6fedfdeca 100644 --- a/translations/pt-BR/data/reusables/saml/assert-the-administrator-attribute.md +++ b/translations/pt-BR/data/reusables/saml/assert-the-administrator-attribute.md @@ -1 +1 @@ -To make a person an enterprise owner, you must delegate ownership permission in your IdP. Include the `administrator` attribute in the SAML assertion for the user account on the IdP, with the value of `true`. For more information about enterprise owners, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +Para tornar uma pessoa um proprietário de empresa, você deve delegar a permissão da propriedade em seu IdP. Inclui o atributo `administrador` na declaração do SAML para a conta do usuário no IdP, com o valor de `verdadeiro`. Para obter mais informações sobre os proprietários corporativos, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". diff --git a/translations/pt-BR/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md b/translations/pt-BR/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md index 9b41c813bd..ac6c725dcc 100644 --- a/translations/pt-BR/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md +++ b/translations/pt-BR/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md @@ -1 +1 @@ -If you can't sign into your enterprise because {% data variables.product.product_name %} can't communicate with your SAML IdP, you can contact {% data variables.contact.github_support %}, who can help you access {% data variables.product.product_name %} to update the SAML SSO configuration. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)". +Se você não puder entrar na sua empresa porque {% data variables.product.product_name %} não pode comunicar-se com seu IdP do SAML, você pode entrar em contato com {% data variables.contact.github_support %}, que pode ajudar você a acessar {% data variables.product.product_name %} para atualizar a configuração do SAML SSO. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)". diff --git a/translations/pt-BR/data/reusables/saml/create-a-machine-user.md b/translations/pt-BR/data/reusables/saml/create-a-machine-user.md index 0f0bdbf11d..42dc488ddd 100644 --- a/translations/pt-BR/data/reusables/saml/create-a-machine-user.md +++ b/translations/pt-BR/data/reusables/saml/create-a-machine-user.md @@ -1 +1 @@ -Create and use a dedicated machine user account on your IdP to associate with the first enterprise owner account on {% data variables.product.product_name %}. Store the credentials for the user account securely in a password manager. +Crie e use uma conta de usuário de máquina dedicada no seu IdP para associar à primeira conta de proprietário corporativo em {% data variables.product.product_name %}. Armazene as credenciais para a conta do usuário em um gerenciador de senhas com segurança. diff --git a/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md b/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md index 295826c10f..f1a2af7d12 100644 --- a/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md +++ b/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md @@ -1 +1 @@ -You must periodically authenticate with your SAML IdP to authenticate and gain access to {% if currentVersion == "free-pro-team@latest" %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}. A duração desse período de login é especificado pelo seu IdP e geralmente é de 24 horas. Esse requisito de login periódico limita a duração do acesso e exige que você identifique-se novamente para continuar. {% if currentVersion == "free-pro-team@latest" %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %} +You must periodically authenticate with your SAML IdP to authenticate and gain access to {% if currentVersion == "free-pro-team@latest" %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires you to re-identify yourself to continue. {% if currentVersion == "free-pro-team@latest" %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %} diff --git a/translations/pt-BR/data/reusables/scim/after-you-configure-saml.md b/translations/pt-BR/data/reusables/scim/after-you-configure-saml.md index 85246f3cf0..631d44fb1d 100644 --- a/translations/pt-BR/data/reusables/scim/after-you-configure-saml.md +++ b/translations/pt-BR/data/reusables/scim/after-you-configure-saml.md @@ -1 +1 @@ -By default, your IdP does not communicate with {% data variables.product.product_name %} automatically when you assign or unassign the application. {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %}provisions access to your resources on {% else %}creates a user account {% endif %}using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% if currentVersion == "free-pro-team@latest" %}your resources on {% endif %} {% data variables.product.product_name %} and signs in by authenticating through your IdP. You may need to manually notify users when you grant access to {% data variables.product.product_name %}, and you must manually {% if currentVersion == "free-pro-team@latest" %}deprovision access {% else %}deactivate the user account on {% endif %}{% data variables.product.product_name %} during offboarding. You can use SCIM to provision and deprovision {% if currentVersion == "free-pro-team@latest" %}access to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %} {% else %}user accounts and access for {% data variables.product.product_name %} {% endif %}automatically when you assign or unassign the application on your IdP. \ No newline at end of file +Por padrão, seu IdP não se comunica com {% data variables.product.product_name %} automaticamente quando você atribuir ou desatribuir o aplicativo. {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %}provisiona acesso aos seus recursos em {% else %}cria uma conta de usuário {% endif %}usando o Just-in-Time (JIT) do SAML, provisionando a primeira vez que alguém acessa {% if currentVersion == "free-pro-team@latest" %}os seus recursos em {% endif %} {% data variables.product.product_name %} e inicia a sessão efetuando a autenticação através do seu IdP. Talvez você precise notificar manualmente os usuários ao conceder acesso a {% data variables.product.product_name %}, e você deve {% if currentVersion == "free-pro-team@latest" %}desprovisionar o acesso manualmente {% else %}desativado na conta do usuário em {% endif %}{% data variables.product.product_name %} durante o processo de saída. Você pode usar o SCIM para provisionar e desprovisionar {% if currentVersion == "free-pro-team@latest" %}o acesso às organizações pertencentes à sua empresa nas contas de usuário de {% data variables.product.prodname_dotcom_the_website %} {% else %} para {% data variables.product.product_name %} {% endif %}automaticamente ao atribuir ou desatribuir o aplicativo no seu IdP. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/scim/supported-idps.md b/translations/pt-BR/data/reusables/scim/supported-idps.md index 84aea5e724..df4c2b2a83 100644 --- a/translations/pt-BR/data/reusables/scim/supported-idps.md +++ b/translations/pt-BR/data/reusables/scim/supported-idps.md @@ -1,4 +1,4 @@ -The following IdPs can provision or deprovision user accounts on {% data variables.product.product_location %} using SCIM. +Os seguintes IdPs podem provisionar ou desprovisionar contas de usuário em {% data variables.product.product_location %} usando o SCIM. {% if currentVersion == "github-ae@latest" %} - Azure AD diff --git a/translations/pt-BR/data/reusables/search/required_login.md b/translations/pt-BR/data/reusables/search/required_login.md index af19a5ce7a..6d8598a94a 100644 --- a/translations/pt-BR/data/reusables/search/required_login.md +++ b/translations/pt-BR/data/reusables/search/required_login.md @@ -1 +1 @@ -Você precisa estar conectado para pesquisar código em todos os repositórios públicos. +You must be signed into a user account on {% data variables.product.product_name %} to search for code across all public repositories. diff --git a/translations/pt-BR/data/reusables/search/syntax_tips.md b/translations/pt-BR/data/reusables/search/syntax_tips.md index 38697327fd..47c43ad577 100644 --- a/translations/pt-BR/data/reusables/search/syntax_tips.md +++ b/translations/pt-BR/data/reusables/search/syntax_tips.md @@ -1,7 +1,7 @@ {% tip %} **Dicas:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - - Este artigo tem exemplos de pesquisa no site {% data variables.product.prodname_dotcom %}.com, mas você pode usar os mesmos filtros de pesquisa na {% data variables.product.product_location %}.{% endif %} + - This article contains links to example searches on the {% data variables.product.prodname_dotcom_the_website %} website, but you can use the same search filters with {% data variables.product.product_name %}. In the linked example searches, replace `github.com` with the hostname for {% data variables.product.product_location %}.{% endif %} - Para obter uma lista de sintaxes de pesquisa que podem ser adicionadas a qualquer qualificador de pesquisa para melhorar ainda mais os resultados, consulte "[Entender a sintaxe de pesquisa](/articles/understanding-the-search-syntax)". - Use aspas em termos de pesquisa com várias palavras. Por exemplo, se quiser pesquisar problemas com a etiqueta "In progress," pesquise `label:"in progress"`. A pesquisa não faz distinção entre maiúsculas e minúsculas. diff --git a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index af4760bd17..415f86736d 100644 --- a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_rsa +$ ssh-add ~/.ssh/id_ed25519 ``` diff --git a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index 94a06dad03..fb1ca5ec34 100644 --- a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -Se você criou sua chave com um nome diferente ou se você estiver adicionando uma chave existente com um nome diferente, substitua *id_rsa* no comando pelo nome do seu arquivo de chave privada. +If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_ed25519* in the command with the name of your private key file. diff --git a/translations/pt-BR/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/pt-BR/data/reusables/support/enterprise-resolving-and-closing-tickets.md index 4de64b795e..4b5aaf8608 100644 --- a/translations/pt-BR/data/reusables/support/enterprise-resolving-and-closing-tickets.md +++ b/translations/pt-BR/data/reusables/support/enterprise-resolving-and-closing-tickets.md @@ -1,5 +1,5 @@ -{% data variables.contact.enterprise_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, {% if currentVersion == "github-ae@latest" %}or {% endif %} workaround instructions{% if enterpriseServerVersions contains currentVersion %}, or by advising you of an available release that addresses the issue{% endif %}. +{% data variables.contact.enterprise_support %} pode considerar um tíquete resolvido após fornecer uma explicação, recomendação, instruções de uso, {% if currentVersion == "github-ae@latest" %}or {% endif %} instruções de soluções alternativas{% if enterpriseServerVersions contains currentVersion %} ou orientando você com relação a uma versão disponível que resolve o problema{% endif %}. Se você usar um plugin, módulo ou código personalizado incompatível, o {% data variables.contact.enterprise_support %} solicitará a remoção desse item incompatível durante a tentativa de solução do problema. Se o problema for corrigido quando o plugin, módulo ou código personalizado incompatível for removido, o {% data variables.contact.enterprise_support %} poderá considerar o tíquete resolvido. -{% data variables.contact.enterprise_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. Se {% data variables.contact.enterprise_support %} encerrar um tíquete por falta de resposta, você poderá solicitar que {% data variables.contact.enterprise_support %} reabra o tíquete. +{% data variables.contact.enterprise_support %} pode fechar um tíquete se este estiver fora do escopo do suporte ou se várias tentativas de entrar em contato com você ficaram sem resposta. Se {% data variables.contact.enterprise_support %} encerrar um tíquete por falta de resposta, você poderá solicitar que {% data variables.contact.enterprise_support %} reabra o tíquete. diff --git a/translations/pt-BR/data/reusables/support/ghae-priorities.md b/translations/pt-BR/data/reusables/support/ghae-priorities.md index 7609606fc3..21df4d4ca4 100644 --- a/translations/pt-BR/data/reusables/support/ghae-priorities.md +++ b/translations/pt-BR/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ -| Prioridade | Descrição | Exemplos | -|:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.

_After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ |
  • Erros ou falhas que afetam a funcionalidade central do Git ou do aplicativo web para todos os usuários
  • Severe network or performance degradation for majority of users
  • Armazenamento esgotado ou que se preenche rapidamente
  • Known security incidents or a breach of access
| -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
  • Redução de desempenho que reduz a produtividade para muitos usuários
  • Reduced redundancy concerns from failures or service degradation
  • Production-impacting bugs or errors
  • {% data variables.product.product_name %} configuraton security concerns
| -| {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}. |
  • Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows
  • Issues with user tools and data collection methods
  • Atualizações
  • Bug reports, general security questions, or other feature related questions
    • | -| {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
    • Feature requests and product feedback
    • General questions on overall configuration or use of {% data variables.product.product_name %}
    • Notifying {% data variables.contact.github_support %} of any planned changes
    | +| Prioridade | Descrição | Exemplos | +|:---------------------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} não pode ser acessado ou há uma falha total e esta afeta diretamente a operação do seu negócio.

    _Depois que você arquivar um tíquete de suporte, entre em contato com {% data variables.contact.github_support %} por telefone._ |
    • Erros ou falhas que afetam a funcionalidade central do Git ou do aplicativo web para todos os usuários
    • Degradação grave da rede ou desempenho para a maioria dos usuários
    • Armazenamento esgotado ou que se preenche rapidamente
    • Incidentes de segurança conhecidos ou uma violação do acesso
    | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falha em um ambiente de produção, com impacto limitado nos seus processos de negócios ou afeta apenas determinados clientes. |
    • Redução de desempenho que reduz a produtividade para muitos usuários
    • Problemas de redundância reduzidos provenientes de falhas ou degradação de serviço
    • Erros ou falhas que impactam a produção
    • Problemas de segurança de configuração de {% data variables.product.product_name %}
    | +| {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} está passando por problemas e erros limitados ou moderados com {% data variables.product.product_name %} ou você tem preocupações ou dúvidas gerais sobre a operação de {% data variables.product.product_name %}. |
    • Orientação sobre a utilização das APIs e recursos de {% data variables.product.prodname_dotcom %} ou questões sobre a integração de fluxos de trabalho de negócios
    • Problemas com ferramentas de usuário e métodos de coleta de dados
    • Atualizações
    • Relatórios de erros, perguntas gerais de segurança ou outras questões relacionadas a recursos
      • | +| {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} está funcionando como esperado. No entanto, você tem uma dúvida ou sugestão sobre {% data variables.product.product_name %} que não é sensível ao tempo, ou não bloqueia a produtividade da sua equipe. |
      • Solicitações de recursos e feedback de produtos
      • Dúvidas gerais sobre a configuração geral ou o uso de {% data variables.product.product_name %}
      • Notificar {% data variables.contact.github_support %} de qualquer alteração planejada
      | diff --git a/translations/pt-BR/data/reusables/support/government-response-times-may-vary.md b/translations/pt-BR/data/reusables/support/government-response-times-may-vary.md index a171b413d8..f288af39f3 100644 --- a/translations/pt-BR/data/reusables/support/government-response-times-may-vary.md +++ b/translations/pt-BR/data/reusables/support/government-response-times-may-vary.md @@ -1,7 +1,7 @@ {% if currentVersion == "github-ae@latest" %} {% note %} -**Note:** Response times and hours of operation may differ for {% data variables.product.prodname_ghe_managed %} for Government. Your Technical Support Account Manager (TSAM) will confirm during your onboarding. +**Observação:** A resposta pode ser diferente para {% data variables.product.prodname_ghe_managed %} no caso das entidades governamentais. Seu Administrador de Conta de Suporte Técnico (TSAM) irá confirmar durante sua integração. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/support/premium-resolving-and-closing-tickets.md b/translations/pt-BR/data/reusables/support/premium-resolving-and-closing-tickets.md index 63d55cbc21..ad4b0eb653 100644 --- a/translations/pt-BR/data/reusables/support/premium-resolving-and-closing-tickets.md +++ b/translations/pt-BR/data/reusables/support/premium-resolving-and-closing-tickets.md @@ -2,4 +2,4 @@ Se você usar um plugin, módulo ou código personalizado incompatível, o {% data variables.contact.premium_support %} solicitará a remoção desse item incompatível durante a tentativa de resolução do problema. Se o problema for corrigido quando o plugin, módulo ou código personalizado incompatível for removido, o {% data variables.contact.premium_support %} poderá considerar o tíquete resolvido. -{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. Se {% data variables.contact.premium_support %} encerrar um tíquete por falta de resposta, você poderá solicitar que {% data variables.contact.premium_support %} reabra o tíquete. +{% data variables.contact.premium_support %} pode fechar um tíquete se este estiver fora do escopo do suporte ou se várias tentativas de entrar em contato com você ficaram sem resposta. Se {% data variables.contact.premium_support %} encerrar um tíquete por falta de resposta, você poderá solicitar que {% data variables.contact.premium_support %} reabra o tíquete. diff --git a/translations/pt-BR/data/reusables/support/scope-of-support.md b/translations/pt-BR/data/reusables/support/scope-of-support.md index dc4f48f918..f4ffd77b0e 100644 --- a/translations/pt-BR/data/reusables/support/scope-of-support.md +++ b/translations/pt-BR/data/reusables/support/scope-of-support.md @@ -1,7 +1,7 @@ ### Escopo do suporte -Se sua solicitação de suporte estiver fora do escopo do que nossa equipe pode ajudá-lo, podemos recomendar os próximos passos para resolver seu problema fora do {% data variables.contact.github_support %}. Your support request is possibly out of {% data variables.contact.github_support %}'s scope if the request is primarily about: +Se sua solicitação de suporte estiver fora do escopo do que nossa equipe pode ajudá-lo, podemos recomendar os próximos passos para resolver seu problema fora do {% data variables.contact.github_support %}. A sua solicitação de suporte possivelmente está fora do escopo de {% data variables.contact.github_support %}, se a solicitação se tratar principalmente de: - Integrações com terceiros - Configurações de hardware - CI/CD, como Jenkins diff --git a/translations/pt-BR/data/reusables/user_settings/link_email_with_your_account.md b/translations/pt-BR/data/reusables/user_settings/link_email_with_your_account.md index a1fa5e4664..70bb22ed8c 100644 --- a/translations/pt-BR/data/reusables/user_settings/link_email_with_your_account.md +++ b/translations/pt-BR/data/reusables/user_settings/link_email_with_your_account.md @@ -1,4 +1,4 @@ {% if currentVersion != "github-ae@latest" %} -Add the email address to your account on -{% data variables.product.product_name %}, so that your commits are attributed to you and appear in your contributions graph. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)." +Adicione o endereço de e-mail à sua conta em +{% data variables.product.product_name %}, para que seus commits sejam atribuídos a você e apareçam no seu gráfico de contribuições. Para obter mais informações, consulte "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)". {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/user_settings/password-authentication-deprecation.md b/translations/pt-BR/data/reusables/user_settings/password-authentication-deprecation.md index bd247793ce..e83515bd82 100644 --- a/translations/pt-BR/data/reusables/user_settings/password-authentication-deprecation.md +++ b/translations/pt-BR/data/reusables/user_settings/password-authentication-deprecation.md @@ -1 +1 @@ -When Git prompts you for your password, enter your personal access token (PAT) instead.{% if currentVersion != "github-ae@latest" %} Password-based authentication for Git is deprecated, and using a PAT is more secure.{% endif %} For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +Quando o Git solicitar a sua senha, insira seu token de acesso pessoal (PAT).{% if currentVersion != "github-ae@latest" %} Autenticação baseada em senha para o Git está obsoleta, e usar um PAT é mais seguro.{% endif %} Para obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". diff --git a/translations/pt-BR/data/reusables/webhooks/check_run_properties.md b/translations/pt-BR/data/reusables/webhooks/check_run_properties.md index 5d75a55254..a95d160f26 100644 --- a/translations/pt-BR/data/reusables/webhooks/check_run_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/check_run_properties.md @@ -1,11 +1,11 @@ -| Tecla | Tipo | Descrição | -| --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `Ação` | `string` | A ação realizada. Pode ser uma das ações a seguir:
      • `created` - Uma nova execução de verificação foi criada.
      • `completed` - O `status` da execução da verificação está `completed`.
      • `rerequested` - Alguém pediu para executar novamente sua verificação a partir da interface de usuário do pull request. Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub. Ao receber uma ação `rerequested`, você deverá [criar uma nova execução de verificação](/v3/checks/runs/#create-a-check-run). Apenas o {% data variables.product.prodname_github_app %} que alguém solicitar para repetir a verificação receberá a carga `rerequested`.
      • `requested_action` - Alguém solicitou novamente que se tome uma ação fornecida pelo seu aplicativo. Apenas o {% data variables.product.prodname_github_app %} para o qual alguém solicitou uma ação receberá a carga `requested_action`. Para saber mais sobre verificações executadas e ações solicitadas, consulte "[Verificar executa e ações solicitadas](/v3/checks/runs/#check-runs-and-requested-actions)".
      | -| `check_run` | `objeto` | O [check_run](/v3/checks/runs/#get-a-check-run). | -| `check_run[status]` | `string` | O status atual da execução da verificação. Pode ser `queued`, `in_progress` ou `completed`. | -| `check_run[conclusion]` | `string` | O resultado da execução de verificação concluída. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. Este valor será `null` até que a execução da verificação seja `completed`. | -| `check_run[name]` | `string` | O nome da execução da verificação. | -| `check_run[check_suite][id]` | `inteiro` | A identificação do conjunto de verificações do qual a execução de verificação faz parte. | -| `check_run[check_suite][pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. Um pull request corresponde a um conjunto de verificações se tiverem os mesmos `head_sha` e `head_branch`. Quando o `head_branch` do conjunto de verificações estiver em um repositório bifurcado, ele será `null` e o array `pull_requests` ficará vazio. | -| `requested_action` | `objeto` | A ação solicitada pelo usuário. | -| `requested_action[identifier]` | `string` | A referência de integrador da ação solicitada pelo usuário. | +| Tecla | Tipo | Descrição | +| --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser uma das ações a seguir:
      • `created` - Uma nova execução de verificação foi criada.
      • `completed` - O `status` da execução da verificação está `completed`.
      • `rerequested` - Alguém pediu para executar novamente sua verificação a partir da interface de usuário do pull request. Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Apenas o {% data variables.product.prodname_github_app %} que alguém solicitar para repetir a verificação receberá a carga `rerequested`.
      • `requested_action` - Alguém solicitou novamente que se tome uma ação fornecida pelo seu aplicativo. Apenas o {% data variables.product.prodname_github_app %} para o qual alguém solicitou uma ação receberá a carga `requested_action`. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
      | +| `check_run` | `objeto` | O [check_run](/rest/reference/checks#get-a-check-run). | +| `check_run[status]` | `string` | O status atual da execução da verificação. Pode ser `queued`, `in_progress` ou `completed`. | +| `check_run[conclusion]` | `string` | O resultado da execução de verificação concluída. Pode ser: `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` ou `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` até que a execução da verificação seja `completed`. | +| `check_run[name]` | `string` | O nome da execução da verificação. | +| `check_run[check_suite][id]` | `inteiro` | A identificação do conjunto de verificações do qual a execução de verificação faz parte. | +| `check_run[check_suite][pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. Um pull request corresponde a um conjunto de verificações se tiverem os mesmos `head_sha` e `head_branch`. Quando o `head_branch` do conjunto de verificações estiver em um repositório bifurcado, ele será `null` e o array `pull_requests` ficará vazio. | +| `requested_action` | `objeto` | A ação solicitada pelo usuário. | +| `requested_action[identifier]` | `string` | A referência de integrador da ação solicitada pelo usuário. | diff --git a/translations/pt-BR/data/reusables/webhooks/check_run_short_desc.md b/translations/pt-BR/data/reusables/webhooks/check_run_short_desc.md index a0c48c63dc..58f14581bf 100644 --- a/translations/pt-BR/data/reusables/webhooks/check_run_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/check_run_short_desc.md @@ -1 +1 @@ -Verifique se a atividade de execução ocorreu. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[execuções de verificação](/v3/checks/runs/)". +Verifique se a atividade de execução ocorreu. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[execuções de verificação](/rest/reference/checks#runs)". diff --git a/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md b/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md index 0555fc42c1..e0ef07d3e3 100644 --- a/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md @@ -1,10 +1,10 @@ -| Tecla | Tipo | Descrição | -| ---------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser:
      • `completed` - Todas as verificações executadas em um conjunto de verificações foram concluídas.
      • `requested` - Ocorre quando o novo código é carregado para o repositório do aplicativo. Quando você receber os eventos de ação `requested`, você deverá [criar uma nova execução de verificação](/v3/checks/runs/#create-a-check-run).
      • `rerequested` - Ocorre quando alguém solicita uma nova execução de todo o conjunto de verificação da interface de usuário do pull request. Ao receber os eventos da ação `rerequested`, você deverá [criar uma nova execução de verificação](/v3/checks/runs/#create-a-check-run). Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub.
      | -| `check_suite` | `objeto` | O [check_suite](/v3/checks/suites/). | -| `check_suite[head_branch]` | `string` | O nome do branch principal em que as alterações se encontram. | -| `check_suite[head_sha]` | `string` | A SHA do commit mais recente para este conjunto de verificações. | -| `check_suite[status]` | `string` | O status de resumo para todas as verificações que fazem parte do conjunto de verificações. Pode ser `requested`, `in_progress` ou `completed`. | -| `check_suite[conclusion]` | `string` | O resumo da conclusão para todas as verificações que fazem parte do conjunto de verificações. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. Este valor será `null` até que a execução da verificação seja `completed`. | -| `check_suite[url]` | `string` | A URL que aponta para o recurso da API do conjunto de verificações. | -| `check_suite[pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. Um pull request corresponde a um conjunto de verificações se tiverem os mesmos `head_sha` e `head_branch`. Quando o `head_branch` do conjunto de verificações estiver em um repositório bifurcado, ele será `null` e o array `pull_requests` ficará vazio. | +| Tecla | Tipo | Descrição | +| ---------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser:
      • `completed` - Todas as verificações executadas em um conjunto de verificações foram concluídas.
      • `requested` - Ocorre quando o novo código é carregado para o repositório do aplicativo. When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).
      • `rerequested` - Ocorre quando alguém solicita uma nova execução de todo o conjunto de verificação da interface de usuário do pull request. When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub.
      | +| `check_suite` | `objeto` | O [check_suite](/rest/reference/checks#suites). | +| `check_suite[head_branch]` | `string` | O nome do branch principal em que as alterações se encontram. | +| `check_suite[head_sha]` | `string` | A SHA do commit mais recente para este conjunto de verificações. | +| `check_suite[status]` | `string` | O status de resumo para todas as verificações que fazem parte do conjunto de verificações. Pode ser `requested`, `in_progress` ou `completed`. | +| `check_suite[conclusion]` | `string` | O resumo da conclusão para todas as verificações que fazem parte do conjunto de verificações. Pode ser: `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` ou `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` até que a execução da verificação seja `completed`. | +| `check_suite[url]` | `string` | A URL que aponta para o recurso da API do conjunto de verificações. | +| `check_suite[pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. Um pull request corresponde a um conjunto de verificações se tiverem os mesmos `head_sha` e `head_branch`. Quando o `head_branch` do conjunto de verificações estiver em um repositório bifurcado, ele será `null` e o array `pull_requests` ficará vazio. | diff --git a/translations/pt-BR/data/reusables/webhooks/check_suite_short_desc.md b/translations/pt-BR/data/reusables/webhooks/check_suite_short_desc.md index 262c3c6cba..72917e38be 100644 --- a/translations/pt-BR/data/reusables/webhooks/check_suite_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/check_suite_short_desc.md @@ -1 +1 @@ -Ocorreu uma atividade de conjuntos de verificações. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de"[conjunto de verificações](/v3/checks/suites/)". +Ocorreu uma atividade de conjuntos de verificações. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de"[conjunto de verificações](/rest/reference/checks#suites)". diff --git a/translations/pt-BR/data/reusables/webhooks/commit_comment_properties.md b/translations/pt-BR/data/reusables/webhooks/commit_comment_properties.md index 324768c82a..b2213e6139 100644 --- a/translations/pt-BR/data/reusables/webhooks/commit_comment_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/commit_comment_properties.md @@ -1,4 +1,4 @@ -| Tecla | Tipo | Descrição | -| ------------ | -------- | ------------------------------------------------------------------------------ | -| `Ação` | `string` | A ação realizada. Pode ser `criado`. | -| `comentário` | `objeto` | O recurso de [comentário de commit](/v3/repos/comments/#get-a-commit-comment). | +| Tecla | Tipo | Descrição | +| ------------ | -------- | -------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser `criado`. | +| `comentário` | `objeto` | O recurso de [comentário de commit](/rest/reference/repos#get-a-commit-comment). | diff --git a/translations/pt-BR/data/reusables/webhooks/commit_comment_short_desc.md b/translations/pt-BR/data/reusables/webhooks/commit_comment_short_desc.md index 76d4d4405f..d5bee754f1 100644 --- a/translations/pt-BR/data/reusables/webhooks/commit_comment_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/commit_comment_short_desc.md @@ -1 +1 @@ -Um comentário de commit foi criado. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[comentário de commit](/v3/repos/comments/)". +Um comentário de commit foi criado. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[comentário de commit](/rest/reference/repos#comments)". diff --git a/translations/pt-BR/data/reusables/webhooks/create_properties.md b/translations/pt-BR/data/reusables/webhooks/create_properties.md index d7a8c23a62..ec1009b546 100644 --- a/translations/pt-BR/data/reusables/webhooks/create_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/create_properties.md @@ -1,6 +1,6 @@ | Tecla | Tipo | Descrição | | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | O recurso [`ref do git`](/v3/git/refs/#get-a-reference). | +| `ref` | `string` | O recurso [`ref do git`](/rest/reference/git#get-a-reference). | | `ref_type` | `string` | O tipo de objeto de ref do Git criado no repositório. Pode ser `branch` ou `tag`. | | `master_branch` | `string` | O nome do branch-padrão do repositório (normalmente {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 3" %}`principal`{% else %}`mestre`{% endif %}). | | `descrição` | `string` | Descrição atual do repositório. | diff --git a/translations/pt-BR/data/reusables/webhooks/create_short_desc.md b/translations/pt-BR/data/reusables/webhooks/create_short_desc.md index 1d5ff03b89..1c0f4ff6ef 100644 --- a/translations/pt-BR/data/reusables/webhooks/create_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/create_short_desc.md @@ -1 +1 @@ -Um branch ou tag do Git é criado. Para obter mais informações, consulte a API REST de "[dados do Git](/v3/git/). +Um branch ou tag do Git é criado. Para obter mais informações, consulte a API REST de "[dados do Git](/rest/reference/git). diff --git a/translations/pt-BR/data/reusables/webhooks/delete_properties.md b/translations/pt-BR/data/reusables/webhooks/delete_properties.md index 8cbb629e7e..a65db49f67 100644 --- a/translations/pt-BR/data/reusables/webhooks/delete_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ | Tecla | Tipo | Descrição | | ---------- | -------- | -------------------------------------------------------------------------------- | -| `ref` | `string` | O recurso [`ref do git`](/v3/git/refs/#get-a-reference). | +| `ref` | `string` | O recurso [`ref do git`](/rest/reference/git#get-a-reference). | | `ref_type` | `string` | O tipo de objeto do Git ref excluído no repositório. Pode ser `branch` ou `tag`. | diff --git a/translations/pt-BR/data/reusables/webhooks/delete_short_desc.md b/translations/pt-BR/data/reusables/webhooks/delete_short_desc.md index 28fd36dd0a..d9f39701b4 100644 --- a/translations/pt-BR/data/reusables/webhooks/delete_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/delete_short_desc.md @@ -1 +1 @@ -Um branch ou tag do Git é excluído. Para obter mais informações, consulte a API REST de "[dados do Git](/v3/git/). +Um branch ou tag do Git é excluído. Para obter mais informações, consulte a API REST de "[dados do Git](/rest/reference/git). diff --git a/translations/pt-BR/data/reusables/webhooks/deploy_key_properties.md b/translations/pt-BR/data/reusables/webhooks/deploy_key_properties.md index 16a75e1634..d4a2dcc17c 100644 --- a/translations/pt-BR/data/reusables/webhooks/deploy_key_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/deploy_key_properties.md @@ -1,4 +1,4 @@ -| Tecla | Tipo | Descrição | -| ------- | -------- | ------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `criado` ou `excluído`. | -| `Chave` | `objeto` | O recurso de [`implantar chave`](/v3/repos/keys/#get-a-deploy-key). | +| Tecla | Tipo | Descrição | +| ------- | -------- | ------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser `criado` ou `excluído`. | +| `Chave` | `objeto` | O recurso de [`implantar chave`](/rest/reference/repos#get-a-deploy-key). | diff --git a/translations/pt-BR/data/reusables/webhooks/deploy_key_short_desc.md b/translations/pt-BR/data/reusables/webhooks/deploy_key_short_desc.md index 75e47eef22..72e8cb810c 100644 --- a/translations/pt-BR/data/reusables/webhooks/deploy_key_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/deploy_key_short_desc.md @@ -1 +1 @@ -Uma chave de implementação foi adicionada ou removida de um repositório. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[Chaves de implementação](/v3/repos/keys/)". +Uma chave de implementação foi adicionada ou removida de um repositório. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[Chaves de implementação](/rest/reference/repos#keys)". diff --git a/translations/pt-BR/data/reusables/webhooks/fork_properties.md b/translations/pt-BR/data/reusables/webhooks/fork_properties.md index d0e7d45559..6531d3bafa 100644 --- a/translations/pt-BR/data/reusables/webhooks/fork_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/fork_properties.md @@ -1,3 +1,3 @@ -| Tecla | Tipo | Descrição | -| -------- | -------- | ----------------------------------------------------------------- | -| `forkee` | `objeto` | O recurso do [`repositório`](/v3/repos/#get-a-repository) criado. | +| Tecla | Tipo | Descrição | +| -------- | -------- | ---------------------------------------------------------------------------- | +| `forkee` | `objeto` | O recurso do [`repositório`](/rest/reference/repos#get-a-repository) criado. | diff --git a/translations/pt-BR/data/reusables/webhooks/fork_short_desc.md b/translations/pt-BR/data/reusables/webhooks/fork_short_desc.md index 070bd3cf12..57c5939cdf 100644 --- a/translations/pt-BR/data/reusables/webhooks/fork_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/fork_short_desc.md @@ -1 +1 @@ -Um usuário bifurca um repositório. Para obter mais informações, consulte a API REST de [bifurcações](/v3/repos/forks/)". +Um usuário bifurca um repositório. Para obter mais informações, consulte a API REST de [bifurcações](/rest/reference/repos#forks)". diff --git a/translations/pt-BR/data/reusables/webhooks/installation_properties.md b/translations/pt-BR/data/reusables/webhooks/installation_properties.md index f6fbd8c92e..d6a2921931 100644 --- a/translations/pt-BR/data/reusables/webhooks/installation_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ | Tecla | Tipo | Descrição | | -------------- | -------- | ----------------------------------------------------------------------------------- | | `Ação` | `string` | A ação que foi executada. Pode ser uma das ações a seguir:
      • `created` - Alguém instala um {% data variables.product.prodname_github_app %}.
      • `deleted` - Alguém desinstala {% data variables.product.prodname_github_app %}
        • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
      • `suspend` - Alguém suspende uma instalação de {% data variables.product.prodname_github_app %}.
      • `unsuspend` - Alguém não suspende uma instalação de {% data variables.product.prodname_github_app %}.
        • {% endif %}
      • `new_permissions_accepted` - Alguém aceita novas permissões para uma instalação de {% data variables.product.prodname_github_app %}. Quando um proprietário de {% data variables.product.prodname_github_app %} solicita novas permissões, a pessoa que instalou o {% data variables.product.prodname_github_app %} deve aceitar a nova solicitação de permissões.
      | -| `repositories` | `array` | An array of repository objects that the installation can access. | +| `repositories` | `array` | Uma matriz de objetos do repositório que a instalação pode acessar. | diff --git a/translations/pt-BR/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/pt-BR/data/reusables/webhooks/installation_repositories_short_desc.md index fb3123c7fe..259ac09676 100644 --- a/translations/pt-BR/data/reusables/webhooks/installation_repositories_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/installation_repositories_short_desc.md @@ -1 +1 @@ -Atividade relacionada aos repositórios adicionados a uma instalação do aplicativo GitHub. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST da "[Instalação do aplicativo GitHub](/v3/apps/)". +Atividade relacionada aos repositórios adicionados a uma instalação do aplicativo GitHub. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST da "[Instalação do aplicativo GitHub](/rest/reference/apps)". diff --git a/translations/pt-BR/data/reusables/webhooks/installation_short_desc.md b/translations/pt-BR/data/reusables/webhooks/installation_short_desc.md index 011de21adf..52bb8eba31 100644 --- a/translations/pt-BR/data/reusables/webhooks/installation_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/installation_short_desc.md @@ -1 +1 @@ -Atividade relacionada a uma instalação do aplicativo GitHub. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST da "[Instalação do aplicativo GitHub](/v3/apps/)". +Atividade relacionada a uma instalação do aplicativo GitHub. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST da "[Instalação do aplicativo GitHub](/rest/reference/apps)". diff --git a/translations/pt-BR/data/reusables/webhooks/issue_comment_properties.md b/translations/pt-BR/data/reusables/webhooks/issue_comment_properties.md index 67de30f6b7..18757101c8 100644 --- a/translations/pt-BR/data/reusables/webhooks/issue_comment_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/issue_comment_properties.md @@ -1 +1 @@ -`alterações`「`objeto` As alterações no comentário se a ação foi `editada`. `alterações[body][from]` |`string` | A versão anterior do texto se a ação foi `editada`. `problema`├`objeto` ├O [problema](/v3/issues/) ao qual o comentário pertence. `comentário`|`objeto` | O próprio [comentário](/v3/issues/comments/). +`alterações`「`objeto` As alterações no comentário se a ação foi `editada`. `alterações[body][from]` |`string` | A versão anterior do texto se a ação foi `editada`. `problema`├`objeto` ├O [problema](/rest/reference/issues) ao qual o comentário pertence. `comentário`|`objeto` | O próprio [comentário](/rest/reference/issues#comments). diff --git a/translations/pt-BR/data/reusables/webhooks/issue_comment_short_desc.md b/translations/pt-BR/data/reusables/webhooks/issue_comment_short_desc.md index f7da7a2069..458b4263b7 100644 --- a/translations/pt-BR/data/reusables/webhooks/issue_comment_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/issue_comment_short_desc.md @@ -1 +1 @@ -Atividade relacionada a um comentário de um problema. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[comentários de problema](/v3/issues/comments/)". +Atividade relacionada a um comentário de um problema. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[comentários de problema](/rest/reference/issues#comments)". diff --git a/translations/pt-BR/data/reusables/webhooks/issue_properties.md b/translations/pt-BR/data/reusables/webhooks/issue_properties.md index cda10c54b9..3b13a0d358 100644 --- a/translations/pt-BR/data/reusables/webhooks/issue_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/issue_properties.md @@ -1 +1 @@ -`problema`|`objeto` | O próprio [problema](/v3/issues). `alterações`|`objeto`| As alterações feitas no problemas se a ação foi `editada`. `alterações[title][from]`|`string` | A versão anterior do título se a ação foi `editada`. `alterações[body][from]`|`string` | A versão anterior do texto se a ação foi `editada`. `responsável`|`objeto` | O usuário opcional ao qual foi atribuído ou não foi atribuído o problema. `etiqueta`|`objeto` | A etiqueta opcional adicionada ou removida do problema. +`problema`|`objeto` | O próprio [problema](/rest/reference/issues). `alterações`|`objeto`| As alterações feitas no problemas se a ação foi `editada`. `alterações[title][from]`|`string` | A versão anterior do título se a ação foi `editada`. `alterações[body][from]`|`string` | A versão anterior do texto se a ação foi `editada`. `responsável`|`objeto` | O usuário opcional ao qual foi atribuído ou não foi atribuído o problema. `etiqueta`|`objeto` | A etiqueta opcional adicionada ou removida do problema. diff --git a/translations/pt-BR/data/reusables/webhooks/issues_short_desc.md b/translations/pt-BR/data/reusables/webhooks/issues_short_desc.md index c15f9905cf..26f0bf844e 100644 --- a/translations/pt-BR/data/reusables/webhooks/issues_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/issues_short_desc.md @@ -1 +1 @@ -Atividade relacionada a um problema. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST de [problemas](/v3/issues/comments/)". +Atividade relacionada a um problema. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST de [problemas](/rest/reference/issues#comments)". diff --git a/translations/pt-BR/data/reusables/webhooks/label_short_desc.md b/translations/pt-BR/data/reusables/webhooks/label_short_desc.md index b9d9b11fb4..6294b0c024 100644 --- a/translations/pt-BR/data/reusables/webhooks/label_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/label_short_desc.md @@ -1 +1 @@ -Atividade relacionada a um problema. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte API REST de [etiquetas](/v3/issues/labels/)". +Atividade relacionada a um problema. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte API REST de [etiquetas](/rest/reference/issues#labels)". diff --git a/translations/pt-BR/data/reusables/webhooks/member_properties.md b/translations/pt-BR/data/reusables/webhooks/member_properties.md index 470b0d1377..d2b44c9e75 100644 --- a/translations/pt-BR/data/reusables/webhooks/member_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/member_properties.md @@ -1 +1 @@ -`integrante`|`objeto` | O [usuário](/v3/users/) que foi adicionado. `alterações`|`objeto`| As alterações nas permissões do colaborador se a ação foi `editada`. `changes[old_permission][from]`|`string` | As permissões anteriores do colaborador se a ação foi `editada`. +`integrante`|`objeto` | O [usuário](/rest/reference/users) que foi adicionado. `alterações`|`objeto`| As alterações nas permissões do colaborador se a ação foi `editada`. `changes[old_permission][from]`|`string` | As permissões anteriores do colaborador se a ação foi `editada`. diff --git a/translations/pt-BR/data/reusables/webhooks/member_short_desc.md b/translations/pt-BR/data/reusables/webhooks/member_short_desc.md index eef75cac3d..f60465f509 100644 --- a/translations/pt-BR/data/reusables/webhooks/member_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/member_short_desc.md @@ -1 +1 @@ -Atividade relacionada aos colaboradores do repositório. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST dos [colaboradores](/v3/repos/collaborators/)". +Atividade relacionada aos colaboradores do repositório. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST dos [colaboradores](/rest/reference/repos#collaborators)". diff --git a/translations/pt-BR/data/reusables/webhooks/member_webhook_properties.md b/translations/pt-BR/data/reusables/webhooks/member_webhook_properties.md index bbf9f855d6..5fc21f827f 100644 --- a/translations/pt-BR/data/reusables/webhooks/member_webhook_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/member_webhook_properties.md @@ -1,3 +1,3 @@ | Tecla | Tipo | Descrição | | ------ | -------- | ----------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Pode ser uma das ações a seguir:
      • `added` - Um usuário aceita um convite para um repositório.
      • `removed` - Um usuário é removido como colaborador de um repositório.
      • `edited` - A user's collaborator permissions have changed.
      | +| `Ação` | `string` | A ação que foi executada. Pode ser uma das ações a seguir:
      • `added` - Um usuário aceita um convite para um repositório.
      • `removed` - Um usuário é removido como colaborador de um repositório.
      • `edited` - As permissões de um colaborador do usuário foram alteradas.
      | diff --git a/translations/pt-BR/data/reusables/webhooks/membership_properties.md b/translations/pt-BR/data/reusables/webhooks/membership_properties.md index 79618ae9f9..6f2521d4a2 100644 --- a/translations/pt-BR/data/reusables/webhooks/membership_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/membership_properties.md @@ -1,6 +1,6 @@ -| Tecla | Tipo | Descrição | -| ------------ | -------- | -------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Pode ser `adicionado` ou `removido`. | -| `escopo` | `string` | O escopo da associação. Atualmente, só pode ser `equipe`. | -| `integrante` | `objeto` | O [usuário](/v3/users/) que foi adicionado ou removido. | -| `equipe` | `objeto` | A [equipe](/v3/teams/) para a associação. | +| Tecla | Tipo | Descrição | +| ------------ | -------- | ------------------------------------------------------------------ | +| `Ação` | `string` | A ação que foi executada. Pode ser `adicionado` ou `removido`. | +| `escopo` | `string` | O escopo da associação. Atualmente, só pode ser `equipe`. | +| `integrante` | `objeto` | O [usuário](/rest/reference/users) que foi adicionado ou removido. | +| `equipe` | `objeto` | A [equipe](/rest/reference/teams) para a associação. | diff --git a/translations/pt-BR/data/reusables/webhooks/membership_short_desc.md b/translations/pt-BR/data/reusables/webhooks/membership_short_desc.md index 85c27a7a27..7bbe7e54f0 100644 --- a/translations/pt-BR/data/reusables/webhooks/membership_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/membership_short_desc.md @@ -1 +1 @@ -Atividade relacionada à associação na equipe. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [integrantes da equipe](/v3/teams/members/)". +Atividade relacionada à associação na equipe. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [integrantes da equipe](/rest/reference/teams#members)". diff --git a/translations/pt-BR/data/reusables/webhooks/milestone_short_desc.md b/translations/pt-BR/data/reusables/webhooks/milestone_short_desc.md index 733f2ecda1..a0a7d03d9e 100644 --- a/translations/pt-BR/data/reusables/webhooks/milestone_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/milestone_short_desc.md @@ -1 +1 @@ -Atividade relacionada aos marcos. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [marcos](/v3/issues/milestones/)". +Atividade relacionada aos marcos. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [marcos](/rest/reference/issues#milestones)". diff --git a/translations/pt-BR/data/reusables/webhooks/org_block_short_desc.md b/translations/pt-BR/data/reusables/webhooks/org_block_short_desc.md index 7c83decc10..3d6ab90998 100644 --- a/translations/pt-BR/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -Atividade relacionada a pessoas que estão sendo bloqueadas em uma organização. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte o[Bloqueando usuários da organização](/v3/orgs/blocking/)" da API REST. +Atividade relacionada a pessoas que estão sendo bloqueadas em uma organização. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte o[bloqueando usuários da organização](/rest/reference/orgs#blocking)" REST API. diff --git a/translations/pt-BR/data/reusables/webhooks/org_desc.md b/translations/pt-BR/data/reusables/webhooks/org_desc.md index 497ae85c8d..840b36a894 100644 --- a/translations/pt-BR/data/reusables/webhooks/org_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/org_desc.md @@ -1 +1 @@ -`organização` | `objeto` Cargas do webhook contêm o objeto da [`organização`](/v3/orgs/#get-an-organization) quando o webhook é configurado para uma organização ou o evento ocorre a partir da atividade em um repositório pertencente a uma organização. +`organização` | `objeto` Cargas do webhook contêm o objeto da [`organização`](/rest/reference/orgs#get-an-organization) quando o webhook é configurado para uma organização ou o evento ocorre a partir da atividade em um repositório pertencente a uma organização. diff --git a/translations/pt-BR/data/reusables/webhooks/organization_short_desc.md b/translations/pt-BR/data/reusables/webhooks/organization_short_desc.md index 57545c34fb..e9d331376c 100644 --- a/translations/pt-BR/data/reusables/webhooks/organization_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/organization_short_desc.md @@ -1 +1 @@ -Atividade relacionada a uma organização e seus integrantes. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APRI REST de "[organizações](/v3/orgs/)". +Atividade relacionada a uma organização e seus integrantes. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APRI REST de "[organizações](/rest/reference/orgs)". diff --git a/translations/pt-BR/data/reusables/webhooks/ping_short_desc.md b/translations/pt-BR/data/reusables/webhooks/ping_short_desc.md index 2e1927ffbf..2c5bd52bb1 100644 --- a/translations/pt-BR/data/reusables/webhooks/ping_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/ping_short_desc.md @@ -1 +1 @@ -Ao criar um novo webhook, enviaremos um simples evento de `ping` para informar que você configurou o webhook corretamente. This event isn't stored so it isn't retrievable via the [Events API](/rest/reference/activity#ping-a-repository-webhook) endpoint. +Ao criar um novo webhook, enviaremos um simples evento de `ping` para informar que você configurou o webhook corretamente. Este evento não é armazenado. Portanto, não é recuperável através do ponto de extremidade da [API de Eventos](/rest/reference/activity#ping-a-repository-webhook). diff --git a/translations/pt-BR/data/reusables/webhooks/project_card_properties.md b/translations/pt-BR/data/reusables/webhooks/project_card_properties.md index 433046861c..7a302e4696 100644 --- a/translations/pt-BR/data/reusables/webhooks/project_card_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/project_card_properties.md @@ -4,4 +4,4 @@ | `alterações` | `objeto` | As alterações no cartão do projeto se a ação foi `editada` ou `convertida`. | | `changes[note][from]` | `string` | A versão anterior da nota se a ação foi `editada` ou `convertida`. | | `after_id` | `inteiro` | O ID do cartão que este cartão agora segue se a ação foi "movida". Será `nulo` se for o primeiro cartão em uma coluna. | -| `project_card` | `objeto` | O próprio [cartão do projeto](/v3/projects/cards). | +| `project_card` | `objeto` | O próprio [cartão do projeto](/rest/reference/projects#cards). | diff --git a/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md b/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md index 39f48549ed..c8caa75605 100644 --- a/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md @@ -1 +1 @@ -Atividade relacionada aos cartões do projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [cartões de projeto](/v3/projects/cards)". +Atividade relacionada aos cartões do projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [cartões de projeto](/rest/reference/projects#cards)". diff --git a/translations/pt-BR/data/reusables/webhooks/project_column_properties.md b/translations/pt-BR/data/reusables/webhooks/project_column_properties.md index 40b481e547..a2c7144088 100644 --- a/translations/pt-BR/data/reusables/webhooks/project_column_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/project_column_properties.md @@ -4,4 +4,4 @@ | `alterações` | `objeto` | As alterações na coluna do projeto, se a ação foi `editada`. | | `changes[name][from]` | `string` | A versão anterior do nome se a ação foi `editada`. | | `after_id` | `inteiro` | O id da coluna que esta coluna agora segue se a ação foi "movida". Será `nulo` se for a primeira coluna em um projeto. | -| `project_column` | `objeto` | A própria [coluna do projeto](/v3/projects/columns). | +| `project_column` | `objeto` | A própria [coluna do projeto](/rest/reference/projects#columns). | diff --git a/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md b/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md index fd604ed44f..7c78f8425c 100644 --- a/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md @@ -1 +1 @@ -Atividade relacionada a colunas em um quadro de projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST das "[colunas do projeto](/v3/projects/columns)". +Atividade relacionada a colunas em um quadro de projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST das "[colunas do projeto](/rest/reference/projects#columns)". diff --git a/translations/pt-BR/data/reusables/webhooks/project_properties.md b/translations/pt-BR/data/reusables/webhooks/project_properties.md index 4ae7477e09..a8802d9240 100644 --- a/translations/pt-BR/data/reusables/webhooks/project_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/project_properties.md @@ -4,4 +4,4 @@ | `alterações` | `objeto` | As alterações no projeto, se a ação foi `editada`. | | `changes[name][from]` | `string` | A versão anterior do nome se a ação foi `editada`. | | `changes[body][from]` | `string` | A versão anterior do texto se a ação foi `editada`. | -| `project` | `objeto` | O próprio [projeto](/v3/projects/). | +| `project` | `objeto` | O próprio [projeto](/rest/reference/projects). | diff --git a/translations/pt-BR/data/reusables/webhooks/project_short_desc.md b/translations/pt-BR/data/reusables/webhooks/project_short_desc.md index 1ee0ba8b55..9aee5961b6 100644 --- a/translations/pt-BR/data/reusables/webhooks/project_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/project_short_desc.md @@ -1 +1 @@ -Atividade relacionada aos quadros de projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte A API REST dos "[projetos](/v3/projects)". +Atividade relacionada aos quadros de projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte A API REST dos "[projetos](/rest/reference/projects)". diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_properties.md b/translations/pt-BR/data/reusables/webhooks/pull_request_properties.md index 943737d6f1..4b5a0b8338 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_properties.md @@ -1 +1 @@ -`número`|`inteiro` | O número do pull request. `alterações`|`objeto`| As alterações no comentário se a ação foi `editada`. `alterações[title][from]`|`string` | A versão anterior do título se a ação foi `editada`. `alterações[body][from]`|`string` | A versão anterior do texto se a ação foi `editada`. `pull_request`|`objeto` | O próprio [pull request](/v3/pulls). +`número`|`inteiro` | O número do pull request. `alterações`|`objeto`| As alterações no comentário se a ação foi `editada`. `alterações[title][from]`|`string` | A versão anterior do título se a ação foi `editada`. `alterações[body][from]`|`string` | A versão anterior do texto se a ação foi `editada`. `pull_request`|`objeto` | O próprio [pull request](/rest/reference/pulls). diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_properties.md index a756fd6bfe..6e61921084 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_properties.md @@ -1 +1 @@ -`alterações`|`objeto`| As alterações no comentário se a ação foi `editada`. `alterações[body][from]`|`string` | A versão anterior do texto se a ação foi `editada`. `pull_request`|`objeto` | O [pull request](/v3/pulls/) ao qual o comentário pertence. `comentário`|`objeto` | O próprio [comentário](/v3/pulls/comments). +`alterações`|`objeto`| As alterações no comentário se a ação foi `editada`. `alterações[body][from]`|`string` | A versão anterior do texto se a ação foi `editada`. `pull_request`|`objeto` | O [pull request](/rest/reference/pulls) ao qual o comentário pertence. `comentário`|`objeto` | O próprio [comentário](/rest/reference/pulls#comments). diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_short_desc.md index 57e1ad1433..23e2e907eb 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_review_comment_short_desc.md @@ -1 +1 @@ -Atividade relacionada aos comentários de revisão do pull request no diff unificado do pull request. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos "[comentários de revisão de pull request](/v3/pulls/comments/)". +Atividade relacionada aos comentários de revisão do pull request no diff unificado do pull request. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos "[comentários de revisão de pull request](/rest/reference/pulls#comments)". diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_review_properties.md b/translations/pt-BR/data/reusables/webhooks/pull_request_review_properties.md index a0b13a0188..548f3ee98f 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ | Tecla | Tipo | Descrição | | --------------------- | -------- | ----------------------------------------------------------------------------------- | | `Ação` | `string` | A ação que foi executada. Pode ser uma das ações a seguir:
      • `submitted` - Uma revisão de pull request é enviada em um estado não pendente.
      • `edited` - O texto de uma revisão foi editado.
      • `dimissed` - Uma revisão foi descartada.
      | -| `pull_request` | `objeto` | O [pull request](/v3/pulls/) ao qual a revisão pertence. | +| `pull_request` | `objeto` | O [pull request](/rest/reference/pulls) ao qual a revisão pertence. | | `revisar` | `objeto` | A revisão que foi afetada. | | `changes[body][from]` | `string` | A versão anterior do texto se a ação foi `editada`. | diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/pt-BR/data/reusables/webhooks/pull_request_review_short_desc.md index d90a1bc655..7817f6f284 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_review_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_review_short_desc.md @@ -1 +1 @@ -Atividade relacionada a revisões de pull request. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST "[Revisões de pull request](/v3/pulls/reviews/)". +Atividade relacionada a revisões de pull request. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST "[Revisões de pull request](/rest/reference/pulls#reviews)". diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_short_desc.md b/translations/pt-BR/data/reusables/webhooks/pull_request_short_desc.md index ffbe719b21..9d3ba180f5 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_short_desc.md @@ -1 +1 @@ -Atividade relacionada a pull requests. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[pull requests](/v3/pulls/)". +Atividade relacionada a pull requests. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[pull requests](/rest/reference/pulls)". diff --git a/translations/pt-BR/data/reusables/webhooks/release_short_desc.md b/translations/pt-BR/data/reusables/webhooks/release_short_desc.md index ae9bb47b6e..17944e167f 100644 --- a/translations/pt-BR/data/reusables/webhooks/release_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/release_short_desc.md @@ -1 +1 @@ -Atividade relacionada a uma versão. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST das [versões](/v3/repos/releases/)". +Atividade relacionada a uma versão. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST das [versões](/rest/reference/repos#releases)". diff --git a/translations/pt-BR/data/reusables/webhooks/repo_desc.md b/translations/pt-BR/data/reusables/webhooks/repo_desc.md index df26fb3e7a..880d21642b 100644 --- a/translations/pt-BR/data/reusables/webhooks/repo_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/repo_desc.md @@ -1 +1 @@ -`repository` | `object` | The [`repository`](/v3/repos/#get-a-repository) where the event occurred. +`repositório` | `objeto` | O [`repositório`](/rest/reference/repos#get-a-repository) em que o evento ocorreu. diff --git a/translations/pt-BR/data/reusables/webhooks/repository_import_short_desc.md b/translations/pt-BR/data/reusables/webhooks/repository_import_short_desc.md index 51fec24a12..07209db7d4 100644 --- a/translations/pt-BR/data/reusables/webhooks/repository_import_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/repository_import_short_desc.md @@ -1 +1 @@ -Atividade relacionada a um repositório que está sendo importado para o GitHub. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[importações de código-fonte"](/v3/migrations/source_imports/)". +Atividade relacionada a um repositório que está sendo importado para o GitHub. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[importações de código-fonte"](/rest/reference/migrations#source-imports)". diff --git a/translations/pt-BR/data/reusables/webhooks/repository_short_desc.md b/translations/pt-BR/data/reusables/webhooks/repository_short_desc.md index 541274b899..cfdb366714 100644 --- a/translations/pt-BR/data/reusables/webhooks/repository_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/repository_short_desc.md @@ -1 +1 @@ -Atividade relacionada a um repositório. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos[repositórios](/v3/repos/)". +Atividade relacionada a um repositório. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos[repositórios](/rest/reference/repos)". diff --git a/translations/pt-BR/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md b/translations/pt-BR/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md index e49c6e71bd..06bd2b488a 100644 --- a/translations/pt-BR/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md @@ -1 +1 @@ -Atividade relacionada a alertas de vulnerabilidade de segurança em um repositório. {% data reusables.webhooks.action_type_desc %} For more information, see the "[About security alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies)". +Atividade relacionada a alertas de vulnerabilidade de segurança em um repositório. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Sobre alertas de segurança para dependências vulneráveis](/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies)". diff --git a/translations/pt-BR/data/reusables/webhooks/star_short_desc.md b/translations/pt-BR/data/reusables/webhooks/star_short_desc.md index c6d38acba5..60cfc84cc8 100644 --- a/translations/pt-BR/data/reusables/webhooks/star_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/star_short_desc.md @@ -1 +1 @@ -Atividade relacionada a um repositório marcado com uma estrela. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[marcar com uma estrela](/v3/activity/starring/)". +Atividade relacionada a um repositório marcado com uma estrela. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[marcar com uma estrela](/rest/reference/activity#starring)". diff --git a/translations/pt-BR/data/reusables/webhooks/status_short_desc.md b/translations/pt-BR/data/reusables/webhooks/status_short_desc.md index e15c21d670..555125decf 100644 --- a/translations/pt-BR/data/reusables/webhooks/status_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/status_short_desc.md @@ -1 +1 @@ -Quando o status de um commit do Git é alterado. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[status](/v3/repos/statuses/)". +Quando o status de um commit do Git é alterado. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[status](/rest/reference/repos#statuses)". diff --git a/translations/pt-BR/data/reusables/webhooks/team_add_short_desc.md b/translations/pt-BR/data/reusables/webhooks/team_add_short_desc.md index 1bbcfaba4a..7cde601a20 100644 --- a/translations/pt-BR/data/reusables/webhooks/team_add_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/team_add_short_desc.md @@ -1 +1 @@ -Quando um repositório [é adicionado a uma equipe](/v3/teams/#add-or-update-team-repository-permissions). +Quando um repositório [é adicionado a uma equipe](/rest/reference/teams#add-or-update-team-repository-permissions). diff --git a/translations/pt-BR/data/reusables/webhooks/team_short_desc.md b/translations/pt-BR/data/reusables/webhooks/team_short_desc.md index 72ee238f5c..1914ab17c6 100644 --- a/translations/pt-BR/data/reusables/webhooks/team_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/team_short_desc.md @@ -1 +1 @@ -Atividade relacionada à equipe de uma organização. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[equipes](/v3/teams/)". +Atividade relacionada à equipe de uma organização. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[equipes](/rest/reference/teams)". diff --git a/translations/pt-BR/data/reusables/webhooks/watch_short_desc.md b/translations/pt-BR/data/reusables/webhooks/watch_short_desc.md index 785a55bca6..b13c64b89f 100644 --- a/translations/pt-BR/data/reusables/webhooks/watch_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/watch_short_desc.md @@ -1 +1 @@ -Quando alguém marca um repositório com uma estrela. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[marcar com uma estrela](/v3/activity/starring/)". +Quando alguém marca um repositório com uma estrela. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST de "[marcar com uma estrela](/rest/reference/activity#starring)". diff --git a/translations/pt-BR/data/variables/action_code_examples.yml b/translations/pt-BR/data/variables/action_code_examples.yml index 6f6e4b4e71..473c0a7438 100644 --- a/translations/pt-BR/data/variables/action_code_examples.yml +++ b/translations/pt-BR/data/variables/action_code_examples.yml @@ -1,12 +1,12 @@ --- - - title: Starter workflows - description: Workflow files for helping people get started with GitHub Actions + title: Fluxos de trabalho iniciais + description: Arquivos do fluxo de trabalho para ajudar pessoas a dar os primeiros passos com o GitHub Actions languages: TypeScript href: actions/starter-workflows tags: - official - - fluxos de trabalho + - fluxo de trabalho - title: Example services description: Example workflows using service containers @@ -64,7 +64,7 @@ - publishing - title: GitHub Project Automation+ - description: Automate GitHub Project cards with any webhook event. + description: Automate GitHub Project cards with any webhook event languages: JavaScript href: alex-page/github-project-automation-plus tags: @@ -131,8 +131,7 @@ - publishing - title: Label your Pull Requests auto-magically (using committed files) - description: >- - Github action to label your pull requests auto-magically (using committed files) + description: Github action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -147,3 +146,191 @@ tags: - pull request - etiquetas +- + title: Get a list of file changes with a PR/Push + description: This action gives you will get outputs of the files that have changed in your repository + languages: 'TypeScript, Shell, JavaScript' + href: trilom/file-changes-action + tags: + - fluxo de trabalho + - repositório +- + title: Private actions in any workflow + description: Allows private GitHub Actions to be easily reused + languages: 'TypeScript, JavaScript, Shell' + href: InVisionApp/private-action-loader + tags: + - fluxo de trabalho + - tools +- + title: Label your issues using the issue's contents + description: A GitHub Action to automatically tag issues with labels and assignees + languages: 'JavaScript, TypeScript' + href: damccorm/tag-ur-it + tags: + - fluxo de trabalho + - tools + - etiquetas + - Problemas +- + title: Rollback a GitHub Release + description: A GitHub Action to rollback or delete a release + languages: 'JavaScript' + href: author/action-rollback + tags: + - fluxo de trabalho + - releases +- + title: Lock closed issues and Pull Requests + description: GitHub Action that locks closed issues and pull requests after a period of inactivity + languages: 'JavaScript' + href: dessant/lock-threads + tags: + - Problemas + - Pull requests + - fluxo de trabalho +- + title: Get Commit Difference Count Between Two Branches + description: This GitHub Action compares two branches and gives you the commit count between them + languages: 'JavaScript, Shell' + href: jessicalostinspace/commit-difference-action + tags: + - commit + - diff + - fluxo de trabalho +- + title: Generate Release Notes Based on Git References + description: GitHub Action to generate changelogs, and release notes + languages: 'JavaScript, Shell' + href: metcalfc/changelog-generator + tags: + - cicd + - release-notes + - fluxo de trabalho + - registro de alterações +- + title: Enforce Policies on GitHub Repositories and Commits + description: Policy enforcement for your pipelines + languages: 'Go, Makefile, Dockerfile, Shell' + href: talos-systems/conform + tags: + - docker + - build-automation + - fluxo de trabalho +- + title: Auto Label Issue Based + description: Automatically label an issue based on the issue description + languages: 'TypeScript, JavaScript, Dockerfile' + href: Renato66/auto-label + tags: + - etiquetas + - fluxo de trabalho + - automation +- + title: Update Configured GitHub Actions to the Latest Versions + description: CLI tool to check whehter all your actions are up-to-date or not + languages: 'C#, Inno Setup, PowerSHell, Shell' + href: fabasoad/ghacu + tags: + - versions + - cli + - fluxo de trabalho +- + title: Create Issue Branch + description: GitHub Action that automates the creation of issue branches + languages: 'JavaScript, Shell' + href: robvanderleek/create-issue-branch + tags: + - probot + - Problemas + - etiquetas +- + title: Remove old artifacts + description: Customize artifact cleanup + languages: 'JavaScript, Shell' + href: c-hive/gha-remove-artifacts + tags: + - artefatos + - fluxo de trabalho +- + title: Sync Defined Files/Binaries to Wiki or External Repositories + description: GitHub Action to automatically sync changes to external repositories, like the wiki, for example + languages: 'Shell, Dockerfile' + href: kai-tub/external-repo-sync-action + tags: + - wiki + - sync + - fluxo de trabalho +- + title: Create/Update/Delete a GitHub Wiki page based on any file + description: Updates your GitHub wiki by using rsync, allowing for exclusion of files and directories and actual deletion of files + languages: 'Shell, Dockerfile' + href: Andrew-Chen-Wang/github-wiki-action + tags: + - wiki + - docker + - fluxo de trabalho +- + title: Prow GitHub Actions + description: Automation of policy enforcement, chat-ops, and automatic PR merging + languages: 'TypeScript, JavaScript' + href: jpmcb/prow-github-actions + tags: + - chat-ops + - prow + - fluxo de trabalho +- + title: Check GitHub Status in your Workflow + description: Check GitHub Status in your workflow + languages: 'TypeScript, JavaScript' + href: crazy-max/ghaction-github-status + tags: + - status + - monitoramento + - fluxo de trabalho +- + title: Manage labels on GitHub as code + description: GitHub Action to manage labels (create/rename/update/delete) + languages: 'TypeScript, JavaScript' + href: crazy-max/ghaction-github-labeler + tags: + - etiquetas + - fluxo de trabalho + - automation +- + title: Distribute funding in free and open source projects + description: Continuous Distribution of funding to project contributors and dependencies + languages: 'Python, Docerfile, Shell, Ruby' + href: protontypes/libreselery + tags: + - sponsors + - funding + - payment +- + title: Herald rules for GitHub + description: Add reviewers, subscribers, labels and assignees to your PR + languages: 'TypeScript, JavaScript' + href: gagoar/use-herald-action + tags: + - reviewers + - etiquetas + - assignees + - pull request +- + title: Codeowner validator + description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations + languages: 'Go, Shell, Makefile, Docerfile' + href: mszostok/codeowners-validator + tags: + - codeowners + - validate + - fluxo de trabalho +- + title: Copybara Action + description: Move and transform code between repositories (ideal to maintain several repos from one monorepo) + languages: 'TypeScript, JavaScript, Shell' + href: olivr/copybara-action + tags: + - monorepo + - copybara + - fluxo de trabalho diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md index 9b8a1a5e54..2957814417 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md @@ -91,7 +91,7 @@ steps: ### Caching dependencies -You can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" and the [`cache` action](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} ```yaml diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md index 5827501db7..8bf1dc05d5 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md @@ -91,7 +91,7 @@ steps: ### Caching dependencies -You can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" and the [`cache` action](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} ```yaml diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md index abca907346..20c76a3bee 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md @@ -129,7 +129,7 @@ If you don't specify a Node.js version, {% data variables.product.prodname_dotco {% data variables.product.prodname_dotcom %}-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux {% data variables.product.prodname_dotcom %}-hosted runners also have Grunt, Gulp, and Bower installed. -You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." #### Example using npm @@ -227,7 +227,7 @@ always-auth=true #### Example caching dependencies -You can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)" and the [`cache` action](https://github.com/marketplace/actions/cache). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} ```yaml @@ -241,7 +241,7 @@ steps: uses: actions/cache@v2 with: # npm cache files are stored in `~/.npm` on Linux/macOS - path: ~/.npm + path: ~/.npm key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }} restore-keys: | ${{ runner.OS }}-node- diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md b/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md index c8f14f7675..dec09e228b 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md @@ -91,7 +91,7 @@ The table below describes the locations for various PowerShell modules in each { {% endnote %} -You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules: @@ -119,7 +119,7 @@ jobs: #### Caching dependencies -You can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "Caching dependencies to speed up workflows." PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system. diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-python.md b/translations/ru-RU/content/actions/guides/building-and-testing-python.md index 0eaff78926..4acf9b7beb 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-python.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-python.md @@ -141,9 +141,9 @@ jobs: uses: actions/setup-python@v2 with: # Semantic version range syntax or exact version of a Python version - python-version: '3.x' + python-version: '3.x' # Optional - x64 or x86 architecture, defaults to x64 - architecture: 'x64' + architecture: 'x64' # You can test your matrix by printing the current Python version - name: Display Python version run: python -c "import sys; print(sys.version)" @@ -192,7 +192,7 @@ We recommend using `setup-python` to configure the version of Python used in you {% data variables.product.prodname_dotcom %}-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. For example, the YAML below installs or upgrades the `pip` package installer and the `setuptools` and `wheel` packages. -You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." {% raw %} ```yaml @@ -228,7 +228,7 @@ steps: #### Caching Dependencies -You can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "[Caching dependencies to speed up workflows](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "Caching dependencies to speed up workflows." Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example below depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip). diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md index 1a8c4f6d86..1fe46e9133 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md @@ -148,7 +148,7 @@ steps: #### Caching dependencies -The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. To enable caching, set the following. @@ -165,7 +165,7 @@ This will configure bundler to install your gems to `vendor/cache`. For each suc **Caching without setup-ruby** -For greater control over caching, you can use the `actions/cache` Action directly. For more information, see "[Caching dependencies to speed up your workflow](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)." +For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. For more information, see "Caching dependencies to speed up workflows." {% raw %} ```yaml diff --git a/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md index 2be0b45740..2ebfa58e4a 100644 --- a/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -131,7 +131,7 @@ The `retention-days` value cannot exceed the retention limit set by the reposito During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact)action to download artifacts that were previously uploaded in the same workflow run. -After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/v3/actions/artifacts/)." +After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." #### Downloading artifacts during a workflow run diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index d164185855..795ee89f10 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -47,9 +47,11 @@ When creating a group, you must choose a policy that defines which repositories {% warning %} - **Warnung** + **Предупреждение** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. + + For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} @@ -77,9 +79,11 @@ When creating a group, you must choose a policy that defines which organizations {% warning %} - **Warnung** + **Предупреждение** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. + + For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} @@ -109,4 +113,3 @@ Self-hosted runners are automatically returned to the default group when their g 1. To remove the group, click **Remove group**. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png) 1. Review the confirmation prompts, and click **Remove this runner group**. - diff --git a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md index 0ba20aeafa..8d3c706848 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md @@ -57,7 +57,7 @@ jobs: needs: build runs-on: ubuntu-latest steps: - - run: ./test_server.sh + - run: ./test_server.sh ``` For more information, see [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). @@ -106,7 +106,7 @@ jobs: ``` {% endraw %} -For more information, see "[Caching dependencies to speed up workflows](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)." +For more information, see "Caching dependencies to speed up workflows." ### Using databases and service containers diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 17d1431c82..497f6175fc 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions
-For more information, see "[Caching dependencies to speed up workflows](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)." +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." {% data variables.product.prodname_actions %} does not have an equivalent of CircleCI’s Docker Layer Caching (or DLC). diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 618503642e..80d2f12511 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -262,7 +262,7 @@ jobs: runs-on: ubuntu-latest steps: - run: echo "This job will be run first, in parallel with build_a" - + test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] @@ -346,7 +346,7 @@ jobs: -For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." ### Artifacts @@ -367,7 +367,7 @@ GitLab CI/CD {% raw %} ```yaml -script: +script: artifacts: paths: - math-homework.txt @@ -414,7 +414,7 @@ GitLab CI/CD container-job: variables: POSTGRES_PASSWORD: postgres - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port @@ -423,10 +423,10 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - npm ci - # Runs a script that creates a PostgreSQL client, + # Runs a script that creates a PostgreSQL client, # populates the client with data, and retrieves data - node client.js tags: @@ -452,7 +452,7 @@ jobs: - name: Check out repository code uses: actions/checkout@v2 - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - name: Install dependencies run: npm ci @@ -462,7 +462,7 @@ jobs: # populates the client with data, and retrieves data run: node client.js env: - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 3e4a548149..497aa02c44 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -163,6 +163,12 @@ git: +#### Using environment variables in a matrix + +Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. + +In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} + ### Key features in {% data variables.product.prodname_actions %} When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}: @@ -281,7 +287,7 @@ jobs: ### Caching dependencies -Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. +Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. @@ -316,7 +322,7 @@ cache: npm
-For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." ### Examples of common tasks diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 7ba456e003..a6150cf4bf 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -14,7 +14,7 @@ You can see whether a workflow run is in progress or complete from the workflow If the run is complete, you can see whether the result was a success, failure, canceled, or neutral. If the run failed, you can view and search the build logs to diagnose the failure and re-run the workflow. You can also view billable job execution minutes, or download logs and build artifacts. -{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/v3/checks/)." +{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/rest/reference/checks)." {% data reusables.github-actions.invalid-workflow-files %} diff --git a/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md b/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md index 69d98496d0..600f771567 100644 --- a/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md @@ -79,7 +79,7 @@ You can use the `GITHUB_TOKEN` to make authenticated API calls. This example wor ### Permissions for the `GITHUB_TOKEN` -For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/v3/apps/permissions/)." +For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)." | Permission | Access type | Access by forked repos | | ------------------- | ----------- | ---------------------- | diff --git a/translations/ru-RU/content/actions/reference/encrypted-secrets.md b/translations/ru-RU/content/actions/reference/encrypted-secrets.md index 85df4fbaf8..a5648dde27 100644 --- a/translations/ru-RU/content/actions/reference/encrypted-secrets.md +++ b/translations/ru-RU/content/actions/reference/encrypted-secrets.md @@ -43,11 +43,11 @@ You can use and read encrypted secrets in a workflow file if you have access to {% endwarning %} -You can also manage secrets using the REST API. For more information, see "[Secrets](/v3/actions/secrets/)." +You can also manage secrets using the REST API. For more information, see "[Secrets](/rest/reference/actions#secrets)." #### Limiting credential permissions -When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/v3/guides/managing-deploy-keys/#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary. +When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary. ### Creating encrypted secrets for a repository diff --git a/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md b/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md index 5de868c0ae..9295302d18 100644 --- a/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md @@ -143,7 +143,7 @@ jobs: {% data reusables.github-actions.branch-requirement %} -You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event)." +You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)." To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% data variables.product.product_name %} API endpoint and provide an `event_type` name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the `repository_dispatch` event. @@ -163,7 +163,7 @@ You can configure your workflow to run when webhook events are created on {% dat #### `check_run` -Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/v3/checks/runs/)." +Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/rest/reference/checks#runs)." {% data reusables.github-actions.branch-requirement %} @@ -183,7 +183,7 @@ on: #### `check_suite` -Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/v3/checks/suites/)." +Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/rest/reference/checks#suites)." {% data reusables.github-actions.branch-requirement %} @@ -209,7 +209,7 @@ on: #### `create` -Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/v3/git/refs/#create-a-reference)." +Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/rest/reference/git#create-a-reference)." | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------- | -------------- | ---------------------------------------- | --------------------- | @@ -224,7 +224,7 @@ on: #### `delete - Удалить` -Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/v3/git/refs/#delete-a-reference)." +Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/rest/reference/git#delete-a-reference)." {% data reusables.github-actions.branch-requirement %} @@ -271,7 +271,7 @@ on: #### `ветвление` -Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/v3/repos/forks/#create-a-fork)." +Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)." {% data reusables.github-actions.branch-requirement %} @@ -354,7 +354,7 @@ jobs: #### `issues` -Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/v3/issues)." +Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/rest/reference/issues)." {% data reusables.github-actions.branch-requirement %} @@ -374,7 +374,7 @@ on: #### `метка` -Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Labels](/v3/issues/labels/)." +Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Labels](/rest/reference/issues#labels)." {% data reusables.github-actions.branch-requirement %} @@ -394,7 +394,7 @@ on: #### `контрольная точка` -Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/v3/issues/milestones/)." +Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)." {% data reusables.github-actions.branch-requirement %} @@ -431,7 +431,7 @@ on: #### `проект` -Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/v3/projects/)." +Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/rest/reference/projects)." {% data reusables.github-actions.branch-requirement %} @@ -451,7 +451,7 @@ on: #### `project_card` -Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/v3/projects/cards)." +Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)." {% data reusables.github-actions.branch-requirement %} @@ -471,7 +471,7 @@ on: #### `project_column` -Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/v3/projects/columns)." +Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)." {% data reusables.github-actions.branch-requirement %} @@ -491,7 +491,7 @@ on: #### `public` -Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/v3/repos/#edit)." +Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)." {% data reusables.github-actions.branch-requirement %} @@ -508,7 +508,7 @@ on: #### `pull_request` -Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/v3/pulls)." +Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)." {% note %} @@ -534,7 +534,7 @@ on: #### `pull_request_review` -Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/v3/pulls/reviews)." +Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)." | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------------------------------- | ---------------------------------------------------------- | -------------------------------------------- | ------------------------------------------- | @@ -554,7 +554,7 @@ on: #### `pull_request_review_comment` -Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/v3/pulls/comments). +Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/rest/reference/pulls#comments). | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------------------------------------------- | ------------------------------------------- | @@ -597,7 +597,7 @@ on: pull_request_target {% note %} -**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a single commit](/v3/repos/commits/#get-a-single-commit)"". +**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a single commit](/rest/reference/repos#get-a-single-commit)"". {% endnote %} @@ -640,7 +640,7 @@ on: {% endnote %} -Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/v3/repos/releases/)." +Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/rest/reference/repos#releases)." | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | -------------- | @@ -658,7 +658,7 @@ on: #### `состояние` -Runs your workflow anytime the status of a Git commit changes, which triggers the `status` event. For information about the REST API, see [Statuses](/v3/repos/statuses/). +Runs your workflow anytime the status of a Git commit changes, which triggers the `status` event. For information about the REST API, see [Statuses](/rest/reference/repos#statuses). {% data reusables.github-actions.branch-requirement %} @@ -675,7 +675,7 @@ on: #### `слежение` -Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/v3/activity/starring/)." +Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/rest/reference/activity#starring)." {% data reusables.github-actions.branch-requirement %} diff --git a/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md b/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md index 98b3b278ed..c78ba6c790 100644 --- a/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md @@ -79,6 +79,7 @@ You can configure the artifact and log retention period for your repository, org - "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" for {% data variables.product.prodname_ghe_cloud %}{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Disabling and enabling workflows You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}. @@ -86,3 +87,4 @@ You can enable and disable individual workflows in your repository on {% data va {% data reusables.actions.scheduled-workflows-disabled %} For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)." +{% endif %} diff --git a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md index b05cc41dbc..77ce7b885f 100644 --- a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md @@ -227,7 +227,7 @@ Each job runs in an environment specified by `runs-on`. You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. -If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/v3/actions/workflow-jobs)." +If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." ### **`jobs.`** @@ -878,34 +878,9 @@ strategy: ##### Using environment variables in a matrix -You can add custom environment variables for each test combination by using `include` with `env`. You can then refer to the custom environment variables in a later step. +You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. -In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: - -{% raw %} -```yaml -name: Node.js CI -on: [push] -jobs: - build: - runs-on: ubuntu-latest - strategy: - matrix: - include: - - node-version: 10.x - site: "prod" - datacenter: "site-a" - - node-version: 12.x - site: "dev" - datacenter: "site-b" - steps: - - name: Echo site details - env: - SITE: ${{ matrix.site }} - DATACENTER: ${{ matrix.datacenter }} - run: echo $SITE $DATACENTER -``` -{% endraw %} +{% data reusables.github-actions.matrix-variable-example %} ### **`jobs..strategy.fail-fast`** diff --git a/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md b/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md index 25be0883c4..4afe0374d7 100644 --- a/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md +++ b/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: User accounts on {% data variables.product.product_location %} are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change. -If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user). +If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). Other issues you should take into consideration include: diff --git a/translations/ru-RU/content/admin/configuration/command-line-utilities.md b/translations/ru-RU/content/admin/configuration/command-line-utilities.md index 495c2290d9..bb95860050 100644 --- a/translations/ru-RU/content/admin/configuration/command-line-utilities.md +++ b/translations/ru-RU/content/admin/configuration/command-line-utilities.md @@ -159,7 +159,7 @@ $ ghe-es-index-status -do | column -ts, #### ghe-legacy-github-services-report -This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/v3/guides/replacing-github-services/)." For more information about this command or for additional options, use the `-h` flag. +This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)." For more information about this command or for additional options, use the `-h` flag. ```shell ghe-legacy-github-services-report diff --git a/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md index 627c419bb1..9cf696baba 100644 --- a/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md +++ b/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md @@ -37,7 +37,7 @@ Enabling {% data variables.product.prodname_github_connect %} also creates a {% Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.prodname_ghe_server %}. -For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." ### Enabling {% data variables.product.prodname_github_connect %} 1. Sign in to diff --git a/translations/ru-RU/content/admin/overview/about-the-github-enterprise-api.md b/translations/ru-RU/content/admin/overview/about-the-github-enterprise-api.md index d2586b8381..8f75a39a07 100644 --- a/translations/ru-RU/content/admin/overview/about-the-github-enterprise-api.md +++ b/translations/ru-RU/content/admin/overview/about-the-github-enterprise-api.md @@ -19,6 +19,6 @@ With the APIs, you can automate many administrative tasks. Some examples include - Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)." - Configure LDAP sync. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %} - Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)." -- Manage your enterprise account. For more information, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +- Manage your enterprise account. For more information, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." -For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). \ No newline at end of file +For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). diff --git a/translations/ru-RU/content/admin/user-management/audited-actions.md b/translations/ru-RU/content/admin/user-management/audited-actions.md index e4c495174c..76a8ffbf10 100644 --- a/translations/ru-RU/content/admin/user-management/audited-actions.md +++ b/translations/ru-RU/content/admin/user-management/audited-actions.md @@ -137,6 +137,6 @@ versions: [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [deploy key]: /guides/managing-deploy-keys/#deploy-keys [generate token]: /articles/creating-an-access-token-for-command-line-use - [OAuth access token]: /v3/oauth/ + [OAuth access token]: /developers/apps/authorizing-oauth-apps [OAuth application]: /guides/basics-of-authentication/#registering-your-app [2fa]: /articles/about-two-factor-authentication diff --git a/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md index 5b4046fe37..2b499848ef 100644 --- a/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md +++ b/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md @@ -27,7 +27,7 @@ versions: To export repository data from {% data variables.product.prodname_dotcom_the_website %}, use the Migrations API. -The Migrations API is currently in a preview period, which means that the endpoints and parameters may change in the future. To access the Migrations API, you must provide a custom [media type](/v3/media) in the `Accept` header: `application/vnd.github.wyandotte-preview+json`. The examples below include the custom media type. +The Migrations API is currently in a preview period, which means that the endpoints and parameters may change in the future. To access the Migrations API, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: `application/vnd.github.wyandotte-preview+json`. The examples below include the custom media type. ### Generating a migration archive @@ -37,7 +37,7 @@ The Migrations API is currently in a preview period, which means that the endpoi 2. Start a migration by `POST`ing to the migration endpoint. You'll need: * Your access token for authentication. - * A [list of the repositories](/v3/repos/#list-organization-repositories) you want to migrate: + * A [list of the repositories](/rest/reference/repos#list-organization-repositories) you want to migrate: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ diff --git a/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md index 14f09e2e6d..863427584f 100644 --- a/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %} -After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository). You'll need your access token for authentication: +After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). You'll need your access token for authentication: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md index dee10d899d..9024201080 100644 --- a/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ You can create a custom message that suspended users will see when attempting to ``` ### Дополнительная литература -- "[Suspend a user](/enterprise/{{ currentVersion }}/v3/enterprise-admin/users/#suspend-a-user)" +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/ru-RU/content/developers/apps/about-apps.md b/translations/ru-RU/content/developers/apps/about-apps.md index 010cd5c2e6..fff85efbab 100644 --- a/translations/ru-RU/content/developers/apps/about-apps.md +++ b/translations/ru-RU/content/developers/apps/about-apps.md @@ -67,13 +67,13 @@ Keep these ideas in mind when creating {% data variables.product.prodname_oauth_ * Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_app %}s authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/v3/guides/basics-of-authentication/#registering-your-app)." +For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." ### Personal access tokens A [personal access token](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A personal access token is also similar to a password, but you can have many of them and you can revoke access to each one at any time. -As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/v3/issues/#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it. +As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it. Keep these ideas in mind when using personal access tokens: diff --git a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md index 750e4ff36a..ec679b8d8c 100644 --- a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md @@ -118,13 +118,13 @@ You'll need to create a new JWT after the time expires. ### Accessing API endpoints as a {% data variables.product.prodname_github_app %} -For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/v3/apps/)." +For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)." ### Authenticating as an installation Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. These installation access tokens are used by {% data variables.product.prodname_github_app %}s to authenticate. -By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour. +By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour. To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request: @@ -144,7 +144,7 @@ $ curl -i -X POST \ ``` {% endif %} -The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint. +The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint. To authenticate with an installation access token, include it in the Authorization header in the API request: @@ -168,9 +168,9 @@ $ curl -i \ ### Accessing API endpoints as an installation -For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_app %}s using an installation access token, see "[Available Endpoints](/v3/apps/available-endpoints/)." +For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_app %}s using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)." -For a list of endpoints related to installations, see "[Installations](/v3/apps/installations/)." +For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)." ### HTTP-based Git access by an installation diff --git a/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md b/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md index 3ef6be158c..9fcdadc687 100644 --- a/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md @@ -235,12 +235,12 @@ For more information, see the "[OAuth 2.0 Device Authorization Grant](https://to ### Non-Web application flow -Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/v3/auth#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. +Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with two-factor authentication](/v3/auth/#working-with-two-factor-authentication) if you or your users have two-factor authentication enabled. +**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if you or your users have two-factor authentication enabled. {% endnote %} {% endif %} @@ -289,7 +289,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% tip %} -**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/v3/guides/discovering-resources-for-a-user/)." +**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." {% endtip %} diff --git a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md index d1eff6877b..b3c1436812 100644 --- a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -52,16 +52,16 @@ The person creating the app will be redirected to a GitHub page with an input fi ##### GitHub App Manifest parameters - | Name | Тип | Description | - | --------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `строка` | The name of the GitHub App. | - | `url` | `строка` | **Required.** The homepage of your GitHub App. | - | `hook_attributes` | `объект` | The configuration of the GitHub App's webhook. | - | `redirect_url` | `строка` | The full URL to redirect to after the person installs the GitHub App. | - | `описание` | `строка` | A description of the GitHub App. | - | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | - | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | - | `default_permissions` | `объект` | The set of [permissions](/v3/apps/permissions/) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | + | Name | Тип | Description | + | --------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `строка` | The name of the GitHub App. | + | `url` | `строка` | **Required.** The homepage of your GitHub App. | + | `hook_attributes` | `объект` | The configuration of the GitHub App's webhook. | + | `redirect_url` | `строка` | The full URL to redirect to after the person installs the GitHub App. | + | `описание` | `строка` | A description of the GitHub App. | + | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | + | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | + | `default_permissions` | `объект` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | The `hook_attributes` object has the following key: @@ -153,13 +153,13 @@ If you provided a `state` parameter, you will also see that parameter in the `re #### 3. You exchange the temporary code to retrieve the app configuration -To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. +To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. You must complete this step of the GitHub App Manifest flow within one hour. {% note %} -**Note:** This endpoint is rate limited. See [Rate limits](/v3/rate_limit/) to learn how to get your current rate limit status. +**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status. {% endnote %} @@ -170,7 +170,7 @@ You must complete this step of the GitHub App Manifest flow within one hour. POST /app-manifests/:code/conversions -For more information about the endpoint's response, see [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest). +For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest). When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time. @@ -191,4 +191,4 @@ Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file #### Hosting your app with Glitch -You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/v3/checks/) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. +You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. diff --git a/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md index 0411e5dbd9..79419f195d 100644 --- a/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -49,37 +49,37 @@ The complete list of available query parameters, permissions, and events is list You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission. -| Permission | Description | -| -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Permission | Description | +| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/v3/users/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/v3/checks/). Can be one of: `none`, `read`, or `write`. | -| `content_references` | Grants access to the "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. | -| [`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. | +| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`. | +| `content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. | +| [`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. | | [`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/v3/users/emails/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/v3/users/followers/). Can be one of: `none`, `read`, or `write`. | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/v3/users/gpg_keys/). Can be one of: `none`, `read`, or `write`. | -| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/v3/issues/). Can be one of: `none`, `read`, or `write`. | -| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/v3/users/keys/). Can be one of: `none`, `read`, or `write`. | +| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`. | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`. | +| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`. | +| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`. | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`метаданные`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. | -| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/v3/orgs/#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`. | -| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/v3/orgs/#get-an-organization)" endpoint. Can be one of: `none` or `read`. | -| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} -| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/v3/orgs/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`. | -| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/v3/users/#get-a-user)" endpoint. Can be one of: `none` or `read`. | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/v3/repos/hooks/). Can be one of: `none`, `read`, or `write`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`. | -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/v3/repos/contents/). Can be one of: `none`, `read`, or `write`. | -| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/v3/activity/starring/). Can be one of: `none`, `read`, or `write`. | -| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/v3/repos/statuses/). Can be one of: `none`, `read`, or `write`. | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/v3/teams/discussions/) and the [Team Discussion Comments API](/v3/teams/discussion_comments/). Can be one of: `none`, `read`, or `write`. | -| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. | -| `наблюдение` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. | +| [`метаданные`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. | +| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`. | +| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`. | +| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} +| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +| [`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`. | +| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`. | +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. | +| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. | +| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`. | +| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. | +| `наблюдение` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. | ### {% data variables.product.prodname_github_app %} webhook events diff --git a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 180fcb0b9b..1b0011c690 100644 --- a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introduction -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/v3/checks/), which you'll use to build a continuous integration (CI) server that runs tests. +This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts. 🙌 @@ -22,15 +22,15 @@ A CI server hosts code that runs CI tests such as code linters (which check styl #### Checks API overview -The [Checks API](/v3/checks/) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. +The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. -A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/v3/repos/branches/) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. +A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. -The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: +The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: 1. Whenever someone pushes code to the repository, GitHub sends the `check_suite` event with an action of `requested` to all GitHub Apps installed on the repository that have the `checks:write` permission. This event lets the apps know that code was pushed and that GitHub has automatically created a new check suite. -1. When your app receives this event, it can [add check runs](/v3/checks/runs/#create-a-check-run) to that suite. -1. Your check runs can include [annotations](/v3/checks/runs/#annotations-object) that are displayed on specific lines of code. +1. When your app receives this event, it can [add check runs](/rest/reference/checks#create-a-check-run) to that suite. +1. Your check runs can include [annotations](/rest/reference/checks#annotations-object) that are displayed on specific lines of code. **In this guide, you’ll learn how to:** @@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t ### Требования -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/v3/checks/), if you're not already. You'll find more APIs in the [REST API docs](/v3/). The Checks API is also available to use in [GraphQL](/v4/), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/v4/object/checksuite/) and [Check Run](/v4/object/checkrun/) objects for more details. +Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app. @@ -140,12 +140,11 @@ You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sina def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { - # This header allows for beta access to Checks API - accept: 'application/vnd.github.antiope-preview+json', + accept: 'application/vnd.github.v3+json', # The name of your check run. name: 'Octo RuboCop', # The payload structure differs depending on whether a check run or a check suite event occurred. @@ -160,7 +159,7 @@ end def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -176,7 +175,7 @@ end ``` {% endif %} -This code calls the "[Create a check run](/v3/checks/runs/#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method. +This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method. To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [Rubocop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo Rubocop" is used here, but you can choose any name you'd like for the check run. @@ -241,7 +240,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -277,7 +276,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -306,11 +305,11 @@ end ``` {% endif %} -The code above calls the "[Update a check run](/v3/checks/runs/#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. +The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. Here's what this code is doing. First, it updates the check run's status to `in_progress` and sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`. -You'll notice in the "[Update a check run](/v3/checks/runs/#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`. +You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`. You could also provide more details about what your check is doing, but you'll get to that in the next section. Let's test this code again by re-running `template_server.rb`: @@ -436,7 +435,7 @@ The code above gets the full repository name and the head SHA of the commit from ### Step 2.3. Running RuboCop -Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/v3/checks/runs/#create-a-check-run). +Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. @@ -524,11 +523,11 @@ You should see the linting errors in the debug output, although they aren't prin The `@output` variable contains the parsed JSON results of the RuboCop report. As shown above, the results contain a `summary` section that your code can use to quickly determine if there are any errors. The following code will set the check run conclusion to `success` when there are no reported errors. RuboCop reports errors for each file in the `files` array, so if there are errors, you'll need to extract some data from the file object. -The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/v3/checks/runs/#update-a-check-run) with annotations. +The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/rest/reference/checks#update-a-check-run) with annotations. -The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. +The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. -A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/v3/checks/runs/#annotations-object-1) reference documentation for details. +A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/rest/reference/checks#annotations-object-1) reference documentation for details. You'll extract the required information from RuboCop needed to create each annotation. Append the following code to the code you added in the [previous section](#step-23-running-rubocop): @@ -537,7 +536,7 @@ annotations = [] # You can create a maximum of 50 annotations per request to the Checks # API. To add more than 50 annotations, use the "Update a check run" API # endpoint. This example code limits the number of annotations to 50. -# See /v3/checks/runs/#update-a-check-run +# See /rest/reference/checks#update-a-check-run # for details. max_annotations = 50 @@ -870,4 +869,4 @@ After walking through this guide, you've learned the basics of using the Checks Here are some ideas for what you can do next: * Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors. -* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/v3/pulls/#create-a-pull-request) with a new branch based on the head branch. +* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch. diff --git a/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 018ea4f338..2699b681e6 100644 --- a/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -90,10 +90,10 @@ Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to requ ### Git access -| GitHub Apps | OAuth Apps | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | -| The token is used as the HTTP password. | The token is used as the HTTP username. | +| GitHub Apps | OAuth Apps | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/repos#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | +| The token is used as the HTTP password. | The token is used as the HTTP username. | ### Machine vs. bot accounts diff --git a/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index f24f47be90..5257e05dec 100644 --- a/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -67,7 +67,7 @@ If the user accepts your request, GitHub redirects back to your site with a temp {% endnote %} -Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." +Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)." Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} @@ -154,7 +154,7 @@ You can also check which repositories are accessible to a user for an installati Authorization: token OAUTH-TOKEN GET /user/installations/:installation_id/repositories -More details can be found in: [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token). +More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). ### Handling a revoked GitHub App authorization @@ -162,7 +162,7 @@ If a user revokes their authorization of a GitHub App, the app will receive the ### User-level permissions -You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/v3/apps/permissions/), which are granted at the time of installation on an organization or user account. +You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account. You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." @@ -172,75 +172,75 @@ Because user-level permissions are granted on an individual user basis, you can ### User-to-server requests -While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/v4/) or [REST v3](/v3/) endpoints. +While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/graphql) or [REST v3](/rest) endpoints. #### Supported endpoints {% if currentVersion == "free-pro-team@latest" %} ##### Actions Runners -* [List runner applications for a repository](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) -* [List self-hosted runners for a repository](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) -* [Get a self-hosted runner for a repository](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) -* [Delete a self-hosted runner from a repository](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) -* [Create a registration token for a repository](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) -* [Create a remove token for a repository](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) -* [List runner applications for an organization](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) -* [List self-hosted runners for an organization](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) -* [Get a self-hosted runner for an organization](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) -* [Delete a self-hosted runner from an organization](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) -* [Create a registration token for an organization](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) -* [Create a remove token for an organization](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) +* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository) +* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization) +* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization) ##### Actions Secrets -* [Get a repository public key](/v3/actions/secrets/#get-a-repository-public-key) -* [List repository secrets](/v3/actions/secrets/#list-repository-secrets) -* [Get a repository secret](/v3/actions/secrets/#get-a-repository-secret) -* [Create or update a repository secret](/v3/actions/secrets/#create-or-update-a-repository-secret) -* [Delete a repository secret](/v3/actions/secrets/#delete-a-repository-secret) -* [Get an organization public key](/v3/actions/secrets/#get-an-organization-public-key) -* [List organization secrets](/v3/actions/secrets/#list-organization-secrets) -* [Get an organization secret](/v3/actions/secrets/#get-an-organization-secret) -* [Create or update an organization secret](/v3/actions/secrets/#create-or-update-an-organization-secret) -* [List selected repositories for an organization secret](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) -* [Set selected repositories for an organization secret](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) -* [Add selected repository to an organization secret](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) -* [Remove selected repository from an organization secret](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) -* [Delete an organization secret](/v3/actions/secrets/#delete-an-organization-secret) +* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key) +* [List repository secrets](/rest/reference/actions#list-repository-secrets) +* [Get a repository secret](/rest/reference/actions#get-a-repository-secret) +* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret) +* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret) +* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key) +* [List organization secrets](/rest/reference/actions#list-organization-secrets) +* [Get an organization secret](/rest/reference/actions#get-an-organization-secret) +* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret) +* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Artifacts -* [List artifacts for a repository](/v3/actions/artifacts/#list-artifacts-for-a-repository) -* [List workflow run artifacts](/v3/actions/artifacts/#list-workflow-run-artifacts) -* [Get an artifact](/v3/actions/artifacts/#get-an-artifact) -* [Delete an artifact](/v3/actions/artifacts/#delete-an-artifact) -* [Download an artifact](/v3/actions/artifacts/#download-an-artifact) +* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository) +* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts) +* [Get an artifact](/rest/reference/actions#get-an-artifact) +* [Delete an artifact](/rest/reference/actions#delete-an-artifact) +* [Download an artifact](/rest/reference/actions#download-an-artifact) {% endif %} ##### Check Runs -* [Create a check run](/v3/checks/runs/#create-a-check-run) -* [Get a check run](/v3/checks/runs/#get-a-check-run) -* [Update a check run](/v3/checks/runs/#update-a-check-run) -* [List check run annotations](/v3/checks/runs/#list-check-run-annotations) -* [List check runs in a check suite](/v3/checks/runs/#list-check-runs-in-a-check-suite) -* [List check runs for a Git reference](/v3/checks/runs/#list-check-runs-for-a-git-reference) +* [Create a check run](/rest/reference/checks#create-a-check-run) +* [Get a check run](/rest/reference/checks#get-a-check-run) +* [Update a check run](/rest/reference/checks#update-a-check-run) +* [List check run annotations](/rest/reference/checks#list-check-run-annotations) +* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference) ##### Проверить пакеты -* [Create a check suite](/v3/checks/suites/#create-a-check-suite) -* [Get a check suite](/v3/checks/suites/#get-a-check-suite) -* [Rerequest a check suite](/v3/checks/suites/#rerequest-a-check-suite) -* [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) -* [List check suites for a Git reference](/v3/checks/suites/#list-check-suites-for-a-git-reference) +* [Create a check suite](/rest/reference/checks#create-a-check-suite) +* [Get a check suite](/rest/reference/checks#get-a-check-suite) +* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite) +* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference) ##### Codes Of Conduct -* [Get all codes of conduct](/v3/codes_of_conduct/#get-all-codes-of-conduct) -* [Get a code of conduct](/v3/codes_of_conduct/#get-a-code-of-conduct) +* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct) ##### Deployment Statuses @@ -266,128 +266,128 @@ While most of your API interaction should occur using your server-to-server inst ##### Git Blobs -* [Create a blob](/v3/git/blobs/#create-a-blob) -* [Get a blob](/v3/git/blobs/#get-a-blob) +* [Create a blob](/rest/reference/git#create-a-blob) +* [Get a blob](/rest/reference/git#get-a-blob) ##### Git Commits -* [Create a commit](/v3/git/commits/#create-a-commit) -* [Get a commit](/v3/git/commits/#get-a-commit) +* [Create a commit](/rest/reference/git#create-a-commit) +* [Get a commit](/rest/reference/git#get-a-commit) ##### Git Refs -* [Create a reference](/v3/git/refs/#create-a-reference)* [Get a reference](/v3/git/refs/#get-a-reference) -* [List matching references](/v3/git/refs/#list-matching-references) -* [Update a reference](/v3/git/refs/#update-a-reference) -* [Delete a reference](/v3/git/refs/#delete-a-reference) +* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference) +* [List matching references](/rest/reference/git#list-matching-references) +* [Update a reference](/rest/reference/git#update-a-reference) +* [Delete a reference](/rest/reference/git#delete-a-reference) ##### Git Tags -* [Create a tag object](/v3/git/tags/#create-a-tag-object) -* [Get a tag](/v3/git/tags/#get-a-tag) +* [Create a tag object](/rest/reference/git#create-a-tag-object) +* [Get a tag](/rest/reference/git#get-a-tag) ##### Git Trees -* [Create a tree](/v3/git/trees/#create-a-tree) -* [Get a tree](/v3/git/trees/#get-a-tree) +* [Create a tree](/rest/reference/git#create-a-tree) +* [Get a tree](/rest/reference/git#get-a-tree) ##### Gitignore Templates -* [Get all gitignore templates](/v3/gitignore/#get-all-gitignore-templates) -* [Get a gitignore template](/v3/gitignore/#get-a-gitignore-template) +* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates) +* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template) ##### Installations -* [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token) +* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} ##### Interaction Limits -* [Get interaction restrictions for an organization](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) -* [Set interaction restrictions for an organization](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) -* [Remove interaction restrictions for an organization](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) -* [Get interaction restrictions for a repository](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) -* [Set interaction restrictions for a repository](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) -* [Remove interaction restrictions for a repository](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) +* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) {% endif %} ##### Issue Assignees -* [Add assignees to an issue](/v3/issues/assignees/#add-assignees-to-an-issue) -* [Remove assignees from an issue](/v3/issues/assignees/#remove-assignees-from-an-issue) +* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue) +* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue) ##### Issue Comments -* [List issue comments](/v3/issues/comments/#list-issue-comments) -* [Create an issue comment](/v3/issues/comments/#create-an-issue-comment) -* [List issue comments for a repository](/v3/issues/comments/#list-issue-comments-for-a-repository) -* [Get an issue comment](/v3/issues/comments/#get-an-issue-comment) -* [Update an issue comment](/v3/issues/comments/#update-an-issue-comment) -* [Delete an issue comment](/v3/issues/comments/#delete-an-issue-comment) +* [List issue comments](/rest/reference/issues#list-issue-comments) +* [Create an issue comment](/rest/reference/issues#create-an-issue-comment) +* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository) +* [Get an issue comment](/rest/reference/issues#get-an-issue-comment) +* [Update an issue comment](/rest/reference/issues#update-an-issue-comment) +* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment) ##### Issue Events -* [List issue events](/v3/issues/events/#list-issue-events) +* [List issue events](/rest/reference/issues#list-issue-events) ##### Issue Timeline -* [List timeline events for an issue](/v3/issues/timeline/#list-timeline-events-for-an-issue) +* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue) ##### Вопросы -* [List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user) -* [List assignees](/v3/issues/assignees/#list-assignees) -* [Check if a user can be assigned](/v3/issues/assignees/#check-if-a-user-can-be-assigned) -* [List repository issues](/v3/issues/#list-repository-issues) -* [Create an issue](/v3/issues/#create-an-issue) -* [Get an issue](/v3/issues/#get-an-issue) -* [Update an issue](/v3/issues/#update-an-issue) -* [Lock an issue](/v3/issues/#lock-an-issue) -* [Unlock an issue](/v3/issues/#unlock-an-issue) +* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [List assignees](/rest/reference/issues#list-assignees) +* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [List repository issues](/rest/reference/issues#list-repository-issues) +* [Create an issue](/rest/reference/issues#create-an-issue) +* [Get an issue](/rest/reference/issues#get-an-issue) +* [Update an issue](/rest/reference/issues#update-an-issue) +* [Lock an issue](/rest/reference/issues#lock-an-issue) +* [Unlock an issue](/rest/reference/issues#unlock-an-issue) {% if currentVersion == "free-pro-team@latest" %} ##### Jobs -* [Get a job for a workflow run](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) -* [Download job logs for a workflow run](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) -* [List jobs for a workflow run](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) +* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run) {% endif %} ##### Labels -* [List labels for an issue](/v3/issues/labels/#list-labels-for-an-issue) -* [Add labels to an issue](/v3/issues/labels/#add-labels-to-an-issue) -* [Set labels for an issue](/v3/issues/labels/#set-labels-for-an-issue) -* [Remove all labels from an issue](/v3/issues/labels/#remove-all-labels-from-an-issue) -* [Remove a label from an issue](/v3/issues/labels/#remove-a-label-from-an-issue) -* [List labels for a repository](/v3/issues/labels/#list-labels-for-a-repository) -* [Create a label](/v3/issues/labels/#create-a-label) -* [Get a label](/v3/issues/labels/#get-a-label) -* [Update a label](/v3/issues/labels/#update-a-label) -* [Delete a label](/v3/issues/labels/#delete-a-label) -* [Get labels for every issue in a milestone](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) +* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue) +* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue) +* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue) +* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue) +* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue) +* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository) +* [Create a label](/rest/reference/issues#create-a-label) +* [Get a label](/rest/reference/issues#get-a-label) +* [Update a label](/rest/reference/issues#update-a-label) +* [Delete a label](/rest/reference/issues#delete-a-label) +* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone) ##### Licenses -* [Get all commonly used licenses](/v3/licenses/#get-all-commonly-used-licenses) -* [Get a license](/v3/licenses/#get-a-license) +* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses) +* [Get a license](/rest/reference/licenses#get-a-license) ##### Markdown -* [Render a Markdown document](/v3/markdown/#render-a-markdown-document) -* [Render a markdown document in raw mode](/v3/markdown/#render-a-markdown-document-in-raw-mode) +* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document) +* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) ##### Meta -* [Meta](/v3/meta/#meta) +* [Meta](/rest/reference/meta#meta) ##### Milestones -* [List milestones](/v3/issues/milestones/#list-milestones) -* [Create a milestone](/v3/issues/milestones/#create-a-milestone) -* [Get a milestone](/v3/issues/milestones/#get-a-milestone) -* [Update a milestone](/v3/issues/milestones/#update-a-milestone) -* [Delete a milestone](/v3/issues/milestones/#delete-a-milestone) +* [List milestones](/rest/reference/issues#list-milestones) +* [Create a milestone](/rest/reference/issues#create-a-milestone) +* [Get a milestone](/rest/reference/issues#get-a-milestone) +* [Update a milestone](/rest/reference/issues#update-a-milestone) +* [Delete a milestone](/rest/reference/issues#delete-a-milestone) ##### Organization Hooks @@ -401,29 +401,29 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Organization Invitations -* [List pending organization invitations](/v3/orgs/members/#list-pending-organization-invitations) -* [Create an organization invitation](/v3/orgs/members/#create-an-organization-invitation) -* [List organization invitation teams](/v3/orgs/members/#list-organization-invitation-teams) +* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations) +* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation) +* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams) {% endif %} ##### Organization Members -* [List organization members](/v3/orgs/members/#list-organization-members) -* [Check organization membership for a user](/v3/orgs/members/#check-organization-membership-for-a-user) -* [Remove an organization member](/v3/orgs/members/#remove-an-organization-member) -* [Get organization membership for a user](/v3/orgs/members/#get-organization-membership-for-a-user) -* [Set organization membership for a user](/v3/orgs/members/#set-organization-membership-for-a-user) -* [Remove organization membership for a user](/v3/orgs/members/#remove-organization-membership-for-a-user) -* [List public organization members](/v3/orgs/members/#list-public-organization-members) -* [Check public organization membership for a user](/v3/orgs/members/#check-public-organization-membership-for-a-user) -* [Set public organization membership for the authenticated user](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) -* [Remove public organization membership for the authenticated user](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) +* [List organization members](/rest/reference/orgs#list-organization-members) +* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user) +* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member) +* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user) +* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user) +* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [List public organization members](/rest/reference/orgs#list-public-organization-members) +* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) ##### Organization Outside Collaborators -* [List outside collaborators for an organization](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) -* [Convert an organization member to outside collaborator](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) -* [Remove outside collaborator from an organization](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) +* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) {% if enterpriseServerVersions contains currentVersion %} ##### Organization Pre Receive Hooks @@ -437,198 +437,198 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Organization Team Projects -* [List team projects](/v3/teams/#list-team-projects) -* [Check team permissions for a project](/v3/teams/#check-team-permissions-for-a-project) -* [Add or update team project permissions](/v3/teams/#add-or-update-team-project-permissions) -* [Remove a project from a team](/v3/teams/#remove-a-project-from-a-team) +* [List team projects](/rest/reference/teams#list-team-projects) +* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project) +* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions) +* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team) {% endif %} ##### Organization Team Repositories -* [List team repositories](/v3/teams/#list-team-repositories) -* [Check team permissions for a repository](/v3/teams/#check-team-permissions-for-a-repository) -* [Add or update team repository permissions](/v3/teams/#add-or-update-team-repository-permissions) -* [Remove a repository from a team](/v3/teams/#remove-a-repository-from-a-team) +* [List team repositories](/rest/reference/teams#list-team-repositories) +* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository) +* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions) +* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team) {% if currentVersion == "free-pro-team@latest" %} ##### Organization Team Sync -* [List idp groups for a team](/v3/teams/team_sync/#list-idp-groups-for-a-team) -* [Create or update idp group connections](/v3/teams/team_sync/#create-or-update-idp-group-connections) -* [List IdP groups for an organization](/v3/teams/team_sync/#list-idp-groups-for-an-organization) +* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team) +* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections) +* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} ##### Organization Teams -* [List teams](/v3/teams/#list-teams) -* [Create a team](/v3/teams/#create-a-team) -* [Get a team by name](/v3/teams/#get-a-team-by-name) +* [List teams](/rest/reference/teams#list-teams) +* [Create a team](/rest/reference/teams#create-a-team) +* [Get a team by name](/rest/reference/teams#get-a-team-by-name) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -* [Get a team](/v3/teams/#get-a-team) +* [Get a team](/rest/reference/teams#get-a-team) {% endif %} -* [Update a team](/v3/teams/#update-a-team) -* [Delete a team](/v3/teams/#delete-a-team) +* [Update a team](/rest/reference/teams#update-a-team) +* [Delete a team](/rest/reference/teams#delete-a-team) {% if currentVersion == "free-pro-team@latest" %} -* [List pending team invitations](/v3/teams/members/#list-pending-team-invitations) +* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations) {% endif %} -* [List team members](/v3/teams/members/#list-team-members) -* [Get team membership for a user](/v3/teams/members/#get-team-membership-for-a-user) -* [Add or update team membership for a user](/v3/teams/members/#add-or-update-team-membership-for-a-user) -* [Remove team membership for a user](/v3/teams/members/#remove-team-membership-for-a-user) -* [List child teams](/v3/teams/#list-child-teams) -* [List teams for the authenticated user](/v3/teams/#list-teams-for-the-authenticated-user) +* [List team members](/rest/reference/teams#list-team-members) +* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user) +* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) +* [List child teams](/rest/reference/teams#list-child-teams) +* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user) ##### Organizations -* [List organizations](/v3/orgs/#list-organizations) -* [Get an organization](/v3/orgs/#get-an-organization) -* [Update an organization](/v3/orgs/#update-an-organization) -* [List organization memberships for the authenticated user](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) -* [Get an organization membership for the authenticated user](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) -* [Update an organization membership for the authenticated user](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) -* [List organizations for the authenticated user](/v3/orgs/#list-organizations-for-the-authenticated-user) -* [List organizations for a user](/v3/orgs/#list-organizations-for-a-user) +* [List organizations](/rest/reference/orgs#list-organizations) +* [Get an organization](/rest/reference/orgs#get-an-organization) +* [Update an organization](/rest/reference/orgs#update-an-organization) +* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Credential Authorizations -* [List SAML SSO authorizations for an organization](/v3/orgs/#list-saml-sso-authorizations-for-an-organization) -* [Remove a SAML SSO authorization for an organization](/v3/orgs/#remove-a-saml-sso-authorization-for-an-organization) +* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Organizations Scim -* [List SCIM provisioned identities](/v3/scim/#list-scim-provisioned-identities) -* [Provision and invite a SCIM user](/v3/scim/#provision-and-invite-a-scim-user) -* [Get SCIM provisioning information for a user](/v3/scim/#get-scim-provisioning-information-for-a-user) -* [Set SCIM information for a provisioned user](/v3/scim/#set-scim-information-for-a-provisioned-user) -* [Update an attribute for a SCIM user](/v3/scim/#update-an-attribute-for-a-scim-user) -* [Delete a SCIM user from an organization](/v3/scim/#delete-a-scim-user-from-an-organization) +* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities) +* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user) +* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Source Imports -* [Get an import status](/v3/migrations/source_imports/#get-an-import-status) -* [Start an import](/v3/migrations/source_imports/#start-an-import) -* [Update an import](/v3/migrations/source_imports/#update-an-import) -* [Cancel an import](/v3/migrations/source_imports/#cancel-an-import) -* [Get commit authors](/v3/migrations/source_imports/#get-commit-authors) -* [Map a commit author](/v3/migrations/source_imports/#map-a-commit-author) -* [Get large files](/v3/migrations/source_imports/#get-large-files) -* [Update Git LFS preference](/v3/migrations/source_imports/#update-git-lfs-preference) +* [Get an import status](/rest/reference/migrations#get-an-import-status) +* [Start an import](/rest/reference/migrations#start-an-import) +* [Update an import](/rest/reference/migrations#update-an-import) +* [Cancel an import](/rest/reference/migrations#cancel-an-import) +* [Get commit authors](/rest/reference/migrations#get-commit-authors) +* [Map a commit author](/rest/reference/migrations#map-a-commit-author) +* [Get large files](/rest/reference/migrations#get-large-files) +* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference) {% endif %} ##### Project Collaborators -* [List project collaborators](/v3/projects/collaborators/#list-project-collaborators) -* [Add project collaborator](/v3/projects/collaborators/#add-project-collaborator) -* [Remove project collaborator](/v3/projects/collaborators/#remove-project-collaborator) -* [Get project permission for a user](/v3/projects/collaborators/#get-project-permission-for-a-user) +* [List project collaborators](/rest/reference/projects#list-project-collaborators) +* [Add project collaborator](/rest/reference/projects#add-project-collaborator) +* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator) +* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user) ##### Projects -* [List organization projects](/v3/projects/#list-organization-projects) -* [Create an organization project](/v3/projects/#create-an-organization-project) -* [Get a project](/v3/projects/#get-a-project) -* [Update a project](/v3/projects/#update-a-project) -* [Delete a project](/v3/projects/#delete-a-project) -* [List project columns](/v3/projects/columns/#list-project-columns) -* [Create a project column](/v3/projects/columns/#create-a-project-column) -* [Get a project column](/v3/projects/columns/#get-a-project-column) -* [Update a project column](/v3/projects/columns/#update-a-project-column) -* [Delete a project column](/v3/projects/columns/#delete-a-project-column) -* [List project cards](/v3/projects/cards/#list-project-cards) -* [Create a project card](/v3/projects/cards/#create-a-project-card) -* [Move a project column](/v3/projects/columns/#move-a-project-column) -* [Get a project card](/v3/projects/cards/#get-a-project-card) -* [Update a project card](/v3/projects/cards/#update-a-project-card) -* [Delete a project card](/v3/projects/cards/#delete-a-project-card) -* [Move a project card](/v3/projects/cards/#move-a-project-card) -* [List repository projects](/v3/projects/#list-repository-projects) -* [Create a repository project](/v3/projects/#create-a-repository-project) +* [List organization projects](/rest/reference/projects#list-organization-projects) +* [Create an organization project](/rest/reference/projects#create-an-organization-project) +* [Get a project](/rest/reference/projects#get-a-project) +* [Update a project](/rest/reference/projects#update-a-project) +* [Delete a project](/rest/reference/projects#delete-a-project) +* [List project columns](/rest/reference/projects#list-project-columns) +* [Create a project column](/rest/reference/projects#create-a-project-column) +* [Get a project column](/rest/reference/projects#get-a-project-column) +* [Update a project column](/rest/reference/projects#update-a-project-column) +* [Delete a project column](/rest/reference/projects#delete-a-project-column) +* [List project cards](/rest/reference/projects#list-project-cards) +* [Create a project card](/rest/reference/projects#create-a-project-card) +* [Move a project column](/rest/reference/projects#move-a-project-column) +* [Get a project card](/rest/reference/projects#get-a-project-card) +* [Update a project card](/rest/reference/projects#update-a-project-card) +* [Delete a project card](/rest/reference/projects#delete-a-project-card) +* [Move a project card](/rest/reference/projects#move-a-project-card) +* [List repository projects](/rest/reference/projects#list-repository-projects) +* [Create a repository project](/rest/reference/projects#create-a-repository-project) ##### Pull Comments -* [List review comments on a pull request](/v3/pulls/comments/#list-review-comments-on-a-pull-request) -* [Create a review comment for a pull request](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) -* [List review comments in a repository](/v3/pulls/comments/#list-review-comments-in-a-repository) -* [Get a review comment for a pull request](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) -* [Update a review comment for a pull request](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) -* [Delete a review comment for a pull request](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) +* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository) +* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) ##### Pull Request Review Events -* [Dismiss a review for a pull request](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) -* [Submit a review for a pull request](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) +* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request) ##### Pull Request Review Requests -* [List requested reviewers for a pull request](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) -* [Request reviewers for a pull request](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) -* [Remove requested reviewers from a pull request](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) +* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) ##### Pull Request Reviews -* [List reviews for a pull request](/v3/pulls/reviews/#list-reviews-for-a-pull-request) -* [Create a review for a pull request](/v3/pulls/reviews/#create-a-review-for-a-pull-request) -* [Get a review for a pull request](/v3/pulls/reviews/#get-a-review-for-a-pull-request) -* [Update a review for a pull request](/v3/pulls/reviews/#update-a-review-for-a-pull-request) -* [List comments for a pull request review](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) +* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review) ##### Pulls -* [List pull requests](/v3/pulls/#list-pull-requests) -* [Create a pull request](/v3/pulls/#create-a-pull-request) -* [Get a pull request](/v3/pulls/#get-a-pull-request) -* [Update a pull request](/v3/pulls/#update-a-pull-request) -* [List commits on a pull request](/v3/pulls/#list-commits-on-a-pull-request) -* [List pull requests files](/v3/pulls/#list-pull-requests-files) -* [Check if a pull request has been merged](/v3/pulls/#check-if-a-pull-request-has-been-merged) -* [Merge a pull request (Merge Button)](/v3/pulls/#merge-a-pull-request) +* [List pull requests](/rest/reference/pulls#list-pull-requests) +* [Create a pull request](/rest/reference/pulls#create-a-pull-request) +* [Get a pull request](/rest/reference/pulls#get-a-pull-request) +* [Update a pull request](/rest/reference/pulls#update-a-pull-request) +* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request) +* [List pull requests files](/rest/reference/pulls#list-pull-requests-files) +* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request) ##### Reactions -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/v3/reactions/#delete-a-reaction-legacy){% else %}* [Delete a reaction](/v3/reactions/#delete-a-reaction){% endif %} -* [List reactions for a commit comment](/v3/reactions/#list-reactions-for-a-commit-comment) -* [Create reaction for a commit comment](/v3/reactions/#create-reaction-for-a-commit-comment) -* [List reactions for an issue](/v3/reactions/#list-reactions-for-an-issue) -* [Create reaction for an issue](/v3/reactions/#create-reaction-for-an-issue) -* [List reactions for an issue comment](/v3/reactions/#list-reactions-for-an-issue-comment) -* [Create reaction for an issue comment](/v3/reactions/#create-reaction-for-an-issue-comment) -* [List reactions for a pull request review comment](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) -* [Create reaction for a pull request review comment](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) -* [List reactions for a team discussion comment](/v3/reactions/#list-reactions-for-a-team-discussion-comment) -* [Create reaction for a team discussion comment](/v3/reactions/#create-reaction-for-a-team-discussion-comment) -* [List reactions for a team discussion](/v3/reactions/#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/v3/reactions/#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a commit comment reaction](/v3/reactions/#delete-a-commit-comment-reaction) -* [Delete an issue reaction](/v3/reactions/#delete-an-issue-reaction) -* [Delete a reaction to a commit comment](/v3/reactions/#delete-an-issue-comment-reaction) -* [Delete a pull request comment reaction](/v3/reactions/#delete-a-pull-request-comment-reaction) -* [Delete team discussion reaction](/v3/reactions/#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/v3/reactions/#delete-team-discussion-comment-reaction){% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %} +* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue) +* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue) +* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction) +* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction) +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} ##### Repositories -* [List organization repositories](/v3/repos/#list-organization-repositories) -* [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) -* [Get a repository](/v3/repos/#get-a-repository) -* [Update a repository](/v3/repos/#update-a-repository) -* [Delete a repository](/v3/repos/#delete-a-repository) -* [Compare two commits](/v3/repos/commits/#compare-two-commits) -* [List repository contributors](/v3/repos/#list-repository-contributors) +* [List organization repositories](/rest/reference/repos#list-organization-repositories) +* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [Get a repository](/rest/reference/repos#get-a-repository) +* [Update a repository](/rest/reference/repos#update-a-repository) +* [Delete a repository](/rest/reference/repos#delete-a-repository) +* [Compare two commits](/rest/reference/repos#compare-two-commits) +* [List repository contributors](/rest/reference/repos#list-repository-contributors) * [List forks](/rest/reference/repos#list-forks) -* [Create a fork](/v3/repos/forks/#create-a-fork) -* [List repository languages](/v3/repos/#list-repository-languages) -* [List repository tags](/v3/repos/#list-repository-tags) -* [List repository teams](/v3/repos/#list-repository-teams) -* [Transfer a repository](/v3/repos/#transfer-a-repository) -* [List public repositories](/v3/repos/#list-public-repositories) -* [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) -* [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -* [Create repository using a repository template](/v3/repos/#create-repository-using-a-repository-template) +* [Create a fork](/rest/reference/repos#create-a-fork) +* [List repository languages](/rest/reference/repos#list-repository-languages) +* [List repository tags](/rest/reference/repos#list-repository-tags) +* [List repository teams](/rest/reference/repos#list-repository-teams) +* [Transfer a repository](/rest/reference/repos#transfer-a-repository) +* [List public repositories](/rest/reference/repos#list-public-repositories) +* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user) +* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template) ##### Repository Activity @@ -643,116 +643,116 @@ While most of your API interaction should occur using your server-to-server inst {% if currentVersion == "free-pro-team@latest" %} ##### Repository Automated Security Fixes -* [Enable automated security fixes](/v3/repos/#enable-automated-security-fixes) -* [Disable automated security fixes](/v3/repos/#disable-automated-security-fixes) +* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes) +* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes) {% endif %} ##### Repository Branches -* [List branches](/v3/repos/branches/#list-branches) -* [Get a branch](/v3/repos/branches/#get-a-branch) -* [Get branch protection](/v3/repos/branches/#get-branch-protection) -* [Update branch protection](/v3/repos/branches/#update-branch-protection) -* [Delete branch protection](/v3/repos/branches/#delete-branch-protection) -* [Get admin branch protection](/v3/repos/branches/#get-admin-branch-protection) -* [Set admin branch protection](/v3/repos/branches/#set-admin-branch-protection) -* [Delete admin branch protection](/v3/repos/branches/#delete-admin-branch-protection) -* [Get pull request review protection](/v3/repos/branches/#get-pull-request-review-protection) -* [Update pull request review protection](/v3/repos/branches/#update-pull-request-review-protection) -* [Delete pull request review protection](/v3/repos/branches/#delete-pull-request-review-protection) -* [Get commit signature protection](/v3/repos/branches/#get-commit-signature-protection) -* [Create commit signature protection](/v3/repos/branches/#create-commit-signature-protection) -* [Delete commit signature protection](/v3/repos/branches/#delete-commit-signature-protection) -* [Get status checks protection](/v3/repos/branches/#get-status-checks-protection) -* [Update status check protection](/v3/repos/branches/#update-status-check-protection) -* [Remove status check protection](/v3/repos/branches/#remove-status-check-protection) -* [Get all status check contexts](/v3/repos/branches/#get-all-status-check-contexts) -* [Add status check contexts](/v3/repos/branches/#add-status-check-contexts) -* [Set status check contexts](/v3/repos/branches/#set-status-check-contexts) -* [Remove status check contexts](/v3/repos/branches/#remove-status-check-contexts) -* [Get access restrictions](/v3/repos/branches/#get-access-restrictions) -* [Delete access restrictions](/v3/repos/branches/#delete-access-restrictions) -* [List teams with access to the protected branch](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) -* [Add team access restrictions](/v3/repos/branches/#add-team-access-restrictions) -* [Set team access restrictions](/v3/repos/branches/#set-team-access-restrictions) -* [Remove team access restriction](/v3/repos/branches/#remove-team-access-restrictions) -* [List user restrictions of protected branch](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) -* [Add user access restrictions](/v3/repos/branches/#add-user-access-restrictions) -* [Set user access restrictions](/v3/repos/branches/#set-user-access-restrictions) -* [Remove user access restrictions](/v3/repos/branches/#remove-user-access-restrictions) -* [Merge a branch](/v3/repos/merging/#merge-a-branch) +* [List branches](/rest/reference/repos#list-branches) +* [Get a branch](/rest/reference/repos#get-a-branch) +* [Get branch protection](/rest/reference/repos#get-branch-protection) +* [Update branch protection](/rest/reference/repos#update-branch-protection) +* [Delete branch protection](/rest/reference/repos#delete-branch-protection) +* [Get admin branch protection](/rest/reference/repos#get-admin-branch-protection) +* [Set admin branch protection](/rest/reference/repos#set-admin-branch-protection) +* [Delete admin branch protection](/rest/reference/repos#delete-admin-branch-protection) +* [Get pull request review protection](/rest/reference/repos#get-pull-request-review-protection) +* [Update pull request review protection](/rest/reference/repos#update-pull-request-review-protection) +* [Delete pull request review protection](/rest/reference/repos#delete-pull-request-review-protection) +* [Get commit signature protection](/rest/reference/repos#get-commit-signature-protection) +* [Create commit signature protection](/rest/reference/repos#create-commit-signature-protection) +* [Delete commit signature protection](/rest/reference/repos#delete-commit-signature-protection) +* [Get status checks protection](/rest/reference/repos#get-status-checks-protection) +* [Update status check protection](/rest/reference/repos#update-status-check-protection) +* [Remove status check protection](/rest/reference/repos#remove-status-check-protection) +* [Get all status check contexts](/rest/reference/repos#get-all-status-check-contexts) +* [Add status check contexts](/rest/reference/repos#add-status-check-contexts) +* [Set status check contexts](/rest/reference/repos#set-status-check-contexts) +* [Remove status check contexts](/rest/reference/repos#remove-status-check-contexts) +* [Get access restrictions](/rest/reference/repos#get-access-restrictions) +* [Delete access restrictions](/rest/reference/repos#delete-access-restrictions) +* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [Add team access restrictions](/rest/reference/repos#add-team-access-restrictions) +* [Set team access restrictions](/rest/reference/repos#set-team-access-restrictions) +* [Remove team access restriction](/rest/reference/repos#remove-team-access-restrictions) +* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [Add user access restrictions](/rest/reference/repos#add-user-access-restrictions) +* [Set user access restrictions](/rest/reference/repos#set-user-access-restrictions) +* [Remove user access restrictions](/rest/reference/repos#remove-user-access-restrictions) +* [Merge a branch](/rest/reference/repos#merge-a-branch) ##### Repository Collaborators -* [List repository collaborators](/v3/repos/collaborators/#list-repository-collaborators) -* [Check if a user is a repository collaborator](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) -* [Add a repository collaborator](/v3/repos/collaborators/#add-a-repository-collaborator) -* [Remove a repository collaborator](/v3/repos/collaborators/#remove-a-repository-collaborator) -* [Get repository permissions for a user](/v3/repos/collaborators/#get-repository-permissions-for-a-user) +* [List repository collaborators](/rest/reference/repos#list-repository-collaborators) +* [Check if a user is a repository collaborator](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator) +* [Remove a repository collaborator](/rest/reference/repos#remove-a-repository-collaborator) +* [Get repository permissions for a user](/rest/reference/repos#get-repository-permissions-for-a-user) ##### Repository Commit Comments -* [List commit comments for a repository](/v3/repos/comments/#list-commit-comments-for-a-repository) -* [Get a commit comment](/v3/repos/comments/#get-a-commit-comment) -* [Update a commit comment](/v3/repos/comments/#update-a-commit-comment) -* [Delete a commit comment](/v3/repos/comments/#delete-a-commit-comment) -* [List commit comments](/v3/repos/comments/#list-commit-comments) -* [Create a commit comment](/v3/repos/comments/#create-a-commit-comment) +* [List commit comments for a repository](/rest/reference/repos#list-commit-comments-for-a-repository) +* [Get a commit comment](/rest/reference/repos#get-a-commit-comment) +* [Update a commit comment](/rest/reference/repos#update-a-commit-comment) +* [Delete a commit comment](/rest/reference/repos#delete-a-commit-comment) +* [List commit comments](/rest/reference/repos#list-commit-comments) +* [Create a commit comment](/rest/reference/repos#create-a-commit-comment) ##### Repository Commits -* [List commits](/v3/repos/commits/#list-commits) -* [Get a commit](/v3/repos/commits/#get-a-commit) -* [List branches for head commit](/v3/repos/commits/#list-branches-for-head-commit) -* [List pull requests associated with commit](/v3/repos/commits/#list-pull-requests-associated-with-commit) +* [List commits](/rest/reference/repos#list-commits) +* [Get a commit](/rest/reference/repos#get-a-commit) +* [List branches for head commit](/rest/reference/repos#list-branches-for-head-commit) +* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit) ##### Repository Community -* [Get the code of conduct for a repository](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) +* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% if currentVersion == "free-pro-team@latest" %} -* [Get community profile metrics](/v3/repos/community/#get-community-profile-metrics) +* [Get community profile metrics](/rest/reference/repos#get-community-profile-metrics) {% endif %} ##### Repository Contents -* [Download a repository archive](/v3/repos/contents/#download-a-repository-archive) -* [Get repository content](/v3/repos/contents/#get-repository-content) -* [Create or update file contents](/v3/repos/contents/#create-or-update-file-contents) -* [Delete a file](/v3/repos/contents/#delete-a-file) -* [Get a repository README](/v3/repos/contents/#get-a-repository-readme) -* [Get the license for a repository](/v3/licenses/#get-the-license-for-a-repository) +* [Download a repository archive](/rest/reference/repos#download-a-repository-archive) +* [Get repository content](/rest/reference/repos#get-repository-content) +* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents) +* [Delete a file](/rest/reference/repos#delete-a-file) +* [Get a repository README](/rest/reference/repos#get-a-repository-readme) +* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ##### Repository Event Dispatches -* [Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event) +* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event) {% endif %} ##### Repository Hooks -* [List repository webhooks](/v3/repos/hooks/#list-repository-webhooks) -* [Create a repository webhook](/v3/repos/hooks/#create-a-repository-webhook) -* [Get a repository webhook](/v3/repos/hooks/#get-a-repository-webhook) -* [Update a repository webhook](/v3/repos/hooks/#update-a-repository-webhook) -* [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) -* [Ping a repository webhook](/v3/repos/hooks/#ping-a-repository-webhook) -* [Test the push repository webhook](/v3/repos/hooks/#test-the-push-repository-webhook) +* [List repository webhooks](/rest/reference/repos#list-repository-webhooks) +* [Create a repository webhook](/rest/reference/repos#create-a-repository-webhook) +* [Get a repository webhook](/rest/reference/repos#get-a-repository-webhook) +* [Update a repository webhook](/rest/reference/repos#update-a-repository-webhook) +* [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) +* [Ping a repository webhook](/rest/reference/repos#ping-a-repository-webhook) +* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook) ##### Repository Invitations -* [List repository invitations](/v3/repos/invitations/#list-repository-invitations) -* [Update a repository invitation](/v3/repos/invitations/#update-a-repository-invitation) -* [Delete a repository invitation](/v3/repos/invitations/#delete-a-repository-invitation) -* [List repository invitations for the authenticated user](/v3/repos/invitations/#list-repository-invitations-for-the-authenticated-user) -* [Accept a repository invitation](/v3/repos/invitations/#accept-a-repository-invitation) -* [Decline a repository invitation](/v3/repos/invitations/#decline-a-repository-invitation) +* [List repository invitations](/rest/reference/repos#list-repository-invitations) +* [Update a repository invitation](/rest/reference/repos#update-a-repository-invitation) +* [Delete a repository invitation](/rest/reference/repos#delete-a-repository-invitation) +* [List repository invitations for the authenticated user](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [Accept a repository invitation](/rest/reference/repos#accept-a-repository-invitation) +* [Decline a repository invitation](/rest/reference/repos#decline-a-repository-invitation) ##### Repository Keys -* [List deploy keys](/v3/repos/keys/#list-deploy-keys) -* [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) -* [Get a deploy key](/v3/repos/keys/#get-a-deploy-key) -* [Delete a deploy key](/v3/repos/keys/#delete-a-deploy-key) +* [List deploy keys](/rest/reference/repos#list-deploy-keys) +* [Create a deploy key](/rest/reference/repos#create-a-deploy-key) +* [Get a deploy key](/rest/reference/repos#get-a-deploy-key) +* [Delete a deploy key](/rest/reference/repos#delete-a-deploy-key) ##### Repository Pages @@ -790,144 +790,144 @@ While most of your API interaction should occur using your server-to-server inst ##### Repository Stats -* [Get the weekly commit activity](/v3/repos/statistics/#get-the-weekly-commit-activity) -* [Get the last year of commit activity](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -* [Get all contributor commit activity](/v3/repos/statistics/#get-all-contributor-commit-activity) -* [Get the weekly commit count](/v3/repos/statistics/#get-the-weekly-commit-count) -* [Get the hourly commit count for each day](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +* [Get the weekly commit activity](/rest/reference/repos#get-the-weekly-commit-activity) +* [Get the last year of commit activity](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [Get all contributor commit activity](/rest/reference/repos#get-all-contributor-commit-activity) +* [Get the weekly commit count](/rest/reference/repos#get-the-weekly-commit-count) +* [Get the hourly commit count for each day](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) {% if currentVersion == "free-pro-team@latest" %} ##### Repository Vulnerability Alerts -* [Enable vulnerability alerts](/v3/repos/#enable-vulnerability-alerts) -* [Disable vulnerability alerts](/v3/repos/#disable-vulnerability-alerts) +* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts) +* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts) {% endif %} ##### Root -* [Root endpoint](/v3/#root-endpoint) -* [Emojis](/v3/emojis/#emojis) -* [Get rate limit status for the authenticated user](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) +* [Root endpoint](/rest#root-endpoint) +* [Emojis](/rest/reference/emojis#emojis) +* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) ##### Поиск -* [Search code](/v3/search/#search-code) -* [Search commits](/v3/search/#search-commits) -* [Search labels](/v3/search/#search-labels) -* [Search repositories](/v3/search/#search-repositories) -* [Search topics](/v3/search/#search-topics) -* [Search users](/v3/search/#search-users) +* [Search code](/rest/reference/search#search-code) +* [Search commits](/rest/reference/search#search-commits) +* [Search labels](/rest/reference/search#search-labels) +* [Search repositories](/rest/reference/search#search-repositories) +* [Search topics](/rest/reference/search#search-topics) +* [Search users](/rest/reference/search#search-users) ##### Statuses -* [Get the combined status for a specific reference](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) -* [List commit statuses for a reference](/v3/repos/statuses/#list-commit-statuses-for-a-reference) -* [Create a commit status](/v3/repos/statuses/#create-a-commit-status) +* [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [List commit statuses for a reference](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [Create a commit status](/rest/reference/repos#create-a-commit-status) ##### Team Discussions -* [List discussions](/v3/teams/discussions/#list-discussions) -* [Create a discussion](/v3/teams/discussions/#create-a-discussion) -* [Get a discussion](/v3/teams/discussions/#get-a-discussion) -* [Update a discussion](/v3/teams/discussions/#update-a-discussion) -* [Delete a discussion](/v3/teams/discussions/#delete-a-discussion) -* [List discussion comments](/v3/teams/discussion_comments/#list-discussion-comments) -* [Create a discussion comment](/v3/teams/discussion_comments/#create-a-discussion-comment) -* [Get a discussion comment](/v3/teams/discussion_comments/#get-a-discussion-comment) -* [Update a discussion comment](/v3/teams/discussion_comments/#update-a-discussion-comment) -* [Delete a discussion comment](/v3/teams/discussion_comments/#delete-a-discussion-comment) +* [List discussions](/rest/reference/teams#list-discussions) +* [Create a discussion](/rest/reference/teams#create-a-discussion) +* [Get a discussion](/rest/reference/teams#get-a-discussion) +* [Update a discussion](/rest/reference/teams#update-a-discussion) +* [Delete a discussion](/rest/reference/teams#delete-a-discussion) +* [List discussion comments](/rest/reference/teams#list-discussion-comments) +* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment) +* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment) +* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment) +* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment) ##### Topics -* [Get all repository topics](/v3/repos#get-all-repository-topics) -* [Replace all repository topics](/v3/repos/#replace-all-repository-topics) +* [Get all repository topics](/rest/reference/repos#get-all-repository-topics) +* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics) {% if currentVersion == "free-pro-team@latest" %} ##### Traffic -* [Get repository clones](/v3/repos/traffic/#get-repository-clones) -* [Get top referral paths](/v3/repos/traffic/#get-top-referral-paths) -* [Get top referral sources](/v3/repos/traffic/#get-top-referral-sources) -* [Get page views](/v3/repos/traffic/#get-page-views) +* [Get repository clones](/rest/reference/repos#get-repository-clones) +* [Get top referral paths](/rest/reference/repos#get-top-referral-paths) +* [Get top referral sources](/rest/reference/repos#get-top-referral-sources) +* [Get page views](/rest/reference/repos#get-page-views) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### User Blocking -* [List users blocked by the authenticated user](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) -* [Check if a user is blocked by the authenticated user](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) -* [List users blocked by an organization](/v3/orgs/blocking/#list-users-blocked-by-an-organization) -* [Check if a user is blocked by an organization](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) -* [Block a user from an organization](/v3/orgs/blocking/#block-a-user-from-an-organization) -* [Unblock a user from an organization](/v3/orgs/blocking/#unblock-a-user-from-an-organization) -* [Block a user](/v3/users/blocking/#block-a-user) -* [Unblock a user](/v3/users/blocking/#unblock-a-user) +* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization) +* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [Block a user](/rest/reference/users#block-a-user) +* [Unblock a user](/rest/reference/users#unblock-a-user) {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ##### User Emails {% if currentVersion == "free-pro-team@latest" %} -* [Set primary email visibility for the authenticated user](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) +* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %} -* [List email addresses for the authenticated user](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) -* [Add email address(es)](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) -* [Delete email address(es)](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) -* [List public email addresses for the authenticated user](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) +* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) {% endif %} ##### User Followers -* [List followers of a user](/v3/users/followers/#list-followers-of-a-user) -* [List the people a user follows](/v3/users/followers/#list-the-people-a-user-follows) -* [Check if a person is followed by the authenticated user](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) -* [Follow a user](/v3/users/followers/#follow-a-user) -* [Unfollow a user](/v3/users/followers/#unfollow-a-user) -* [Check if a user follows another user](/v3/users/followers/#check-if-a-user-follows-another-user) +* [List followers of a user](/rest/reference/users#list-followers-of-a-user) +* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows) +* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [Follow a user](/rest/reference/users#follow-a-user) +* [Unfollow a user](/rest/reference/users#unfollow-a-user) +* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user) ##### User Gpg Keys -* [List GPG keys for the authenticated user](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) -* [Create a GPG key for the authenticated user](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) -* [Get a GPG key for the authenticated user](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) -* [Delete a GPG key for the authenticated user](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) -* [List gpg keys for a user](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) +* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user) ##### User Public Keys -* [List public SSH keys for the authenticated user](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) -* [Create a public SSH key for the authenticated user](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) -* [Get a public SSH key for the authenticated user](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) -* [Delete a public SSH key for the authenticated user](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) -* [List public keys for a user](/v3/users/keys/#list-public-keys-for-a-user) +* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user) ##### Users -* [Get the authenticated user](/v3/users/#get-the-authenticated-user) -* [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) +* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) +* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% endif %} -* [List users](/v3/users/#list-users) -* [Get a user](/v3/users/#get-a-user) +* [List users](/rest/reference/users#list-users) +* [Get a user](/rest/reference/users#get-a-user) {% if currentVersion == "free-pro-team@latest" %} ##### Workflow Runs -* [List workflow runs for a repository](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) -* [Get a workflow run](/v3/actions/workflow-runs/#get-a-workflow-run) -* [Cancel a workflow run](/v3/actions/workflow-runs/#cancel-a-workflow-run) -* [Download workflow run logs](/v3/actions/workflow-runs/#download-workflow-run-logs) -* [Delete workflow run logs](/v3/actions/workflow-runs/#delete-workflow-run-logs) -* [Re run a workflow](/v3/actions/workflow-runs/#re-run-a-workflow) -* [List workflow runs](/v3/actions/workflow-runs/#list-workflow-runs) -* [Get workflow run usage](/v3/actions/workflow-runs/#get-workflow-run-usage) +* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [Get a workflow run](/rest/reference/actions#get-a-workflow-run) +* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run) +* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs) +* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs) +* [Re run a workflow](/rest/reference/actions#re-run-a-workflow) +* [List workflow runs](/rest/reference/actions#list-workflow-runs) +* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### Workflows -* [List repository workflows](/v3/actions/workflows/#list-repository-workflows) -* [Get a workflow](/v3/actions/workflows/#get-a-workflow) -* [Get workflow usage](/v3/actions/workflows/#get-workflow-usage) +* [List repository workflows](/rest/reference/actions#list-repository-workflows) +* [Get a workflow](/rest/reference/actions#get-a-workflow) +* [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} diff --git a/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 596cfc341c..b0236b40ae 100644 --- a/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -23,7 +23,7 @@ This article provides guidelines for existing integrators who are considering mi - Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). - Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration. - Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation. -- Open Source community support is available through [Octokit libraries](/v3/libraries/) and other frameworks such as [Probot](https://probot.github.io/). +- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/). - Integrators building GitHub Apps have opportunities to adopt earlier access to APIs. ### Converting an OAuth App to a GitHub App @@ -42,13 +42,13 @@ These guidelines assume that you have a registered OAuth App{% if currentVersion #### Review the available API endpoints for GitHub Apps -While the majority of [REST API](/v3) endpoints and [GraphQL](/v4) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/v3/apps/available-endpoints/) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. +While the majority of [REST API](/rest) endpoints and [GraphQL](/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_app %}s. #### Design to stay within API rate limits -GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/v3/#conditional-requests) or consolidate requests by using the [GraphQL API V4](/v4/). +GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest#conditional-requests) or consolidate requests by using the [GraphQL API V4](/graphql). #### Register a new GitHub App @@ -56,7 +56,7 @@ Once you've decided to make the switch to Github Apps, you'll need to [create a #### Determine the permissions your app requires -When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/v3/apps/permissions/)" for a list of the permissions needed for each endpoint available to GitHub Apps. +When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps. In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality. @@ -90,11 +90,11 @@ Once you've made the transition from an OAuth App to a GitHub App, you will need https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) and [List organization repositories](/v3/repos/#list-organization-repositories) endpoints. +You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints. #### Remove any unnecessary repository hooks -Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) on those repositories that were created by your OAuth App. +Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) on those repositories that were created by your OAuth App. #### Encourage users to revoke access to your OAuth app diff --git a/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md index 86db4a6770..b764ccce1e 100644 --- a/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -25,7 +25,7 @@ To renew an expiring user-to-server access token, you can exchange the `refresh_ `POST https://github.com/login/oauth/access_token` -This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/v3/guides/basics-of-authentication/#providing-a-callback)." +This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." #### Parameters diff --git a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md index a8a5eb946a..c2d1e6230d 100644 --- a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md @@ -41,13 +41,13 @@ X-Accepted-OAuth-Scopes: user | Name | Description | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/v3/enterprise-admin).{% endif %} +| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} | **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/v3/repos/deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/v3/code-scanning).{% endif %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | |  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | diff --git a/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md b/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md index f63d641cdb..c7b9470177 100644 --- a/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md +++ b/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md @@ -17,4 +17,4 @@ When you create a GitHub App, you can select the permissions it needs to access By default, GitHub Apps have `Read-only` access to metadata endpoints. Metadata is a collection of read-only endpoints that provide general information about resources that the authorized installation can access. -{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/v3/apps/permissions/#metadata-permissions)." +{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/rest/reference/permissions-required-for-github-apps#metadata-permissions)." diff --git a/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index 252aae4ecd..631fe6f7e7 100644 --- a/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -37,7 +37,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [Webhooks](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -220,7 +220,7 @@ end #### Define a route handler -An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You'll won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. ``` ruby post '/event_handler' do diff --git a/translations/ru-RU/content/developers/apps/using-content-attachments.md b/translations/ru-RU/content/developers/apps/using-content-attachments.md index 7655844b1b..c78b7725e9 100644 --- a/translations/ru-RU/content/developers/apps/using-content-attachments.md +++ b/translations/ru-RU/content/developers/apps/using-content-attachments.md @@ -55,7 +55,7 @@ The content attachment flow shows you the relationship between the URL in the is } ``` -**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/v3/apps/installations/#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -116,7 +116,7 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -For more information on `node_id`, see "[Using Global Node IDs](/v4/guides/using-global-node-ids/)." +For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ### Example using Probot and GitHub App Manifests diff --git a/translations/ru-RU/content/developers/apps/using-the-github-api-in-your-app.md b/translations/ru-RU/content/developers/apps/using-the-github-api-in-your-app.md index fab5a5610a..359b697c14 100644 --- a/translations/ru-RU/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/ru-RU/content/developers/apps/using-the-github-api-in-your-app.md @@ -31,7 +31,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub Apps](/apps/about-apps) * [Webhooks](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -143,11 +143,11 @@ Before the label can be _added_ anywhere, you'll need to _create_ the custom lab {% tip %} -**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/v3/issues/labels/#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. +**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. {% endtip %} -Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/v3/issues/labels/#add-labels-to-an-issue). +Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue). ### Step 4. Add label handling diff --git a/translations/ru-RU/content/developers/github-marketplace/billing-customers.md b/translations/ru-RU/content/developers/github-marketplace/billing-customers.md index 04aa5ff0dc..fdea7d49a4 100644 --- a/translations/ru-RU/content/developers/github-marketplace/billing-customers.md +++ b/translations/ru-RU/content/developers/github-marketplace/billing-customers.md @@ -25,7 +25,7 @@ Customers must be able to perform the following actions from your app's website: Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." -You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). +You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). #### Улучшения diff --git a/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index e44d60d15e..eda04f7c45 100644 --- a/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -68,7 +68,7 @@ After the customer completes the authorization, your app receives an OAuth acces ### Step 4. Provisioning customer accounts -Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. +Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. {% data reusables.marketplace.marketplace-double-purchases %} @@ -76,6 +76,6 @@ If the purchase is for an organization and per-user, you can prompt the customer You can customize the way that organization members receive access to your app. Here are a few suggestions: -**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/v3/orgs/members/#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. +**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/rest/reference/orgs#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. **Per-unit pricing:** One method of provisioning per-unit seats is to allow users to occupy a seat as they log in to the app. Once the customer hits the seat count threshold, your app can alert the user that they need to upgrade through {% data variables.product.prodname_marketplace %}. diff --git a/translations/ru-RU/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/ru-RU/content/developers/github-marketplace/handling-plan-cancellations.md index 17cd1d8b80..ed287efb5e 100644 --- a/translations/ru-RU/content/developers/github-marketplace/handling-plan-cancellations.md +++ b/translations/ru-RU/content/developers/github-marketplace/handling-plan-cancellations.md @@ -28,6 +28,6 @@ When a customer cancels a free or paid plan, your app must perform these steps t {% note %} -**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." {% endnote %} diff --git a/translations/ru-RU/content/developers/github-marketplace/handling-plan-changes.md b/translations/ru-RU/content/developers/github-marketplace/handling-plan-changes.md index 98758c327a..7fb64dd96c 100644 --- a/translations/ru-RU/content/developers/github-marketplace/handling-plan-changes.md +++ b/translations/ru-RU/content/developers/github-marketplace/handling-plan-changes.md @@ -54,7 +54,7 @@ https://www.github.com/marketplace//upgrade// For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page. -Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/v3/apps/marketplace/#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. +Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. {% note %} diff --git a/translations/ru-RU/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md b/translations/ru-RU/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md index 5ad1d2f177..db3482b992 100644 --- a/translations/ru-RU/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md +++ b/translations/ru-RU/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md @@ -13,10 +13,10 @@ versions: Here are some useful endpoints available for Marketplace listings: -* [List plans](/v3/apps/marketplace/#list-plans) -* [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan) -* [Get a subscription plan for an account](/v3/apps/marketplace/#get-a-subscription-plan-for-an-account) -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [List plans](/rest/reference/apps#list-plans) +* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan) +* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API: @@ -25,6 +25,6 @@ See these pages for details on how to authenticate when using the {% data variab {% note %} -**Note:** [Rate limits for the REST API](/v3/#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. +**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. {% endnote %} diff --git a/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md b/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md index 352aaf9c5e..09e79b1a7a 100644 --- a/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md +++ b/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md @@ -37,7 +37,7 @@ Your testing scenarios may require setting up listing plans that offer free tria ### Testing APIs -For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/v3/apps/marketplace/#github-marketplace). +For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace). ### Testing webhooks diff --git a/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 7044feab2b..c507787cdb 100644 --- a/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -31,15 +31,15 @@ Each `marketplace_purchase` webhook payload will have the following information: The `marketplace_purchase` object has the following keys: -| Клавиша | Тип | Description | -| -------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `учетная запись` | `объект` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/v3/users/#get-the-authenticated-user) endpoint. | -| `billing_cycle` | `строка` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. | -| `unit_count` | `integer` | Number of units purchased. | -| `on_free_trial` | `boolean` | `true` when the `account` is on a free trial. | -| `free_trial_ends_on` | `строка` | The date the free trial will expire. | -| `next_billing_date` | `строка` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. | -| `plan` | `объект` | The plan purchased by the `user` or `organization`. | +| Клавиша | Тип | Description | +| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `учетная запись` | `объект` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint. | +| `billing_cycle` | `строка` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. | +| `unit_count` | `integer` | Number of units purchased. | +| `on_free_trial` | `boolean` | `true` when the `account` is on a free trial. | +| `free_trial_ends_on` | `строка` | The date the free trial will expire. | +| `next_billing_date` | `строка` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. | +| `plan` | `объект` | The plan purchased by the `user` or `organization`. | The `plan` object has the following keys: diff --git a/translations/ru-RU/content/developers/overview/about-githubs-apis.md b/translations/ru-RU/content/developers/overview/about-githubs-apis.md index 39e74b19f1..0d647b78cb 100644 --- a/translations/ru-RU/content/developers/overview/about-githubs-apis.md +++ b/translations/ru-RU/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/v3/) and the [GraphQL API](/v4/). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). -When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). +When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). -For information on using the GraphQL API, see the [v4 docs](/v4/). +For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/ru-RU/content/developers/webhooks-and-events/about-webhooks.md b/translations/ru-RU/content/developers/webhooks-and-events/about-webhooks.md index 6d81dc54ea..6090d532c8 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/about-webhooks.md @@ -31,4 +31,4 @@ See "[Webhook event payloads](/webhooks/event-payloads)" for the list of availab For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. [org-hooks]: /rest/reference/orgs#webhooks/ -[repo-hooks]: /v3/repos/hooks/ +[repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/ru-RU/content/developers/webhooks-and-events/creating-webhooks.md b/translations/ru-RU/content/developers/webhooks-and-events/creating-webhooks.md index 3e3f958278..4ea76f0b85 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/creating-webhooks.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/creating-webhooks.md @@ -65,5 +65,5 @@ When you're finished, click **Add webhook**. Phew! Now that you created the webh To configure a webhook for all events, use the wildcard (`*`) character to specify the webhook events. When you add the wildcard event, we'll replace any existing events you have configured with the wildcard event and send you payloads for all supported events. You'll also automatically get any new events we might add in the future. [webhooks-overview]: /webhooks/ -[webhook-api]: /v3/repos/hooks/ +[webhook-api]: /rest/reference/repos#hooks [hooks-api]: /webhooks/#events diff --git a/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md b/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md index 3a16411de9..97bad95979 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md @@ -40,7 +40,7 @@ The event objects returned from the Events API endpoints have the same structure #### Example WatchEvent event object -This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/v3/activity/events). +This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events). ``` Status: 200 OK @@ -198,22 +198,22 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -| Клавиша | Тип | Description | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `push_id` | `integer` | Unique identifier for the push. | -| `size` | `integer` | The number of commits in the push. | -| `distinct_size` | `integer` | The number of distinct commits in the push. | -| `ref` | `строка` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/master`. | -| `заголовок` | `строка` | The SHA of the most recent commit on `ref` after the push. | -| `before` | `строка` | The SHA of the most recent commit on `ref` before the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][sha]` | `строка` | The SHA of the commit. | -| `commits[][message]` | `строка` | The commit message. | -| `commits[][author]` | `объект` | The git author of the commit. | -| `commits[][author][name]` | `строка` | The git author's name. | -| `commits[][author][email]` | `строка` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| Клавиша | Тип | Description | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `push_id` | `integer` | Unique identifier for the push. | +| `size` | `integer` | The number of commits in the push. | +| `distinct_size` | `integer` | The number of distinct commits in the push. | +| `ref` | `строка` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/master`. | +| `заголовок` | `строка` | The SHA of the most recent commit on `ref` after the push. | +| `before` | `строка` | The SHA of the most recent commit on `ref` before the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][sha]` | `строка` | The SHA of the commit. | +| `commits[][message]` | `строка` | The commit message. | +| `commits[][author]` | `объект` | The git author of the commit. | +| `commits[][author][name]` | `строка` | The git author's name. | +| `commits[][author][email]` | `строка` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | ### ReleaseEvent diff --git a/translations/ru-RU/content/developers/webhooks-and-events/issue-event-types.md b/translations/ru-RU/content/developers/webhooks-and-events/issue-event-types.md index b4041813b7..16c6a75b21 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/issue-event-types.md @@ -10,7 +10,7 @@ versions: --- -Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/v3/issues/events) and the [Timeline Events API](/v3/issues/timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. +Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. @@ -129,7 +129,7 @@ A comment was added to the issue or pull request. | `html_url` | `строка` | The HTML URL of the issue comment. | | `issue_url` | `строка` | The HTML URL of the issue. | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `строка` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `строка` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `пользователь` | `объект` | The person who commented on the issue. | | `created_at` | `строка` | The timestamp indicating when the comment was added. | | `updated_at` | `строка` | The timestamp indicating when the comment was updated or created, if the comment is never updated. | @@ -152,19 +152,19 @@ A commit was added to the pull request's `HEAD` branch. {% data reusables.issue-events.timeline_events_object_properties %} -| Name | Тип | Description | -| ------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `sha` | `строка` | The SHA of the commit in the pull request. | -| `node_id` | `строка` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `строка` | The REST API URL to retrieve the commit. | -| `html_url` | `строка` | The HTML URL of the commit. | -| `автор` | `объект` | The person who authored the commit. | -| `участник` | `объект` | The person who committed the commit on behalf of the author. | -| `дерево` | `объект` | The Git tree of the commit. | -| `message` | `строка` | The commit message. | -| `parents` | `array of objects` | A list of parent commits. | -| `verfication` | `объект` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/v3/git/commits/#signature-verification-object)." | -| `событие` | `строка` | The event value is `"committed"`. | +| Name | Тип | Description | +| ------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sha` | `строка` | The SHA of the commit in the pull request. | +| `node_id` | `строка` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `строка` | The REST API URL to retrieve the commit. | +| `html_url` | `строка` | The HTML URL of the commit. | +| `автор` | `объект` | The person who authored the commit. | +| `участник` | `объект` | The person who committed the commit on behalf of the author. | +| `дерево` | `объект` | The Git tree of the commit. | +| `message` | `строка` | The commit message. | +| `parents` | `array of objects` | A list of parent commits. | +| `verfication` | `объект` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#signature-verification-object)." | +| `событие` | `строка` | The event value is `"committed"`. | ### connected @@ -583,7 +583,7 @@ The pull request was reviewed. | Name | Тип | Description | | -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `integer` | The unique identifier of the event. | -| `node_id` | `строка` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `строка` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `пользователь` | `объект` | The person who commented on the issue. | | `тело` | `строка` | The review summary text. | | `commit_id` | `строка` | The SHA of the latest commit in the pull request at the time of the review. | diff --git a/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md index 8eb8622fc2..25924a8d36 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -33,7 +33,7 @@ Each webhook event payload also contains properties unique to the event. You can {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)." -The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/v3/activity/events/). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. +The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. {% tip %} @@ -45,14 +45,14 @@ The unique properties for a webhook event are the same properties you'll find in HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: -| Header | Description | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | Name of the event that triggered the delivery. | +| Header | Description | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-GitHub-Event` | Name of the event that triggered the delivery. | | `X-GitHub-Delivery` | A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | +| `X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. | | `X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} -| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} +| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. @@ -195,7 +195,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.content_reference_short_desc %} -Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" to create a new content attachment. +Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event. @@ -715,7 +715,7 @@ The webhook this event is configured on was deleted. This event will only listen ### пакет -Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. +Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. #### Availability @@ -775,7 +775,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus | -------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `zen` | `строка` | Random string of GitHub zen. | | `hook_id` | `integer` | The ID of the webhook that triggered the ping. | -| `перехватчик` | `объект` | The [webhook configuration](/v3/repos/hooks/#get-a-repository-webhook). | +| `перехватчик` | `объект` | The [webhook configuration](/rest/reference/repos#get-a-repository-webhook). | | `hook[app_id]` | `integer` | When you register a new {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} sends a ping event to the **webhook URL** you specified during registration. The event contains the `app_id`, which is required for [authenticating](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) an app. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} @@ -969,24 +969,24 @@ Deliveries for `review_requested` and `review_request_removed` events will have #### Webhook payload object -| Клавиша | Тип | Description | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `строка` | The full [`git ref`](/v3/git/refs/) that was pushed. Example: `refs/heads/master`. | -| `before` | `строка` | The SHA of the most recent commit on `ref` before the push. | -| `after` | `строка` | The SHA of the most recent commit on `ref` after the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/v3/repos/commits/) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `строка` | The SHA of the commit. | -| `commits[][timestamp]` | `строка` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `строка` | The commit message. | -| `commits[][author]` | `объект` | The git author of the commit. | -| `commits[][author][name]` | `строка` | The git author's name. | -| `commits[][author][email]` | `строка` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | -| `commits[][added]` | `array` | An array of files added in the commit. | -| `commits[][modified]` | `array` | An array of files modified by the commit. | -| `commits[][removed]` | `array` | An array of files removed in the commit. | -| `pusher` | `объект` | The user who pushed the commits. | +| Клавиша | Тип | Description | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ref` | `строка` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/master`. | +| `before` | `строка` | The SHA of the most recent commit on `ref` before the push. | +| `after` | `строка` | The SHA of the most recent commit on `ref` after the push. | +| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | +| `commits[][id]` | `строка` | The SHA of the commit. | +| `commits[][timestamp]` | `строка` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `строка` | The commit message. | +| `commits[][author]` | `объект` | The git author of the commit. | +| `commits[][author][name]` | `строка` | The git author's name. | +| `commits[][author][email]` | `строка` | The git author's email address. | +| `commits[][url]` | `url` | URL that points to the commit API resource. | +| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| `commits[][added]` | `array` | An array of files added in the commit. | +| `commits[][modified]` | `array` | An array of files modified by the commit. | +| `commits[][removed]` | `array` | An array of files removed in the commit. | +| `pusher` | `объект` | The user who pushed the commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1022,7 +1022,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### repository_dispatch -This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event)" endpoint. +This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. #### Availability @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | Клавиша | Тип | Description | | ---------- | -------- | --------------------------------------------------------------------------- | -| `действие` | `строка` | The action that was performed. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/v3/orgs/hooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/v3/previews/#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| +| `действие` | `строка` | The action that was performed. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/v3/orgs/hooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1060,7 +1060,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% if currentVersion == "free-pro-team@latest"%} ### repository_import -{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/v3/migrations/source_imports/). +{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports). #### Availability @@ -1237,9 +1237,9 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ #### Webhook payload object -| Клавиша | Тип | Description | -| --------- | -------- | ------------------------------------------------------------------------------------------------------ | -| `команда` | `объект` | The [team](/v3/teams/) that was modified. **Note:** Older events may not include this in the payload. | +| Клавиша | Тип | Description | +| --------- | -------- | ----------------------------------------------------------------------------------------------------------------- | +| `команда` | `объект` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1268,7 +1268,7 @@ When a user is `created` or `deleted`. {% data reusables.webhooks.watch_short_desc %} -The event’s actor is the [user](/v3/users/) who starred a repository, and the event’s repository is the [repository](/v3/repos/) that was starred. +The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. #### Availability diff --git a/translations/ru-RU/content/github/administering-a-repository/about-releases.md b/translations/ru-RU/content/github/administering-a-repository/about-releases.md index 65fd50ecbb..194786ffab 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-releases.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-releases.md @@ -37,7 +37,7 @@ If a release fixes a security vulnerability, you should publish a security advis You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/v3/repos/releases/)." +You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)." {% if currentVersion == "free-pro-team@latest" %} ### Storage and bandwidth quotas diff --git a/translations/ru-RU/content/github/administering-a-repository/about-required-status-checks.md b/translations/ru-RU/content/github/administering-a-repository/about-required-status-checks.md index 747dd9aeaa..e1ccb74a91 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-required-status-checks.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-required-status-checks.md @@ -36,7 +36,7 @@ You can set up either loose or strict status checks, depending on whether you wa ### Troubleshooting required status checks -If you have a check and a status with the same name and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/v3/checks/)." +If you have a check and a status with the same name and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)." Once you've set up required status checks, your branch must be up to date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. @@ -62,7 +62,7 @@ remote: error: Required status check "ci-build" is failing {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, it must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pull Requests](/v3/pulls/#response-1)." +Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, it must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pull Requests](/rest/reference/pulls#response-1)." ![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md index 9138de4245..726a264da3 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,12 +15,15 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} + ### About release management +{% if currentVersion == "free-pro-team@latest" %} You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "Publishing an action in the {% data variables.product.prodname_marketplace %}." - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% endif %} You can choose whether + {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/ru-RU/content/github/authenticating-to-github/about-githubs-ip-addresses.md index 1292984f10..5fb446ceee 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/about-githubs-ip-addresses.md +++ b/translations/ru-RU/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -12,7 +12,7 @@ versions: free-pro-team: '*' --- -You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/v3/meta/)." +You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)." These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges. diff --git a/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md index eea87b7430..19881f47e7 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -12,7 +12,7 @@ versions: github-ae: '*' --- -Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/v3/auth/#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). +Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). {% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %} diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md index 7acf9caa10..4723d04971 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md @@ -29,7 +29,7 @@ There are two types of status checks on {% data variables.product.product_name % _Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_app %}s. -Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/v3/checks/)" and "[Statuses](/v3/repos/statuses/)." +Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/rest/reference/checks)" and "[Statuses](/rest/reference/repos#statuses)." ### Checks diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index a9d94c5b60..aec3db403f 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -11,7 +11,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/v3/migrations/)." +To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/rest/reference/migrations)." {% else %} You can download and back up your repositories manually: @@ -21,15 +21,15 @@ You can download and back up your repositories manually: When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your {% data variables.product.product_name %} repository to your local machine: -- [Вопросы](/v3/issues/#list-issues-for-a-repository) -- [Pull requests](/v3/pulls/#list-pull-requests) +- [Вопросы](/rest/reference/issues#list-issues-for-a-repository) +- [Pull requests](/rest/reference/pulls#list-pull-requests) - [Forks](/rest/reference/repos#list-forks) - [Комментарии](/rest/reference/issues#list-issue-comments-for-a-repository) - [Milestones](/rest/reference/issues#list-milestones) - [Labels](/rest/reference/issues#list-labels-for-a-repository) - [Watchers](/rest/reference/activity#list-watchers) - [Старгейзеры](/rest/reference/activity#list-stargazers) -- [Projects](/v3/projects/#list-repository-projects) +- [Projects](/rest/reference/projects#list-repository-projects) {% endif %} Once you have {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index be136a291c..8321b47291 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ When you search by a family license, your results will include all licenses in t ### Detecting a license -[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/v3/licenses/) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. diff --git a/translations/ru-RU/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/ru-RU/content/github/extending-github/git-automation-with-oauth-tokens.md index 477272e509..23179f918f 100644 --- a/translations/ru-RU/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/ru-RU/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -43,4 +43,4 @@ To avoid these prompts, you can use Git password caching. For information, see " ### Дополнительная литература -- "[Authorizing OAuth Apps](/v3/oauth/)" +- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)" diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index 562b914e12..cb09e6bdec 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ You can use {% data variables.product.prodname_code_scanning %} to find, triage, If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/v3/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index fc315b34d3..48d380143d 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -50,6 +50,32 @@ The default {% data variables.product.prodname_codeql_workflow %} uses the `pull For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +#### Avoiding unnecessary scans of pull requests + +You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. + +``` yaml +on: + push: + branches: [main, protected] + pull_request: + branches: [main] + paths-ignore: + - '**/*.md' + - '**/*.txt' +``` + +{% note %} + +**Замечания** + +* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." +* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. + +{% endnote %} + +For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." + #### Scanning on a schedule If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." @@ -233,13 +259,13 @@ If you only want to run custom queries, you can disable the default security que #### Specifying directories to scan -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from scans by adding a `paths-ignore` array. +For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. ``` yaml -paths: +paths: - src paths-ignore: - - node_modules + - src/node_modules - '**/*.test.js' ``` @@ -252,7 +278,7 @@ paths-ignore: {% endnote %} -For C/C++, C#, and Java, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index 0c46df8cbb..e9a1652381 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -41,7 +41,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie {% endtip %} {% endif %} -Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage worflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### Reviewing all of your subscriptions diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/index.md b/translations/ru-RU/content/github/managing-your-work-on-github/index.md index c6f2a858e0..d882a90b1d 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/index.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/index.md @@ -14,7 +14,7 @@ versions: ### Table of Contents -{% topic_link_in_list /managing-your-work-with-issues %} +{% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} @@ -27,6 +27,7 @@ versions: {% link_in_list /pinning-an-issue-to-your-repository %} {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} + {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} {% link_in_list /about-automation-for-issues-and-pull-requests-with-query-parameters %} {% link_in_list /file-attachments-on-issues-and-pull-requests %} @@ -35,12 +36,6 @@ versions: {% link_in_list /disabling-issues %} {% link_in_list /linking-a-pull-request-to-an-issue %} {% link_in_list /about-duplicate-issues-and-pull-requests %} -{% topic_link_in_list /labeling-issues-and-pull-requests %} - {% link_in_list /about-labels %} - {% link_in_list /creating-a-label %} - {% link_in_list /applying-labels-to-issues-and-pull-requests %} - {% link_in_list /editing-a-label %} - {% link_in_list /deleting-a-label %} {% topic_link_in_list /managing-project-boards %} {% link_in_list /about-project-boards %} {% link_in_list /creating-a-project-board %} diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md b/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md new file mode 100644 index 0000000000..332071d1f5 --- /dev/null +++ b/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md @@ -0,0 +1,97 @@ +--- +title: Managing labels +intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +redirect_from: + - /articles/managing-Labels + - /articles/labeling-issues-and-pull-requests + - /github/managing-your-work-on-github/labeling-issues-and-pull-requests + - /articles/about-labels + - /github/managing-your-work-on-github/about-labels + - /articles/creating-and-editing-labels-for-issues-and-pull-requests + - /articles/creating-a-label + - /github/managing-your-work-on-github/creating-a-label + - /articles/customizing-issue-labels/ + - /articles/applying-labels-to-issues-and-pull-requests + - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests + - /articles/editing-a-label + - /github/managing-your-work-on-github/editing-a-label + - /articles/deleting-a-label + - /github/managing-your-work-on-github/deleting-a-label +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### About labels + +You can manage your work on {% data variables.product.product_name %} by creating labels to categorize issues and pull requests. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. + +Anyone with read access to a repository can view and search the repository’s labels. To create, edit, apply, or delete a label, you must have write access to the repository. + +### About default labels + +{% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository. + +| Label | Description | +| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `документация` | Indicates a need for improvements or additions to documentation{% endif %} +| `duplicate` | Indicates similar issues or pull requests | +| `enhancement` | Indicates new feature requests | +| `good first issue` | Indicates a good issue for first-time contributors | +| `help wanted` | Indicates that a maintainer wants help on an issue or pull request | +| `invalid` | Indicates that an issue or pull request is no longer relevant | +| `question` | Indicates that an issue or pull request needs more information | +| `wontfix` | Indicates that work won't continue on an issue or pull request | + +Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +Organization owners can customize the default labels for repositories in their organization. For more information, see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)." +{% endif %} + +### Creating a label + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. To the right of the search field, click **New label**. +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### Applying labels to issues and pull requests + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. In the upper-right corner, click **Label**, then start typing the name of an existing label. Click the label's name to associate it with the selected items. ![Issues Milestone assignment drop-down](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### Editing a label + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### Deleting a label +Deleting a label will remove the label from issues and pull requests. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.delete-label %} + +### Дополнительная литература +- "[About labels](/articles/about-labels)" +- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md new file mode 100644 index 0000000000..7627c87e95 --- /dev/null +++ b/translations/ru-RU/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Managing your work with issues and pull requests +intro: 'You can manage your work on {% data variables.product.product_name %} by creating issues to track ideas, enhancements, tasks, or bugs.' +mapTopic: true +redirect_from: + - /github/managing-your-work-on-github/managing-your-work-with-issues + - /articles/managing-your-work-with-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 8a62bcf033..0bf0c6ab43 100644 --- a/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -163,7 +163,7 @@ You can use the `project` qualifier to find issues that are associated with a sp ### Search by commit status -You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/v3/repos/statuses/) or a CI service. +You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service. | Qualifier | Пример | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index c6e806ae7e..62fde838c0 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -40,7 +40,7 @@ Some IdPs support provisioning access to a {% data variables.product.prodname_d ### Adding members to an organization using SAML SSO -After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/v3/orgs/members/#add-or-update-organization-membership)." +After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." {% data reusables.organizations.team-synchronization %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 1d82383ac3..adc17332af 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -12,7 +12,7 @@ If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-s If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. -These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/v3/scim/) in the {% data variables.product.product_name %} API documentation. +These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% data variables.product.product_name %} API documentation. - Azure AD - Okta - OneLogin diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 1476faaf20..4c9a5eed7b 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -59,6 +59,7 @@ In addition to managing organization-level settings, organization owners have ad | Edit wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} | [Report abusive or spammy content](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} | Apply labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | | Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** | | Apply milestones | | **X** | **X** | **X** | **X** | | Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 45b8372a5b..5f2377b56c 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -429,9 +429,9 @@ For more information, see "[Restricting publication of {% data variables.product | Действие | Description | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | -| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data.variables.product.prodname_dotcom %} for a draft security advisory. | -| `github_broadcast` | Triggered when {% data.variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | -| `github_withdraw` | Triggered when {% data.variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | | `open` | Triggered when someone opens a draft security advisory. | | `publish` | Triggered when someone publishes a security advisory. | | `reopen` | Triggered when someone reopens as draft security advisory. | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 9eaf964917..2b910f9530 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -23,7 +23,7 @@ Parent teams cannot synchronize with IdP groups. If the team you want to connect To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." -You can also manage team synchronization with the API. For more information, see "[Team synchronization](/v3/teams/team_sync/)." +You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)." ### Requirements for members of synchronized teams diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md index ea38298892..fab3c8a0ca 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -26,7 +26,7 @@ For more information about the differences between {% data variables.product.pro For more information about member access and management, see "{% if currentVersion == "free-pro-team@latest" %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}." -For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)." +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 8a776247ea..8bee3f1ed7 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -10,7 +10,7 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} -3. In the left sidebar, click **{% data variables.product.prodname_oauth_app %}s**. ![{ site.data.variables.product.prodname_oauth_app }}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. In the left sidebar, click **{% data variables.product.prodname_oauth_app %}s**. ![{% data variables.product.prodname_oauth_app %}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) 3. Click **Register a new application**. 4. Under **Application name**, type "Jira". 5. Under **Homepage URL**, type the full URL to your Jira instance. diff --git a/translations/ru-RU/content/github/site-policy/github-privacy-statement.md b/translations/ru-RU/content/github/site-policy/github-privacy-statement.md index 6db712401f..e94a3e5eb4 100644 --- a/translations/ru-RU/content/github/site-policy/github-privacy-statement.md +++ b/translations/ru-RU/content/github/site-policy/github-privacy-statement.md @@ -201,7 +201,7 @@ Please contact the Account owners for more information about how they might proc #### Third party applications -You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/v3/users/) to see what information is provided when you authenticate into a Developer Product using your GitHub profile. +You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile. #### Страницы GitHub diff --git a/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index d7198c1cac..b88292324e 100644 --- a/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -28,7 +28,7 @@ With respect to their personal information, California residents may exercise th California residents have the right to request from a business disclosure of the categories and specific pieces of personal information it has collected from them in the preceding 12 months, the categories of sources from which such personal information is collected, the business or commercial purpose for collecting or selling such personal information, and the categories of third parties with whom the business shares personal information. -If you request that a business disclose categories and specific pieces of personal information collected about you, you have the right to receive that information, free of charge, twice a year. The information may be delivered by mail or electronically and, if provided electronically, shall be in a portable and, to the extent technically feasible, readily usable format that allows the California resident to relatively easily transmit this information to another entity. You can use GitHub’s [User Migration API](/v3/migrations/users/) to access and download your data. Learn more [here](https://github.blog/2018-12-19-download-your-data/). +If you request that a business disclose categories and specific pieces of personal information collected about you, you have the right to receive that information, free of charge, twice a year. The information may be delivered by mail or electronically and, if provided electronically, shall be in a portable and, to the extent technically feasible, readily usable format that allows the California resident to relatively easily transmit this information to another entity. You can use GitHub’s [User Migration API](/rest/reference/migrations#users) to access and download your data. Learn more [here](https://github.blog/2018-12-19-download-your-data/). ### 2. Right to know whether your personal information is sold or disclosed for a business purpose and to whom diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index 83f2ce29f2..f11ff74a9a 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -54,8 +54,6 @@ If you live in a supported region, you can follow these instructions to submit y {% data reusables.sponsors.double-check-stripe-info %} -If you live in an unsupported region and are accepted to the beta of {% data variables.product.prodname_sponsors %}, you will receive an email with instructions to provide your bank information so that you can receive payments via ACH transfer or wire transfer. - {% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} diff --git a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md index a205866918..67d6ea0ff6 100644 --- a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md +++ b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md @@ -10,7 +10,7 @@ versions: {% data variables.product.product_name %} stores repository and profile metadata from your personal account's activity. You can export your personal account's data through settings on {% data variables.product.prodname_dotcom_the_website %} or with the User Migration API. -For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see "[Download a user migration archive](/v3/migrations/users/#download-a-user-migration-archive)" and "[About {% data variables.product.product_name %}'s use of your data](/articles/about-github-s-use-of-your-data). +For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see "[Download a user migration archive](/rest/reference/migrations#download-a-user-migration-archive)" and "[About {% data variables.product.product_name %}'s use of your data](/articles/about-github-s-use-of-your-data). When you request an export of your personal data through settings on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.product_name %} packages your personal data in a `tar.gz` file and sends you an email to your primary email address with a download link. diff --git a/translations/ru-RU/content/github/using-git/which-remote-url-should-i-use.md b/translations/ru-RU/content/github/using-git/which-remote-url-should-i-use.md index f6c233d9b0..7bc2fb657d 100644 --- a/translations/ru-RU/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/ru-RU/content/github/using-git/which-remote-url-should-i-use.md @@ -44,7 +44,7 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit {% tip %} -**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/v3/guides/using-ssh-agent-forwarding/)." +**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index bc0f615a44..d3ef7ec30a 100644 --- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -36,7 +36,7 @@ If you don't appear in a repository's contributors graph, it may be because: {% tip %} -**Tip:** To list all commit contributors in a repository, see "[Repositories](/v3/repos/#list-contributors)." +**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)." {% endtip %} diff --git a/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md b/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md index f7a60f566f..e4caf3934c 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md @@ -150,4 +150,4 @@ While you can't specify custom MIME types on a per-file or per-repository basis, ### Дополнительная литература - [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %} -- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)" +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index f3ca97d471..dc00414587 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -16,7 +16,7 @@ versions: Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} - The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} -- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/v3/guides/managing-deploy-keys/#machine-users)." +- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)." - You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safelist. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation. {% note %} diff --git a/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md b/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md index c37dffaac6..98b4fba1b5 100644 --- a/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md @@ -18,7 +18,7 @@ Follow the steps in "[Creating a personal access token](/github/authenticating-t {% if currentVersion == "free-pro-team@latest" %} -To match the behavior of the [GraphQL Explorer](/v4/guides/using-the-explorer), request the following scopes: +To match the behavior of the [GraphQL Explorer](/graphql/guides/using-the-explorer), request the following scopes: {% else %} @@ -50,9 +50,9 @@ The endpoint remains constant no matter what operation you perform. ### Communicating with GraphQL -Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/v4/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. +Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/graphql/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. -In REST, [HTTP verbs](/v3/#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/v4/guides/intro-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest)." +In REST, [HTTP verbs](/rest#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." To query GraphQL using cURL, make a `POST` request with a JSON payload. The payload must contain a string called `query`: @@ -72,15 +72,15 @@ curl -H "Authorization: bearer token" -X POST -d " \ #### About query and mutation operations -The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/v4/mutation/) determines which modification is executed. +The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/graphql/reference/mutations) determines which modification is executed. -For information about rate limiting, see "[GraphQL resource limitations](/v4/guides/resource-limitations/)." +For information about rate limiting, see "[GraphQL resource limitations](/graphql/overview/resource-limitations)." Queries and mutations share similar forms, with some important differences. #### About queries -GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/v4/guides/intro-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/v4/scalar/). +GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/graphql/guides/introduction-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/graphql/reference/scalars). Queries are structured like this: @@ -107,7 +107,7 @@ Mutations are structured like this: The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. -In the [mutations](/v4/mutation/) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. +In the [mutations](/graphql/reference/mutations) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. For a real-world example, see "[Example mutation](#example-mutation)." @@ -117,7 +117,7 @@ For a real-world example, see "[Example mutation](#example-mutation)." {% note %} -**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/v4/guides/using-the-explorer/#using-the-variable-pane), and do not include the word `variables` before the JSON object. +**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object. {% endnote %} @@ -207,7 +207,7 @@ Looking at the composition line by line: * `repository(owner:"octocat", name:"Hello-World") {` - To begin the query, we want to find a [`repository`](/v4/object/repository/) object. The schema validation indicates this object requires an `owner` and a `name` argument. + To begin the query, we want to find a [`repository`](/graphql/reference/objects#repository) object. The schema validation indicates this object requires an `owner` and a `name` argument. * `issues(last:20, states:CLOSED) {` @@ -215,9 +215,9 @@ Looking at the composition line by line: Some details about the `issues` object: - - The [docs](/v4/object/repository/) tell us this object has the type `IssueConnection`. + - The [docs](/graphql/reference/objects#repository) tell us this object has the type `IssueConnection`. - Schema validation indicates this object requires a `last` or `first` number of results as an argument, so we provide `20`. - - The [docs](/v4/object/repository/) also tell us this object accepts a `states` argument, which is an [`IssueState`](/v4/enum/issuestate/) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. + - The [docs](/graphql/reference/objects#repository) also tell us this object accepts a `states` argument, which is an [`IssueState`](/graphql/reference/enums#issuestate) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. * `edges {` @@ -225,9 +225,9 @@ Looking at the composition line by line: * `node {` - Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/v4/object/issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. + Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/graphql/reference/objects#issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. -* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/v4/object/issue) and specify the fields we want to return: +* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/graphql/reference/objects#issue) and specify the fields we want to return: ```graphql title @@ -243,7 +243,7 @@ Looking at the composition line by line: Here we specify the `title`, `url`, and `labels` fields of the `Issue` object. - The `labels` field has the type [`LabelConnection`](/v4/object/labelconnection/). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. + The `labels` field has the type [`LabelConnection`](/graphql/reference/objects#labelconnection). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. You may notice that running this query on the Octocat's public `Hello-World` repository won't return many labels. Try running it on one of your own repositories that does use labels, and you'll likely see a difference. @@ -285,7 +285,7 @@ Let's walk through the example. The task sounds simple: add an emoji reaction to So how do we know to begin with a query? We don't, yet. -Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/v4/mutation/addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! +Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/graphql/reference/mutations#addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! The docs for the mutation list three input fields: @@ -337,13 +337,13 @@ With the ID known, we can proceed with the mutation: - `addReaction` is the name of the mutation. - `input` is the required argument key. This will always be `input` for a mutation. - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/v4/input_object/) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/graphql/reference/input-objects) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. - How do we know which value to use for the content? The [`addReaction` docs](/v4/mutation/addreaction/) tell us the `content` field has the type [`ReactionContent`](/v4/enum/reactioncontent/), which is an [enum](/v4/enum) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): + How do we know which value to use for the content? The [`addReaction` docs](/graphql/reference/mutations#addreaction) tell us the `content` field has the type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an [enum](/graphql/reference/enums) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): {% data reusables.repositories.reaction_list %} -* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/v4/mutation/addreaction), which three possible return fields: +* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/graphql/reference/mutations#addreaction), which three possible return fields: - `clientMutationId` (`String`) - `reaction` (`Reaction!`) @@ -394,7 +394,7 @@ variables { {% note %} You may notice that the `content` field value in the earlier example (where it's used directly in the mutation) does not have quotes around `HOORAY`, but it does have quotes when used in the variable. There's a reason for this: -* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/v4/enum/reactioncontent/), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. +* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. * When you use `content` in a variable, the variables section must be valid JSON, so the quotes are required. Schema validation correctly interprets the `ReactionContent` type when the variable is passed into the mutation during execution. For more information on the difference between enums and strings, see the [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). diff --git a/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md b/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md index f4d05b5bee..017b674775 100644 --- a/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md +++ b/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md @@ -12,7 +12,7 @@ versions: ### GraphQL terminology -The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/v4/). +The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/graphql). ### Schema @@ -30,11 +30,11 @@ This means that if you try to return a field that is not a scalar, schema valida ### Argument -An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/v4/guides/forming-calls#about-mutations) require an input object as an argument. +An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/graphql/guides/forming-calls-with-graphql#about-mutations) require an input object as an argument. ### Implementation -A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/v4/interface). +A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/graphql/reference/interfaces). Here's a contrived example of a schema that defines interface `X` and object `Y`: @@ -55,13 +55,13 @@ This means object `Y` requires the same fields/arguments/return types that inter In the reference docs, you'll find that: -* Each [object](/v4/object) lists the interface(s) _from which it inherits_ under **Implements**. +* Each [object](/graphql/reference/objects) lists the interface(s) _from which it inherits_ under **Implements**. -* Each [interface](/v4/interface) lists the objects _that inherit from it_ under **Implementations**. +* Each [interface](/graphql/reference/interfaces) lists the objects _that inherit from it_ under **Implementations**. ### Connection -Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest)." +Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." It's helpful to picture a graph: dots connected by lines. The dots are nodes, the lines are edges. A connection defines a relationship between nodes. @@ -71,7 +71,7 @@ Edges represent connections between nodes. When you query a connection, you trav ### Node -_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/v4/scalar), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/v4/guides/using-global-node-ids)." +_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/graphql/reference/scalars), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ## Discovering the GraphQL API @@ -130,4 +130,4 @@ query { {% endnote %} - For more information about performing queries, see "[Forming calls with GraphQL](/v4/guides/forming-calls)." + For more information about performing queries, see "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." diff --git a/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md b/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md index 171ad97756..8576e4ad69 100644 --- a/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md @@ -33,7 +33,7 @@ With the Enterprise Accounts API, you can: - Invite administrators to your enterprise account. - Create new organizations in your enterprise account. -For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/v4/guides/managing-enterprise-accounts/#graphql-fields-and-types-for-the-enterprise-accounts-api)." +For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)." ### Getting started using GraphQL for enterprise accounts @@ -197,12 +197,12 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio } ``` -For more information about getting started with GraphQL, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql/)" and "[Forming Calls with GraphQL](/v4/guides/forming-calls/)." +For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." ### GraphQL fields and types for the Enterprise Accounts API Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API. -For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/v4/). +For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql). -You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)." For other information, such as authentication and rate limit details, check out the [guides](/v4/guides). +You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)." For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). diff --git a/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md index dbc64338ed..27493df1c5 100644 --- a/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: Migrating from REST to GraphQL represents a significant shift in API logic. The differences between REST as a style and GraphQL as a specification make it difficult—and often undesirable—to replace REST API calls with GraphQL API queries on a one-to-one basis. We've included specific examples of migration below. -To migrate your code from the [REST API](/v3) to the GraphQL API: +To migrate your code from the [REST API](/rest) to the GraphQL API: - Review the [GraphQL spec](https://graphql.github.io/graphql-spec/June2018/) -- Review GitHub's [GraphQL schema](/v4/reference/) +- Review GitHub's [GraphQL schema](/graphql/reference) - Consider how any existing code you have currently interacts with the GitHub REST API -- Use [Global Node IDs](/v4/guides/using-global-node-ids) to reference objects between API versions +- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions Significant advantages of GraphQL include: @@ -53,12 +53,12 @@ query { } ``` -Consider another example: retrieving a list of pull requests and checking if each one is mergeable. A call to the REST API retrieves a list of pull requests and their [summary representations](/v3/#summary-representations): +Consider another example: retrieving a list of pull requests and checking if each one is mergeable. A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/v3/#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: +Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ Using the **GraphQL API**, you can retrieve the data with a single query using n } ``` -You can also extend the power of this query by [substituting a variable](/v4/guides/forming-calls/#working-with-variables) for the pull request number. +You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. ## Example: Strong typing GraphQL schemas are strongly typed, making data handling safer. -Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/v4/mutation), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/v4/mutation/addcomment/): +Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): ```graphql mutation { diff --git a/translations/ru-RU/content/graphql/guides/using-global-node-ids.md b/translations/ru-RU/content/graphql/guides/using-global-node-ids.md index 77307ca9eb..0fb33e4920 100644 --- a/translations/ru-RU/content/graphql/guides/using-global-node-ids.md +++ b/translations/ru-RU/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ You can access most objects in GitHub (users, issues, pull requests, etc.) using {% note %} -**Note:** In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql/#node)." +**Note:** In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." {% endnote %} @@ -29,7 +29,7 @@ Let's walk through an example. ### 1. Call a REST endpoint that returns an object's node ID -If you [request the authenticated user](/v3/users/#get-the-authenticated-user): +If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { This type of query—that is, finding the node by ID—is known as a "direct node lookup." -When you run this query, you'll see that the `__typename` is [`User`](/v4/object/user/). +When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). ### 3. Do a direct node lookup in GraphQL @@ -122,4 +122,4 @@ This type of query is the standard approach for looking up an object by its glob ### Using global node IDs in migrations -When building integrations that use either the REST API or the GraphQL API, it's best practice to persist the global node ID so you can easily reference objects across API versions. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/v4/guides/migrating-from-rest/)." +When building integrations that use either the REST API or the GraphQL API, it's best practice to persist the global node ID so you can easily reference objects across API versions. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." diff --git a/translations/ru-RU/content/graphql/guides/using-the-explorer.md b/translations/ru-RU/content/graphql/guides/using-the-explorer.md index f9b1c02f3e..50ced501bf 100644 --- a/translations/ru-RU/content/graphql/guides/using-the-explorer.md +++ b/translations/ru-RU/content/graphql/guides/using-the-explorer.md @@ -13,11 +13,11 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -[GraphQL Explorer](/v4/explorer) is an instance of [GraphiQL](https://github.com/graphql/graphiql), which is a "graphical interactive in-browser GraphQL IDE." +[GraphQL Explorer](/graphql/overview/explorer) is an instance of [GraphiQL](https://github.com/graphql/graphiql), which is a "graphical interactive in-browser GraphQL IDE." {% note %} -**Note**: {% data variables.product.prodname_dotcom %} has disabled [mutations](/v4/mutation/) in the Explorer, but you can use them in your own GraphiQL instance. +**Note**: {% data variables.product.prodname_dotcom %} has disabled [mutations](/graphql/reference/mutations) in the Explorer, but you can use them in your own GraphiQL instance. {% endnote %} @@ -33,7 +33,7 @@ To use the GraphiQL app, download and install it from https://github.com/skevy/g #### Configuring GraphiQL -1. Get an [OAuth token](/v4/guides/forming-calls#authenticating-with-graphql). +1. Get an [OAuth token](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql). 1. Launch GraphiQL. 1. In the upper-right corner of GraphiQL, click **Edit HTTP Headers**. 1. In the **Key** field, enter `Authorization`. In the **Value** field, enter `Bearer `, where `` is your generated OAuth token. ![graphiql headers](/assets/images/developer/graphiql-headers.png) @@ -44,7 +44,7 @@ To use the GraphiQL app, download and install it from https://github.com/skevy/g {% note %} -**Note**: For more information about why `POST` is the method, see "[Communicating with GraphQL](/v4/guides/forming-calls#communicating-with-graphql)." +**Note**: For more information about why `POST` is the method, see "[Communicating with GraphQL](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)." {% endnote %} @@ -66,13 +66,13 @@ All types in a GraphQL schema include a `description` field compiled into docume {% note %} -The **Docs** sidebar contains the same content that is automatically generated from the schema under "[Reference](/v4/)," though it is formatted differently in places. +The **Docs** sidebar contains the same content that is automatically generated from the schema under "[Reference](/graphql)," though it is formatted differently in places. {% endnote %} ### Using the variable pane -Some example calls include [variables](/v4/guides/forming-calls#working-with-variables) written like this: +Some example calls include [variables](/graphql/guides/forming-calls-with-graphql#working-with-variables) written like this: ```graphql query($number_of_repos:Int!){ @@ -90,7 +90,7 @@ variables { } ``` -This is the correct format to submit the call via a cURL `POST` (as long as you [escape newlines](/v4/guides/forming-calls#communicating-with-graphql)). +This is the correct format to submit the call via a cURL `POST` (as long as you [escape newlines](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)). If you want to run the call in the Explorer, enter the `query` segment in the main pane and the variables in the **Query Variables** pane below it. Omit the word `variables` from the Explorer: @@ -106,12 +106,12 @@ If you want to run the call in the Explorer, enter the `query` segment in the ma ### Troubleshooting errors -Because GraphQL is [introspective](/v4/guides/intro-to-graphql#discovering-the-graphql-api), the Explorer supports: +Because GraphQL is [introspective](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), the Explorer supports: * Intelligent typeaheads aware of the current schema * Validation error previews as you type -If you enter a query that is not well-formed or does not pass [schema validation](/v4/guides/intro-to-graphql#schema), a popup warns you of an error. If you run the query, the error returns in the response pane. +If you enter a query that is not well-formed or does not pass [schema validation](/graphql/guides/introduction-to-graphql#schema), a popup warns you of an error. If you run the query, the error returns in the response pane. A GraphQL response contains several keys: a `data` hash and an `errors` array. diff --git a/translations/ru-RU/content/graphql/overview/about-the-graphql-api.md b/translations/ru-RU/content/graphql/overview/about-the-graphql-api.md index 576e0accaf..05e03d7260 100644 --- a/translations/ru-RU/content/graphql/overview/about-the-graphql-api.md +++ b/translations/ru-RU/content/graphql/overview/about-the-graphql-api.md @@ -11,25 +11,25 @@ versions: Here are some quick links to get you up and running with the GraphQL API v4: -* [Authentication](/v4/guides/forming-calls/#authenticating-with-graphql) -* [Root endpoint](/v4/guides/forming-calls/#the-graphql-endpoint) -* [Schema introspection](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) -* [Rate limits](/v4/guides/resource-limitations/) -* [Migrating from REST](/v4/guides/migrating-from-rest) +* [Authentication](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) +* [Root endpoint](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) +* [Schema introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) +* [Rate limits](/graphql/overview/resource-limitations) +* [Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql) ### About GraphQL The [GraphQL](https://graphql.github.io/) data query language is: -* **A [specification](https://graphql.github.io/graphql-spec/June2018/).** The spec determines the validity of the [schema](/v4/guides/intro-to-graphql#schema) on the API server. The schema determines the validity of client calls. +* **A [specification](https://graphql.github.io/graphql-spec/June2018/).** The spec determines the validity of the [schema](/graphql/guides/introduction-to-graphql#schema) on the API server. The schema determines the validity of client calls. * **[Strongly typed](#about-the-graphql-schema-reference).** The schema defines an API's type system and all object relationships. -* **[Introspective](/v4/guides/intro-to-graphql#discovering-the-graphql-api).** A client can query the schema for details about the schema. +* **[Introspective](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api).** A client can query the schema for details about the schema. -* **[Hierarchical](/v4/guides/forming-calls).** The shape of a GraphQL call mirrors the shape of the JSON data it returns. [Nested fields](/v4/guides/migrating-from-rest/#example-nesting) let you query for and receive only the data you specify in a single round trip. +* **[Hierarchical](/graphql/guides/forming-calls-with-graphql).** The shape of a GraphQL call mirrors the shape of the JSON data it returns. [Nested fields](/graphql/guides/migrating-from-rest-to-graphql#example-nesting) let you query for and receive only the data you specify in a single round trip. -* **An application layer.** GraphQL is not a storage model or a database query language. The _graph_ refers to graph structures defined in the schema, where [nodes](/v4/guides/intro-to-graphql#node) define objects and [edges](/v4/guides/intro-to-graphql#edge) define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored. +* **An application layer.** GraphQL is not a storage model or a database query language. The _graph_ refers to graph structures defined in the schema, where [nodes](/graphql/guides/introduction-to-graphql#node) define objects and [edges](/graphql/guides/introduction-to-graphql#edge) define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored. ### Why GitHub is using GraphQL @@ -39,15 +39,15 @@ For more details about why GitHub has moved to GraphQL, see the original [announ ### About the GraphQL schema reference -The docs in the sidebar are generated from the {% data variables.product.prodname_dotcom %} GraphQL [schema](/v4/guides/intro-to-graphql/#discovering-the-graphql-api). All calls are validated and executed against the schema. Use these docs to find out what data you can call: +The docs in the sidebar are generated from the {% data variables.product.prodname_dotcom %} GraphQL [schema](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api). All calls are validated and executed against the schema. Use these docs to find out what data you can call: -* Allowed operations: [queries](/v4/query) and [mutations](/v4/mutation). +* Allowed operations: [queries](/graphql/reference/queries) and [mutations](/graphql/reference/mutations). -* Schema-defined types: [scalars](/v4/scalar), [objects](/v4/object), [enums](/v4/enum), [interfaces](/v4/interface), [unions](/v4/union), and [input objects](/v4/input_object). +* Schema-defined types: [scalars](/graphql/reference/scalars), [objects](/graphql/reference/objects), [enums](/graphql/reference/enums), [interfaces](/graphql/reference/interfaces), [unions](/graphql/reference/unions), and [input objects](/graphql/reference/input-objects). -You can access this same content via the [Explorer Docs sidebar](/v4/guides/using-the-explorer#accessing-the-sidebar-docs). Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API. +You can access this same content via the [Explorer Docs sidebar](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API. -For other information, such as authentication and rate limit details, check out the [guides](/v4/guides). +For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). ### Requesting support diff --git a/translations/ru-RU/content/graphql/overview/breaking-changes.md b/translations/ru-RU/content/graphql/overview/breaking-changes.md index f9fde6b0f6..ba29ae3c09 100644 --- a/translations/ru-RU/content/graphql/overview/breaking-changes.md +++ b/translations/ru-RU/content/graphql/overview/breaking-changes.md @@ -16,7 +16,7 @@ Breaking changes are any changes that might require action from our integrators. - **Breaking:** Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change. - **Dangerous:** Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change. -We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a [schema preview](/v4/previews/). +We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a [schema preview](/graphql/overview/schema-previews). We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st. diff --git a/translations/ru-RU/content/graphql/overview/changelog.md b/translations/ru-RU/content/graphql/overview/changelog.md index dbb8876a2b..6c051b659f 100644 --- a/translations/ru-RU/content/graphql/overview/changelog.md +++ b/translations/ru-RU/content/graphql/overview/changelog.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -Breaking changes include changes that will break existing queries or could affect the runtime behavior of clients. For a list of breaking changes and when they will occur, see our [breaking changes log](/v4/breaking_changes). +Breaking changes include changes that will break existing queries or could affect the runtime behavior of clients. For a list of breaking changes and when they will occur, see our [breaking changes log](/graphql/overview/breaking-changes). {% for entry in graphql.changelog %} ### Schema Changes for {{ entry.date }} diff --git a/translations/ru-RU/content/graphql/overview/public-schema.md b/translations/ru-RU/content/graphql/overview/public-schema.md index 0df87e7653..d2a8c7309b 100644 --- a/translations/ru-RU/content/graphql/overview/public-schema.md +++ b/translations/ru-RU/content/graphql/overview/public-schema.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -You can [perform introspection](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) against the GraphQL API directly. +You can [perform introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) against the GraphQL API directly. Alternatively, you can download the latest version of the public schema here: diff --git a/translations/ru-RU/content/graphql/overview/resource-limitations.md b/translations/ru-RU/content/graphql/overview/resource-limitations.md index bd5cdb791c..d0714a5d93 100644 --- a/translations/ru-RU/content/graphql/overview/resource-limitations.md +++ b/translations/ru-RU/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## Node limit -To pass [schema](/v4/guides/intro-to-graphql#schema) validation, all GraphQL API v4 [calls](/v4/guides/forming-calls) must meet these standards: +To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: -* Clients must supply a `first` or `last` argument on any [connection](/v4/guides/intro-to-graphql#connection). +* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). * Values of `first` and `last` must be within 1-100. -* Individual calls cannot request more than 500,000 total [nodes](/v4/guides/intro-to-graphql#node). +* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). #### Calculating nodes in a call @@ -121,7 +121,7 @@ These two examples show how to calculate the total nodes in a call. The GraphQL API v4 limit is different from the REST API v3's [rate limits](/rest/overview/resources-in-the-rest-api#rate-limiting). -Why are the API rate limits different? With [GraphQL](/v4/), one GraphQL call can replace [multiple REST calls](/v4/guides/migrating-from-rest/). A single complex GraphQL call could be the equivalent of thousands of REST requests. While a single GraphQL call would fall well below the REST API rate limit, the query might be just as expensive for GitHub's servers to compute. +Why are the API rate limits different? With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). A single complex GraphQL call could be the equivalent of thousands of REST requests. While a single GraphQL call would fall well below the REST API rate limit, the query might be just as expensive for GitHub's servers to compute. To accurately represent the server cost of a query, the GraphQL API v4 calculates a call's **rate limit score** based on a normalized scale of points. A query's score factors in first and last arguments on a parent connection and its children. diff --git a/translations/ru-RU/content/graphql/overview/schema-previews.md b/translations/ru-RU/content/graphql/overview/schema-previews.md index b0b3a5e30f..6272f17066 100644 --- a/translations/ru-RU/content/graphql/overview/schema-previews.md +++ b/translations/ru-RU/content/graphql/overview/schema-previews.md @@ -13,7 +13,7 @@ versions: During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -To access a schema preview, you'll need to provide a custom [media type](/v3/media) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. +To access a schema preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% note %} diff --git a/translations/ru-RU/content/graphql/reference/enums.md b/translations/ru-RU/content/graphql/reference/enums.md index 3cec114335..f87cc2e4cc 100644 --- a/translations/ru-RU/content/graphql/reference/enums.md +++ b/translations/ru-RU/content/graphql/reference/enums.md @@ -12,9 +12,9 @@ versions: [Enums](https://graphql.github.io/graphql-spec/June2018/#sec-Enums) represent possible sets of values for a field. -For example, the [`Issue`](/v4/object/issue) object has a field called `state`. The state is an enum (specifically, of type [`IssueState`](/v4/enum/issuestate/)) because it may be `OPEN` or `CLOSED`. +For example, the [`Issue`](/graphql/reference/objects#issue) object has a field called `state`. The state is an enum (specifically, of type [`IssueState`](/graphql/reference/enums#issuestate)) because it may be `OPEN` or `CLOSED`. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." {% for item in graphql.schemaForCurrentVersion.enums %} {% include graphql-enum %} diff --git a/translations/ru-RU/content/graphql/reference/input-objects.md b/translations/ru-RU/content/graphql/reference/input-objects.md index 6726cfaf2c..423c6511c8 100644 --- a/translations/ru-RU/content/graphql/reference/input-objects.md +++ b/translations/ru-RU/content/graphql/reference/input-objects.md @@ -12,9 +12,9 @@ versions: [Input objects](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects) can be described as "composable objects" because they include a set of input fields that define the object. -For example, [`CommitAuthor`](/v4/input_object/commitauthor/) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/v4/object) **may** have input objects, whereas [mutations](/v4/mutation) **require** input objects. +For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/graphql/reference/objects) **may** have input objects, whereas [mutations](/graphql/reference/mutations) **require** input objects. -For more information, see "[About mutations](/v4/guides/forming-calls#about-mutations)." +For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)." {% for item in graphql.schemaForCurrentVersion.inputObjects %} {% include graphql-input-object %} diff --git a/translations/ru-RU/content/graphql/reference/interfaces.md b/translations/ru-RU/content/graphql/reference/interfaces.md index 0baee2c467..bfc411d796 100644 --- a/translations/ru-RU/content/graphql/reference/interfaces.md +++ b/translations/ru-RU/content/graphql/reference/interfaces.md @@ -12,9 +12,9 @@ versions: [Interfaces](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces) serve as parent objects from which other objects can inherit. -For example, [`Lockable`](/v4/interface/lockable/) is an interface because both [`Issue`](/v4/object/issue/) and [`PullRequest`](/v4/object/pullrequest/) objects can be locked. An interface has its own list of named fields that are shared by implementing objects. +For example, [`Lockable`](/graphql/reference/interfaces#lockable) is an interface because both [`Issue`](/graphql/reference/objects#issue) and [`PullRequest`](/graphql/reference/objects#pullrequest) objects can be locked. An interface has its own list of named fields that are shared by implementing objects. -For more information, see "[Implementation](/v4/guides/intro-to-graphql#implementation)." +For more information, see "[Implementation](/graphql/guides/introduction-to-graphql#implementation)." {% for item in graphql.schemaForCurrentVersion.interfaces %} {% include graphql-interface %} diff --git a/translations/ru-RU/content/graphql/reference/mutations.md b/translations/ru-RU/content/graphql/reference/mutations.md index 9f6542ab79..e42955c3d3 100644 --- a/translations/ru-RU/content/graphql/reference/mutations.md +++ b/translations/ru-RU/content/graphql/reference/mutations.md @@ -12,7 +12,7 @@ versions: Every GraphQL schema has a root type for both queries and mutations. The [mutation type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that change data on the server. It is analogous to performing HTTP verbs such as `POST`, `PATCH`, and `DELETE`. -For more information, see "[About mutations](/v4/guides/forming-calls#about-mutations)." +For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)." {% for item in graphql.schemaForCurrentVersion.mutations %} {% include graphql-mutation %} diff --git a/translations/ru-RU/content/graphql/reference/objects.md b/translations/ru-RU/content/graphql/reference/objects.md index 84cbbabfdf..345786d5e1 100644 --- a/translations/ru-RU/content/graphql/reference/objects.md +++ b/translations/ru-RU/content/graphql/reference/objects.md @@ -14,7 +14,7 @@ versions: For example, the [`Repository`](/graphql/reference/objects#repository) object has a field called `name`, which is a `String`. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." diff --git a/translations/ru-RU/content/graphql/reference/queries.md b/translations/ru-RU/content/graphql/reference/queries.md index 4d87cd2e25..a2cc6af7b1 100644 --- a/translations/ru-RU/content/graphql/reference/queries.md +++ b/translations/ru-RU/content/graphql/reference/queries.md @@ -13,7 +13,7 @@ versions: Every GraphQL schema has a root type for both queries and mutations. The [query type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that retrieve data from the server. -For more information, see "[About queries](/v4/guides/forming-calls#about-queries)." +For more information, see "[About queries](/graphql/guides/forming-calls-with-graphql#about-queries)." {% note %} diff --git a/translations/ru-RU/content/graphql/reference/scalars.md b/translations/ru-RU/content/graphql/reference/scalars.md index 0a37135d2c..338b4f42c7 100644 --- a/translations/ru-RU/content/graphql/reference/scalars.md +++ b/translations/ru-RU/content/graphql/reference/scalars.md @@ -14,7 +14,7 @@ versions: When calling the GraphQL API, you must specify nested subfields until you return only scalars. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql#field)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#field)." {% for item in graphql.schemaForCurrentVersion.scalars %} {% include graphql-scalar %} diff --git a/translations/ru-RU/content/graphql/reference/unions.md b/translations/ru-RU/content/graphql/reference/unions.md index 95f5a9f633..5a87c63fc0 100644 --- a/translations/ru-RU/content/graphql/reference/unions.md +++ b/translations/ru-RU/content/graphql/reference/unions.md @@ -12,9 +12,9 @@ versions: A [union](https://graphql.github.io/graphql-spec/June2018/#sec-Unions) is a type of object representing many objects. -For example, a field marked as an [`ProjectCardItem`](/v4/union/projectcarditem/) could be an [`Issue`](/v4/object/issue/) or a [`PullRequest`](/v4/object/pullrequest/) because each of those objects can be inside a project card. Using a union instead of an object gives you flexibility. +For example, a field marked as an [`ProjectCardItem`](/graphql/reference/unions#projectcarditem) could be an [`Issue`](/graphql/reference/objects#issue) or a [`PullRequest`](/graphql/reference/objects#pullrequest) because each of those objects can be inside a project card. Using a union instead of an object gives you flexibility. -For more information, see "[Introduction to GraphQL](/v4/guides/intro-to-graphql)." +For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)." {% for item in graphql.schemaForCurrentVersion.unions %} {% include graphql-union %} diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 87f5be536c..a4cfdabbeb 100644 --- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: Enabling a link between GitHub Insights and GitHub Enterprise -intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {{ site.data.variables.product.prodname_insights }}.' +intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.' redirect_from: diff --git a/translations/ru-RU/content/packages/publishing-and-managing-packages/about-github-packages.md b/translations/ru-RU/content/packages/publishing-and-managing-packages/about-github-packages.md index c3364bf00d..34595ed9a0 100644 --- a/translations/ru-RU/content/packages/publishing-and-managing-packages/about-github-packages.md +++ b/translations/ru-RU/content/packages/publishing-and-managing-packages/about-github-packages.md @@ -182,7 +182,7 @@ When you create a {% data variables.product.prodname_actions %} workflow, you ca ### Managing packages -You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package)" and "[Forming calls with GraphQL](/v4/guides/forming-calls/)." +You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." diff --git a/translations/ru-RU/content/rest/guides/basics-of-authentication.md b/translations/ru-RU/content/rest/guides/basics-of-authentication.md index 2abad95383..60ab1b8afc 100644 --- a/translations/ru-RU/content/rest/guides/basics-of-authentication.md +++ b/translations/ru-RU/content/rest/guides/basics-of-authentication.md @@ -130,7 +130,7 @@ Also, since there's a hierarchical relationship between scopes, you should check Checking for scopes only before making requests is not enough since it's possible that users will change the scopes in between your check and the actual request. In case that happens, API calls you expected to succeed might fail with a `404` or `401` status, or return a different subset of information. -To help you gracefully handle these situations, all API responses for requests made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes]. This header contains the list of scopes of the token that was used to make the request. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/v3/apps/oauth_applications/#check-an-authorization\]{% endif %}. Use this information to detect changes in token scopes, and inform your users of changes in available application functionality. +To help you gracefully handle these situations, all API responses for requests made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes]. This header contains the list of scopes of the token that was used to make the request. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. Use this information to detect changes in token scopes, and inform your users of changes in available application functionality. #### Making authenticated requests diff --git a/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md b/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md index a391e94b22..a376d64466 100644 --- a/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md +++ b/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md @@ -20,7 +20,7 @@ It's very important that you secure [the payloads sent from GitHub][event-types] There are several steps you can take to secure receipt of payloads delivered by GitHub: 1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% if currentVersion == "free-pro-team@latest" %} -1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/v3/meta/#meta) to find the address we use.{% endif %} +1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %} 1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected. ### Favor asynchronous work over synchronous @@ -49,7 +49,7 @@ Users can dig into the server responses you send back to GitHub. Ensure that you GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove. -We've provided [a list of HTTP status codes](/v3/#http-redirects) to watch out for when designing your app to follow redirects. +We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects. ### Don't manually parse URLs diff --git a/translations/ru-RU/content/rest/guides/building-a-ci-server.md b/translations/ru-RU/content/rest/guides/building-a-ci-server.md index 617e14ef14..fab413a4b9 100644 --- a/translations/ru-RU/content/rest/guides/building-a-ci-server.md +++ b/translations/ru-RU/content/rest/guides/building-a-ci-server.md @@ -129,7 +129,7 @@ At GitHub, we've used a version of [Janky][janky] to manage our CI for years. Th All of this communication is funneled back to our chat rooms. You don't need to build your own CI setup to use this example. You can always rely on [GitHub integrations][integrations]. -[status API]: /v3/repos/statuses/ +[status API]: /rest/reference/repos#statuses [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server diff --git a/translations/ru-RU/content/rest/guides/delivering-deployments.md b/translations/ru-RU/content/rest/guides/delivering-deployments.md index 5634a80079..d5713bacec 100644 --- a/translations/ru-RU/content/rest/guides/delivering-deployments.md +++ b/translations/ru-RU/content/rest/guides/delivering-deployments.md @@ -145,7 +145,7 @@ At GitHub, we've used a version of [Heaven][heaven] to manage our deployments fo That's it! You don't need to build your own deployment setup to use this example. You can always rely on [GitHub integrations][integrations]. -[deploy API]: /v3/repos/deployments/ +[deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok diff --git a/translations/ru-RU/content/rest/guides/discovering-resources-for-a-user.md b/translations/ru-RU/content/rest/guides/discovering-resources-for-a-user.md index 48301c2ed4..45840dd9fa 100644 --- a/translations/ru-RU/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/ru-RU/content/rest/guides/discovering-resources-for-a-user.md @@ -93,19 +93,19 @@ If you've read the docs from cover to cover, you may have noticed an [API method As an application, you typically want all of the user's organizations (public and private) that your app is authorized to access. The workflow above will give you exactly that. -[basics-of-authentication]: /v3/guides/basics-of-authentication/ -[list-public-orgs]: /v3/orgs/#list-organizations-for-a-user -[list-repositories-for-current-user]: /v3/repos/#list-repositories-for-the-authenticated-user -[list-orgs-for-current-user]: /v3/orgs/#list-organizations-for-the-authenticated-user -[list-teams]: /v3/teams/#list-teams -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests +[basics-of-authentication]: /rest/guides/basics-of-authentication +[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user +[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user +[list-teams]: /rest/reference/teams#list-teams +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ [octokit.rb]: https://github.com/octokit/octokit.rb [octokit.rb]: https://github.com/octokit/octokit.rb -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user -[publicize-membership]: /v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user -[register-oauth-app]: /v3/guides/basics-of-authentication/#registering-your-app +[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user +[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/ru-RU/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/ru-RU/content/rest/guides/getting-started-with-the-git-database-api.md index 32e3af1347..4b6a7b8a1a 100644 --- a/translations/ru-RU/content/rest/guides/getting-started-with-the-git-database-api.md +++ b/translations/ru-RU/content/rest/guides/getting-started-with-the-git-database-api.md @@ -11,7 +11,7 @@ versions: This basically allows you to reimplement a lot of Git functionality over our API - by creating raw objects directly into the database and updating branch references you could technically do just about anything that Git can do without having Git installed. -Git Database API functions will return a `409 Conflict` if the Git repository is empty or unavailable. An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the "[Create or update file contents](/v3/repos/contents/#create-or-update-file-contents)" endpoint to create content and initialize the repository so you can use the Git Database API. Contact {% data variables.contact.contact_support %} if this response status persists. +Git Database API functions will return a `409 Conflict` if the Git repository is empty or unavailable. An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" endpoint to create content and initialize the repository so you can use the Git Database API. Contact {% data variables.contact.contact_support %} if this response status persists. ![git database overview](/assets/images/git-database-overview.png) @@ -33,14 +33,14 @@ It might seem complex, but it's actually pretty simple when you understand the m {% warning %} -**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. +**Warning!** Please do not depend on using Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs, because this content becomes outdated without warning. {% endwarning %} -A consuming API needs to explicitly request a pull request to create a _test_ merge commit. A _test_ merge commit is created when you view the pull request in the UI and the "Merge" button is displayed, or when you [get](/v3/pulls/#get-a-pull-request), [create](/v3/pulls/#create-a-pull-request), or [edit](/v3/pulls/#update-a-pull-request) a pull request using the REST API. Without this request, the `merge` Git refs will fall out of date until the next time someone views the pull request. +A consuming API needs to explicitly request a pull request to create a _test_ merge commit. A _test_ merge commit is created when you view the pull request in the UI and the "Merge" button is displayed, or when you [get](/rest/reference/pulls#get-a-pull-request), [create](/rest/reference/pulls#create-a-pull-request), or [edit](/rest/reference/pulls#update-a-pull-request) a pull request using the REST API. Without this request, the `merge` Git refs will fall out of date until the next time someone views the pull request. If you are currently using polling methods that produce outdated `merge` Git refs, then GitHub recommends using the following steps to get the latest changes from the default branch: 1. Receive the pull request webhook. -2. Call [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) to start a background job for creating the merge commit candidate. -3. Poll your repository using [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) to see if the `mergeable` attribute is `true` or `false`. You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. +2. Call [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) to start a background job for creating the merge commit candidate. +3. Poll your repository using [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) to see if the `mergeable` attribute is `true` or `false`. You can use Git directly or [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` Git refs only after performing the previous steps. diff --git a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md index 93a70f433c..c0e4e63f87 100644 --- a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md @@ -367,33 +367,33 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]! [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[repos-api]: /v3/repos/ -[repos-api]: /v3/repos/ +[repos-api]: /rest/reference/repos +[repos-api]: /rest/reference/repos [pages]: http://pages.github.com [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore -[issues-api]: /v3/issues/ +[issues-api]: /rest/reference/issues [link-header]: http://www.w3.org/wiki/LinkHeader/ -[conditional-requests]: /v3/#conditional-requests -[rate-limiting]: /v3/#rate-limiting -[rate-limiting]: /v3/#rate-limiting -[users api]: /v3/users/#get-a-user +[conditional-requests]: /rest#conditional-requests +[rate-limiting]: /rest#rate-limiting +[rate-limiting]: /rest#rate-limiting +[users api]: /rest/reference/users#get-a-user [defunkt github]: https://github.com/defunkt [defunkt github]: https://github.com/defunkt [json]: http://en.wikipedia.org/wiki/JSON -[authentication]: /v3/#authentication +[authentication]: /rest#authentication [personal token]: /articles/creating-an-access-token-for-command-line-use [personal token]: /articles/creating-an-access-token-for-command-line-use [tokens settings]: https://github.com/settings/tokens -[pagination]: /v3/#pagination -[get repo]: /v3/repos/#get-a-repository -[create repo]: /v3/repos/#create-a-repository-for-the-authenticated-user -[create issue]: /v3/issues/#create-an-issue +[pagination]: /rest#pagination +[get repo]: /rest/reference/repos#get-a-repository +[create repo]: /rest/reference/repos#create-a-repository-for-the-authenticated-user +[create issue]: /rest/reference/issues#create-an-issue [auth guide]: /guides/basics-of-authentication -[user repos api]: /v3/repos/#list-repositories-for-the-authenticated-user -[other user repos api]: /v3/repos/#list-repositories-for-a-user -[org repos api]: /v3/repos/#list-organization-repositories -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[repo issues api]: /v3/issues/#list-repository-issues +[user repos api]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[other user repos api]: /rest/reference/repos#list-repositories-for-a-user +[org repos api]: /rest/reference/repos#list-organization-repositories +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[repo issues api]: /rest/reference/issues#list-repository-issues [etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md b/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md index 292181cd58..ff1c44d330 100644 --- a/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md @@ -333,7 +333,7 @@ Et voila! Beautiful rectangles containing your repo languages, with relative pro [Octokit]: https://github.com/octokit/octokit.rb [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ [D3 treemap]: http://bl.ocks.org/mbostock/4063582 -[language API]: /v3/repos/#list-repository-languages -[language API]: /v3/repos/#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs [new oauth application]: https://github.com/settings/applications/new diff --git a/translations/ru-RU/content/rest/guides/traversing-with-pagination.md b/translations/ru-RU/content/rest/guides/traversing-with-pagination.md index e3171400f0..7783f89877 100644 --- a/translations/ru-RU/content/rest/guides/traversing-with-pagination.md +++ b/translations/ru-RU/content/rest/guides/traversing-with-pagination.md @@ -20,9 +20,9 @@ In this guide, we'll make some calls to the {% data variables.product.product_na To start with, it's important to know a few facts about receiving paginated items: -1. Different API calls respond with different defaults. For example, a call to [List public repositories](/v3/repos/#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API provides items in sets of 100 +1. Different API calls respond with different defaults. For example, a call to [List public repositories](/rest/reference/repos#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API provides items in sets of 100 2. You can specify how many items to receive (up to a maximum of 100); but, -3. For technical reasons, not every endpoint behaves the same. For example, [events](/v3/activity/events/) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. +3. For technical reasons, not every endpoint behaves the same. For example, [events](/rest/reference/activity#events) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. Information about pagination is provided in [the Link header](http://tools.ietf.org/html/rfc5988) of an API call. For example, let's make a curl request to the search API, to find out how many times Mozilla projects use the phrase `addClass`: @@ -201,7 +201,7 @@ puts "The prev page link is #{prev_page_href}" puts "The next page link is #{next_page_href}" ``` -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination [octokit.rb]: https://github.com/octokit/octokit.rb [personal token]: /articles/creating-an-access-token-for-command-line-use diff --git a/translations/ru-RU/content/rest/guides/working-with-comments.md b/translations/ru-RU/content/rest/guides/working-with-comments.md index eb56a1f30e..4b48576560 100644 --- a/translations/ru-RU/content/rest/guides/working-with-comments.md +++ b/translations/ru-RU/content/rest/guides/working-with-comments.md @@ -97,8 +97,8 @@ Note that this API call will retrieve single line comments, as well as comments [commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 [sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 [platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments -[issues]: /v3/issues/comments/ +[issues]: /rest/reference/issues#comments [personal token]: /articles/creating-an-access-token-for-command-line-use [octokit.rb]: https://github.com/octokit/octokit.rb -[PR Review API]: /v3/pulls/comments/ -[commit comment API]: /v3/repos/comments/#get-a-commit-comment +[PR Review API]: /rest/reference/pulls#comments +[commit comment API]: /rest/reference/repos#get-a-commit-comment diff --git a/translations/ru-RU/content/rest/overview/api-previews.md b/translations/ru-RU/content/rest/overview/api-previews.md index 1d7dc7cdbe..1806d8eef0 100644 --- a/translations/ru-RU/content/rest/overview/api-previews.md +++ b/translations/ru-RU/content/rest/overview/api-previews.md @@ -15,12 +15,12 @@ API previews let you try out new APIs and changes to existing API methods before During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -To access an API preview, you'll need to provide a custom [media type](/v3/media) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. +To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% if currentVersion == "free-pro-team@latest" %} ### Migrations -Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/v3/migrations/) data to {% data variables.product.prodname_ghe_server %}. +Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/rest/reference/migrations) data to {% data variables.product.prodname_ghe_server %}. **Custom media type:** `wyandotte-preview` **Announced:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) {% endif %} @@ -33,13 +33,13 @@ Exercise greater control over [deployments](/v3/repos/deployments/) with more in ### Reactions -Manage [reactions](/v3/reactions/) for commits, issues, and comments. +Manage [reactions](/rest/reference/reactions) for commits, issues, and comments. **Custom media type:** `squirrel-girl-preview` **Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) ### Timeline -Get a [list of events](/v3/issues/timeline/) for an issue or pull request. +Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request. **Custom media type:** `mockingbird-preview` **Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) @@ -61,40 +61,40 @@ Manage [integrations](/early-access/integrations/) through the API. ### Projects -Manage [projects](/v3/projects/). +Manage [projects](/rest/reference/projects). **Custom media type:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) ### Commit search -[Search commits](/v3/search/). +[Search commits](/rest/reference/search). **Custom media type:** `cloak-preview` **Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% if currentVersion == "free-pro-team@latest" %} ### User blocking -Users can [block other users](/v3/users/blocking/). Organizations can [block users](/v3/orgs/blocking/), too. +Users can [block other users](/rest/reference/users#blocking). Organizations can [block users](/rest/reference/orgs#blocking), too. **Custom media type:** `giant-sentry-fist-preview` **Announced:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Update 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Update 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) {% endif %} ### Repository topics -View a list of [repository topics](/articles/about-topics/) in [calls](/v3/repos/) that return repository results. +View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results. **Custom media type:** `mercy-preview` **Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics) ### Codes of conduct -View all [codes of conduct](/v3/codes_of_conduct) or get which code of conduct a repository has currently. +View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently. **Custom media type:** `scarlet-witch-preview` {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### Nested teams -Include nested team content in [team](/v3/teams/) payloads. +Include nested team content in [team](/rest/reference/teams) payloads. **Custom media type:** `hellcat-preview` **Announced:** [2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) @@ -113,7 +113,7 @@ Enables [global webhooks](/v3/enterprise-admin/global_webhooks/) for [organizat {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### Repository transfer -Transfer a [repository](/v3/repos/) to an organization or user. +Transfer a [repository](/rest/reference/repos) to an organization or user. **Custom media type:** `nightshade-preview` **Announced:** [2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) {% endif %} @@ -121,27 +121,27 @@ Transfer a [repository](/v3/repos/) to an organization or user. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### Add lock reason -You can now add a reason when you [lock an issue](/v3/issues/#lock-an-issue). +You can now add a reason when you [lock an issue](/rest/reference/issues#lock-an-issue). **Custom media type:** `sailor-v-preview` **Announced:** [2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) {% endif %} ### Require signed commits -You can now use the API to manage the setting for [requiring signed commits on protected branches](/v3/repos/branches). +You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches). **Custom media type:** `zzzax-preview` **Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) ### Require multiple approving reviews -You can now [require multiple approving reviews](/v3/repos/branches) for a pull request using the API. +You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API. **Custom media type:** `luke-cage-preview` **Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.19" %} ### Retrieve hovercard information -Retrieve information from [someone's hovercard](/v3/users/#get-contextual-information-for-a-user). +Retrieve information from [someone's hovercard](/rest/reference/users#get-contextual-information-for-a-user). **Custom media type:** `echo-preview` **Announced:** [2018-02-07](https://developer.github.com/changes/2018-02-07-team-discussions-api) @@ -150,7 +150,7 @@ Retrieve information from [someone's hovercard](/v3/users/#get-contextual-inform {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} ### Check runs and check suites API -Allows a GitHub App to run external checks on a repository's code. See the [Check runs](/v3/checks/runs/) and [Check suites](/v3/checks/suites/) APIs for more details. +Allows a GitHub App to run external checks on a repository's code. See the [Check runs](/rest/reference/checks#runs) and [Check suites](/rest/reference/checks#suites) APIs for more details. **Custom media type:** `antiope-preview` **Announced:** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) {% endif %} @@ -167,7 +167,7 @@ When a {% data variables.product.prodname_ghe_server %} instance is in private m ### Project card details -The REST API responses for [issue events](/v3/issues/events/) and [issue timeline events](/v3/issues/timeline/) now return the `project_card` field for project-related events. +The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events. **Custom media type:** `starfox-preview` **Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) @@ -189,7 +189,7 @@ You can now update the `environment` of a [deployment status](/v3/repos/deployme ### Repository creation permissions -You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/v3/orgs/#update-an-organization)" for more details. +You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details. **Custom media types:** `surtur-preview` **Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) @@ -202,7 +202,7 @@ You can now provide more information in GitHub for URLs that link to registered {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### Draft pull requests -You can use the Draft Pull Requests API and its [pull request](/v3/pulls/) endpoints to see whether a pull request is in draft state. To learn more about draft pull requests, see "[About pull requests](/articles/about-pull-requests/)". +You can use the Draft Pull Requests API and its [pull request](/rest/reference/pulls) endpoints to see whether a pull request is in draft state. To learn more about draft pull requests, see "[About pull requests](/articles/about-pull-requests/)". **Custom media types:** `shadow-cat-preview` **Announced:** [2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) @@ -216,48 +216,48 @@ You can use the new endpoints in the [Pages API](/v3/repos/pages/) to enable or ### List branches or pull requests for a commit -You can use two new endpoints in the [Commits API](/v3/repos/commits/) to list branches or pull requests for a commit. +You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit. **Custom media types:** `groot-preview` **Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### Uninstall a GitHub App -Owners of GitHub Apps can now uninstall an app using the [Apps API](/v3/apps/#delete-an-installation-for-the-authenticated-app). +Owners of GitHub Apps can now uninstall an app using the [Apps API](/rest/reference/apps#delete-an-installation-for-the-authenticated-app). **Custom media types:** `gambit-preview` {% endif %} ### Enable or disable vulnerability alerts for a repository -You can use two new endpoints in the [Repos API](/v3/repos/) to enable or disable vulnerability alerts. +You can use two new endpoints in the [Repos API](/rest/reference/repos) to enable or disable vulnerability alerts. **Custom media types:** `dorian-preview` **Announced:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) ### Update a pull request branch -You can use a new endpoint to [update a pull request branch](/v3/pulls/#update-a-pull-request-branch) with changes from the HEAD of the upstream branch. +You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch. **Custom media types:** `lydian-preview` **Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) {% if currentVersion == "free-pro-team@latest" %} ### Enable or disable automated security fixes -You can use a new set of endpoints to [enable and disable automated security fixes](/v3/repos/#enable-automated-security-fixes). +You can use a new set of endpoints to [enable and disable automated security fixes](/rest/reference/repos#enable-automated-security-fixes). **Custom media types:** `london-preview` **Announced:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ### Create and use repository templates -You can use a new endpoint to [Create a repository using a template](/v3/repos/#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/v3/repos/#get-a-repository) to check whether it's set as a template repository using the `is_template` key. +You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key. **Custom media types:** `baptiste-preview` **Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% if currentVersion == "enterprise-server@2.20" %} ### New OAuth Applications API endpoints -You can more securely manage tokens for OAuth Apps by using OAuth tokens as input parameters instead of path parameters with the new [OAuth Applications API](/v3/apps/oauth_applications/) endpoints. +You can more securely manage tokens for OAuth Apps by using OAuth tokens as input parameters instead of path parameters with the new [OAuth Applications API](/rest/reference/apps#oauth-applications) endpoints. **Custom media types:** `doctor-strange-preview` **Announced:** [2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) {% endif %} @@ -265,7 +265,7 @@ You can more securely manage tokens for OAuth Apps by using OAuth tokens as inpu {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ### New visibility parameter for the Repositories API -You can set and retrieve the visibility of a repository in the [Repositories API](/v3/repos/). +You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos). **Custom media types:** `nebula-preview` **Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/ru-RU/content/rest/overview/media-types.md b/translations/ru-RU/content/rest/overview/media-types.md index cebcfb498c..db238d6341 100644 --- a/translations/ru-RU/content/rest/overview/media-types.md +++ b/translations/ru-RU/content/rest/overview/media-types.md @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### Comment body properties -The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/v3/issues/), [issue comments](/v3/issues/comments/), [pull request comments](/v3/pulls/comments/), and the [gist comments](/v3/gists/comments/) APIs all accept these same media types: +The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: #### Raw @@ -85,7 +85,7 @@ Return raw, text and HTML representations. Response will include `body`, `body_t ### Git blob properties -The following media types are allowed when [getting a blob](/v3/git/blobs/#get-a-blob): +The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): #### JSON @@ -102,7 +102,7 @@ Return the raw blob data. ### Commits, commit comparison, and pull requests -The [commits API](/v3/repos/commits/) and [pull requests API](/v3/pulls/) support [diff][git-diff] and [patch][git-patch] formats: +The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: #### разница @@ -147,4 +147,4 @@ The gist contents are base64-encoded before being sent out. This can be useful i [gfm]: http://github.github.com/github-flavored-markdown/ [git-diff]: http://git-scm.com/docs/git-diff [git-patch]: http://git-scm.com/docs/git-format-patch -[versions]: /v3/versions +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/ru-RU/content/rest/overview/other-authentication-methods.md b/translations/ru-RU/content/rest/overview/other-authentication-methods.md index 26fe40cff4..afa1fd3815 100644 --- a/translations/ru-RU/content/rest/overview/other-authentication-methods.md +++ b/translations/ru-RU/content/rest/overview/other-authentication-methods.md @@ -59,7 +59,7 @@ For example, if you're accessing the API via [cURL][curl], the following command ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/v3/auth/#working-with-two-factor-authentication). +If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). {% endif %} @@ -124,8 +124,8 @@ $ curl --request POST \ {% endif %} [curl]: http://curl.haxx.se/ -[oauth-auth]: /v3/#authentication +[oauth-auth]: /rest#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -[user-issues]: /v3/issues/#list-issues-assigned-to-the-authenticated-user +[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md index 65ca0ecb94..4b76372d51 100644 --- a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md @@ -14,13 +14,13 @@ This describes the resources that make up the official {% data variables.product ### Current version -By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/v3/versions) of the REST API. We encourage you to [explicitly request this version via the `Accept` header](/v3/media/#request-specific-version). +By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API. We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version). Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -For information about GitHub's GraphQL API, see the [v4 documentation](/v4). For information about migrating to GraphQL, see "[Migrating from REST](/v4/guides/migrating-from-rest/)." +For information about GitHub's GraphQL API, see the [v4 documentation](/graphql). For information about migrating to GraphQL, see "[Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql)." {% endif %} @@ -171,7 +171,7 @@ $ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "gith ### GraphQL global node IDs -See the guide on "[Using Global Node IDs](/v4/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. +See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. ### Client errors @@ -262,7 +262,7 @@ You can then expand these templates using something like the [uri_template][uri] ### Pagination -Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/v3/activity/events/) for example. +Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' @@ -287,7 +287,7 @@ The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination inform _The example includes a line break for readability._ -This `Link` response header contains one or more [Hypermedia](/v3/#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). +This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). The possible `rel` values are: @@ -312,7 +312,7 @@ For unauthenticated requests, the rate limit allows for up to 60 requests per ho {% data reusables.enterprise.rate_limit %} -Note that [the Search API has custom rate limit rules](/v3/search/#rate-limit). +Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). The returned HTTP headers of any API request show your current rate limit status: @@ -355,7 +355,7 @@ If you exceed the rate limit, an error response returns: > } ``` -You can [check your rate limit status](/v3/rate_limit) without incurring an API hit. +You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. #### Increasing the unauthenticated rate limit for OAuth applications @@ -586,9 +586,9 @@ Some requests that create new data, such as creating a new commit, allow you to #### Explicitly providing an ISO 8601 timestamp with timezone information -For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/v3/git/commits). +For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits). -These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/v3/git/commits/#example-input) for how these timestamps can be specified. +These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. #### Using the `Time-Zone` header @@ -598,7 +598,7 @@ It is possible to supply a `Time-Zone` header which defines a timezone according $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/v3/repos/contents/) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. +This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. #### Using the last known timezone for the user diff --git a/translations/ru-RU/content/rest/overview/troubleshooting.md b/translations/ru-RU/content/rest/overview/troubleshooting.md index dde7daba1b..fe452f17d8 100644 --- a/translations/ru-RU/content/rest/overview/troubleshooting.md +++ b/translations/ru-RU/content/rest/overview/troubleshooting.md @@ -23,7 +23,7 @@ To troubleshoot, ensure [you're authenticating correctly](/guides/getting-starte Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support pagination. If you're making requests and receiving an incomplete set of results, you're probably only seeing the first page. You'll need to request the remaining pages in order to get more results. -It's important to *not* try and guess the format of the pagination URL. Not every API call uses the same structure. Instead, extract the pagination information from [the Link Header](/v3/#pagination), which is sent with every request. +It's important to *not* try and guess the format of the pagination URL. Not every API call uses the same structure. Instead, extract the pagination information from [the Link Header](/rest#pagination), which is sent with every request. {% if currentVersion == "free-pro-team@latest" %} ### Basic authentication errors diff --git a/translations/ru-RU/content/rest/reference/apps.md b/translations/ru-RU/content/rest/reference/apps.md index e458f98399..a59a43409f 100644 --- a/translations/ru-RU/content/rest/reference/apps.md +++ b/translations/ru-RU/content/rest/reference/apps.md @@ -18,7 +18,7 @@ When authenticated as a GitHub App, the GitHub Apps API enables you to get high- 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](/v3/apps/installations/) for a list of these endpoints. +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 %} @@ -36,7 +36,7 @@ You can use this API to manage the OAuth tokens an OAuth application uses to acc 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](/v3/orgs/#list-app-installations-for-an-organization)." +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 %} @@ -70,4 +70,4 @@ Be sure to replace stubbed endpoints with production endpoints before deploying {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ru-RU/content/rest/reference/codes-of-conduct.md b/translations/ru-RU/content/rest/reference/codes-of-conduct.md index 16d7e8bda3..50cb78757e 100644 --- a/translations/ru-RU/content/rest/reference/codes-of-conduct.md +++ b/translations/ru-RU/content/rest/reference/codes-of-conduct.md @@ -9,6 +9,6 @@ versions: github-ae: '*' --- -You can use the Codes of Conduct API to retrieve information about a repository's code of conduct. To get a repository's code of conduct, use the "[Get a repository](/v3/repos/#get-a-repository)" endpoint. +You can use the Codes of Conduct API to retrieve information about a repository's code of conduct. To get a repository's code of conduct, use the "[Get a repository](/rest/reference/repos#get-a-repository)" endpoint. {% include rest_operations_at_current_path %} diff --git a/translations/ru-RU/content/rest/reference/enterprise-admin.md b/translations/ru-RU/content/rest/reference/enterprise-admin.md index 1e969094e0..5437c29df8 100644 --- a/translations/ru-RU/content/rest/reference/enterprise-admin.md +++ b/translations/ru-RU/content/rest/reference/enterprise-admin.md @@ -86,7 +86,7 @@ The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/v3/auth/#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." {% endnote %} diff --git a/translations/ru-RU/content/rest/reference/git.md b/translations/ru-RU/content/rest/reference/git.md index ef43832bc6..4d3d088ee8 100644 --- a/translations/ru-RU/content/rest/reference/git.md +++ b/translations/ru-RU/content/rest/reference/git.md @@ -34,7 +34,7 @@ For more information, see "[Media types](/rest/overview/media-types)." ## Commits -A Git commit is a snapshot of the hierarchy ([Git tree](/v3/git/trees)) and the contents of the files ([Git blob](/v3/git/blobs)) in a Git repository. These endpoints allow you to read and write [commit objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) to your Git database on {% data variables.product.product_name %}. +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. These endpoints allow you to read and write [commit objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) to your Git database on {% data variables.product.product_name %}. {% for operation in currentRestOperations %} {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} @@ -50,7 +50,7 @@ A Git reference (`git ref`) is just a file that contains a Git commit SHA-1 hash ## Tags -A Git tag is similar to a [Git reference](/v3/git/refs), but the Git commit that it points to never changes. Git tags are helpful when you want to point to specific releases. These endpoints allow you to read and write [tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) to your Git database on {% data variables.product.product_name %}. The Git tags API only supports [annotated tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), not lightweight tags. +A Git tag is similar to a [Git reference](/rest/reference/git#refs), but the Git commit that it points to never changes. Git tags are helpful when you want to point to specific releases. These endpoints allow you to read and write [tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) to your Git database on {% data variables.product.product_name %}. The Git tags API only supports [annotated tag objects](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), not lightweight tags. {% for operation in currentRestOperations %} {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %} diff --git a/translations/ru-RU/content/rest/reference/issues.md b/translations/ru-RU/content/rest/reference/issues.md index a368a136f7..cdce650dd5 100644 --- a/translations/ru-RU/content/rest/reference/issues.md +++ b/translations/ru-RU/content/rest/reference/issues.md @@ -33,7 +33,7 @@ For more information about media types, see "[Custom media types](/rest/overview The Issue Comments API supports listing, viewing, editing, and creating comments on issues and pull requests. -Issue Comments use [these custom media types](#custom-media-types). You can read more about the use of media types in the API [here](/v3/media/). +Issue Comments use [these custom media types](#custom-media-types). 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 == 'comments' %}{% include rest_operation %}{% endif %} diff --git a/translations/ru-RU/content/rest/reference/licenses.md b/translations/ru-RU/content/rest/reference/licenses.md index 0ccf586a35..080f5cba43 100644 --- a/translations/ru-RU/content/rest/reference/licenses.md +++ b/translations/ru-RU/content/rest/reference/licenses.md @@ -16,12 +16,12 @@ If a license is matched, the license key and name returned conforms to the [SPDX **Note:** These endpoints will also return a repository's license information: -- [Get a repository](/v3/repos/#get-a-repository) -- [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -- [List organization repositories](/v3/repos/#list-organization-repositories) +- [Get a repository](/rest/reference/repos#get-a-repository) +- [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user) +- [List organization repositories](/rest/reference/repos#list-organization-repositories) - [List forks](/rest/reference/repos#list-forks) - [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user) -- [List team repositories](/v3/teams/#list-team-repositories) +- [List team repositories](/rest/reference/teams#list-team-repositories) {% warning %} diff --git a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md index c395bab5a9..21dd7104f7 100644 --- a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md @@ -19,63 +19,63 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe {% data reusables.apps.metadata-permissions %} -- [`GET /`](/v3/#root-endpoint) -- [`GET /codes_of_conduct`](/v3/codes_of_conduct/#get-all-codes-of-conduct) -- [`GET /codes_of_conduct/:key`](/v3/codes_of_conduct/#get-a-code-of-conduct) -- [`GET /emojis`](/v3/emojis/#emojis) +- [`GET /`](/rest#root-endpoint) +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +- [`GET /emojis`](/rest/reference/emojis#emojis) - [`GET /feeds`](/rest/reference/activity#get-feeds) -- [`GET /licenses`](/v3/licenses/#get-all-commonly-used-licenses) -- [`GET /licenses/:key`](/v3/licenses/#get-a-license) -- [`POST /markdown`](/v3/markdown/#render-a-markdown-document) -- [`POST /markdown/raw`](/v3/markdown/#render-a-markdown-document-in-raw-mode) -- [`GET /meta`](/v3/meta/#meta) -- [`GET /organizations`](/v3/orgs/#list-organizations) -- [`GET /orgs/:org`](/v3/orgs/#get-an-organization) -- [`GET /orgs/:org/projects`](/v3/projects/#list-organization-projects) -- [`GET /orgs/:org/repos`](/v3/repos/#list-organization-repositories) -- [`GET /rate_limit`](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) -- [`GET /repos/:owner/:repo`](/v3/repos/#get-a-repository) +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license) +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +- [`GET /meta`](/rest/reference/meta#meta) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization) +- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects) +- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories) +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/community/profile`](/v3/repos/community/#get-community-profile-metrics) +- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics) {% endif %} -- [`GET /repos/:owner/:repo/contributors`](/v3/repos/#list-repository-contributors) +- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors) - [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks) -- [`GET /repos/:owner/:repo/languages`](/v3/repos/#list-repository-languages) -- [`GET /repos/:owner/:repo/license`](/v3/licenses/#get-the-license-for-a-repository) +- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository) - [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers) -- [`GET /repos/:owner/:repo/stats/code_frequency`](/v3/repos/statistics/#get-the-weekly-commit-activity) -- [`GET /repos/:owner/:repo/stats/commit_activity`](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -- [`GET /repos/:owner/:repo/stats/contributors`](/v3/repos/statistics/#get-all-contributor-commit-activity) -- [`GET /repos/:owner/:repo/stats/participation`](/v3/repos/statistics/#get-the-weekly-commit-count) -- [`GET /repos/:owner/:repo/stats/punch_card`](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity) +- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity) +- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity) +- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count) +- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) - [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers) -- [`GET /repos/:owner/:repo/tags`](/v3/repos/#list-repository-tags) -- [`GET /repos/:owner/:repo/topics`](/v3/repos#get-all-repository-topics) -- [`GET /repositories`](/v3/repos/#list-public-repositories) -- [`GET /user/repos`](/v3/repos/#list-repositories-for-the-authenticated-user) +- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) - [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) - [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) -- [`GET /users`](/v3/users/#list-users) -- [`GET /users/:username`](/v3/users/#get-a-user) -- [`GET /users/:username/followers`](/v3/users/followers/#list-followers-of-a-user) -- [`GET /users/:username/following`](/v3/users/followers/#list-the-people-a-user-follows) -- [`GET /users/:username/following/:target_user`](/v3/users/followers/#check-if-a-user-follows-another-user) -- [`GET /users/:username/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) -- [`GET /users/:username/orgs`](/v3/orgs/#list-organizations-for-a-user) +- [`GET /users`](/rest/reference/users#list-users) +- [`GET /users/:username`](/rest/reference/users#get-a-user) +- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user) - [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) - [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) -- [`GET /users/:username/repos`](/v3/repos/#list-repositories-for-a-user) +- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) _Collaborators_ -- [`GET /repos/:owner/:repo/collaborators`](/v3/repos/collaborators/#list-repository-collaborators) -- [`GET /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) +- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) +- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) _Commit comments_ -- [`GET /repos/:owner/:repo/comments`](/v3/repos/comments/#list-commit-comments-for-a-repository) -- [`GET /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#get-a-commit-comment) -- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-commit-comment) -- [`GET /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#list-commit-comments) +- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) +- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) +- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) _События_ - [`GET /events`](/rest/reference/activity#list-public-events) @@ -86,311 +86,311 @@ _События_ - [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user) _Git_ -- [`GET /gitignore/templates`](/v3/gitignore/#get-all-gitignore-templates) -- [`GET /gitignore/templates/:key`](/v3/gitignore/#get-a-gitignore-template) +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) +- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) _Keys_ -- [`GET /users/:username/keys`](/v3/users/keys/#list-public-keys-for-a-user) +- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) _Organization members_ -- [`GET /orgs/:org/members`](/v3/orgs/members/#list-organization-members) -- [`GET /orgs/:org/members/:username`](/v3/orgs/members/#check-organization-membership-for-a-user) -- [`GET /orgs/:org/public_members`](/v3/orgs/members/#list-public-organization-members) -- [`GET /orgs/:org/public_members/:username`](/v3/orgs/members/#check-public-organization-membership-for-a-user) +- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`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) _Поиск_ -- [`GET /search/code`](/v3/search/#search-code) -- [`GET /search/commits`](/v3/search/#search-commits) -- [`GET /search/issues`](/v3/search/#search-issues-and-pull-requests) -- [`GET /search/labels`](/v3/search/#search-labels) -- [`GET /search/repositories`](/v3/search/#search-repositories) -- [`GET /search/topics`](/v3/search/#search-topics) -- [`GET /search/users`](/v3/search/#search-users) +- [`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) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "actions" -- [`GET /repos/:owner/:repo/actions/artifacts`](/v3/actions/artifacts/#list-artifacts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} ### Permission on "administration" -- [`POST /orgs/:org/repos`](/v3/repos/#create-an-organization-repository) (:write) -- [`PATCH /repos/:owner/:repo`](/v3/repos/#update-a-repository) (:write) -- [`DELETE /repos/:owner/:repo`](/v3/repos/#delete-a-repository) (:write) +- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) +- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) +- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) (:read) -- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) (:write)git +- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write)git {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#enable-automated-security-fixes) (:write) +- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#disable-automated-security-fixes) (:write) +- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:write) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write) {% endif %} -- [`PUT /repos/:owner/:repo/topics`](/v3/repos/#replace-all-repository-topics) (:write) -- [`POST /repos/:owner/:repo/transfer`](/v3/repos/#transfer-a-repository) (:write) +- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write) +- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#disable-vulnerability-alerts) (:write) +- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write) {% endif %} -- [`PATCH /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#accept-a-repository-invitation) (:write) -- [`DELETE /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#decline-a-repository-invitation) (:write) +- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write) +- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write) _Branches_ -- [`GET /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#get-branch-protection) (:read) -- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#update-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#delete-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#get-admin-branch-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#set-admin-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#delete-admin-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#get-pull-request-review-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#update-pull-request-review-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#delete-pull-request-review-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#get-commit-signature-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#create-commit-signature-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#delete-commit-signature-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#get-status-checks-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#update-status-check-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#remove-status-check-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#get-all-status-check-contexts) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#add-status-check-contexts) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#set-status-check-contexts) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#remove-status-check-contexts) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#get-access-restrictions) (:read) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#delete-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#add-team-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#set-team-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#remove-team-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#add-user-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#set-user-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read) +- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Collaborators_ -- [`PUT /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#add-a-repository-collaborator) (:write) -- [`DELETE /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#remove-a-repository-collaborator) (:write) +- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) +- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) _Invitations_ -- [`GET /repos/:owner/:repo/invitations`](/v3/repos/invitations/#list-repository-invitations) (:read) -- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#update-a-repository-invitation) (:write) -- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#delete-a-repository-invitation) (:write) +- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) +- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) +- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) _Keys_ -- [`GET /repos/:owner/:repo/keys`](/v3/repos/keys/#list-deploy-keys) (:read) -- [`POST /repos/:owner/:repo/keys`](/v3/repos/keys/#create-a-deploy-key) (:write) -- [`GET /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#get-a-deploy-key) (:read) -- [`DELETE /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#delete-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) +- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) +- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) _Teams_ -- [`GET /repos/:owner/:repo/teams`](/v3/repos/#list-repository-teams) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:write) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) +- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) {% if currentVersion == "free-pro-team@latest" %} _Traffic_ -- [`GET /repos/:owner/:repo/traffic/clones`](/v3/repos/traffic/#get-repository-clones) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/paths`](/v3/repos/traffic/#get-top-referral-paths) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/v3/repos/traffic/#get-top-referral-sources) (:read) -- [`GET /repos/:owner/:repo/traffic/views`](/v3/repos/traffic/#get-page-views) (:read) +- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) +- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "blocking" -- [`GET /user/blocks`](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) (:read) -- [`GET /user/blocks/:username`](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) -- [`PUT /user/blocks/:username`](/v3/users/blocking/#block-a-user) (:write) -- [`DELETE /user/blocks/:username`](/v3/users/blocking/#unblock-a-user) (:write) +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) +- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) +- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (:write) +- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) {% endif %} ### Permission on "checks" -- [`POST /repos/:owner/:repo/check-runs`](/v3/checks/runs/#create-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#update-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`POST /repos/:owner/:repo/check-suites`](/v3/checks/suites/#create-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/v3/checks/suites/#update-repository-preferences-for-check-suites) (:write) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) +- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (:write) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) ### Permission on "contents" -- [`GET /repos/:owner/:repo/:archive_format/:ref`](/v3/repos/contents/#download-a-repository-archive) (:read) +- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:write) +- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#get-a-repository-secret) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) +- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) +- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/commits`](/v3/repos/commits/#list-commits) (:read) -- [`GET /repos/:owner/:repo/commits/:sha`](/v3/repos/commits/#get-a-commit) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/community/code_of_conduct`](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/compare/:base...:head`](/v3/repos/commits/#compare-two-commits) (:read) -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read) +- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`POST /repos/:owner/:repo/dispatches`](/v3/repos/#create-a-repository-dispatch-event) (:write) +- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:read) -- [`POST /repos/:owner/:repo/merges`](/v3/repos/merging/#merge-a-branch) (:write) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#merge-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/v3/repos/contents/#get-a-repository-readme) (:read) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read) +- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read) _Branches_ -- [`GET /repos/:owner/:repo/branches`](/v3/repos/branches/#list-branches) (:read) -- [`GET /repos/:owner/:repo/branches/:branch`](/v3/repos/branches/#get-a-branch) (:read) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#list-apps-with-access-to-the-protected-branch) (:write) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#add-app-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#set-app-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read) +- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) _Commit comments_ -- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#update-a-commit-comment) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#delete-a-commit-comment) (:write) -- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-commit-comment) (:read) -- [`POST /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#create-a-commit-comment) (:read) +- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) +- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) +- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read) _Git_ -- [`POST /repos/:owner/:repo/git/blobs`](/v3/git/blobs/#create-a-blob) (:write) -- [`GET /repos/:owner/:repo/git/blobs/:sha`](/v3/git/blobs/#get-a-blob) (:read) -- [`POST /repos/:owner/:repo/git/commits`](/v3/git/commits/#create-a-commit) (:write) -- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/v3/git/commits/#get-a-commit) (:read) -- [`POST /repos/:owner/:repo/git/refs`](/v3/git/refs/#create-a-reference) (:write) -- [`GET /repos/:owner/:repo/git/ref/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/v3/git/refs/#list-matching-references) (:read) -- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#update-a-reference) (:write) -- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#delete-a-reference) (:write) -- [`POST /repos/:owner/:repo/git/tags`](/v3/git/tags/#create-a-tag-object) (:write) -- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/v3/git/tags/#get-a-tag) (:read) -- [`POST /repos/:owner/:repo/git/trees`](/v3/git/trees/#create-a-tree) (:write) -- [`GET /repos/:owner/:repo/git/trees/:sha`](/v3/git/trees/#get-a-tree) (:read) +- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write) +- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (:read) +- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (:write) +- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (:read) +- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (:write) +- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (:read) +- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (:read) +- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (:write) +- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (:write) +- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (:write) +- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (:read) +- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (:write) +- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) {% if currentVersion == "free-pro-team@latest" %} _Импорт_ -- [`GET /repos/:owner/:repo/import`](/v3/migrations/source_imports/#get-an-import-status) (:read) -- [`PUT /repos/:owner/:repo/import`](/v3/migrations/source_imports/#start-an-import) (:write) -- [`PATCH /repos/:owner/:repo/import`](/v3/migrations/source_imports/#update-an-import) (:write) -- [`DELETE /repos/:owner/:repo/import`](/v3/migrations/source_imports/#cancel-an-import) (:write) -- [`GET /repos/:owner/:repo/import/authors`](/v3/migrations/source_imports/#get-commit-authors) (:read) -- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/v3/migrations/source_imports/#map-a-commit-author) (:write) -- [`GET /repos/:owner/:repo/import/large_files`](/v3/migrations/source_imports/#get-large-files) (:read) -- [`PATCH /repos/:owner/:repo/import/lfs`](/v3/migrations/source_imports/#update-git-lfs-preference) (:write) +- [`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) +- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (:write) +- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (:read) +- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (:write) +- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (:read) +- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) {% endif %} _Reactions_ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% endif %} _Релизы_ - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read) @@ -419,195 +419,195 @@ _Релизы_ ### Permission on "emails" {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /user/email/visibility`](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) (:write) +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) {% endif %} -- [`GET /user/emails`](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) (:read) -- [`POST /user/emails`](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) (:write) -- [`DELETE /user/emails`](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) (:write) -- [`GET /user/public_emails`](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) (:read) +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (:write) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (:write) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) {% endif %} ### Permission on "followers" -- [`GET /user/followers`](/v3/users/followers/#list-followers-of-a-user) (:read) -- [`GET /user/following`](/v3/users/followers/#list-the-people-a-user-follows) (:read) -- [`GET /user/following/:username`](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) (:read) -- [`PUT /user/following/:username`](/v3/users/followers/#follow-a-user) (:write) -- [`DELETE /user/following/:username`](/v3/users/followers/#unfollow-a-user) (:write) +- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) +- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) +- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (:read) +- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) +- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) ### Permission on "gpg keys" -- [`GET /user/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) (:read) -- [`POST /user/gpg_keys`](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) (:write) -- [`GET /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) (:read) -- [`DELETE /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (:read) +- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) ### Permission on "issues" -Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues. +Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues. -- [`GET /repos/:owner/:repo/issues`](/v3/issues/#list-repository-issues) (:read) -- [`POST /repos/:owner/:repo/issues`](/v3/issues/#create-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#get-an-issue) (:read) -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) +- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (:read) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) _Assignees_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _События_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [Get an issue event](/v3/issues/events/#get-an-issue-event) (:read) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [Get an issue event](/rest/reference/issues#get-an-issue-event) (:read) _Labels_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Milestones_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reactions_ -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} ### Permission on "keys" _Keys_ -- [`GET /user/keys`](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) (:read) -- [`POST /user/keys`](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) (:write) -- [`GET /user/keys/:key_id`](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) (:read) -- [`DELETE /user/keys/:key_id`](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) +- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) ### Permission on "members" {% if currentVersion == "free-pro-team@latest" %} -- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#list-idp-groups-for-a-team) (:write) +- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#create-or-update-idp-group-connections) (:write) +- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write) {% endif %} -- [`GET /orgs/:org/outside_collaborators`](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) (:read) -- [`PUT /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) (:write) -- [`DELETE /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) (:write) +- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read) +- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write) +- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/team-sync/groups`](/v3/teams/team_sync/#list-idp-groups-for-an-organization) (:write) +- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write) {% endif %} -- [`GET /orgs/:org/team/:team_id`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users`](/v3/scim/#list-scim-provisioned-identities) (:read) +- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /scim/v2/orgs/:org/Users`](/v3/scim/#provision-and-invite-a-scim-user) (:write) +- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#get-scim-provisioning-information-for-a-user) (:read) +- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#set-scim-information-for-a-provisioned-user) (:write) +- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#update-an-attribute-for-a-scim-user) (:write) +- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#delete-a-scim-user-from-an-organization) (:write) +- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} _Invitations_ -- [`GET /orgs/:org/invitations`](/v3/orgs/members/#list-pending-organization-invitations) (:read) -- [`POST /orgs/:org/invitations`](/v3/orgs/members/#create-an-organization-invitation) (:write) -- [`GET /orgs/:org/invitations/:invitation_id/teams`](/v3/orgs/members/#list-organization-invitation-teams) (:read) -- [`GET /teams/:team_id/invitations`](/v3/teams/members/#list-pending-team-invitations) (:read) +- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) +- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) +- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) +- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) {% endif %} _Organization members_ -- [`DELETE /orgs/:org/members/:username`](/v3/orgs/members/#remove-an-organization-member) (:write) -- [`GET /orgs/:org/memberships/:username`](/v3/orgs/members/#get-organization-membership-for-a-user) (:read) -- [`PUT /orgs/:org/memberships/:username`](/v3/orgs/members/#set-organization-membership-for-a-user) (:write) -- [`DELETE /orgs/:org/memberships/:username`](/v3/orgs/members/#remove-organization-membership-for-a-user) (:write) -- [`PUT /orgs/:org/public_members/:username`](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) (:write) -- [`DELETE /orgs/:org/public_members/:username`](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) (:write) -- [`GET /user/memberships/orgs`](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) (:read) -- [`GET /user/memberships/orgs/:org`](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) (:read) -- [`PATCH /user/memberships/orgs/:org`](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) +- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) +- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) +- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (:write) +- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (:write) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (:read) +- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) +- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) _Team members_ -- [`GET /teams/:team_id/members`](/v3/teams/members/#list-team-members) (:read) -- [`GET /teams/:team_id/memberships/:username`](/v3/teams/members/#get-team-membership-for-a-user) (:read) -- [`PUT /teams/:team_id/memberships/:username`](/v3/teams/members/#add-or-update-team-membership-for-a-user) (:write) -- [`DELETE /teams/:team_id/memberships/:username`](/v3/teams/members/#remove-team-membership-for-a-user) (:write) +- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) +- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) +- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) +- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) _Teams_ -- [`GET /orgs/:org/teams`](/v3/teams/#list-teams) (:read) -- [`POST /orgs/:org/teams`](/v3/teams/#create-a-team) (:write) -- [`GET /orgs/:org/teams/:team_slug`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) +- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) +- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -- [`GET /teams/:team_id`](/v3/teams/#get-a-team) (:read) +- [`GET /teams/:team_id`](/rest/reference/teams#get-a-team) (:read) {% endif %} -- [`PATCH /teams/:team_id`](/v3/teams/#update-a-team) (:write) -- [`DELETE /teams/:team_id`](/v3/teams/#delete-a-team) (:write) +- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write) +- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`GET /teams/:team_id/projects`](/v3/teams/#list-team-projects) (:read) -- [`GET /teams/:team_id/projects/:project_id`](/v3/teams/#check-team-permissions-for-a-project) (:read) -- [`PUT /teams/:team_id/projects/:project_id`](/v3/teams/#add-or-update-team-project-permissions) (:read) -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read) +- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read) +- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% endif %} -- [`GET /teams/:team_id/repos`](/v3/teams/#list-team-repositories) (:read) -- [`GET /teams/:team_id/repos/:owner/:repo`](/v3/teams/#check-team-permissions-for-a-repository) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:read) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) -- [`GET /teams/:team_id/teams`](/v3/teams/#list-child-teams) (:read) +- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read) +- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) +- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) ### Permission on "organization administration" -- [`PATCH /orgs/:org`](/v3/orgs/#update-an-organization) (:write) +- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/interaction-limits`](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) (:read) +- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /orgs/:org/interaction-limits`](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) (:write) +- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /orgs/:org/interaction-limits`](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) (:write) +- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) {% endif %} ### Permission on "organization hooks" @@ -620,7 +620,7 @@ _Teams_ - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write) _Teams_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permission on "organization pre receive hooks" @@ -633,31 +633,31 @@ _Teams_ ### Permission on "organization projects" -- [`POST /orgs/:org/projects`](/v3/projects/#create-an-organization-project) (:write) -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) +- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "organization user blocking" -- [`GET /orgs/:org/blocks`](/v3/orgs/blocking/#list-users-blocked-by-an-organization) (:read) -- [`GET /orgs/:org/blocks/:username`](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) (:read) -- [`PUT /orgs/:org/blocks/:username`](/v3/orgs/blocking/#block-a-user-from-an-organization) (:write) -- [`DELETE /orgs/:org/blocks/:username`](/v3/orgs/blocking/#unblock-a-user-from-an-organization) (:write) +- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) +- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) +- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (:write) +- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) {% endif %} ### Permission on "pages" @@ -675,99 +675,99 @@ _Teams_ Pull requests and issues are closely related.. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests. -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls`](/v3/pulls/#list-pull-requests) (:read) -- [`POST /repos/:owner/:repo/pulls`](/v3/pulls/#create-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#get-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#update-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#list-review-comments-on-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/v3/pulls/#list-commits-on-a-pull-request) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/v3/pulls/#list-pull-requests-files) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#check-if-a-pull-request-has-been-merged) (:read) -- [`GET /repos/:owner/:repo/pulls/comments`](/v3/pulls/comments/#list-review-comments-in-a-repository) (:read) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) (:write) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (:read) +- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (:read) +- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (:read) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) _Assignees_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _События_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [`GET /repos/:owner/:repo/issues/events/:event_id`](/v3/issues/events/#get-an-issue-event) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) _Labels_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _Milestones_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _Reactions_ -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) (:read) -- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) (:write) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read) +- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} _Requested reviewers_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) _Reviews_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#list-reviews-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#create-a-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#get-a-review-for-a-pull-request) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#update-a-review-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#delete-a-pending-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) ### Permission on "repository hooks" -- [`GET /repos/:owner/:repo/hooks`](/v3/repos/hooks/#list-repository-webhooks) (:read) -- [`POST /repos/:owner/:repo/hooks`](/v3/repos/hooks/#create-a-repository-webhook) (:write) -- [`GET /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#get-a-repository-webhook) (:read) -- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#update-a-repository-webhook) (:write) -- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#delete-a-repository-webhook) (:write) -- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/v3/repos/hooks/#ping-a-repository-webhook) (:read) -- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/v3/repos/hooks/#test-the-push-repository-webhook) (:read) +- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) +- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) +- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read) +- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write) +- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write) +- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read) +- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read) {% if enterpriseServerVersions contains currentVersion %} ### Permission on "repository pre receive hooks" @@ -780,70 +780,70 @@ _Reviews_ ### Permission on "repository projects" -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) -- [`GET /repos/:owner/:repo/projects`](/v3/projects/#list-repository-projects) (:read) -- [`POST /repos/:owner/:repo/projects`](/v3/projects/#create-a-repository-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) +- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) +- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) _Teams_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if currentVersion == "free-pro-team@latest" %} ### Permission on "secrets" -* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:read) -* [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:read) -* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#get-a-repository-secret) (:read) -* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -* [`GET /orgs/:org/actions/secrets/public-key`](/v3/actions/secrets/#get-an-organization-public-key) (:read) -* [`GET /orgs/:org/actions/secrets`](/v3/actions/secrets/#list-organization-secrets) (:read) -* [`GET /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#get-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-an-organization-secret) (:write) -* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) (:write) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-an-organization-secret) (:write) +* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) +* [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) +* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (:read) +* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (:write) +* [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (:read) +* [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (:read) +* [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (:write) +* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (:write) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "security events" -- [`GET /repos/:owner/:repo/code-scanning/alerts`](/v3/code-scanning/#list-code-scanning-alerts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/v3/code-scanning/#get-a-code-scanning-alert) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### Permission on "self-hosted runners" -- [`GET /orgs/:org/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) (:write) -- [`GET /orgs/:org/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) (:read) -- [`GET /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) (:write) -- [`DELETE /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) +- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) +- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) {% endif %} ### Permission on "single file" -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -- [`PUT /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#create-or-update-file-contents) (:write) -- [`DELETE /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#delete-a-file) (:write) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) +- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) ### Permission on "starring" @@ -853,23 +853,23 @@ _Teams_ ### Permission on "statuses" -- [`GET /repos/:owner/:repo/commits/:ref/status`](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/v3/repos/statuses/#list-commit-statuses-for-a-reference) (:read) -- [`POST /repos/:owner/:repo/statuses/:sha`](/v3/repos/statuses/#create-a-commit-status) (:write) +- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) +- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) ### Permission on "team discussions" -- [`GET /teams/:team_id/discussions`](/v3/teams/discussions/#list-discussions) (:read) -- [`POST /teams/:team_id/discussions`](/v3/teams/discussions/#create-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#get-a-discussion) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#update-a-discussion) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#delete-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#list-discussion-comments) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#create-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#get-a-discussion-comment) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#update-a-discussion-comment) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#delete-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion-comment) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion) (:write) +- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) +- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/ru-RU/content/rest/reference/pulls.md b/translations/ru-RU/content/rest/reference/pulls.md index c6addaf6bf..c10ba9fee1 100644 --- a/translations/ru-RU/content/rest/reference/pulls.md +++ b/translations/ru-RU/content/rest/reference/pulls.md @@ -10,7 +10,7 @@ versions: 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](/v3/issues). +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 @@ -33,16 +33,16 @@ If a diff is corrupt, contact {% data variables.contact.contact_support %}. Incl 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. | -| `проблема` | The API location of this Pull Request's [Issue](/v3/issues/). | -| `комментарии` | The API location of this Pull Request's [Issue comments](/v3/issues/comments/). | -| `review_comments` | The API location of this Pull Request's [Review comments](/v3/pulls/comments/). | -| `review_comment` | The [URL template](/v3/#hypermedia) to construct the API location for a [Review comment](/v3/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](/v3/repos/statuses/), which are the statuses of its `head` branch. | +| Name | Description | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `self` | The API location of this Pull Request. | +| `html` | The HTML location of this Pull Request. | +| `проблема` | The API location of this Pull Request's [Issue](/rest/reference/issues). | +| `комментарии` | 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/repos#statuses), which are the statuses of its `head` branch. | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/ru-RU/content/rest/reference/rate-limit.md b/translations/ru-RU/content/rest/reference/rate-limit.md index b81dff0260..7c33a37028 100644 --- a/translations/ru-RU/content/rest/reference/rate-limit.md +++ b/translations/ru-RU/content/rest/reference/rate-limit.md @@ -13,18 +13,18 @@ The REST API overview documentation describes the [rate limit rules](/rest/overv ### Understanding your rate limit status -The Search API has a [custom rate limit](/v3/search/#rate-limit), separate from the rate limit governing the rest of the REST API. The GraphQL API also has a [custom rate limit](/v4/guides/resource-limitations/#rate-limit) that is separate from and calculated differently than rate limits in the REST API. +The Search API has a [custom rate limit](/rest/reference/search#rate-limit), separate from the rate limit governing the rest of the REST API. The GraphQL API also has a [custom rate limit](/graphql/overview/resource-limitations#rate-limit) that is separate from and calculated differently than rate limits in the REST API. For these reasons, the Rate Limit API response categorizes your rate limit. Under `resources`, you'll see four objects: * The `core` object provides your rate limit status for all non-search-related resources in the REST API. -* The `search` object provides your rate limit status for the [Search API](/v3/search/). +* The `search` object provides your rate limit status for the [Search API](/rest/reference/search). -* The `graphql` object provides your rate limit status for the [GraphQL API](/v4/). +* The `graphql` object provides your rate limit status for the [GraphQL API](/graphql). * The `integration_manifest` object provides your rate limit status for the [GitHub App Manifest code conversion](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration) endpoint. -For more information on the headers and values in the rate limit response, see "[Rate limiting](/v3/#rate-limiting)." +For more information on the headers and values in the rate limit response, see "[Rate limiting](/rest#rate-limiting)." {% include rest_operations_at_current_path %} diff --git a/translations/ru-RU/content/rest/reference/repos.md b/translations/ru-RU/content/rest/reference/repos.md index 04d6edfdbf..f779c766b2 100644 --- a/translations/ru-RU/content/rest/reference/repos.md +++ b/translations/ru-RU/content/rest/reference/repos.md @@ -29,7 +29,7 @@ versions: ### Custom media types for commit comments -These are the supported media types for commit comments. You can read more about the use of media types in the API [here](/v3/media/). +These are the supported media types for commit comments. You can read more about the use of media types in the API [here](/rest/overview/media-types). application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json @@ -65,7 +65,7 @@ These API endpoints let you create, modify, and delete Base64 encoded content in ### Custom media types for repository contents -[READMEs](/v3/repos/contents/#get-a-repository-readme), [files](/v3/repos/contents/#get-repository-content), and [symlinks](/v3/repos/contents/#get-repository-content) support the following custom media types: +[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 @@ -74,13 +74,13 @@ 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](/v3/repos/contents/#get-repository-content) support the following custom media type: +[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](/v3/media/). +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 %} diff --git a/translations/ru-RU/content/rest/reference/scim.md b/translations/ru-RU/content/rest/reference/scim.md index 5a481b5139..fa43642571 100644 --- a/translations/ru-RU/content/rest/reference/scim.md +++ b/translations/ru-RU/content/rest/reference/scim.md @@ -12,7 +12,7 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/v3/auth/#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." {% endnote %} diff --git a/translations/ru-RU/content/rest/reference/search.md b/translations/ru-RU/content/rest/reference/search.md index ac5b70081c..a17f2d1c3d 100644 --- a/translations/ru-RU/content/rest/reference/search.md +++ b/translations/ru-RU/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**. -You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/v3/search/#constructing-a-search-query)." +You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." ### Ranking search results @@ -18,7 +18,7 @@ Unless another sort option is provided as a query parameter, results are sorted ### Rate limit -The Search API has a custom rate limit. For requests using [Basic Authentication](/v3/#authentication), [OAuth](/v3/#authentication), or [client ID and secret](/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute. +The Search API has a custom rate limit. For requests using [Basic Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute. {% data reusables.enterprise.rate_limit %} diff --git a/translations/ru-RU/content/rest/reference/teams.md b/translations/ru-RU/content/rest/reference/teams.md index a39f3abce4..7223e949ec 100644 --- a/translations/ru-RU/content/rest/reference/teams.md +++ b/translations/ru-RU/content/rest/reference/teams.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -This API is only available to authenticated members of the team's [organization](/v3/orgs). OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} generates the team's `slug` from the team `name`. +This API is only available to authenticated members of the team's [organization](/rest/reference/orgs). OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} generates the team's `slug` from the team `name`. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -16,7 +16,7 @@ This API is only available to authenticated members of the team's [organization] ## Discussions -The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/v3/orgs) can create and read public discussion posts. For more details, see "[About team discussions](/articles/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/v3/teams/discussion_comments). This API is only available to authenticated members of the team's organization. +The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](/articles/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -24,7 +24,7 @@ The team discussions API allows you to get, create, edit, and delete discussion ## Discussion comments -The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/v3/teams/discussions) post. Any member of the team's [organization](/v3/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/articles/about-team-discussions/)." This API is only available to authenticated members of the team's organization. +The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/articles/about-team-discussions/)." This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -58,4 +58,4 @@ You can manage GitHub team members through your IdP with team synchronization. T {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ru-RU/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/ru-RU/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 10f9989a12..3d4deaabeb 100644 --- a/translations/ru-RU/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/ru-RU/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.' reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/ru-RU/data/graphql/graphql_upcoming_changes.public.yml b/translations/ru-RU/data/graphql/graphql_upcoming_changes.public.yml index f12ecd0331..2b5e3ec561 100644 --- a/translations/ru-RU/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ru-RU/data/graphql/graphql_upcoming_changes.public.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.' reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/ru-RU/data/reusables/apps/app-ruby-guides.md b/translations/ru-RU/data/reusables/apps/app-ruby-guides.md index fe649b0de5..19a860b9e9 100644 --- a/translations/ru-RU/data/reusables/apps/app-ruby-guides.md +++ b/translations/ru-RU/data/reusables/apps/app-ruby-guides.md @@ -1,5 +1,5 @@ {% note %} -**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/v3/libraries/). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. +**Note:** This guide demonstrates the app development process using the Ruby programming language. However, there are many [flavors of Octokit](/rest/overview/libraries). If you prefer JavaScript, you can use [Probot](https://probot.github.io/) and [Node.js](https://octokit.github.io/rest.js/) to develop GitHub Apps. {% endnote %} diff --git a/translations/ru-RU/data/reusables/apps/checks-availability.md b/translations/ru-RU/data/reusables/apps/checks-availability.md index 7360c3112d..441b6cc35b 100644 --- a/translations/ru-RU/data/reusables/apps/checks-availability.md +++ b/translations/ru-RU/data/reusables/apps/checks-availability.md @@ -1 +1 @@ -Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/v3/repos/statuses/). +Write permission for the Checks API is only available to GitHub Apps. OAuth Apps and authenticated users can view check runs and check suites, but they are not able to create them. If you aren't building a GitHub App, you might be interested in the [Statuses API](/rest/reference/repos#statuses). diff --git a/translations/ru-RU/data/reusables/apps/deletes_ssh_keys.md b/translations/ru-RU/data/reusables/apps/deletes_ssh_keys.md index 6b5e91b011..c1a3e41f10 100644 --- a/translations/ru-RU/data/reusables/apps/deletes_ssh_keys.md +++ b/translations/ru-RU/data/reusables/apps/deletes_ssh_keys.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/v3/guides/managing-deploy-keys/#deploy-keys). +**Warning**: Revoking all permission from an {% data variables.product.prodname_oauth_app %} deletes any SSH keys the application generated on behalf of the user, including [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys). {% endwarning %} diff --git a/translations/ru-RU/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/ru-RU/data/reusables/apps/deprecating_auth_with_query_parameters.md index 07fd7f5941..26ea19355f 100644 --- a/translations/ru-RU/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/ru-RU/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/v3/auth/#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). +**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} diff --git a/translations/ru-RU/data/reusables/apps/deprecating_github_services_ghe.md b/translations/ru-RU/data/reusables/apps/deprecating_github_services_ghe.md index 72e5d399fb..b44e17370a 100644 --- a/translations/ru-RU/data/reusables/apps/deprecating_github_services_ghe.md +++ b/translations/ru-RU/data/reusables/apps/deprecating_github_services_ghe.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} {% note %} -**Note:** GitHub Enterprise release 2.17 and higher no longer allows admins to install new GitHub Services, and existing services will stop working in GitHub Enterprise release 2.20 and higher. You can use the [Replacing GitHub Services guide](/v3/guides/replacing-github-services) to help you update your services to webhooks. +**Note:** GitHub Enterprise release 2.17 and higher no longer allows admins to install new GitHub Services, and existing services will stop working in GitHub Enterprise release 2.20 and higher. You can use the [Replacing GitHub Services guide](/developers/overview/replacing-github-services) to help you update your services to webhooks. {% endnote %} {% endif %} diff --git a/translations/ru-RU/data/reusables/code-scanning/example-configuration-files.md b/translations/ru-RU/data/reusables/code-scanning/example-configuration-files.md index 940d94e8d4..f429bb12cf 100644 --- a/translations/ru-RU/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/ru-RU/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), and to exclude the _node_modules_ directory (also relative to the root), as well as any file whose name ends in _.test.js_. +The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. ``` yaml name: "My {% data variables.product.prodname_codeql %} config" @@ -24,9 +24,9 @@ queries: - name: Use a query suite file (run queries from a query suite in this repo) uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls -paths-ignore: - - node_modules - - '**/*.test.js' paths: - src +paths-ignore: + - src/node_modules + - '**/*.test.js' ``` diff --git a/translations/ru-RU/data/reusables/github-actions/matrix-variable-example.md b/translations/ru-RU/data/reusables/github-actions/matrix-variable-example.md new file mode 100644 index 0000000000..ce6e9d6d24 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/matrix-variable-example.md @@ -0,0 +1,26 @@ +In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: + +{% raw %} +```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - node-version: 10.x + site: "prod" + datacenter: "site-a" + - node-version: 12.x + site: "dev" + datacenter: "site-b" + steps: + - name: Echo site details + env: + SITE: ${{ matrix.site }} + DATACENTER: ${{ matrix.datacenter }} + run: echo $SITE $DATACENTER +``` +{% endraw %} diff --git a/translations/ru-RU/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/ru-RU/data/reusables/github-actions/permissions-statement-secrets-api.md index 0e62bb6498..53142b325e 100644 --- a/translations/ru-RU/data/reusables/github-actions/permissions-statement-secrets-api.md +++ b/translations/ru-RU/data/reusables/github-actions/permissions-statement-secrets-api.md @@ -1 +1 @@ -To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/v3/actions/secrets/)." +To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)." diff --git a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 9ac93498fa..0632ee2cdc 100644 --- a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,12 +1,12 @@ -1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. - ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. {% warning %} - **Warning** + **Предупреждение** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} - diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 8cb48608dd..125c285ead 100644 --- a/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/v3/teams/team_sync/)." +After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/ru-RU/data/reusables/issue-events/issue-event-common-properties.md b/translations/ru-RU/data/reusables/issue-events/issue-event-common-properties.md index 845712722f..e0c9b69747 100644 --- a/translations/ru-RU/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/ru-RU/data/reusables/issue-events/issue-event-common-properties.md @@ -1,10 +1,10 @@ -| Name | Тип | Description | -| ------------ | --------- | -------------------------------------------------------------------- | -| `id` | `integer` | The unique identifier of the event. | -| `node_id` | `строка` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `строка` | The REST API URL for fetching the event. | -| `actor` | `объект` | The person who generated the event. | -| `событие` | `строка` | Identifies the actual type of event that occurred. | -| `commit_id` | `строка` | The SHA of the commit that referenced this issue. | -| `commit_url` | `строка` | The GitHub REST API link to the commit that referenced this issue. | -| `created_at` | `строка` | The timestamp indicating when the event occurred. | +| Name | Тип | Description | +| ------------ | --------- | ------------------------------------------------------------------------- | +| `id` | `integer` | The unique identifier of the event. | +| `node_id` | `строка` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `строка` | The REST API URL for fetching the event. | +| `actor` | `объект` | The person who generated the event. | +| `событие` | `строка` | Identifies the actual type of event that occurred. | +| `commit_id` | `строка` | The SHA of the commit that referenced this issue. | +| `commit_url` | `строка` | The GitHub REST API link to the commit that referenced this issue. | +| `created_at` | `строка` | The timestamp indicating when the event occurred. | diff --git a/translations/ru-RU/data/reusables/pre-release-program/corsair-preview.md b/translations/ru-RU/data/reusables/pre-release-program/corsair-preview.md index d5131c62d3..7724c1caaf 100644 --- a/translations/ru-RU/data/reusables/pre-release-program/corsair-preview.md +++ b/translations/ru-RU/data/reusables/pre-release-program/corsair-preview.md @@ -1,6 +1,6 @@ {% note %} -**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.corsair-preview+json diff --git a/translations/ru-RU/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/ru-RU/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md index 6bf0fb2ed4..7bed2bb577 100644 --- a/translations/ru-RU/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md +++ b/translations/ru-RU/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Note:** Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)." For more information, see "[Expiring user-to-server access tokens for GitHub Apps](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)." diff --git a/translations/ru-RU/data/reusables/pre-release-program/fury-pre-release.md b/translations/ru-RU/data/reusables/pre-release-program/fury-pre-release.md index 25b74a97ea..adf434c97e 100644 --- a/translations/ru-RU/data/reusables/pre-release-program/fury-pre-release.md +++ b/translations/ru-RU/data/reusables/pre-release-program/fury-pre-release.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} {% note %} -**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** {% data variables.product.prodname_github_app %} Manifests are currently available for developers to preview. To access this API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.fury-preview+json diff --git a/translations/ru-RU/data/reusables/pre-release-program/machine-man-preview.md b/translations/ru-RU/data/reusables/pre-release-program/machine-man-preview.md index d18399b663..82549b4331 100644 --- a/translations/ru-RU/data/reusables/pre-release-program/machine-man-preview.md +++ b/translations/ru-RU/data/reusables/pre-release-program/machine-man-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** To access the API with your GitHub App, you must provide a custom [media type](/v3/media) in the `Accept` Header for your requests. +**Note:** To access the API with your GitHub App, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` Header for your requests. `application/vnd.github.machine-man-preview+json` diff --git a/translations/ru-RU/data/reusables/pre-release-program/sailor-v-preview.md b/translations/ru-RU/data/reusables/pre-release-program/sailor-v-preview.md index fcf2e98e68..ac0d210355 100644 --- a/translations/ru-RU/data/reusables/pre-release-program/sailor-v-preview.md +++ b/translations/ru-RU/data/reusables/pre-release-program/sailor-v-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/v3/media) in the `Accept` header: +**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.sailor-v-preview+json diff --git a/translations/ru-RU/data/reusables/pre-release-program/starfox-preview.md b/translations/ru-RU/data/reusables/pre-release-program/starfox-preview.md index 5de305adb6..138455a9eb 100644 --- a/translations/ru-RU/data/reusables/pre-release-program/starfox-preview.md +++ b/translations/ru-RU/data/reusables/pre-release-program/starfox-preview.md @@ -2,7 +2,7 @@ **Note:** Project card details are now shown in REST API responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events). -To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/v3/media) in the `Accept` header: +To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: ``` application/vnd.github.starfox-preview+json diff --git a/translations/ru-RU/data/reusables/repositories/deploy-keys.md b/translations/ru-RU/data/reusables/repositories/deploy-keys.md index ae039b459e..3f3948dc84 100644 --- a/translations/ru-RU/data/reusables/repositories/deploy-keys.md +++ b/translations/ru-RU/data/reusables/repositories/deploy-keys.md @@ -1 +1 @@ -You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/v3/guides/delivering-deployments/)." +You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)." diff --git a/translations/ru-RU/data/reusables/webhooks/check_run_properties.md b/translations/ru-RU/data/reusables/webhooks/check_run_properties.md index 175bc993cf..87f2509a1e 100644 --- a/translations/ru-RU/data/reusables/webhooks/check_run_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/check_run_properties.md @@ -1,7 +1,7 @@ | Клавиша | Тип | Description | | --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `действие` | `строка` | The action performed. Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/v3/checks/runs/#check-runs-and-requested-actions)."
| -| `check_run` | `объект` | The [check_run](/v3/checks/runs/#get-a-check-run). | +| `действие` | `строка` | The action performed. Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `check_run` | `объект` | The [check_run](/rest/reference/checks#get-a-check-run). | | `check_run[status]` | `строка` | The current status of the check run. Can be `queued`, `in_progress`, or `completed`. | | `check_run[conclusion]` | `строка` | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. | | `check_run[name]` | `строка` | The name of the check run. | diff --git a/translations/ru-RU/data/reusables/webhooks/check_run_short_desc.md b/translations/ru-RU/data/reusables/webhooks/check_run_short_desc.md index 19fd0846b8..15cbbb7936 100644 --- a/translations/ru-RU/data/reusables/webhooks/check_run_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/check_run_short_desc.md @@ -1 +1 @@ -Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/v3/checks/runs/)" REST API. +Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/rest/reference/checks#runs)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/check_suite_properties.md b/translations/ru-RU/data/reusables/webhooks/check_suite_properties.md index 01f3e8c405..352cf4c64a 100644 --- a/translations/ru-RU/data/reusables/webhooks/check_suite_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/check_suite_properties.md @@ -1,7 +1,7 @@ | Клавиша | Тип | Description | | ---------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `действие` | `строка` | The action performed. Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/v3/checks/runs/#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| -| `check_suite` | `объект` | The [check_suite](/v3/checks/suites/). | +| `действие` | `строка` | The action performed. Can be:
  • `completed` - All check runs in a check suite have completed.
  • `requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.
| +| `check_suite` | `объект` | The [check_suite](/rest/reference/checks#suites). | | `check_suite[head_branch]` | `строка` | The head branch name the changes are on. | | `check_suite[head_sha]` | `строка` | The SHA of the most recent commit for this check suite. | | `check_suite[status]` | `строка` | The summary status for all check runs that are part of the check suite. Can be `requested`, `in_progress`, or `completed`. | diff --git a/translations/ru-RU/data/reusables/webhooks/check_suite_short_desc.md b/translations/ru-RU/data/reusables/webhooks/check_suite_short_desc.md index 00c4c00937..94ed6dc937 100644 --- a/translations/ru-RU/data/reusables/webhooks/check_suite_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/check_suite_short_desc.md @@ -1 +1 @@ -Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/v3/checks/suites/)" REST API. +Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/rest/reference/checks#suites)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/commit_comment_properties.md b/translations/ru-RU/data/reusables/webhooks/commit_comment_properties.md index 80abdd2789..1b7b5da7ef 100644 --- a/translations/ru-RU/data/reusables/webhooks/commit_comment_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/commit_comment_properties.md @@ -1,4 +1,4 @@ -| Клавиша | Тип | Description | -| ------------- | -------- | ------------------------------------------------------------------------ | -| `действие` | `строка` | The action performed. Can be `created`. | -| `комментарий` | `объект` | The [commit comment](/v3/repos/comments/#get-a-commit-comment) resource. | +| Клавиша | Тип | Description | +| ------------- | -------- | -------------------------------------------------------------------------- | +| `действие` | `строка` | The action performed. Can be `created`. | +| `комментарий` | `объект` | The [commit comment](/rest/reference/repos#get-a-commit-comment) resource. | diff --git a/translations/ru-RU/data/reusables/webhooks/commit_comment_short_desc.md b/translations/ru-RU/data/reusables/webhooks/commit_comment_short_desc.md index 20e258a1ea..7329b1ed61 100644 --- a/translations/ru-RU/data/reusables/webhooks/commit_comment_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/commit_comment_short_desc.md @@ -1 +1 @@ -A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/v3/repos/comments/)" REST API. +A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/rest/reference/repos#comments)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/create_properties.md b/translations/ru-RU/data/reusables/webhooks/create_properties.md index 1e5141b957..5442d3ca8a 100644 --- a/translations/ru-RU/data/reusables/webhooks/create_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/create_properties.md @@ -1,6 +1,6 @@ | Клавиша | Тип | Description | | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `строка` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | +| `ref` | `строка` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | | `ref_type` | `строка` | The type of Git ref object created in the repository. Can be either `branch` or `tag`. | | `master_branch` | `строка` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" %}`main`{% else %}`master`{% endif %}). | | `описание` | `строка` | The repository's current description. | diff --git a/translations/ru-RU/data/reusables/webhooks/create_short_desc.md b/translations/ru-RU/data/reusables/webhooks/create_short_desc.md index a43ab39943..5cf906a338 100644 --- a/translations/ru-RU/data/reusables/webhooks/create_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/create_short_desc.md @@ -1 +1 @@ -A Git branch or tag is created. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is created. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/delete_properties.md b/translations/ru-RU/data/reusables/webhooks/delete_properties.md index 0b1055fa4a..97dce458aa 100644 --- a/translations/ru-RU/data/reusables/webhooks/delete_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ | Клавиша | Тип | Description | | ---------- | -------- | ------------------------------------------------------------------------------ | -| `ref` | `строка` | The [`git ref`](/v3/git/refs/#get-a-reference) resource. | +| `ref` | `строка` | The [`git ref`](/rest/reference/git#get-a-reference) resource. | | `ref_type` | `строка` | The type of Git ref oject deleted in the repository. Can be `branch` or `tag`. | diff --git a/translations/ru-RU/data/reusables/webhooks/delete_short_desc.md b/translations/ru-RU/data/reusables/webhooks/delete_short_desc.md index 7557d8e4ed..726e68df82 100644 --- a/translations/ru-RU/data/reusables/webhooks/delete_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/delete_short_desc.md @@ -1 +1 @@ -A Git branch or tag is deleted. For more information, see the "[Git data](/v3/git/)" REST API. +A Git branch or tag is deleted. For more information, see the "[Git data](/rest/reference/git)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/deploy_key_properties.md b/translations/ru-RU/data/reusables/webhooks/deploy_key_properties.md index 6e445bc624..6c5b485126 100644 --- a/translations/ru-RU/data/reusables/webhooks/deploy_key_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/deploy_key_properties.md @@ -1,4 +1,4 @@ -| Клавиша | Тип | Description | -| ---------- | -------- | -------------------------------------------------------------- | -| `действие` | `строка` | The action performed. Can be either `created` or `deleted`. | -| `клавиша` | `объект` | The [`deploy key`](/v3/repos/keys/#get-a-deploy-key) resource. | +| Клавиша | Тип | Description | +| ---------- | -------- | -------------------------------------------------------------------- | +| `действие` | `строка` | The action performed. Can be either `created` or `deleted`. | +| `клавиша` | `объект` | The [`deploy key`](/rest/reference/repos#get-a-deploy-key) resource. | diff --git a/translations/ru-RU/data/reusables/webhooks/deploy_key_short_desc.md b/translations/ru-RU/data/reusables/webhooks/deploy_key_short_desc.md index c83fe68579..1d4565e788 100644 --- a/translations/ru-RU/data/reusables/webhooks/deploy_key_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/deploy_key_short_desc.md @@ -1 +1 @@ -A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/v3/repos/keys/)" REST API. +A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/rest/reference/repos#keys)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/fork_properties.md b/translations/ru-RU/data/reusables/webhooks/fork_properties.md index c4301b8dfe..deb7484b44 100644 --- a/translations/ru-RU/data/reusables/webhooks/fork_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/fork_properties.md @@ -1,3 +1,3 @@ -| Клавиша | Тип | Description | -| -------- | -------- | ----------------------------------------------------------------- | -| `forkee` | `объект` | The created [`repository`](/v3/repos/#get-a-repository) resource. | +| Клавиша | Тип | Description | +| -------- | -------- | ---------------------------------------------------------------------------- | +| `forkee` | `объект` | The created [`repository`](/rest/reference/repos#get-a-repository) resource. | diff --git a/translations/ru-RU/data/reusables/webhooks/fork_short_desc.md b/translations/ru-RU/data/reusables/webhooks/fork_short_desc.md index 60f88625b0..23b9eff136 100644 --- a/translations/ru-RU/data/reusables/webhooks/fork_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/fork_short_desc.md @@ -1 +1 @@ -A user forks a repository. For more information, see the "[forks](/v3/repos/forks/)" REST API. +A user forks a repository. For more information, see the "[forks](/rest/reference/repos#forks)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/ru-RU/data/reusables/webhooks/installation_repositories_short_desc.md index 63166ba6e2..f1debb10f2 100644 --- a/translations/ru-RU/data/reusables/webhooks/installation_repositories_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/installation_repositories_short_desc.md @@ -1 +1 @@ -Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/installation_short_desc.md b/translations/ru-RU/data/reusables/webhooks/installation_short_desc.md index 4abc1de643..21cffb5f50 100644 --- a/translations/ru-RU/data/reusables/webhooks/installation_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/installation_short_desc.md @@ -1 +1 @@ -Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/v3/apps/)" REST API. +Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/issue_comment_properties.md b/translations/ru-RU/data/reusables/webhooks/issue_comment_properties.md index b983deb16f..5a93e1a350 100644 --- a/translations/ru-RU/data/reusables/webhooks/issue_comment_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/issue_comment_properties.md @@ -1 +1 @@ -`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | The previous version of the body if the action was `edited`. `issue`|`object` | The [issue](/v3/issues/) the comment belongs to. `comment`|`object` | The [comment](/v3/issues/comments/) itself. +`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | The previous version of the body if the action was `edited`. `issue`|`object` | The [issue](/rest/reference/issues) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/issues#comments) itself. diff --git a/translations/ru-RU/data/reusables/webhooks/issue_comment_short_desc.md b/translations/ru-RU/data/reusables/webhooks/issue_comment_short_desc.md index cc07764d19..dd67c3de2d 100644 --- a/translations/ru-RU/data/reusables/webhooks/issue_comment_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/issue_comment_short_desc.md @@ -1 +1 @@ -Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/v3/issues/comments/)" REST API. +Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/rest/reference/issues#comments)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/issue_properties.md b/translations/ru-RU/data/reusables/webhooks/issue_properties.md index c146faa968..bff204fc72 100644 --- a/translations/ru-RU/data/reusables/webhooks/issue_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/issue_properties.md @@ -1 +1 @@ -`issue`|`object` | The [issue](/v3/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. +`issue`|`object` | The [issue](/rest/reference/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue. diff --git a/translations/ru-RU/data/reusables/webhooks/issues_short_desc.md b/translations/ru-RU/data/reusables/webhooks/issues_short_desc.md index 7dadec073b..3edc02859f 100644 --- a/translations/ru-RU/data/reusables/webhooks/issues_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/issues_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/v3/issues/comments/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/rest/reference/issues#comments)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/label_short_desc.md b/translations/ru-RU/data/reusables/webhooks/label_short_desc.md index c5f7178d8a..a634b7faa7 100644 --- a/translations/ru-RU/data/reusables/webhooks/label_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/label_short_desc.md @@ -1 +1 @@ -Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/v3/issues/labels/)" REST API. +Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/rest/reference/issues#labels)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/member_properties.md b/translations/ru-RU/data/reusables/webhooks/member_properties.md index d9e1757f40..add035dc19 100644 --- a/translations/ru-RU/data/reusables/webhooks/member_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/member_properties.md @@ -1 +1 @@ -`member`|`object` | The [user](/v3/users/) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. +`member`|`object` | The [user](/rest/reference/users) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`. diff --git a/translations/ru-RU/data/reusables/webhooks/member_short_desc.md b/translations/ru-RU/data/reusables/webhooks/member_short_desc.md index 2e82896773..b664392fdf 100644 --- a/translations/ru-RU/data/reusables/webhooks/member_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/member_short_desc.md @@ -1 +1 @@ -Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/v3/repos/collaborators/)" REST API. +Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/rest/reference/repos#collaborators)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/membership_properties.md b/translations/ru-RU/data/reusables/webhooks/membership_properties.md index 71701a5425..d914801684 100644 --- a/translations/ru-RU/data/reusables/webhooks/membership_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/membership_properties.md @@ -1,6 +1,6 @@ -| Клавиша | Тип | Description | -| ---------- | -------- | ----------------------------------------------------------- | -| `действие` | `строка` | The action that was performed. Can be `added` or `removed`. | -| `область` | `строка` | The scope of the membership. Currently, can only be `team`. | -| `участник` | `объект` | The [user](/v3/users/) that was added or removed. | -| `команда` | `объект` | The [team](/v3/teams/) for the membership. | +| Клавиша | Тип | Description | +| ---------- | -------- | ------------------------------------------------------------ | +| `действие` | `строка` | The action that was performed. Can be `added` or `removed`. | +| `область` | `строка` | The scope of the membership. Currently, can only be `team`. | +| `участник` | `объект` | The [user](/rest/reference/users) that was added or removed. | +| `команда` | `объект` | The [team](/rest/reference/teams) for the membership. | diff --git a/translations/ru-RU/data/reusables/webhooks/membership_short_desc.md b/translations/ru-RU/data/reusables/webhooks/membership_short_desc.md index e557eea902..f7867d25a9 100644 --- a/translations/ru-RU/data/reusables/webhooks/membership_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/membership_short_desc.md @@ -1 +1 @@ -Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/v3/teams/members/)" REST API. +Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/rest/reference/teams#members)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/milestone_short_desc.md b/translations/ru-RU/data/reusables/webhooks/milestone_short_desc.md index 6b6bd073ce..c9edf73236 100644 --- a/translations/ru-RU/data/reusables/webhooks/milestone_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/milestone_short_desc.md @@ -1 +1 @@ -Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/v3/issues/milestones/)" REST API. +Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/rest/reference/issues#milestones)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/org_block_short_desc.md b/translations/ru-RU/data/reusables/webhooks/org_block_short_desc.md index 7c3896f63c..f75660fcdb 100644 --- a/translations/ru-RU/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/v3/orgs/blocking/)" REST API. +Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/org_desc.md b/translations/ru-RU/data/reusables/webhooks/org_desc.md index 8b344e764c..90d218b876 100644 --- a/translations/ru-RU/data/reusables/webhooks/org_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/org_desc.md @@ -1 +1 @@ -`organization` | `object` | Webhook payloads contain the [`organization`](/v3/orgs/#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. +`organization` | `object` | Webhook payloads contain the [`organization`](/rest/reference/orgs#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. diff --git a/translations/ru-RU/data/reusables/webhooks/organization_short_desc.md b/translations/ru-RU/data/reusables/webhooks/organization_short_desc.md index 895b584aaf..0b539ee364 100644 --- a/translations/ru-RU/data/reusables/webhooks/organization_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/organization_short_desc.md @@ -1 +1 @@ -Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/v3/orgs/)" REST API. +Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/rest/reference/orgs)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/project_card_properties.md b/translations/ru-RU/data/reusables/webhooks/project_card_properties.md index d205b443db..2f39350d4d 100644 --- a/translations/ru-RU/data/reusables/webhooks/project_card_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/project_card_properties.md @@ -4,4 +4,4 @@ | `changes` | `объект` | The changes to the project card if the action was `edited` or `converted`. | | `changes[note][from]` | `строка` | The previous version of the note if the action was `edited` or `converted`. | | `after_id` | `integer` | The id of the card that this card now follows if the action was "moved". Will be `null` if it is the first card in a column. | -| `project_card` | `объект` | The [project card](/v3/projects/cards) itself. | +| `project_card` | `объект` | The [project card](/rest/reference/projects#cards) itself. | diff --git a/translations/ru-RU/data/reusables/webhooks/project_card_short_desc.md b/translations/ru-RU/data/reusables/webhooks/project_card_short_desc.md index bbea9ea6c4..6fe2904d9e 100644 --- a/translations/ru-RU/data/reusables/webhooks/project_card_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/project_card_short_desc.md @@ -1 +1 @@ -Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/v3/projects/cards)" REST API. +Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/project_column_properties.md b/translations/ru-RU/data/reusables/webhooks/project_column_properties.md index 2d5af9fa19..0af9e24c0c 100644 --- a/translations/ru-RU/data/reusables/webhooks/project_column_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/project_column_properties.md @@ -4,4 +4,4 @@ | `changes` | `объект` | The changes to the project column if the action was `edited`. | | `changes[name][from]` | `строка` | The previous version of the name if the action was `edited`. | | `after_id` | `integer` | The id of the column that this column now follows if the action was "moved". Will be `null` if it is the first column in a project. | -| `project_column` | `объект` | The [project column](/v3/projects/columns) itself. | +| `project_column` | `объект` | The [project column](/rest/reference/projects#columns) itself. | diff --git a/translations/ru-RU/data/reusables/webhooks/project_column_short_desc.md b/translations/ru-RU/data/reusables/webhooks/project_column_short_desc.md index 19ac3f6412..35d38e4101 100644 --- a/translations/ru-RU/data/reusables/webhooks/project_column_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/project_column_short_desc.md @@ -1 +1 @@ -Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/v3/projects/columns)" REST API. +Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/project_properties.md b/translations/ru-RU/data/reusables/webhooks/project_properties.md index 20495d4508..08ce98c883 100644 --- a/translations/ru-RU/data/reusables/webhooks/project_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/project_properties.md @@ -4,4 +4,4 @@ | `changes` | `объект` | The changes to the project if the action was `edited`. | | `changes[name][from]` | `строка` | The previous version of the name if the action was `edited`. | | `changes[body][from]` | `строка` | The previous version of the body if the action was `edited`. | -| `проект` | `объект` | The [project](/v3/projects/) itself. | +| `проект` | `объект` | The [project](/rest/reference/projects) itself. | diff --git a/translations/ru-RU/data/reusables/webhooks/project_short_desc.md b/translations/ru-RU/data/reusables/webhooks/project_short_desc.md index 6f18da5d69..2ae5d8be21 100644 --- a/translations/ru-RU/data/reusables/webhooks/project_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/project_short_desc.md @@ -1 +1 @@ -Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/v3/projects)" REST API. +Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_properties.md b/translations/ru-RU/data/reusables/webhooks/pull_request_properties.md index 21544ccd9e..948f78e0b0 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_properties.md @@ -1 +1 @@ -`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls) itself. +`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) itself. diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_properties.md index a38df37d8c..1b854809c7 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_properties.md @@ -1 +1 @@ -`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/v3/pulls/) the comment belongs to. `comment`|`object` | The [comment](/v3/pulls/comments) itself. +`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/pulls#comments) itself. diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_short_desc.md index 7b05ee9a9a..e002a3be49 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_review_comment_short_desc.md @@ -1 +1 @@ -Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/v3/pulls/comments/)" REST API. +Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/rest/reference/pulls#comments)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_review_properties.md b/translations/ru-RU/data/reusables/webhooks/pull_request_review_properties.md index 739e86ca4b..30e4709af5 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ | Клавиша | Тип | Description | | --------------------- | -------- | ---------------------------------------------------------------------- | | `действие` | `строка` | The action that was performed. Can be one of:
  • `submitted` - A pull request review is submitted into a non-pending state.
  • `edited` - The body of a review has been edited.
  • `dismissed` - A review has been dismissed.
| -| `pull_request` | `объект` | The [pull request](/v3/pulls/) the review pertains to. | +| `pull_request` | `объект` | The [pull request](/rest/reference/pulls) the review pertains to. | | `проверка` | `объект` | The review that was affected. | | `changes[body][from]` | `строка` | The previous version of the body if the action was `edited`. | diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/ru-RU/data/reusables/webhooks/pull_request_review_short_desc.md index 07b263364d..3329d4b62e 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_review_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_review_short_desc.md @@ -1 +1 @@ -Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/v3/pulls/reviews/)" REST API. +Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/rest/reference/pulls#reviews)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_short_desc.md b/translations/ru-RU/data/reusables/webhooks/pull_request_short_desc.md index ea9e435d03..45bc1b5789 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_short_desc.md @@ -1 +1 @@ -Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/v3/pulls/)" REST API. +Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/rest/reference/pulls)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/release_short_desc.md b/translations/ru-RU/data/reusables/webhooks/release_short_desc.md index e3a9a3bb3a..a8d506f409 100644 --- a/translations/ru-RU/data/reusables/webhooks/release_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/release_short_desc.md @@ -1 +1 @@ -Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/v3/repos/releases/)" REST API. +Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/rest/reference/repos#releases)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/repo_desc.md b/translations/ru-RU/data/reusables/webhooks/repo_desc.md index df26fb3e7a..e0eca4218d 100644 --- a/translations/ru-RU/data/reusables/webhooks/repo_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/repo_desc.md @@ -1 +1 @@ -`repository` | `object` | The [`repository`](/v3/repos/#get-a-repository) where the event occurred. +`repository` | `object` | The [`repository`](/rest/reference/repos#get-a-repository) where the event occurred. diff --git a/translations/ru-RU/data/reusables/webhooks/repository_import_short_desc.md b/translations/ru-RU/data/reusables/webhooks/repository_import_short_desc.md index 056531b019..d4b6cf9aa0 100644 --- a/translations/ru-RU/data/reusables/webhooks/repository_import_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/repository_import_short_desc.md @@ -1 +1 @@ -Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/v3/migrations/source_imports/)" REST API. +Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/rest/reference/migrations#source-imports)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/repository_short_desc.md b/translations/ru-RU/data/reusables/webhooks/repository_short_desc.md index df290ac0ea..b3e90e8d64 100644 --- a/translations/ru-RU/data/reusables/webhooks/repository_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/repository_short_desc.md @@ -1 +1 @@ -Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/v3/repos/)" REST API. +Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/rest/reference/repos)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/star_short_desc.md b/translations/ru-RU/data/reusables/webhooks/star_short_desc.md index f4fb663419..9569c6958e 100644 --- a/translations/ru-RU/data/reusables/webhooks/star_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/star_short_desc.md @@ -1 +1 @@ -Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/status_short_desc.md b/translations/ru-RU/data/reusables/webhooks/status_short_desc.md index 754f871add..6d835788c9 100644 --- a/translations/ru-RU/data/reusables/webhooks/status_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/status_short_desc.md @@ -1 +1 @@ -When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/v3/repos/statuses/)" REST API. +When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/rest/reference/repos#statuses)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/team_add_short_desc.md b/translations/ru-RU/data/reusables/webhooks/team_add_short_desc.md index 914535a212..ff260fc3cb 100644 --- a/translations/ru-RU/data/reusables/webhooks/team_add_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/team_add_short_desc.md @@ -1 +1 @@ -When a [repository is added to a team](/v3/teams/#add-or-update-team-repository-permissions). +When a [repository is added to a team](/rest/reference/teams#add-or-update-team-repository-permissions). diff --git a/translations/ru-RU/data/reusables/webhooks/team_short_desc.md b/translations/ru-RU/data/reusables/webhooks/team_short_desc.md index fdcf742789..ff27913e21 100644 --- a/translations/ru-RU/data/reusables/webhooks/team_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/team_short_desc.md @@ -1 +1 @@ -Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/v3/teams/)" REST API. +Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/rest/reference/teams)" REST API. diff --git a/translations/ru-RU/data/reusables/webhooks/watch_short_desc.md b/translations/ru-RU/data/reusables/webhooks/watch_short_desc.md index a853027b12..1b250fb019 100644 --- a/translations/ru-RU/data/reusables/webhooks/watch_short_desc.md +++ b/translations/ru-RU/data/reusables/webhooks/watch_short_desc.md @@ -1 +1 @@ -When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/v3/activity/starring/)" REST API. +When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API. diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md index 3e0b0d75d2..de8b19ee75 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md @@ -91,7 +91,7 @@ steps: ### 缓存依赖项 -您可以缓存依赖项来加快工作流程运行。 运行成功后，您的本地 Gradle 缓存将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程包仓库下载依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 运行成功后，您的本地 Gradle 缓存将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程包仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} ```yaml diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md index fa9a25bf0e..336882b1d1 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md @@ -91,7 +91,7 @@ steps: ### 缓存依赖项 -您可以缓存依赖项来加快工作流程运行。 运行成功后，您的本地 Maven 仓库将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程 Maven 仓库下载依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 运行成功后，您的本地 Maven 仓库将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程 Maven 仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} ```yaml diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md index 9e30bec773..05b2fdecc9 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md @@ -129,7 +129,7 @@ jobs: {% data variables.product.prodname_dotcom %} 托管的运行器安装了 npm 和 Yarn 依赖项管理器。 在构建和测试代码之前，可以使用 npm 和 Yarn 在工作流程中安装依赖项。 Windows 和 Linux {% data variables.product.prodname_dotcom %} 托管的运行器也安装了 Grunt、Gulp 和 Bower。 -您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 更多信息请参阅“缓存依赖项以加快工作流程”。 #### 使用 npm 的示例 @@ -227,7 +227,7 @@ always-auth=true #### 缓存依赖项示例 -您可以使用唯一的密钥缓存依赖项，并在使用 `cache` 操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} ```yaml @@ -241,7 +241,7 @@ steps: uses: actions/cache@v2 with: # npm cache files are stored in `~/.npm` on Linux/macOS - path: ~/.npm + path: ~/.npm key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }} restore-keys: | ${{ runner.OS }}-node- diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md b/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md index 5a02b9e89e..9c238651b7 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md @@ -91,7 +91,7 @@ jobs: {% endnote %} -您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 更多信息请参阅“缓存依赖项以加快工作流程”。 例如，以下作业将安装 `SqlServer` 和 `PSScriptAnalyzer` 模块： @@ -119,7 +119,7 @@ jobs: #### 缓存依赖项 -您可以使用唯一密钥缓存 PowerShell 依赖项，以在使用 [`cache`](https://github.com/marketplace/actions/cache) 操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. 更多信息请参阅“缓存依赖项以加快工作流程”。 PowerShell 根据运行器的操作系统将其依赖项缓存在不同的位置。 例如，以下 Ubuntu 示例中使用的 `path` 位置在 Windows 操作系统中是不同的。 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-python.md b/translations/zh-CN/content/actions/guides/building-and-testing-python.md index fbe5803da5..4cb51e7352 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-python.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-python.md @@ -152,11 +152,11 @@ jobs: - name: Set up Python 3.x uses: actions/setup-python@v2 with: - # Python 版本的语义版本范围矩阵或准确的版本 - python-version: '3.x' - # 可选 - x64 或 x86 架构，默认为 x64 - architecture: 'x64' - # 您可以打印当前 Python 版本以测试矩阵 + # Semantic version range syntax or exact version of a Python version + python-version: '3.x' + # Optional - x64 or x86 architecture, defaults to x64 + architecture: 'x64' + # You can test your matrix by printing the current Python version - name: Display Python version run: python -c "import sys; print(sys.version)" ``` @@ -217,7 +217,7 @@ jobs: {% data variables.product.prodname_dotcom %} 托管的运行器安装了 pip 软件包管理器。 在构建和测试代码之前，您可以使用 pip 从 PyPI 软件包注册表安装依赖项。 例如，下面的 YAML 安装或升级 `pip` 软件包安装程序以及 `setuptools` 和 `wheel` 软件包。 -您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 更多信息请参阅“缓存依赖项以加快工作流程”。 {% raw %} @@ -265,7 +265,7 @@ steps: #### 缓存依赖项 -您可以使用唯一密钥缓存 pip 依赖项，并在使用 [`cache`](https://github.com/marketplace/actions/cache) 操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。 +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. 更多信息请参阅“缓存依赖项以加快工作流程”。 Pip 根据运行器的操作系统将依赖项缓存在不同的位置。 您需要缓存的路径可能不同于下面的 Ubuntu 示例，具体取决于您使用的操作系统。 更多信息请参阅 [Python 缓存示例](https://github.com/actions/cache/blob/main/examples.md#python---pip)。 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md index 729b1d1341..7a9a51e67b 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md @@ -1,6 +1,6 @@ --- -title: Building and testing Ruby -intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +title: 构建和测试 Ruby +intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 Ruby 项目。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' @@ -12,18 +12,18 @@ versions: ### 简介 -This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem. +本指南介绍如何创建用来生成和测试 Ruby 应用程序的持续集成 (CI) 工作流程。 如果 CI 测试通过，您可能想要部署代码或发布 gem。 ### 基本要求 -We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. 更多信息请参阅： +建议基本了解 Ruby、YAML、工作流程配置选项以及如何创建工作流程文件。 更多信息请参阅： - [了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions) -- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) +- [Ruby 20 分钟](https://www.ruby-lang.org/en/documentation/quickstart/) -### Starting with the Ruby workflow template +### 从 Ruby 工作流程模板开始 -{% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml). +{% data variables.product.prodname_dotcom %} 提供 Ruby 适用于大多数 Ruby 项目的工作流程模板。 更多信息请参阅 [Ruby 工作流程模板](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml)。 要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。 @@ -58,13 +58,13 @@ jobs: ``` {% endraw %} -### Specifying the Ruby version +### 指定 Ruby 版本 -The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). +指定 Ruby 版本的最简单方法是使用 Ruby 组织在 GitHub 上提供的 `ruby/setup-ruby` 操作。 该操作将任何受支持的 Ruby 版本添加到工作流程中运行的每个作业的 `PATH`。 更多信息请参阅 [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby)。 -Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. +使用 Ruby 的 `ruby/setup-ruby` 操作或 GitHub 的 `actions/setup-ruby` 操作是 Python 与 GitHub Actions 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 Ruby 行为一致。 -The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. +`setup-ruby` 操作采用 Ruby 版本作为输入，并在运行器上配置该版本。 {% raw %} ```yaml @@ -78,11 +78,11 @@ steps: ``` {% endraw %} -Alternatively, you can check a `.ruby-version` file into the root of your repository and `setup-ruby` will use the version defined in that file. +或者，您也可以将 `.ruby-version` 文件检入仓库的根目录，而 `setup-ruby` 将使用该文件中定义的版本。 -### Testing with multiple versions of Ruby +### 使用多个版本的 Ruby 进行测试 -You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version. +您可以添加矩阵策略，以在多个版本的 Ruby 上运行工作流程。 例如，您可以根据版本 2.7、2.6 和 2.5 的最新修补程序版本测试代码。 "x" 是一个通配符，与版本的最新修补程序版本匹配。 {% raw %} ```yaml @@ -92,9 +92,9 @@ strategy: ``` {% endraw %} -Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "Workflow syntax for GitHub Actions" and "Context and expression syntax for GitHub Actions." +`ruby-version` 阵列中指定的每个 Ruby 版本都会创建一个运行相同步骤的作业。 {% raw %}`${{ matrix.ruby-version }}`{% endraw %} 上下文用于访问当前作业的版本。 有关矩阵策略和上下文的更多信息，请参阅“GitHub Actions 的工作流语法”和“GitHub Actions 的上下文和表达式语法”。 -The full updated workflow with a matrix strategy could look like this: +包含矩阵策略的完整更新工作流程可能看起如下： {% raw %} ```yaml @@ -131,9 +131,9 @@ jobs: ``` {% endraw %} -### Installing dependencies with Bundler +### 使用 Bundler 安装依赖项 -The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed. +`setup-ruby` 操作将自动为您安装 Bundler。 版本由您的 `gemfile.lock` 文件决定。 如果您的锁定文件中没有版本，则会安装最新的兼容版本。 {% raw %} ```yaml @@ -148,9 +148,9 @@ steps: #### 缓存依赖项 -The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. -To enable caching, set the following. +要启用缓存，请设置以下内容。 {% raw %} ```yaml @@ -161,11 +161,11 @@ steps: ``` {% endraw %} -This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install. +这将配置 Bundler 以安装 gem 到 `vendor/cache`。 对于工作流程的每次成功运行，此文件夹将由 Actions 缓存，并重新下载用于后续的工作流程运行。 gemfile.lock 和 Ruby 版本的哈希值用作缓存密钥。 如果安装任何新 Gem 或更改版本，缓存将失效，Bundler 将进行全新安装。 -**Caching without setup-ruby** +**无 setup-ruby 的缓存** -For greater control over caching, you can use the `actions/cache` Action directly. 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。 +For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. 更多信息请参阅“缓存依赖项以加快工作流程”。 {% raw %} ```yaml @@ -183,7 +183,7 @@ steps: ``` {% endraw %} -If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this: +如果您使用的是矩阵构建，您将会想要在缓存密钥中包含矩阵变量。 例如，如果您e 不同 ruby 版本 (`matrix.ruby-version`) 和不同系统 (`matrix.os`) 的矩阵策略，您的工作流程步骤可能看起来如下： {% raw %} ```yaml @@ -201,9 +201,9 @@ steps: ``` {% endraw %} -### Matrix testing your code +### 测试代码的矩阵 -The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS. +下面的示例矩阵在 Ubuntu 和 macOS 上测试 MRI、JRuby 和 TruffleRuby 的所有稳定版本和头部版本。 {% raw %} ```yaml @@ -234,9 +234,9 @@ jobs: ``` {% endraw %} -### Linting your code +### 嵌入代码 -The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules. +下面的示例安装 `rubocop` 并用它来嵌入所有文件。 更多信息请参阅 [Rubocop](https://github.com/rubocop-hq/rubocop)。 您可以[配置 Rubocop](https://docs.rubocop.org/rubocop/configuration.html) 来决定特定的嵌入规则。 {% raw %} ```yaml @@ -258,11 +258,11 @@ jobs: ``` {% endraw %} -### Publishing Gems +### 发布 Gem -You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. +您可以配置工作流程在 CI 测试通过时将 Ruby 包发布到您想要的任何包注册表。 -您可以使用仓库密码存储发布软件包所需的访问令牌或凭据。 The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. +您可以使用仓库密码存储发布软件包所需的访问令牌或凭据。 下面的示例创建包并将其发布到 `GitHub Package 注册表`和 `RubyGems`。 {% raw %} ```yaml diff --git a/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md index f0511e8702..225976407a 100644 --- a/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -131,7 +131,7 @@ jobs: 在工作流程运行期间，您可以使用 [`download-artifact`](https://github.com/actions/download-artifact) 操作下载以前在同一工作流程运行中上传的构件。 -工作流程运行完成后，您可以在 {% data variables.product.prodname_dotcom %} 上或使用 REST API 下载或删除构件。 更多信息请参阅“[下载工作流程构件](/actions/managing-workflow-runs/downloading-workflow-artifacts)”、“[删除工作流程构件](/actions/managing-workflow-runs/removing-workflow-artifacts)”和“[构件 REST API](/v3/actions/artifacts/)”。 +工作流程运行完成后，您可以在 {% data variables.product.prodname_dotcom %} 上或使用 REST API 下载或删除构件。 更多信息请参阅“[下载工作流程构件](/actions/managing-workflow-runs/downloading-workflow-artifacts)”、“[删除工作流程构件](/actions/managing-workflow-runs/removing-workflow-artifacts)”和“[构件 REST API](/rest/reference/actions#artifacts)”。 #### 在工作流程运行期间下载构件 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 d164185855..cafe8453c0 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 @@ -1,6 +1,6 @@ --- -title: Managing access to self-hosted runners using groups -intro: You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise. +title: 使用组管理自托管运行器的访问权限 +intro: 您可以使用策略来限制对已添加到组织或企业的自托管运行器的访问。 redirect_from: - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners versions: @@ -11,102 +11,105 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### About self-hosted runner groups +### 关于自托管运行器组 {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** All organizations have a single default self-hosted runner group. Creating and managing additional self-hosted runner groups is only available to enterprise accounts, and for organizations owned by an enterprise account. +**注：**所有组织都有一个默认的自托管运行器组。 创建和管理其他自托管运行器组仅适用于企业帐户以及企业帐户拥有的组织。 {% endnote %} {% endif %} -Self-hosted runner groups are used to control access to self-hosted runners at the organization and enterprise level. Enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group. Organization admins can configure access policies that control which repositories in an organization have access to the runner group. +自托管运行器组用于控制对组织和企业级自托管运行器的访问。 企业管理员可以配置访问策略，用以控制企业中的哪些组织可以访问运行器组。 组织管理员可以配置访问策略，用以控制组织中的哪些组织可以访问运行器组。 -When an enterprise admin grants an organization access to a runner group, organization admins can see the runner group listed in the organization's self-hosted runner settings. The organizations admins can then assign additional granular repository access policies to the enterprise runner group. +当企业管理员授予组织对运行器组的访问权限时，组织管理员可以看到组织的自托管运行器设置中列出的运行器组。 然后，组织管理员可以为企业运行器组分配其他细致的仓库访问策略。 -When new runners are created, they are automatically assigned to the default group. Runners can only be in one group at a time. You can move runners from the default group to another group. For more information, see "[Moving a self-hosted runner to a group](#moving-a-self-hosted-runner-to-a-group)." +新运行器在创建时，将自动分配给默认组。 运行器每次只能在一个组中。 您可以将运行器从默认组移到另一组。 更多信息请参阅“[将自托管运行器移动到组](#moving-a-self-hosted-runner-to-a-group)”。 -### Creating a self-hosted runner group for an organization +### 为组织创建自托管的运行器组 -All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. +所有组织都有一个默认的自托管运行器组。 企业帐户中的组织可以创建其他自托管组。 组织管理员可以允许单个仓库访问运行器组。 -Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create. +自托管运行器在创建时会自动分配给默认组，并且每次只能成为一个组的成员。 您可以将运行器从默认组移到您创建的任何组。 -When creating a group, you must choose a policy that defines which repositories have access to the runner group. +创建组时，必须选择用于定义哪些仓库有权访问运行器组的策略。 {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. In the **Self-hosted runners** section, click **Add new**, and then **New group**. +1. 在 **Self-hosted runners（自托管运行器）**部分，单击 **Add new（新增）**，然后单击 **New group（新组）**。 - ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png) -1. Enter a name for your runner group, and assign a policy for repository access. + ![添加运行器组](/assets/images/help/settings/actions-org-add-runner-group.png) +1. 输入运行程序组的名称，并分配仓库访问策略。 - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to a specific list of repositories, all private repositories, or all repositories in the organization.{% endif %} + {% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 2" %} 您可以将运行器组配置为供一组特定的仓库访问，或者供组织中的所有仓库访问。 默认情况下，公共仓库不能访问运行器组中的运行器。 但您可以使用 **Allow public repositories（允许公共仓库）**选项覆盖此设置。{% else if currentVersion == "enterprise-server@2.22"%}您可以将运行器组配置为供一组特定的仓库、所有私人仓库或组织中所有仓库访问。{% endif %} {% warning %} - **Warnung** + **警告** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. + + 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。 {% endwarning %} - ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png) -1. Click **Save group** to create the group and apply the policy. + ![添加运行器组选项](/assets/images/help/settings/actions-org-add-runner-group-options.png) +1. 单击 **Save group（保存组）**创建组并应用策略。 -### Creating a self-hosted runner group for an enterprise +### 为企业创建自托管运行器组 -Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. +企业可以将其自托管的运行器添加到组以进行访问管理。 企业可以创建供企业帐户中特定组织访问的自托管运行器组。 然后，组织管理员可以为企业运行器组分配其他细致的仓库访问策略。 -Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group. +自托管运行器在创建时会自动分配给默认组，并且每次只能成为一个组的成员。 您可以在注册过程中将运行器分配给特定组，也可以稍后将运行器从默认组移到自定义组。 -When creating a group, you must choose a policy that defines which organizations have access to the runner group. +创建组时，必须选择用于定义哪些组织有权访问运行器组的策略。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Click the **Self-hosted runners** tab. -1. Click **Add new**, and then **New group**. +1. 单击 **Self-hosted runners（自托管运行器）**选项卡。 +1. 单击 **Add new（新增）**，然后单击 **New group（新组）**。 - ![Add runner group](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) -1. Enter a name for your runner group, and assign a policy for organization access. + ![添加运行器组](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) +1. 输入运行程序组的名称，并分配组织访问策略。 - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to all organizations in the enterprise or choose specific organizations.{% endif %} + {% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 2" %} 您可以将运行器组配置为供一组特定的组织访问，或者供企业中的所有组织访问。 默认情况下，公共仓库不能访问运行器组中的运行器。 但您可以使用 **Allow public repositories（允许公共仓库）**选项覆盖此设置。{% else if currentVersion == "enterprise-server@2.22"%}您可以将运行器组配置为供企业中的所有组织或选择的特定组织访问。{% endif %} {% warning %} - **Warnung** + **警告** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. + + 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。 {% endwarning %} - ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png) -1. Click **Save group** to create the group and apply the policy. + ![添加运行器组选项](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png) +1. 单击 **Save group（保存组）**创建组并应用策略。 -### Changing the access policy of a self-hosted runner group +### 更改自托管运行器组的访问策略 -You can update the access policy of a runner group, or rename a runner group. +您可以更新运行器组的访问策略，或重命名运行器组。 {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} -### Moving a self-hosted runner to a group +### 将自托管的运行器移动到组 -New self-hosted runners are automatically assigned to the default group, and can then be moved to another group. +新的自托管运行器将自动分配给默认组，然后可以移到另一个组。 -1. In the **Self-hosted runners** section of the settings page, locate the current group of the runner you want to move group and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) -1. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png) -1. To move the runner, click on the destination group. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) +1. 在设置页面的 **Self-hosted runners（自托管运行器）**部分，找到要移动组的运行器的当前组，并展开组成员列表。 ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png) +1. 选中自托管运行器旁边的复选框，然后单击 **Move to group（移动到组）**以查看可用的目的地。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move.png) +1. 要移动运行器，请单击目标组。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) -### Removing a self-hosted runner group +### 删除自托管运行器组 -Self-hosted runners are automatically returned to the default group when their group is removed. +自托管运行器在其组被删除时将自动返回到默认组。 -1. In the **Self-hosted runners** section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) +1. 在设置页面的 **Self-hosted runners（自托管运行器）**部分，找到您想要删除的组，并单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 按钮。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-kebab.png) -1. To remove the group, click **Remove group**. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png) - -1. Review the confirmation prompts, and click **Remove this runner group**. +1. 要删除组，请单击 **Remove group（删除组）**。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-remove.png) +1. 查看确认提示，然后单击 **Remove this runner group（删除此运行器组）**。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md index 8df2adc6c2..21aecae1e7 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -42,7 +42,7 @@ versions: #### 步骤 -A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. 作业中的每个步骤在同一运行器上执行，可让该作业中的操作互相共享数据。 +步骤是可以在作业中运行命令的单个任务。 步骤可以是_操作_或 shell 命令。 作业中的每个步骤在同一运行器上执行，可让该作业中的操作互相共享数据。 #### 操作 @@ -50,7 +50,7 @@ _操作_ 是独立命令，它们组合到_步骤_以创建_作业_。 操作是 #### 运行器 -A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. 您可以使用 {% data variables.product.prodname_dotcom %} 托管的运行器或托管您自己的运行器。 运行器将侦听可用的作业，每次运行一个作业，并将进度、日志和结果报告回 {% data variables.product.prodname_dotcom %}。 对于 {% data variables.product.prodname_dotcom %} 托管的运行器，工作流程中的每项作业都会在一个新的虚拟环境中运行。 +运行器是安装了 [{% data variables.product.prodname_actions %} 运行器应用程序](https://github.com/actions/runner)的服务器。 您可以使用 {% data variables.product.prodname_dotcom %} 托管的运行器或托管您自己的运行器。 运行器将侦听可用的作业，每次运行一个作业，并将进度、日志和结果报告回 {% data variables.product.prodname_dotcom %}。 对于 {% data variables.product.prodname_dotcom %} 托管的运行器，工作流程中的每项作业都会在一个新的虚拟环境中运行。 {% data variables.product.prodname_dotcom %} 托管的运行器基于 Ubuntu Linux、Microsoft Windows 和 macOS 。 有关 {% data variables.product.prodname_dotcom %} 托管的运行器的信息，请参阅“[ {% data variables.product.prodname_dotcom %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners)”。 如果您需要不同的操作系统或需要特定的硬件配置，可以托管自己的运行器。 有关自托管运行器的信息，请参阅“[托管您自己的运行器](/actions/hosting-your-own-runners)”。 @@ -197,7 +197,7 @@ A runner is a server that has the [{% data variables.product.prodname_actions %} #### 可视化工作流程文件 -在此关系图中，您可以看到刚刚创建的工作流程文件，以及 {% data variables.product.prodname_actions %} 组件在层次结构中的组织方式。 Each step executes a single action or shell command. 步骤 1 和 2 使用预构建的社区操作。 Steps 3 and 4 run shell commands directly on the runner. 要查找更多为工作流预构建的操作，请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。 +在此关系图中，您可以看到刚刚创建的工作流程文件，以及 {% data variables.product.prodname_actions %} 组件在层次结构中的组织方式。 每个步骤执行单个操作或 shell 命令。 步骤 1 和 2 使用预构建的社区操作。 步骤 3 和 4 直接在运行器上运行 shell 命令。 要查找更多为工作流预构建的操作，请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。 ![工作流程概述](/assets/images/help/images/overview-actions-event.png) diff --git a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md index 86279ee4e6..dd8f37e740 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md @@ -57,7 +57,7 @@ jobs: needs: build runs-on: ubuntu-latest steps: - - run: ./test_server.sh + - run: ./test_server.sh ``` 更多信息请参阅 [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)。 @@ -106,7 +106,7 @@ jobs: ``` {% endraw %} -更多信息请参阅“[缓存依赖项以加快工作流程](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)”。 +更多信息请参阅“缓存依赖项以加快工作流程”。 ### 使用数据库和服务容器 diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index af9185d7fa..c13b8837be 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions -更多信息请参阅“[缓存依赖项以加快工作流程](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)”。 +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 更多信息请参阅“缓存依赖项以加快工作流程”。 {% data variables.product.prodname_actions %} 没有 CircleCI 的 Docker 层缓存（或 DLC）的等效项。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 5b1773107b..456e291e95 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -262,7 +262,7 @@ jobs: runs-on: ubuntu-latest steps: - run: echo "This job will be run first, in parallel with build_a" - + test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] @@ -346,7 +346,7 @@ jobs: -更多信息请参阅“[缓存依赖项以加快工作流程](/actions/guides/caching-dependencies-to-speed-up-workflows)”。 +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 更多信息请参阅“缓存依赖项以加快工作流程”。 ### 构件 @@ -367,7 +367,7 @@ GitLab CI/CD {% raw %} ```yaml -script: +script: artifacts: paths: - math-homework.txt @@ -414,7 +414,7 @@ GitLab CI/CD container-job: variables: POSTGRES_PASSWORD: postgres - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port @@ -423,10 +423,10 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - npm ci - # Runs a script that creates a PostgreSQL client, + # Runs a script that creates a PostgreSQL client, # populates the client with data, and retrieves data - node client.js tags: @@ -452,7 +452,7 @@ jobs: - name: Check out repository code uses: actions/checkout@v2 - # Performs a clean installation of all dependencies + # Performs a clean installation of all dependencies # in the `package.json` file - name: Install dependencies run: npm ci @@ -462,7 +462,7 @@ jobs: # populates the client with data, and retrieves data run: node client.js env: - # The hostname used to communicate with the + # The hostname used to communicate with the # PostgreSQL service container POSTGRES_HOST: postgres # The default PostgreSQL port diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 6046eadc90..9592224022 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -163,6 +163,12 @@ git: +#### 在矩阵中使用环境变量 + +Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. + +In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} + ### {% data variables.product.prodname_actions %} 中的关键功能 从 Travis CI 迁移时，请考虑 {% data variables.product.prodname_actions %} 中的以下关键功能： @@ -281,7 +287,7 @@ jobs: ### 缓存依赖项 -Travis CI 和 {% data variables.product.prodname_actions %} 可让您手动缓存依赖供以后使用。 此示例说明每个系统的缓存语法。 +Travis CI 和 {% data variables.product.prodname_actions %} 可让您手动缓存依赖供以后使用。 此示例说明每个系统的缓存语法。 @@ -316,7 +322,7 @@ cache: npm
-更多信息请参阅“[缓存依赖项以加快工作流程](/actions/guides/caching-dependencies-to-speed-up-workflows)”。 +{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 更多信息请参阅“缓存依赖项以加快工作流程”。 ### 常见任务示例 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md index e2e93a2a24..533f006117 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -14,7 +14,7 @@ versions: 如果运行已完成，则可查看运行结果是成功、失败、已取消还是中性。 如果运行失败，您可以查看并搜索构建日志，来诊断失败原因并重新运行工作流程。 您也可以查看可计费作业执行分钟数，或下载日志和创建构件。 -{% data variables.product.prodname_actions %} 使用 Checks API 来输出工作流程的状态、结果和日志。 {% data variables.product.prodname_dotcom %} 对每个工作流程创建新检查套件。 检查套件包含检查工作流程中每项作业的运行，而每项作业包含步骤。 {% data variables.product.prodname_actions %} 作为工作流程中的一个步骤运行。 有关检查 API 的详细信息，请参阅“[检查](/v3/checks/)”。 +{% 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 %} diff --git a/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md b/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md index aeecab8883..9a7c91ea9d 100644 --- a/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md @@ -79,7 +79,7 @@ versions: ### `GITHUB_TOKEN` 的权限 -有关 {% data variables.product.prodname_github_apps %} 可通过各种权限访问的 API 端点的信息，请参阅“[{% data variables.product.prodname_github_app %} 权限](/v3/apps/permissions/)”。 +有关 {% data variables.product.prodname_github_apps %} 可通过各种权限访问的 API 端点的信息，请参阅“[{% data variables.product.prodname_github_app %} 权限](/rest/reference/permissions-required-for-github-apps)”。 | 权限 | 访问类型 | 通过复刻的仓库访问 | | -------- | ---- | --------- | diff --git a/translations/zh-CN/content/actions/reference/encrypted-secrets.md b/translations/zh-CN/content/actions/reference/encrypted-secrets.md index 4a1bcbb97e..8de463d1c9 100644 --- a/translations/zh-CN/content/actions/reference/encrypted-secrets.md +++ b/translations/zh-CN/content/actions/reference/encrypted-secrets.md @@ -43,11 +43,11 @@ versions: {% endwarning %} -您还可以使用 REST API 管理密码。 更多信息请参阅“[密码](/v3/actions/secrets/)”。 +您还可以使用 REST API 管理密码。 更多信息请参阅“[密码](/rest/reference/actions#secrets)”。 #### 限制凭据权限 -生成凭据时，建议尽可能授予最低的权限。 例如，不使用个人凭据，而使用[部署密钥](/v3/guides/managing-deploy-keys/#deploy-keys)或服务帐户。 请考虑授予只读权限（如果这是所需的全部权限）并尽可能限制访问。 生成个人访问令牌 (PAT) 时，选择所需的最小范围。 +生成凭据时，建议尽可能授予最低的权限。 例如，不使用个人凭据，而使用[部署密钥](/developers/overview/managing-deploy-keys#deploy-keys)或服务帐户。 请考虑授予只读权限（如果这是所需的全部权限）并尽可能限制访问。 生成个人访问令牌 (PAT) 时，选择所需的最小范围。 ### 为仓库创建加密密码 diff --git a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md index 124fa1ab0d..be7f0a266b 100644 --- a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md @@ -143,7 +143,7 @@ jobs: {% data reusables.github-actions.branch-requirement %} -当您想要触发在 {% data variables.product.product_name %} 外发生的活动的工作流程时，可以使用 {% data variables.product.prodname_dotcom %} API 触发名为 [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) 的 web 挂钩事件。 更多信息请参阅“[创建仓库调度事件](/v3/repos/#create-a-repository-dispatch-event)”。 +当您想要触发在 {% data variables.product.product_name %} 外发生的活动的工作流程时，可以使用 {% data variables.product.prodname_dotcom %} API 触发名为 [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) 的 web 挂钩事件。 更多信息请参阅“[创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event)”。 要触发自定义 `repository_dispatch` web 挂钩事件，必须将 `POST` 请求发送到 {% data variables.product.product_name %} API 端点，并提供 `event_type` 名称来描述活动类型。 要触发工作流程运行，还必须配置工作流程使用 `repository_dispatch` 事件。 @@ -163,7 +163,7 @@ on: #### `check_run` -在发生 `check_run` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[检查运行](/v3/checks/runs/)”。 +在发生 `check_run` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[检查运行](/rest/reference/checks#runs)”。 {% data reusables.github-actions.branch-requirement %} @@ -183,7 +183,7 @@ on: #### `check_suite` -在发生 `check_suite` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[检查套件](/v3/checks/suites/)”。 +在发生 `check_suite` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[检查套件](/rest/reference/checks#suites)”。 {% data reusables.github-actions.branch-requirement %} @@ -209,7 +209,7 @@ on: #### `create` -每当有人创建分支或标记（触发 `create` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[创建引用](/v3/git/refs/#create-a-reference)”。 +每当有人创建分支或标记（触发 `create` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[创建引用](/rest/reference/git#create-a-reference)”。 | Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------- | ---- | -------------- | ------------ | @@ -224,7 +224,7 @@ on: #### `delete` -每当有人删除分支或标记（触发 `delete` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[删除引用](/v3/git/refs/#delete-a-reference)”。 +每当有人删除分支或标记（触发 `delete` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[删除引用](/rest/reference/git#delete-a-reference)”。 {% data reusables.github-actions.branch-requirement %} @@ -271,7 +271,7 @@ on: #### `复刻` -每当有人复刻仓库（触发 `fork` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[创建复刻](/v3/repos/forks/#create-a-fork)”。 +每当有人复刻仓库（触发 `fork` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[创建复刻](/rest/reference/repos#create-a-fork)”。 {% data reusables.github-actions.branch-requirement %} @@ -354,7 +354,7 @@ jobs: #### `issues` -在发生 `issues` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[议题](/v3/issues)”。 +在发生 `issues` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[议题](/rest/reference/issues)”。 {% data reusables.github-actions.branch-requirement %} @@ -374,7 +374,7 @@ on: #### `标签` -在发生 `label` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[标签](/v3/issues/labels/)”。 +在发生 `label` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[标签](/rest/reference/issues#labels)”。 {% data reusables.github-actions.branch-requirement %} @@ -394,7 +394,7 @@ on: #### `里程碑` -在发生 `milestone` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[里程碑](/v3/issues/milestones/)”。 +在发生 `milestone` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[里程碑](/rest/reference/issues#milestones)”。 {% data reusables.github-actions.branch-requirement %} @@ -431,7 +431,7 @@ on: #### `project` -在发生 `project` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目](/v3/projects/)”。 +在发生 `project` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目](/rest/reference/projects)”。 {% data reusables.github-actions.branch-requirement %} @@ -451,7 +451,7 @@ on: #### `project_card` -在发生 `project_card` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目卡](/v3/projects/cards)”。 +在发生 `project_card` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目卡](/rest/reference/projects#cards)”。 {% data reusables.github-actions.branch-requirement %} @@ -471,7 +471,7 @@ on: #### `project_column` -在发生 `project_column` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目列](/v3/projects/columns)”。 +在发生 `project_column` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目列](/rest/reference/projects#columns)”。 {% data reusables.github-actions.branch-requirement %} @@ -491,7 +491,7 @@ on: #### `public` -每当有人将私有仓库公开（触发 `public` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[编辑仓库](/v3/repos/#edit)”。 +每当有人将私有仓库公开（触发 `public` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[编辑仓库](/rest/reference/repos#edit)”。 {% data reusables.github-actions.branch-requirement %} @@ -508,7 +508,7 @@ on: #### `pull_request` -在发生 `pull_request` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[拉取请求](/v3/pulls)”。 +在发生 `pull_request` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[拉取请求](/rest/reference/pulls)”。 {% note %} @@ -534,7 +534,7 @@ on: #### `pull_request_review` -在发生 `pull_request_review` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[拉取请求审查](/v3/pulls/reviews)”。 +在发生 `pull_request_review` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[拉取请求审查](/rest/reference/pulls#reviews)”。 | Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | | ---------------------------------------------------------------------- | ---------------------------------------------------------- | ----------------------- | ----------------------------------- | @@ -554,7 +554,7 @@ on: #### `pull_request_review_comment` -每当拉取请求统一差异的评论被修改（触发 `pull_request_review_comment` 事件）时运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %} 有关 REST API 的信息，请参阅“[审查评论](/v3/pulls/comments)”。 +每当拉取请求统一差异的评论被修改（触发 `pull_request_review_comment` 事件）时运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %} 有关 REST API 的信息，请参阅“[审查评论](/rest/reference/pulls#comments)”。 | Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------------------------------------- | ------------------------------------------------------ | ----------------------- | ----------------------------------- | @@ -597,7 +597,7 @@ on: pull_request_target {% note %} -**注：**适用于 GitHub Actions 的 web 挂钩有效负载在 `commit` 对象中不包括 `added`、`removed` 和 `modified` 属性。 您可以使用 REST API 检索完整的提交对象。 更多信息请参阅“[获取单个提交](/v3/repos/commits/#get-a-single-commit)”。 +**注：**适用于 GitHub Actions 的 web 挂钩有效负载在 `commit` 对象中不包括 `added`、`removed` 和 `modified` 属性。 您可以使用 REST API 检索完整的提交对象。 更多信息请参阅“[获取单个提交](/rest/reference/repos#get-a-single-commit)”。 {% endnote %} @@ -640,7 +640,7 @@ on: {% endnote %} -在发生 `release` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[发行版](/v3/repos/releases/)”。 +在发生 `release` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[发行版](/rest/reference/repos#releases)”。 | Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ | @@ -658,7 +658,7 @@ on: #### `状态` -在 Git 提交的状态发生变化（触发 `status` 事件）的任何时间运行您的工作流程。 有关 REST API 的信息，请参阅“[状态](/v3/repos/statuses/)”。 +在 Git 提交的状态发生变化（触发 `status` 事件）的任何时间运行您的工作流程。 有关 REST API 的信息，请参阅“[状态](/rest/reference/repos#statuses)”。 {% data reusables.github-actions.branch-requirement %} @@ -675,7 +675,7 @@ on: #### `查看` -在发生 `watch` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[星标](/v3/activity/starring/)”。 +在发生 `watch` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[星标](/rest/reference/activity#starring)”。 {% data reusables.github-actions.branch-requirement %} diff --git a/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md b/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md index 6200179914..5f98a4e8c4 100644 --- a/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md @@ -79,6 +79,7 @@ GitHub Actions 使用对 - "[对组织禁用或限制 {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[在企业帐户中实施 {% data variables.product.prodname_ghe_cloud %} 的 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)"{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### 禁用和启用工作流程 您可以在 {% data variables.product.prodname_dotcom %} 上启用和禁用仓库中的个别工作流程。 @@ -86,3 +87,4 @@ GitHub Actions 使用对 {% data reusables.actions.scheduled-workflows-disabled %} 更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。 +{% endif %} diff --git a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md index 2801fbbc44..c8730aedf7 100644 --- a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md @@ -227,7 +227,7 @@ defaults: 在工作流程的使用限制之内可运行无限数量的作业。 更多信息请参阅“[使用限制和计费](/actions/reference/usage-limits-billing-and-administration)”（对于 {% data variables.product.prodname_dotcom %} 托管的运行器）和“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)”（对于自托管运行器使用限制）。 -如果需要查找在工作流程运行中运行的作业的唯一标识符，可以使用 {% data variables.product.prodname_dotcom %} ApI。 更多信息请参阅“[工作流程作业](/v3/actions/workflow-jobs)”。 +如果需要查找在工作流程运行中运行的作业的唯一标识符，可以使用 {% data variables.product.prodname_dotcom %} ApI。 更多信息请参阅“[工作流程作业](/rest/reference/actions#workflow-jobs)”。 ### **`jobs.`** @@ -659,7 +659,7 @@ steps: - `cmd` - 除了编写脚本来检查每个错误代码并相应地响应之外，似乎没有办法完全选择快速失败行为。 由于我们默认不能实际提供该行为，因此您需要将此行为写入脚本。 - - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. 此行为在内部与上一个 `sh` 和 `pwsh` 默认行为一致，是 `cmd.exe` 的默认值，所以此行为保持不变。 + - `cmd.exe` 在退出时带有其执行的最后一个程序的错误等级，并且会将错误代码返回到运行程序。 此行为在内部与上一个 `sh` 和 `pwsh` 默认行为一致，是 `cmd.exe` 的默认值，所以此行为保持不变。 #### **`jobs..steps.with`** @@ -718,7 +718,7 @@ 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`** @@ -876,36 +876,11 @@ strategy: {% endnote %} -##### Using environment variables in a matrix +##### 在矩阵中使用环境变量 -You can add custom environment variables for each test combination by using `include` with `env`. You can then refer to the custom environment variables in a later step. +You can add custom environment variables for each test combination by using the `include` key. 然后，您可以在后面的步骤中引用自定义环境变量。 -In this example, the matrix entries for `node-version` are each configured to use different values for the `site` and `datacenter` environment variables. The `Echo site details` step then uses {% raw %}`env: ${{ matrix.env }}`{% endraw %} to refer to the custom variables: - -{% raw %} -```yaml -name: Node.js CI -on: [push] -jobs: - build: - runs-on: ubuntu-latest - strategy: - matrix: - include: - - node-version: 10.x - site: "prod" - datacenter: "site-a" - - node-version: 12.x - site: "dev" - datacenter: "site-b" - steps: - - name: Echo site details - env: - SITE: ${{ matrix.site }} - DATACENTER: ${{ matrix.datacenter }} - run: echo $SITE $DATACENTER -``` -{% endraw %} +{% data reusables.github-actions.matrix-variable-example %} ### **`jobs..strategy.fail-fast`** diff --git a/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md b/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md index eacfd8bed4..6959f20c16 100644 --- a/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md +++ b/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: 在您更改身份验证方法时，{% data variables.product.product_location %} 上的用户帐户将保留，只要他们的用户名没有发生变化，用户就可以继续登录原来的帐户。 -如果新的身份验证方法更改了用户名，将创建新帐户。 作为管理员，您可以通过站点管理员设置或使用 [User Administration API](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user) 重命名用户。 +如果新的身份验证方法更改了用户名，将创建新帐户。 As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). 您应当考虑的其他问题包括： diff --git a/translations/zh-CN/content/admin/configuration/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/command-line-utilities.md index 0da28a89c1..e464619972 100644 --- a/translations/zh-CN/content/admin/configuration/command-line-utilities.md +++ b/translations/zh-CN/content/admin/configuration/command-line-utilities.md @@ -159,7 +159,7 @@ $ ghe-es-index-status -do | column -ts, #### ghe-legacy-github-services-report -此实用程序会列出您的设备中使用 {% data variables.product.prodname_dotcom %} Services 的仓库，作为一种集成方法，此服务将于 2018 年 10 月 1 日停用。 您的设备上的用户可能已设置 {% data variables.product.prodname_dotcom %} Services，为发往某些仓库的推送创建通知。 更多信息请参阅 {% data variables.product.prodname_blog %} 上的“[宣布弃用 {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)”或“[替换 {% data variables.product.prodname_dotcom %} Services](/v3/guides/replacing-github-services/)”。 如需获取关于此命令的更多信息或附加选项，请使用 `-h` 标志。 +此实用程序会列出您的设备中使用 {% data variables.product.prodname_dotcom %} Services 的仓库，作为一种集成方法，此服务将于 2018 年 10 月 1 日停用。 您的设备上的用户可能已设置 {% data variables.product.prodname_dotcom %} Services，为发往某些仓库的推送创建通知。 更多信息请参阅 {% data variables.product.prodname_blog %} 上的“[宣布弃用 {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)”或“[替换 {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)”。 如需获取关于此命令的更多信息或附加选项，请使用 `-h` 标志。 ```shell ghe-legacy-github-services-report diff --git a/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md index 6a8f7549fd..9c74075263 100644 --- a/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md +++ b/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md @@ -37,7 +37,7 @@ versions: 启用 {% data variables.product.prodname_github_connect %} 将不允许 {% data variables.product.prodname_dotcom_the_website %} 用户对 {% data variables.product.prodname_ghe_server %} 进行更改。 -有关使用 GraphQL API 管理企业帐户的信息，请参阅“[企业帐户](/v4/guides/managing-enterprise-accounts)”。 +有关使用 GraphQL API 管理企业帐户的信息，请参阅“[企业帐户](/graphql/guides/managing-enterprise-accounts)”。 ### 启用 {% data variables.product.prodname_github_connect %} 1. 登录到 diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md b/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md index b8109797de..76a9f6ccda 100644 --- a/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md +++ b/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md @@ -11,7 +11,7 @@ versions: ### 设置外部 `collectd` 服务器 -如果您尚未设置外部 `collectd` 服务器，则需要首先进行设置，然后才能在 {% data variables.product.product_location %} 上启用 `collectd` 转发。 Your `collectd` server must be running `collectd` version 5.x or higher. +如果您尚未设置外部 `collectd` 服务器，则需要首先进行设置，然后才能在 {% data variables.product.product_location %} 上启用 `collectd` 转发。 您的 `collectd` 服务器运行的 `collectd` 版本不得低于 5.x。 1. 登录 `collectd` 服务器。 2. 创建或编辑 `collectd` 配置文件，以加载网络插件并为服务器和端口指令填入适当的值。 在大多数分发中，此文件位于 `/etc/collectd/collectd.conf` 中 diff --git a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md index 7a6e917b80..02c92ad31d 100644 --- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md +++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md @@ -1,5 +1,5 @@ --- -title: 关于企业帐户 +title: About enterprise accounts intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management{% if enterpriseServerVersions contains currentVersion %} for billing and license usage{% endif %}.' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -### 关于 {% data variables.product.product_name %} 上的企业账户 +### About enterprise accounts on {% data variables.product.product_name %} -An enterprise account allows you to manage multiple organizations{% if enterpriseServerVersions contains currentVersion %} and {% data variables.product.prodname_ghe_server %} instances{% else %} on {% data variables.product.product_name %}{% endif %}. 您的企业帐户必须有操作点，如 {% data variables.product.prodname_dotcom %} 上的组织或个人帐户。 企业管理员可以管理设置和首选项，如： +An enterprise account allows you to manage multiple organizations{% if enterpriseServerVersions contains currentVersion %} and {% data variables.product.prodname_ghe_server %} instances{% else %} on {% data variables.product.product_name %}{% endif %}. Your enterprise account must have a handle, like an organization or personal account on {% data variables.product.prodname_dotcom %}. Enterprise administrators can manage settings and preferences, like: - Member access and management (organization members, outside collaborators){% if enterpriseServerVersions contains currentVersion %} - Billing and usage ({% data variables.product.prodname_ghe_server %} instances, user licenses, {% data variables.large_files.product_name_short %} packs){% endif %} @@ -22,9 +22,9 @@ An enterprise account allows you to manage multiple organizations{% if enterpris {% if enterpriseServerVersions contains currentVersion %} -有关 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_ghe_server %} 之间差异的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。 要升级至 {% data variables.product.prodname_enterprise %} 或开始使用企业帐户，请联系 {% data variables.contact.contact_enterprise_sales %}。 +For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." To upgrade to {% data variables.product.prodname_enterprise %} or to get started with an enterprise account, contact {% data variables.contact.contact_enterprise_sales %}. -### 管理链接至企业帐户的 {% data variables.product.prodname_ghe_server %} 许可 +### Managing {% data variables.product.prodname_ghe_server %} licenses linked to your enterprise account {% data reusables.enterprise-accounts.admin-managing-licenses %} diff --git a/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md b/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md index 597a20c8fe..83f2fc3d4f 100644 --- a/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md +++ b/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md @@ -19,6 +19,6 @@ versions: - 对 {% data variables.enterprise.management_console %} 进行更改。 更多信息请参阅“[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)”。 - 配置 LDAP 同步。 更多信息请参阅“[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)”。{% endif %} - 收集关于企业的统计信息。 更多信息请参阅“[管理统计](/rest/reference/enterprise-admin#admin-stats)”。 -- 管理企业帐户。 更多信息请参阅“[企业帐户](/v4/guides/managing-enterprise-accounts)”。 +- 管理企业帐户。 更多信息请参阅“[企业帐户](/graphql/guides/managing-enterprise-accounts)”。 -有关 {% data variables.product.prodname_enterprise_api %} 的完整文档，请参阅 [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql)。 \ No newline at end of file +有关 {% data variables.product.prodname_enterprise_api %} 的完整文档，请参阅 [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql)。 diff --git a/translations/zh-CN/content/admin/packages/configuring-third-party-storage-for-packages.md b/translations/zh-CN/content/admin/packages/configuring-third-party-storage-for-packages.md index 3c7b283458..3ea86b41ce 100644 --- a/translations/zh-CN/content/admin/packages/configuring-third-party-storage-for-packages.md +++ b/translations/zh-CN/content/admin/packages/configuring-third-party-storage-for-packages.md @@ -13,7 +13,7 @@ versions: {% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_registry %} 使用外部 Blob 存储来存储您的软件包。 所需存储量取决于您使用 {% data variables.product.prodname_registry %} 的情况。 -目前，{% data variables.product.prodname_registry %} 支持使用 Amazon Web Services (AWS) S3 的 Blob 存储。 还支持 MinIO，但配置当前未在 {% data variables.product.product_name %} 界面中实现。 您可以按照 AWS S3 的说明使用 MinIO 进行存储，输入 MinIO 配置的类似信息。 Before configuring third-party storage for {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, you must set up a bucket with your third-party storage provider. For more information on installing and running a MinIO bucket to use with {% data variables.product.prodname_registry %}, see the "[Quickstart for configuring MinIO storage](/admin/packages/quickstart-for-configuring-minio-storage)." +目前，{% data variables.product.prodname_registry %} 支持使用 Amazon Web Services (AWS) S3 的 Blob 存储。 还支持 MinIO，但配置当前未在 {% data variables.product.product_name %} 界面中实现。 您可以按照 AWS S3 的说明使用 MinIO 进行存储，输入 MinIO 配置的类似信息。 在 {% data variables.product.prodname_dotcom %} 上为 {% data variables.product.prodname_registry %} 配置第三方存储之前，必须使用第三方存储提供商设置存储桶。 有关安装和运行 MinIO 存储桶以用于 {% data variables.product.prodname_registry %} 的详细信息，请参阅“[配置 MinIO 存储快速入门](/admin/packages/quickstart-for-configuring-minio-storage)”。 为了获得最佳体验，我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 @@ -22,9 +22,9 @@ versions: {% warning %} **警告：** -- It's critical you set the restrictive access policies you want for your storage bucket because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. For more information, see [Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html) in the AWS Documentation. -- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. -- Make sure to configure the bucket you'll want to use in the future. 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。 +- 为存储桶设置所需的限制性访问策略至关重要，因为 {% data variables.product.company_short %} 不会将特定对象权限或其他访问控制列表 (ACL) 应用于存储桶配置。 例如，如果将存储桶设为公共，则在公共互联网上可以访问存储桶中的数据。 更多信息请参阅 AWS 文档中的[设置存储桶和对象访问权限](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)。 +- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 +- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。 {% endwarning %} diff --git a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md index bf6565fef2..a14a0b63f0 100644 --- a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md +++ b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md @@ -1,15 +1,15 @@ --- -title: Quickstart for configuring MinIO storage -intro: 'Set up MinIO as a storage provider for using {% data variables.product.prodname_registry %} on your enterprise.' +title: 配置 MinIO 存储快速入门 +intro: '设置 MinIO 作为存储提供商以在企业上使用 {% data variables.product.prodname_registry %}。' versions: enterprise-server: '>=2.22' --- {% data reusables.package_registry.packages-ghes-release-stage %} -Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your third-party storage solution. +在 {% data variables.product.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前，您必须准备第三方存储解决方案。 -MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise. +MinIO 在企业上提供对象存储并支持 S3 API 和 {% data variables.product.prodname_registry %}。 This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). @@ -38,9 +38,9 @@ For more information about your options, see the official [MinIO docs](https://d ```shell $ docker pull minio/minio ``` - For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)." + 更多信息请参阅官方的“[MinIO 快速入门指南](https://docs.min.io/docs/minio-quickstart-guide)”。 -3. Sign in to MinIO using your MinIO access key and secret. +3. 使用您的 MinIO 访问密钥登录 MinIO。 {% linux %} ```shell @@ -58,16 +58,16 @@ For more information about your options, see the official [MinIO docs](https://d ``` {% endmac %} - You can access your MinIO keys using the environment variables: + 您可以使用环境变量访问 MinIO 密钥： ```shell $ echo $MINIO_ACCESS_KEY $ echo $MINIO_SECRET_KEY ``` -4. Run MinIO in your chosen mode. +4. 在您选择的模式下运行 MinIO。 - * Run MinIO using Docker on a single host: + * 在单一主机上使用 Docker 运行 MinIO： ```shell $ docker run -p 9000:9000 \ @@ -77,9 +77,9 @@ For more information about your options, see the official [MinIO docs](https://d minio/minio server /data ``` - For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)." + 更多信息请参阅“[MinIO Docker 快速入门指南](https://docs.min.io/docs/minio-docker-quickstart-guide.html)”。 - * Run MinIO using Docker as a NAS gateway: + * 使用 Docker 作为 NAS 网关运行 MinIO： This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. diff --git a/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md index f3f1e3cc19..3d7b84da9d 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,7 +34,7 @@ versions: 每次有人在您的企业上创建新仓库时，此人必须选择仓库的可见性。 当您配置企业的默认可见性设置时，需要选择默认可见性。 有关仓库可见性的更多信息，请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)。” -If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. 更多信息请参阅“[设置仓库创建策略](#setting-a-policy-for-repository-creation)”。 +如果企业所有者不允许成员创建某种类型的仓库，成员将无法创建此类仓库，即使可见性设置默认为此类型。 更多信息请参阅“[设置仓库创建策略](#setting-a-policy-for-repository-creation)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} @@ -49,9 +49,9 @@ If an enterprise owner disallows members from creating certain types of reposito ### 设置有关更改仓库可见性的策略 -When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository. +当您阻止成员更改仓库可见性时，只有企业所有者可以更改仓库的可见性。 -If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. 更多信息请参阅“[设置仓库创建策略](#setting-a-policy-for-repository-creation)”。 +如果企业所有者仅允许组织所有者创建仓库，则成员将无法更改仓库可见性。 如果企业所有者只允许私有仓库成员创建私有仓库，则成员只能将仓库的可见性更改为私有。 更多信息请参阅“[设置仓库创建策略](#setting-a-policy-for-repository-creation)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -77,7 +77,7 @@ If an enterprise owner has restricted repository creation to organization owners ### 实施有关复刻私有或内部仓库的策略 -Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level. +在企业拥有的所有组织中，您可以允许有权访问私有或内部仓库的人员复刻仓库、永远不允许分支私有或内部仓库，或者允许所有者在组织级别管理设置。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/zh-CN/content/admin/user-management/audited-actions.md b/translations/zh-CN/content/admin/user-management/audited-actions.md index d5d9ad32ee..72c7fad1fb 100644 --- a/translations/zh-CN/content/admin/user-management/audited-actions.md +++ b/translations/zh-CN/content/admin/user-management/audited-actions.md @@ -36,12 +36,12 @@ versions: #### 企业配置设置 -| 名称 | 描述 | -| -------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `business.update_member_repository_creation_permission` | 站点管理员限制在企业中的组织中创建仓库。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。 | -| `business.clear_members_can_create_repos` | 站点管理员取消了对在企业中的组织中创建仓库的限制。 For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% if enterpriseServerVersions contains currentVersion %} -| `enterprise.config.lock_anonymous_git_access` | 站点管理员锁定匿名 Git 读取权限，以防止仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。 | -| `enterprise.config.unlock_anonymous_git_access` | 站点管理员解锁匿名 Git 读取权限，以允许仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."{% endif %} +| 名称 | 描述 | +| -------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `business.update_member_repository_creation_permission` | 站点管理员限制在企业中的组织中创建仓库。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。 | +| `business.clear_members_can_create_repos` | 站点管理员取消了对在企业中的组织中创建仓库的限制。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。{% if enterpriseServerVersions contains currentVersion %} +| `enterprise.config.lock_anonymous_git_access` | 站点管理员锁定匿名 Git 读取权限，以防止仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。 | +| `enterprise.config.unlock_anonymous_git_access` | 站点管理员解锁匿名 Git 读取权限，以允许仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。{% endif %} #### 议题和拉取请求 @@ -77,23 +77,23 @@ versions: #### 仓库 -| 名称 | 描述 | -| ------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo.access` | The visibility of a repository changed to private{% if enterpriseServerVersions contains currentVersion %}, public,{% endif %} or internal. | -| `repo.archive` | 已存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。 | -| `repo.add_member` | 已向仓库添加协作者。 | -| `repo.config` | 站点管理员已阻止强制推送。 更多信息请参阅“[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)”。 | -| `repo.create` | 已创建仓库。 | -| `repo.destroy` | 已删除仓库。 | -| `repo.remove_member` | 已从仓库中移除协作者。 | -| `repo.rename` | 已重命名仓库。 | -| `repo.transfer` | 用户已接受接收传输仓库的请求。 | -| `repo.transfer_start` | 用户已发送向另一用户或组织传输仓库的请求。 | -| `repo.unarchive` | 已取消存档仓库。 For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% if enterpriseServerVersions contains currentVersion %} -| `repo.config.disable_anonymous_git_access` | Anonymous Git read access is disabled for a repository. 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” | -| `repo.config.enable_anonymous_git_access` | Anonymous Git read access is enabled for a repository. 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” | -| `repo.config.lock_anonymous_git_access` | 已锁定仓库的匿名 Git 读取权限设置，阻止仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 | -| `repo.config.unlock_anonymous_git_access` | 已解锁仓库的匿名 Git 读取权限设置，允许仓库管理员更改（启用或禁用）此设置。 For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %} +| 名称 | 描述 | +| ------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.access` | 仓库的可见性已更改为私有{% if enterpriseServerVersions contains currentVersion %}、公共{% endif %} 或内部。 | +| `repo.archive` | 已存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。 | +| `repo.add_member` | 已向仓库添加协作者。 | +| `repo.config` | 站点管理员已阻止强制推送。 更多信息请参阅“[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)”。 | +| `repo.create` | 已创建仓库。 | +| `repo.destroy` | 已删除仓库。 | +| `repo.remove_member` | 已从仓库中移除协作者。 | +| `repo.rename` | 已重命名仓库。 | +| `repo.transfer` | 用户已接受接收传输仓库的请求。 | +| `repo.transfer_start` | 用户已发送向另一用户或组织传输仓库的请求。 | +| `repo.unarchive` | 已取消存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。{% if enterpriseServerVersions contains currentVersion %} +| `repo.config.disable_anonymous_git_access` | 已为仓库禁用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” | +| `repo.config.enable_anonymous_git_access` | 已为仓库启用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” | +| `repo.config.lock_anonymous_git_access` | 已锁定仓库的匿名 Git 读取权限设置，阻止仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 | +| `repo.config.unlock_anonymous_git_access` | 已解锁仓库的匿名 Git 读取权限设置，允许仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。{% endif %} #### 站点管理员工具 @@ -137,6 +137,6 @@ versions: [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [部署密钥]: /guides/managing-deploy-keys/#deploy-keys [generate token]: /articles/creating-an-access-token-for-command-line-use - [OAuth 访问令牌]: /v3/oauth/ + [OAuth 访问令牌]: /developers/apps/authorizing-oauth-apps [OAuth 应用程序]: /guides/basics-of-authentication/#registering-your-app [2fa]: /articles/about-two-factor-authentication diff --git a/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md index e39978d80b..b8afe090cd 100644 --- a/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md +++ b/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md @@ -27,7 +27,7 @@ versions: 要从 {% data variables.product.prodname_dotcom_the_website %} 导出仓库数据，请使用 Migrations API。 -Migrations API 目前正处于预览阶段，这意味着端点和参数未来可能发生变化。 要访问 Migrations API，您必须在 `Accept` 标头中提供自定义[媒体类型](/v3/media)：`application/vnd.github.wyandotte-preview+json`。 以下示例包括自定义媒体类型。 +Migrations API 目前正处于预览阶段，这意味着端点和参数未来可能发生变化。 要访问 Migrations API，您必须在 `Accept` 标头中提供自定义[媒体类型](/rest/overview/media-types)：`application/vnd.github.wyandotte-preview+json`。 以下示例包括自定义媒体类型。 ### 生成迁移存档 @@ -37,7 +37,7 @@ Migrations API 目前正处于预览阶段，这意味着端点和参数未来 2. 向迁移端点发送 `POST` 请求，开始迁移。 您需要： * 身份验证的访问令牌。 - * 想要迁移的[仓库列表](/v3/repos/#list-organization-repositories)： + * 想要迁移的[仓库列表](/rest/reference/repos#list-organization-repositories)： ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md index 294985b047..3bd214e7ca 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/categories/admin-bootcamp/ - /enterprise/admin/user-management/organizations-and-teams - /enterprise/admin/user-management/managing-organizations-in-your-enterprise -intro: '组织适合在您的公司内创建不同的用户组，例如部门或参与相似项目的组。 {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to users in other organizations, while private repositories are inaccessible to anyone but members of the organization that are granted access.' +intro: '组织适合在您的公司内创建不同的用户组，例如部门或参与相似项目的组。 属于组织的{% if currentversion == "github-ae@latest" %}内部{% else %}公共和内部{% endif %}仓库可供其他组织中的用户访问，而私有仓库只能供被授予访问权限的组织成员访问。' mapTopic: true versions: enterprise-server: '*' diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md index 31eaa6921e..aea5e17284 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### 从 {% data variables.product.prodname_dotcom_the_website %} 上的组织中删除仓库 -在解锁 {% data variables.product.prodname_dotcom_the_website %} 组织的仓库后，您应当使用[仓库删除端点](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository)删除之前迁移的每一个仓库。 您需要身份验证的访问令牌： +After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). 您需要身份验证的访问令牌： ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md index ad2d05f918..640650e6d5 100644 --- a/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ fatal: The remote end hung up unexpectedly ``` ### 延伸阅读 -- "[暂停用户](/enterprise/{{ currentVersion }}/v3/enterprise-admin/users/#suspend-a-user)" +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/zh-CN/content/developers/apps/about-apps.md b/translations/zh-CN/content/developers/apps/about-apps.md index b2affb4262..2a0de07a04 100644 --- a/translations/zh-CN/content/developers/apps/about-apps.md +++ b/translations/zh-CN/content/developers/apps/about-apps.md @@ -45,35 +45,35 @@ versions: * 如果您_只_想作为 GitHub 用户并做用户可以执行的所有操作，请不要构建 {% data variables.product.prodname_github_app %}。{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.general-apps-restrictions %}{% endif %} -To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% if currentVersion == "free-pro-team@latest" %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %} +要开始开发 {% data variables.product.prodname_github_apps %}，请先“[创建 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)”。{% if currentVersion == "free-pro-team@latest" %} 要了解如何使用 {% data variables.product.prodname_github_app %} 清单创建预配置的 {% data variables.product.prodname_github_apps %}，请参阅“[从清单创建 {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/creating-github-apps-from-a-manifest/)”。{% endif %} -### About {% data variables.product.prodname_oauth_app %}s +### 关于 {% data variables.product.prodname_oauth_app %} -OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. 此协议优先于基本验证，因为令牌可能仅限于特定类型的数据，用户可以随时撤销。 +OAuth2 是一种协议，它允许外部应用程序请求授权在不使用密码的情况下访问用户 {% data variables.product.prodname_dotcom %} 帐户中的私有信息。 此协议优先于基本验证，因为令牌可能仅限于特定类型的数据，用户可以随时撤销。 {% data reusables.apps.deletes_ssh_keys %} -An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access. +{% data variables.product.prodname_oauth_app %} 使用 {% data variables.product.prodname_dotcom %} 作为身份提供程序以验证为授予应用程序访问权限的用户。 这意味着，当用户授予 {% data variables.product.prodname_oauth_app %} 访问权限时，将授权访问其帐户有权访问的_所有_仓库，以及他们所属的、未阻止第三方访问的任何组织。 -Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_app %}s are applications that need to be hosted somewhere. +如果要创建比简单脚本的处理范围更复杂的流程，构建 {% data variables.product.prodname_oauth_app %} 是一个很好的选择。 请注意，{% data variables.product.prodname_oauth_app %} 是需要托管在某处的应用程序。 -Keep these ideas in mind when creating {% data variables.product.prodname_oauth_app %}s: +创建 {% data variables.product.prodname_oauth_app %} 时，请记住以下几点： {% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %} -* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications). -* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user. -* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_app %}s can act on _all_ of the authenticated user's repositories. -* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_app %}s authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% if currentVersion == "free-pro-team@latest" %} +* {% data variables.product.prodname_oauth_app %} 在所有 {% data variables.product.prodname_dotcom %} 中（例如，在提供用户通知时）应始终代表经身份验证的 {% data variables.product.prodname_dotcom %} 用户。 +* 通过为经身份验证的用户启用“使用 {% data variables.product.prodname_dotcom %} 进行登录”，{% data variables.product.prodname_oauth_app %} 可用作身份提供程序。 +* 如果您希望应用程序作用于单个仓库，请不要构建 {% data variables.product.prodname_oauth_app %}。 使用 `repo` OAuth 作用域，{% data variables.product.prodname_oauth_app %} 可以作用于经验证用户的_所有_仓库。 +* 不要构建 {% data variables.product.prodname_oauth_app %} 作为团队或公司的应用程序。 {% data variables.product.prodname_oauth_app %} 将验证为单个用户，因此，如果有人创建了 {% data variables.product.prodname_oauth_app %} 供公司使用，那么一旦他们离开公司，其他人将无法访问它。{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/v3/guides/basics-of-authentication/#registering-your-app)." +有关 {% data variables.product.prodname_oauth_app %} 的更多信息，请参阅“[创建 {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)”和“[注册应用程序](/rest/guides/basics-of-authentication#registering-your-app)”。 ### 个人访问令牌 [个人访问令牌](/articles/creating-a-personal-access-token-for-the-command-line/)是一个字符串，与 [OAuth 令牌](/apps/building-oauth-apps/authorizing-oauth-apps/)功能相似，您可以通过[作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)指定其权限。 个人访问令牌还与密码类似，但您能拥有很多令牌，而且可以随时撤销对每个令牌的访问权限。 -例如，您可以启用个人访问令牌，以写入仓库。 然后，如果您运行 cURL 命令或编写脚本，在仓库中[创建议题](/v3/issues/#create-an-issue)，需要传递个人访问令牌进行验证。 您可以将个人访问令牌存储为环境变量，以免每次使用时都要输入。 +例如，您可以启用个人访问令牌，以写入仓库。 然后，如果您运行 cURL 命令或编写脚本，在仓库中[创建议题](/rest/reference/issues#create-an-issue)，需要传递个人访问令牌进行验证。 您可以将个人访问令牌存储为环境变量，以免每次使用时都要输入。 使用个人访问令牌时，请牢记以下几点： @@ -85,7 +85,7 @@ For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an ### 确定要构建的集成 -Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% data variables.product.prodname_dotcom %} APIs. The following image offers some questions to ask yourself when deciding whether to use personal access tokens, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_app %}s for your integration. +开始创建集成之前，需要确定访问、验证和与 {% data variables.product.prodname_dotcom %} API 交互的最佳方式。 下图提供了一些问题，您在决定是否对集成使用个人访问令牌、{% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_app %} 时可以考虑这些问题。 ![应用程序问题流程简介](/assets/images/intro-to-apps-flow.png) @@ -94,7 +94,7 @@ Before you get started creating integrations, you need to determine the best way * 我的集成是只像我一样，还是更像一个应用程序？ * 我是否希望它作为单独的实体独立于我运行？ * 它是否能访问我可以访问的一切，或者说我想限制它的访问权限？ -* 它是简单还是复杂？ For example, personal access tokens are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting. +* 它是简单还是复杂？ 例如，个人访问令牌对简单的脚本和 cURL 有益，而 {% data variables.product.prodname_oauth_app %} 可以处理更复杂的脚本。 ### 请求支持 diff --git a/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md b/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md index f349501d5f..85df970947 100644 --- a/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md @@ -1,25 +1,25 @@ --- -title: Activating beta features for apps -intro: 'You can test new app features released in public beta for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s.' +title: 激活应用程序的测试版功能 +intro: '您可以在 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_app %} 的公开测试版中测试所发布的新应用程序功能。' versions: free-pro-team: '*' --- {% warning %} -**Warning:** Features available in public beta are subject to change. +**警告：**公开测试版中的功能可能会有变化。 {% endwarning %} -### Activating beta features for {% data variables.product.prodname_github_apps %} +### 激活 {% data variables.product.prodname_github_apps %} 的测试版功能 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} -3. Select the -{% data variables.product.prodname_github_app %} you want to enable a beta feature for. +3. 选择 +您要为其启用测试版功能的 {% data variables.product.prodname_github_app %}。 {% data reusables.apps.beta_feature_activation %} -### Activating beta features for {% data variables.product.prodname_oauth_app %}s +### 激活 {% data variables.product.prodname_oauth_app %} 的测试版功能 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} diff --git a/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md b/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md index 5e7d3c1151..edc5993b54 100644 --- a/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md @@ -38,12 +38,12 @@ versions: {% endnote %} ### 验证私钥 -{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the {% if currentVersion ver_lt "enterprise-server@2.23" %}SHA-1{% else %}SHA-256{% endif %} hash function. 您可以生成私钥指纹，然后与 {% data variables.product.product_name %} 显示的指纹相比较，以验证私钥是否与 {% data variables.product.product_name %} 上存储的公钥匹配。 +{% data variables.product.product_name %} 使用 {% if currentVersion ver_lt "enterprise-server@2.23" %}SHA-1{% else %}SHA-256{% endif %} 哈希函数为每对私钥和公钥生成指纹。 您可以生成私钥指纹，然后与 {% data variables.product.product_name %} 显示的指纹相比较，以验证私钥是否与 {% data variables.product.product_name %} 上存储的公钥匹配。 要验证私钥： 1. 在 {% data variables.product.prodname_github_app %} 开发者设置页面的“私钥”部分，查找要验证的私钥和公钥对的指纹。 更多信息请参阅[生成私钥](#generating-a-private-key)。 ![私钥指纹](/assets/images/github-apps/github_apps_private_key_fingerprint.png) -2. Generate the fingerprint of your private key (PEM) locally by using the following command: +2. 使用以下命令在本地生成私钥指纹 (PEM)： ```shell $ openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl {% if currentVersion ver_lt "enterprise-server@2.23" %}sha1 -c{% else %}sha256 -binary | openssl base64{% endif %} ``` @@ -118,13 +118,13 @@ $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github ### 作为 {% data variables.product.prodname_github_app %} 访问 API 端点 -有关获取关于 {% data variables.product.prodname_github_app %} 的高级信息所用的 REST API 端点列表，请参阅“[GitHub 应用程序](/v3/apps/)。” +有关获取关于 {% data variables.product.prodname_github_app %} 的高级信息所用的 REST API 端点列表，请参阅“[GitHub 应用程序](/rest/reference/apps)。” ### 验证为安装 通过验证为安装，您可以在 API 中为此安装执行操作。 验证为安装之前，必须创建安装访问令牌。 这些安装访问令牌由 {% data variables.product.prodname_github_app %} 用于进行身份验证。 -默认情况下，安装访问令牌的作用域为安装可访问的所有仓库。 您可以使用 `repository_ids` 参数将安装访问令牌的作用域限定于特定仓库。 See the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint for more details. 安装访问令牌具有由 {% data variables.product.prodname_github_app %} 配置的权限，一个小时后到期。 +默认情况下，安装访问令牌的作用域为安装可访问的所有仓库。 您可以使用 `repository_ids` 参数将安装访问令牌的作用域限定于特定仓库。 请参阅[创建应用程序的安装访问令牌](/rest/reference/apps#create-an-installation-access-token-for-an-app)端点了解更多详细信息。 安装访问令牌具有由 {% data variables.product.prodname_github_app %} 配置的权限，一个小时后到期。 要创建安装访问令牌，请在 API 请求的“授权”标头中加入[上文生成的](#jwt-payload) JWT： @@ -144,7 +144,7 @@ $ curl -i -X POST \ ``` {% endif %} -响应将包括您的安装访问令牌、到期日期、令牌权限及令牌可访问的仓库。 For more information about the response format, see the [Create an installation access token for an app](/v3/apps/#create-an-installation-access-token-for-an-app) endpoint. +响应将包括您的安装访问令牌、到期日期、令牌权限及令牌可访问的仓库。 有关响应格式的更多信息，请参阅[创建应用程序的安装访问令牌](/rest/reference/apps#create-an-installation-access-token-for-an-app)端点。 要使用安装访问令牌进行身份验证，请将其加入 API 请求的“授权”标头中。 @@ -168,9 +168,9 @@ $ curl -i \ ### 作为安装访问 API 端点 -有关适用于使用安装访问令牌的 {% data variables.product.prodname_github_app %} 的 REST API 端点列表，请参阅“[可用端点](/v3/apps/available-endpoints/)。” +有关适用于使用安装访问令牌的 {% data variables.product.prodname_github_app %} 的 REST API 端点列表，请参阅“[可用端点](/rest/overview/endpoints-available-for-github-apps)。” -有关与安装相关的端点的列表，请参阅“[安装](/v3/apps/installations/)。” +有关与安装相关的端点的列表，请参阅“[安装](/rest/reference/apps#installations)。” ### 由安装验证基于 HTTP 的 Git 访问权限 diff --git a/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md index 42b9da91d5..062db9e522 100644 --- a/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md @@ -14,20 +14,20 @@ versions: github-ae: '*' --- -{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser{% endif %}. +{% data variables.product.product_name %} 的 OAuth 实现支持标准[授权代码授予类型](https://tools.ietf.org/html/rfc6749#section-4.1){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}以及 OAuth 2.0 [设备授权授予](https://tools.ietf.org/html/rfc8628)（针对无法访问 web 浏览器的应用程序）{% endif %}。 -If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow). +如果您想要跳过以标准方式授权应用程序，例如测试应用程序时， 您可以使用[非 web 应用程序流程](#non-web-application-flow)。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -To authorize your OAuth app, consider which authorization flow best fits your app. +要授权您的 OAuth 应用程序，请考虑哪个授权流程最适合您的应用程序。 -- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. （不支持[隐式授予类型](https://tools.ietf.org/html/rfc6749#section-4.2)。） -- [device flow](#device-flow): Used for headless apps, such as CLI tools. +- [Web 应用程序流程](#web-application-flow)：用于授权在浏览器中运行标准 OAuth 应用程序的用户。 （不支持[隐式授予类型](https://tools.ietf.org/html/rfc6749#section-4.2)。） +- [设备流程](#device-flow)：用于无头应用程序，例如 CLI 工具。 {% else %} -For standard apps that run in the browser, use the [web application flow](#web-application-flow) to obtain an authorization code and exchange it for a token. （不支持[隐式授予类型](https://tools.ietf.org/html/rfc6749#section-4.2)。） +对于在浏览器中运行的标准应用程序，请使用 [web 应用程序流程](#web-application-flow)获取授权代码并将其更换为令牌。 （不支持[隐式授予类型](https://tools.ietf.org/html/rfc6749#section-4.2)。） {% endif %} @@ -35,11 +35,11 @@ For standard apps that run in the browser, use the [web application flow](#web-a {% note %} -**注：**如果您要构建 GitHub 应用程序，依然可以使用 OAuth web 应用程序流程，但设置方面有一些重要差异。 See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. +**注：**如果您要构建 GitHub 应用程序，依然可以使用 OAuth web 应用程序流程，但设置方面有一些重要差异。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 {% endnote %} -The web application flow to authorize users for your app is: +授权应用程序用户的 web 应用程序流程是： 1. 用户被重定向，以请求他们的 GitHub 身份 2. 用户被 GitHub 重定向回您的站点 @@ -55,7 +55,7 @@ The web application flow to authorize users for your app is: | 名称 | 类型 | 描述 | | -------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `字符串` | **必填**。 The client ID you received from GitHub when you {% if currentVersion == "free-pro-team@latest" %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}. | +| `client_id` | `字符串` | **必填**。 您{% if currentVersion == "free-pro-team@latest" %}[注册 ](https://github.com/settings/applications/new){% else %}注册{% endif %} 时从 GitHub 收到的客户端 ID。 | | `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 有关[重定向 url](#redirect-urls)，请参阅下方的详细信息。 | | `login` | `字符串` | 提供用于登录和授权应用程序的特定账户。 | | `作用域` | `字符串` | 用空格分隔的[作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)列表。 如果未提供，对于未向应用程序授权任何作用域的用户，`scope` 将默认为空白列表。 对于已向应用程序授权作用域的用户，不会显示含作用域列表的 OAuth 授权页面。 相反，通过用户向应用程序授权的作用域集，此流程步骤将自动完成。 例如，如果用户已执行两次 web 流程，且授权了一个拥有 `user` 作用域的令牌和一个拥有 `repo` 作用域的令牌，未提供 `scope` 的第三次 web 流程将收到拥有 `user` 和 `repo` 作用域的令牌。 | @@ -112,36 +112,36 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre ``` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -### Device flow +### 设备流程 {% if currentVersion ver_lt "enterprise-server@3.1" %} {% note %} -**Note:** The device flow is in public beta and subject to change. +**注：**设备流程处于公开测试阶段，可能会有变化。 {% endnote %} {% endif %} -The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. +设备流程允许您授权用户使用无头应用程序，例如 CLI 工具或 Git 凭据管理器。 -#### Overview of the device flow +#### 设备流程概述 -1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. -2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}. -3. The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token. +1. 您的应用程序会请求设备和用户验证码，并获取用户将在其中输入用户验证码的授权 URL。 +2. 应用程序提示用户在 {% data variables.product.device_authorization_url %} 中输入用户验证码。 +3. 应用程序轮询用户身份验证状态。 用户授权设备后，应用程序将能够使用新的访问令牌进行 API 调用。 -#### Step 1: App requests the device and user verification codes from GitHub +#### 第 1 步：应用程序从 GitHub 请求设备和用户验证码 POST {% data variables.product.oauth_host_code %}/login/device/code -Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication. +您的应用程序必须请求用户验证码和验证 URL，因为应用程序在下一步中提示用户进行身份验证时将使用它们。 此请求还返回设备验证代码，应用程序必须使用它们来接收访问令牌和检查用户身份验证的状态。 -##### Input Parameters +##### 输入参数 -| 名称 | 类型 | 描述 | -| ----------- | ----- | ----------------------------------------------------------------------------------------------------- | -| `client_id` | `字符串` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app. | -| `作用域` | `字符串` | The scope that your app is requesting access to. | +| 名称 | 类型 | 描述 | +| ----------- | ----- | ------------------------------------------------------------------ | +| `client_id` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的应用程序客户端 ID。 | +| `作用域` | `字符串` | 应用程序请求访问的范围。 | ##### 响应 @@ -167,39 +167,39 @@ Your app must request a user verification code and verification URL that the app ``` {% endif %} -##### Response parameters +##### 响应参数 -| 名称 | 类型 | 描述 | -| ------------------ | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `device_code` | `字符串` | The device verification code is 40 characters and used to verify the device. | -| `user_code` | `字符串` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle. | -| `verification_uri` | `字符串` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}. | -| `expires_in` | `整数` | The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes. | -| `interval` | `整数` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error. | +| 名称 | 类型 | 描述 | +| ------------------ | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `device_code` | `字符串` | 设备验证码为 40 个字符，用于验证设备。 | +| `user_code` | `字符串` | 用户验证码显示在设备上，以便用户可以在浏览器中输入该代码。 此代码为 8 个字符，中间有连字符。 | +| `verification_uri` | `字符串` | 用户需要在其中输入 `user_code` 的验证 URL：{% data variables.product.device_authorization_url %}。 | +| `expires_in` | `整数` | `device_code` 和 `user_code` 到期前的秒数。 默认值为 900 秒或 15 分钟。 | +| `间隔` | `整数` | 发出新的访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) 以完成设备授权之前必须经过的最小秒数。 例如，如果间隔为 5，则只有经过 5 秒后才能发出新请求。 如果您在 5 秒内发出多个请求，则将达到速率限制并收到 `slow_down` 错误。 | -#### Step 2: Prompt the user to enter the user code in a browser +#### 第 2 步：提示用户在浏览器中输入用户代码 -Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}. +您的设备将显示用户验证码并提示用户在 {% data variables.product.device_authorization_url %} 中输入该代码。 - ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png) + ![用于输入设备上显示的用户验证码的字段](/assets/images/github-apps/device_authorization_page_for_user_code.png) -#### Step 3: App polls GitHub to check if the user authorized the device +#### 第 3 步：应用程序轮询 GitHub 以检查用户是否授权设备 POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)." +应用程序将发出设备授权请求以轮询 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`，直到设备和用户代码到期或者用户已使用有效的用户代码成功授权该应用程序。 应用程序必须使用在第 1 步中检索到的最小轮询 `interval`，以避免速率限制错误。 更多信息请参阅“[设备流程的速率限制](#rate-limits-for-the-device-flow)”。 -The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`. +用户必须在 15 分钟（或 900 秒内）内输入有效代码。 15 分钟后，您需要使用 `POST {% data variables.product.oauth_host_code %}/login/device/code` 请求新的设备授权代码。 -Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user. +一旦用户授权， 应用程序将收到一个访问令牌，该令牌可用于代表用户向 API 发出请求。 -##### Input parameters +##### 输入参数 -| 名称 | 类型 | 描述 | -| ------------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端 ID。 | -| `device_code` | `字符串` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request. | -| `grant_type` | `字符串` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`. | +| 名称 | 类型 | 描述 | +| ------------- | ----- | ------------------------------------------------------------------------------------------------------------------ | +| `client_id` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端 ID。 | +| `device_code` | `字符串` | **必填。**您从 `POST {% data variables.product.oauth_host_code %}/login/device/code` 请求收到的设备验证码。 | +| `grant_type` | `字符串` | **必填。**授予类型必须是 `urn:ietf:params:oauth:grant-type:device_code`。 | ##### 响应 @@ -211,36 +211,36 @@ Once the user has authorized, the app will receive an access token that can be u } ``` -#### Rate limits for the device flow +#### 设备流程的速率限制 -When a user submits the verification code on the browser, there is a there is a rate limit of 50 submissions in an hour per application. +当用户在浏览器上提交验证码时，每个应用程序在一个小时内的提交速率限制为 50 个。 -If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). +如果您在请求之间所需的最短时间段（或 `interval`）内发出多个访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`)，您将达到速率限制并收到 `slow_down` 错误响应。 `slow_down` 错误响应将给最近的`间隔`增加 5 秒。 更多信息请参阅“[设备流程的错误](#errors-for-the-device-flow)”。 -#### Error codes for the device flow +#### 设备流程的错误代码 -| Error code | 描述 | -| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `authorization_pending` | This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. | -| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use. | -| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code. | -| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. | -| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow. | -| `incorrect_device_code` | The device_code provided is not valid. | -| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again. | +| 错误代码 | 描述 | +| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `authorization_pending` | 授权请求待处理并且用户尚未输入用户代码时，将发生此错误。 应用程序应该继续轮询 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`，但不会超过 [`interval`](#response-parameters)，它规定了每个请求之间的最小秒数。 | +| `slow_down` | 当您收到 `slow_down` 错误时，使用 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 请求之间的所需最小 `interval` 或时间段将额外增加 5 秒。 例如，如果两次请求之间的开始间隔至少需要 5 秒，并且您收到了 `slow_down` 错误响应，则现在必须等待至少 10 秒才能发出新的 OAuth 访问令牌请求。 错误响应包括您必须使用的新 `interval`。 | +| `expired_token` | 如果设备代码已过期，您将会看到 `token_expendent` 错误。 您必须发出新的设备代码请求。 | +| `unsupported_grant_type` | 授予类型必须为 `urn:ietf:params:oauth:grant-type:device_code`，并在您轮询 OAuth 令牌请求 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 时作为输入参数包括在内。 | +| `incorrect_client_credentials` | 对于设备流程，您必须传递应用程序的客户端 ID，您可以在应用程序设置页面上找到该 ID。 设备流程不需要 `client_secret`。 | +| `incorrect_device_code` | 提供的 device_code 无效。 | +| `access_denied` | 当用户在授权过程中单击取消时，您将收到 `access_denied` 错误，用户将无法再次使用验证码。 | -For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)." +更多信息请参阅“[OAuth 2.0 设备授权授予](https://tools.ietf.org/html/rfc8628#section-3.5)”。 {% endif %} ### 非 Web 应用程序流程 -非 web 身份验证适用于测试等有限的情况。 如果您需要，可以使用[基本验证](/v3/auth#basic-authentication)，通过[个人访问令牌设置页面](/articles/creating-an-access-token-for-command-line-use)创建个人访问令牌。 此方法支持用户随时撤销访问权限。 +非 web 身份验证适用于测试等有限的情况。 如果您需要，可以使用[基本验证](/rest/overview/other-authentication-methods#basic-authentication)，通过[个人访问令牌设置页面](/articles/creating-an-access-token-for-command-line-use)创建个人访问令牌。 此方法支持用户随时撤销访问权限。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**注：**使用非 web 应用流程创建 OAuth2 令牌时，如果您或您的用户已启用双重身份验证，请确保明白如何[使用双重身份验证](/v3/auth/#working-with-two-factor-authentication)。 +**注：**使用非 web 应用流程创建 OAuth2 令牌时，如果您或您的用户已启用双重身份验证，请确保明白如何[使用双重身份验证](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)。 {% endnote %} {% endif %} @@ -289,7 +289,7 @@ For more information, see the "[OAuth 2.0 Device Authorization Grant](https://to {% tip %} -**提示：**要详细了解您的 OAuth 应用程序可以为用户访问的资源，请参阅“[为用户发现资源](/v3/guides/discovering-resources-for-a-user/)。” +**提示：**要详细了解您的 OAuth 应用程序可以为用户访问的资源，请参阅“[为用户发现资源](/rest/guides/discovering-resources-for-a-user)。” {% endtip %} @@ -298,5 +298,5 @@ For more information, see the "[OAuth 2.0 Device Authorization Grant](https://to * "[对授权请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" * "[对 OAuth 应用程序访问令牌请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -* "[Device flow errors](#errors-for-the-device-flow)" +* "[设备流程错误](#errors-for-the-device-flow)" {% endif %} diff --git a/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-github-app.md b/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-github-app.md index 557cb1d480..07358a2a91 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-github-app.md +++ b/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-github-app.md @@ -15,7 +15,7 @@ versions: 创建 GitHub 应用程序后，可以通过上传徽标和选择背景颜色自定义应用程序的徽章。 徽章是圆形徽章内的方形徽标图像。 您可以为徽章选择背景颜色，以便从视觉上与应用程序区分开。 -徽标应为 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获得最佳渲染效果，建议图像大小至少为 200px x 200px。 {% if currentVersion == "free-pro-team@latest" %}See "[Tips for logo and badge images](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" for more guidance on customizing badges.{% endif %} +徽标应为 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获得最佳渲染效果，建议图像大小至少为 200px x 200px。 {% if currentVersion == "free-pro-team@latest" %}请参阅“[徽标和徽章图像提示](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)”，了解更详细的自定义徽章指南。{% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -31,7 +31,7 @@ versions: {% data reusables.user-settings.modify_github_app %} 5. 在“Display information（显示信息）”中，从本地文件夹拖放图像，或单击 **Upload a logo（上传徽标）**，从计算机选择图像。 ![上传徽标](/assets/images/github-apps/github_apps_upload_logo.png) 6. 裁剪图片。 完成后，单击 **Set new avatar（设置新头像）**。 ![裁剪和设置徽标 ](/assets/images/github-apps/github_apps_crop_and_set_avatar.png) -7. 在“Badge background color（徽章背景颜色）”中，输入徽章背景颜色的[十六进制颜色代码](http://www.color-hex.com/)。 {% if currentVersion == "free-pro-team@latest" %}**Note:** The "Badge background color" input field will only appear after you upload an application logo.{% endif %} ![徽章背景颜色](/assets/images/github-apps/github_apps_badge_background_color.png) +7. 在“Badge background color（徽章背景颜色）”中，输入徽章背景颜色的[十六进制颜色代码](http://www.color-hex.com/)。 {% if currentVersion == "free-pro-team@latest" %}**注：**只有在上传应用程序徽标后才会显示“徽章背景颜色”输入字段。{% endif %} ![徽章背景颜色](/assets/images/github-apps/github_apps_badge_background_color.png) {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-oauth-app.md b/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-oauth-app.md index 0fdfa6a9a9..a05bb5f81a 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-oauth-app.md +++ b/translations/zh-CN/content/developers/apps/creating-a-custom-badge-for-your-oauth-app.md @@ -1,5 +1,5 @@ --- -title: Creating a custom badge for your OAuth App +title: 为 OAuth 应用程序创建自定义徽章 intro: '{% data reusables.shortdesc.creating_custom_badges_oauth_apps %}' redirect_from: - /apps/building-oauth-apps/creating-custom-badges-for-oauth-apps @@ -9,13 +9,13 @@ versions: github-ae: '*' --- -By default, a new OAuth App will have an automatically generated [identicon](https://github.com/blog/1586-identicons). 默认肖像徽章如下所示： +默认情况下，新的 OAuth 应用程序拥有一个自动生成的[默认肖像](https://github.com/blog/1586-identicons)。 默认肖像徽章如下所示： ![默认肖像](/assets/images/identicon.png) -After you create an OAuth App, you can customize the app's badge by uploading a logo and selecting a background color. 徽章是圆形徽章内的方形徽标图像。 You can choose a background color for the badge, which can be used to visually distinguish your app. +创建 OAuth 应用程序后，可以通过上传徽标和选择背景颜色自定义应用程序的徽章。 徽章是圆形徽章内的方形徽标图像。 您可以为徽章选择背景颜色，以便从视觉上区分您的应用程序。 -徽标应为 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获得最佳渲染效果，建议图像大小至少为 200px x 200px。 {% if currentVersion == "free-pro-team@latest" %}See "[Tips for logo and badge images](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" for more guidance on customizing badges.{% endif %} +徽标应为 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获得最佳渲染效果，建议图像大小至少为 200px x 200px。 {% if currentVersion == "free-pro-team@latest" %}请参阅“[徽标和徽章图像提示](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)”，了解更详细的自定义徽章指南。{% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -29,10 +29,10 @@ After you create an OAuth App, you can customize the app's badge by uploading a {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %} {% data reusables.user-settings.modify_oauth_app %} -1. In "Application logo", drag-and-drop an image from a local folder or click **Upload new logo** to select an image from your computer. ![上传徽标](/assets/images/oauth-apps/oauth_apps_upload_logo.png) -6. 裁剪图片。 When you're done, click **Set new application logo**. ![裁剪和设置徽标](/assets/images/oauth-apps/oauth_apps_crop_and_set_logo.png) +1. 在“Application logo（应用程序徽标）”中，从本地文件夹拖放图像，或单击 **Upload new logo（上传新徽标）**，从计算机选择图像。 ![上传徽标](/assets/images/oauth-apps/oauth_apps_upload_logo.png) +6. 裁剪图片。 完成后，单击 **Set new application logo（设置新应用程序徽标）**。 ![裁剪和设置徽标](/assets/images/oauth-apps/oauth_apps_crop_and_set_logo.png) 7. 在“Badge background color（徽章背景颜色）”中，输入徽章背景颜色的[十六进制颜色代码](http://www.color-hex.com/)。 -{% if currentVersion == "free-pro-team@latest" %}**Note:** The "Badge background color" input field will be visible after an application logo has been uploaded.{% endif %} +{% if currentVersion == "free-pro-team@latest" %}**注：**“徽章背景颜色”输入字段将在上传应用程序徽标后显示。{% endif %} ![徽章背景颜色](/assets/images/oauth-apps/oauth_apps_badge_background_color.png) {% data reusables.user-settings.update_oauth_app %} diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md index bb7b09c169..80a92d8860 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -1,6 +1,6 @@ --- -title: Creating a GitHub App from a manifest -intro: 'A GitHub App Manifest is a preconfigured GitHub App you can share with anyone who wants to use your app in their personal repositories. The manifest flow allows someone to quickly create, install, and start extending a GitHub App without needing to register the app or connect the registration to the hosted app code.' +title: 从清单创建 GitHub 应用程序 +intro: 'GitHub 应用程序清单是预先配置的 GitHub 应用程序，您可以与希望在其个人仓库中使用您的应用程序的任何用户分享它。 清单流程允许用户快速创建、安装和开始扩展 GitHub 应用程序，而无需注册应用程序或将注册连接到托管应用代码。' redirect_from: - /apps/building-github-apps/creating-github-apps-from-a-manifest versions: @@ -10,65 +10,65 @@ versions: --- -### About GitHub App Manifests +### 关于 GitHub 应用程序清单 -When someone creates a GitHub App from a manifest, they only need to follow a URL and name the app. The manifest includes the permissions, events, and webhook URL needed to automatically register the app. The manifest flow creates the GitHub App registration and retrieves the app's webhook secret, private key (PEM file), and GitHub App ID. The person who creates the app from the manifest will own the app and can choose to [edit the app's configuration settings](/apps/managing-github-apps/modifying-a-github-app/), delete it, or transfer it to another person on GitHub. +当有人从清单创建 GitHub 应用程序时，他们只需遵循 URL 并命名应用程序即可。 清单包括自动注册应用程序所需的权限、事件和 web 挂钩 URL。 清单流程创建 GitHub 应用程序注册并检索应用程序的 web 挂钩密钥、私钥 （PEM 文件） 和 GitHub 应用程序 ID。 从清单创建应用程序的人将拥有该应用程序，并且可以选择[编辑应用程序的配置设置](/apps/managing-github-apps/modifying-a-github-app/)、删除它或将其转让给 GitHub 上的其他人。 -You can use [Probot](https://probot.github.io/) to get started with GitHub App Manifests or see an example implementation. See "[Using Probot to implement the GitHub App Manifest flow](#using-probot-to-implement-the-github-app-manifest-flow)" to learn more. +您可以使用 [Probot](https://probot.github.io/) 开始使用 GitHub 应用程序清单或查看示例实现。 更多信息请参阅“[使用 Probot 实现 GitHub 应用程序清单流程](#using-probot-to-implement-the-github-app-manifest-flow)”。 -Here are some scenarios where you might use GitHub App Manifests to create preconfigured apps: +以下是您可以使用 GitHub 应用程序清单来创建预配置应用程序的一些场景： -* Help new team members come up-to-speed quickly when developing GitHub Apps. -* Allow others to extend a GitHub App using the GitHub APIs without requiring them to configure an app. -* Create GitHub App reference designs to share with the GitHub community. -* Ensure you deploy GitHub Apps to development and production environments using the same configuration. -* Track revisions to a GitHub App configuration. +* 开发 GitHub 应用程序时，帮助新的团队成员快速上手。 +* 允许其他人使用 GitHub API 扩展 GitHub 应用程序，而无需他们配置应用程序。 +* 创建 GitHub 应用程序参考设计，与 GitHub 社区分享。 +* 确保使用相同的配置将 GitHub 应用程序部署到开发和生产环境。 +* 跟踪对 GitHub 应用程序配置的修订。 -### Implementing the GitHub App Manifest flow +### 实现 GitHub 应用程序清单流程 -The GitHub App Manifest flow uses a handshaking process similar to the [OAuth flow](/apps/building-oauth-apps/authorizing-oauth-apps/). The flow uses a manifest to [register a GitHub App](/apps/building-github-apps/creating-a-github-app/) and receives a temporary `code` used to retrieve the app's private key, webhook secret, and ID. +GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-apps/authorizing-oauth-apps/)的握手过程。 该流程使用清单[注册 GitHub 应用程序](/apps/building-github-apps/creating-a-github-app/)，并接收用于检索应用程序私钥、web 挂钩密钥和 ID 的临时 `code`。 {% note %} -**Note:** You must complete all three steps in the GitHub App Manifest flow within one hour. +**注：**您必须在一小时内完成 GitHub 应用程序清单流程中的所有三个步骤。 {% endnote %} -Follow these steps to implement the GitHub App Manifest flow: +按照以下步骤实现 GitHub 应用程序清单流程： -1. You redirect people to GitHub to create a new GitHub App. -1. GitHub redirects people back to your site. -1. You exchange the temporary code to retrieve the app configuration. +1. 将人员重定向到 GitHub 以创建新的 GitHub 应用程序。 +1. GitHub 将人员重定向回您的站点。 +1. 交换临时代码以检索应用程序配置。 -#### 1. You redirect people to GitHub to create a new GitHub App +#### 1. 将人员重定向到 GitHub 以创建新的 GitHub 应用程序。 -To redirect people to create a new GitHub App, [provide a link](#examples) for them to click that sends a `POST` request to `https://github.com/settings/apps/new` for a user account or `https://github.com/organizations/ORGANIZATION/settings/apps/new` for an organization account, replacing `ORGANIZATION` with the name of the organization account where the app will be created. +要重定向人员以创建新的 GitHub 应用程序，请[提供一个链接](#examples)，供他们单击以将 `POST` 请求发送到用户帐户的 `https://github.com/settings/apps/new` 或组织帐户的 `https://github.com/organizations/ORGANIZATION/settings/apps/new`，其中的 `ORGANIZATION` 替换为要在其中创建应用程序的组织帐户的名称。 -You must include the [GitHub App Manifest parameters](#github-app-manifest-parameters) as a JSON-encoded string in a parameter called `manifest`. You can also include a `state` [parameter](#parameters) for additional security. +必须将 [GitHub 应用程序清单参数](#github-app-manifest-parameters)作为 JSON 编码的字符串包含在名为 `manifest` 的参数中。 还可以包括 `state` [参数](#parameters) 以增加安全性。 -The person creating the app will be redirected to a GitHub page with an input field where they can edit the name of the app you included in the `manifest` parameter. If you do not include a `name` in the `manifest`, they can set their own name for the app in this field. +创建应用程序的人将被重定向到含有输入字段的 GitHub 页面，他们可以在其中编辑您包含在 `manifest` 参数中的应用程序名称。 如果您在 `manifest` 中没有包含 `name`，他们可以在此字段中为应用程序设置自己的名称。 -![Create a GitHub App Manifest](/assets/images/github-apps/create-github-app-manifest.png) +![创建 GitHub 应用程序清单](/assets/images/github-apps/create-github-app-manifest.png) -##### GitHub App Manifest parameters +##### GitHub 应用程序清单参数 - | 名称 | 类型 | 描述 | - | --------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `字符串` | The name of the GitHub App. | - | `url` | `字符串` | **Required.** The homepage of your GitHub App. | - | `hook_attributes` | `对象` | The configuration of the GitHub App's webhook. | - | `redirect_url` | `字符串` | The full URL to redirect to after the person installs the GitHub App. | - | `说明` | `字符串` | A description of the GitHub App. | - | `public` | `布尔值` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | - | `default_events` | `数组` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | - | `default_permissions` | `对象` | The set of [permissions](/v3/apps/permissions/) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | + | 名称 | 类型 | 描述 | + | --------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------- | + | `name` | `字符串` | GitHub 应用程序的名称。 | + | `url` | `字符串` | **必填。**GitHub 应用程序的主页。 | + | `hook_attributes` | `对象` | GitHub 应用程序 web 挂钩的配置 | + | `redirect_url` | `字符串` | 用户安装 GitHub 应用程序后要重定向到的完整 URL。 | + | `说明` | `字符串` | GitHub 应用程序的说明。 | + | `public` | `布尔值` | 当 GitHub 应用程序可供公众使用时，设置为 `true` ；当它仅供应用程序的所有者访问时，设置为 `false`。 | + | `default_events` | `数组` | GitHub 应用程序订阅的[事件](/webhooks/event-payloads)列表。 | + | `default_permissions` | `对象` | GitHub 应用程序所需的[权限](/rest/reference/permissions-required-for-github-apps)集。 对象的格式使用键的权限名称（例如 `issues`）和值的访问类型（例如 `write`）。 | -The `hook_attributes` object has the following key: +`hook_attributes` 对象含有以下键： -| 名称 | 类型 | 描述 | -| -------- | ----- | ---------------------------------------------------------------------------------- | -| `url` | `字符串` | **Required.** The URL of the server that will receive the webhook `POST` requests. | -| `active` | `布尔值` | Deliver event details when this hook is triggered, defaults to true. | +| 名称 | 类型 | 描述 | +| -------- | ----- | ------------------------------------- | +| `url` | `字符串` | **必填。**将接收 web 挂钩 `POST` 请求的服务器的 URL。 | +| `active` | `布尔值` | 当此挂钩被触发时提供事件详细信息，默认值为 true。 | ##### 参数 @@ -78,7 +78,7 @@ The `hook_attributes` object has the following key: ##### 示例 -This example uses a form on a web page with a button that triggers the `POST` request for a user account: +此示例使用网页上的表单，其中包含一个按钮，该按钮可触发用户帐户的 `POST` 请求： ```
@@ -109,7 +109,7 @@ This example uses a form on a web page with a button that triggers the `POST` re }) ``` -This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app. +此示例使用网页上的表单，其中包含一个按钮，该按钮可触发组织帐户的 `POST` 请求： 将 `ORGANIZATION` 替换为要在其中创建应用程序的组织帐户的名称。 ``` @@ -141,25 +141,25 @@ This example uses a form on a web page with a button that triggers the `POST` re ``` -#### 2. GitHub redirects people back to your site +#### 2. GitHub 将人员重定向回您的站点 -When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. 例如： +当用户单击**创建 GitHub 应用程序**时，GitHub 将使用代码参数中的临时 `code` 重定向回 `redirect_url` 。 例如： https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 -If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. 例如： +如果您提供了 `state` 参数，您还会在 `redirect_url` 中看到该参数。 例如： https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 -#### 3. You exchange the temporary code to retrieve the app configuration +#### 3. 交换临时代码以检索应用程序配置 -To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. +要完成握手，请在 `POST` 请求中将临时 `code` 发送到[从清单创建 GitHub 应用程序](/rest/reference/apps#create-a-github-app-from-a-manifest)端点。 响应将包括 `id`（GitHub 应用程序 ID）、`pem`（私钥）和 `webhook_secret`。 GitHub 会自动为应用程序创建一个 web 挂钩密钥。 您可以将这些值存储在应用程序服务器上的环境变量中。 例如，如果您的应用程序使用 [dotenv](https://github.com/bkeepers/dotenv) 来存储环境变量，则您将把变量存储在应用程序的 `.env` 文件中。 -You must complete this step of the GitHub App Manifest flow within one hour. +您必须在一小时内完成 GitHub 应用程序清单流程中的此步骤。 {% note %} -**Note:** This endpoint is rate limited. See [Rate limits](/v3/rate_limit/) to learn how to get your current rate limit status. +**注：**此端点受速率限制。 请参阅[速率限制](/rest/reference/rate-limit)，了解如何获取当前速率限制状态。 {% endnote %} @@ -170,25 +170,25 @@ You must complete this step of the GitHub App Manifest flow within one hour. POST /app-manifests/:code/conversions -For more information about the endpoint's response, see [Create a GitHub App from a manifest](/v3/apps/#create-a-github-app-from-a-manifest). +有关端点响应的更多信息，请参阅[从清单创建 GitHub 应用程序](/rest/reference/apps#create-a-github-app-from-a-manifest)。 -When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time. +清单流程的最后一步完成后，从流程创建应用程序的人将是注册 GitHub 应用程序的所有者，他们可以将其安装到他们的任何个人仓库中。 他们可以选择使用 GitHub API 扩展应用程序、将所有权转让给其他人或者随时删除它。 -### Using Probot to implement the GitHub App Manifest flow +### 使用 Probot 实现 GitHub 应用程序清单流程 -[Probot](https://probot.github.io/) is a framework built with [Node.js](https://nodejs.org/) that performs many of the tasks needed by all GitHub Apps, like validating webhooks and performing authentication. Probot implements the [GitHub App manifest flow](#implementing-the-github-app-manifest-flow), making it easy to create and share GitHub App reference designs with the GitHub community. +[Probot](https://probot.github.io/) 是一个使用 [Node.js](https://nodejs.org/) 构建的框架，可执行所有 GitHub 应用程序所需的许多任务，例如验证 web 挂钩和执行身份验证。 Probot 实现 [GitHub 应用程序清单流程](#implementing-the-github-app-manifest-flow)，便于创建 GitHub 应用程序参考设计并与 GitHub 社区分享。 -To create a Probot App that you can share, follow these steps: +要创建可以分享的 Probot 应用程序，请遵循以下步骤： -1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app). -1. Open the project you created, and customize the settings in the `app.yml` file. Probot uses the settings in `app.yml` as the [GitHub App Manifest parameters](#github-app-manifest-parameters). -1. Add your application's custom code. -1. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally) or [host it anywhere you'd like](#hosting-your-app-with-glitch). When you navigate to the hosted app's URL, you'll find a web page with a **Register GitHub App** button that people can click to create a preconfigured app. The web page below is Probot's implementation of [step 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) in the GitHub App Manifest flow: +1. [生成新的 GitHub 应用程序](https://probot.github.io/docs/development/#generating-a-new-app)。 +1. 打开您创建的项目，自定义 `app.yml` 文件中的设置。 Probot 使用 `app.yml` 中的设置作为 [GitHub 应用程序清单参数](#github-app-manifest-parameters)。 +1. 添加应用程序的自定义代码。 +1. [在本地运行 GitHub 应用程序](https://probot.github.io/docs/development/#running-the-app-locally)或[将其托管在您想要的任何位置](#hosting-your-app-with-glitch)。 导航到托管应用程序的 URL 时，您会发现一个包含**注册 GitHub 应用程序**按钮的网页，用户可以单击该按钮创建预配置的应用程序。 以下网页是 Probot 实现 GitHub 应用程序清单流程中的[第 1 步](#1-you-redirect-people-to-github-to-create-a-new-github-app)： -![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png) +![注册 Probot GitHub 应用程序](/assets/images/github-apps/github_apps_probot-registration.png) -Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file and sets the `APP_ID`, `PRIVATE_KEY`, and `WEBHOOK_SECRET` environment variables with the values [retrieved from the app configuration](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). +Probot 使用 [dotenv](https://github.com/bkeepers/dotenv) 创建 `.env` 文件，并设置 `APP_ID`、`PRIVATE_KEY` 和 `WEBHOOK_SECRET` 环境变量，变量值[从应用程序配置中检索](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)。 -#### Hosting your app with Glitch +#### 使用 Glitch 托管应用程序 -You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/v3/checks/) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. +您可以看到一个使用 [Glitch](https://glitch.com/) 托管和分享应用程序的[示例 Probot 应用程序](https://glitch.com/~auspicious-aardwolf)。 该示例使用[检查 API](/rest/reference/checks)，并在 `app.yml` 文件中选择必要的检查 API 事件和权限。 Glitch 是一个允许您“重新组合自己的”应用程序的工具。 重新组合应用程序将创建一个 Glitch 托管和部署的应用程序副本。 请参阅“[关于 Glitch](https://glitch.com/about/)”了解如何重新组合 Glitch 应用程序。 diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md index 1f48e3acff..c762436959 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -1,6 +1,6 @@ --- -title: Creating a GitHub App using URL parameters -intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.' +title: 使用 URL 参数创建 GitHub 应用程序 +intro: '您可以使用 URL [查询参数](https://en.wikipedia.org/wiki/Query_string) 预选新 {% data variables.product.prodname_github_app %} 的设置，以快速设置新 {% data variables.product.prodname_github_app %} 的配置。' redirect_from: - /apps/building-github-apps/creating-github-apps-using-url-parameters versions: @@ -10,112 +10,112 @@ versions: --- -### About {% data variables.product.prodname_github_app %} URL parameters +### 关于 {% data variables.product.prodname_github_app %} URL 参数 -You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account: -* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new` -* **Organization account:** `{% data variables.product.oauth_host_code %}/:org/settings/apps/new` +您可以将查询参数添加到这些 URL 中，以便在个人或组织帐户上预选 {% data variables.product.prodname_github_app %} 的配置： +* **用户帐户：** `{% data variables.product.oauth_host_code %}/settings/apps/new` +* **组织帐户：** `{% data variables.product.oauth_host_code %}/:org/settings/apps/new` -The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app. +创建应用程序的人在提交应用程序之前，可以从 {% data variables.product.prodname_github_app %} 注册页面编辑预选值。 如果您没有在 URL 查询字符串中包含必需的参数，例如 `name`，则创建应用程序的人在提交该应用程序之前需要输入值。 -The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: +以下 URL 使用预配置的说明和回调 URL 创建名为 `octocat-github-app` 的新公共应用程序。 此 URL 还选择了 `checks` 的读取和写入权限，订阅了 `check_run` 和 `check_suite` web 挂钩事件，并选择了在安装过程中请求用户授权 (OAuth) 的选项： ``` {% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite ``` -The complete list of available query parameters, permissions, and events is listed in the sections below. +下面几节列出了可用查询参数、权限和事件的完整列表。 -### {% data variables.product.prodname_github_app %} configuration parameters +### {% data variables.product.prodname_github_app %} 配置参数 - | 名称 | 类型 | 描述 | - | -------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `字符串` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. | - | `说明` | `字符串` | A description of the {% data variables.product.prodname_github_app %}. | - | `url` | `字符串` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage. | - | `callback_url` | `字符串` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. | - | `request_oauth_on_install` | `布尔值` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. | - | `setup_url` | `字符串` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation. | - | `setup_on_update` | `布尔值` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed. | - | `public` | `布尔值` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app. | - | `webhook_url` | `字符串` | The full URL that you would like to send webhook event payloads to. | - | `webhook_secret` | `字符串` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details. | - | `事件` | `字符串数组` | Web 挂钩事件. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`. | - | `域` | `字符串` | The URL of a content reference. | - | `single_file_name` | `字符串` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - | `single_file_paths` | `字符串数组` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %} + | 名称 | 类型 | 描述 | + | -------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | + | `name` | `字符串` | {% data variables.product.prodname_github_app %} 的名称。 给应用程序一个清晰简洁的名称。 应用程序不能与现有 GitHub 用户同名，除非它是您自己的用户或组织的名称。 当您的集成执行操作时，应用程序名称的缓存版本将显示在用户界面上。 | + | `说明` | `字符串` | {% data variables.product.prodname_github_app %} 的说明。 | + | `url` | `字符串` | 您的 {% data variables.product.prodname_github_app %} 网站主页的完整 URL。 | + | `callback_url` | `字符串` | 在用户授权安装后重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。 | + | `request_oauth_on_install` | `布尔值` | 如果应用程序授权用户使用 OAuth 流程，您可以将此选项设置为 `true`，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则 `setup_url` 将不可用，用户在安装应用程序后将被重定向到您的 `callback_url`。 | + | `setup_url` | `字符串` | 在用户安装 {% data variables.product.prodname_github_app %} 后重定向到的完整 URL（如果应用程序在安装之后需要额外设置）。 | + | `setup_on_update` | `布尔值` | 设置为 `true` 可在更新安装后（例如在添加或删除仓库之后）将用户重定向到设置 URL。 | + | `public` | `布尔值` | 当 {% data variables.product.prodname_github_app %} 可供公众使用时，设置为 `true` ；当它仅供应用程序的所有者访问时，设置为 `false`。 | + | `webhook_url` | `字符串` | 要向其发送 web 挂钩事件有效负载的完整 URL。 | + | `webhook_secret` | `字符串` | 您可以指定一个密钥来保护 web 挂钩。 更多信息请参阅“[保护 web 挂钩](/webhooks/securing/)”。 | + | `事件` | `字符串数组` | Web 挂钩事件. 某些 web 挂钩事件需要您对资源有 `read` 或 `write` 权限，才能在注册新 {% data variables.product.prodname_github_app %} 时选择事件。 有关可用事件及其所需权限，请参阅“[{% data variables.product.prodname_github_app %} web 挂钩事件](#github-app-webhook-events)”一节。 您可以在查询字符串中选择多个事件。 例如，`events[]=public&events[]=label`。 | + | `域` | `字符串` | 内容引用的 URL。 | + | `single_file_name` | `字符串` | 这是一种范围狭窄的权限，允许应用程序访问任何仓库中的单个文件。 当您将 `single_file` 权限设置为 `read` 或 `write` 时，此字段提供 {% data variables.product.prodname_github_app %} 将要管理的单个文件的路径。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 如果您需要管理多个文件，请参阅下面的 `single_file_paths`。 {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + | `single_file_paths` | `字符串数组` | 这允许应用程序访问仓库中的最多 10 个指定文件。 当您将 `single_file` 权限设置为 `read` 或 `write` 时，此数组可存储 {% data variables.product.prodname_github_app %} 将要管理的最多 10 个文件的路径。 这些文件都接收由 `single_file` 设置的相同权限，没有单独的权限。 配置了两个或更多文件时，API 将返回 `multiple_single_files=true`，否则它将返回 `multiple_single_files=false`。{% endif %} -### {% data variables.product.prodname_github_app %} permissions +### {% data variables.product.prodname_github_app %} 权限 -You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission. +您可以在查询字符串中选择权限：使用下表中的权限名称作为查询参数名称，使用权限类型作为查询值。 例如，要在用户界面中为 `contents` 选择 `Read & write` 权限，您的查询字符串将包括 `&contents=write`。 要在用户界面中为 `blocking` 选择 `Read-only` 权限，您的查询字符串将包括 `&blocking=read`。 要在用户界面中为 `checks` 选择 `no-access` ，您的查询字符串将包括 `checks` 权限。 -| 权限 | 描述 | -| -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`管理`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/v3/users/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`检查`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/v3/checks/). Can be one of: `none`, `read`, or `write`. | -| `content_references` | Grants access to the "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. | -| [`内容`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. | -| [`部署`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/v3/users/emails/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`关注者`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/v3/users/followers/). Can be one of: `none`, `read`, or `write`. | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/v3/users/gpg_keys/). Can be one of: `none`, `read`, or `write`. | -| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/v3/issues/). Can be one of: `none`, `read`, or `write`. | -| [`键`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/v3/users/keys/). Can be one of: `none`, `read`, or `write`. | -| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`元数据`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. | -| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/v3/orgs/#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`. | -| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/v3/orgs/#get-an-organization)" endpoint. Can be one of: `none` or `read`. | -| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} -| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/v3/orgs/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -| [`页面`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`. | -| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/v3/users/#get-a-user)" endpoint. Can be one of: `none` or `read`. | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/v3/repos/hooks/). Can be one of: `none`, `read`, or `write`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`. | -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/v3/repos/contents/). Can be one of: `none`, `read`, or `write`. | -| [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/v3/activity/starring/). Can be one of: `none`, `read`, or `write`. | -| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/v3/repos/statuses/). Can be one of: `none`, `read`, or `write`. | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/v3/teams/discussions/) and the [Team Discussion Comments API](/v3/teams/discussion_comments/). Can be one of: `none`, `read`, or `write`. | -| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. | -| `关注` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. | +| 权限 | 描述 | +| -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`管理`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | 对用于组织和仓库管理的各种端点授予访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" %} +| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | 授予对[阻止用户 API](/rest/reference/users#blocking) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} +| [`检查`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | 授予对[检查 API](/rest/reference/checks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `content_references` | 授予对“[创建内容附件](/rest/reference/apps#create-a-content-attachment)”端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`内容`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | 对用于修改仓库内容的各种端点授予访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`部署`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | 授予对[部署 API](/rest/reference/repos#deployments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | 授予对[电子邮件 API](/rest/reference/users#emails) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} +| [`关注者`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | 授予对[关注者 API](/rest/reference/users#followers) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | 授予对[GPG 密钥 API](/rest/reference/users#gpg-keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | 授予对[议题 API](/rest/reference/issues) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`键`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | 授予对[公钥 API](/rest/reference/users#keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | 授予管理组织成员的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" %} +| [`元数据`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | 授予对不泄漏敏感数据的只读端点的访问权限。 可以是 `read` 或 `none`。 设置任何权限时，默认值为 `read`；没有为 {% data variables.product.prodname_github_app %} 指定任何权限时，默认值为 `none`。 | +| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | 授予对“[更新组织](/rest/reference/orgs#update-an-organization)”端点和[组织交互限制 API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | 授予对[组织 web 挂钩 API](/rest/reference/orgs#webhooks/) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `organization_plan` | 授予使用“[获取组织](/rest/reference/orgs#get-an-organization)”端点获取有关组织计划的信息的权限。 可以是以下项之一：`none` 或 `read`。 | +| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | 授予对[项目 API](/rest/reference/projects) 的访问权限。 可以是以下项之一：`none`、`read`、`write` 或 `admin`。{% if currentVersion == "free-pro-team@latest" %} +| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | 授予对[阻止组织用户 API](/rest/reference/orgs#blocking) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} +| [`页面`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | 授予对[页面 API](/rest/reference/repos#pages) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `plan` | 授予使用“[获取用户](/rest/reference/users#get-a-user)”端点获取有关用户 GitHub 计划的信息的权限。 可以是以下项之一：`none` 或 `read`。 | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | 授予对各种拉取请求端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | 授予对[仓库 web 挂钩 API](/rest/reference/repos#hooks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | 授予对[项目 API](/rest/reference/projects) 的访问权限。 可以是以下项之一：`none`、`read`、`write` 或 `admin`。 | +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | 授予对[内容 API](/rest/reference/repos#contents) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | 授予对[标星 API](/rest/reference/activity#starring) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | 授予对[状态 API](/rest/reference/repos#statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `vulnerability_alerts` | 授予接收仓库漏洞依赖项安全警报的权限。 更多信息请参阅“[关于漏洞依赖项安全警报](/articles/about-security-alerts-for-vulnerable-dependencies)”。 可以是以下项之一：`none` 或 `read`。 | +| `关注` | 授予列出和更改用户订阅的仓库的权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -### {% data variables.product.prodname_github_app %} webhook events +### {% data variables.product.prodname_github_app %} web 挂钩事件 -| Web 挂钩事件名称 | Required permission | 描述 | -| -------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | -| [`check_run`](/webhooks/event-payloads/#check_run) | `检查` | {% data reusables.webhooks.check_run_short_desc %} -| [`check_suite`](/webhooks/event-payloads/#check_suite) | `检查` | {% data reusables.webhooks.check_suite_short_desc %} -| [`commit_comment`](/webhooks/event-payloads/#commit_comment) | `内容` | {% data reusables.webhooks.commit_comment_short_desc %} -| [`content_reference`](/webhooks/event-payloads/#content_reference) | `content_references` | {% data reusables.webhooks.content_reference_short_desc %} -| [`create`](/webhooks/event-payloads/#create) | `内容` | {% data reusables.webhooks.create_short_desc %} -| [`delete`](/webhooks/event-payloads/#delete) | `内容` | {% data reusables.webhooks.delete_short_desc %} -| [`deployment`](/webhooks/event-payloads/#deployment) | `部署` | {% data reusables.webhooks.deployment_short_desc %} -| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | `部署` | {% data reusables.webhooks.deployment_status_short_desc %} -| [`复刻`](/webhooks/event-payloads/#fork) | `内容` | {% data reusables.webhooks.fork_short_desc %} -| [`gollum`](/webhooks/event-payloads/#gollum) | `内容` | {% data reusables.webhooks.gollum_short_desc %} -| [`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %} -| [`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %} -| [`标签`](/webhooks/event-payloads/#label) | `元数据` | {% data reusables.webhooks.label_short_desc %} -| [`成员`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} -| [`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} -| [`里程碑`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} -| [`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} -| [`组织`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} -| [`page_build`](/webhooks/event-payloads/#page_build) | `页面` | {% data reusables.webhooks.page_build_short_desc %} -| [`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %} -| [`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} -| [`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} -| [`public`](/webhooks/event-payloads/#public) | `元数据` | {% data reusables.webhooks.public_short_desc %} -| [`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} -| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} -| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} -| [`推送`](/webhooks/event-payloads/#push) | `内容` | {% data reusables.webhooks.push_short_desc %} -| [`发行版`](/webhooks/event-payloads/#release) | `内容` | {% data reusables.webhooks.release_short_desc %} -| [`仓库`](/webhooks/event-payloads/#repository) | `元数据` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} -| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `内容` | Allows integrators using GitHub Actions to trigger custom events.{% endif %} -| [`状态`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %} -| [`团队`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} -| [`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} -| [`查看`](/webhooks/event-payloads/#watch) | `元数据` | {% data reusables.webhooks.watch_short_desc %} +| Web 挂钩事件名称 | 所需权限 | 描述 | +| -------------------------------------------------------------------------------------- | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------- | +| [`check_run`](/webhooks/event-payloads/#check_run) | `检查` | {% data reusables.webhooks.check_run_short_desc %} +| [`check_suite`](/webhooks/event-payloads/#check_suite) | `检查` | {% data reusables.webhooks.check_suite_short_desc %} +| [`commit_comment`](/webhooks/event-payloads/#commit_comment) | `内容` | {% data reusables.webhooks.commit_comment_short_desc %} +| [`content_reference`](/webhooks/event-payloads/#content_reference) | `content_references` | {% data reusables.webhooks.content_reference_short_desc %} +| [`create`](/webhooks/event-payloads/#create) | `内容` | {% data reusables.webhooks.create_short_desc %} +| [`delete`](/webhooks/event-payloads/#delete) | `内容` | {% data reusables.webhooks.delete_short_desc %} +| [`deployment`](/webhooks/event-payloads/#deployment) | `部署` | {% data reusables.webhooks.deployment_short_desc %} +| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | `部署` | {% data reusables.webhooks.deployment_status_short_desc %} +| [`复刻`](/webhooks/event-payloads/#fork) | `内容` | {% data reusables.webhooks.fork_short_desc %} +| [`gollum`](/webhooks/event-payloads/#gollum) | `内容` | {% data reusables.webhooks.gollum_short_desc %} +| [`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %} +| [`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %} +| [`标签`](/webhooks/event-payloads/#label) | `元数据` | {% data reusables.webhooks.label_short_desc %} +| [`成员`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} +| [`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} +| [`里程碑`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} +| [`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} +| [`组织`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} +| [`page_build`](/webhooks/event-payloads/#page_build) | `页面` | {% data reusables.webhooks.page_build_short_desc %} +| [`project`](/webhooks/event-payloads/#project) | `repository_projects` 或 `organization_projects` | {% data reusables.webhooks.project_short_desc %} +| [`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` 或 `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} +| [`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` 或 `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} +| [`public`](/webhooks/event-payloads/#public) | `元数据` | {% data reusables.webhooks.public_short_desc %} +| [`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} +| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} +| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} +| [`推送`](/webhooks/event-payloads/#push) | `内容` | {% data reusables.webhooks.push_short_desc %} +| [`发行版`](/webhooks/event-payloads/#release) | `内容` | {% data reusables.webhooks.release_short_desc %} +| [`仓库`](/webhooks/event-payloads/#repository) | `元数据` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} +| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `内容` | 允许集成者使用 GitHub 操作触发自定义事件。{% endif %} +| [`状态`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %} +| [`团队`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} +| [`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} +| [`查看`](/webhooks/event-payloads/#watch) | `元数据` | {% data reusables.webhooks.watch_short_desc %} diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app.md b/translations/zh-CN/content/developers/apps/creating-a-github-app.md index 8d94a22431..2acadca7d4 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app.md @@ -1,5 +1,5 @@ --- -title: Creating a GitHub App +title: 创建 GitHub 应用程序 intro: '{% data reusables.shortdesc.creating_github_apps %}' redirect_from: - /early-access/integrations/creating-an-integration/ @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" %}To learn how to use GitHub App Manifests, which allow people to create preconfigured GitHub Apps, see "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %} 要了解如何使用 GitHub 应用程序清单允许用户创建预配置 GitHub 应用程序，请参阅“[从清单创建 GitHub 应用程序](/apps/building-github-apps/creating-github-apps-from-a-manifest/)。”{% endif %} {% if currentVersion == "free-pro-team@latest" %} {% note %} @@ -24,46 +24,46 @@ versions: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Click **New GitHub App**. ![Button to create a new GitHub App](/assets/images/github-apps/github_apps_new.png) -5. In "GitHub App name", type the name of your app. ![Field for the name of your GitHub App](/assets/images/github-apps/github_apps_app_name.png) +4. 单击 **New GitHub App（新建 GitHub 应用程序）**。 ![用于创建新 GitHub 应用程序的按钮](/assets/images/github-apps/github_apps_new.png) +5. 在“GitHub App name（GitHub 应用程序名称）”中，输入应用程序的名称。 ![GitHub 应用程序名称字段](/assets/images/github-apps/github_apps_app_name.png) - Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. + 给应用程序一个清晰简洁的名称。 应用程序不能与现有 GitHub 用户同名，除非它是您自己的用户或组织的名称。 当您的集成执行操作时，应用程序名称的缓存版本将显示在用户界面上。 -6. Optionally, in "Description", type a description of your app that users will see. ![Field for a description of your GitHub App](/assets/images/github-apps/github_apps_description.png) -7. In "Homepage URL", type the full URL to your app's website. ![Field for the homepage URL of your GitHub App](/assets/images/github-apps/github_apps_homepage_url.png) +6. （可选）在“Description（说明）”中，输入用户将看到的应用程序说明。 ![GitHub 应用程序说明字段](/assets/images/github-apps/github_apps_description.png) +7. 在“Homepage URL（主页 URL）”中，输入应用程序网站的完整 URL。 ![GitHub 应用程序主页 URL 字段](/assets/images/github-apps/github_apps_homepage_url.png) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -8. In "Callback URL", type the full URL to redirect to after a user authorizes the installation. This URL is used if your app needs to identify and authorize user-to-server requests. +8. 在“Callback URL（回调 URL）”中，键入用户授权安装后要重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。 - You can use **Add callback URL** to provide additional callback URLs, up to a maximum of 10. + 您可以使用 **Add callback URL（添加回调 URL）**来提供额外的回调 URL，最多不超过 10 个。 - ![Button for 'Add callback URL' and field for callback URL](/assets/images/github-apps/github_apps_callback_url_multiple.png) + ![用于“添加回调 URL”的按钮和回调 URL 的字段](/assets/images/github-apps/github_apps_callback_url_multiple.png) {% else %} -8. In "User authorization callback URL", type the full URL to redirect to after a user authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. ![Field for the user authorization callback URL of your GitHub App](/assets/images/github-apps/github_apps_user_authorization.png) +8. 在“User authorization callback URL（用户授权回调 URL）”中，键入用户授权安装后要重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。 ![GitHub 应用程序的用户授权回调 URL 字段](/assets/images/github-apps/github_apps_user_authorization.png) {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -9. By default, to improve your app's security, your app will use expiring user authorization tokens. To opt-out of using expiring user tokens, you must deselect "Expire user authorization tokens". To learn more about setting up a refresh token flow and the benefits of expiring user tokens, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png) +9. 默认情况下，为了提高应用程序的安全性，应用程序将使用过期用户授权令牌。 要选择不使用过期用户令牌，您必须取消选中“Expire user authorization tokens（过期用户授权令牌）”。 要了解有关设置刷新令牌流程和过期用户令牌的好处，请参阅“[刷新用户到服务器的访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”。 ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png) {% endif %} -9. If your app authorizes users using the OAuth flow, you can select **Request user authorization (OAuth) during installation** to allow people to authorize the app when they install it, saving a step. If you select this option, the "Setup URL" becomes unavailable and users will be redirected to your "User authorization callback URL" after installing the app. See "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)" for more information. ![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png) -10. If additional setup is required after installation, add a "Setup URL" to redirect users to after they install your app. ![Field for the setup URL of your GitHub App ](/assets/images/github-apps/github_apps_setup_url.png) +9. 如果应用程序授权用户使用 OAuth 流程，您可以选择**在安装过程中请求用户授权 (OAuth)**，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则“设置 URL”将不可用，用户在安装应用程序后将被重定向到您的“用户授权回调 URL”。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。 ![安装过程中请求用户授权](/assets/images/github-apps/github_apps_request_auth_upon_install.png) +10. 如果安装后需要附加设置，请添加一个“设置 URL”以便在用户安装应用程序后重定向他们。 ![GitHub 应用程序的设置 URL 字段 ](/assets/images/github-apps/github_apps_setup_url.png) {% note %} - **Note:** When you select **Request user authorization (OAuth) during installation** in the previous step, this field becomes unavailable and people will be redirected to the "User authorization callback URL" after installing the app. + **注：**如果您在上一步选择了**在安装过程中请求用户授权 (OAuth)**，此字段将不可用，用户在安装应用程序后将被重定向到“用户授权回调 URL”。 {% endnote %} -11. In "Webhook URL", type the URL that events will POST to. Each app receives its own webhook which will notify you every time the app is installed or modified, as well as any other events the app subscribes to. ![Field for the webhook URL of your GitHub App](/assets/images/github-apps/github_apps_webhook_url.png) +11. 在“Webhook URL（Web 挂钩 URL）”中，输入事件将 POST 到的 URL。 每个应用程序都会收到自己的 web 挂钩（每当应用程序被安装或修改时都会通知您）以及应用程序订阅的任何其他事件。 ![GitHub 应用程序的 web 挂钩 URL 字段](/assets/images/github-apps/github_apps_webhook_url.png) -12. Optionally, in "Webhook Secret", type an optional secret token used to secure your webhooks. ![Field to add a secret token for your webhook](/assets/images/github-apps/github_apps_webhook_secret.png) +12. （可选）在“Webhook Secret（Web 挂钩密钥）”中，输入用于保护 web 挂钩的可选密钥令牌。 ![添加 web 挂钩密钥令牌的字段](/assets/images/github-apps/github_apps_webhook_secret.png) {% note %} - **Note:** We highly recommend that you set a secret token. 更多信息请参阅“[保护 web 挂钩](/webhooks/securing/)”。 + **注：**我们强烈建议您设置密钥令牌。 更多信息请参阅“[保护 web 挂钩](/webhooks/securing/)”。 {% endnote %} -13. In "Permissions", choose the permissions your app will request. For each type of permission, use the drop-down menu and click **Read-only**, **Read & write**, or **No access**. ![Various permissions for your GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png) -14. In "Subscribe to events", choose whether to subscribe your app to **Label**, **Public**, **Repository**, or **Watch** events. ![Subscribe to events options for your GitHub App](/assets/images/github-apps/github_apps_subscribe_to_events.png) -15. To choose where the app can be installed, select either **Only on this account** or **Any account**. For more information on installation options, see "[Making a GitHub App public or private](/apps/managing-github-apps/making-a-github-app-public-or-private/)." ![Installation options for your GitHub App](/assets/images/github-apps/github_apps_installation_options.png) -16. Click **Create GitHub App**. ![Button to create your GitHub App](/assets/images/github-apps/github_apps_create_github_app.png) +13. 在“Permissions（权限）”中，选择应用程序将请求的权限。 对于每种类型的权限，请使用下拉菜单并单击 **Read-only（只读）**、**Read & write（读取和写入）** 或 **No access（无访问权限）**。 ![GitHub 应用程序的各种权限](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png) +14. 在“Subscribe to events（订阅事件）”中，选择是否让应用程序订阅 **Label（标签）**、**Public（公开）**、**Repository（仓库）**或 **Watch（关注）**事件。 ![订阅 GitHub 应用程序的事件选项](/assets/images/github-apps/github_apps_subscribe_to_events.png) +15. 要选择可安装应用程序的位置，请选择 **Only on this account（仅在此帐户上）**或 **Any account（任何帐户）**。 有关安装选项的更多信息，请参阅“[将 GitHub 应用程序设为公开或私有](/apps/managing-github-apps/making-a-github-app-public-or-private/)”。 ![GitHub 应用程序的安装选项](/assets/images/github-apps/github_apps_installation_options.png) +16. 单击 **Create GitHub App（创建 GitHub 应用程序）**。 ![创建 GitHub 应用程序的按钮](/assets/images/github-apps/github_apps_create_github_app.png) diff --git a/translations/zh-CN/content/developers/apps/creating-an-oauth-app.md b/translations/zh-CN/content/developers/apps/creating-an-oauth-app.md index 05339f28f4..328628e328 100644 --- a/translations/zh-CN/content/developers/apps/creating-an-oauth-app.md +++ b/translations/zh-CN/content/developers/apps/creating-an-oauth-app.md @@ -1,5 +1,5 @@ --- -title: Creating an OAuth App +title: 创建 OAuth 应用程序 intro: '{% data reusables.shortdesc.creating_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps/ @@ -21,29 +21,29 @@ versions: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %} -4. Click **New OAuth App**. ![Button to create a new OAuth app](/assets/images/oauth-apps/oauth_apps_new_app.png) +4. 单击 **New OAuth App（新建 OAuth 应用程序）**。 ![创建新 OAuth 应用程序的按钮](/assets/images/oauth-apps/oauth_apps_new_app.png) {% note %} - **Note:** If you haven't created an app before, this button will say, **Register a new application**. + **注：**如果您以前没有创建过应用程序，该按钮将显示 **Register a new application（注册新应用程序）**。 {% endnote %} -6. In "Application name", type the name of your app. ![Field for the name of your app](/assets/images/oauth-apps/oauth_apps_application_name.png) +6. 在“Application name（应用程序名称）”中，输入应用程序的名称。 ![应用程序名称字段](/assets/images/oauth-apps/oauth_apps_application_name.png) {% warning %} - **Warning:** Only use information in your OAuth app that you consider public. Avoid using sensitive data, such as internal URLs, when creating an OAuth App. + **警告：**仅在 OAuth 应用程序中使用您认为公开的信息。 创建 OAuth 应用程序时，应避免使用敏感数据（如内部 URL）。 {% endwarning %} -7. In "Homepage URL", type the full URL to your app's website. ![Field for the homepage URL of your app](/assets/images/oauth-apps/oauth_apps_homepage_url.png) -8. Optionally, in "Application description", type a description of your app that users will see. ![Field for a description of your app](/assets/images/oauth-apps/oauth_apps_application_description.png) -9. In "Authorization callback URL", type the callback URL of your app. ![Field for the authorization callback URL of your app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png) +7. 在“Homepage URL（主页 URL）”中，输入应用程序网站的完整 URL。 ![应用程序主页 URL 字段](/assets/images/oauth-apps/oauth_apps_homepage_url.png) +8. （可选）在“Application description（应用程序说明）”中，输入用户将看到的应用程序说明。 ![应用程序说明字段](/assets/images/oauth-apps/oauth_apps_application_description.png) +9. 在“Authorization callback URL（授权回调 URL）”中，输入应用程序的回调 URL。 ![应用程序的授权回调 URL 字段](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} - **Note:** OAuth Apps cannot have multiple callback URLs, unlike {% data variables.product.prodname_github_apps %}. + **注：**与 {% data variables.product.prodname_github_apps %} 不同，OAuth 应用程序不能有多个回调 URL。 {% endnote %} {% endif %} -10. 单击 **Register application（注册应用程序）**。 ![Button to register an application](/assets/images/oauth-apps/oauth_apps_register_application.png) +10. 单击 **Register application（注册应用程序）**。 ![注册应用程序的按钮](/assets/images/oauth-apps/oauth_apps_register_application.png) diff --git a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 7ca7e89367..90452b023a 100644 --- a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -1,6 +1,6 @@ --- -title: Creating CI tests with the Checks API -intro: 'Build a continuous integration server to run tests using a {% data variables.product.prodname_github_app %} and the Checks API.' +title: 使用检查 API 创建 CI 测试 +intro: '使用 {% data variables.product.prodname_github_app %} 和检查 API 构建一个持续集成服务器以运行测试。' redirect_from: - /apps/quickstart-guides/creating-ci-tests-with-the-checks-api versions: @@ -12,95 +12,95 @@ versions: ### 简介 -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/v3/checks/), which you'll use to build a continuous integration (CI) server that runs tests. +本指南将介绍 [Github 应用程序](/apps/)和[检查 API](/rest/reference/checks)，您将使用它们来构建运行测试的持续集成 (CI) 服务器。 -CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. 频繁的代码更新也更便于从软件开发团队的不同成员合并更改。 这对开发者非常有益，他们可以将更多时间用于编写代码，而减少在调试错误或解决合并冲突上所花的时间。 🙌 +CI 是一种需要频繁提交代码到共享仓库的软件实践。 频繁提交代码能较早检测到错误，减少在查找错误来源时开发者需要调试的代码量。 频繁的代码更新也更便于从软件开发团队的不同成员合并更改。 这对开发者非常有益，他们可以将更多时间用于编写代码，而减少在调试错误或解决合并冲突上所花的时间。 🙌 -A CI server hosts code that runs CI tests such as code linters (which check style formatting), security checks, code coverage, and other checks against new code commits in a repository. CI servers can even build and deploy code to staging or production servers. For some examples of the types of CI tests you can create with a GitHub App, check out the [continuous integration apps](https://github.com/marketplace/category/continuous-integration) available in GitHub Marketplace. +CI 服务器托管运行 CI 测试的代码，如代码语法检查（检查样式格式）、安全检查、代码覆盖率以及针对仓库中新代码提交的其他检查。 CI 服务器甚至可以构建代码并将其部署到暂存或生产服务器。 有关您可以使用 GitHub 应用程序创建的 CI 测试类型的一些示例，请查看 GitHub Marketplace 中提供的[持续集成应用程序](https://github.com/marketplace/category/continuous-integration)。 {% data reusables.apps.app-ruby-guides %} -#### Checks API overview +#### 检查 API 概述 -The [Checks API](/v3/checks/) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. +[检查 API](/rest/reference/checks) 允许您设置针对仓库中的每个代码提交自动运行的 CI 测试。 检查 API 在拉取请求的 **Checks（检查）**选项卡中报告 GitHub 上每个检查的详细信息。 使用检查 API，您可以创建带有特定代码行附加细节的注释。 注释在 **Checks（检查）**选项卡中可见。 当您为拉取请求中的文件创建注释时，注释也会显示在 **Files changed（文件已更改）**选项卡中。 -A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/v3/repos/branches/) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. +_检查套件_是一组_检查运行_（单个 CI 测试）。 套件和运行都包含 GitHub 上的拉取请求中可见的_状态_。 您可以使用状态来确定何时代码提交引入错误。 对[受保护分支](/rest/reference/repos#branches)使用这些状态可防止用户草率地合并拉取请求。 更多信息请参阅“[启用必需状态检查](/articles/enabling-required-status-checks/)”。 -The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: +每当有新代码推送到仓库时，检查 API 会将 [`check_suite` web 挂钩事件](/webhooks/event-payloads/#check_suite)发送到仓库中安装的所有 GitHub 应用程序。 要接收所有检查 API 事件操作，应用程序必须具有 `checks:write` 权限。 GitHub 使用默认流程自动为仓库中的新代码提交创建 `check_suite` 事件，但您可以根据需要[更新检查套件的仓库首选项](/rest/reference/checks#update-repository-preferences-for-check-suites)。 以下是默认流程的工作方式： -1. Whenever someone pushes code to the repository, GitHub sends the `check_suite` event with an action of `requested` to all GitHub Apps installed on the repository that have the `checks:write` permission. This event lets the apps know that code was pushed and that GitHub has automatically created a new check suite. -1. When your app receives this event, it can [add check runs](/v3/checks/runs/#create-a-check-run) to that suite. -1. Your check runs can include [annotations](/v3/checks/runs/#annotations-object) that are displayed on specific lines of code. +1. 每当有人向仓库推送代码时，GitHub 会将带有 `requested` 操作的 `check_suite` 事件发送到仓库中安装的所有具有 `checks:write` 权限的 GitHub 应用程序。 此事件让应用程序知道推送了代码，并且 GitHub 已自动创建新的检查套件。 +1. 应用程序收到此事件后，它可以[添加检查运行](/rest/reference/checks#create-a-check-run)到该套件。 +1. 检查运行可包括显示在特定代码行上的[注释](/rest/reference/checks#annotations-object)。 -**In this guide, you’ll learn how to:** +**在本指南中，您将学习如何：** -* Part 1: Set up the framework for a CI server using the Checks API. - * Configure a GitHub App as a server that receives Checks API events. - * Create new check runs for CI tests when a repository receives newly pushed commits. - * Re-run check runs when a user requests that action on GitHub. -* Part 2: Build on the CI server framework you created by adding a linter CI test. - * Update a check run with a `status`, `conclusion`, and `output` details. - * Create annotations on lines of code that GitHub displays in the **Checks** and **Files Changed** tab of a pull request. - * Automatically fix linter recommendations by exposing a "Fix this" button in the **Checks** tab of the pull request. +* 第 1 部分：使用检查 API 为 CI 服务器设置框架。 + * 将 GitHub 应用程序配置为接收检查 API 事件的服务器。 + * 当仓库收到新推送的提交时，为 CI 测试创建新的检查运行。 + * 当用户在 GitHub 上请求该操作时，重新运行检查。 +* 第 2 部分：通过添加语法检查 CI 测试在您创建的 CI 服务器框架上构建。 + * 使用 `status`、`conclusion` 和 `output` 详细信息更新检查运行。 + * 在 GitHub 显示在**Checks（检查）** 和**Files Changed（文件已更改）**选项卡中的 代码行上创建注释。 + * 通过在 **Checks（检查）**选项卡中显示 “Fix this（修复此问题）”按钮来自动修复语法检查建议。 -To get an idea of what your Checks API CI server will do when you've completed this quickstart, check out the demo below: +要了解完成此快速入门后检查 API CI 服务器将执行的操作，请查看以下演示： -![Demo of Checks API CI sever quickstart](/assets/images/github-apps/github_apps_checks_api_ci_server.gif) +![检查 API CI 服务器快速入门演示](/assets/images/github-apps/github_apps_checks_api_ci_server.gif) ### 基本要求 -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/v3/checks/), if you're not already. You'll find more APIs in the [REST API docs](/v3/). The Checks API is also available to use in [GraphQL](/v4/), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/v4/object/checksuite/) and [Check Run](/v4/object/checkrun/) objects for more details. +在开始之前，如果您尚未熟悉 [Github 应用程序](/apps/)、[web 挂钩](/webhooks)和[检查 API](/rest/reference/checks)，可能需要先熟悉一下。 您将在 [REST API 文档](/rest)中找到更多 API。 检查 API 也可用于 [GraphQL](/graphql)，但本快速入门指南侧重于 REST。 更多信息请参阅 GraphQL [检查套件](/graphql/reference/objects#checksuite)和[检查运行](/graphql/reference/objects#checkrun)对象。 -You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app. +您将使用 [Ruby 编程语言](https://www.ruby-lang.org/en/)、[Smee](https://smee.io/) web 挂钩有效负载交付服务、用于 GitHub REST API 的 [Octokit.rb Ruby 库](http://octokit.github.io/octokit.rb/)以及 [Sinatra web 框架](http://sinatrarb.com/)来创建检查 API CI 服务器应用程序。 -You don't need to be an expert in any of these tools or concepts to complete this project. This guide will walk you through all the required steps. Before you begin creating CI tests with the Checks API, you'll need to do the following: +完成此项目并不需要您精通任何这些工具或概念。 本指南将引导您完成所有必需的步骤。 在开始使用检查 API 创建 CI 测试之前，您需要执行以下操作： -1. Clone the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository. +1. 克隆[使用检查 API 创建 CI 测试](https://github.com/github-developer/creating-ci-tests-with-the-checks-api)仓库。 ```shell $ git clone https://github.com/github-developer/creating-ci-tests-with-the-checks-api.git ``` - Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code. + 在目录中，您将找到包含本快速入门将要使用的模板代码的 `template_server.rb` 文件以及包含已完成项目代码的 `server.rb` 文件。 -1. Follow the steps in the "[Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/)" quickstart to configure and run the app server. **Note:** Instead of [cloning the GitHub App template repository](/apps/quickstart-guides/setting-up-your-development-environment/#prerequisites), use the `template_server.rb` file in the repository you cloned in the previous step in this quickstart. +1. 请按照“[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)”快速入门中的步骤来配置和运行应用程序服务器。 **注：**不要[克隆 GitHub 应用程序模板仓库](/apps/quickstart-guides/setting-up-your-development-environment/#prerequisites)，而应使用在本快速入门的上一步中克隆的仓库中的 `template_server.rb` 文件。 - If you've completed a GitHub App quickstart before, make sure to register a _new_ GitHub App and start a new Smee channel to use with this quickstart. + 如果您之前已完成 GitHub 应用程序快速入门，请确保注册一个_新_ GitHub 应用程序，并开启一个新的 Smee 通道用于本快速入门。 - See the [troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App. + 如果在设置模板 GitHub 应用程序时遇到问题，请参阅[故障排除](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting)部分。 -### Part 1. Creating the Checks API interface +### 第 1 部分。 创建检查 API 接口 -In this part, you will add the code necessary to receive `check_suite` webhook events and create and update check runs. You'll also learn how to create check runs when a check was re-requested on GitHub. At the end of this section, you'll be able to view the check run you created in a GitHub pull request. +在本部分，您将添加必要的代码以接收 `check_suite` web 挂钩事件并创建和更新检查运行。 您还将学习在 GitHub 上重新请求检查时如何创建检查运行。 在本节的最后，您将能够查看在 GitHub 拉取请求中创建的检查运行。 -Your check run will not be performing any checks on the code in this section. You'll add that functionality in [Part 2: Creating the Octo RuboCop CI test](#part-2-creating-the-octo-rubocop-ci-test). +您的检查运行不会对本节中的代码执行任何检查。 您将在[第 2 部分：创建 Octo RuboCop CI 测试](#part-2-creating-the-octo-rubocop-ci-test)中添加该功能。 -You should already have a Smee channel configured that is forwarding webhook payloads to your local server. Your server should be running and connected to the GitHub App you registered and installed on a test repository. If you haven't completed the steps in "[Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/)," you'll need to do that before you can continue. +您应该已经配置了可将 web 挂钩有效负载转发到本地服务器的 Smee 通道。 您的服务器应该正在运行并连接到您注册并安装在测试仓库的 GitHub 应用程序。 如果您尚未完成“[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)”中的步骤，则需要先完成这些步骤才能继续。 -Let's get started! These are the steps you'll complete in Part 1: +让我们开始吧！ 以下是您将在第 1 部分中完成的步骤： -1. [Updating app permissions](#step-11-updating-app-permissions) -1. [Adding event handling](#step-12-adding-event-handling) -1. [Creating a check run](#step-13-creating-a-check-run) -1. [Updating a check run](#step-14-updating-a-check-run) +1. [更新应用程序权限](#step-11-updating-app-permissions) +1. [添加事件处理](#step-12-adding-event-handling) +1. [创建检查运行](#step-13-creating-a-check-run) +1. [更新检查运行](#step-14-updating-a-check-run) -### 步骤 1.1. Updating app permissions +### 步骤 1.1. 更新应用程序权限 -When you [first registered your app](#prerequisites), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read and write checks. +如果您在[首次注册应用程序](#prerequisites)时接受了 默认权限，则意味着您的应用程序无法访问大多数资源。 对于此示例，您的应用程序将需要读取和写入检查的权限。 -To update your app's permissions: +要更新应用程序的权限： -1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar. -1. In the "Permissions" section, find "Checks", and select **Read & write** in the Access dropdown next to it. -1. In the "Subscribe to events" section, select **Check suite** and **Check run** to subscribe to these events. +1. 从[应用程序设置页面](https://github.com/settings/apps)选择应用程序，然后单击边栏中的 **Permissions & Webhooks（权限和 web 挂钩）**。 +1. 在“Permissions（权限）”部分，找到“Checks（检查）”，然后在其旁边的“Access（访问权限）”下拉列表中选择 **Read & write（读取和写入）**。 +1. 在“Subscribe to events（订阅事件）”部分，选择 **Check suite（检查套件）**和 **Check run（检查运行）**以订阅这些事件。 {% data reusables.apps.accept_new_permissions_steps %} -太好了！ Your app has permission to do the tasks you want it to do. Now you can add the code to handle the events. +太好了！ 您的应用程序现在有权限执行所需的任务。 现在您可以添加代码来处理事件。 -### 步骤 1.2. Adding event handling +### 步骤 1.2. 添加事件处理 -Now that your app is subscribed to the **Check suite** and **Check run** events, it will start receiving the [`check_suite`](/webhooks/event-payloads/#check_suite) and [`check_run`](/webhooks/event-payloads/#check_run) webhooks. GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads at the `post '/event_handler'` route. +现在，您的应用程序已订阅**检查套件**和**检查运行**事件，它将开始接收 [`check_suite`](/webhooks/event-payloads/#check_suite) 和 [`check_run`](/webhooks/event-payloads/#check_run) web 挂钩。 GitHub 将 web 挂钩有效负载作为 `POST` 请求发送。 因为您已将 Smee web 挂钩有效负载转发到 `http://localhost/event_handler:3000`，因此您的服务器将在 `post '/event_handler'` 路由中接收 `POST` 请求有效负载。 -An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this: +您在[前提条件](#prerequisites)部分中下载的 `template_server.rb` 文件中已包括空 `post '/event_handler'` 路由。 空路由如下所示： ``` ruby post '/event_handler' do @@ -113,7 +113,7 @@ An empty `post '/event_handler'` route is already included in the `template_serv end ``` -Use this route to handle the `check_suite` event by adding the following code: +通过添加以下代码，使用此路由来处理 `check_suite` 事件： ``` ruby # Get the event type from the HTTP_X_GITHUB_EVENT header @@ -126,13 +126,13 @@ when 'check_suite' end ``` -Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in events of type `check_suite`, which are emitted when a new check suite is created. Each event has an additional `action` field that indicates the type of action that triggered the events. For `check_suite`, the `action` field can be `requested`, `rerequested`, or `completed`. +GitHub 发送的每个事件都包含一个名为 `HTTP_X_GITHUB_EVENT` 的请求标头，它指示 `POST` 请求中的事件类型。 现在，您只关注类型为 `check_suite` 的事件，它在创建新的检查套件时触发。 每个事件都有一个附加的 `action` 字段，它指示触发事件的操作类型。 对于 `check_suite`，`action` 字段可以是 `requested`、`rerequested` 或 `completed`。 -The `requested` action requests a check run each time code is pushed to the repository, while the `rerequested` action requests that you re-run a check for code that already exists in the repository. Because both the `requested` and `rerequested` actions require creating a check run, you'll call a helper called `create_check_run`. Let's write that method now. +每当有代码推送到仓库时，`requested` 操作会请求检查运行，而 `rerequested` 操作则请求您对仓库中已经存在的代码重新运行检查。 由于 `requested` 和 `rerequested` 操作都需要创建检查运行，因此您将调用名为 `create_check_run` 的小助手。 现在我们来编写该方法。 -### 步骤 1.3. Creating a check run +### 步骤 1.3. 创建检查运行 -You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sinatra#helpers) in case you want other routes to use it too. Under `helpers do`, add this `create_check_run` method: +如果希望其他路由也使用此新方法，您可以将其添加为 [Sinatra 小助手](https://github.com/sinatra/sinatra#helpers)。 在 `helpers do` 下，添加此 `create_check_run` 方法： {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} ``` ruby @@ -140,7 +140,7 @@ You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sina def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -159,7 +159,7 @@ end def create_check_run # # At the time of writing, Octokit does not support the Checks API yet, but # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run + # /rest/reference/checks#create-a-check-run check_run = @installation_client.post( "repos/#{@payload['repository']['full_name']}/check-runs", { @@ -175,17 +175,17 @@ end ``` {% endif %} -This code calls the "[Create a check run](/v3/checks/runs/#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method. +此代码使用通用的 [HTTP `POST` 方法](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method)调用“[创建检查运行](/rest/reference/checks#create-a-check-run)”端点。 此方法采用两个参数：端点的 URL 和方法的输入参数。 -To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [Rubocop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo Rubocop" is used here, but you can choose any name you'd like for the check run. +要创建检查运行，只有两个输入参数是必需的：`name` 和 `head_sha`。 在本快速入门中的稍后部分，我们将使用 [Rubocop](https://rubocop.readthedocs.io/en/latest/) 来实现 CI 测试，这就是在此处使用名称 "Octo Rubocop" 的原因，但是您可以为检查运行选择任何想用的名称。 -You're only supplying the required parameters now to get the basic functionality working, but you'll update the check run later as you collect more information about the check run. By default, GitHub sets the `status` to `queued`. +您现在仅提供必需的参数以使基本功能正常工作，但是稍后您将在收集有关检查运行的更多信息时更新检查运行。 默认情况下，GitHub 将 `status` 设置为 `queued`。 -GitHub creates a check run for a specific commit SHA, which is why `head_sha` is a required parameter. You can find the commit SHA in the webhook payload. Although you're only creating a check run for the `check_suite` event right now, it's good to know that the `head_sha` is included in both the `check_suite` and `check_run` objects in the event payloads. +GitHub 为特定的提交 SHA 创建检查运行，这就是 `head_sha` 是必需参数的原因。 您可以在 web 挂钩有效负载中找到提交 SHA。 虽然您现在只为 `check_suite` 事件创建了检查运行，但是已经知道事件有效负载中的 `check_suite` 和 `check_run` 对象中都包含了 `head_sha`。 -In the code above, you're using the [ternary operator](https://ruby-doc.org/core-2.3.0/doc/syntax/control_expressions_rdoc.html#label-Ternary+if), which works like an `if/else` statement, to check if the payload contains a `check_run` object. If it does, you read the `head_sha` from the `check_run` object, otherwise you read it from the `check_suite` object. +在上面的代码中，您使用[三元运算符](https://ruby-doc.org/core-2.3.0/doc/syntax/control_expressions_rdoc.html#label-Ternary+if)（其工作方式类似于 `if/else` 语句）检查有效负载是否包含 `check_run` 对象。 如果是，则从 `check_run` 对象读取 `head_sha`，否则将从 `check_suite` 对象读取它。 -To test this code, restart the server from your terminal: +要测试此代码，请从您的终端重启服务器： ```shell $ ruby template_server.rb @@ -193,24 +193,23 @@ $ ruby template_server.rb {% data reusables.apps.sinatra_restart_instructions %} -Now open a pull request in the repository where you installed your app. Your app should respond by creating a check run on your pull request. Click on the **Checks** tab, and you should see something like this: +现在，在安装应用程序的仓库中打开拉取请求。 您的应用程序应该通过对拉取请求创建检查运行来响应。 单击 **Checks（检查）**选项卡，您应该会看到以下内容： -![Queued check run](/assets/images/github-apps/github_apps_queued_check_run.png) +![排队检查运行](/assets/images/github-apps/github_apps_queued_check_run.png) -If you see other apps in the Checks tab, it means you have other apps installed on your repository that have **Read & write** access to checks and are subscribed to **Check suite** and **Check run** events. +如果您在“Checks（检查）”选项卡中看到其他应用程序，则意味着您的仓库中安装了其他应用程序，它们对检查具有 **Read & write（读取和写入）** 权限，并且订阅了 **Check suite（检查套件）**和 **Check run（检查运行）**事件。 -太好了！ You've told GitHub to create a check run. You can see the check run status is set to `queued` next to a yellow icon. Next, you'll want to wait for GitHub to create the check run and update its status. +太好了！ 您已告诉 GitHub 创建检查运行。 您可以在黄色图标旁边看到检查运行状态设置为 `queued`。 接下来，您需要等待 GitHub 创建检查运行并更新其状态。 -### 步骤 1.4. Updating a check run +### 步骤 1.4. 更新检查运行 -When your `create_check_run` method runs, it asks GitHub to create a new check run. When Github finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check. +当 `create_check_run` 方法运行时，它会要求 GitHub 创建新的检查运行。 当 Github 完成创建检查运行时，您将收到带有 `created` 操作的 `check_run` web 挂钩事件。 该事件是您开始运行检查的信号。 -You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run. +您需要更新事件处理程序以查找 `created` 操作。 在更新事件处理程序时，可以为 `rerequested` 操作添加条件。 当某人通过单击“Re-run（重新运行）”按钮在 GitHub 上重新运行单个测试时，GitHub 将 `rerequested` 检查运行事件发送到您的应用程序。 当检查运行为 `rerequested` 时，您需要启动整个进程并创建新的检查运行。 -To include a condition for the `check_run` event in the `post '/event_handler'` route, add the following code under `case request.env['HTTP_X_GITHUB_EVENT']`: +要在 `post '/event_handler'` 路由中包含 check_run 事件的条件，请在 `case request.env['HTTP_X_GITHUB_EVENT'] 案例下添加以下代码：

-``` ruby -when 'check_run' +
when 'check_run'
   # Check that the event is being sent to this app
   if @payload['check_run']['app']['id'].to_s === APP_IDENTIFIER
     case @payload['action']
@@ -220,15 +219,15 @@ when 'check_run'
       create_check_run
     end
   end
-```
+`
-GitHub sends all events for `created` check runs to every app installed on a repository that has the necessary checks permissions. That means that your app will receive check runs created by other apps. A `created` check run is a little different from a `requested` or `rerequested` check suite, which GitHub sends only to apps that are being requested to run a check. The code above looks for the check run's application ID. This filters out all check runs for other apps on the repository. +GitHub 将 `created` 检查运行的所有事件发送到仓库中安装的每个具有必要检查权限的应用程序。 这意味着您的应用程序将收到其他应用程序创建的检查运行。 `created` 检查运行与 `requested` 或 `rerequested` 检查套件稍有不同，GitHub 只将其发送给被请求运行检查的应用程序。 上面的代码查找检查运行的应用程序 ID。 这将过滤掉仓库中其他应用程序的所有检查运行。 -Next you'll write the `initiate_check_run` method, which is where you'll update the check run status and prepare to kick off your CI test. +接下来，您将编写 `initiate_check_run` 方法，您将在其中更新检查运行状态并准备开始 CI 测试。 -In this section, you're not going to kick off the CI test yet, but you'll walk through how to update the status of the check run from `queued` to `pending` and then from `pending` to `completed` to see the overall flow of a check run. In "[Part 2: Creating the Octo RuboCop CI test](#part-2-creating-the-octo-rubocop-ci-test)," you'll add the code that actually performs the CI test. +在本节中，您尚未开始 CI 测试，但是您将演练如何更新检查运行的状态，从 `queued` 到 `pending` 然后从 `pending` 到 `completed`，以查看检查运行的总体流程。 在“[第 2 部分：创建 Octo RuboCop CI 测试](#part-2-creating-the-octo-rubocop-ci-test)”中，您将添加实际执行 CI 测试的代码。 -Let's create the `initiate_check_run` method and update the status of the check run. Add the following code to the helpers section: +让我们创建 `initiate_check_run` 方法并更新检查运行的状态。 将以下代码添加到小助手部分： {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} ``` ruby @@ -240,7 +239,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -276,7 +275,7 @@ def initiate_check_run # Octokit doesn't yet support the Checks API, but it does provide generic # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run + # /rest/reference/checks#update-a-check-run updated_check_run = @installation_client.patch( "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", { @@ -305,53 +304,53 @@ end ``` {% endif %} -The code above calls the "[Update a check run](/v3/checks/runs/#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. +上述代码使用通用的 [`patch` HTTP 方法](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method)调用“[更新检查运行](/rest/reference/checks#update-a-check-run)”API 端点，以更新已创建的检查运行。 -Here's what this code is doing. First, it updates the check run's status to `in_progress` and sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`. +以下是此代码的作用。 首先，它将检查运行的状态更新为 `in_progress`，并将 `started_at` 时间设置为当前时间。 在本快速入门的[第 2 部分](#part-2-creating-the-octo-rubocop-ci-test)，您将添加代码以在 `***** RUN A CI TEST *****` 下开始真正的 CI 测试。 现在，您将该部分保留为占位符，因此后面的代码将模拟 CI 流程成功并且所有测试都通过。 最后，代码将检查运行的状态再次更新为 `completed`。 -You'll notice in the "[Update a check run](/v3/checks/runs/#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`. +在“[更新检查运行](/rest/reference/checks#update-a-check-run)”文档中，您会注意到，当您提供状态 `completed` 时，`conclusion` 和 `completed_at` 参数是必需的。 `conclusion` 总结检查运行的结果，可以是 `success`、`failure`、`neutral`、`cancelled`、`timed_out` 或 `action_required`。 您将结论设置为 `success`，将 `completed_at` 时间设置为当前时间，并将状态设置为 `completed`。 -You could also provide more details about what your check is doing, but you'll get to that in the next section. Let's test this code again by re-running `template_server.rb`: +您还可以提供有关检查操作的更多详细信息，但这些内容将在下一部分进行介绍。 让我们重新运行 `template_server.rb` 来测试此代码： ```shell $ ruby template_server.rb ``` -Head over to your open pull request and click the **Checks** tab. Click the "Re-run all" button in the upper left corner. You should see the check run move from `pending` to `in_progress` and end with `success`: +转到打开的拉取请求，然后单击 **Checks（检查）**选项卡。 单击左上角的“Re-run all（全部重新运行）”按钮。 您应该会看到检查运行的状态从 `pending` 变成 `in_progress`，最后变成 `success`： -![Completed check run](/assets/images/github-apps/github_apps_complete_check_run.png) +![完整的检查运行](/assets/images/github-apps/github_apps_complete_check_run.png) -### Part 2. Creating the Octo RuboCop CI test +### 第 2 部分。 创建 Octo RuboCop CI 测试 -[RuboCop](https://rubocop.readthedocs.io/en/latest/) is a Ruby code linter and formatter. It checks Ruby code to ensure that it complies with the "[Ruby Style Guide](https://github.com/rubocop-hq/ruby-style-guide)." RuboCop has three primary functions: +[RuboCop](https://rubocop.readthedocs.io/en/latest/) 是 Ruby 代码语法检查和格式化工具。 它检查 Ruby 代码以确保其符合“[Ruby 样式指南](https://github.com/rubocop-hq/ruby-style-guide)”。 RuboCop 有三个主要功能： -* Linting to check code style -* Code formatting -* Replaces the native Ruby linting capabilities using `ruby -w` +* 分析检查代码样式 +* 代码格式化 +* 使用 `ruby -w` 替换本地 Ruby 分析功能。 -Now that you've got the interface created to receive Checks API events and create check runs, you can create a check run that implements a CI test. +您已经创建了用于接收检查 API 事件和创建检查运行的接口，现在，您可以创建实现 CI 测试的检查运行。 -Your app will run RuboCop on the CI server and create check runs (CI tests in this case) that report the results that RuboCop reports to GitHub. +您的应用程序将在 CI 服务器上运行 RuboCop，并创建检查运行（本例中为 CI 测试），以报告 RuboCop 向 GitHub 报告的结果。 -The Checks API allows you to report rich details about each check run, including statuses, images, summaries, annotations, and requested actions. +检查 API 允许您报告关于每个检查运行的丰富细节，包括状态、图像、摘要、注释和请求的操作。 -Annotations are information about specific lines of code in a repository. An annotation allows you to pinpoint and visualize the exact parts of the code you'd like to show additional information for. That information can be anything: for example, a comment, an error, or a warning. This quickstart uses annotations to visualize RuboCop errors. +注释是关于仓库中特定代码行的信息。 注释允许您精确定位和可视化要显示其他信息的代码确切部分。 这些信息可以是任何内容：例如，注释、错误或警告。 本快速入门使用注释来可视化 RuboCop 错误。 -To take advantage of requested actions, app developers can create buttons in the **Checks** tab of pull requests. When someone clicks one of these buttons, the click sends a `requested_action` `check_run` event to the GitHub App. The action that the app takes is completely configurable by the app developer. This quickstart will walk you through adding a button that allows users to request that RuboCop fix the errors it finds. RuboCop supports automatically fixing errors using a command-line option, and you'll configure the `requested_action` to take advantage of this option. +为了利用请求的操作，应用程序开发者可以在拉取请求的 **Checks（检查）**选项卡中创建按钮。 当有人单击这些按钮之一时，该单击操作将发送 `requested_action` `check_run` 事件到 GitHub 应用程序。 应用程序执行的操作完全由应用程序开发者配置。 此快速入门将引导您添加一个按钮，允许用户请求 RuboCop 修复它发现的错误。 RuboCop 支持使用命令行选项自动修复错误，您将配置 `requested_action` 以利用此选项。 -Let's get started! These are the steps you'll complete in this section: +让我们开始吧！ 以下是您将在本部分中完成的步骤： -1. [Adding a Ruby file](#step-21-adding-a-ruby-file) -1. [Cloning the repository](#step-22-cloning-the-repository) -1. [Running RuboCop](#step-23-running-rubocop) -1. [Collecting RuboCop errors](#step-24-collecting-rubocop-errors) -1. [Updating the check run with CI test results](#step-25-updating-the-check-run-with-ci-test-results) -1. [Automatically fixing RuboCop errors](#step-26-automatically-fixing-rubocop-errors) -1. [Security tips](#step-27-security-tips) +1. [添加 Ruby 文件](#step-21-adding-a-ruby-file) +1. [克隆仓库](#step-22-cloning-the-repository) +1. [运行 RuboCop](#step-23-running-rubocop) +1. [收集 RuboCop 错误](#step-24-collecting-rubocop-errors) +1. [使用 CI 测试结果更新检查运行](#step-25-updating-the-check-run-with-ci-test-results) +1. [自动修复 RuboCop 错误](#step-26-automatically-fixing-rubocop-errors) +1. [安全提示](#step-27-security-tips) -### 步骤 2.1. Adding a Ruby file +### 步骤 2.1. 添加 Ruby 文件 -You can pass specific files or entire directories for RuboCop to check. In this quickstart, you'll run RuboCop on an entire directory. Because RuboCop only checks Ruby code, you'll want at least one Ruby file in your repository that contains errors. The example file provided below contains a few errors. Add this example Ruby file to the repository where your app is installed (make sure to name the file with an `.rb` extension, as in `myfile.rb`): +您可以传递特定文件或整个目录供 RuboCop 检查。 在本快速入门中，您将在整个目录上运行 RuboCop。 由于 RuboCop 只检查 Ruby 代码，因此您的仓库中至少需要一个含有错误的 Ruby 文件。 下面提供的示例文件包含一些错误。 将此示例 Ruby 文件添加到安装应用程序的仓库（确保使用 `.rb` 扩展名命名文件，如 `myfile.rb`）： ```ruby # The Octocat class tells you about different breeds of Octocat @@ -373,31 +372,31 @@ m = Octocat.new("Mona", "cat", "octopus") m.display ``` -### 步骤 2.2. Cloning the repository +### 步骤 2.2. 克隆仓库 -RuboCop is available as a command-line utility. That means your GitHub App will need to clone a local copy of the repository on the CI server so RuboCop can parse the files. To run Git operations in your Ruby app, you can use the [ruby-git](https://github.com/ruby-git/ruby-git) gem. +RuboCop 可用作命令行实用工具。 这意味着您的 GitHub 应用程序将需要克隆 CI 服务器上仓库的本地副本，以便 RuboCop 可以解析文件。 要在 Ruby 应用程序中运行 Git 操作，您可以使用 [ruby-git](https://github.com/ruby-git/ruby-git) gem。 -The `Gemfile` in the `building-a-checks-api-ci-server` repository already includes the ruby-git gem, and you installed it when you ran `bundle install` in the [prerequisite steps](#prerequisites). To use the gem, add this code to the top of your `template_server.rb` file: +`building-a-checks-api-ci-server` 仓库中的 `Gemfile` 已包含 ruby-git gem，您在[前提步骤](#prerequisites)中运行 `bundle install` 时安装了它。 要使用 gem，请将此代码添加到 `template_server.rb` 文件的顶部： ``` ruby require 'git' ``` -Your app needs read permission for "Repository contents" to clone a repository. Later in this quickstart, you'll need to push contents to GitHub, which requires write permission. Go ahead and set your app's "Repository contents" permission to **Read & write** now so you don't need to update it again later. To update your app's permissions: +您的应用程序需要“仓库内容”的读取权限才能克隆仓库。 在本快速入门后面的部分，您需要将内容推送到 GitHub，这需要写入权限。 现在将应用程序的“仓库内容”权限设置为 **Read & write（读取和写入）**，这样以后就不需要再更新它了。 要更新应用程序的权限： -1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar. -1. In the "Permissions" section, find "Repository contents", and select **Read & write** in the "Access" dropdown next to it. +1. 从[应用程序设置页面](https://github.com/settings/apps)选择应用程序，然后单击边栏中的 **Permissions & Webhooks（权限和 web 挂钩）**。 +1. 在“Permissions（权限）”部分，找到“Repository contents（仓库内容）”，然后在其旁边的“Access（访问权限）”下拉列表中选择 **Read & write（读取和写入）**。 {% data reusables.apps.accept_new_permissions_steps %} -To clone a repository using your GitHub App's permissions, you can use the app's installation token (`x-access-token:`) shown in the example below: +要使用 GitHub 应用程序的权限克隆仓库，您可以使用该应用程序的安装令牌 (`x-access-token:`)，如下例所示： ```shell git clone https://x-access-token:@github.com//.git ``` -The code above clones a repository over HTTP. It requires the full repository name, which includes the repository owner (user or organization) and the repository name. For example, the [octocat Hello-World](https://github.com/octocat/Hello-World) repository has a full name of `octocat/hello-world`. +上面的代码通过 HTTP 克隆仓库。 它需要完整的仓库名称，其中包括仓库所有者（用户或组织）和仓库名称。 例如，[octocat Hello-World](https://github.com/octocat/Hello-World) 仓库的全名是 `octocat/hello-world`。 -After your app clones the repository, it needs to pull the latest code changes and check out a specific Git ref. The code to do all of this will fit nicely into its own method. To perform these operations, the method needs the name and full name of the repository and the ref to checkout. The ref can be a commit SHA, branch, or tag. Add the following new method to the helper method section in `template_server.rb`: +应用程序克隆仓库后，它需要拉取最新的代码更改并检出特定的 Git ref。 执行所有这些操作的代码将很好地适应其自己的方法。 要执行这些操作，该方法需要仓库的名称和全名以及要检出的 ref。 Ref 可以是提交 SHA、分支或标记。 将以下新方法添加到 `template_server.rb` 中的辅助方法部分： ``` ruby # Clones the repository to the current working directory, updates the @@ -416,11 +415,11 @@ def clone_repository(full_repo_name, repository, ref) end ``` -The code above uses the `ruby-git` gem to clone the repository using the app's installation token. This code clones the code in the same directory as `template_server.rb`. To run Git commands in the repository, the code needs to change into the repository directory. Before changing directories, the code stores the current working directory in a variable (`pwd`) to remember where to return before exiting the `clone_repository` method. +上面的代码通过应用程序的安装令牌使用 `rubby-git` gem 来克隆仓库。 此代码在 `template_server.rb` 的目录中克隆代码。 要在仓库中运行 Git 命令，代码需要更改为仓库目录。 在更改目录之前，代码将当前工作目录存储在变量 (`pwd`) 中，以便在退出 `clone_repository` 方法之前记住要返回的位置。 -From the repository directory, this code fetches and merges the latest changes (`@git.pull`), checks out the ref (`@git.checkout(ref)`), then changes the directory back to the original working directory (`pwd`). +此代码从仓库目录获取并合并最新的更改 (`@git.pull`)，检出 ref (`@git.checkout(ref)`)，然后将目录改回原始工作目录 (`pwd`)。 -Now you've got a method that clones a repository and checks out a ref. Next, you need to add code to get the required input parameters and call the new `clone_repository` method. Add the following code under the `***** RUN A CI TEST *****` comment in your `initiate_check_run` helper method: +现在，您有了克隆仓库并检出 ref 的方法。 接下来，您需要添加代码来获取所需的输入参数，并调用新的 `clone_repository` 方法。 在 `initiate_check_run` 辅助方法的 `***** RUN A CI TEST *****` 注释下添加以下代码： ``` ruby # ***** RUN A CI TEST ***** @@ -431,13 +430,13 @@ head_sha = @payload['check_run']['head_sha'] clone_repository(full_repo_name, repository, head_sha) ``` -The code above gets the full repository name and the head SHA of the commit from the `check_run` webhook payload. +上面的代码从 `check_run` web 挂钩有效负载获取完整的仓库名称和注释的头部 SHA。 -### 步骤 2.3. Running RuboCop +### 步骤 2.3. 运行 RuboCop -太好了！ You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/v3/checks/runs/#create-a-check-run). +太好了！ 您正在克隆仓库并使用 CI 服务器创建检查运行。 现在，您将了解 [RuboCop 语法检查](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker)和[检查 API 注释](/rest/reference/checks#create-a-check-run)的实质内容。 -The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. +下面的代码运行 RuboCop 并以 JSON 格式保存样式代码错误。 将此代码添加到您在[上一步](#step-22-cloning-the-repository)中添加的 `clone_repository` 调用之下，更新要完成检查运行的代码之上。 ``` ruby # Run RuboCop on all files in the repository @@ -447,23 +446,23 @@ logger.debug @report @output = JSON.parse @report ``` -The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) for details and an example of the JSON format. +上面的代码在仓库目录中的所有文件上运行 RuboCop 。 选项 `--format json` 是将分析结果的副本保存为机器可解析格式的方便方法。 有关 JSON 格式的详细信息和示例，请参阅 [RuboCop 文档](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter)。 -Because this code stores the RuboCop results in a `@report` variable, it can safely remove the checkout of the repository. This code also parses the JSON so you can easily access the keys and values in your GitHub App using the `@output` variable. +由于此代码将 RuboCop 结果存储在 `@report` 变量中，因此可以安全地删除仓库的检出。 此代码还解析 JSON，因此您可以使用 `@output` 变量轻松访问 GitHub 应用程序中的键和值。 {% note %} -**Note:** The command used to remove the repository (`rm -rf`) cannot be undone. See [Step 2.7. Security tips](#step-27-security-tips) to learn how to check webhooks for injected malicious commands that could be used to remove a different directory than intended by your app. For example, if a bad actor sent a webhook with the repository name `./`, your app would remove the root directory. 😱 If for some reason you're _not_ using the method `verify_webhook_signature` (which is included in `template_server.rb`) to validate the sender of the webhook, make sure you check that the repository name is valid. +**注：**用于删除仓库的命令 (`rm -rf`) 无法撤销。 请参阅[步骤 2.7. 安全提示](#step-27-security-tips)了解如何检查 web 挂钩中是否注入了可用于删除与应用程序预期不同的目录的恶意命令。 例如，如果一个恶意行为者发送了一个仓库名称为 `./` 的 web 挂钩，您的应用程序将会删除根目录。 😱 如果出于某些原因，您_没有_使用方法 `verify_webhook_signature`（包含在 `template_server.rb` 中）来验证 web 挂钩的发送者，请确保检查仓库名称是否有效。 {% endnote %} -You can test that this code works and see the errors reported by RuboCop in your server's debug output. Start up the `template_server.rb` server again and create a new pull request in the repository where you're testing your app: +您可以测试此代码是否有效，并在服务器的调试输出中查看 RuboCop 报告的错误。 再次启动 `template_server.rb` 服务器，并在测试应用程序的仓库中创建新的拉取请求： ```shell $ ruby template_server.rb ``` -You should see the linting errors in the debug output, although they aren't printed with formatting. You can use a web tool like [JSON formatter](https://jsonformatter.org/) to format your JSON output like this formatted linting error output: +您应该在调试输出中看到分析错误，尽管它们不是用格式打印的。 您可以使用 [JSON 格式化程序](https://jsonformatter.org/)之类的 web 工具来格式化 JSON 输出，例如以下格式化的分析错误输出： ```json { @@ -519,24 +518,24 @@ You should see the linting errors in the debug output, although they aren't prin } ``` -### 步骤 2.4. Collecting RuboCop errors +### 步骤 2.4. 收集 RuboCop 错误 -The `@output` variable contains the parsed JSON results of the RuboCop report. As shown above, the results contain a `summary` section that your code can use to quickly determine if there are any errors. The following code will set the check run conclusion to `success` when there are no reported errors. RuboCop reports errors for each file in the `files` array, so if there are errors, you'll need to extract some data from the file object. +`@output` 变量包含 RuboCop 报告的已解析 JSON 结果。 如上所示，结果包含 `summary` 部分，您的代码可使用它快速确定是否存在错误。 如果没有报告错误，以下代码将检查运行结论设置为 `success`。 RuboCop 报告 `files` 数组中每个文件的错误，如果存在错误，则需要从文件对象中提取一些数据。 -The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/v3/checks/runs/#update-a-check-run) with annotations. +检查 API 允许您为特定代码行创建注释。 创建或更新检查运行时，可以添加注释。 在本快速入门中，您将使用注释[更新检查运行](/rest/reference/checks#update-a-check-run)。 -The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/v3/checks/runs/#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. +检查 API 将注释数量限制为每个 API 请求最多 50 个注释。 要创建 50 个以上的注释，您必须向[更新检查运行](/rest/reference/checks#update-a-check-run)端点发出多个请求。 例如，要创建 105 个注释，您需要调用[更新检查运行](/rest/reference/checks#update-a-check-run)端点三次。 前两个请求各有 50 个注释，第三个请求将包括其余五个注释。 每次更新检查运行时，注释都会添加到已经存在的检查运行注释列表中。 -A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/v3/checks/runs/#annotations-object-1) reference documentation for details. +检查运行会将注释作为对象数组。 每个注释对象必须包括 `path`、`start_line`、`end_line`、`annotation_level` 和 `message`。 RuboCop 还提供 `start_column` 和 `end_column`， 因此您可以在注释中包括这些可选参数。 注释只支持同一行上的 `start_column` 和 `end_column`。 更多信息请参阅 [`annotations` 对象](/rest/reference/checks#annotations-object-1)参考文档。 -You'll extract the required information from RuboCop needed to create each annotation. Append the following code to the code you added in the [previous section](#step-23-running-rubocop): +您将从 RuboCop 中提取创建每个注释所需的信息。 将以下代码追加到您[上一节](#step-23-running-rubocop)中添加的代码： ``` ruby annotations = [] # You can create a maximum of 50 annotations per request to the Checks # API. To add more than 50 annotations, use the "Update a check run" API # endpoint. This example code limits the number of annotations to 50. -# See /v3/checks/runs/#update-a-check-run +# See /rest/reference/checks#update-a-check-run # for details. max_annotations = 50 @@ -584,21 +583,21 @@ else end ``` -This code limits the total number of annotations to 50. But you can modify this code to update the check run for each batch of 50 annotations. The code above includes the variable `max_annotations` that sets the limit to 50, which is used in the loop that iterates through the offenses. +此代码将注释总数限制为 50。 但是，您可以修改此代码以更新每批 50 个注释的检查运行。 上面的代码包含变量 `max_annotations`，它将限制设置为 50，用于循环遍历超限问题。 -When the `offense_count` is zero, the CI test is a `success`. If there are errors, this code sets the conclusion to `neutral` in order to prevent strictly enforcing errors from code linters. But you can change the conclusion to `failure` if you would like to ensure that the check suite fails when there are linting errors. +当 `offense_count` 为零时，CI 测试为 `success`。 如果存在错误，此代码会将结论设置为 `neutral`，以防止严格执行来自代码语法检查的错误。 但如果您想确保检查套件在发现分析错误时失败，您可以将结论更改为 `failure`。 -When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. +当报告错误时，上面的代码将遍历 RuboCop 报告中的 `files` 数组。 对于每个文件，它会提取文件路径，并将注释级别设置为 `notice`。 您可以更进一步，为每种类型的 [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/) 设置特定的警告级别，但本快速入门为简单起见，将所有错误都设置为 `notice` 级别。 -This code also iterates through each error in the `offenses` array and collects the location of the offense and error message. After extracting the information needed, the code creates an annotation for each error and stores it in the `annotations` array. Because annotations only support start and end columns on the same line, `start_column` and `end_column` are only added to the `annotation` object if the start and end line values are the same. +此代码还会遍历 `offenses` 数组中的每个错误，并收集超限和错误消息的位置。 提取所需的信息后，代码将为每个错误创建一个注释，并将其存储在 `annotations` 数组中。 由于注释只支持同一行上的开始和结束列，因此，只有在开始和结束行的值相同的情况下，才会将 `start_column` 和 `end_column` 添加到 `annotation` 对象中。 -This code doesn't yet create an annotation for the check run. You'll add that code in the next section. +此代码尚未为检查运行创建注释。 您将在下一节中添加该代码。 -### 步骤 2.5. Updating the check run with CI test results +### 步骤 2.5. 使用 CI 测试结果更新检查运行 -Each check run from GitHub contains an `output` object that includes a `title`, `summary`, `text`, `annotations`, and `images`. The `summary` and `title` are the only required parameters for the `output`, but those alone don't offer much detail, so this quickstart adds `text` and `annotations` too. The code here doesn't add an image, but feel free to add one if you'd like! +GitHub 的每个检查运行都包括 `output` 对象，其中包含 `title`、`summary`、`text`、`annotations` 和 `images`。 只有 `summary` 和 `title` 是 `output` 的必需参数，但仅仅这些参数并不能提供太多细节，因此本快速入门还添加了 `text` 和 `annotations`。 此处的代码没有添加图片，但是您可以根据需要随意添加！ -For the `summary`, this example uses the summary information from RuboCop and adds some newlines (`\n`) to format the output. You can customize what you add to the `text` parameter, but this example sets the `text` parameter to the RuboCop version. To set the `summary` and `text`, append this code to the code you added in the [previous section](#step-24-collecting-rubocop-errors): +对于 `summary`，此示例使用 RuboCop 的摘要信息，并添加一些换行符 (`\n`) 来格式化输出。 您可以自定义要添加到 `text` 参数的内容，而此示例将 `text` 参数设置为 RuboCop 版本。 要设置 `summary` 和 `text`，请将此代码追加到您在[上一节](#step-24-collecting-rubocop-errors)中添加的代码中： ``` ruby # Updated check run summary and text parameters @@ -606,7 +605,7 @@ summary = "Octo RuboCop summary\n-Offense count: #{@output['summary']['offense_c text = "Octo RuboCop version: #{@output['metadata']['rubocop_version']}" ``` -Now you've got all the information you need to update your check run. In the [first half of this quickstart](#step-14-updating-a-check-run), you added this code to set the status of the check run to `success`: +现在您已经获得了更新检查运行所需的所有信息。 在[本快速入门的前半部分](#step-14-updating-a-check-run)，您添加了此代码以将检查运行的状态设置为 `success`： {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} ``` ruby @@ -638,7 +637,7 @@ updated_check_run = @installation_client.patch( ``` {% endif %} -You'll need to update that code to use the `conclusion` variable you set based on the RuboCop results (to `success` or `neutral`). You can update the code with the following: +您需要更新该代码以使用基于 RuboCop 结果设置的 `conclusion` 变量（`success` 或 `neutral`）。 您可以使用以下内容更新代码： {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} ``` ruby @@ -692,48 +691,48 @@ updated_check_run = @installation_client.patch( ``` {% endif %} -Now that you're setting a conclusion based on the status of the CI test and you've added the output from the RuboCop results, you've created a CI test! Congratulations. 🙌 +现在，您正在根据 CI 测试的状态设置结论，并且添加了 RuboCop 结果的输出，您已经创建了 CI 测试！ 恭喜。 🙌 -The code above also adds a feature to your CI server called [requested actions](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/) via the `actions` object. {% if currentVersion == "free-pro-team@latest" %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}Requested actions add a button in the **Checks** tab on GitHub that allows someone to request the check run to take additional action. The additional action is completely configurable by your app. For example, because RuboCop has a feature to automatically fix the errors it finds in Ruby code, your CI server can use a requested actions button to allow people to request automatic error fixes. When someone clicks the button, the app receives the `check_run` event with a `requested_action` action. Each requested action has an `identifier` that the app uses to determine which button was clicked. +上面的代码还通过 `actions` 对象向您的 CI 服务器添加了一个名为 [requested actions](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/) 的功能。 {% if currentVersion == "free-pro-team@latest" %}（请注意，这与 [GitHub 操作](/actions)无关。） {% endif %}请求的操作在 GitHub 的 **Checks（检查）**选项卡中添加一个按钮，允许用户请求检查运行执行附加操作。 附加操作完全由您的应用程序配置。 例如，由于 RuboCop 具有自动修复在 Ruby 代码中发现的错误的功能，因此您的 CI 服务器可以使用请求操作按钮来允许用户请求自动修复错误。 当有人单击该按钮时，应用程序会收到带有 `requested_action` 操作的 `check_run` 事件。 每个请求的操作都有一个 `identifier`，应用程序使用它来确定哪个按钮被单击。 -The code above doesn't have RuboCop automatically fix errors yet. You'll add that in the next section. But first, take a look at the CI test that you just created by starting up the `template_server.rb` server again and creating a new pull request: +上面的代码还没有让 RuboCop 自动修复错误。 您将在下一节中添加该功能。 但我们先通过再次启动 `template_server.rb` 服务器并创建一个新的拉取请求，来看看您刚刚创建的 CI 测试： ```shell $ ruby template_server.rb ``` -The annotations will show up in the **Checks** tab. +注释将显示在 **Checks（检查）**选项卡中。 -![Check run annotations in the checks tab](/assets/images/github-apps/github_apps_checks_annotations.png) +![检查选项卡中的检查运行注释](/assets/images/github-apps/github_apps_checks_annotations.png) -Notice the "Fix this" button that you created by adding a requested action. +请注意您通过添加请求的操作创建的“Fix this（修复此问题）”按钮。 ![检查运行请求操作按钮](/assets/images/github-apps/github_apps_checks_fix_this_button.png) -If the annotations are related to a file already included in the PR, the annotations will also show up in the **Files changed** tab. +如果注释与 PR 中已包含的文件有关，则注释还将显示在 **Files changed（文件已更改）**选项卡中。 -![Check run annotations in the files changed tab](/assets/images/github-apps/github_apps_checks_annotation_diff.png) +![文件已更改选项卡中的检查运行注释](/assets/images/github-apps/github_apps_checks_annotation_diff.png) -### 步骤 2.6. Automatically fixing RuboCop errors +### 步骤 2.6. 自动修复 RuboCop 错误 -If you've made it this far, kudos! 👏 You've already created a CI test. In this section, you'll add one more feature that uses RuboCop to automatically fix the errors it finds. You already added the "Fix this" button in the [previous section](#step-25-updating-the-check-run-with-ci-test-results). Now you'll add the code to handle the `requested_action` check run event triggered when someone clicks the "Fix this" button. +如果您走到了这一步，为您点赞！ 👏 您已经创建了 CI 测试。 在本节中，您将添加另外一个功能，即使用 RuboCop 自动修复它发现的错误。 您在[上一节](#step-25-updating-the-check-run-with-ci-test-results)中已经添加了“Fix this（修复此问题）”按钮。 现在，您将添加代码以处理当有人单击“Fix this（修复此问题）”按钮时触发的 `requested_action` 检查运行事件。 -The RuboCop tool [offers](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. +RuboCop 工具[提供](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) `--auto-correct` 命令行选项，以自动修复它发现的错误。 使用 `--auto-correct` 功能时，更新将应用于服务器上的本地文件。 在 RuboCop 发挥作用之后，您需要将更改推送到 GitHub。 -To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set. +要推送到仓库，您的应用程序必须具备“仓库内容”的写入权限。 您在[步骤 2.2 中重新设置了该权限。 将仓库克隆](#step-22-cloning-the-repository)为**Read & write（读取和写入）**，现在所有设置就绪。 -In order to commit files, Git must know which [username](/articles/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. 例如： +要提交文件，Git 必须知道哪些[用户名](/articles/setting-your-username-in-git/)和[电子邮件](/articles/setting-your-commit-email-address-in-git/)与提交关联。 在 `.env` 文件中再添加两个变量，以存储名称 (`GITHUB_APP_USER_NAME`) 和电子邮件 (`GITHUB_APP_USER_EMAIL`) 设置。 您的名称可以是应用程序名称，电子邮件可以是您在本例中想使用的任何电子邮件地址。 例如： ``` GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` -Once you've updated your `.env` file with the name and email of the author and committer, you'll be ready to add code to read the environment variables and set the Git configuration. You'll add that code soon. +使用作者和提交者的名称和电子邮件更新 `.env` 文件后，即可准备添加代码以读取环境变量并设置 Git 配置。 您很快就将添加该代码。 -When someone clicks the "Fix this" button, your app receives the [check run webhook](/webhooks/event-payloads/#check_run) with the `requested_action` action type. +当有人单击“Fix this（修复此问题）”按钮时，应用程序会收到操作类型为 `requested_action` 的[检查运行 web 挂钩](/webhooks/event-payloads/#check_run)。 -In [Step 1.4. Updating a check run](#step-14-updating-a-check-run) you updated the your `event_handler` to handle look for actions in the `check_run` event. You already have a case statement to handle the `created` and `rerequested` action types: +在[步骤 1.4. 更新检查运行时，](#step-14-updating-a-check-run)您更新了 `event_handler` 以处理 `check_run` 事件中的查找操作。 您已经有一个 case 语句来处理 `created` 和 `rerequested` 操作类型： ``` ruby when 'check_run' @@ -748,14 +747,14 @@ when 'check_run' end ``` -Add another `when` statement after the `rerequested` case to handle the `rerequested_action` event: +在 `rerequested` case 之后添加另一个 `when` 语句来处理 `rerequested_action` 事件： ``` ruby when 'requested_action' take_requested_action ``` -This code calls a new method that will handle all `requested_action` events for your app. Add the following method to the helper methods section of your code: +这个代码调用一个新方法来处理应用程序的所有 `requested_action` 事件。 将以下方法添加到代码的辅助方法部分： ``` ruby # Handles the check run `requested_action` event @@ -790,11 +789,11 @@ def take_requested_action end ``` -The code above clones a repository just like the code you added in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository). An `if` statement checks that the requested action's identifier matches the RuboCop button identifier (`fix_rubocop_notices`). When they match, the code clones the repository, sets the Git username and email, and runs RuboCop with the option `--auto-correct`. The `--auto-correct` option applies the changes to the local CI server files automatically. +上面的代码将克隆仓库，就像您在[步骤 2.2. 中添加的代码一样。 克隆仓库](#step-22-cloning-the-repository)。 `if` 语句检查请求操作的标识符是否匹配 RuboCop 按钮标识符 (`fix_rubocop_notices`)。 当它们匹配时，代码将克隆仓库，设置 Git 用户名和电子邮件，并使用选项 `--auto-correct` 运行 RuboCop。 `--auto-correct` 选项将更改自动应用于本地 CI 服务器文件。 -The files are changed locally, but you'll still need to push them to GitHub. You'll use the handy `ruby-git` gem again to commit all of the files. Git has a single command that stages all modified or deleted files and commits them: `git commit -a`. To do the same thing using `ruby-git`, the code above uses the `commit_all` method. Then the code pushes the committed files to GitHub using the installation token, using the same authentication method as the Git `clone` command. Finally, it removes the repository directory to ensure the working directory is prepared for the next event. +文件在本地更改，但您仍然需要将它们推送到 GitHub。 您将再次使用方便的 `ruby-git` gem 提交所有文件。 Git 有一个命令可以暂存所有已修改或删除的文件并提交它们：`git commit -a`。 为了使用 `rubby-git` 实现同样的功能，上面的代码使用 `commit_all` 方法。 然后，代码使用与 Git `clone` 命令相同的身份验证方法，通过安装令牌将提交的文件推送到GitHub。 最后，它删除仓库目录，以确保为下一个事件准备工作目录。 -搞定！ The code you have written now completes your Checks API CI server. 💪 Restart your `template_server.rb` server again and create a new pull request: +搞定！ 您编写的代码现在完成了检查 API CI 服务器的构建。 💪 再次重新启动 `template_server.rb` 服务器并创建新的拉取请求： ```shell $ ruby template_server.rb @@ -802,21 +801,21 @@ $ ruby template_server.rb {% data reusables.apps.sinatra_restart_instructions %} -This time, click the "Fix this" button to automatically fix the errors RuboCop found from the **Checks** tab. +现在，单击“Fix this（修复此问题）”按钮以自动修复 RuboCop 在 **Checks（检查）**选项卡中发现的错误。 -In the **Commits** tab, you'll see a brand new commit by the username you set in your Git configuration. You may need to refresh your browser to see the update. +在 **Commits（提交）**选项卡中，您会看到由 Git 配置中设置的用户名提供的全新提交。 您可能需要刷新浏览器才能看到更新。 -![A new commit to automatically fix Octo RuboCop notices](/assets/images/github-apps/github_apps_new_requested_action_commit.png) +![自动修复 Octo RuboCop 通知的新提交](/assets/images/github-apps/github_apps_new_requested_action_commit.png) -Because a new commit was pushed to the repo, you'll see a new check suite for Octo RuboCop in the **Checks** tab. But this time there are no errors because RuboCop fixed them all. 🎉 +由于新的提交被推送到仓库，您将在 **Checks（检查）**选项卡中看到新的 Octo RuboCop 检查套件。 但这次没有任何错误，因为 RuboCop 已经修复了所有错误。 🎉 -![No check suite or check run errors](/assets/images/github-apps/github_apps_checks_api_success.png) +![没有检查套件或检查运行错误](/assets/images/github-apps/github_apps_checks_api_success.png) -You can find the completed code for the app you just built in the `server.rb` file in the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository. +您可以在[使用检查 API 创建 CI 测试](https://github.com/github-developer/creating-ci-tests-with-the-checks-api)仓库的 `server.rb` 文件中找到您刚才构建的应用程序的完整代码。 -### 步骤 2.7. Security tips +### 步骤 2.7. 安全提示 -The template GitHub App code already has a method to verify incoming webhook payloads to ensure they are from a trusted source. If you are not validating webhook payloads, you'll need to ensure that when repository names are included in the webhook payload, the webhook does not contain arbitrary commands that could be used maliciously. The code below validates that the repository name only contains Latin alphabetic characters, hyphens, and underscores. To provide you with a complete example, the complete `server.rb` code available in the [companion repository](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) for this quickstart includes both the method of validating incoming webhook payloads and this check to verify the repository name. +模板 GitHub 应用程序代码已经有方法来验证传入的 web 挂钩有效负载，以确保它们来自受信任的源。 如果不验证 web 挂钩有效负载，则需要确保当仓库名称包含在 web 挂钩有效负载中时，该 web 挂钩不包含可能被恶意使用的任意命令。 下面的代码将验证仅包含拉丁字母、连字符和下划线的仓库名称。 为了提供完整的示例，[配套仓库](https://github.com/github-developer/creating-ci-tests-with-the-checks-api)中提供本快速入门的完整 `server.rb` 代码，包括验证传入 web 挂钩有效负载的方法和验证仓库名称的检查。 ``` ruby # This quickstart example uses the repository name in the webhook with @@ -834,39 +833,39 @@ end Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}. -* **Q:** My app isn't pushing code to GitHub. I don't see the fixes that RuboCop automatically makes! +* **问：**我的应用程序没有将代码推送到 GitHub。 我没有看到 RuboCop 自动进行修复！ - **A:** Make sure you have **Read & write** permissions for "Repository contents," and that you are cloning the repository with your installation token. See [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) for details. + **答：**确保您对“仓库内容”具有 **Read & write（读取和写入）**权限，并且使用安装令牌克隆仓库。 请参阅[步骤 2.2. 克隆仓库](#step-22-cloning-the-repository)了解详细信息。 -* **Q:** I see an error in the `template_server.rb` debug output related to cloning my repository. +* **问：**我在 `template_server.rb` 调试输出中看到与克隆仓库相关的错误。 - **A:** If you see the following error, you haven't deleted the checkout of the repository in one or both of the `initiate_check_run` or `take_requested_action` methods: + **答：**如果您看到以下错误，则说明您没有在 `initiate_check_run` 和/或 `take_requested_action` 方法中删除仓库的检出： ```shell 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:v1.9b2080277016f797074c4debd350745f4257f8dd@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: ``` - Compare your code to the `server.rb` file to ensure you have the same code in your `initiate_check_run` and `take_requested_action` methods. + 将您的代码与 `server.rb` 文件进行比较，以确保您的 `initiate_check_run` 和 `take_requested_action` 方法中具有相同的代码。 -* **Q:** New check runs are not showing up in the "Checks" tab on GitHub. +* **问：**新的检查运行未显示在 GitHub 的“Checks（检查）”选项卡中。 - **A:** Restart Smee and re-run your `template_server.rb` server. + **答：**重新启动 Smee 并重新运行 `template_server.rb` 服务器。 -* **Q:** I do not see the "Re-run all" button in the "Checks" tab on GitHub. +* **问：**我在 GitHub 的“Checks（检查）”选项卡 中没有看到“Re-run all（全部重新运行）”按钮。 - **A:** Restart Smee and re-run your `template_server.rb` server. + **答：**重新启动 Smee 并重新运行 `template_server.rb` 服务器。 ### 结论 -After walking through this guide, you've learned the basics of using the Checks API to create a CI server! To review, you: +完成本指南后，您已经学会了使用检查 API 创建 CI 服务器的基础知识！ To review, you: -* Configured your server to receive Checks API events and create check runs. -* Used RuboCop to check code in repositories and create annotations for the errors. -* Implemented a requested action that automatically fixes linter errors. +* 配置您的服务器来接收检查 API 事件并创建检查运行。 +* 使用 RuboCop 来检查仓库中的代码并为错误创建注释。 +* 实现自动修复语法检查错误的请求操作。 ### 后续步骤 Here are some ideas for what you can do next: -* Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors. -* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/v3/pulls/#create-a-pull-request) with a new branch based on the head branch. +* 目前，始终显示“Fix this（修复此问题）”按钮。 更新您编写的代码，仅在 RuboCop 发现错误时显示“Fix this（修复此问题）”按钮。 +* 如果您不希望 RuboCop 将文件直接提交到头部分支，您可以更新代码，以使用基于头部分支的新分支[创建拉取请求](/rest/reference/pulls#create-a-pull-request)。 diff --git a/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index bede289849..f375058c3b 100644 --- a/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -1,6 +1,6 @@ --- -title: Differences between GitHub Apps and OAuth Apps -intro: 'Understanding the differences between {% data variables.product.prodname_github_app %}s and {% data variables.product.prodname_oauth_app %}s will help you decide which app you want to create. An {% data variables.product.prodname_oauth_app %} acts as a GitHub user, whereas a {% data variables.product.prodname_github_app %} uses its own identity when installed on an organization or on repositories within an organization.' +title: GitHub 应用程序和 OAuth 应用程序之间的差异 +intro: '了解 {% data variables.product.prodname_github_app %} 和 {% data variables.product.prodname_oauth_app %} 之间的差异可帮助您决定要创建哪个应用程序。 在组织或组织内的仓库上安装时，{% data variables.product.prodname_oauth_app %} 代表 GitHub 用户，而 {% data variables.product.prodname_github_app %} 使用它自己的身份。' redirect_from: - /early-access/integrations/integrations-vs-oauth-applications/ - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type/ @@ -11,97 +11,97 @@ versions: github-ae: '*' --- -### Who can install GitHub Apps and authorize OAuth Apps? +### 谁可以安装 GitHub 应用程序并授权 OAuth 应用程序？ -You can install GitHub Apps in your personal account or organizations you own. If you have admin permissions in a repository, you can install GitHub Apps on organization accounts. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. +您可以在您的个人帐户或您拥有的组织中安装 GitHub 应用程序。 如果拥有仓库管理员权限，您可以在组织帐户上安装 GitHub 应用程序。 如果 GitHub 应用程序安装在仓库中，并且需要组织权限，则组织所有者必须批准该应用程序。 {% data reusables.apps.app_manager_role %} -By contrast, users _authorize_ OAuth Apps, which gives the app the ability to act as the authenticated user. For example, you can authorize an OAuth App that finds all notifications for the authenticated user. You can always revoke permissions from an OAuth App. +相比之下，一旦用户_授权_ OAuth 应用程序，该应用程序就能代表经身份验证的用户。 例如，您可以授权 OAuth 应用程序查找经身份验证用户的所有通知。 您可以随时撤销 OAuth 应用程序的权限。 {% data reusables.apps.deletes_ssh_keys %} -| GitHub 应用程序 | OAuth Apps | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| You must be an organization owner or have admin permissions in a repository to install a GitHub App on an organization. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. | You can authorize an OAuth app to have access to resources. | -| You can install a GitHub App on your personal repository. | You can authorize an OAuth app to have access to resources. | -| You must be an organization owner, personal repository owner, or have admin permissions in a repository to uninstall a GitHub App and remove its access. | You can delete an OAuth access token to remove access. | -| You must be an organization owner or have admin permissions in a repository to request a GitHub App installation. | If an organization application policy is active, any organization member can request to install an OAuth App on an organization. An organization owner must approve or deny the request. | +| GitHub 应用程序 | OAuth 应用程序 | +| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------ | +| 您必须是组织所有者或者具有仓库管理员权限才能在组织上安装 GitHub 应用程序。 如果 GitHub 应用程序安装在仓库中，并且需要组织权限，则组织所有者必须批准该应用程序。 | 您可以授权 OAuth 应用程序访问资源。 | +| 您可以在个人仓库上安装 GitHub 应用程序。 | 您可以授权 OAuth 应用程序访问资源。 | +| 您必须是组织所有者、个人仓库所有者或者拥有仓库的管理员权限才能卸载 GitHub 应用程序和删除其访问权限。 | 您可以删除 OAuth 访问令牌以删除访问权限。 | +| 您必须是组织所有者或者具有仓库管理员权限才能请求安装 GitHub 应用程序。 | 如果组织应用程序策略已激活，则任何组织成员都可以请求在组织上安装 OAuth 应用程序。 组织所有者必须批准或拒绝请求。 | -### What can GitHub Apps and OAuth Apps access? +### GitHub 应用程序和 OAuth 应用程序可以访问什么？ -Account owners can use a {% data variables.product.prodname_github_app %} in one account without granting access to another. For example, you can install a third-party build service on your employer's organization, but decide not to grant that build service access to repositories in your personal account. A GitHub App remains installed if the person who set it up leaves the organization. +帐户所有者可以在一个帐户中使用 {% data variables.product.prodname_github_app %} ，而不授予对其他帐户的访问权限。 例如，您可以在您的雇主组织中安装第三方构建服务，但决定不授权该构建服务访问您个人帐户中的仓库。 即使安装者离开组织，GitHub 应用程序仍然存在。 -An _authorized_ OAuth App has access to all of the user's or organization owner's accessible resources. +_授权的_ OAuth 应用程序有权访问用户或组织所有者可访问的所有资源。 -| GitHub 应用程序 | OAuth Apps | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Installing a GitHub App grants the app access to a user or organization account's chosen repositories. | Authorizing an OAuth App grants the app access to the user's accessible resources. For example, repositories they can access. | -| The installation token from a GitHub App loses access to resources if an admin removes repositories from the installation. | An OAuth access token loses access to resources when the user loses access, such as when they lose write access to a repository. | -| Installation access tokens are limited to specified repositories with the permissions chosen by the creator of the app. | An OAuth access token is limited via scopes. | -| GitHub Apps can request separate access to issues and pull requests without accessing the actual contents of the repository. | OAuth Apps need to request the `repo` scope to get access to issues, pull requests, or anything owned by the repository. | -| GitHub Apps aren't subject to organization application policies. A GitHub App only has access to the repositories an organization owner has granted. | If an organization application policy is active, only an organization owner can authorize the installation of an OAuth App. If installed, the OAuth App gains access to anything visible to the token the organization owner has within the approved organization. | -| A GitHub App receives a webhook event when an installation is changed or removed. This tells the app creator when they've received more or less access to an organization's resources. | OAuth Apps can lose access to an organization or repository at any time based on the granting user's changing access. The OAuth App will not inform you when it loses access to a resource. | +| GitHub 应用程序 | OAuth 应用程序 | +| -------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | +| 安装 GitHub 应用程序将授予该应用程序访问用户或组织帐户所选仓库的权限。 | 授权 OAuth 应用程序将授予该应用程序访问用户可访问资源的权限。 例如，他们可以访问的仓库。 | +| 如果管理员从安装中删除仓库，则 GitHub 应用程序的安装令牌将失去对资源的访问权限。 | 当用户失去对资源的访问权限时，例如失去对仓库的写入权限，OAuth 访问令牌也会失去相应的访问权限。 | +| 安装访问令牌仅限于指定的仓库，其权限由应用程序创建者选择。 | OAuth 访问令牌受作用域限制。 | +| GitHub Apps 可以请求单独访问议题和拉取请求，而不访问仓库的实际内容。 | OAuth 应用程序需要请求 `repo` 作用域才能访问议题、拉取请求或仓库拥有的任何内容。 | +| GitHub 应用程序不受组织应用程序策略的约束。 GitHub 应用程序只能访问组织所有者授权的仓库。 | 如果组织应用程序策略已激活，则只有组织所有者才能授权安装 OAuth 应用程序。 安装后，OAuth 应用程序将有权访问组织所有者在批准组织内的令牌可见的任何内容。 | +| 当安装被更改或删除时，GitHub 应用程序会收到 web 挂钩事件。 当它们对组织资源的访问权限扩大或缩小时，这将告诉应用程序创建者。 | 根据授予用户访问权限的变化，OAuth 应用程序可能会随时失去对组织或仓库的访问权限。 OAuth 应用程序在失去对资源的访问权限时不会通知您。 | -### Token-based identification +### 基于令牌的识别 {% note %} -**Note:** GitHub Apps can also use a user-based token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +**注：**GitHub 应用程序也可以使用基于用户的令牌。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 {% endnote %} -| GitHub 应用程序 | OAuth Apps | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| A GitHub App can request an installation access token by using a private key with a JSON web token format out-of-band. | An OAuth app can exchange a request token for an access token after a redirect via a web request. | -| An installation token identifies the app as the GitHub Apps bot, such as @jenkins-bot. | An access token identifies the app as the user who granted the token to the app, such as @octocat. | -| Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. | -| {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} Higher rate limits apply for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Rate limits for GitHub Apps](/developers/apps/rate-limits-for-github-apps)."{% endif %} | OAuth tokens use the user's rate limit of 5,000 requests per hour. | -| Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| {% data variables.product.prodname_github_app %}s can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_app %}s authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. |{% endif %} +| GitHub 应用程序 | OAuth 应用程序 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| GitHub 应用可以使用带外 JSON Web 令牌格式的私钥请求安装访问令牌。 | OAuth 应用程序可以通过 Web 请求在重定向后将请求令牌交换为访问令牌。 | +| 安装程序将应用程序识别为 GitHub 应用自动程序，例如 @jenkins-bot。 | 访问令牌将应用程序识别为向应用程序授予令牌的用户，例如 @octocat。 | +| 安装令牌在预定义的时间（当前为 1 小时）后过期。 | OAuth 令牌在被客户撤销之前一直保持活动状态。 | +| {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} 更高的速率限制适用于 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[GitHub 应用程序的速率限制](/developers/apps/rate-limits-for-github-apps)”。{% endif %} | OAuth 令牌使用用户的每小时 5,000 个请求的速率限制。 | +| 速率限制的增加可在 GitHub 应用程序级别（影响所有安装）和单个安装级别上授予。 | 速率限制的增加按 OAuth 应用程序授予。 授予该 OAuth 应用程序的每个令牌都会获得增加的上限。 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| {% data variables.product.prodname_github_app %} 可以代表用户进行身份验证，这称为用户到服务器请求。 授权流程与 OAuth 应用程序授权流程相同。 用户到服务器令牌可能会过期，可通过刷新令牌进行续订。 更多信息请参阅“[刷新用户到服务器访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”和“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 | {% data variables.product.prodname_oauth_app %} 使用的 OAuth 流程代表用户授权 {% data variables.product.prodname_oauth_app %}。 这与用于 {% data variables.product.prodname_github_app %} 用户到服务器授权中使用的流程相同。 |{% endif %} -### Requesting permission levels for resources +### 请求资源的权限级别 -Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to request access only to what they need. For example, a Continuous Integration (CI) GitHub App can request read access to repository content and write access to the status API. Another GitHub App can have no read or write access to code but still have the ability to manage issues, labels, and milestones. OAuth Apps can't use granular permissions. +与 OAuth 应用程序不同，GitHub 应用程序具有针对性的权限，只允许它们请求访问所需的资源。 例如，持续集成 (CI) GitHub 应用程序可以请求对仓库内容的读取权限和对状态 API 的写入权限。 另一个 GitHub 应用程序可能没有对代码的读取或写入权限，但仍能管理议题、标签和里程碑。 OAuth 应用程序不能使用精细权限。 -| 访问 | GitHub Apps (`read` or `write` permissions) | OAuth Apps | -| ------------------------------------------------------- | --------------------------------------------------------- | -------------------------------------------- | -| **For access to public repositories** | Public repository needs to be chosen during installation. | `public_repo` scope. | -| **For access to repository code/contents** | 仓库内容 | `repo` scope. | -| **For access to issues, labels, and milestones** | 议题 | `repo` scope. | -| **For access to pull requests, labels, and milestones** | 拉取请求 | `repo` scope. | -| **For access to commit statuses (for CI builds)** | Commit statuses | `repo:status` scope. | -| **For access to deployments and deployment statuses** | 部署 | `repo_deployment` scope. | -| **To receive events via a webhook** | A GitHub App includes a webhook by default. | `write:repo_hook` or `write:org_hook` scope. | +| 访问 | GitHub 应用程序（`read` 或 `write` 权限） | OAuth 应用程序 | +| -------------------- | -------------------------------- | ----------------------------------------- | +| **访问公共仓库** | 需要在安装过程中选择公共仓库。 | `public_repo` 作用域。 | +| **访问仓库代码/内容** | 仓库内容 | `repo` 作用域。 | +| **获取议题、标签和里程碑** | 议题 | `repo` 作用域。 | +| **获取拉取请求、标签和里程碑** | 拉取请求 | `repo` 作用域。 | +| **访问提交状态（对于 CI 构建）** | 提交状态 | `repo:status` 作用域。 | +| **访问部署和部署状态** | 部署 | `repo_deployment` 作用域。 | +| **通过 web 挂钩接收事件** | GitHub 应用程序默认包含一个 web 挂钩。 | `write:repo_hook` 或 `write:org_hook` 作用域。 | -### Repository discovery +### 仓库发现 -| GitHub 应用程序 | OAuth Apps | -| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | -| GitHub Apps can look at `/installation/repositories` to see repositories the installation can access. | OAuth Apps can look at `/user/repos` for a user view or `/orgs/:org/repos` for an organization view of accessible repositories. | -| GitHub Apps receive webhooks when repositories are added or removed from the installation. | OAuth Apps create organization webhooks for notifications when a new repository is created within an organization. | +| GitHub 应用程序 | OAuth 应用程序 | +| --------------------------------------------------------- | ----------------------------------------------------------------------- | +| GitHub 应用程序可以访问 `/installation/repositories` 以查看安装可访问的仓库。 | OAuth 应用程序可访问用户视图中的 `/user/repos` 或组织视图中的 `/orgs/:org/repos` 以查看可访问的资源。 | +| 当从安装中添加或删除仓库时，GitHub 应用程序会接收 web 挂钩。 | 在组织内创建新仓库时，OAuth 应用程序为通知创建组织 web 挂钩。 | ### Web 挂钩 -| GitHub 应用程序 | OAuth Apps | -| ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they needs to receive events from. | -| GitHub Apps receive certain organization-level events with the organization member's permission. | OAuth Apps request the organization webhook scope to create an organization webhook for each organization they need to receive organization-level events from. | +| GitHub 应用程序 | OAuth 应用程序 | +| --------------------------------------------------- | ------------------------------------------------------- | +| 默认情况下，GitHub 应用程序有一个 web 挂钩，可根据配置接收它们有权访问的每个仓库中的事件。 | OAuth 应用程序请求 web 挂钩作用域为它们需要接收其事件的每个仓库创建仓库 web 挂钩。 | +| GitHub 应用程序使用组织成员的权限接收某些组织级别的事件。 | OAuth 应用程序请求组织 web 挂钩作用域为它们需要接收其组织级别事件的每个组织创建组织 web 挂钩。 | -### Git access +### Git 访问 -| GitHub 应用程序 | OAuth Apps | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | -| The token is used as the HTTP password. | The token is used as the HTTP username. | +| GitHub 应用程序 | OAuth 应用程序 | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | +| GitHub 应用程序请求仓库内容权限，并使用安装令牌通过[基于 HTTP 的 Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation) 进行身份验证。 | OAuth 应用程序请求 `write:public_key` 作用域，并通过 API [创建部署密钥](/rest/reference/repos#create-a-deploy-key)。 然后您可以使用该密钥来执行 Git 命令。 | +| 令牌用作 HTTP 密码。 | 令牌用作 HTTP 用户名。 | -### Machine vs. bot accounts +### 机器与机器人帐户 -Machine user accounts are OAuth-based user accounts that segregate automated systems using GitHub's user system. +机器用户帐户是基于 OAuth 的用户帐户，它使用 GitHub 的用户系统隔离自动系统。 -Bot accounts are specific to GitHub Apps and are built into every GitHub App. +机器人帐户特定于 GitHub 应用，并内置于每个 GitHub 应用程序中。 -| GitHub 应用程序 | OAuth Apps | -| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | -| GitHub App bots do not consume a {% data variables.product.prodname_enterprise %} seat. | A machine user account consumes a {% data variables.product.prodname_enterprise %} seat. | -| Because a GitHub App bot is never granted a password, a customer can't sign into it directly. | A machine user account is granted a username and password to be managed and secured by the customer. | +| GitHub 应用程序 | OAuth 应用程序 | +| ---------------------------------------------------------------------- | ------------------------------------------------------------- | +| GitHub 应用程序机器人不占用 {% data variables.product.prodname_enterprise %} 席位。 | 机器用户帐户占用 {% data variables.product.prodname_enterprise %} 席位。 | +| 由于 GitHub 应用程序机器人永远不会被授予密码，因此客户无法直接登录它。 | 机器用户帐户被授予由客户管理和保护的用户名和密码。 | diff --git a/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 314ead212d..4d11be938d 100644 --- a/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Identifying and authorizing users for GitHub Apps +title: 识别和授权 GitHub 应用程序用户 intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}' redirect_from: - /early-access/integrations/user-identification-authorization/ @@ -14,27 +14,27 @@ versions: {% data reusables.pre-release-program.expiring-user-access-tokens-beta %} -When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build. +当 GitHub 应用程序代表用户时，它执行用户到服务器请求。 这些请求必须使用用户的访问令牌进行授权。 用户到服务器请求包括请求用户的数据，例如确定要向特定用户显示哪些仓库。 这些请求还包括用户触发的操作，例如运行构建。 {% data reusables.apps.expiring_user_authorization_tokens %} -### Identifying users on your site +### 识别站点上的用户 -To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow). +要授权用户使用在浏览器中运行的标准应用程序，请使用 [web 应用程序流程](#web-application-flow)。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628). +要授权用户使用不直接访问浏览器的无头应用程序（例如 CLI 工具或 Git 凭据管理器），请使用[设备流程](#device-flow)。 设备流程使用 OAuth 2.0 [设备授权授予](https://tools.ietf.org/html/rfc8628)。 {% endif %} ### Web 应用程序流程 -Using the web application flow, the process to identify users on your site is: +使用 web 应用程序流程时，识别您站点上用户的过程如下： 1. 用户被重定向，以请求他们的 GitHub 身份 2. 用户被 GitHub 重定向回您的站点 -3. Your GitHub App accesses the API with the user's access token +3. 您的 GitHub 应用程序使用用户的访问令牌访问 API -If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)." +如果您在创建或修改应用程序时选择**在安装过程中请求用户授权 (OAuth)**，则步骤 1 将在应用程序安装过程中完成。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。 #### 1. 请求用户的 GitHub 身份 @@ -44,50 +44,50 @@ If you select **Request user authorization (OAuth) during installation** when cr ##### 参数 -| 名称 | 类型 | 描述 | -| -------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `字符串` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. | -| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 This must be an exact match to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters. | -| `state` | `字符串` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data. | -| `login` | `字符串` | 提供用于登录和授权应用程序的特定账户。 | +| 名称 | 类型 | 描述 | +| -------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `字符串` | **必填。**GitHub 应用程序的客户端 ID。 选择应用程序时，您可以在 [GitHub 应用程序设置](https://github.com/settings/apps)中找到它。 | +| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 它必须完全匹配设置 GitHub 应用程序时 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 作为 **Callback URL（回调 URL）**提供的 URL 之一 {% else %} 在 **User authorization callback URL（用户授权回调 URL）**字段中提供的 URL{% endif %}，并且不能包含任何其他参数。 | +| `state` | `字符串` | 它应该包含一个随机字符串以防止伪造攻击，并且可以包含任何其他任意数据。 | +| `login` | `字符串` | 提供用于登录和授权应用程序的特定账户。 | {% note %} -**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user. +**注** ：不需要在授权请求中提供作用域。 不同于传统的 OAuth，授权令牌仅限于与您的 GitHub 应用程序和用户的应用程序相关联的权限。 {% endnote %} #### 2. 用户被 GitHub 重定向回您的站点 -If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted. +如果用户接受您的请求，GitHub 将重定向回您的站点，其中，代码参数为临时 `code`，`state` 参数为您在上一步提供的状态。 如果状态不匹配，则请求是由第三方创建的，该过程应中止。 {% note %} -**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation. +**注：**如果您在创建或修改应用程序时选择**在安装过程中请求用户授权 (OAuth)**，则 GitHub 将返回需要交换访问令牌的临时 `code`。 当 GitHub 在应用程序安装过程中启动 OAuth 流程时，不会返回 `state` 参数。 {% endnote %} -Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." +将此 `code` 交换为访问令牌。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} 启用过期令牌后，访问令牌将在 8 小时后过期，刷新令牌将在 6 个月后过期。 每次刷新令牌时都会得到一个新的刷新令牌。 更多信息请参阅“[刷新用户到服务器访问令牌](/developers/apps/refreshing-user-to-server-access-tokens)”。 -Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} +过期用户令牌当前是用户到服务器令牌过期测试版的一部分，可能会更改。 要选择使用用户到服务器令牌过期测试版功能，请参阅“[激活应用程序的测试版功能](/developers/apps/activating-beta-features-for-apps)”。{% endif %} POST {% data variables.product.oauth_host_code %}/login/oauth/access_token ##### 参数 -| 名称 | 类型 | 描述 | -| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `字符串` | **Required.** The client ID for your GitHub App. | -| `client_secret` | `字符串` | **Required.** The client secret for your GitHub App. | -| `代码` | `字符串` | **必填。**您收到的响应第 1 步的代码。 | -| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 This must be an exact match to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters. | -| `state` | `字符串` | 您在第 1 步提供的不可猜测的随机字符串。 | +| 名称 | 类型 | 描述 | +| --------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `字符串` | **必填。**GitHub 应用程序的客户端 ID。 | +| `client_secret` | `字符串` | **必填。**GitHub 应用程序的客户端密钥。 | +| `代码` | `字符串` | **必填。**您收到的响应第 1 步的代码。 | +| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 它必须完全匹配设置 GitHub 应用程序时 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 作为 **Callback URL（回调 URL）**提供的 URL 之一 {% else %} 在 **User authorization callback URL（用户授权回调 URL）**字段中提供的 URL{% endif %}，并且不能包含任何其他参数。 | +| `state` | `字符串` | 您在第 1 步提供的不可猜测的随机字符串。 | ##### 响应 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`, and `refresh_token_expires_in` are only returned when you enable the beta for expiring user-to-server access tokens. +默认情况下，响应采用以下形式。 响应参数 `expires_in`、`refresh_token` 和 `refresh_token_expires_in` 仅当您启用过期用户到服务器访问令牌测试版功能时才会返回。 ``` { @@ -107,9 +107,9 @@ By default, the response takes the following form. The response parameters `expi {% endif %} -#### 3. Your GitHub App accesses the API with the user's access token +#### 3. 您的 GitHub 应用程序使用用户的访问令牌访问 API -The user's access token allows the GitHub App to make requests to the API on behalf of a user. +用户的访问令牌允许 GitHub 应用程序代表用户向 API 发出请求。 Authorization: token OAUTH-TOKEN GET {% data variables.product.api_url_code %}/user @@ -121,813 +121,813 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre ``` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -### Device flow +### 设备流程 {% if currentVersion ver_lt "enterprise-server@3.1" %} {% note %} -**Note:** The device flow is in public beta and subject to change. +**注：**设备流程处于公开测试阶段，可能会有变化。 {% endnote %} {% endif %} -The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. +设备流程允许您授权用户使用无头应用程序，例如 CLI 工具或 Git 凭据管理器。 -For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)". +有关使用设备流程授权用户的更多信息，请参阅“[授权 OAuth 应用程序](/developers/apps/authorizing-oauth-apps#device-flow)”。 {% endif %} -### Check which installation's resources a user can access +### 检查用户可以访问哪些安装资源 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% data reusables.pre-release-program.machine-man-preview %} {% data reusables.pre-release-program.api-preview-warning %} {% endif %} -Once you have an OAuth token for a user, you can check which installations that user can access. +获得用户的 OAuth 令牌后，您可以检查该用户可以访问哪些安装。 Authorization: token OAUTH-TOKEN GET /user/installations -You can also check which repositories are accessible to a user for an installation. +您还可以检查用户可以访问哪些仓库进行安装。 Authorization: token OAUTH-TOKEN GET /user/installations/:installation_id/repositories -More details can be found in: [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token). +更多信息请参阅：[列出用户访问令牌可访问的应用程序安装](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)和[列出用户访问令牌可访问的仓库](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)。 -### Handling a revoked GitHub App authorization +### 处理已撤销的 GitHub 应用程序授权 -If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %} +默认情况下，如果用户撤销对 GitHub 应用程序的授权，该应用程序将收到 [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) web 挂钩。 GitHub 应用程序无法取消订阅此事件。 {% data reusables.webhooks.authorization_event %} -### User-level permissions +### 用户级别的权限 -You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/v3/apps/permissions/), which are granted at the time of installation on an organization or user account. +您可以向 GitHub 应用程序添加用户级别的权限，以访问用户电子邮件等用户资源，这些权限是单个用户在[用户授权流程](#identifying-users-on-your-site)中授予的。 用户级别的权限不同于[仓库和组织级别的权限](/rest/reference/permissions-required-for-github-apps)，后者是在组织或用户帐户上安装时授予的。 -You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." +您可以在 **Permissions & webhooks（权限和 web 挂钩）**页面 **User permissions（用户权限）**部分的 GitHub 应用程序设置中选择用户级别的权限。 有关选择权限的更多信息，请参阅“[编辑 GitHub 应用程序的权限](/apps/managing-github-apps/editing-a-github-app-s-permissions/)”。 -When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions. +当用户在他们的帐户上安装您的应用程序时，安装提示将列出应用程序请求的用户级别权限，并说明应用程序会向各个用户请求这些权限。 -Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests. +由于用户级别的权限是基于单个用户授予的，因此您可以将它们添加到现有应用中，而无需提示用户升级。 但是，您需要通过用户授权流程发送现有用户，以授权新权限并为这些请求获取新的用户到服务器令牌。 -### User-to-server requests +### 用户到服务器请求 -While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/v4/) or [REST v3](/v3/) endpoints. +虽然大多数 API 交互应使用服务器到服务器安装访问令牌进行，但某些端点允许您使用用户访问令牌通过 API 执行操作。 您的应用程序可以使用[GraphQL v4](/graphql) 或 [REST v3](/rest) 端点发出以下请求。 -#### Supported endpoints +#### 支持的端点 {% if currentVersion == "free-pro-team@latest" %} -##### Actions Runners +##### 操作运行器 -* [List runner applications for a repository](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) -* [List self-hosted runners for a repository](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) -* [Get a self-hosted runner for a repository](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) -* [Delete a self-hosted runner from a repository](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) -* [Create a registration token for a repository](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) -* [Create a remove token for a repository](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) -* [List runner applications for an organization](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) -* [List self-hosted runners for an organization](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) -* [Get a self-hosted runner for an organization](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) -* [Delete a self-hosted runner from an organization](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) -* [Create a registration token for an organization](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) -* [Create a remove token for an organization](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) +* [列出仓库的运行器应用程序](/rest/reference/actions#list-runner-applications-for-a-repository) +* [列出仓库的自托管运行器](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [获取仓库的自托管运行器](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [从仓库删除自托管运行器](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [为仓库创建注册令牌](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [为仓库创建删除令牌](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [列出组织的运行器应用程序](/rest/reference/actions#list-runner-applications-for-an-organization) +* [列出组织的自托管运行器](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [获取组织的自托管运行器](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [从组织删除自托管运行器](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [为组织创建注册令牌](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [为组织创建删除令牌](/rest/reference/actions#create-a-remove-token-for-an-organization) -##### Actions Secrets +##### 操作密钥 -* [Get a repository public key](/v3/actions/secrets/#get-a-repository-public-key) -* [List repository secrets](/v3/actions/secrets/#list-repository-secrets) -* [Get a repository secret](/v3/actions/secrets/#get-a-repository-secret) -* [Create or update a repository secret](/v3/actions/secrets/#create-or-update-a-repository-secret) -* [Delete a repository secret](/v3/actions/secrets/#delete-a-repository-secret) -* [Get an organization public key](/v3/actions/secrets/#get-an-organization-public-key) -* [List organization secrets](/v3/actions/secrets/#list-organization-secrets) -* [Get an organization secret](/v3/actions/secrets/#get-an-organization-secret) -* [Create or update an organization secret](/v3/actions/secrets/#create-or-update-an-organization-secret) -* [List selected repositories for an organization secret](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) -* [Set selected repositories for an organization secret](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) -* [Add selected repository to an organization secret](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) -* [Remove selected repository from an organization secret](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) -* [Delete an organization secret](/v3/actions/secrets/#delete-an-organization-secret) +* [获取仓库公钥](/rest/reference/actions#get-a-repository-public-key) +* [列出仓库密钥](/rest/reference/actions#list-repository-secrets) +* [获取仓库密钥](/rest/reference/actions#get-a-repository-secret) +* [创建或更新仓库密钥](/rest/reference/actions#create-or-update-a-repository-secret) +* [删除仓库密钥](/rest/reference/actions#delete-a-repository-secret) +* [获取组织公钥](/rest/reference/actions#get-an-organization-public-key) +* [列出组织密钥](/rest/reference/actions#list-organization-secrets) +* [获取组织密钥](/rest/reference/actions#get-an-organization-secret) +* [创建或更新组织密钥](/rest/reference/actions#create-or-update-an-organization-secret) +* [列出组织密钥的所选仓库](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [设置组织密钥的所选仓库](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [向组织密钥添加所选仓库](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [从组织密钥删除所选仓库](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [删除组织密钥](/rest/reference/actions#delete-an-organization-secret) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### 构件 -* [List artifacts for a repository](/v3/actions/artifacts/#list-artifacts-for-a-repository) -* [List workflow run artifacts](/v3/actions/artifacts/#list-workflow-run-artifacts) -* [Get an artifact](/v3/actions/artifacts/#get-an-artifact) -* [Delete an artifact](/v3/actions/artifacts/#delete-an-artifact) -* [Download an artifact](/v3/actions/artifacts/#download-an-artifact) +* [列出仓库的构件](/rest/reference/actions#list-artifacts-for-a-repository) +* [列出工作流程运行构件](/rest/reference/actions#list-workflow-run-artifacts) +* [获取构件](/rest/reference/actions#get-an-artifact) +* [删除构件](/rest/reference/actions#delete-an-artifact) +* [下载构件](/rest/reference/actions#download-an-artifact) {% endif %} ##### 检查运行 -* [Create a check run](/v3/checks/runs/#create-a-check-run) -* [Get a check run](/v3/checks/runs/#get-a-check-run) -* [Update a check run](/v3/checks/runs/#update-a-check-run) -* [List check run annotations](/v3/checks/runs/#list-check-run-annotations) -* [List check runs in a check suite](/v3/checks/runs/#list-check-runs-in-a-check-suite) -* [List check runs for a Git reference](/v3/checks/runs/#list-check-runs-for-a-git-reference) +* [创建检查运行](/rest/reference/checks#create-a-check-run) +* [获取检查运行](/rest/reference/checks#get-a-check-run) +* [更新检查运行](/rest/reference/checks#update-a-check-run) +* [列出检查运行注释](/rest/reference/checks#list-check-run-annotations) +* [列出检查套件中的检查运行](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [列出 Git 引用的检查运行](/rest/reference/checks#list-check-runs-for-a-git-reference) ##### 检查套件 -* [Create a check suite](/v3/checks/suites/#create-a-check-suite) -* [Get a check suite](/v3/checks/suites/#get-a-check-suite) -* [Rerequest a check suite](/v3/checks/suites/#rerequest-a-check-suite) -* [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) -* [List check suites for a Git reference](/v3/checks/suites/#list-check-suites-for-a-git-reference) +* [创建检查套件](/rest/reference/checks#create-a-check-suite) +* [获取检查套件](/rest/reference/checks#get-a-check-suite) +* [重新请求检查套件](/rest/reference/checks#rerequest-a-check-suite) +* [更新检查套件的仓库首选项](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [列出 Git 引用的检查套件](/rest/reference/checks#list-check-suites-for-a-git-reference) -##### Codes Of Conduct +##### 行为准则 -* [Get all codes of conduct](/v3/codes_of_conduct/#get-all-codes-of-conduct) -* [Get a code of conduct](/v3/codes_of_conduct/#get-a-code-of-conduct) +* [获取所有行为准则](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [获取行为准则](/rest/reference/codes-of-conduct#get-a-code-of-conduct) -##### Deployment Statuses +##### 部署状态 -* [List deployment statuses](/rest/reference/repos#list-deployment-statuses) -* [Create a deployment status](/rest/reference/repos#create-a-deployment-status) -* [Get a deployment status](/rest/reference/repos#get-a-deployment-status) +* [列出部署状态](/rest/reference/repos#list-deployment-statuses) +* [创建部署状态](/rest/reference/repos#create-a-deployment-status) +* [获取部署状态](/rest/reference/repos#get-a-deployment-status) ##### 部署 -* [List deployments](/rest/reference/repos#list-deployments) -* [Create a deployment](/rest/reference/repos#create-a-deployment) -* [Get a deployment](/rest/reference/repos#get-a-deployment){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a deployment](/rest/reference/repos#delete-a-deployment){% endif %} +* [列出部署](/rest/reference/repos#list-deployments) +* [创建部署](/rest/reference/repos#create-a-deployment) +* [获取部署](/rest/reference/repos#get-a-deployment){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [删除部署](/rest/reference/repos#delete-a-deployment){% endif %} ##### 事件 -* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories) -* [List public organization events](/rest/reference/activity#list-public-organization-events) +* [列出仓库网络的公开事件](/rest/reference/activity#list-public-events-for-a-network-of-repositories) +* [列出公开组织事件](/rest/reference/activity#list-public-organization-events) ##### 馈送 -* [Get feeds](/rest/reference/activity#get-feeds) +* [获取馈送](/rest/reference/activity#get-feeds) -##### Git Blobs +##### Git Blob -* [Create a blob](/v3/git/blobs/#create-a-blob) -* [Get a blob](/v3/git/blobs/#get-a-blob) +* [创建 Blob](/rest/reference/git#create-a-blob) +* [获取 Blob](/rest/reference/git#get-a-blob) -##### Git Commits +##### Git 提交 -* [Create a commit](/v3/git/commits/#create-a-commit) -* [Get a commit](/v3/git/commits/#get-a-commit) +* [创建提交](/rest/reference/git#create-a-commit) +* [获取提交](/rest/reference/git#get-a-commit) -##### Git Refs +##### Git 引用 -* [Create a reference](/v3/git/refs/#create-a-reference)* [Get a reference](/v3/git/refs/#get-a-reference) -* [List matching references](/v3/git/refs/#list-matching-references) -* [Update a reference](/v3/git/refs/#update-a-reference) -* [Delete a reference](/v3/git/refs/#delete-a-reference) +* [创建引用](/rest/reference/git#create-a-reference)* [获取引用](/rest/reference/git#get-a-reference) +* [列出匹配的引用](/rest/reference/git#list-matching-references) +* [更新引用](/rest/reference/git#update-a-reference) +* [删除引用](/rest/reference/git#delete-a-reference) -##### Git Tags +##### Git 标记 -* [Create a tag object](/v3/git/tags/#create-a-tag-object) -* [Get a tag](/v3/git/tags/#get-a-tag) +* [创建标记对象](/rest/reference/git#create-a-tag-object) +* [获取标记](/rest/reference/git#get-a-tag) -##### Git Trees +##### Git 树 -* [Create a tree](/v3/git/trees/#create-a-tree) -* [Get a tree](/v3/git/trees/#get-a-tree) +* [创建树](/rest/reference/git#create-a-tree) +* [获取树](/rest/reference/git#get-a-tree) -##### Gitignore Templates +##### Gitignore 模板 -* [Get all gitignore templates](/v3/gitignore/#get-all-gitignore-templates) -* [Get a gitignore template](/v3/gitignore/#get-a-gitignore-template) +* [获取所有 gitignore 模板](/rest/reference/gitignore#get-all-gitignore-templates) +* [获取 gitignore 模板](/rest/reference/gitignore#get-a-gitignore-template) ##### 安装设施 -* [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token) +* [列出用户访问令牌可访问的仓库](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -##### Interaction Limits +##### 交互限制 -* [Get interaction restrictions for an organization](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) -* [Set interaction restrictions for an organization](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) -* [Remove interaction restrictions for an organization](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) -* [Get interaction restrictions for a repository](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) -* [Set interaction restrictions for a repository](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) -* [Remove interaction restrictions for a repository](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) +* [获取组织的交互限制](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [设置组织的交互限制](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [删除组织的交互限制](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [获取仓库的交互限制](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [设置仓库的交互限制](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [删除仓库的交互限制](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) {% endif %} -##### Issue Assignees +##### 议题受理人 -* [Add assignees to an issue](/v3/issues/assignees/#add-assignees-to-an-issue) -* [Remove assignees from an issue](/v3/issues/assignees/#remove-assignees-from-an-issue) +* [向议题添加受理人](/rest/reference/issues#add-assignees-to-an-issue) +* [从议题删除受理人](/rest/reference/issues#remove-assignees-from-an-issue) -##### Issue Comments +##### 议题评论 -* [List issue comments](/v3/issues/comments/#list-issue-comments) -* [Create an issue comment](/v3/issues/comments/#create-an-issue-comment) -* [List issue comments for a repository](/v3/issues/comments/#list-issue-comments-for-a-repository) -* [Get an issue comment](/v3/issues/comments/#get-an-issue-comment) -* [Update an issue comment](/v3/issues/comments/#update-an-issue-comment) -* [Delete an issue comment](/v3/issues/comments/#delete-an-issue-comment) +* [列出议题评论](/rest/reference/issues#list-issue-comments) +* [创建议题评论](/rest/reference/issues#create-an-issue-comment) +* [列出仓库的议题评论](/rest/reference/issues#list-issue-comments-for-a-repository) +* [获取议题评论](/rest/reference/issues#get-an-issue-comment) +* [更新议题评论](/rest/reference/issues#update-an-issue-comment) +* [删除议题评论](/rest/reference/issues#delete-an-issue-comment) -##### Issue Events +##### 议题事件 -* [List issue events](/v3/issues/events/#list-issue-events) +* [列出议题事件](/rest/reference/issues#list-issue-events) -##### Issue Timeline +##### 议题时间表 -* [List timeline events for an issue](/v3/issues/timeline/#list-timeline-events-for-an-issue) +* [列出议题的时间表事件](/rest/reference/issues#list-timeline-events-for-an-issue) ##### 议题 -* [List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user) -* [List assignees](/v3/issues/assignees/#list-assignees) -* [Check if a user can be assigned](/v3/issues/assignees/#check-if-a-user-can-be-assigned) -* [List repository issues](/v3/issues/#list-repository-issues) -* [创建议题](/v3/issues/#create-an-issue) -* [Get an issue](/v3/issues/#get-an-issue) -* [Update an issue](/v3/issues/#update-an-issue) -* [Lock an issue](/v3/issues/#lock-an-issue) -* [Unlock an issue](/v3/issues/#unlock-an-issue) +* [列出分配给经验证用户的议题](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [列出受理人](/rest/reference/issues#list-assignees) +* [检查是否可以分配给用户](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [列出仓库议题](/rest/reference/issues#list-repository-issues) +* [创建议题](/rest/reference/issues#create-an-issue) +* [获取议题](/rest/reference/issues#get-an-issue) +* [更新议题](/rest/reference/issues#update-an-issue) +* [锁定议题](/rest/reference/issues#lock-an-issue) +* [解锁议题](/rest/reference/issues#unlock-an-issue) {% if currentVersion == "free-pro-team@latest" %} ##### Jobs -* [Get a job for a workflow run](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) -* [Download job logs for a workflow run](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) -* [List jobs for a workflow run](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) +* [获取工作流程运行的作业](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [下载工作流程运行的作业日志](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [列出工作流程运行的作业](/rest/reference/actions#list-jobs-for-a-workflow-run) {% endif %} ##### 标签 -* [List labels for an issue](/v3/issues/labels/#list-labels-for-an-issue) -* [Add labels to an issue](/v3/issues/labels/#add-labels-to-an-issue) -* [Set labels for an issue](/v3/issues/labels/#set-labels-for-an-issue) -* [Remove all labels from an issue](/v3/issues/labels/#remove-all-labels-from-an-issue) -* [Remove a label from an issue](/v3/issues/labels/#remove-a-label-from-an-issue) -* [List labels for a repository](/v3/issues/labels/#list-labels-for-a-repository) -* [Create a label](/v3/issues/labels/#create-a-label) -* [Get a label](/v3/issues/labels/#get-a-label) -* [Update a label](/v3/issues/labels/#update-a-label) -* [Delete a label](/v3/issues/labels/#delete-a-label) -* [Get labels for every issue in a milestone](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) +* [列出议题的标签](/rest/reference/issues#list-labels-for-an-issue) +* [向议题添加标签](/rest/reference/issues#add-labels-to-an-issue) +* [为议题设置标签](/rest/reference/issues#set-labels-for-an-issue) +* [删除议题的所有标签](/rest/reference/issues#remove-all-labels-from-an-issue) +* [删除议题的一个标签](/rest/reference/issues#remove-a-label-from-an-issue) +* [列出仓库的标签](/rest/reference/issues#list-labels-for-a-repository) +* [创建标签](/rest/reference/issues#create-a-label) +* [获取标签](/rest/reference/issues#get-a-label) +* [更新标签](/rest/reference/issues#update-a-label) +* [删除标签](/rest/reference/issues#delete-a-label) +* [获取里程碑中每个议题的标签](/rest/reference/issues#list-labels-for-issues-in-a-milestone) ##### 许可 -* [Get all commonly used licenses](/v3/licenses/#get-all-commonly-used-licenses) -* [Get a license](/v3/licenses/#get-a-license) +* [获取所有常用许可](/rest/reference/licenses#get-all-commonly-used-licenses) +* [获取许可](/rest/reference/licenses#get-a-license) ##### Markdown -* [Render a Markdown document](/v3/markdown/#render-a-markdown-document) -* [Render a markdown document in raw mode](/v3/markdown/#render-a-markdown-document-in-raw-mode) +* [渲染 Markdown 文档](/rest/reference/markdown#render-a-markdown-document) +* [在原始模式下渲染 Markdown 文档](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) ##### 元数据 -* [元数据](/v3/meta/#meta) +* [元数据](/rest/reference/meta#meta) ##### 里程碑 -* [List milestones](/v3/issues/milestones/#list-milestones) -* [Create a milestone](/v3/issues/milestones/#create-a-milestone) -* [Get a milestone](/v3/issues/milestones/#get-a-milestone) -* [Update a milestone](/v3/issues/milestones/#update-a-milestone) -* [Delete a milestone](/v3/issues/milestones/#delete-a-milestone) +* [列出里程碑](/rest/reference/issues#list-milestones) +* [创建里程碑](/rest/reference/issues#create-a-milestone) +* [获取里程碑](/rest/reference/issues#get-a-milestone) +* [更新里程碑](/rest/reference/issues#update-a-milestone) +* [删除里程碑](/rest/reference/issues#delete-a-milestone) -##### Organization Hooks +##### 组织挂钩 -* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks) -* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook) -* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook) -* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook) -* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) -* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) +* [列出组织 web 挂钩](/rest/reference/orgs#webhooks/#list-organization-webhooks) +* [创建组织 web 挂钩](/rest/reference/orgs#webhooks/#create-an-organization-webhook) +* [获取组织 web 挂钩](/rest/reference/orgs#webhooks/#get-an-organization-webhook) +* [更新组织 web 挂钩](/rest/reference/orgs#webhooks/#update-an-organization-webhook) +* [删除组织 web 挂钩](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) +* [Ping 组织 web 挂钩](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) {% if currentVersion == "free-pro-team@latest" %} -##### Organization Invitations +##### 组织邀请 -* [List pending organization invitations](/v3/orgs/members/#list-pending-organization-invitations) -* [Create an organization invitation](/v3/orgs/members/#create-an-organization-invitation) -* [List organization invitation teams](/v3/orgs/members/#list-organization-invitation-teams) +* [列出待处理的组织邀请](/rest/reference/orgs#list-pending-organization-invitations) +* [创建组织邀请](/rest/reference/orgs#create-an-organization-invitation) +* [列出组织邀请团队](/rest/reference/orgs#list-organization-invitation-teams) {% endif %} -##### Organization Members +##### 组织成员 -* [List organization members](/v3/orgs/members/#list-organization-members) -* [Check organization membership for a user](/v3/orgs/members/#check-organization-membership-for-a-user) -* [Remove an organization member](/v3/orgs/members/#remove-an-organization-member) -* [Get organization membership for a user](/v3/orgs/members/#get-organization-membership-for-a-user) -* [Set organization membership for a user](/v3/orgs/members/#set-organization-membership-for-a-user) -* [Remove organization membership for a user](/v3/orgs/members/#remove-organization-membership-for-a-user) -* [List public organization members](/v3/orgs/members/#list-public-organization-members) -* [Check public organization membership for a user](/v3/orgs/members/#check-public-organization-membership-for-a-user) -* [Set public organization membership for the authenticated user](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) -* [Remove public organization membership for the authenticated user](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) +* [列出组织成员](/rest/reference/orgs#list-organization-members) +* [检查用户的组织成员身份](/rest/reference/orgs#check-organization-membership-for-a-user) +* [删除组织成员](/rest/reference/orgs#remove-an-organization-member) +* [获取用户的组织成员身份](/rest/reference/orgs#get-organization-membership-for-a-user) +* [设置用户的组织成员身份](/rest/reference/orgs#set-organization-membership-for-a-user) +* [删除用户的组织成员身份](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [列出公共组织成员](/rest/reference/orgs#list-public-organization-members) +* [检查用户的公共组织成员身份](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [设置经验证用户的公共组织成员身份](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [删除经验证用户的公共组织成员身份](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) -##### Organization Outside Collaborators +##### 组织外部协作者 -* [List outside collaborators for an organization](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) -* [Convert an organization member to outside collaborator](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) -* [Remove outside collaborator from an organization](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) +* [列出组织的外部协作者](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [将组织成员转换为外部协作者](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [删除组织的外部协作者](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) {% if enterpriseServerVersions contains currentVersion %} -##### Organization Pre Receive Hooks +##### 组织预接收挂钩 -* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) -* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) -* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) -* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) +* [列出组织的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) +* [获取组织的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) +* [更新组织的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) +* [删除组织的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -##### Organization Team Projects +##### 组织团队项目 -* [List team projects](/v3/teams/#list-team-projects) -* [Check team permissions for a project](/v3/teams/#check-team-permissions-for-a-project) -* [Add or update team project permissions](/v3/teams/#add-or-update-team-project-permissions) -* [Remove a project from a team](/v3/teams/#remove-a-project-from-a-team) +* [列出团队项目](/rest/reference/teams#list-team-projects) +* [检查项目的团队权限](/rest/reference/teams#check-team-permissions-for-a-project) +* [添加或更新团队项目权限](/rest/reference/teams#add-or-update-team-project-permissions) +* [从团队删除项目](/rest/reference/teams#remove-a-project-from-a-team) {% endif %} -##### Organization Team Repositories +##### 组织团队仓库 -* [列出团队仓库](/v3/teams/#list-team-repositories) -* [Check team permissions for a repository](/v3/teams/#check-team-permissions-for-a-repository) -* [Add or update team repository permissions](/v3/teams/#add-or-update-team-repository-permissions) -* [Remove a repository from a team](/v3/teams/#remove-a-repository-from-a-team) +* [列出团队仓库](/rest/reference/teams#list-team-repositories) +* [检查仓库的团队权限](/rest/reference/teams#check-team-permissions-for-a-repository) +* [添加或更新团队仓库权限](/rest/reference/teams#add-or-update-team-repository-permissions) +* [从团队删除仓库](/rest/reference/teams#remove-a-repository-from-a-team) {% if currentVersion == "free-pro-team@latest" %} -##### Organization Team Sync +##### 组织团队同步 -* [List idp groups for a team](/v3/teams/team_sync/#list-idp-groups-for-a-team) -* [Create or update idp group connections](/v3/teams/team_sync/#create-or-update-idp-group-connections) -* [List IdP groups for an organization](/v3/teams/team_sync/#list-idp-groups-for-an-organization) +* [列出团队的 idp 组](/rest/reference/teams#list-idp-groups-for-a-team) +* [创建或更新 idp 组连接](/rest/reference/teams#create-or-update-idp-group-connections) +* [列出组织的 IdP 组](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} -##### Organization Teams +##### 组织团队 -* [List teams](/v3/teams/#list-teams) -* [Create a team](/v3/teams/#create-a-team) -* [Get a team by name](/v3/teams/#get-a-team-by-name) +* [列出团队](/rest/reference/teams#list-teams) +* [创建团队](/rest/reference/teams#create-a-team) +* [按名称获取团队](/rest/reference/teams#get-a-team-by-name) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -* [Get a team](/v3/teams/#get-a-team) +* [获取团队](/rest/reference/teams#get-a-team) {% endif %} -* [Update a team](/v3/teams/#update-a-team) -* [Delete a team](/v3/teams/#delete-a-team) +* [更新团队](/rest/reference/teams#update-a-team) +* [删除团队](/rest/reference/teams#delete-a-team) {% if currentVersion == "free-pro-team@latest" %} -* [List pending team invitations](/v3/teams/members/#list-pending-team-invitations) +* [列出待处理的团队邀请](/rest/reference/teams#list-pending-team-invitations) {% endif %} -* [List team members](/v3/teams/members/#list-team-members) -* [Get team membership for a user](/v3/teams/members/#get-team-membership-for-a-user) -* [Add or update team membership for a user](/v3/teams/members/#add-or-update-team-membership-for-a-user) -* [Remove team membership for a user](/v3/teams/members/#remove-team-membership-for-a-user) -* [List child teams](/v3/teams/#list-child-teams) -* [List teams for the authenticated user](/v3/teams/#list-teams-for-the-authenticated-user) +* [列出团队成员](/rest/reference/teams#list-team-members) +* [获取用户的团队成员身份](/rest/reference/teams#get-team-membership-for-a-user) +* [添加或更新用户的团队成员身份](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [删除用户的团队成员身份](/rest/reference/teams#remove-team-membership-for-a-user) +* [列出子团队](/rest/reference/teams#list-child-teams) +* [列出经验证用户的团队](/rest/reference/teams#list-teams-for-the-authenticated-user) ##### 组织 -* [List organizations](/v3/orgs/#list-organizations) -* [Get an organization](/v3/orgs/#get-an-organization) -* [Update an organization](/v3/orgs/#update-an-organization) -* [List organization memberships for the authenticated user](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) -* [Get an organization membership for the authenticated user](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) -* [Update an organization membership for the authenticated user](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) -* [List organizations for the authenticated user](/v3/orgs/#list-organizations-for-the-authenticated-user) -* [List organizations for a user](/v3/orgs/#list-organizations-for-a-user) +* [列出组织](/rest/reference/orgs#list-organizations) +* [获取组织](/rest/reference/orgs#get-an-organization) +* [更新组织](/rest/reference/orgs#update-an-organization) +* [列出经验证用户的组织成员身份](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [获取经验证用户的组织成员身份](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [更新经验证用户的组织成员身份](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [列出经验证用户的组织](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [列出用户的组织](/rest/reference/orgs#list-organizations-for-a-user) {% if currentVersion == "free-pro-team@latest" %} -##### Organizations Credential Authorizations +##### 组织凭据授权 -* [List SAML SSO authorizations for an organization](/v3/orgs/#list-saml-sso-authorizations-for-an-organization) -* [Remove a SAML SSO authorization for an organization](/v3/orgs/#remove-a-saml-sso-authorization-for-an-organization) +* [列出组织的 SAML SSO 授权](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [删除组织的 SAML SSO 授权](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### Organizations Scim +##### 组织 SCIM -* [List SCIM provisioned identities](/v3/scim/#list-scim-provisioned-identities) -* [Provision and invite a SCIM user](/v3/scim/#provision-and-invite-a-scim-user) -* [Get SCIM provisioning information for a user](/v3/scim/#get-scim-provisioning-information-for-a-user) -* [Set SCIM information for a provisioned user](/v3/scim/#set-scim-information-for-a-provisioned-user) -* [Update an attribute for a SCIM user](/v3/scim/#update-an-attribute-for-a-scim-user) -* [Delete a SCIM user from an organization](/v3/scim/#delete-a-scim-user-from-an-organization) +* [列出 SCIM 预配标识](/rest/reference/scim#list-scim-provisioned-identities) +* [预配并邀请 SCIM 用户](/rest/reference/scim#provision-and-invite-a-scim-user) +* [获取用户的 SCIM 预配信息](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [为预配用户设置 SCIM 信息](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [更新 SCIM 用户的属性](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [从组织中删除 SCIM 用户](/rest/reference/scim#delete-a-scim-user-from-an-organization) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### Source Imports +##### 源导入 -* [Get an import status](/v3/migrations/source_imports/#get-an-import-status) -* [Start an import](/v3/migrations/source_imports/#start-an-import) -* [Update an import](/v3/migrations/source_imports/#update-an-import) -* [Cancel an import](/v3/migrations/source_imports/#cancel-an-import) -* [Get commit authors](/v3/migrations/source_imports/#get-commit-authors) -* [Map a commit author](/v3/migrations/source_imports/#map-a-commit-author) -* [Get large files](/v3/migrations/source_imports/#get-large-files) -* [Update Git LFS preference](/v3/migrations/source_imports/#update-git-lfs-preference) +* [获取导入状态](/rest/reference/migrations#get-an-import-status) +* [开始导入](/rest/reference/migrations#start-an-import) +* [更新导入](/rest/reference/migrations#update-an-import) +* [取消导入](/rest/reference/migrations#cancel-an-import) +* [获取提交作者](/rest/reference/migrations#get-commit-authors) +* [映射提交作者](/rest/reference/migrations#map-a-commit-author) +* [获取大文件](/rest/reference/migrations#get-large-files) +* [更新 Git LFS 首选项](/rest/reference/migrations#update-git-lfs-preference) {% endif %} -##### Project Collaborators +##### 项目协作者 -* [List project collaborators](/v3/projects/collaborators/#list-project-collaborators) -* [Add project collaborator](/v3/projects/collaborators/#add-project-collaborator) -* [Remove project collaborator](/v3/projects/collaborators/#remove-project-collaborator) -* [Get project permission for a user](/v3/projects/collaborators/#get-project-permission-for-a-user) +* [列出项目协作者](/rest/reference/projects#list-project-collaborators) +* [添加项目协作者](/rest/reference/projects#add-project-collaborator) +* [删除项目协作者](/rest/reference/projects#remove-project-collaborator) +* [获取用户的项目权限](/rest/reference/projects#get-project-permission-for-a-user) ##### 项目 -* [List organization projects](/v3/projects/#list-organization-projects) -* [Create an organization project](/v3/projects/#create-an-organization-project) -* [Get a project](/v3/projects/#get-a-project) -* [Update a project](/v3/projects/#update-a-project) -* [Delete a project](/v3/projects/#delete-a-project) -* [List project columns](/v3/projects/columns/#list-project-columns) -* [Create a project column](/v3/projects/columns/#create-a-project-column) -* [Get a project column](/v3/projects/columns/#get-a-project-column) -* [Update a project column](/v3/projects/columns/#update-a-project-column) -* [Delete a project column](/v3/projects/columns/#delete-a-project-column) -* [List project cards](/v3/projects/cards/#list-project-cards) -* [Create a project card](/v3/projects/cards/#create-a-project-card) -* [Move a project column](/v3/projects/columns/#move-a-project-column) -* [Get a project card](/v3/projects/cards/#get-a-project-card) -* [Update a project card](/v3/projects/cards/#update-a-project-card) -* [Delete a project card](/v3/projects/cards/#delete-a-project-card) -* [Move a project card](/v3/projects/cards/#move-a-project-card) -* [List repository projects](/v3/projects/#list-repository-projects) -* [Create a repository project](/v3/projects/#create-a-repository-project) +* [列出组织项目](/rest/reference/projects#list-organization-projects) +* [创建组织项目](/rest/reference/projects#create-an-organization-project) +* [获取项目](/rest/reference/projects#get-a-project) +* [更新项目](/rest/reference/projects#update-a-project) +* [删除项目](/rest/reference/projects#delete-a-project) +* [列出项目列](/rest/reference/projects#list-project-columns) +* [创建项目列](/rest/reference/projects#create-a-project-column) +* [获取项目列](/rest/reference/projects#get-a-project-column) +* [更新项目列](/rest/reference/projects#update-a-project-column) +* [删除项目列](/rest/reference/projects#delete-a-project-column) +* [列出项目卡](/rest/reference/projects#list-project-cards) +* [创建项目卡](/rest/reference/projects#create-a-project-card) +* [移动项目列](/rest/reference/projects#move-a-project-column) +* [获取项目卡](/rest/reference/projects#get-a-project-card) +* [更新项目卡](/rest/reference/projects#update-a-project-card) +* [删除项目卡](/rest/reference/projects#delete-a-project-card) +* [移动项目卡](/rest/reference/projects#move-a-project-card) +* [列出仓库项目](/rest/reference/projects#list-repository-projects) +* [创建仓库项目](/rest/reference/projects#create-a-repository-project) -##### Pull Comments +##### 拉取注释 -* [List review comments on a pull request](/v3/pulls/comments/#list-review-comments-on-a-pull-request) -* [Create a review comment for a pull request](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) -* [List review comments in a repository](/v3/pulls/comments/#list-review-comments-in-a-repository) -* [Get a review comment for a pull request](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) -* [Update a review comment for a pull request](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) -* [Delete a review comment for a pull request](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) +* [列出拉取请求的审查注释](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [为拉取请求创建审查注释](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [列出仓库中的审查注释](/rest/reference/pulls#list-review-comments-in-a-repository) +* [获取拉取请求的审查注释](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [更新拉取请求的审查注释](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [删除拉取请求的审查注释](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) -##### Pull Request Review Events +##### 拉取请求审查事件 -* [Dismiss a review for a pull request](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) -* [Submit a review for a pull request](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) +* [忽略拉取请求审查](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [提交拉取请求审查](/rest/reference/pulls#submit-a-review-for-a-pull-request) -##### Pull Request Review Requests +##### 拉取请求审查请求 -* [List requested reviewers for a pull request](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) -* [Request reviewers for a pull request](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) -* [Remove requested reviewers from a pull request](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) +* [列出拉取请求的请求审查者](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [请求拉取请求的审查者](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [删除拉取请求的请求审查者](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) -##### Pull Request Reviews +##### 拉取请求审查 -* [List reviews for a pull request](/v3/pulls/reviews/#list-reviews-for-a-pull-request) -* [Create a review for a pull request](/v3/pulls/reviews/#create-a-review-for-a-pull-request) -* [Get a review for a pull request](/v3/pulls/reviews/#get-a-review-for-a-pull-request) -* [Update a review for a pull request](/v3/pulls/reviews/#update-a-review-for-a-pull-request) -* [List comments for a pull request review](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) +* [列出拉取请求审查](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [创建拉取请求审查](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [获取拉取请求审查](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [更新拉取请求审查](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [列出拉取请求审查的注释](/rest/reference/pulls#list-comments-for-a-pull-request-review) ##### 拉取 -* [List pull requests](/v3/pulls/#list-pull-requests) -* [Create a pull request](/v3/pulls/#create-a-pull-request) -* [Get a pull request](/v3/pulls/#get-a-pull-request) -* [Update a pull request](/v3/pulls/#update-a-pull-request) -* [List commits on a pull request](/v3/pulls/#list-commits-on-a-pull-request) -* [List pull requests files](/v3/pulls/#list-pull-requests-files) -* [Check if a pull request has been merged](/v3/pulls/#check-if-a-pull-request-has-been-merged) -* [Merge a pull request (Merge Button)](/v3/pulls/#merge-a-pull-request) +* [列出拉取请求](/rest/reference/pulls#list-pull-requests) +* [创建拉取请求](/rest/reference/pulls#create-a-pull-request) +* [获取拉取请求](/rest/reference/pulls#get-a-pull-request) +* [更新拉取请求](/rest/reference/pulls#update-a-pull-request) +* [列出拉取请求上的提交](/rest/reference/pulls#list-commits-on-a-pull-request) +* [列出拉取请求文件](/rest/reference/pulls#list-pull-requests-files) +* [检查拉取请求是否已合并](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [合并拉取请求（合并按钮）](/rest/reference/pulls#merge-a-pull-request) ##### 反应 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Delete a reaction](/v3/reactions/#delete-a-reaction-legacy){% else %}* [Delete a reaction](/v3/reactions/#delete-a-reaction){% endif %} -* [List reactions for a commit comment](/v3/reactions/#list-reactions-for-a-commit-comment) -* [Create reaction for a commit comment](/v3/reactions/#create-reaction-for-a-commit-comment) -* [List reactions for an issue](/v3/reactions/#list-reactions-for-an-issue) -* [Create reaction for an issue](/v3/reactions/#create-reaction-for-an-issue) -* [List reactions for an issue comment](/v3/reactions/#list-reactions-for-an-issue-comment) -* [Create reaction for an issue comment](/v3/reactions/#create-reaction-for-an-issue-comment) -* [List reactions for a pull request review comment](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) -* [Create reaction for a pull request review comment](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) -* [List reactions for a team discussion comment](/v3/reactions/#list-reactions-for-a-team-discussion-comment) -* [Create reaction for a team discussion comment](/v3/reactions/#create-reaction-for-a-team-discussion-comment) -* [List reactions for a team discussion](/v3/reactions/#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/v3/reactions/#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -* [Delete a commit comment reaction](/v3/reactions/#delete-a-commit-comment-reaction) -* [Delete an issue reaction](/v3/reactions/#delete-an-issue-reaction) -* [Delete a reaction to a commit comment](/v3/reactions/#delete-an-issue-comment-reaction) -* [Delete a pull request comment reaction](/v3/reactions/#delete-a-pull-request-comment-reaction) -* [Delete team discussion reaction](/v3/reactions/#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/v3/reactions/#delete-team-discussion-comment-reaction){% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [删除反应](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [删除反应](/rest/reference/reactions#delete-a-reaction){% endif %} +* [列出提交注释的反应](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [创建提交注释的反应](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [列出议题的反应](/rest/reference/reactions#list-reactions-for-an-issue) +* [创建议题的反应](/rest/reference/reactions#create-reaction-for-an-issue) +* [列出议题注释的反应](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [创建议题注释的反应](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [列出拉取请求审查注释的反应](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [创建拉取请求审查注释的反应](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [列出团队讨论注释的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [创建团队讨论注释的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [列出团队讨论的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [创建团队讨论的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [删除提交注释反应](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [删除议题反应](/rest/reference/reactions#delete-an-issue-reaction) +* [删除对提交注释的反应](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [删除拉取请求注释反应](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [删除团队讨论反应](/rest/reference/reactions#delete-team-discussion-reaction) +* [删除团队讨论注释反应](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} ##### 仓库 -* [列出组织仓库](/v3/repos/#list-organization-repositories) -* [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) -* [获取仓库](/v3/repos/#get-a-repository) -* [Update a repository](/v3/repos/#update-a-repository) -* [Delete a repository](/v3/repos/#delete-a-repository) -* [Compare two commits](/v3/repos/commits/#compare-two-commits) -* [List repository contributors](/v3/repos/#list-repository-contributors) +* [列出组织仓库](/rest/reference/repos#list-organization-repositories) +* [为经验证的用户创建仓库。](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [获取仓库](/rest/reference/repos#get-a-repository) +* [更新仓库](/rest/reference/repos#update-a-repository) +* [删除仓库](/rest/reference/repos#delete-a-repository) +* [比较两个提交](/rest/reference/repos#compare-two-commits) +* [列出仓库贡献者](/rest/reference/repos#list-repository-contributors) * [列出复刻](/rest/reference/repos#list-forks) -* [Create a fork](/v3/repos/forks/#create-a-fork) -* [List repository languages](/v3/repos/#list-repository-languages) -* [List repository tags](/v3/repos/#list-repository-tags) -* [List repository teams](/v3/repos/#list-repository-teams) -* [Transfer a repository](/v3/repos/#transfer-a-repository) -* [List public repositories](/v3/repos/#list-public-repositories) -* [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) -* [列出用户的仓库](/v3/repos/#list-repositories-for-a-user) -* [Create repository using a repository template](/v3/repos/#create-repository-using-a-repository-template) +* [创建复刻](/rest/reference/repos#create-a-fork) +* [列出仓库语言](/rest/reference/repos#list-repository-languages) +* [列出仓库标记](/rest/reference/repos#list-repository-tags) +* [列出仓库团队](/rest/reference/repos#list-repository-teams) +* [转让仓库](/rest/reference/repos#transfer-a-repository) +* [列出公共仓库](/rest/reference/repos#list-public-repositories) +* [列出经验证用户的仓库](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [列出用户的仓库](/rest/reference/repos#list-repositories-for-a-user) +* [使用仓库模板创建仓库](/rest/reference/repos#create-repository-using-a-repository-template) -##### Repository Activity +##### 仓库活动 -* [List stargazers](/rest/reference/activity#list-stargazers) -* [List watchers](/rest/reference/activity#list-watchers) -* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user) -* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) -* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user) -* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) +* [列出标星者](/rest/reference/activity#list-stargazers) +* [列出关注者](/rest/reference/activity#list-watchers) +* [列出用户标星的仓库](/rest/reference/activity#list-repositories-starred-by-a-user) +* [检查仓库是否被经验证用户标星](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) +* [标星经验证用户的仓库](/rest/reference/activity#star-a-repository-for-the-authenticated-user) +* [取消标星经验证用户的仓库](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) * [列出用户关注的仓库](/rest/reference/activity#list-repositories-watched-by-a-user) {% if currentVersion == "free-pro-team@latest" %} -##### Repository Automated Security Fixes +##### 仓库自动安全修复 -* [Enable automated security fixes](/v3/repos/#enable-automated-security-fixes) -* [Disable automated security fixes](/v3/repos/#disable-automated-security-fixes) +* [启用自动安全修复](/rest/reference/repos#enable-automated-security-fixes) +* [禁用自动安全修复](/rest/reference/repos#disable-automated-security-fixes) {% endif %} -##### Repository Branches +##### 仓库分支 -* [List branches](/v3/repos/branches/#list-branches) -* [Get a branch](/v3/repos/branches/#get-a-branch) -* [Get branch protection](/v3/repos/branches/#get-branch-protection) -* [Update branch protection](/v3/repos/branches/#update-branch-protection) -* [Delete branch protection](/v3/repos/branches/#delete-branch-protection) -* [Get admin branch protection](/v3/repos/branches/#get-admin-branch-protection) -* [Set admin branch protection](/v3/repos/branches/#set-admin-branch-protection) -* [Delete admin branch protection](/v3/repos/branches/#delete-admin-branch-protection) -* [Get pull request review protection](/v3/repos/branches/#get-pull-request-review-protection) -* [Update pull request review protection](/v3/repos/branches/#update-pull-request-review-protection) -* [Delete pull request review protection](/v3/repos/branches/#delete-pull-request-review-protection) -* [Get commit signature protection](/v3/repos/branches/#get-commit-signature-protection) -* [Create commit signature protection](/v3/repos/branches/#create-commit-signature-protection) -* [Delete commit signature protection](/v3/repos/branches/#delete-commit-signature-protection) -* [Get status checks protection](/v3/repos/branches/#get-status-checks-protection) -* [Update status check protection](/v3/repos/branches/#update-status-check-protection) -* [Remove status check protection](/v3/repos/branches/#remove-status-check-protection) -* [Get all status check contexts](/v3/repos/branches/#get-all-status-check-contexts) -* [Add status check contexts](/v3/repos/branches/#add-status-check-contexts) -* [Set status check contexts](/v3/repos/branches/#set-status-check-contexts) -* [Remove status check contexts](/v3/repos/branches/#remove-status-check-contexts) -* [Get access restrictions](/v3/repos/branches/#get-access-restrictions) -* [Delete access restrictions](/v3/repos/branches/#delete-access-restrictions) -* [List teams with access to the protected branch](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) -* [Add team access restrictions](/v3/repos/branches/#add-team-access-restrictions) -* [Set team access restrictions](/v3/repos/branches/#set-team-access-restrictions) -* [Remove team access restriction](/v3/repos/branches/#remove-team-access-restrictions) -* [List user restrictions of protected branch](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) -* [Add user access restrictions](/v3/repos/branches/#add-user-access-restrictions) -* [Set user access restrictions](/v3/repos/branches/#set-user-access-restrictions) -* [Remove user access restrictions](/v3/repos/branches/#remove-user-access-restrictions) -* [Merge a branch](/v3/repos/merging/#merge-a-branch) +* [列出分支](/rest/reference/repos#list-branches) +* [获取分支](/rest/reference/repos#get-a-branch) +* [获取分支保护](/rest/reference/repos#get-branch-protection) +* [更新分支保护](/rest/reference/repos#update-branch-protection) +* [删除分支保护](/rest/reference/repos#delete-branch-protection) +* [获取管理员分支保护](/rest/reference/repos#get-admin-branch-protection) +* [设置管理员分支保护](/rest/reference/repos#set-admin-branch-protection) +* [删除管理员分支保护](/rest/reference/repos#delete-admin-branch-protection) +* [获取拉取请求审查保护](/rest/reference/repos#get-pull-request-review-protection) +* [更新拉取请求审查保护](/rest/reference/repos#update-pull-request-review-protection) +* [删除拉取请求审查保护](/rest/reference/repos#delete-pull-request-review-protection) +* [获取提交签名保护](/rest/reference/repos#get-commit-signature-protection) +* [创建提交签名保护](/rest/reference/repos#create-commit-signature-protection) +* [删除提交签名保护](/rest/reference/repos#delete-commit-signature-protection) +* [获取状态检查保护](/rest/reference/repos#get-status-checks-protection) +* [更新状态检查保护](/rest/reference/repos#update-status-check-protection) +* [删除状态检查保护](/rest/reference/repos#remove-status-check-protection) +* [获取所有状态检查上下文](/rest/reference/repos#get-all-status-check-contexts) +* [添加状态检查上下文](/rest/reference/repos#add-status-check-contexts) +* [设置状态检查上下文](/rest/reference/repos#set-status-check-contexts) +* [删除状态检查上下文](/rest/reference/repos#remove-status-check-contexts) +* [获取访问限制](/rest/reference/repos#get-access-restrictions) +* [删除访问限制](/rest/reference/repos#delete-access-restrictions) +* [列出有权访问受保护分支的团队](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [添加团队访问限制](/rest/reference/repos#add-team-access-restrictions) +* [设置团队访问限制](/rest/reference/repos#set-team-access-restrictions) +* [删除团队访问限制](/rest/reference/repos#remove-team-access-restrictions) +* [列出受保护分支的用户限制](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [添加用户访问限制](/rest/reference/repos#add-user-access-restrictions) +* [设置用户访问限制](/rest/reference/repos#set-user-access-restrictions) +* [删除用户访问限制](/rest/reference/repos#remove-user-access-restrictions) +* [合并分支](/rest/reference/repos#merge-a-branch) -##### Repository Collaborators +##### 仓库协作者 -* [List repository collaborators](/v3/repos/collaborators/#list-repository-collaborators) -* [Check if a user is a repository collaborator](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) -* [Add a repository collaborator](/v3/repos/collaborators/#add-a-repository-collaborator) -* [Remove a repository collaborator](/v3/repos/collaborators/#remove-a-repository-collaborator) -* [Get repository permissions for a user](/v3/repos/collaborators/#get-repository-permissions-for-a-user) +* [列出仓库协作者](/rest/reference/repos#list-repository-collaborators) +* [检查用户是否为仓库协作者](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [添加仓库协作者](/rest/reference/repos#add-a-repository-collaborator) +* [删除仓库协作者](/rest/reference/repos#remove-a-repository-collaborator) +* [获取用户的仓库权限](/rest/reference/repos#get-repository-permissions-for-a-user) -##### Repository Commit Comments +##### 仓库提交注释 -* [List commit comments for a repository](/v3/repos/comments/#list-commit-comments-for-a-repository) -* [Get a commit comment](/v3/repos/comments/#get-a-commit-comment) -* [Update a commit comment](/v3/repos/comments/#update-a-commit-comment) -* [Delete a commit comment](/v3/repos/comments/#delete-a-commit-comment) -* [List commit comments](/v3/repos/comments/#list-commit-comments) -* [Create a commit comment](/v3/repos/comments/#create-a-commit-comment) +* [列出仓库的提交注释](/rest/reference/repos#list-commit-comments-for-a-repository) +* [获取提交注释](/rest/reference/repos#get-a-commit-comment) +* [更新提交注释](/rest/reference/repos#update-a-commit-comment) +* [删除提交注释](/rest/reference/repos#delete-a-commit-comment) +* [列出提交注释](/rest/reference/repos#list-commit-comments) +* [创建提交注释](/rest/reference/repos#create-a-commit-comment) -##### Repository Commits +##### 仓库提交 -* [List commits](/v3/repos/commits/#list-commits) -* [Get a commit](/v3/repos/commits/#get-a-commit) -* [List branches for head commit](/v3/repos/commits/#list-branches-for-head-commit) -* [List pull requests associated with commit](/v3/repos/commits/#list-pull-requests-associated-with-commit) +* [列出提交](/rest/reference/repos#list-commits) +* [获取提交](/rest/reference/repos#get-a-commit) +* [列出头部提交分支](/rest/reference/repos#list-branches-for-head-commit) +* [列出与提交关联的拉取请求](/rest/reference/repos#list-pull-requests-associated-with-commit) -##### Repository Community +##### 仓库社区 -* [Get the code of conduct for a repository](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) +* [获取仓库的行为准则](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% if currentVersion == "free-pro-team@latest" %} -* [Get community profile metrics](/v3/repos/community/#get-community-profile-metrics) +* [获取社区资料指标](/rest/reference/repos#get-community-profile-metrics) {% endif %} -##### Repository Contents +##### 仓库内容 -* [Download a repository archive](/v3/repos/contents/#download-a-repository-archive) -* [Get repository content](/v3/repos/contents/#get-repository-content) -* [Create or update file contents](/v3/repos/contents/#create-or-update-file-contents) -* [Delete a file](/v3/repos/contents/#delete-a-file) -* [Get a repository README](/v3/repos/contents/#get-a-repository-readme) -* [Get the license for a repository](/v3/licenses/#get-the-license-for-a-repository) +* [下载仓库存档](/rest/reference/repos#download-a-repository-archive) +* [获取仓库内容](/rest/reference/repos#get-repository-content) +* [创建或更新文件内容](/rest/reference/repos#create-or-update-file-contents) +* [删除文件](/rest/reference/repos#delete-a-file) +* [获取仓库自述文件](/rest/reference/repos#get-a-repository-readme) +* [获取仓库许可](/rest/reference/licenses#get-the-license-for-a-repository) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -##### Repository Event Dispatches +##### 仓库事件调度 -* [Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event) +* [创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event) {% endif %} -##### Repository Hooks +##### 仓库挂钩 -* [List repository webhooks](/v3/repos/hooks/#list-repository-webhooks) -* [Create a repository webhook](/v3/repos/hooks/#create-a-repository-webhook) -* [Get a repository webhook](/v3/repos/hooks/#get-a-repository-webhook) -* [Update a repository webhook](/v3/repos/hooks/#update-a-repository-webhook) -* [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) -* [Ping a repository webhook](/v3/repos/hooks/#ping-a-repository-webhook) -* [Test the push repository webhook](/v3/repos/hooks/#test-the-push-repository-webhook) +* [列出仓库 web 挂钩](/rest/reference/repos#list-repository-webhooks) +* [创建仓库 web 挂钩](/rest/reference/repos#create-a-repository-webhook) +* [获取仓库 web 挂钩](/rest/reference/repos#get-a-repository-webhook) +* [更新仓库 web 挂钩](/rest/reference/repos#update-a-repository-webhook) +* [删除仓库 web 挂钩](/rest/reference/repos#delete-a-repository-webhook) +* [Ping 仓库 web 挂钩](/rest/reference/repos#ping-a-repository-webhook) +* [测试推送仓库 web 挂钩](/rest/reference/repos#test-the-push-repository-webhook) -##### Repository Invitations +##### 仓库邀请 -* [List repository invitations](/v3/repos/invitations/#list-repository-invitations) -* [Update a repository invitation](/v3/repos/invitations/#update-a-repository-invitation) -* [Delete a repository invitation](/v3/repos/invitations/#delete-a-repository-invitation) -* [List repository invitations for the authenticated user](/v3/repos/invitations/#list-repository-invitations-for-the-authenticated-user) -* [Accept a repository invitation](/v3/repos/invitations/#accept-a-repository-invitation) -* [Decline a repository invitation](/v3/repos/invitations/#decline-a-repository-invitation) +* [列出仓库邀请](/rest/reference/repos#list-repository-invitations) +* [更新仓库邀请](/rest/reference/repos#update-a-repository-invitation) +* [删除仓库邀请](/rest/reference/repos#delete-a-repository-invitation) +* [列出经验证用户的仓库邀请](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [接受仓库邀请](/rest/reference/repos#accept-a-repository-invitation) +* [拒绝仓库邀请](/rest/reference/repos#decline-a-repository-invitation) -##### Repository Keys +##### 仓库密钥 -* [List deploy keys](/v3/repos/keys/#list-deploy-keys) -* [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) -* [Get a deploy key](/v3/repos/keys/#get-a-deploy-key) -* [Delete a deploy key](/v3/repos/keys/#delete-a-deploy-key) +* [列出部署密钥](/rest/reference/repos#list-deploy-keys) +* [创建部署密钥](/rest/reference/repos#create-a-deploy-key) +* [获取部署密钥](/rest/reference/repos#get-a-deploy-key) +* [删除部署密钥](/rest/reference/repos#delete-a-deploy-key) -##### Repository Pages +##### 仓库页面 -* [Get a GitHub Pages site](/rest/reference/repos#get-a-github-pages-site) -* [Create a GitHub Pages site](/rest/reference/repos#create-a-github-pages-site) -* [Update information about a GitHub Pages site](/rest/reference/repos#update-information-about-a-github-pages-site) -* [Delete a GitHub Pages site](/rest/reference/repos#delete-a-github-pages-site) -* [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) -* [Request a GitHub Pages build](/rest/reference/repos#request-a-github-pages-build) -* [Get GitHub Pages build](/rest/reference/repos#get-github-pages-build) -* [Get latest pages build](/rest/reference/repos#get-latest-pages-build) +* [获取 GitHub Pages 站点](/rest/reference/repos#get-a-github-pages-site) +* [创建 GitHub Pages 站点](/rest/reference/repos#create-a-github-pages-site) +* [更新关于 GitHub Pages 站点的信息](/rest/reference/repos#update-information-about-a-github-pages-site) +* [删除 GitHub Pages 站点](/rest/reference/repos#delete-a-github-pages-site) +* [列出 GitHub Pages 构建](/rest/reference/repos#list-github-pages-builds) +* [请求 GitHub Pages 构建](/rest/reference/repos#request-a-github-pages-build) +* [获取 GitHub Pages 构建](/rest/reference/repos#get-github-pages-build) +* [获取最新页面构建](/rest/reference/repos#get-latest-pages-build) {% if enterpriseServerVersions contains currentVersion %} -##### Repository Pre Receive Hooks +##### 仓库预接收挂钩 -* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) -* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) -* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) -* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) +* [列出仓库的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) +* [获取仓库的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) +* [更新仓库的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) +* [删除仓库的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) {% endif %} -##### Repository Releases +##### 仓库发行版 * [列出发行版](/rest/reference/repos/#list-releases) -* [Create a release](/rest/reference/repos/#create-a-release) -* [Get a release](/rest/reference/repos/#get-a-release) +* [创建发行版](/rest/reference/repos/#create-a-release) +* [获取发行版](/rest/reference/repos/#get-a-release) * [更新发行版](/rest/reference/repos/#update-a-release) -* [Delete a release](/rest/reference/repos/#delete-a-release) -* [List release assets](/rest/reference/repos/#list-release-assets) -* [Get a release asset](/rest/reference/repos/#get-a-release-asset) -* [Update a release asset](/rest/reference/repos/#update-a-release-asset) -* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset) -* [Get the latest release](/rest/reference/repos/#get-the-latest-release) -* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name) +* [删除发行版](/rest/reference/repos/#delete-a-release) +* [列出发行版资产](/rest/reference/repos/#list-release-assets) +* [获取发行版资产](/rest/reference/repos/#get-a-release-asset) +* [更新发行版资产](/rest/reference/repos/#update-a-release-asset) +* [删除发行版资产](/rest/reference/repos/#delete-a-release-asset) +* [获取最新发行版](/rest/reference/repos/#get-the-latest-release) +* [按标记名称获取发行版](/rest/reference/repos/#get-a-release-by-tag-name) -##### Repository Stats +##### 仓库统计 -* [Get the weekly commit activity](/v3/repos/statistics/#get-the-weekly-commit-activity) -* [Get the last year of commit activity](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -* [Get all contributor commit activity](/v3/repos/statistics/#get-all-contributor-commit-activity) -* [Get the weekly commit count](/v3/repos/statistics/#get-the-weekly-commit-count) -* [Get the hourly commit count for each day](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +* [获取每周提交活动](/rest/reference/repos#get-the-weekly-commit-activity) +* [获取最近一年的提交活动](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [获取所有参与者提交活动](/rest/reference/repos#get-all-contributor-commit-activity) +* [获取每周提交计数](/rest/reference/repos#get-the-weekly-commit-count) +* [获取每天的每小时提交计数](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) {% if currentVersion == "free-pro-team@latest" %} ##### 仓库漏洞警报 -* [Enable vulnerability alerts](/v3/repos/#enable-vulnerability-alerts) -* [Disable vulnerability alerts](/v3/repos/#disable-vulnerability-alerts) +* [启用漏洞警报](/rest/reference/repos#enable-vulnerability-alerts) +* [禁用漏洞警报](/rest/reference/repos#disable-vulnerability-alerts) {% endif %} ##### 根 -* [根端点](/v3/#root-endpoint) -* [表情符号](/v3/emojis/#emojis) -* [Get rate limit status for the authenticated user](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) +* [根端点](/rest#root-endpoint) +* [表情符号](/rest/reference/emojis#emojis) +* [获取经验证用户的速率限制状态](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) ##### 搜索 -* [Search code](/v3/search/#search-code) -* [Search commits](/v3/search/#search-commits) -* [Search labels](/v3/search/#search-labels) -* [搜索仓库](/v3/search/#search-repositories) -* [Search topics](/v3/search/#search-topics) -* [Search users](/v3/search/#search-users) +* [搜索代码](/rest/reference/search#search-code) +* [搜索提交](/rest/reference/search#search-commits) +* [搜索标签](/rest/reference/search#search-labels) +* [搜索仓库](/rest/reference/search#search-repositories) +* [搜索主题](/rest/reference/search#search-topics) +* [搜索用户](/rest/reference/search#search-users) ##### 状态 -* [Get the combined status for a specific reference](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) -* [List commit statuses for a reference](/v3/repos/statuses/#list-commit-statuses-for-a-reference) -* [Create a commit status](/v3/repos/statuses/#create-a-commit-status) +* [获取特定引用的组合状态](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [列出引用的提交状态](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [创建提交状态](/rest/reference/repos#create-a-commit-status) -##### Team Discussions +##### 团队讨论 -* [List discussions](/v3/teams/discussions/#list-discussions) -* [Create a discussion](/v3/teams/discussions/#create-a-discussion) -* [Get a discussion](/v3/teams/discussions/#get-a-discussion) -* [Update a discussion](/v3/teams/discussions/#update-a-discussion) -* [Delete a discussion](/v3/teams/discussions/#delete-a-discussion) -* [List discussion comments](/v3/teams/discussion_comments/#list-discussion-comments) -* [Create a discussion comment](/v3/teams/discussion_comments/#create-a-discussion-comment) -* [Get a discussion comment](/v3/teams/discussion_comments/#get-a-discussion-comment) -* [Update a discussion comment](/v3/teams/discussion_comments/#update-a-discussion-comment) -* [Delete a discussion comment](/v3/teams/discussion_comments/#delete-a-discussion-comment) +* [列出讨论](/rest/reference/teams#list-discussions) +* [创建讨论](/rest/reference/teams#create-a-discussion) +* [获取讨论](/rest/reference/teams#get-a-discussion) +* [更新讨论](/rest/reference/teams#update-a-discussion) +* [删除讨论](/rest/reference/teams#delete-a-discussion) +* [列出讨论注释](/rest/reference/teams#list-discussion-comments) +* [创建讨论注释](/rest/reference/teams#create-a-discussion-comment) +* [获取讨论注释](/rest/reference/teams#get-a-discussion-comment) +* [更新讨论注释](/rest/reference/teams#update-a-discussion-comment) +* [删除讨论注释](/rest/reference/teams#delete-a-discussion-comment) ##### 主题 -* [Get all repository topics](/v3/repos#get-all-repository-topics) -* [Replace all repository topics](/v3/repos/#replace-all-repository-topics) +* [获取所有仓库主题](/rest/reference/repos#get-all-repository-topics) +* [替换所有仓库主题](/rest/reference/repos#replace-all-repository-topics) {% if currentVersion == "free-pro-team@latest" %} ##### 流量 -* [Get repository clones](/v3/repos/traffic/#get-repository-clones) -* [Get top referral paths](/v3/repos/traffic/#get-top-referral-paths) -* [Get top referral sources](/v3/repos/traffic/#get-top-referral-sources) -* [Get page views](/v3/repos/traffic/#get-page-views) +* [获取仓库克隆](/rest/reference/repos#get-repository-clones) +* [获取主要推荐途径](/rest/reference/repos#get-top-referral-paths) +* [获取主要推荐来源](/rest/reference/repos#get-top-referral-sources) +* [获取页面视图](/rest/reference/repos#get-page-views) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -##### User Blocking +##### 用户阻止 -* [List users blocked by the authenticated user](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) -* [Check if a user is blocked by the authenticated user](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) -* [List users blocked by an organization](/v3/orgs/blocking/#list-users-blocked-by-an-organization) -* [Check if a user is blocked by an organization](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) -* [Block a user from an organization](/v3/orgs/blocking/#block-a-user-from-an-organization) -* [Unblock a user from an organization](/v3/orgs/blocking/#unblock-a-user-from-an-organization) -* [Block a user](/v3/users/blocking/#block-a-user) -* [Unblock a user](/v3/users/blocking/#unblock-a-user) +* [列出经验证用户阻止的用户](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [检查用户是否被经验证的用户阻止](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [列出被组织阻止的用户](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [检查用户是否被组织阻止](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [阻止用户访问组织](/rest/reference/orgs#block-a-user-from-an-organization) +* [取消阻止用户访问组织](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [阻止用户](/rest/reference/users#block-a-user) +* [取消阻止用户](/rest/reference/users#unblock-a-user) {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -##### User Emails +##### 用户电子邮件 {% if currentVersion == "free-pro-team@latest" %} -* [Set primary email visibility for the authenticated user](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) +* [设置经验证用户的主电子邮件地址可见性](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %} -* [List email addresses for the authenticated user](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) -* [Add email address(es)](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) -* [Delete email address(es)](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) -* [List public email addresses for the authenticated user](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) +* [列出经验证用户的电子邮件地址](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [添加电子邮件地址](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [删除电子邮件地址](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [列出经验证用户的公开电子邮件地址](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) {% endif %} -##### User Followers +##### 用户关注者 -* [List followers of a user](/v3/users/followers/#list-followers-of-a-user) -* [List the people a user follows](/v3/users/followers/#list-the-people-a-user-follows) -* [Check if a person is followed by the authenticated user](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) -* [Follow a user](/v3/users/followers/#follow-a-user) -* [Unfollow a user](/v3/users/followers/#unfollow-a-user) -* [Check if a user follows another user](/v3/users/followers/#check-if-a-user-follows-another-user) +* [列出用户的关注者](/rest/reference/users#list-followers-of-a-user) +* [列出用户关注的人](/rest/reference/users#list-the-people-a-user-follows) +* [检查用户是否被经验证用户关注](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [关注用户](/rest/reference/users#follow-a-user) +* [取消关注用户](/rest/reference/users#unfollow-a-user) +* [检查用户是否关注其他用户](/rest/reference/users#check-if-a-user-follows-another-user) -##### User Gpg Keys +##### 用户 Gpg 密钥 -* [List GPG keys for the authenticated user](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) -* [Create a GPG key for the authenticated user](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) -* [Get a GPG key for the authenticated user](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) -* [Delete a GPG key for the authenticated user](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) -* [List gpg keys for a user](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) +* [列出经验证用户的 GPG 密钥](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [为经验证用户创建 GPG 密钥](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [获取经验证用户的 GPG 密钥](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [删除经验证用户的 GPG 密钥](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [列出用户的 Gpg 密钥](/rest/reference/users#list-gpg-keys-for-a-user) -##### User Public Keys +##### 用户公钥 -* [List public SSH keys for the authenticated user](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) -* [Create a public SSH key for the authenticated user](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) -* [Get a public SSH key for the authenticated user](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) -* [Delete a public SSH key for the authenticated user](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) -* [List public keys for a user](/v3/users/keys/#list-public-keys-for-a-user) +* [列出经验证用户的 SSH 公钥](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [为经验证用户创建 SSH 公钥](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [获取经验证用户的 SSH 公钥](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [删除经验证用户的 SSH 公钥](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [列出用户的公钥](/rest/reference/users#list-public-keys-for-a-user) ##### 用户 -* [Get the authenticated user](/v3/users/#get-the-authenticated-user) -* [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) +* [获取经验证的用户](/rest/reference/users#get-the-authenticated-user) +* [列出用户访问令牌可访问的应用程序安装设施](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) {% if currentVersion == "free-pro-team@latest" %} -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [列出经验证用户的订阅](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% endif %} -* [List users](/v3/users/#list-users) -* [Get a user](/v3/users/#get-a-user) +* [列出用户](/rest/reference/users#list-users) +* [获取用户](/rest/reference/users#get-a-user) {% if currentVersion == "free-pro-team@latest" %} -##### Workflow Runs +##### 工作流程运行 -* [List workflow runs for a repository](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) -* [Get a workflow run](/v3/actions/workflow-runs/#get-a-workflow-run) -* [Cancel a workflow run](/v3/actions/workflow-runs/#cancel-a-workflow-run) -* [Download workflow run logs](/v3/actions/workflow-runs/#download-workflow-run-logs) -* [Delete workflow run logs](/v3/actions/workflow-runs/#delete-workflow-run-logs) -* [Re run a workflow](/v3/actions/workflow-runs/#re-run-a-workflow) -* [List workflow runs](/v3/actions/workflow-runs/#list-workflow-runs) -* [Get workflow run usage](/v3/actions/workflow-runs/#get-workflow-run-usage) +* [列出仓库的工作流程运行](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [获取工作流程运行](/rest/reference/actions#get-a-workflow-run) +* [取消工作流程运行](/rest/reference/actions#cancel-a-workflow-run) +* [下载工作流程运行日志](/rest/reference/actions#download-workflow-run-logs) +* [删除工作流程运行日志](/rest/reference/actions#delete-workflow-run-logs) +* [重新运行工作流程](/rest/reference/actions#re-run-a-workflow) +* [列出工作流程运行](/rest/reference/actions#list-workflow-runs) +* [获取工作流程运行使用情况](/rest/reference/actions#get-workflow-run-usage) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ##### 工作流程 -* [List repository workflows](/v3/actions/workflows/#list-repository-workflows) -* [Get a workflow](/v3/actions/workflows/#get-a-workflow) -* [Get workflow usage](/v3/actions/workflows/#get-workflow-usage) +* [列出仓库工作流程](/rest/reference/actions#list-repository-workflows) +* [获取工作流程](/rest/reference/actions#get-a-workflow) +* [获取工作流程使用情况](/rest/reference/actions#get-workflow-usage) {% endif %} diff --git a/translations/zh-CN/content/developers/apps/installing-github-apps.md b/translations/zh-CN/content/developers/apps/installing-github-apps.md index 0daf74da0b..ed8bc1e8af 100644 --- a/translations/zh-CN/content/developers/apps/installing-github-apps.md +++ b/translations/zh-CN/content/developers/apps/installing-github-apps.md @@ -1,6 +1,6 @@ --- -title: Installing GitHub Apps -intro: 'When your app is public, anyone can install your app on their repository through {% if currentVersion == "free-pro-team@latest" %} the {% data variables.product.prodname_marketplace %} or {% endif %}an installation URL. When your app is private, you can only install the app on repositories that you own.' +title: 安装 GitHub 应用程序 +intro: '当您的应用程序为公共时，任何人都可以通过 {% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_marketplace %} 或{% endif %}安装 URL 将您的应用程序安装在他们的仓库中。 当您的应用程序为私有时，您只能将该应用程序安装在您自己的仓库中。' redirect_from: - /apps/installing-github-apps versions: @@ -11,22 +11,22 @@ versions: {% note %} -**Note:** Your {% data variables.product.prodname_github_app %} will have access to any repositories the app creates, even if someone only installs your app on selected repositories. +**注：**您的 {% data variables.product.prodname_github_app %} 将有权访问应用程序创建的任何仓库，即使用户只在选定的仓库中安装您的应用程序。 {% endnote %} -### Installing your private GitHub App on your repository +### 在您的仓库中安装您的私有 GitHub 应用程序 -Once you create a private GitHub App, you can install it on one of your org or user repositories. For more information, see "[Private installation flow](/apps/managing-github-apps/making-a-github-app-public-or-private/#private-installation-flow)." +创建私有 GitHub 应用程序后，您可以将其安装在您的某个组织或用户仓库中。 更多信息请参阅“[私有安装流程](/apps/managing-github-apps/making-a-github-app-public-or-private/#private-installation-flow)”。 -1. From the [GitHub Apps settings page](https://github.com/settings/apps), select your app. -2. In the left sidebar, click **Install App**. -3. Click **Install** next to the organization or user account containing the correct repository. -4. Install the app on all repositories or select repositories. ![App installation permissions](/assets/images/install_permissions.png) -5. Once installed, you will see configuration options for the app on your selected account. You can make changes here, or repeat the previous steps to install the app on another account. +1. 从 [GitHub 应用程序设置页面](https://github.com/settings/apps)，选择您的应用程序。 +2. 在左边栏中，单击 **Install App（安装应用程序）**。 +3. 单击包含适当仓库的组织或用户帐户旁边的 **Install（安装）**。 +4. 将应用程序安装在所有仓库或所选仓库中。 ![App installation permissions](/assets/images/install_permissions.png) +5. 安装后，您将在所选帐户上看到应用程序的配置选项。 您可以在这里进行更改，或重复前面的步骤将应用程序安装到其他帐户上。 {% if currentVersion == "free-pro-team@latest" %} -### Offering your app in the GitHub Marketplace +### 在 GitHub Marketplace 中提供您的应用程序 You can offer a paid or free version of your app in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), where people can search for and view details about your app. {% data variables.product.prodname_marketplace %} automatically installs a GitHub App when an order is complete. diff --git a/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md index bd3a18babc..1262767482 100644 --- a/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -23,7 +23,7 @@ This article provides guidelines for existing integrators who are considering mi - Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). - Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration. - Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation. -- Open Source community support is available through [Octokit libraries](/v3/libraries/) and other frameworks such as [Probot](https://probot.github.io/). +- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/). - Integrators building GitHub Apps have opportunities to adopt earlier access to APIs. ### Converting an OAuth App to a GitHub App @@ -42,13 +42,13 @@ These guidelines assume that you have a registered OAuth App{% if currentVersion #### Review the available API endpoints for GitHub Apps -While the majority of [REST API](/v3) endpoints and [GraphQL](/v4) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/v3/apps/available-endpoints/) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. +While the majority of [REST API](/rest) endpoints and [GraphQL](/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_app %}s. #### Design to stay within API rate limits -GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/v3/#conditional-requests) or consolidate requests by using the [GraphQL API V4](/v4/). +GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest#conditional-requests) or consolidate requests by using the [GraphQL API V4](/graphql). #### Register a new GitHub App @@ -56,7 +56,7 @@ Once you've decided to make the switch to Github Apps, you'll need to [create a #### Determine the permissions your app requires -When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/v3/apps/permissions/)" for a list of the permissions needed for each endpoint available to GitHub Apps. +When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps. In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality. @@ -90,11 +90,11 @@ Once you've made the transition from an OAuth App to a GitHub App, you will need https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) and [List organization repositories](/v3/repos/#list-organization-repositories) endpoints. +You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints. #### Remove any unnecessary repository hooks -Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) on those repositories that were created by your OAuth App. +Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) on those repositories that were created by your OAuth App. #### Encourage users to revoke access to your OAuth app diff --git a/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md b/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md index 31607e2e14..27c41012e7 100644 --- a/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md @@ -32,7 +32,7 @@ Different server-to-server request rate limits apply to {% data variables.produc {% endif %} -### User-to-server requests +### 用户到服务器请求 {% data variables.product.prodname_github_app %}s can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests. diff --git a/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md index b8d6121a4d..6e392de83c 100644 --- a/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -25,7 +25,7 @@ To renew an expiring user-to-server access token, you can exchange the `refresh_ `POST https://github.com/login/oauth/access_token` -This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/v3/guides/basics-of-authentication/#providing-a-callback)." +This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." #### 参数 @@ -69,4 +69,4 @@ If you want your app to use non-expiring user-to-server access tokens, you can d Existing {% data variables.product.prodname_github_app %}s using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app. -Enabling expiring user tokens for existing {% data variables.product.prodname_github_app %}s requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +Enabling expiring user tokens for existing {% data variables.product.prodname_github_app %}s requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 diff --git a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md index ad77981106..1e0b15d4f3 100644 --- a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md @@ -41,13 +41,13 @@ X-Accepted-OAuth-Scopes: user | 名称 | 描述 | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/v3/enterprise-admin).{% endif %} +| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} | **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/v3/repos/deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/v3/code-scanning).{% endif %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | |  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | diff --git a/translations/zh-CN/content/developers/apps/setting-permissions-for-github-apps.md b/translations/zh-CN/content/developers/apps/setting-permissions-for-github-apps.md index aac9981033..ae0b72796d 100644 --- a/translations/zh-CN/content/developers/apps/setting-permissions-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/setting-permissions-for-github-apps.md @@ -17,4 +17,4 @@ When you create a GitHub App, you can select the permissions it needs to access By default, GitHub Apps have `Read-only` access to metadata endpoints. Metadata is a collection of read-only endpoints that provide general information about resources that the authorized installation can access. -{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/v3/apps/permissions/#metadata-permissions)." +{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/rest/reference/permissions-required-for-github-apps#metadata-permissions)." diff --git a/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index 6257e39292..8c71adf5db 100644 --- a/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -37,7 +37,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub 应用程序](/apps/about-apps) * [Web 挂钩](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -220,7 +220,7 @@ end #### Define a route handler -An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You'll won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. ``` ruby post '/event_handler' do diff --git a/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md b/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md index ca8e909492..a5f289705b 100644 --- a/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md @@ -24,7 +24,7 @@ People who have installed a GitHub App, also called installation owners, can onl {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Select the +4. 选择 {% data variables.product.prodname_github_app %} you want to suspend. ![App selection](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} diff --git a/translations/zh-CN/content/developers/apps/using-content-attachments.md b/translations/zh-CN/content/developers/apps/using-content-attachments.md index af7d3f3b5b..664b642e52 100644 --- a/translations/zh-CN/content/developers/apps/using-content-attachments.md +++ b/translations/zh-CN/content/developers/apps/using-content-attachments.md @@ -55,7 +55,7 @@ The content attachment flow shows you the relationship between the URL in the is } ``` -**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/v3/apps/installations/#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -116,7 +116,7 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -For more information on `node_id`, see "[Using Global Node IDs](/v4/guides/using-global-node-ids/)." +For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." ### Example using Probot and GitHub App Manifests @@ -124,8 +124,8 @@ To quickly setup a GitHub App that can use the {% data variables.product.prodnam To create a Probot App, follow these steps: -1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app). -2. Open the project you created, and customize the settings in the `app.yml` file. Subscribe to the `content_reference` event and enable `content_references` write permissions: +1. [生成新的 GitHub 应用程序](https://probot.github.io/docs/development/#generating-a-new-app)。 +2. 打开您创建的项目，自定义 `app.yml` 文件中的设置。 Subscribe to the `content_reference` event and enable `content_references` write permissions: ``` yml @@ -168,7 +168,7 @@ To create a Probot App, follow these steps: 4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to [localhost:3000](http://localhost:3000), and click the **Register GitHub App** button: - ![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png) + ![注册 Probot GitHub 应用程序](/assets/images/github-apps/github_apps_probot-registration.png) 5. Install the app on a test repository. 6. Create an issue in your test repository. diff --git a/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md b/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md index 45c9664bf8..d969ac5d6b 100644 --- a/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md @@ -31,7 +31,7 @@ You may find it helpful to have a basic understanding of the following: * [GitHub 应用程序](/apps/about-apps) * [Web 挂钩](/webhooks) * [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/v3) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) But you can follow along at any experience level. We'll link out to information you need along the way! @@ -43,7 +43,7 @@ Before you begin, you'll need to do the following: $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git ``` - Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code. + 在目录中，您将找到包含本快速入门将要使用的模板代码的 `template_server.rb` 文件以及包含已完成项目代码的 `server.rb` 文件。 1. Follow the steps in the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart to configure and run the `template_server.rb` app server. If you've previously completed a GitHub App quickstart other than [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/), you should register a _new_ GitHub App and start a new Smee channel to use with this quickstart. @@ -76,22 +76,22 @@ These are the steps you'll complete to create your first GitHub App: When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels. -To update your app's permissions: +要更新应用程序的权限： -1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar. +1. 从[应用程序设置页面](https://github.com/settings/apps)选择应用程序，然后单击边栏中的 **Permissions & Webhooks（权限和 web 挂钩）**。 1. In the "Permissions" section, find "Issues," and select **Read & Write** in the "Access" dropdown next to it. The description says this option grants access to both issues and labels, which is just what you need. 1. In the "Subscribe to events" section, select **Issues** to subscribe to the event. {% data reusables.apps.accept_new_permissions_steps %} -太好了！ Your app has permission to do the tasks you want it to do. Now you can add the code to make it work. +太好了！ 您的应用程序现在有权限执行所需的任务。 Now you can add the code to make it work. ### 步骤 2. Add event handling The first thing your app needs to do is listen for new issues that are opened. Now that you've subscribed to the **Issues** event, you'll start receiving the [`issues`](/webhooks/event-payloads/#issues) webhook, which is triggered when certain issue-related actions occur. You can filter this event type for the specific action you want in your code. -GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route. +GitHub 将 web 挂钩有效负载作为 `POST` 请求发送。 Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route. -An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this: +您在[前提条件](#prerequisites)部分中下载的 `template_server.rb` 文件中已包括空 `post '/event_handler'` 路由。 空路由如下所示： ``` ruby post '/event_handler' do @@ -115,7 +115,7 @@ when 'issues' end ``` -Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in `issues` event types. Each event has an additional `action` field that indicates the type of action that triggered the events. For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`. +GitHub 发送的每个事件都包含一个名为 `HTTP_X_GITHUB_EVENT` 的请求标头，它指示 `POST` 请求中的事件类型。 Right now, you're only interested in `issues` event types. 每个事件都有一个附加的 `action` 字段，它指示触发事件的操作类型。 For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`. To test your event handler, try adding a temporary helper method. You'll update later when you [Add label handling](#step-4-add-label-handling). For now, add the following code inside the `helpers do` section of the code. You can put the new method above or below any of the other helper methods. Order doesn't matter. @@ -143,11 +143,11 @@ Before the label can be _added_ anywhere, you'll need to _create_ the custom lab {% tip %} -**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/v3/issues/labels/#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. +**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. {% endtip %} -Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/v3/issues/labels/#add-labels-to-an-issue). +Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue). ### 步骤 4. Add label handling diff --git a/translations/zh-CN/content/developers/github-marketplace/billing-customers.md b/translations/zh-CN/content/developers/github-marketplace/billing-customers.md index 3dbf647276..a3bffbc31b 100644 --- a/translations/zh-CN/content/developers/github-marketplace/billing-customers.md +++ b/translations/zh-CN/content/developers/github-marketplace/billing-customers.md @@ -25,7 +25,7 @@ Customers must be able to perform the following actions from your app's website: Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." -You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). +You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). #### 升级 diff --git a/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index b5d9ea4a0a..13c59a79b6 100644 --- a/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% warning %} -If you offer a GitHub App in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate OAuth App to support this flow. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. +If you offer a GitHub App in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate OAuth App to support this flow. 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 {% endwarning %} @@ -68,7 +68,7 @@ After the customer completes the authorization, your app receives an OAuth acces ### 步骤 4. Provisioning customer accounts -Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. +Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. {% data reusables.marketplace.marketplace-double-purchases %} @@ -76,6 +76,6 @@ If the purchase is for an organization and per-user, you can prompt the customer You can customize the way that organization members receive access to your app. Here are a few suggestions: -**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/v3/orgs/members/#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. +**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/rest/reference/orgs#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. **Per-unit pricing:** One method of provisioning per-unit seats is to allow users to occupy a seat as they log in to the app. Once the customer hits the seat count threshold, your app can alert the user that they need to upgrade through {% data variables.product.prodname_marketplace %}. diff --git a/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md index b40035ac89..0237b09988 100644 --- a/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md +++ b/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md @@ -28,6 +28,6 @@ When a customer cancels a free or paid plan, your app must perform these steps t {% note %} -**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." {% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md b/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md index 048eb588fc..89841d8db0 100644 --- a/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md +++ b/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md @@ -54,7 +54,7 @@ https://www.github.com/marketplace//upgrade// For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page. -Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/v3/apps/marketplace/#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. +Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. {% note %} diff --git a/translations/zh-CN/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md b/translations/zh-CN/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md index 5ad1d2f177..1ef04efa9f 100644 --- a/translations/zh-CN/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md +++ b/translations/zh-CN/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md @@ -13,10 +13,10 @@ versions: Here are some useful endpoints available for Marketplace listings: -* [List plans](/v3/apps/marketplace/#list-plans) -* [List accounts for a plan](/v3/apps/marketplace/#list-accounts-for-a-plan) -* [Get a subscription plan for an account](/v3/apps/marketplace/#get-a-subscription-plan-for-an-account) -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) +* [List plans](/rest/reference/apps#list-plans) +* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan) +* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [列出经验证用户的订阅](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API: @@ -25,6 +25,6 @@ See these pages for details on how to authenticate when using the {% data variab {% note %} -**Note:** [Rate limits for the REST API](/v3/#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. +**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. {% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md b/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md index 352aaf9c5e..09e79b1a7a 100644 --- a/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md @@ -37,7 +37,7 @@ Your testing scenarios may require setting up listing plans that offer free tria ### Testing APIs -For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/v3/apps/marketplace/#github-marketplace). +For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace). ### Testing webhooks diff --git a/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md index 045237bda9..50d90f1cb1 100644 --- a/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md @@ -47,7 +47,7 @@ To access {% data variables.product.prodname_marketplace %} Insights: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.marketplace_apps %} -4. Select the +4. 选择 {% data variables.product.prodname_github_app %} that you'd like to view Insights for. {% data reusables.user-settings.edit_marketplace_listing %} 6. Click the **Insights** tab. diff --git a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index 15ede21ee3..ce64f0ae76 100644 --- a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -39,7 +39,7 @@ To access {% data variables.product.prodname_marketplace %} transactions: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.marketplace_apps %} -4. Select the +4. 选择 {% data variables.product.prodname_github_app %} that you'd like to view transactions for. {% data reusables.user-settings.edit_marketplace_listing %} 6. Click the **Transactions** tab. diff --git a/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 8aba97ad0a..3254c9670c 100644 --- a/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -31,15 +31,15 @@ Web 挂钩 `POST` 请求具有特殊标头。 有关详细信息，请参阅“[ `marketplace_purchase` 对象含有以下键： -| 键 | 类型 | 描述 | -| -------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `帐户` | `对象` | 与订阅关联的 `organization` 或 `user` 帐户。 组织帐户将包含 `Organization_billing_email`, 这是组织的行政电子邮件地址。 要查找个人帐户的电子邮件地址，您可以使用[获取经过身份验证的用户](/v3/users/#get-the-authenticated-user)端点。 | -| `billing_cycle` | `字符串` | 可以是 `yearly` 或 `monthly`。 如果 `account` 所有者拥有免费 GitHub 计划并且购买了免费 {% data variables.product.prodname_marketplace %} 计划，则 `billing_cycle` 将为 `nil`。 | -| `unit_count` | `整数` | 购买的单位数。 | -| `on_free_trial` | `布尔值` | 当 `account` 处于免费试用期时，该值为 `true`。 | -| `free_trial_ends_on` | `字符串` | 免费试用到期日期。 | -| `next_billing_date` | `字符串` | 下一个结算周期开始日期。 如果 `account` 所有者拥有免费 GitHub.com 计划并且购买了免费 {% data variables.product.prodname_marketplace %} 计划，则 `next_billing_date` 将为 `nil`。 | -| `plan` | `对象` | `user` 或 `organization` 购买的计划。 | +| 键 | 类型 | 描述 | +| -------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `帐户` | `对象` | 与订阅关联的 `organization` 或 `user` 帐户。 组织帐户将包含 `Organization_billing_email`, 这是组织的行政电子邮件地址。 要查找个人帐户的电子邮件地址，您可以使用[获取经过身份验证的用户](/rest/reference/users#get-the-authenticated-user)端点。 | +| `billing_cycle` | `字符串` | 可以是 `yearly` 或 `monthly`。 如果 `account` 所有者拥有免费 GitHub 计划并且购买了免费 {% data variables.product.prodname_marketplace %} 计划，则 `billing_cycle` 将为 `nil`。 | +| `unit_count` | `整数` | 购买的单位数。 | +| `on_free_trial` | `布尔值` | 当 `account` 处于免费试用期时，该值为 `true`。 | +| `free_trial_ends_on` | `字符串` | 免费试用到期日期。 | +| `next_billing_date` | `字符串` | 下一个结算周期开始日期。 如果 `account` 所有者拥有免费 GitHub.com 计划并且购买了免费 {% data variables.product.prodname_marketplace %} 计划，则 `next_billing_date` 将为 `nil`。 | +| `plan` | `对象` | `user` 或 `organization` 购买的计划。 | `plan` 对象含有以下键： diff --git a/translations/zh-CN/content/developers/overview/about-githubs-apis.md b/translations/zh-CN/content/developers/overview/about-githubs-apis.md index db0e1b3843..3ffd0aa908 100644 --- a/translations/zh-CN/content/developers/overview/about-githubs-apis.md +++ b/translations/zh-CN/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/v3/) and the [GraphQL API](/v4/). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). -When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). +When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). -For information on using the GraphQL API, see the [v4 docs](/v4/). +For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md index 262e5c8447..8856911048 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md @@ -31,4 +31,4 @@ See "[Webhook event payloads](/webhooks/event-payloads)" for the list of availab For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. [org-hooks]: /rest/reference/orgs#webhooks/ -[repo-hooks]: /v3/repos/hooks/ +[repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md index 650d389d82..b52573e1b7 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md @@ -65,5 +65,5 @@ When you're finished, click **Add webhook**. 唷！ Now that you created the web To configure a webhook for all events, use the wildcard (`*`) character to specify the webhook events. When you add the wildcard event, we'll replace any existing events you have configured with the wildcard event and send you payloads for all supported events. You'll also automatically get any new events we might add in the future. [webhooks-overview]: /webhooks/ -[webhook-api]: /v3/repos/hooks/ +[webhook-api]: /rest/reference/repos#hooks [hooks-api]: /webhooks/#events diff --git a/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md b/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md index 0ee3af7ee6..117b732c22 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md @@ -40,7 +40,7 @@ The event objects returned from the Events API endpoints have the same structure #### Example WatchEvent event object -This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/v3/activity/events). +This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events). ``` Status: 200 OK @@ -198,22 +198,22 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -| 键 | 类型 | 描述 | -| -------------------------- | ----- | ----------------------------------------------------------------------------------------------------------------- | -| `push_id` | `整数` | Unique identifier for the push. | -| `size` | `整数` | The number of commits in the push. | -| `distinct_size` | `整数` | The number of distinct commits in the push. | -| `ref` | `字符串` | 被推送的完整 [`git ref`](/v3/git/refs/)。 Example: `refs/heads/main`. | -| `头部` | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。 | -| `before` | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。 | -| `commits` | `数组` | 描述所推送提交的提交对象数组。 （该数组最多包含 20 个提交。 如有必要，可使用 [Commits API](/v3/repos/commits/) 获取更多提交。 此限制仅适用于时间表事件，而不适用于 web 挂钩递送。） | -| `commits[][sha]` | `字符串` | 提交的 SHA。 | -| `commits[][message]` | `字符串` | 提交消息. | -| `commits[][author]` | `对象` | 提交的 Git 作者。 | -| `commits[][author][name]` | `字符串` | Git 作者的名称。 | -| `commits[][author][email]` | `字符串` | Git 作者的电子邮件地址。 | -| `commits[][url]` | `url` | 指向提交 API 资源的 URL。 | -| `commits[][distinct]` | `布尔值` | 此提交是否与之前推送的任何提交不同。 | +| 键 | 类型 | 描述 | +| -------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `push_id` | `整数` | Unique identifier for the push. | +| `size` | `整数` | The number of commits in the push. | +| `distinct_size` | `整数` | The number of distinct commits in the push. | +| `ref` | `字符串` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `头部` | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。 | +| `before` | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。 | +| `commits` | `数组` | 描述所推送提交的提交对象数组。 （该数组最多包含 20 个提交。 If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. 此限制仅适用于时间表事件，而不适用于 web 挂钩递送。） | +| `commits[][sha]` | `字符串` | 提交的 SHA。 | +| `commits[][message]` | `字符串` | 提交消息. | +| `commits[][author]` | `对象` | 提交的 Git 作者。 | +| `commits[][author][name]` | `字符串` | Git 作者的名称。 | +| `commits[][author][email]` | `字符串` | Git 作者的电子邮件地址。 | +| `commits[][url]` | `url` | 指向提交 API 资源的 URL。 | +| `commits[][distinct]` | `布尔值` | 此提交是否与之前推送的任何提交不同。 | ### ReleaseEvent diff --git a/translations/zh-CN/content/developers/webhooks-and-events/issue-event-types.md b/translations/zh-CN/content/developers/webhooks-and-events/issue-event-types.md index 722303132a..dfac9e4e09 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/issue-event-types.md @@ -10,7 +10,7 @@ versions: --- -Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/v3/issues/events) and the [Timeline Events API](/v3/issues/timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. +Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. @@ -129,7 +129,7 @@ A comment was added to the issue or pull request. | `html_url` | `字符串` | The HTML URL of the issue comment. | | `issue_url` | `字符串` | The HTML URL of the issue. | | `id` | `整数` | The unique identifier of the event. | -| `node_id` | `字符串` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `字符串` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `用户` | `对象` | The person who commented on the issue. | | `created_at` | `字符串` | The timestamp indicating when the comment was added. | | `updated_at` | `字符串` | The timestamp indicating when the comment was updated or created, if the comment is never updated. | @@ -152,19 +152,19 @@ A commit was added to the pull request's `HEAD` branch. {% data reusables.issue-events.timeline_events_object_properties %} -| 名称 | 类型 | 描述 | -| ------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `sha` | `字符串` | The SHA of the commit in the pull request. | -| `node_id` | `字符串` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `字符串` | The REST API URL to retrieve the commit. | -| `html_url` | `字符串` | The HTML URL of the commit. | -| `作者` | `对象` | The person who authored the commit. | -| `提交者` | `对象` | The person who committed the commit on behalf of the author. | -| `树` | `对象` | The Git tree of the commit. | -| `message` | `字符串` | 提交消息. | -| `父项` | `array of objects` | A list of parent commits. | -| `verfication` | `对象` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/v3/git/commits/#signature-verification-object)." | -| `event` | `字符串` | The event value is `"committed"`. | +| 名称 | 类型 | 描述 | +| ------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sha` | `字符串` | The SHA of the commit in the pull request. | +| `node_id` | `字符串` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `字符串` | The REST API URL to retrieve the commit. | +| `html_url` | `字符串` | The HTML URL of the commit. | +| `作者` | `对象` | The person who authored the commit. | +| `提交者` | `对象` | The person who committed the commit on behalf of the author. | +| `树` | `对象` | The Git tree of the commit. | +| `message` | `字符串` | 提交消息. | +| `父项` | `array of objects` | A list of parent commits. | +| `verfication` | `对象` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#signature-verification-object)." | +| `event` | `字符串` | The event value is `"committed"`. | ### connected @@ -583,7 +583,7 @@ The pull request was reviewed. | 名称 | 类型 | 描述 | | -------------------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `整数` | The unique identifier of the event. | -| `node_id` | `字符串` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | +| `node_id` | `字符串` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | | `用户` | `对象` | The person who commented on the issue. | | `正文` | `字符串` | The review summary text. | | `commit_id` | `字符串` | The SHA of the latest commit in the pull request at the time of the review. | diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md index eb4a105f30..ccd933fa4d 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -33,7 +33,7 @@ versions: {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} 更多信息请参阅“[构建 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)”。 -Web 挂钩事件的独特属性与您使用 [Events API](/v3/activity/events/) 时在 `payload` 属性中发现的属性相同。 唯一的例外是 [`push` 事件](#push)。 `push` 事件 web 挂钩有效负载的独特属性与 Events API 中的 `payload` 属性不同。 Web 挂钩有效负载包含更详细的信息。 +The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). 唯一的例外是 [`push` 事件](#push)。 `push` 事件 web 挂钩有效负载的独特属性与 Events API 中的 `payload` 属性不同。 Web 挂钩有效负载包含更详细的信息。 {% tip %} @@ -45,14 +45,14 @@ Web 挂钩事件的独特属性与您使用 [Events API](/v3/activity/events/) 递送到 web 挂钩已配置 URL 端点的 HTTP POST 有效负载将包含几个特殊标头： -| 标头 | 描述 | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | 触发递送的事件名称。 | +| 标头 | 描述 | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-GitHub-Event` | 触发递送的事件名称。 | | `X-GitHub-Delivery` | A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| `X-GitHub-Enterprise-Version` | 发送 HTTP POST 有效负载的 {% data variables.product.prodname_ghe_server %} 实例的版本。 | +| `X-GitHub-Enterprise-Version` | 发送 HTTP POST 有效负载的 {% data variables.product.prodname_ghe_server %} 实例的版本。 | | `X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} -| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/v3/repos/hooks/#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} +| `X-Hub-Signature` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `X-Hub-Signature-256` | This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} 此外，请求的 `User-Agent` 将含有前缀 `GitHub-Hookshot/`。 @@ -195,7 +195,7 @@ Web 挂钩事件的独特属性与您使用 [Events API](/v3/activity/events/) {% data reusables.webhooks.content_reference_short_desc %} -Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如果您注册了一个子域 (`https://subdomain.example.com`)，则只有该子域的 URL 才会触发此事件。 如果您注册了一个域 (`https://example.com`)，则该域及所有子域的 URL 都会触发此事件。 请参阅“[创建内容附件](/v3/apps/installations/#create-a-content-attachment)”以创建新的内容附件。 +Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如果您注册了一个子域 (`https://subdomain.example.com`)，则只有该子域的 URL 才会触发此事件。 如果您注册了一个域 (`https://example.com`)，则该域及所有子域的 URL 都会触发此事件。 See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. 只有 {% data variables.product.prodname_github_app %} 才能接收此事件。 {% data variables.product.prodname_github_app %} 必须具有 `content_references` `write` 权限才能订阅此事件。 @@ -715,7 +715,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ### package -与 {% data variables.product.prodname_registry %} 有关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[阻止组织用户](/v3/orgs/blocking/)”REST API。 更多信息请参阅“[使用 {% data variables.product.prodname_registry %} 管理包](/github/managing-packages-with-github-packages)”以详细了解 {% data variables.product.prodname_registry %}。 +与 {% data variables.product.prodname_registry %} 有关的活动。 {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. 更多信息请参阅“[使用 {% data variables.product.prodname_registry %} 管理包](/github/managing-packages-with-github-packages)”以详细了解 {% data variables.product.prodname_registry %}。 #### 可用性 @@ -775,7 +775,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 | -------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `zen` | `字符串` | GitHub zen 的随机字符串。 | | `hook_id` | `整数` | 触发 ping 的 web 挂钩的 ID。 | -| `挂钩` | `对象` | [web 挂钩配置](/v3/repos/hooks/#get-a-repository-webhook)。 | +| `挂钩` | `对象` | The [webhook configuration](/rest/reference/repos#get-a-repository-webhook). | | `hook[app_id]` | `整数` | 注册新的 {% data variables.product.prodname_github_app %} 时，{% data variables.product.product_name %} 将 ping 事件发送到您在注册过程中指定的 **web 挂钩 URL**。 该事件包含 `app_id`，这是[验证](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/)应用程序的必需项。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} @@ -969,24 +969,24 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 #### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| -------------------------- | ----- | ----------------------------------------------------------------------------------------------------------------- | -| `ref` | `字符串` | 被推送的完整 [`git ref`](/v3/git/refs/)。 Example: `refs/heads/main`. | -| `before` | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。 | -| `after` | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。 | -| `commits` | `数组` | 描述所推送提交的提交对象数组。 （该数组最多包含 20 个提交。 如有必要，可使用 [Commits API](/v3/repos/commits/) 获取更多提交。 此限制仅适用于时间表事件，而不适用于 web 挂钩递送。） | -| `commits[][id]` | `字符串` | 提交的 SHA。 | -| `commits[][timestamp]` | `字符串` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `字符串` | 提交消息. | -| `commits[][author]` | `对象` | 提交的 Git 作者。 | -| `commits[][author][name]` | `字符串` | Git 作者的名称。 | -| `commits[][author][email]` | `字符串` | Git 作者的电子邮件地址。 | -| `commits[][url]` | `url` | 指向提交 API 资源的 URL。 | -| `commits[][distinct]` | `布尔值` | 此提交是否与之前推送的任何提交不同。 | -| `commits[][added]` | `数组` | An array of files added in the commit. | -| `commits[][modified]` | `数组` | An array of files modified by the commit. | -| `commits[][removed]` | `数组` | An array of files removed in the commit. | -| `pusher` | `对象` | 推送提交的用户。 | +| 键 | 类型 | 描述 | +| -------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `字符串` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | +| `before` | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。 | +| `after` | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。 | +| `commits` | `数组` | 描述所推送提交的提交对象数组。 （该数组最多包含 20 个提交。 If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. 此限制仅适用于时间表事件，而不适用于 web 挂钩递送。） | +| `commits[][id]` | `字符串` | 提交的 SHA。 | +| `commits[][timestamp]` | `字符串` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `字符串` | 提交消息. | +| `commits[][author]` | `对象` | 提交的 Git 作者。 | +| `commits[][author][name]` | `字符串` | Git 作者的名称。 | +| `commits[][author][email]` | `字符串` | Git 作者的电子邮件地址。 | +| `commits[][url]` | `url` | 指向提交 API 资源的 URL。 | +| `commits[][distinct]` | `布尔值` | 此提交是否与之前推送的任何提交不同。 | +| `commits[][added]` | `数组` | An array of files added in the commit. | +| `commits[][modified]` | `数组` | An array of files modified by the commit. | +| `commits[][removed]` | `数组` | An array of files removed in the commit. | +| `pusher` | `对象` | 推送提交的用户。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1022,7 +1022,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### repository_dispatch -当 {% data variables.product.prodname_github_app %} 将 `POST` 请求发送到“[创建仓库分发事件](/v3/repos/#create-a-repository-dispatch-event)”端点时，此事件发生。 +This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. #### 可用性 @@ -1047,7 +1047,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 | 键 | 类型 | 描述 | | -------- | ----- | -------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
  • `created` - 创建了仓库。
  • `deleted` - 仓库被删除。 This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - 仓库被存档。
  • `unarchived` - 仓库被取消存档。
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - 仓库被[启用匿名 Git 访问](/v3/previews/#anonymous-git-access-to-repositories)，`anonymous_access_disabled` - 仓库被[禁用匿名 Git 访问](/v3/previews/#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - 仓库的信息被编辑。
  • `renamed` - 仓库被重命名。
  • `transferred` - 仓库被转让。
  • `publicized` - 仓库被设为公共。
  • `privatized` - 仓库被设为私有。
| +| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
  • `created` - 创建了仓库。
  • `deleted` - 仓库被删除。 This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - 仓库被存档。
  • `unarchived` - 仓库被取消存档。
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - 仓库的信息被编辑。
  • `renamed` - 仓库被重命名。
  • `transferred` - 仓库被转让。
  • `publicized` - 仓库被设为公共。
  • `privatized` - 仓库被设为私有。
| {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1060,7 +1060,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% if currentVersion == "free-pro-team@latest"%} ### repository_import -{% data reusables.webhooks.repository_import_short_desc %} 要在个人仓库中接收此事件，必须在导入之前创建一个空仓库。 此事件可使用 [GitHub 导入工具](/articles/importing-a-repository-with-github-importer/)或[来源导入 API](/v3/migrations/source_imports/) 触发。 +{% data reusables.webhooks.repository_import_short_desc %} 要在个人仓库中接收此事件，必须在导入之前创建一个空仓库。 This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports). #### 可用性 @@ -1237,9 +1237,9 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 #### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| ---- | ---- | ------------------------------------------------- | -| `团队` | `对象` | 被修改的[团队](/v3/teams/)。 **注：**较旧的事件可能不会在有效负载中包括此值。 | +| 键 | 类型 | 描述 | +| ---- | ---- | -------------------------------------------------------------------------------- | +| `团队` | `对象` | The [team](/rest/reference/teams) that was modified. **注：**较旧的事件可能不会在有效负载中包括此值。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1268,7 +1268,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.watch_short_desc %} -事件的执行者是标星仓库的[用户](/v3/users/)，并且事件的仓库是被标星的[仓库](/v3/repos/)。 +The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. #### 可用性 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-releases.md b/translations/zh-CN/content/github/administering-a-repository/about-releases.md index 48a5e64b85..c52945f514 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-releases.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-releases.md @@ -37,7 +37,7 @@ versions: 您可以查看依赖项图的 **Dependents（依赖项）**选项卡，了解哪些仓库和包依赖于您仓库中的代码，并因此可能受到新发行版的影响。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 {% endif %} -您也可以使用发行版 API 来收集信息，例如人们下载发行版资产的次数。 更多信息请参阅“[发行版](/v3/repos/releases/)”。 +您也可以使用发行版 API 来收集信息，例如人们下载发行版资产的次数。 更多信息请参阅“[发行版](/rest/reference/repos#releases)”。 {% if currentVersion == "free-pro-team@latest" %} ### 存储和带宽配额 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-required-status-checks.md b/translations/zh-CN/content/github/administering-a-repository/about-required-status-checks.md index fb56d49179..2130658b71 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-required-status-checks.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-required-status-checks.md @@ -36,7 +36,7 @@ versions: ### 必需状态检查故障排除 -如果您有名称相同的检查和状态，并且选择该名称作为必需状态检查，则检查和状态都是必需的。 更多信息请参阅“[检查](/v3/checks/)”。 +如果您有名称相同的检查和状态，并且选择该名称作为必需状态检查，则检查和状态都是必需的。 更多信息请参阅“[检查](/rest/reference/checks)”。 在设置必需状态检查后，您的分支在合并之前必须使用基本分支更新。 这可确保您的分支已经使用基本分支的最新代码做过测试。 如果您的分支过期，则需要将基本分支合并到您的分支。 @@ -62,7 +62,7 @@ remote: error: Required status check "ci-build" is failing {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -有时，测试合并提交与头部提交的状态检查结果存在冲突。 如果测试合并提交具有状态，则必须传递该状态。 否则，必须传递头部提交的状态后才可合并该分支。 有关合并提交的更多信息，请参阅“[拉取请求](/v3/pulls/#response-1)”。 +有时，测试合并提交与头部提交的状态检查结果存在冲突。 如果测试合并提交具有状态，则必须传递该状态。 否则，必须传递头部提交的状态后才可合并该分支。 有关合并提交的更多信息，请参阅“[拉取请求](/rest/reference/pulls#response-1)”。 ![具有冲突的合并提交的分支](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md index 87a37b7942..6d833ad48f 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,12 +15,15 @@ versions: github-ae: '*' --- +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} + ### 关于发行版管理 -您也可以在 {% data variables.product.prodname_marketplace %} 中从特定的发行版发布操作。 更多信息请参阅“在 {% data variables.product.prodname_marketplace %} 中发布操作”。 - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} +You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. 更多信息请参阅“在 {% data variables.product.prodname_marketplace %} 中发布操作”。 +{% endif %} 您可以选择是否 + 将 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在 {% data variables.product.product_name %} 为每个发行版创建的 ZIP 文件和 tarball 中。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 {% endif %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/zh-CN/content/github/authenticating-to-github/about-githubs-ip-addresses.md index 2d5a9f0225..50a2476579 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-githubs-ip-addresses.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -12,7 +12,7 @@ versions: free-pro-team: '*' --- -您可以从 [meta](https://api.github.com/meta) API 端点检索 {% data variables.product.prodname_dotcom %} 的 IP 地址列表。 更多信息请参阅“[元数据](/v3/meta/)”。 +您可以从 [meta](https://api.github.com/meta) API 端点检索 {% data variables.product.prodname_dotcom %} 的 IP 地址列表。 更多信息请参阅“[元数据](/rest/reference/meta)”。 这些范围在 [CIDR 表示法](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)中。 您可以使用在线转换工具（例如s这个 [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php)）将 CIDR 表示法转换为 IP 地址范围。 diff --git a/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md index 104ebd77a5..577a2157b4 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -12,7 +12,7 @@ versions: github-ae: '*' --- -在使用[GitHub API 或](/v3/auth/#via-oauth-and-personal-access-tokens)命令[行](#using-a-token-on-the-command-line)时，可使用个人访问令牌 (PAT) 代替密码向 {% data variables.product.product_name %} 进行身份验证。 +在使用[GitHub API 或](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)命令[行](#using-a-token-on-the-command-line)时，可使用个人访问令牌 (PAT) 代替密码向 {% data variables.product.product_name %} 进行身份验证。 {% if currentVersion == "free-pro-team@latest" %}如果要使用 PAT 访问使用 SAML SSO 的组织所拥有的资源，则必须授权 PAT。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/articles/about-authentication-with-saml-single-sign-on)”和“[授权个人访问令牌用于 SAML 单点登录](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”。{% endif %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md index 22e7da490a..58b2edc082 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md @@ -29,7 +29,7 @@ versions: _检查_与_状态_的不同之处在于它们提供行注解、更详细的信息，并且只适用于 {% data variables.product.prodname_github_app %}。 -组织所有者和能够推送到仓库的用户可使用 {% data variables.product.product_name %} 的 API 创建检查和状态。 更多信息请参阅“[检查](/v3/checks/)”和“[状态](/v3/repos/statuses/)”。 +组织所有者和能够推送到仓库的用户可使用 {% data variables.product.product_name %} 的 API 创建检查和状态。 更多信息请参阅“[检查](/rest/reference/checks)”和“[状态](/rest/reference/repos#statuses)”。 ### 检查 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index d7ac5179bc..c204e39ff7 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -11,7 +11,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -要下载仓库的存档，您可以使用 API 进行用户或组织迁移。 更多信息请参阅“[迁移](/v3/migrations/)”。 +要下载仓库的存档，您可以使用 API 进行用户或组织迁移。 更多信息请参阅“[迁移](/rest/reference/migrations)”。 {% else %} 您可以手动下载和备份仓库： @@ -21,15 +21,15 @@ versions: 克隆仓库或 wiki 时，仅下载 Git 数据，例如项目文件和提交历史记录。 您可以使用我们的 API 将 {% data variables.product.product_name %} 仓库的其他元素导出到您的本地计算机： -- [议题](/v3/issues/#list-issues-for-a-repository) -- [拉取请求](/v3/pulls/#list-pull-requests) +- [议题](/rest/reference/issues#list-issues-for-a-repository) +- [拉取请求](/rest/reference/pulls#list-pull-requests) - [复刻](/rest/reference/repos#list-forks) - [评论](/rest/reference/issues#list-issue-comments-for-a-repository) - [里程碑](/rest/reference/issues#list-milestones) - [标签](/rest/reference/issues#list-labels-for-a-repository) - [关注者](/rest/reference/activity#list-watchers) - [空想家](/rest/reference/activity#list-stargazers) -- [项目](/v3/projects/#list-repository-projects) +- [项目](/rest/reference/projects#list-repository-projects) {% endif %} 一旦您拥有 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}所有要备份内容的本地版本，您就可以创建一个 zip 存档并{% else %}下载您的存档。您可以{% endif %}将其复制到外部硬盘和/或将其上传到基于云的备份服务，例如 [Google Drive](https://www.google.com/drive/) 或 [Dropbox](https://www.dropbox.com/)。 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 9274ba154f..1a98d4c8ca 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ versions: ### 检测许可 -[开源 Ruby gem 被许可人](https://github.com/benbalter/licensee)比较仓库的 *LICENSE* 文件与已知许可短列表。 被许可人还提供[许可 API](/v3/licenses/) 并[向我们提供如何许可 {% data variables.product.product_name %} 上的仓库的洞见](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 如果您的仓库使用的许可未列在[选择许可网站](http://choosealicense.com/appendix/)中，您可以[申请包含该许可](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)。 +[开源 Ruby gem 被许可人](https://github.com/benbalter/licensee)比较仓库的 *LICENSE* 文件与已知许可短列表。 被许可人还提供[许可 API](/rest/reference/licenses) 并[向我们提供如何许可 {% data variables.product.product_name %} 上的仓库的洞见](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 如果您的仓库使用的许可未列在[选择许可网站](http://choosealicense.com/appendix/)中，您可以[申请包含该许可](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)。 如果您的仓库使用的许可列在“选择许可”网站中，但未明确显示在仓库页面顶部，其中可能包含多个许可或存在其他复杂性。 为使您的许可被检测到，请简化*许可*文件，并在其他位置注明复杂性，例如在仓库的*自述文件*中。 diff --git a/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md index 15dacb45ee..dce7f2aa15 100644 --- a/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -43,4 +43,4 @@ versions: ### 延伸阅读 -- "[授权 OAuth 应用程序](/v3/oauth/)" +- "[授权 OAuth 应用程序](/developers/apps/authorizing-oauth-apps)" diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index 572ca132eb..f929ac5fc4 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ versions: 如果 {% data variables.product.prodname_code_scanning %} 发现您的代码中可能存在漏洞或错误，{% data variables.product.prodname_dotcom %} 会在仓库中显示警报。 在修复触发警报的代码之后，{% data variables.product.prodname_dotcom %} 将关闭警报。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 -{% data variables.product.prodname_code_scanning_capc %} 使用 {% data variables.product.prodname_actions %}。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。 +{% data variables.product.prodname_code_scanning_capc %} 使用 {% data variables.product.prodname_actions %}。 For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." 要开始 {% data variables.product.prodname_code_scanning %}，请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 0cc08d5b3c..878369e4a0 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -52,6 +52,32 @@ The default {% data variables.product.prodname_codeql_workflow %} uses the `pull For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +#### Avoiding unnecessary scans of pull requests + +You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. + +``` yaml +on: + push: + branches: [main, protected] + pull_request: + branches: [main] + paths-ignore: + - '**/*.md' + - '**/*.txt' +``` + +{% note %} + +**Notes** + +* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." +* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. + +{% endnote %} + +For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." + #### Scanning on a schedule If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." @@ -235,13 +261,13 @@ If you only want to run custom queries, you can disable the default security que #### Specifying directories to scan -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from scans by adding a `paths-ignore` array. +For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. ``` yaml -paths: +paths: - src paths-ignore: - - node_modules + - src/node_modules - '**/*.test.js' ``` @@ -254,7 +280,7 @@ paths-ignore: {% endnote %} -For C/C++, C#, and Java, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index 0372f1e184..0f50e7d215 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -41,7 +41,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie {% endtip %} {% endif %} -许多人忘记了他们过去选择关注的仓库。 从“Watched repositories（已关注仓库）”页面，您可以快速取消关注仓库。 For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage worflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +许多人忘记了他们过去选择关注的仓库。 从“Watched repositories（已关注仓库）”页面，您可以快速取消关注仓库。 For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### 查看所有订阅 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/index.md b/translations/zh-CN/content/github/managing-your-work-on-github/index.md index 191d31de43..e1a17afdf5 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/index.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/index.md @@ -14,7 +14,7 @@ versions: ### 目录 -{% topic_link_in_list /managing-your-work-with-issues %} +{% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} @@ -27,6 +27,7 @@ versions: {% link_in_list /pinning-an-issue-to-your-repository %} {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} + {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} {% link_in_list /about-automation-for-issues-and-pull-requests-with-query-parameters %} {% link_in_list /file-attachments-on-issues-and-pull-requests %} @@ -35,12 +36,6 @@ versions: {% link_in_list /disabling-issues %} {% link_in_list /linking-a-pull-request-to-an-issue %} {% link_in_list /about-duplicate-issues-and-pull-requests %} -{% topic_link_in_list /labeling-issues-and-pull-requests %} - {% link_in_list /about-labels %} - {% link_in_list /creating-a-label %} - {% link_in_list /applying-labels-to-issues-and-pull-requests %} - {% link_in_list /editing-a-label %} - {% link_in_list /deleting-a-label %} {% topic_link_in_list /managing-project-boards %} {% link_in_list /about-project-boards %} {% link_in_list /creating-a-project-board %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md b/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md new file mode 100644 index 0000000000..c4c2ab9de1 --- /dev/null +++ b/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md @@ -0,0 +1,97 @@ +--- +title: Managing labels +intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +redirect_from: + - /articles/managing-Labels + - /articles/labeling-issues-and-pull-requests + - /github/managing-your-work-on-github/labeling-issues-and-pull-requests + - /articles/about-labels + - /github/managing-your-work-on-github/about-labels + - /articles/creating-and-editing-labels-for-issues-and-pull-requests + - /articles/creating-a-label + - /github/managing-your-work-on-github/creating-a-label + - /articles/customizing-issue-labels/ + - /articles/applying-labels-to-issues-and-pull-requests + - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests + - /articles/editing-a-label + - /github/managing-your-work-on-github/editing-a-label + - /articles/deleting-a-label + - /github/managing-your-work-on-github/deleting-a-label +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### 关于标签 + +您可以创建标签对议题和拉取请求分类，以管理您在 {% data variables.product.product_name %} 上的工作。 You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. + +对仓库具有读取权限的任何人都能查看和搜索仓库的标签。 要创建、编辑、应用或删除标签，必须对仓库具有写入权限。 + +### About default labels + +{% data variables.product.product_name %} 在每个新仓库中提供默认标签。 You can use these default labels to help create a standard workflow in a repository. + +| 标签 | 描述 | +| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `文档` | 表示文档需要改进或补充{% endif %} +| `duplicate` | 表示类似的议题或拉取请求 | +| `enhancement` | 表示新功能申请 | +| `good first issue` | 表示适用首次贡献者的议题 | +| `help wanted` | 表示维护员需要议题或拉取请求方面的帮助 | +| `invalid` | 表示议题或拉取请求不再相关 | +| `question` | 表示议题或拉取请求需要更多信息 | +| `wontfix` | 表示不会继续处理议题或拉取请求 | + +创建仓库时，每个新仓库中均包含默认标签，但您稍后可以编辑或删除标签。 + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +组织所有者可以自定义其组织中仓库的默认标签。 更多信息请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”。 +{% endif %} + +### 创建标签 + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. 在搜索字段的右侧，单击 **New label（新建标签）**。 +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### 应用标签到议题和拉取请求 + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. 在右上角单击 **Label（标签）**，然后开始输入现有标签的名称。 单击标签名称以将其与所选项目关联。 ![议题里程碑分配下拉菜单](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### 编辑标签 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### 删除标签 +Deleting a label will remove the label from issues and pull requests. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.delete-label %} + +### 延伸阅读 +- "[关于标签](/articles/about-labels)" +- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md new file mode 100644 index 0000000000..c9f3017c71 --- /dev/null +++ b/translations/zh-CN/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Managing your work with issues and pull requests +intro: '您可以创建议题来跟踪想法、增强、任务或漏洞，以管理您在 {% data variables.product.product_name %} 上的工作。' +mapTopic: true +redirect_from: + - /github/managing-your-work-on-github/managing-your-work-with-issues + - /articles/managing-your-work-with-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 91f818b77b..3dc814a4cb 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -163,7 +163,7 @@ You can filter by the visibility of the repository containing the issues and pul ### 按提交状态搜索 -您可以基于提交的状态过滤拉取请求。 这在使用 [Status API](/v3/repos/statuses/) 或 CI 服务时特别有用。 +您可以基于提交的状态过滤拉取请求。 这在使用 [Status API](/rest/reference/repos#statuses) 或 CI 服务时特别有用。 | 限定符 | 示例 | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 890ff2f1f7..20b6f904ad 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -40,7 +40,7 @@ versions: ### 使用 SAML SSO 添加成员到组织 -在启用 SAML SSO 后，可通过多种方式向组织添加新成员。 组织所有者可在 {% data variables.product.product_name %} 上或使用 API 手动邀请新成员。 更多信息请参阅“[邀请用户加入组织](/articles/inviting-users-to-join-your-organization)”和“[成员](/v3/orgs/members/#add-or-update-organization-membership)”。 +在启用 SAML SSO 后，可通过多种方式向组织添加新成员。 组织所有者可在 {% data variables.product.product_name %} 上或使用 API 手动邀请新成员。 更多信息请参阅“[邀请用户加入组织](/articles/inviting-users-to-join-your-organization)”和“[成员](/rest/reference/orgs#add-or-update-organization-membership)”。 {% data reusables.organizations.team-synchronization %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index c2b7f59e22..65db75ec33 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -12,7 +12,7 @@ versions: 如果您使用 SAML SSO 而不实施 SCIM，将不能自动撤销配置。 当组织成员的会话在其访问权限从 IdP 删除后到期时，他们就会自动从组织中删除。 即使会话已到期，通过授权的令牌也可授予对组织的访问。 要删除访问权限，组织管理员可以手动从组织删除授权的令牌，或者通过 SCIM 自动执行删除。 -这些身份提供程序兼容组织的 {% data variables.product.product_name %} SCIM API。 更多信息请参阅 {% data variables.product.product_name %} API 文档中的 [SCIM](/v3/scim/)。 +这些身份提供程序兼容组织的 {% data variables.product.product_name %} SCIM API。 更多信息请参阅 {% data variables.product.product_name %} API 文档中的 [SCIM](/rest/reference/scim)。 - Azure AD - Okta - OneLogin diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 68114d16da..1d1b15004b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -59,6 +59,7 @@ versions: | 编辑 wiki | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} | [举报滥用或垃圾内容](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} | 应用标签 | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | | 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** | | 应用里程碑 | | **X** | **X** | **X** | **X** | | 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 55a9b47450..b7b953ccf1 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -23,7 +23,7 @@ versions: 要管理 {% data variables.product.prodname_dotcom %} 团队（包括连接到 IdP 组的团队）的仓库访问权限，您必须使用 {% data variables.product.product_name %} 进行更改。 更多信息请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)”。 -您还可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/v3/teams/team_sync/)”。 +您还可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。 ### 已同步团队成员的要求 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md index 25efdd44be..908d5acaa4 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -26,7 +26,7 @@ versions: For more information about member access and management, see "{% if currentVersion == "free-pro-team@latest" %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}." -有关使用 GraphQL API 管理企业帐户的信息，请参阅“[企业帐户](/v4/guides/managing-enterprise-accounts)”。 +有关使用 GraphQL API 管理企业帐户的信息，请参阅“[企业帐户](/graphql/guides/managing-enterprise-accounts)”。 {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 49a1c62602..30f6c04c71 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -10,7 +10,7 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} -3. 在左侧边栏中，单击 **{% data variables.product.prodname_oauth_app %}**。 ![左侧边栏中的 { site.data.variables.product.prodname_oauth_app }} 选项卡](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. 在左侧边栏中，单击 **{% data variables.product.prodname_oauth_app %}**。 ![{% data variables.product.prodname_oauth_app %}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) 3. 单击 **Register a new application（注册新应用程序）**。 4. 在 **Application name（应用程序名称）**下输入 "Jira"。 5. 在 **Homepage URL（主页 URL）**下，输入 Jira 实例的完整 URL。 diff --git a/translations/zh-CN/content/github/site-policy/github-privacy-statement.md b/translations/zh-CN/content/github/site-policy/github-privacy-statement.md index 2546db1601..05337c081e 100644 --- a/translations/zh-CN/content/github/site-policy/github-privacy-statement.md +++ b/translations/zh-CN/content/github/site-policy/github-privacy-statement.md @@ -201,7 +201,7 @@ If you would like to compile GitHub data, you must comply with our Terms of Serv #### 第三方应用程序 -您可以选择在自己的帐户中启用或添加第三方应用程序（称为“开发者产品”）。 这些开发者产品并非使用 GitHub 的必要条件。 我们会在您要求时（例如从 Marketplace 购买开发者产品）将您的用户个人信息分享给第三方；但是，对于您使用第三方开发者产品以及您选择与之分享的用户个人信息，您自行负责。 您可以查看我们的 [API 文档](/v3/users/)，以了解您使用自己的 GitHub 个人资料向开发者产品验证时会提供哪些信息。 +您可以选择在自己的帐户中启用或添加第三方应用程序（称为“开发者产品”）。 这些开发者产品并非使用 GitHub 的必要条件。 我们会在您要求时（例如从 Marketplace 购买开发者产品）将您的用户个人信息分享给第三方；但是，对于您使用第三方开发者产品以及您选择与之分享的用户个人信息，您自行负责。 您可以查看我们的 [API 文档](/rest/reference/users)，以了解您使用自己的 GitHub 个人资料向开发者产品验证时会提供哪些信息。 #### GitHub Pages diff --git a/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index 7fed60b717..98ab7d3d46 100644 --- a/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -28,7 +28,7 @@ CCPA 为加州居民提供关于其个人信息的某些权利。 要提交基 加州居民有权要求企业披露：在过去 12 个月内从他们那里收集的个人信息的类别和具体部分；此类个人信息收集来源的类别；收集或出售此类个人信息的业务或商业目的；以及企业与其分享个人信息的第三方类别。 -如果您要求企业披露所收集的有关您的个人信息类别和具体部分，您有权每年两次免费接收该披露信息。 该信息可通过邮寄或电子方式传递，如果以电子方式提供，应采用可移植且易于使用的格式（在技术上可行的范围内），以便加州居民能够相对容易地将该信息传输给其他实体。 您可以使用 GitHub 的[用户迁移 API](/v3/migrations/users/) 来访问和下载您的数据。 单击[此处](https://github.blog/2018-12-19-download-your-data/)了解更多信息。 +如果您要求企业披露所收集的有关您的个人信息类别和具体部分，您有权每年两次免费接收该披露信息。 该信息可通过邮寄或电子方式传递，如果以电子方式提供，应采用可移植且易于使用的格式（在技术上可行的范围内），以便加州居民能够相对容易地将该信息传输给其他实体。 You can use GitHub’s [User Migration API](/rest/reference/migrations#users) to access and download your data. 单击[此处](https://github.blog/2018-12-19-download-your-data/)了解更多信息。 ### 2. 了解您的个人信息是否出于商业目的而出售或披露以及接收方是谁的权利 diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index 00145331b0..09c1271145 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -54,8 +54,6 @@ versions: {% data reusables.sponsors.double-check-stripe-info %} -如果您居住在不受支持的区域，并且被接受参加 {% data variables.product.prodname_sponsors %} 公测，您将收到一封电子邮件，其中说明如何提供银行信息，以便您可以通过 ACH 转账或电汇接收付款。 - {% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} diff --git a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md index 4af041149b..233e45b218 100644 --- a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md +++ b/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md @@ -10,7 +10,7 @@ versions: {% data variables.product.product_name %} 存储您个人帐户活动的仓库和个人资料元数据。 您可以通过 {% data variables.product.prodname_dotcom_the_website %} 上的设置或使用用户迁移 API 导出个人帐户的数据。 -有关可供导出的数据 {% data variables.product.product_name %} 存储的更多信息，请参阅“[下载用户迁移存档](/v3/migrations/users/#download-a-user-migration-archive)”和“[关于 {% data variables.product.product_name %} 对数据的使用](/articles/about-github-s-use-of-your-data)”。 +有关可供导出的数据 {% data variables.product.product_name %} 存储的更多信息，请参阅“[下载用户迁移存档](/rest/reference/migrations#download-a-user-migration-archive)”和“[关于 {% data variables.product.product_name %} 对数据的使用](/articles/about-github-s-use-of-your-data)”。 当您通过 {% data variables.product.prodname_dotcom_the_website %} 上的设置请求导出个人数据时，{% data variables.product.product_name %} 会将您的个人数据打包到 `tar.gz` 文件中，并向您的主电子邮件地址发送含有下载链接的电子邮件。 diff --git a/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md b/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md index c198e77710..692e403766 100644 --- a/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md @@ -44,7 +44,7 @@ SSH URL 通过 SSH（一种安全协议）提供 Git 仓库的访问权限。 {% tip %} -**提示**：您可以使用 SSH URL 将仓库克隆到计算机，或作为将代码部署到生产服务器的安全方法。 您还可以将 SSH 代理转发与部署脚本一起使用，以避免管理服务器上的密钥。 更多信息请参阅“[使用 SSH 代理转发](/v3/guides/using-ssh-agent-forwarding/)”。 +**提示**：您可以使用 SSH URL 将仓库克隆到计算机，或作为将代码部署到生产服务器的安全方法。 您还可以将 SSH 代理转发与部署脚本一起使用，以避免管理服务器上的密钥。 更多信息请参阅“[使用 SSH 代理转发](/developers/overview/using-ssh-agent-forwarding)”。 {% endtip %} diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index 9f93d07cd5..765684457a 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -36,7 +36,7 @@ You can view the top 100 contributors to a repository{% if enterpriseServerVersi {% tip %} -**提示：**要列出仓库中的所有提交贡献者，请参阅“[仓库](/v3/repos/#list-contributors)”。 +**提示：**要列出仓库中的所有提交贡献者，请参阅“[仓库](/rest/reference/repos#list-contributors)”。 {% endtip %} diff --git a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md index a57af3ecbe..b40c4142d9 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md @@ -150,4 +150,4 @@ MIME 类型是服务器发送到浏览器的标头，提供有关浏览器所请 ### 延伸阅读 - {% data variables.product.prodname_learning %} 上的 [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) -- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)" +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index e1324380be..ce355ff29c 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -16,7 +16,7 @@ versions: Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} - 推送更改的人尚未验证他们的电子邮件地址。 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。{% endif %} -- 您使用部署密钥推送。 如果要自动推送到站点的仓库，您可以改为设置计算机用户。 更多信息请参阅“[管理部署密钥](/v3/guides/managing-deploy-keys/#machine-users)”。 +- 您使用部署密钥推送。 如果要自动推送到站点的仓库，您可以改为设置计算机用户。 更多信息请参阅“[管理部署密钥](/developers/overview/managing-deploy-keys#machine-users)”。 - 您使用的是未配置为构建发布源的 CI 服务。 例如，Travis CI 不会构建 `gh-pages` 分支，除非您将该分支添加到安全列表。 更多信息请参阅 Travis CI 上的“[定制构建](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)”或者 CI 服务的文档。 {% note %} diff --git a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md index cdd6a18157..323b7488f8 100644 --- a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md @@ -18,7 +18,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -要匹配 [GraphQL Explorer](/v4/guides/using-the-explorer) 的行为，需请求以下作用域： +要匹配 [GraphQL Explorer](/graphql/guides/using-the-explorer) 的行为，需请求以下作用域： {% else %} @@ -50,9 +50,9 @@ REST API 有多个端点；GraphQL API 只有一个端点： ### 与 GraphQL 通信 -由于 GraphQL 操作由多行 JSON 组成，因此 GitHub 建议使用 [Explorer](/v4/guides/using-the-explorer) 进行 GraphQL 调用。 也可以使用 cURL 或任何其他采用 HTTP 的库。 +由于 GraphQL 操作由多行 JSON 组成，因此 GitHub 建议使用 [Explorer](/graphql/guides/using-the-explorer) 进行 GraphQL 调用。 也可以使用 cURL 或任何其他采用 HTTP 的库。 -在 REST 中，[HTTP 请求方法](/v3/#http-verbs)确定执行的操作。 在 GraphQL 中，无论是执行查询还是突变，都要提供 JSON 编码的正文，因此 HTTP 请求方法是 `POST`。 唯一的例外是[内省查询](/v4/guides/intro-to-graphql#discovering-the-graphql-api)，它是一种简单的 `GET` 到端点查询。 有关 GraphQL 与 REST 的更多信息，请参阅“[从 REST 迁移到 GraphQL](/v4/guides/migrating-from-rest)”。 +在 REST 中，[HTTP 请求方法](/rest#http-verbs)确定执行的操作。 在 GraphQL 中，无论是执行查询还是突变，都要提供 JSON 编码的正文，因此 HTTP 请求方法是 `POST`。 唯一的例外是[内省查询](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)，它是一种简单的 `GET` 到端点查询。 有关 GraphQL 与 REST 的更多信息，请参阅“[从 REST 迁移到 GraphQL](/graphql/guides/migrating-from-rest-to-graphql)”。 要使用 cURL 查询 GraphQL，请利用 JSON 有效负载提出 `POST` 请求。 有效负载必须包含一个名为 `query` 的字符串： @@ -72,15 +72,15 @@ curl -H "Authorization: bearer token" -X POST -d " \ #### 关于查询和突变操作 -GitHub 的 GraphQL API 中允许的两种操作类型为_查询_和_突变_。 比较 GraphQL 与 REST，查询操作就像 `GET` 请求，而突变操作则像 `POST`/`PATCH`/`DELETE`。 [突变名称](/v4/mutation/)确定执行哪些修改。 +GitHub 的 GraphQL API 中允许的两种操作类型为_查询_和_突变_。 比较 GraphQL 与 REST，查询操作就像 `GET` 请求，而突变操作则像 `POST`/`PATCH`/`DELETE`。 [突变名称](/graphql/reference/mutations)确定执行哪些修改。 -有关速率限制的信息，请参阅“[GraphQL 资源限制](/v4/guides/resource-limitations/)”。 +有关速率限制的信息，请参阅“[GraphQL 资源限制](/graphql/overview/resource-limitations)”。 查询和突变形式相似，但有一些重要差异。 #### 关于查询 -GraphQL 查询仅返回您指定的数据。 要建立查询，必须指定[字段内的字段](/v4/guides/intro-to-graphql#field)（也称为_嵌套的子字段_），直到仅返回[标量](/v4/scalar/)。 +GraphQL 查询仅返回您指定的数据。 要建立查询，必须指定[字段内的字段](/graphql/guides/introduction-to-graphql#field)（也称为_嵌套的子字段_），直到仅返回[标量](/graphql/reference/scalars)。 查询的结构如下： @@ -107,7 +107,7 @@ GraphQL 查询仅返回您指定的数据。 要建立查询，必须指定[字 本示例中的输入对象为 `MutationNameInput`，有效负载对象为 `MutationNamePayload`。 -在引用的[突变](/v4/mutation/)中，列出的_输入字段_即是作为输入对象传递的内容。 列出的_返回字段_即是作为有效负载对象传递的内容。 +在引用的[突变](/graphql/reference/mutations)中，列出的_输入字段_即是作为输入对象传递的内容。 列出的_返回字段_即是作为有效负载对象传递的内容。 有关真实示例，请参阅“[突变示例](#example-mutation)”。 @@ -117,7 +117,7 @@ GraphQL 查询仅返回您指定的数据。 要建立查询，必须指定[字 {% note %} -**注**：如果使用的是 Explorer，请确保在单独的[查询变量窗格](/v4/guides/using-the-explorer/#using-the-variable-pane)中输入变量，且 JSON 对象之前不含 `variables` 一词。 +**注**：如果使用的是 Explorer，请确保在单独的[查询变量窗格](/graphql/guides/using-the-explorer#using-the-variable-pane)中输入变量，且 JSON 对象之前不含 `variables` 一词。 {% endnote %} @@ -207,7 +207,7 @@ query { * `repository(owner:"octocat", name:"Hello-World") {` - 要开始查询，我们需要查找 [`repository`](/v4/object/repository/) 对象。 架构验证指示此对象需要 `owner` 和 `name` 参数。 + 要开始查询，我们需要查找 [`repository`](/graphql/reference/objects#repository) 对象。 架构验证指示此对象需要 `owner` 和 `name` 参数。 * `issues(last:20, states:CLOSED) {` @@ -215,9 +215,9 @@ query { 关于 `issues` 对象的一些详细信息： - - [文档](/v4/object/repository/)告诉我们此对象的类型为 `IssueConnection`。 + - [文档](/graphql/reference/objects#repository)告诉我们此对象的类型为 `IssueConnection`。 - 架构验证表明此对象需要将 `last` 或 `first` 个结果作为参数，因此我们提供了 `20`。 - - [文档](/v4/object/repository/)还告诉我们此对象接受 `states` 参数，即一种 [`IssueState`](/v4/enum/issuestate/) 枚举类型，可接受的值为 `OPEN` 或 `CLOSED`。 要仅查找关闭状态的议题，我们对 `states` 键赋值 `CLOSED`。 + - [文档](/graphql/reference/objects#repository)还告诉我们此对象接受 `states` 参数，即一种 [`IssueState`](/graphql/reference/enums#issuestate) 枚举类型，可接受的值为 `OPEN` 或 `CLOSED`。 要仅查找关闭状态的议题，我们对 `states` 键赋值 `CLOSED`。 * `edges {` @@ -225,9 +225,9 @@ query { * `node {` - 在本示例中，我们将检索边缘末尾的节点。 [`IssueConnection` 文档](/v4/object/issueconnection)指示 `IssueConnection` 类型末尾的节点为 `Issue` 对象。 + 在本示例中，我们将检索边缘末尾的节点。 [`IssueConnection` 文档](/graphql/reference/objects#issueconnection)指示 `IssueConnection` 类型末尾的节点为 `Issue` 对象。 -* 我们已经知道要检索 `Issue` 对象，现在可以查看[文档](/v4/object/issue)并指定要返回的字段了： +* 我们已经知道要检索 `Issue` 对象，现在可以查看[文档](/graphql/reference/objects#issue)并指定要返回的字段了： ```graphql title @@ -243,7 +243,7 @@ query { 我们在此指定 `Issue` 对象的 `title`、`url` 和 `labels` 字段。 - `labels` 字段的类型为 [`LabelConnection`](/v4/object/labelconnection/)。 与 `issues` 对象一样，`labels` 也是一种连接，因此我们必须将其边缘传送至连接的节点：`label` 对象。 在此节点上，我们可以指定要返回的 `label` 对象字段，在本例中为 `name`。 + `labels` 字段的类型为 [`LabelConnection`](/graphql/reference/objects#labelconnection)。 与 `issues` 对象一样，`labels` 也是一种连接，因此我们必须将其边缘传送至连接的节点：`label` 对象。 在此节点上，我们可以指定要返回的 `label` 对象字段，在本例中为 `name`。 您可能会注意到，在 Octocat 的公共 `Hello-World` 仓库中运行此查询不会返回很多标签。 尝试在您自己的其中一个使用标签的仓库中运行，很可能会看到不同的结果。 @@ -285,7 +285,7 @@ mutation AddReactionToIssue { 那么，我们怎么知道从查询开始呢？ 还不知道。 -因为我们想修改服务器上的数据（向议题添加表情符号），所以先搜索架构，查找有用的突变。 参考文档所示为 [`addReaction`](/v4/mutation/addreaction) 突变，其描述为：`Adds a reaction to a subject.` Perfect! +因为我们想修改服务器上的数据（向议题添加表情符号），所以先搜索架构，查找有用的突变。 参考文档所示为 [`addReaction`](/graphql/reference/mutations#addreaction) 突变，其描述为：`Adds a reaction to a subject.` Perfect! 突变文档列出了三个输入字段： @@ -337,13 +337,13 @@ mutation AddReactionToIssue { - `addReaction` 是突变的名称。 - `input` 是必需的参数键。 突变的参数键始终是 `input`。 - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` 是必需的参数值。 突变的参数值始终是由输入字段（在本例中为 `subjectId` 和 `content`）组成的[输入对象](/v4/input_object/)（因此带有大括号）。 + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` 是必需的参数值。 突变的参数值始终是由输入字段（在本例中为 `subjectId` 和 `content`）组成的[输入对象](/graphql/reference/input-objects)（因此带有大括号）。 - 我们怎么知道内容使用哪个值呢？ [`addReaction` 文档](/v4/mutation/addreaction/)告诉我们 `content` 字段的类型为 [`ReactionContent`](/v4/enum/reactioncontent/)，即一种[枚举类型](/v4/enum)，因为 GitHub 议题只支持某些表情符号反应。 这些是允许的反应值 （注意，某些值与其相应的表情符号名称不同）： + 我们怎么知道内容使用哪个值呢？ [`addReaction` 文档](/graphql/reference/mutations#addreaction)告诉我们 `content` 字段的类型为 [`ReactionContent`](/graphql/reference/enums#reactioncontent)，即一种[枚举类型](/graphql/reference/enums)，因为 GitHub 议题只支持某些表情符号反应。 这些是允许的反应值 （注意，某些值与其相应的表情符号名称不同）： {% data reusables.repositories.reaction_list %} -* 调用的其余部分由有效负载对象组成。 我们将在此指定执行突变后由服务器返回的数据。 这几行来自 [`addReaction` 文档](/v4/mutation/addreaction)，其中包含三个可能返回的字段： +* 调用的其余部分由有效负载对象组成。 我们将在此指定执行突变后由服务器返回的数据。 这几行来自 [`addReaction` 文档](/graphql/reference/mutations#addreaction)，其中包含三个可能返回的字段： - `clientMutationId` (`String`) - `reaction` (`Reaction!`) @@ -394,7 +394,7 @@ variables { {% note %} 您可能会注意到，前文示例中的 `content` 字段值（直接用于突变）在 `HOORAY` 两侧没有引号，但在变量中使用时有引号。 原因是： -* 当您直接在突变中使用 `content` 时，架构预计此值的类型为 [`ReactionContent`](/v4/enum/reactioncontent/)，即一种_枚举类型_，而非字符串。 如果您在枚举值两侧添加引号，架构验证将出现错误，因为引号是为字符串保留的。 +* 当您直接在突变中使用 `content` 时，架构预计此值的类型为 [`ReactionContent`](/graphql/reference/enums#reactioncontent)，即一种_枚举类型_，而非字符串。 如果您在枚举值两侧添加引号，架构验证将出现错误，因为引号是为字符串保留的。 * 当您在变量中使用 `content` 时，变量部分必须为有效的 JSON，因此需要引号。 当变量在执行过程中传递至突变时，架构验证将正确解释 `ReactionContent` 类型。 有关枚举类型与字符串之间差异的更多信息，请参阅[官方 GraphQL 规格](https://graphql.github.io/graphql-spec/June2018/#sec-Enums)。 diff --git a/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md b/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md index f4cdb8d62c..f9653b6aa6 100644 --- a/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md +++ b/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md @@ -12,7 +12,7 @@ versions: ### GraphQL 术语 -GitHub GraphQL API 表示 GitHub REST API 发生的架构和概念转变。 您可能会在 GraphQL API [参考文档](/v4/)中遇到一些新术语。 +GitHub GraphQL API 表示 GitHub REST API 发生的架构和概念转变。 您可能会在 GraphQL API [参考文档](/graphql)中遇到一些新术语。 ### 架构 @@ -30,11 +30,11 @@ GitHub GraphQL API 表示 GitHub REST API 发生的架构和概念转变。 您 ### 参数 -参数是指一组附加至特定字段的键值对。 某些字段需要参数。 [突变](/v4/guides/forming-calls#about-mutations)需要将输入对象作为参数。 +参数是指一组附加至特定字段的键值对。 某些字段需要参数。 [突变](/graphql/guides/forming-calls-with-graphql#about-mutations)需要将输入对象作为参数。 ### 实现 -GraphQL 架构可以使用术语_实现_定义对象如何继承[接口](/v4/interface)。 +GraphQL 架构可以使用术语_实现_定义对象如何继承[接口](/graphql/reference/interfaces)。 下面是定义接口 `X` 和对象 `Y` 的设定架构示例： @@ -55,13 +55,13 @@ type Y implements X { 在参考文档中，您将发现： -* 每个[对象](/v4/object)都会在 **Implements（实现）**下列出它_继承的_ 接口。 +* 每个[对象](/graphql/reference/objects)都会在 **Implements（实现）**下列出它_继承的_ 接口。 -* 每个[接口](/v4/interface)都会在 **Implementations（实现）**下列出它_继承的_对象。 +* 每个[接口](/graphql/reference/interfaces)都会在 **Implementations（实现）**下列出它_继承的_对象。 ### 连接 -连接可用于查询作为同一个调用的一部分的相关对象。 通过连接，可以使用单个 GraphQL 调用，其中，必须对 REST API 使用多个调用。 更多信息请参阅“[从 REST 迁移到 GraphQL](/v4/guides/migrating-from-rest)。” +连接可用于查询作为同一个调用的一部分的相关对象。 通过连接，可以使用单个 GraphQL 调用，其中，必须对 REST API 使用多个调用。 更多信息请参阅“[从 REST 迁移到 GraphQL](/graphql/guides/migrating-from-rest-to-graphql)。” 它有助于绘制图形：用线连接点。 点是节点，线是边缘。 连接可定义节点之间的关系。 @@ -71,7 +71,7 @@ type Y implements X { ### Node -_节点_是对象的通用术语。 您可以直接查找节点，或通过连接访问相关节点。 如果您指定的 `node` 不能返回[标量](/v4/scalar)，则必须包含子字段，直到所有字段都返回标量。 有关通过 REST API 访问节点 ID 和将它们用于 GraphQL 查询的信息，请参阅“[使用全局节点 ID](/v4/guides/using-global-node-ids)。” +_节点_是对象的通用术语。 您可以直接查找节点，或通过连接访问相关节点。 如果您指定的 `node` 不能返回[标量](/graphql/reference/scalars)，则必须包含子字段，直到所有字段都返回标量。 有关通过 REST API 访问节点 ID 和将它们用于 GraphQL 查询的信息，请参阅“[使用全局节点 ID](/graphql/guides/using-global-node-ids)。” ## 了解 GraphQL API @@ -130,4 +130,4 @@ query { {% endnote %} - 有关执行查询的更多信息，请参阅“[使用 GraphQL 建立调用](/v4/guides/forming-calls)。” + 有关执行查询的更多信息，请参阅“[使用 GraphQL 建立调用](/graphql/guides/forming-calls-with-graphql)。” diff --git a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md index ac282cebc8..762c86f4c5 100644 --- a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md @@ -33,7 +33,7 @@ GraphQL 可用于仅请求和返回您指定的数据。 例如，您可以创 - 邀请管理员加入您的企业帐户。 - 在企业帐户中创建新组织。 -有关通过企业帐户 API 获得的字段列表，请参阅“[企业帐户 API 的 GraphQL 字段和类型](/v4/guides/managing-enterprise-accounts/#graphql-fields-and-types-for-the-enterprise-accounts-api)。” +有关通过企业帐户 API 获得的字段列表，请参阅“[企业帐户 API 的 GraphQL 字段和类型](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)。” ### 开始将 GraphQL 用于企业帐户 @@ -197,12 +197,12 @@ fragment repositories on Organization { } ``` -有关开始使用 GraphQL 的更多信息，请参阅“[GraphQL 简介](/v4/guides/intro-to-graphql/)”和“[使用 GraphQL 建立调用](/v4/guides/forming-calls/)。” +有关开始使用 GraphQL 的更多信息，请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql)”和“[使用 GraphQL 建立调用](/graphql/guides/forming-calls-with-graphql)。” ### 企业账户 API 的 GraphQL 字段和类型 下面是关于可与企业账户 API 结合使用的新查询、突变和架构定义类型的概述。 -有关可与企业账户 API 结合使用的新查询、突变和架构定义类型的详细信息，请参阅任何 [GraphQL 参考页面](/v4/)含有详细 GraphQL 定义的边栏。 +有关可与企业账户 API 结合使用的新查询、突变和架构定义类型的详细信息，请参阅任何 [GraphQL 参考页面](/graphql)含有详细 GraphQL 定义的边栏。 -您可以从 GitHub 的 GraphQL explorer 访问参考文档。 更多信息请参阅“[使用 explorer](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)。” 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/v4/guides)。 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/v4/guides)。 +您可以从 GitHub 的 GraphQL explorer 访问参考文档。 更多信息请参阅“[使用 explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)。” 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/v4/guides)。 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/graphql/guides)。 diff --git a/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md index 142eae4d55..e9305fbb73 100644 --- a/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: 从 REST 迁移到 GraphQL 代表了 API 逻辑的一次重大转变。 作为样式的 REST 与作为规范的 GraphQL 之间的差异使得很难—且通常不可取—以一对一方式将 REST API 调用替换为 GraphQL API 查询。 我们在下面提供了具体的迁移示例。 -要将代码从 [REST API](/v3) 迁移到 GraphQL API： +To migrate your code from the [REST API](/rest) to the GraphQL API: - 查看 [GraphQL 规范](https://graphql.github.io/graphql-spec/June2018/) -- 查看 GitHub 的 [GraphQL 架构](/v4/reference/) +- Review GitHub's [GraphQL schema](/graphql/reference) - 考虑您当前的现有代码如何与 GitHub REST API 交互 -- 使用[全局节点 ID](/v4/guides/using-global-node-ids) 引用 API 版本之间的对象 +- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions GraphQL 的重要优势包括： @@ -53,12 +53,12 @@ query { } ``` -考虑另一个示例：检索拉取请求列表并检查每个请求是否可合并。 对 REST API 的调用可检索拉取请求列表及其[摘要陈述](/v3/#summary-representations)： +考虑另一个示例：检索拉取请求列表并检查每个请求是否可合并。 A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -确定拉取请求是否可合并需要分别检索每个拉取请求，查看其[详细陈述](/v3/#detailed-representations)（大型有效负载），并检查它的 `mergeable` 属性是真还是假： +Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:numbe } ``` -您也可以通过[用变量替换](/v4/guides/forming-calls/#working-with-variables)拉取请求编号扩大此查询的能力。 +You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. ## 示例：强类型化 GraphQL 架构属于强类型化架构，可使数据处理更加安全。 -考虑一个利用 GraphQL [突变](/v4/mutation)向议题或拉取请求添加注释，并错误地将 [`clientMutationId`](/v4/mutation/addcomment/) 值指定为整数而非字符串的示例： +Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): ```graphql mutation { diff --git a/translations/zh-CN/content/graphql/guides/using-global-node-ids.md b/translations/zh-CN/content/graphql/guides/using-global-node-ids.md index 71a3ce275c..f62c178e2c 100644 --- a/translations/zh-CN/content/graphql/guides/using-global-node-ids.md +++ b/translations/zh-CN/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ versions: {% note %} -**注：**在 REST 中，全局节点 ID 字段被命名为 `node_id`。 在 GraphQL 中，此字段为 `node` 接口上的 `id` 字段。 若要重温“节点”在 GraphQL 中的含义，请参阅“[GraphQL 简介](/v4/guides/intro-to-graphql/#node)。” +**注：**在 REST 中，全局节点 ID 字段被命名为 `node_id`。 在 GraphQL 中，此字段为 `node` 接口上的 `id` 字段。 For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." {% endnote %} @@ -29,7 +29,7 @@ versions: ### 1. 调用可返回对象节点 ID 的 REST 端点 -如果您[请求经过身份验证的用户](/v3/users/#get-the-authenticated-user)： +If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { 此查询类型—即按 ID 查找节点—被称为“直接节点查找。” -当您运行此查询时，将发现 `__typename` 为 [`User`](/v4/object/user/)。 +When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). ### 3. 在 GraphQL 中执行直接节点查找 @@ -122,4 +122,4 @@ query { ### 在迁移中使用全局节点 ID -构建使用 REST API 或 GraphQL API 的集成时，最佳做法是保留全局节点 ID，以便轻松引用不同 API 版本的对象。 有关处理 REST 与 GraphQL 之间的转换的更多信息，请参阅“[从 REST 迁移到 GraphQL](/v4/guides/migrating-from-rest/)。” +构建使用 REST API 或 GraphQL API 的集成时，最佳做法是保留全局节点 ID，以便轻松引用不同 API 版本的对象。 For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." diff --git a/translations/zh-CN/content/graphql/guides/using-the-explorer.md b/translations/zh-CN/content/graphql/guides/using-the-explorer.md index 35166fe7f9..59fa2d25f9 100644 --- a/translations/zh-CN/content/graphql/guides/using-the-explorer.md +++ b/translations/zh-CN/content/graphql/guides/using-the-explorer.md @@ -13,11 +13,11 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -[GraphQL Explorer](/v4/explorer) 是 [GraphiQL](https://github.com/graphql/graphiql) -“浏览器内的图形交互式 GraphQL IDE”- 的实例。 +[GraphQL Explorer](/graphql/overview/explorer) 是 [GraphiQL](https://github.com/graphql/graphiql) -“浏览器内的图形交互式 GraphQL IDE”- 的实例。 {% note %} -**注**：{% data variables.product.prodname_dotcom %} 在 Explorer 中禁用[突变](/v4/mutation/)，但您在自己的 GraphiQL 实例中可以使用它们。 +**注**：{% data variables.product.prodname_dotcom %} 在 Explorer 中禁用[突变](/graphql/reference/mutations)，但您在自己的 GraphiQL 实例中可以使用它们。 {% endnote %} @@ -33,7 +33,7 @@ versions: #### 配置 GraphiQL -1. 获取 [OAuth 令牌](/v4/guides/forming-calls#authenticating-with-graphql)。 +1. 获取 [OAuth 令牌](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql)。 1. 启动 GraphiQL。 1. 在 GraphiQL 的右上角，单击 **Edit HTTP Headers（编辑 HTTP 标头）**。 1. 在 **Key（密钥）**字段中，输入 `Authorization`。 在 **Value（值）**字段中，输入 `Bearer `，其中 `` 是您生成的 OAuth 令牌。 ![graphiql 标头](/assets/images/developer/graphiql-headers.png) @@ -44,7 +44,7 @@ versions: {% note %} -**注**：有关为何选择 `POST` 作为方法的更多信息，请参阅“[与 GraphQL 通信](/v4/guides/forming-calls#communicating-with-graphql)”。 +**注**：有关为何选择 `POST` 作为方法的更多信息，请参阅“[与 GraphQL 通信](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)”。 {% endnote %} @@ -66,13 +66,13 @@ GraphQL 架构中的所有类型都包含一个编译到文档中的 `descriptio {% note %} -**Docs（文档）**边栏包含的内容，与“[引用](/v4/)”下的架构自动生成的内容相同，但有些地方的格式不同。 +**Docs（文档）**边栏包含的内容，与“[引用](/graphql)”下的架构自动生成的内容相同，但有些地方的格式不同。 {% endnote %} ### 使用变量窗格 -包含[变量](/v4/guides/forming-calls#working-with-variables)的一些示例调用可能写作： +包含[变量](/graphql/guides/forming-calls-with-graphql#working-with-variables)的一些示例调用可能写作： ```graphql query($number_of_repos:Int!){ @@ -90,7 +90,7 @@ variables { } ``` -这是通过 cURL `POST` 提交调用的正确格式（但要[避免使用换行符](/v4/guides/forming-calls#communicating-with-graphql)）。 +这是通过 cURL `POST` 提交调用的正确格式（但要[避免使用换行符](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)）。 如果要在 Explorer 中运行调用，请在主窗格中输入 `query` 字段，并在其下方的 **Query Variables（查询变量）**窗格中输入变量。 在 Explorer 中省略 `variables` 一词： @@ -106,12 +106,12 @@ variables { ### 排查错误 -由于 GraphQL 可以[自省](/v4/guides/intro-to-graphql#discovering-the-graphql-api)，因此 Explorer 支持： +由于 GraphQL 可以[自省](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)，因此 Explorer 支持： * 基于当前架构的智能输入提示 * 键入时预提示验证错误 -如果您输入的查询格式不正确或未通过[架构验证](/v4/guides/intro-to-graphql#schema)，则会弹出错误警示窗口。 如果您运行查询，错误将返回响应窗格中。 +如果您输入的查询格式不正确或未通过[架构验证](/graphql/guides/introduction-to-graphql#schema)，则会弹出错误警示窗口。 如果您运行查询，错误将返回响应窗格中。 GraphQL 响应中包含多个密钥：`data` 哈希和 `errors` 数组。 diff --git a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md index 4f08eb9c1c..2d352f448f 100644 --- a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md +++ b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md @@ -11,25 +11,25 @@ versions: 下面是一些帮助您启动和运行 GraphQL API v4 的快速链接： -* [身份验证](/v4/guides/forming-calls/#authenticating-with-graphql) -* [根端点](/v4/guides/forming-calls/#the-graphql-endpoint) -* [架构内省](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) -* [速率限制](/v4/guides/resource-limitations/) -* [从 REST 迁移](/v4/guides/migrating-from-rest) +* [身份验证](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) +* [根端点](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) +* [架构内省](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) +* [速率限制](/graphql/overview/resource-limitations) +* [从 REST 迁移](/graphql/guides/migrating-from-rest-to-graphql) ### 关于 GraphQL [GraphQL](https://graphql.github.io/) 数据查询语言为： -* **[规范](https://graphql.github.io/graphql-spec/June2018/)。**此规范可确定 API 服务器上[架构](/v4/guides/intro-to-graphql#schema)的有效性。 架构可确定客户端调用的有效性。 +* **[规范](https://graphql.github.io/graphql-spec/June2018/)。**此规范可确定 API 服务器上[架构](/graphql/guides/introduction-to-graphql#schema)的有效性。 架构可确定客户端调用的有效性。 * **[强类型化](#about-the-graphql-schema-reference)。**架构可定义 API 的类型系统和所有对象关系。 -* **[内省](/v4/guides/intro-to-graphql#discovering-the-graphql-api)。**客户端可查询架构，了解关于架构的详细信息。 +* **[内省](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)。**客户端可查询架构，了解关于架构的详细信息。 -* **[层次](/v4/guides/forming-calls)。**GraphQL 调用的形式可反映它返回的 JSON 数据的形式。 [嵌套字段](/v4/guides/migrating-from-rest/#example-nesting)可用于仅查询和接收您在单个往返向行程中指定的数据。 +* **[层次](/graphql/guides/forming-calls-with-graphql)。**GraphQL 调用的形式可反映它返回的 JSON 数据的形式。 [嵌套字段](/graphql/guides/migrating-from-rest-to-graphql#example-nesting)可用于仅查询和接收您在单个往返向行程中指定的数据。 -* **应用层。**GraphQL 不是存储模型或数据库查询语言。 _graph_ 是指架构中定义的图形结构，其中，[节点](/v4/guides/intro-to-graphql#node)定义对象，[边缘](/v4/guides/intro-to-graphql#edge)定义对象之间的关系。 API 可以根据架构定义遍历和返回应用数据，与数据的存储方式无关。 +* **应用层。**GraphQL 不是存储模型或数据库查询语言。 _graph_ 是指架构中定义的图形结构，其中，[节点](/graphql/guides/introduction-to-graphql#node)定义对象，[边缘](/graphql/guides/introduction-to-graphql#edge)定义对象之间的关系。 API 可以根据架构定义遍历和返回应用数据，与数据的存储方式无关。 ### GitHub 为什么使用 GraphQL @@ -39,15 +39,15 @@ GitHub 选择将 GraphQL 用于 API v4，因为它可以为我们的集成商提 ### 关于 GraphQL 架构引用 -边栏中的文档是从 {% data variables.product.prodname_dotcom %} GraphQL [架构](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) 生成的。 所有调用均根据架构验证和执行。 使用这些文档查找您可以调用的数据： +边栏中的文档是从 {% data variables.product.prodname_dotcom %} GraphQL [架构](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) 生成的。 所有调用均根据架构验证和执行。 使用这些文档查找您可以调用的数据： -* 允许的操作：[查询](/v4/query)和[突变](/v4/mutation)。 +* 允许的操作：[查询](/graphql/reference/queries)和[突变](/graphql/reference/mutations)。 -* 架构定义的类型：[标量](/v4/scalar)、[对象](/v4/object)、[枚举类型](/v4/enum)、[接口](/v4/interface)、[并集](/v4/union)和[输入对象](/v4/input_object)。 +* 架构定义的类型：[标量](/graphql/reference/scalars)、[对象](/graphql/reference/objects)、[枚举类型](/graphql/reference/enums)、[接口](/graphql/reference/interfaces)、[并集](/graphql/reference/unions)和[输入对象](/graphql/reference/input-objects)。 -您可以通过 [Explorer 文档边栏](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)访问同样的内容。 请注意，您可能需要依靠文档和架构验证才能成功调用 GraphQL API。 +您可以通过 [Explorer 文档边栏](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)访问同样的内容。 请注意，您可能需要依靠文档和架构验证才能成功调用 GraphQL API。 -有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/v4/guides)。 +有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/graphql/guides)。 ### 请求支持 diff --git a/translations/zh-CN/content/graphql/overview/breaking-changes.md b/translations/zh-CN/content/graphql/overview/breaking-changes.md index 880cd7f140..796d03dd97 100644 --- a/translations/zh-CN/content/graphql/overview/breaking-changes.md +++ b/translations/zh-CN/content/graphql/overview/breaking-changes.md @@ -16,7 +16,7 @@ versions: - **重大：**会改变 GraphQL API 的现有查询的变更。 例如，删除字段就是重大变更。 - **危险：**不会改变现有查询，但会影响客户端运行时的行为的变更。 添加枚举值就是一个危险变更示例。 -我们努力为集成商提供稳定的 API。 当某项新功能还处于演进阶段时，我们将在[架构预览](/v4/previews/)模式下发布此功能。 +我们努力为集成商提供稳定的 API。 当某项新功能还处于演进阶段时，我们将在[架构预览](/graphql/overview/schema-previews)模式下发布此功能。 我们将在更改 GraphQL 架构前至少三个月宣布即将发生的重大变更，以便给集成商预留进行必要调整的时间。 变更在季度第一天（1 月 1 日、4 月 1 日、7 月 1 日或 10 月 1 日）生效。 例如，如果我们在 1 月 15 日宣布变更，将在 7 月 1 日执行。 diff --git a/translations/zh-CN/content/graphql/overview/changelog.md b/translations/zh-CN/content/graphql/overview/changelog.md index 630f002add..b8dc629444 100644 --- a/translations/zh-CN/content/graphql/overview/changelog.md +++ b/translations/zh-CN/content/graphql/overview/changelog.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -重大变更包括会改变现有查询或可能影响客户端运行时行为的变更。 有关重大变更及它们何时发生的列表，请参阅我们的[重大变更日志](/v4/breaking_changes)。 +重大变更包括会改变现有查询或可能影响客户端运行时行为的变更。 有关重大变更及它们何时发生的列表，请参阅我们的[重大变更日志](/graphql/overview/breaking-changes)。 {% for entry in graphql.changelog %} ### {{ entry.date }} 的架构变更 diff --git a/translations/zh-CN/content/graphql/overview/public-schema.md b/translations/zh-CN/content/graphql/overview/public-schema.md index d440f1f6eb..feb0215cf3 100644 --- a/translations/zh-CN/content/graphql/overview/public-schema.md +++ b/translations/zh-CN/content/graphql/overview/public-schema.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -您可以直接对 GraphQL API [执行内省](/v4/guides/intro-to-graphql/#discovering-the-graphql-api)。 +您可以直接对 GraphQL API [执行内省](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)。 或者，您也可以在此处下载公共架构的最新版本： diff --git a/translations/zh-CN/content/graphql/overview/resource-limitations.md b/translations/zh-CN/content/graphql/overview/resource-limitations.md index f720c2f351..8351e51eff 100644 --- a/translations/zh-CN/content/graphql/overview/resource-limitations.md +++ b/translations/zh-CN/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## 节点限制 -要通过[架构](/v4/guides/intro-to-graphql#schema)验证，所有 GraphQL API v4 [调用](/v4/guides/forming-calls)都必须满足这些标准： +To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: -* 客户端必须提供任何[连接](/v4/guides/intro-to-graphql#connection)上的 `first` 或 `last` 参数。 +* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). * `first` 和 `last` 的值必须在 1 至 100 之间。 -* 单个调用请求的[节点](/v4/guides/intro-to-graphql#node)总数不能超过 500,000。 +* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). #### 计算调用中的节点 @@ -121,7 +121,7 @@ versions: GraphQL API v4 限制不同于 REST API v3 的 [速率限制](/rest/overview/resources-in-the-rest-api#rate-limiting)。 -API 速率限制为什么不同？ 使用 [GraphQL](/v4/)，一个 GraphQL 调用可替换[多个 REST 调用](/v4/guides/migrating-from-rest/)。 单个复杂 GraphQL 调用可能相当于数千个 REST 请求。 虽然单个 GraphQL 调用远远低于 REST API v3 速率限制，但对 GitHub 的服务器来说，查询的计算成本可能同样高昂。 +API 速率限制为什么不同？ With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). 单个复杂 GraphQL 调用可能相当于数千个 REST 请求。 虽然单个 GraphQL 调用远远低于 REST API v3 速率限制，但对 GitHub 的服务器来说，查询的计算成本可能同样高昂。 要准确表示查询的服务器成本，GraphQL API v4 可根据标准分数量表计算调用的 **rate limit score（速率限制分数）**。 查询分数计入了父连接及其子连接上的第一个和最后一个参数。 diff --git a/translations/zh-CN/content/graphql/overview/schema-previews.md b/translations/zh-CN/content/graphql/overview/schema-previews.md index f86d21b630..a43c2a1cf7 100644 --- a/translations/zh-CN/content/graphql/overview/schema-previews.md +++ b/translations/zh-CN/content/graphql/overview/schema-previews.md @@ -13,7 +13,7 @@ versions: 在预览期间，我们可以根据开发者的反馈更改某些功能。 如果我们要执行变更，将在[开发者博客](https://developer.github.com/changes/)上宣布消息，不会事先通知。 -要访问架构预览，需要在 `Accept` 标头中为您的请求提供自定义[媒体类型](/v3/media)。 每个预览的功能文档可指定要提供的自定义媒体类型。 +要访问架构预览，需要在 `Accept` 标头中为您的请求提供自定义[媒体类型](/rest/overview/media-types)。 每个预览的功能文档可指定要提供的自定义媒体类型。 {% note %} diff --git a/translations/zh-CN/content/graphql/reference/enums.md b/translations/zh-CN/content/graphql/reference/enums.md index 2194329877..099abbb4be 100644 --- a/translations/zh-CN/content/graphql/reference/enums.md +++ b/translations/zh-CN/content/graphql/reference/enums.md @@ -12,9 +12,9 @@ versions: [枚举](https://graphql.github.io/graphql-spec/June2018/#sec-Enums)表示可能的字段值集。 -例如，[`Issue`](/v4/object/issue) 对象有一个名为 `state` 的字段。 状态是一种枚举（具体来说是 [`IssueState`](/v4/enum/issuestate/) 类型），因为它的值可能为 `OPEN` 或 `CLOSED`。 +例如，[`Issue`](/graphql/reference/objects#issue) 对象有一个名为 `state` 的字段。 状态是一种枚举（具体来说是 [`IssueState`](/graphql/reference/enums#issuestate) 类型），因为它的值可能为 `OPEN` 或 `CLOSED`。 -更多信息请参阅“[GraphQL 简介](/v4/guides/intro-to-graphql)”。 +更多信息请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql)”。 {% for item in graphql.schemaForCurrentVersion.enums %} {% include graphql-enum %} diff --git a/translations/zh-CN/content/graphql/reference/input-objects.md b/translations/zh-CN/content/graphql/reference/input-objects.md index 04a9881bcd..6c91a83eab 100644 --- a/translations/zh-CN/content/graphql/reference/input-objects.md +++ b/translations/zh-CN/content/graphql/reference/input-objects.md @@ -12,9 +12,9 @@ versions: [输入对象](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects)可描述为“可组合对象”，因为它们包含一组用于定义对象的输入字段。 -例如，[`CommitAuthor`](/v4/input_object/commitauthor/) 需要一个名为 `emails` 的字段。 为 `emails` 提供一个值可将 `CommitAuthor` 转变成包含电子邮件地址的 `User` 对象列表。 请注意，[对象](/v4/object) **may（可能）**包含输入对象，然而，[突变](/v4/mutation) **require（需要）**输入对象。 +例如，[`CommitAuthor`](/graphql/reference/input-objects#commitauthor) 需要一个名为 `emails` 的字段。 为 `emails` 提供一个值可将 `CommitAuthor` 转变成包含电子邮件地址的 `User` 对象列表。 请注意，[对象](/graphql/reference/objects) **may（可能）**包含输入对象，然而，[突变](/graphql/reference/mutations) **require（需要）**输入对象。 -更多信息请参阅“[关于突变](/v4/guides/forming-calls#about-mutations)。” +更多信息请参阅“[关于突变](/graphql/guides/forming-calls-with-graphql#about-mutations)。” {% for item in graphql.schemaForCurrentVersion.inputObjects %} {% include graphql-input-object %} diff --git a/translations/zh-CN/content/graphql/reference/interfaces.md b/translations/zh-CN/content/graphql/reference/interfaces.md index 97ce5790be..0e8cae2b94 100644 --- a/translations/zh-CN/content/graphql/reference/interfaces.md +++ b/translations/zh-CN/content/graphql/reference/interfaces.md @@ -12,9 +12,9 @@ versions: [接口](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces)可作为供其他对象继承的父对象。 -例如，[`Lockable`](/v4/interface/lockable/)是一个接口，因为 [`Issue`](/v4/object/issue/) 和 [`PullRequest`](/v4/object/pullrequest/) 对象都可以锁定。 接口拥有自己的指定字段列表，这些字段通过实现对象得以共享。 +例如，[`Lockable`](/graphql/reference/interfaces#lockable)是一个接口，因为 [`Issue`](/graphql/reference/objects#issue) 和 [`PullRequest`](/graphql/reference/objects#pullrequest) 对象都可以锁定。 接口拥有自己的指定字段列表，这些字段通过实现对象得以共享。 -更多信息请参阅“[实现](/v4/guides/intro-to-graphql#implementation)。” +更多信息请参阅“[实现](/graphql/guides/introduction-to-graphql#implementation)。” {% for item in graphql.schemaForCurrentVersion.interfaces %} {% include graphql-interface %} diff --git a/translations/zh-CN/content/graphql/reference/mutations.md b/translations/zh-CN/content/graphql/reference/mutations.md index 7956b9c674..8cfdfa57b4 100644 --- a/translations/zh-CN/content/graphql/reference/mutations.md +++ b/translations/zh-CN/content/graphql/reference/mutations.md @@ -12,7 +12,7 @@ versions: 每个 GraphQL 架构的查询和突变都有根类型。 [突变类型](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System)可定义用于更改服务器上数据的 GraphQL 操作。 此操作类似于执行 HTTP 请求方法，如 `POST`、`PATCH` 和 `DELETE`。 -更多信息请参阅“[关于突变](/v4/guides/forming-calls#about-mutations)。” +更多信息请参阅“[关于突变](/graphql/guides/forming-calls-with-graphql#about-mutations)。” {% for item in graphql.schemaForCurrentVersion.mutations %} {% include graphql-mutation %} diff --git a/translations/zh-CN/content/graphql/reference/objects.md b/translations/zh-CN/content/graphql/reference/objects.md index 5bff2681ad..a34c610ae0 100644 --- a/translations/zh-CN/content/graphql/reference/objects.md +++ b/translations/zh-CN/content/graphql/reference/objects.md @@ -14,7 +14,7 @@ GraphQL 中的[对象](https://graphql.github.io/graphql-spec/June2018/#sec-Obje 例如，[`Repository`](/graphql/reference/objects#repository) 对象包含一个名为 `name` 的字段，类型为 `String`。 -更多信息请参阅“[GraphQL 简介](/v4/guides/intro-to-graphql)”。 +更多信息请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql)”。 diff --git a/translations/zh-CN/content/graphql/reference/queries.md b/translations/zh-CN/content/graphql/reference/queries.md index ff4827e3ba..268b503da1 100644 --- a/translations/zh-CN/content/graphql/reference/queries.md +++ b/translations/zh-CN/content/graphql/reference/queries.md @@ -13,7 +13,7 @@ versions: 每个 GraphQL 架构的查询和突变都有根类型。 [查询类型](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System)可定义从服务器中检索数据的 GraphQL 操作。 -更多信息请参阅“[关于查询](/v4/guides/forming-calls#about-queries)。” +更多信息请参阅“[关于查询](/graphql/guides/forming-calls-with-graphql#about-queries)。” {% note %} diff --git a/translations/zh-CN/content/graphql/reference/scalars.md b/translations/zh-CN/content/graphql/reference/scalars.md index ddde87adc6..22e32bd3b9 100644 --- a/translations/zh-CN/content/graphql/reference/scalars.md +++ b/translations/zh-CN/content/graphql/reference/scalars.md @@ -14,7 +14,7 @@ versions: 调用 GraphQL API 时，必须指定嵌套子字段，直到仅返回标量。 -更多信息请参阅“[GraphQL 简介](/v4/guides/intro-to-graphql#field)。” +更多信息请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql#field)。” {% for item in graphql.schemaForCurrentVersion.scalars %} {% include graphql-scalar %} diff --git a/translations/zh-CN/content/graphql/reference/unions.md b/translations/zh-CN/content/graphql/reference/unions.md index a7f5b63e19..5aa7af3029 100644 --- a/translations/zh-CN/content/graphql/reference/unions.md +++ b/translations/zh-CN/content/graphql/reference/unions.md @@ -12,9 +12,9 @@ versions: [并集](https://graphql.github.io/graphql-spec/June2018/#sec-Unions)是一种表示多个对象的对象类型。 -例如，标记为 [`ProjectCardItem`](/v4/union/projectcarditem/) 的字段可能是 [`Issue`](/v4/object/issue/) 或 [`PullRequest`](/v4/object/pullrequest/)，因为每个对象都可能在项目卡内。 使用并集代替对象可以带来灵活性。 +例如，标记为 [`ProjectCardItem`](/graphql/reference/unions#projectcarditem) 的字段可能是 [`Issue`](/graphql/reference/objects#issue) 或 [`PullRequest`](/graphql/reference/objects#pullrequest)，因为每个对象都可能在项目卡内。 使用并集代替对象可以带来灵活性。 -更多信息请参阅“[GraphQL 简介](/v4/guides/intro-to-graphql)”。 +更多信息请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql)”。 {% for item in graphql.schemaForCurrentVersion.unions %} {% include graphql-union %} diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index e1b89ea2cb..c10ee1f002 100644 --- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: 启用 GitHub Insights 与 GitHub Enterprise 之间的链接 -intro: '您可以启用一个允许用户从 {% data variables.product.prodname_ghe_server %} 导航到 {{ site.data.variables.product.prodname_insights }} 的链接。' +intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员可启用 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_insights %} 之间的链接。' redirect_from: diff --git a/translations/zh-CN/content/packages/publishing-and-managing-packages/about-github-packages.md b/translations/zh-CN/content/packages/publishing-and-managing-packages/about-github-packages.md index ce9044313c..7dbfe85885 100644 --- a/translations/zh-CN/content/packages/publishing-and-managing-packages/about-github-packages.md +++ b/translations/zh-CN/content/packages/publishing-and-managing-packages/about-github-packages.md @@ -182,7 +182,7 @@ versions: ### 管理包 -您可以在 {% data variables.product.product_name %} 上或使用 GraphQL API 删除私有包的版本。 使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“[删除包](/packages/publishing-and-managing-packages/deleting-a-package)”和“[使用 GraphQL 进行调用](/v4/guides/forming-calls/)”。 +您可以在 {% data variables.product.product_name %} 上或使用 GraphQL API 删除私有包的版本。 使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“[删除包](/packages/publishing-and-managing-packages/deleting-a-package)”和“[使用 GraphQL 进行调用](/graphql/guides/forming-calls-with-graphql)”。 您可以配置 web 挂钩来订阅与包相关的事件，例如包的发布或更新等事件。 更多信息请参阅“[`package` web 挂钩事件](/webhooks/event-payloads/#package)”。 diff --git a/translations/zh-CN/content/rest/guides/basics-of-authentication.md b/translations/zh-CN/content/rest/guides/basics-of-authentication.md index d12d15de40..157e378b87 100644 --- a/translations/zh-CN/content/rest/guides/basics-of-authentication.md +++ b/translations/zh-CN/content/rest/guides/basics-of-authentication.md @@ -130,7 +130,7 @@ end 仅在发出请求之前检查作用域是不够的，因为用户可能会在检查与实际请求之间的时间段更改作用域。 如果发生这种情况，您期望成功的 API 调用可能会以 `404` 或 `401` 状态失败，或者返回不同的信息子集。 -为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 API 响应还包含一个 [`X-OAuth-Scopes` 标头][oauth scopes]。 此标头包含用于发出请求的令牌的作用域列表。 除此之外，OAuth 应用程序 API 还提供 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[检查令牌的有效性\]\[/v3/apps/oauth_applications/#check-a-token\]{% else %}\[检查令牌的有效性\]\[/v3/apps/oauth_applications/#check-an-authorization\]{% endif %} 的端点。 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 +为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 API 响应还包含一个 [`X-OAuth-Scopes` 标头][oauth scopes]。 此标头包含用于发出请求的令牌的作用域列表。 In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 #### 发出经过身份验证的请求 diff --git a/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md b/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md index 539b13b283..9cfbde2d64 100644 --- a/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md +++ b/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md @@ -20,7 +20,7 @@ versions: 您可以采取以下几个步骤来确保安全接收由 GitHub 交付的工作负载： 1. 确保您的接收服务器在 HTTPS 连接上。 默认情况下，GitHub 在交付有效负载时会验证 SSL 证书。{% if currentVersion == "free-pro-team@latest" %} -1. 您可以将[我们在交付挂钩时使用的 IP 地址](/github/authenticating-to-github/about-githubs-ip-addresses)添加到服务器的允许列表中。 为确保始终检查 IP 地址是否正确，您可以[使用 `/meta` 端点](/v3/meta/#meta)查找我们使用的地址。{% endif %} +1. 您可以将[我们在交付挂钩时使用的 IP 地址](/github/authenticating-to-github/about-githubs-ip-addresses)添加到服务器的允许列表中。 为确保始终检查 IP 地址是否正确，您可以[使用 `/meta` 端点](/rest/reference/meta#meta)查找我们使用的地址。{% endif %} 1. 提供[密钥令牌](/webhooks/securing/)以确保有效负载肯定来自 GitHub。 通过实施密钥令牌，您可以确保服务器接收的任何数据绝对来自 GitHub。 理想情况下，您应该为您服务的*每个用户*都提供一个不同的密钥令牌。 这样，即使某个令牌被泄露，也不至于影响其他用户。 ### 支持异步工作而非同步工作 @@ -49,7 +49,7 @@ GitHub 要求在收到 web 挂钩有效负载后 {% if currentVersion == "free-p GitHub 在资源发生移动时会通过提供重定向状态代码来明确告诉您。 您应该遵循这些重定向。 每个重定向响应都使用要转到的新 URI 来设置 `Location` 标头。 如果您收到了重定向，最好更新代码以遵循新的 URI，以防您请求我们可能已删除的无效路径。 -我们提供了 [HTTP 状态代码列表](/v3/#http-redirects)，供您在设计应用程序时参考以便遵循重定向。 +我们提供了 [HTTP 状态代码列表](/rest#http-redirects)，供您在设计应用程序时参考以便遵循重定向。 ### 不要手动解析 URL diff --git a/translations/zh-CN/content/rest/guides/building-a-ci-server.md b/translations/zh-CN/content/rest/guides/building-a-ci-server.md index 8b1772324e..0102a6d585 100644 --- a/translations/zh-CN/content/rest/guides/building-a-ci-server.md +++ b/translations/zh-CN/content/rest/guides/building-a-ci-server.md @@ -129,7 +129,7 @@ end 所有这些通信都会流回我们的聊天室。 使用此示例并不需要构建自己的 CI 设置。 您始终可以依赖 [GitHub 集成][integrations]。 -[status API]: /v3/repos/statuses/ +[status API]: /rest/reference/repos#statuses [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server diff --git a/translations/zh-CN/content/rest/guides/delivering-deployments.md b/translations/zh-CN/content/rest/guides/delivering-deployments.md index a8d50333c2..3b0bb2d3b3 100644 --- a/translations/zh-CN/content/rest/guides/delivering-deployments.md +++ b/translations/zh-CN/content/rest/guides/delivering-deployments.md @@ -13,7 +13,7 @@ versions: -[部署 API][deploy API] 为您托管在 {% data variables.product.product_name %} 上的项目提供在您自己的服务器上启动它们的功能。 结合 [状态 API][status API]，您将能够在您的代码到达 `master` 时协调部署。 +The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with the capability to launch them on a server that you own. 结合 [状态 API][status API]，您将能够在您的代码到达 `master` 时协调部署。 本指南将使用该 API 来演示您可以使用的设置。 在我们的场景中，我们将： @@ -145,7 +145,7 @@ end 搞定！ 使用此示例并不需要构建自己的部署设置。 您始终可以依赖 [GitHub 集成][integrations]。 -[deploy API]: /v3/repos/deployments/ +[deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok diff --git a/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md b/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md index 3f7e2602e1..fcbf2655c8 100644 --- a/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md @@ -93,19 +93,19 @@ end 作为应用程序开发者，您通常希望您的应用程序被授权访问用户的所有组织（公共和私有）。 上述工作流程恰好能满足您的要求。 -[basics-of-authentication]: /v3/guides/basics-of-authentication/ -[list-public-orgs]: /v3/orgs/#list-organizations-for-a-user -[list-repositories-for-current-user]: /v3/repos/#list-repositories-for-the-authenticated-user -[list-orgs-for-current-user]: /v3/orgs/#list-organizations-for-the-authenticated-user -[list-teams]: /v3/teams/#list-teams -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests +[basics-of-authentication]: /rest/guides/basics-of-authentication +[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user +[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user +[list-teams]: /rest/reference/teams#list-teams +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ [octokit.rb]: https://github.com/octokit/octokit.rb [octokit.rb]: https://github.com/octokit/octokit.rb -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user -[publicize-membership]: /v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user -[register-oauth-app]: /v3/guides/basics-of-authentication/#registering-your-app +[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user +[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/zh-CN/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-git-database-api.md index 3cc85e31ad..9cfb6a9cee 100644 --- a/translations/zh-CN/content/rest/guides/getting-started-with-the-git-database-api.md +++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-git-database-api.md @@ -11,7 +11,7 @@ versions: 这基本上允许您通过我们的 API 重新实现大量 Git 功能 - 通过直接在数据库中创建原始对象并更新分支引用，从技术上讲，您可以在不安装 Git 的情况下完成 Git 能做的任何事情。 -如果 Git 仓库为空或不可用，Git 数据库 API 函数将返回 `409 Conflict`。 仓库不可用通常意味着 {% data variables.product.product_name %} 正在创建仓库。 对于空仓库，您可以使用“[创建或更新文件内容](/v3/repos/contents/#create-or-update-file-contents)”端点来创建内容并初始化仓库，以便您可以使用 Git 数据库 API。 如果此响应状态仍然存在，请联系 {% data variables.contact.contact_support %}。 +如果 Git 仓库为空或不可用，Git 数据库 API 函数将返回 `409 Conflict`。 仓库不可用通常意味着 {% data variables.product.product_name %} 正在创建仓库。 对于空仓库，您可以使用“[创建或更新文件内容](/rest/reference/repos#create-or-update-file-contents)”端点来创建内容并初始化仓库，以便您可以使用 Git 数据库 API。 如果此响应状态仍然存在，请联系 {% data variables.contact.contact_support %}。 ![git 数据库概述](/assets/images/git-database-overview.png) @@ -33,14 +33,14 @@ versions: {% warning %} -**警告！**请不要依赖直接使用 Git 或 [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) 更新 `merge` Git 引用，因为此内容会在不发出警告的情况下过期。 +**警告！**请不要依赖直接使用 Git 或 [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) 更新 `merge` Git 引用，因为此内容会在不发出警告的情况下过期。 {% endwarning %} -消费 API 需要明确请求拉取请求来创建一个_测试_合并提交。 当您在 UI 中查看拉取请求并且“ Merge（合并）”按钮显示时，或者当您使用 REST API 来[获取](/v3/pulls/#get-a-pull-request)、[创建](/v3/pulls/#create-a-pull-request)或[编辑](/v3/pulls/#update-a-pull-request)拉取请求时，将创建一个_测试_合并提交。 如果没有此请求，`merge` Git 引用将过时，直到下次有人查看拉取请求。 +消费 API 需要明确请求拉取请求来创建一个_测试_合并提交。 当您在 UI 中查看拉取请求并且“ Merge（合并）”按钮显示时，或者当您使用 REST API 来[获取](/rest/reference/pulls#get-a-pull-request)、[创建](/rest/reference/pulls#create-a-pull-request)或[编辑](/rest/reference/pulls#update-a-pull-request)拉取请求时，将创建一个_测试_合并提交。 如果没有此请求，`merge` Git 引用将过时，直到下次有人查看拉取请求。 如果您当前正在使用会生成过时 `merge` Git 引用的轮询方法，GitHub 建议使用以下步骤从默认分支获取最新更改： 1. 接收拉取请求 web 挂钩。 -2. 调用 [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) 以启动创建合并提交候选项的后台作业。 -3. 使用 [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) 轮询仓库，以查看 `mergeable` 属性是 `true` 还是 `false`。 您仅在执行上述步骤后才可直接使用 Git 或 [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference) 更新 `merge` Git 引用。 +2. 调用 [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) 以启动创建合并提交候选项的后台作业。 +3. 使用 [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) 轮询仓库，以查看 `mergeable` 属性是 `true` 还是 `false`。 您仅在执行上述步骤后才可直接使用 Git 或 [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) 更新 `merge` Git 引用。 diff --git a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md index 6228d58954..a7439ee421 100644 --- a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md @@ -367,33 +367,33 @@ $ {% data variables.product.api_url_pre %}/users/defunkt [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[repos-api]: /v3/repos/ -[repos-api]: /v3/repos/ +[repos-api]: /rest/reference/repos +[repos-api]: /rest/reference/repos [pages]: http://pages.github.com [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore -[issues-api]: /v3/issues/ +[issues-api]: /rest/reference/issues [link-header]: http://www.w3.org/wiki/LinkHeader/ -[conditional-requests]: /v3/#conditional-requests -[rate-limiting]: /v3/#rate-limiting -[rate-limiting]: /v3/#rate-limiting -[users api]: /v3/users/#get-a-user +[conditional-requests]: /rest#conditional-requests +[rate-limiting]: /rest#rate-limiting +[rate-limiting]: /rest#rate-limiting +[users api]: /rest/reference/users#get-a-user [defunkt github]: https://github.com/defunkt [defunkt github]: https://github.com/defunkt [json]: http://en.wikipedia.org/wiki/JSON -[authentication]: /v3/#authentication +[authentication]: /rest#authentication [personal token]: /articles/creating-an-access-token-for-command-line-use [personal token]: /articles/creating-an-access-token-for-command-line-use [tokens settings]: https://github.com/settings/tokens -[pagination]: /v3/#pagination -[get repo]: /v3/repos/#get-a-repository -[create repo]: /v3/repos/#create-a-repository-for-the-authenticated-user -[create issue]: /v3/issues/#create-an-issue +[pagination]: /rest#pagination +[get repo]: /rest/reference/repos#get-a-repository +[create repo]: /rest/reference/repos#create-a-repository-for-the-authenticated-user +[create issue]: /rest/reference/issues#create-an-issue [auth guide]: /guides/basics-of-authentication -[user repos api]: /v3/repos/#list-repositories-for-the-authenticated-user -[other user repos api]: /v3/repos/#list-repositories-for-a-user -[org repos api]: /v3/repos/#list-organization-repositories -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[repo issues api]: /v3/issues/#list-repository-issues +[user repos api]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[other user repos api]: /rest/reference/repos#list-repositories-for-a-user +[org repos api]: /rest/reference/repos#list-organization-repositories +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[repo issues api]: /rest/reference/issues#list-repository-issues [etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md b/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md index 01e7469214..66e547c176 100644 --- a/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md @@ -232,7 +232,7 @@ erb :lang_freq, :locals => { :languages => languages.to_json} ] ``` -我们在前面已经获取了仓库列表，现在我们来检查每个仓库，然后调用[语言列表 API 方法][language API]： +Since we already have a list of repositories above, let's inspect each one, and call [the language listing API method][language API]: ``` ruby repos.each do |repo| @@ -264,7 +264,7 @@ end language_bytes = [ :name => "language_bytes", :elements => language_byte_count] ``` -（有关 D3 树图魔方的更多信息，请查看[这个简单教程][language API]。） +(For more information on D3 tree map magic, check out [this simple tutorial][language API].) 最后，我们将这些 JSON 信息传递到同一个 ERB 模板： @@ -333,7 +333,7 @@ erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_cou [Octokit]: https://github.com/octokit/octokit.rb [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ [D3 treemap]: http://bl.ocks.org/mbostock/4063582 -[language API]: /v3/repos/#list-repository-languages -[language API]: /v3/repos/#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs [new oauth application]: https://github.com/settings/applications/new diff --git a/translations/zh-CN/content/rest/guides/traversing-with-pagination.md b/translations/zh-CN/content/rest/guides/traversing-with-pagination.md index 6bed206ec2..e79e2d8011 100644 --- a/translations/zh-CN/content/rest/guides/traversing-with-pagination.md +++ b/translations/zh-CN/content/rest/guides/traversing-with-pagination.md @@ -20,9 +20,9 @@ versions: 首先需要了解有关接收分页条目的一些事实： -1. 不同的 API 调用响应具有不同的默认值。 例如，调用[列出公共仓库](/v3/repos/#list-public-repositories)将提供以 30 项为单位的分页结果，而调用 GitHub 搜索 API 将提供以 100 项为单位的分页结果 +1. 不同的 API 调用响应具有不同的默认值。 例如，调用[列出公共仓库](/rest/reference/repos#list-public-repositories)将提供以 30 项为单位的分页结果，而调用 GitHub 搜索 API 将提供以 100 项为单位的分页结果 2. 您可以指定要接收的条目数（最多 100 个）；但是， -3. 出于技术原因，并非每个端点的行为都相同。 例如，[事件](/v3/activity/events/)不允许设置要接收的最大条目数量。 请务必阅读关于如何处理特定端点分页结果的文档。 +3. 出于技术原因，并非每个端点的行为都相同。 例如，[事件](/rest/reference/activity#events)不允许设置要接收的最大条目数量。 请务必阅读关于如何处理特定端点分页结果的文档。 有关分页的信息包含在 API 调用的 [Link 标头](http://tools.ietf.org/html/rfc5988)中。 例如，我们向搜索 API 发出一个 curl 请求，以查明 Mozilla 项目使用短语 `addClass` 的次数： @@ -201,7 +201,7 @@ puts "The prev page link is #{prev_page_href}" puts "The next page link is #{next_page_href}" ``` -[pagination]: /v3/#pagination +[pagination]: /rest#pagination [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination [octokit.rb]: https://github.com/octokit/octokit.rb [personal token]: /articles/creating-an-access-token-for-command-line-use diff --git a/translations/zh-CN/content/rest/guides/working-with-comments.md b/translations/zh-CN/content/rest/guides/working-with-comments.md index 6bfdd46332..314974c3d7 100644 --- a/translations/zh-CN/content/rest/guides/working-with-comments.md +++ b/translations/zh-CN/content/rest/guides/working-with-comments.md @@ -18,7 +18,7 @@ versions: ### 拉取请求注释 -要访问拉取请求的注释，需要通过[议题 API][issues]。 乍一看这似乎不符合直觉。 但是，一旦您理解了拉取请求只是一个带有代码的议题，使用议题 API 来创建拉取请求注释就合情合理了。 +To access comments on a Pull Request, you'll go through [the Issues API][issues]. 乍一看这似乎不符合直觉。 但是，一旦您理解了拉取请求只是一个带有代码的议题，使用议题 API 来创建拉取请求注释就合情合理了。 我们将通过使用 [Octokit.rb][octokit.rb] 创建一个 Ruby 脚本来演示如何获取拉取请求注释 您还需要创建[个人访问令牌][personal token]。 @@ -44,7 +44,7 @@ end ### 拉取请求行注释 -在差异视图中，您可以开始讨论在拉取请求中进行的某个更改的特定方面。 这些注释出现在已更改文件中的各个行上。 此讨论的端点 URL 来自[拉取请求审查 API][PR Review API]。 +在差异视图中，您可以开始讨论在拉取请求中进行的某个更改的特定方面。 这些注释出现在已更改文件中的各个行上。 The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API]. 以下代码将获取文件中所做的所有拉取请求注释（给定一个拉取请求编号）： @@ -70,7 +70,7 @@ end ### 提交注释 -最后一类注释专门针对单个提交。 因此，它们使用 [提交注释 API][commit comment API]。 +最后一类注释专门针对单个提交。 For this reason, they make use of [the commit comment API][commit comment API]. 要检索对提交的注释，您需要使用该提交的 SHA1。 换句话说，您不能使用与拉取请求相关的任何标识符。 例如： @@ -97,8 +97,8 @@ end [commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 [sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 [platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments -[issues]: /v3/issues/comments/ +[issues]: /rest/reference/issues#comments [personal token]: /articles/creating-an-access-token-for-command-line-use [octokit.rb]: https://github.com/octokit/octokit.rb -[PR Review API]: /v3/pulls/comments/ -[commit comment API]: /v3/repos/comments/#get-a-commit-comment +[PR Review API]: /rest/reference/pulls#comments +[commit comment API]: /rest/reference/repos#get-a-commit-comment diff --git a/translations/zh-CN/content/rest/overview/api-previews.md b/translations/zh-CN/content/rest/overview/api-previews.md index 4a9f680afd..cab5d0f4cb 100644 --- a/translations/zh-CN/content/rest/overview/api-previews.md +++ b/translations/zh-CN/content/rest/overview/api-previews.md @@ -15,12 +15,12 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 在预览期间，我们可以根据开发者的反馈更改某些功能。 如果我们要执行变更，将在[开发者博客](https://developer.github.com/changes/)上宣布消息，不会事先通知。 -要访问 API 预览，需要在 `Accept` 标头中为您的请求提供自定义[媒体类型](/v3/media)。 每个预览的功能文档可指定要提供的自定义媒体类型。 +要访问 API 预览，需要在 `Accept` 标头中为您的请求提供自定义[媒体类型](/rest/overview/media-types)。 每个预览的功能文档可指定要提供的自定义媒体类型。 {% if currentVersion == "free-pro-team@latest" %} ### 迁移 -允许您从自己的 GitHub 用户或组织帐户下载仓库，以审查、备份以及[迁移](/v3/migrations/)数据到 {% data variables.product.prodname_ghe_server %}。 +允许您从自己的 GitHub 用户或组织帐户下载仓库，以审查、备份以及[迁移](/rest/reference/migrations)数据到 {% data variables.product.prodname_ghe_server %}。 **自定义媒体类型：** `wyandotte-preview` **公布日期：** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) {% endif %} @@ -33,13 +33,13 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 ### 反应 -管理对提交、议题和注释的[反应](/v3/reactions/)。 +管理对提交、议题和注释的[反应](/rest/reference/reactions)。 **自定义媒体类型：** `squirrel-girl-preview` **公布日期：** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **更新日期：** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) ### 时间表 -获取针对议题或拉取请求的[事件列表](/v3/issues/timeline/)。 +获取针对议题或拉取请求的[事件列表](/rest/reference/issues#timeline)。 **自定义媒体类型：** `mockingbird-preview` **公布日期：** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) @@ -61,40 +61,40 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 ### 项目 -管理[项目](/v3/projects/)。 +管理[项目](/rest/reference/projects)。 **自定义媒体类型：** `inertia-preview` **公布日期：** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **更新日期：** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) ### 提交搜索 -[搜索提交](/v3/search/)。 +[搜索提交](/rest/reference/search)。 **自定义媒体类型：** `cloak-preview` **公布日期：** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% if currentVersion == "free-pro-team@latest" %} ### 用户阻止 -用户可以[阻止其他用户](/v3/users/blocking/)。 组织也可以[阻止用户](/v3/orgs/blocking/)。 +用户可以[阻止其他用户](/rest/reference/users#blocking)。 组织也可以[阻止用户](/rest/reference/orgs#blocking)。 **自定义媒体类型：** `giant-sentry-fist-preview` **公布日期：** [2011-05-31](https://github.com/blog/862-block-the-bullies) **更新日期 1：** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **更新日期 2：** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) {% endif %} ### 仓库主题 -在返回仓库结果的[调用](/v3/repos/)中查看[仓库主题](/articles/about-topics/)列表。 +在返回仓库结果的[调用](/rest/reference/repos)中查看[仓库主题](/articles/about-topics/)列表。 **自定义媒体类型：** `mercy-preview` **公布日期：** [2017-01-31](https://github.com/blog/2309-introducing-topics) ### 行为准则 -查看[所有行为准则](/v3/codes_of_conduct)或获取仓库的当前行为准则。 +查看[所有行为准则](/rest/reference/codes-of-conduct)或获取仓库的当前行为准则。 **自定义媒体类型：** `scarlet-witch-preview` {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### 嵌套团队 -在[团队](/v3/teams/)有效负载中包含嵌套团队内容。 +在[团队](/rest/reference/teams)有效负载中包含嵌套团队内容。 **自定义媒体类型：** `hellcat-preview` **公布日期：** [2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) @@ -113,7 +113,7 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} ### 仓库转让 -将[仓库](/v3/repos/)转让给组织或用户。 +将[仓库](/rest/reference/repos)转让给组织或用户。 **自定义媒体类型：** `nightshade-preview` **公布日期：** [2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) {% endif %} @@ -121,27 +121,27 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### 添加锁定原因 -现在，您可以在[锁定议题](/v3/issues/#lock-an-issue)时添加原因。 +现在，您可以在[锁定议题](/rest/reference/issues#lock-an-issue)时添加原因。 **自定义媒体类型：** `sailor-v-preview` **公布日期：** [2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) {% endif %} ### 要求签名提交 -现在，您可以使用 API 来管理[要求在受保护的分支上进行签名提交](/v3/repos/branches)的设置。 +现在，您可以使用 API 来管理[要求在受保护的分支上进行签名提交](/rest/reference/repos#branches)的设置。 **自定义媒体类型：** `zzzax-preview` **公布日期：** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) ### 要求多次审批 -现在，您可以使用 API [要求多次审批](/v3/repos/branches)拉取请求。 +现在，您可以使用 API [要求多次审批](/rest/reference/repos#branches)拉取请求。 **自定义媒体类型：** `luke-cage-preview` **公布日期：** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.19" %} ### 检索悬停卡信息 -从[某人的悬停卡](/v3/users/#get-contextual-information-for-a-user)检索信息。 +从[某人的悬停卡](/rest/reference/users#get-contextual-information-for-a-user)检索信息。 **自定义媒体类型：** `hagar-preview` **公布日期：** [2018-03-21](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) @@ -150,7 +150,7 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} ### 检查运行和检查套件 API -允许 GitHub 应用程序对仓库的代码运行外部检查。 更多信息请参阅[检查运行](/v3/checks/runs/)和[检查套件](/v3/checks/suites/) API。 +允许 GitHub 应用程序对仓库的代码运行外部检查。 更多信息请参阅[检查运行](/rest/reference/checks#runs)和[检查套件](/rest/reference/checks#suites) API。 **自定义媒体类型：** `antiope-preview` **公布日期：** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) {% endif %} @@ -167,7 +167,7 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 ### 项目卡详细信息 -REST API 对[议题事件](/v3/issues/events/)和[议题时间表事件](/v3/issues/timeline/)的响应现在可返回项目相关事件的 `project_card` 字段。 +REST API 对[议题事件](/rest/reference/issues#events)和[议题时间表事件](/rest/reference/issues#timeline)的响应现在可返回项目相关事件的 `project_card` 字段。 **自定义媒体类型：** `starfox-preview` **公布日期：** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) @@ -189,7 +189,7 @@ GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 ### 仓库创建权限 -现在，您可以配置组织成员是否可以创建仓库以及他们可以创建哪些类型的仓库。 更多信息请参阅“[更新组织](/v3/orgs/#update-an-organization)”。 +现在，您可以配置组织成员是否可以创建仓库以及他们可以创建哪些类型的仓库。 更多信息请参阅“[更新组织](/rest/reference/orgs#update-an-organization)”。 **自定义媒体类型：** `surtur-preview` **公布日期：** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) @@ -202,7 +202,7 @@ GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### 草稿拉取请求 -您可以使用草稿拉取请求 API 及其[拉取请求](/v3/pulls/)端点来查看拉取请求是否处于草稿状态。 要了解有关草稿拉取请求的更多信息，请参阅“[关于拉取请求](/articles/about-pull-requests/)”。 +您可以使用草稿拉取请求 API 及其[拉取请求](/rest/reference/pulls)端点来查看拉取请求是否处于草稿状态。 要了解有关草稿拉取请求的更多信息，请参阅“[关于拉取请求](/articles/about-pull-requests/)”。 **自定义媒体类型：** `shadow-cat-preview` **公布日期：** [2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) @@ -216,48 +216,48 @@ GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 ### 列出提交的分支或拉取请求 -您可以使用[提交 API](/v3/repos/commits/) 中的两个新端点来列出提交的分支或拉取请求。 +您可以使用[提交 API](/rest/reference/repos#commits) 中的两个新端点来列出提交的分支或拉取请求。 **自定义媒体类型：** `groot-preview` **公布日期：** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} ### 卸载 GitHub 应用程序 -GitHub 应用程序的所有者现在可以使用[应用程序 API](/v3/apps/#delete-an-installation-for-the-authenticated-app) 卸载其应用程序。 +GitHub 应用程序的所有者现在可以使用[应用程序 API](/rest/reference/apps#delete-an-installation-for-the-authenticated-app) 卸载其应用程序。 **自定义媒体类型：** `gambit-preview` {% endif %} ### 为仓库启用或禁用漏洞警报 -您可以使用[仓库 API](/v3/repos/) 中的两个新端点来启用或禁用漏洞警报。 +您可以使用[仓库 API](/rest/reference/repos) 中的两个新端点来启用或禁用漏洞警报。 **自定义媒体类型：** `dorian-preview` **公布日期：** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) ### 更新拉取请求分支 -您可以使用新的端点根据上游分支的 HEAD 更改来[更新拉取请求分支](/v3/pulls/#update-a-pull-request-branch)。 +您可以使用新的端点根据上游分支的 HEAD 更改来[更新拉取请求分支](/rest/reference/pulls#update-a-pull-request-branch)。 **自定义媒体类型：** `lydian-preview` **公布日期：** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) {% if currentVersion == "free-pro-team@latest" %} ### 启用或禁用自动安全修复 -您可以使用一组新的端点来[启用和禁用自动安全修复](/v3/repos/#enable-automated-security-fixes)。 +您可以使用一组新的端点来[启用和禁用自动安全修复](/rest/reference/repos#enable-automated-security-fixes)。 **自定义媒体类型：** `london-preview` **公布日期：** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ### 创建和使用仓库模板 -您可以使用新的端点来[利用模板创建仓库](/v3/repos/#create-a-repository-using-a-template)，并通过将 `is_template` 参数设置为 `true`，[为经过身份验证的用户创建模板仓库](/v3/repos/#create-a-repository-for-the-authenticated-user)。 [获取仓库](/v3/repos/#get-a-repository)以检查是否使用 `is_template` 键将其设置为模板仓库。 +您可以使用新的端点来[利用模板创建仓库](/rest/reference/repos#create-a-repository-using-a-template)，并通过将 `is_template` 参数设置为 `true`，[为经过身份验证的用户创建模板仓库](/rest/reference/repos#create-a-repository-for-the-authenticated-user)。 [获取仓库](/rest/reference/repos#get-a-repository)以检查是否使用 `is_template` 键将其设置为模板仓库。 **自定义媒体类型：** `baptiste-preview` **公布日期：** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% if currentVersion == "enterprise-server@2.20" %} ### 新的 OAuth 应用程序 API 端点 -您可以使用新的 [OAuth 应用程序 API](/v3/apps/oauth_applications/) 端点，通过将 OAuth 令牌用作输入参数而不是路径参数，更安全地管理 OAuth 应用程序的令牌。 +您可以使用新的 [OAuth 应用程序 API](/rest/reference/apps#oauth-applications) 端点，通过将 OAuth 令牌用作输入参数而不是路径参数，更安全地管理 OAuth 应用程序的令牌。 **自定义媒体类型：** `doctor-strange-preview` **公布日期：** [2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) {% endif %} @@ -265,7 +265,7 @@ GitHub 应用程序的所有者现在可以使用[应用程序 API](/v3/apps/#de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ### 仓库 API 的新可见性参数 -您可以在[仓库 API](/v3/repos/) 中设置和检索仓库可见性。 +您可以在[仓库 API](/rest/reference/repos) 中设置和检索仓库可见性。 **自定义媒体类型：** `nebula-preview` **公布日期：** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/zh-CN/content/rest/overview/media-types.md b/translations/zh-CN/content/rest/overview/media-types.md index a567d5c7e5..74ad097b26 100644 --- a/translations/zh-CN/content/rest/overview/media-types.md +++ b/translations/zh-CN/content/rest/overview/media-types.md @@ -21,7 +21,7 @@ API 支持的最基本媒体类型是： application/json application/vnd.github+json -这两者都没有指定[版本][versions]，因此您总是会获取资源的当前默认 JSON 表示形式。 +Neither of these specify a [version][versions], so you will always get the current default JSON representation of resources. {% note %} @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### 注释正文属性 -注释正文可采用 [GitHub Flavored Markdown][gfm] 编写，[议题](/v3/issues/)、[议题注释](/v3/issues/comments/)、[拉取请求注释](/v3/pulls/comments/)和 [gist 注释](/v3/gists/comments/) API 都接受以下媒体类型： +The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: #### Raw @@ -85,7 +85,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### Git blob 属性 -[获取 Blob](/v3/git/blobs/#get-a-blob) 时允许使用以下媒体类型： +The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): #### JSON @@ -102,7 +102,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### 提交、提交比较和拉取请求 -[提交 API](/v3/repos/commits/) 和[拉取请求 API](/v3/pulls/) 支持 [diff][git-diff] 和 [patch][git-patch] 格式： +The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: #### 差异 @@ -147,4 +147,4 @@ Gist 内容在发送前经过 base64 编码。 这在 gist 包含任何无效的 [gfm]: http://github.github.com/github-flavored-markdown/ [git-diff]: http://git-scm.com/docs/git-diff [git-patch]: http://git-scm.com/docs/git-format-patch -[versions]: /v3/versions +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/zh-CN/content/rest/overview/other-authentication-methods.md b/translations/zh-CN/content/rest/overview/other-authentication-methods.md index ec4a6ae19e..e641de8216 100644 --- a/translations/zh-CN/content/rest/overview/other-authentication-methods.md +++ b/translations/zh-CN/content/rest/overview/other-authentication-methods.md @@ -69,7 +69,7 @@ would authenticate you if you replace `` with your {% data variables.p ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/v3/auth/#working-with-two-factor-authentication). +If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). {% endif %} @@ -134,9 +134,9 @@ $ curl --request POST \ {% endif %} [curl]: http://curl.haxx.se/ -[oauth-auth]: /v3/#authentication +[oauth-auth]: /rest#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on [saml-sso-tokens]: https://github.com/settings/tokens [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -[user-issues]: /v3/issues/#list-issues-assigned-to-the-authenticated-user +[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md index 8dff7c69ab..ab864346b6 100644 --- a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md @@ -14,13 +14,13 @@ versions: ### 当前版本 -默认情况下，对 `{% data variables.product.api_url_code %}` 的所有请求都会收到 REST API 的 **v3** [版本](/v3/versions)。 我们建议您[通过 `Accept` 标头明确请求此版本](/v3/media/#request-specific-version)。 +默认情况下，对 `{% data variables.product.api_url_code %}` 的所有请求都会收到 REST API 的 **v3** [版本](/developers/overview/about-githubs-apis)。 我们建议您[通过 `Accept` 标头明确请求此版本](/rest/overview/media-types#request-specific-version)。 Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -有关 GitHub GraphQL API 的信息，请参阅 [v4 文档](/v4)。 有关迁移到 GraphQL 的信息，请参阅“[从 REST 迁移](/v4/guides/migrating-from-rest/)”。 +有关 GitHub GraphQL API 的信息，请参阅 [v4 文档](/graphql)。 有关迁移到 GraphQL 的信息，请参阅“[从 REST 迁移](/graphql/guides/migrating-from-rest-to-graphql)”。 {% endif %} @@ -171,7 +171,7 @@ $ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "gith ### GraphQL 全局节点 ID -请参阅“[使用全局节点 ID](/v4/guides/using-global-node-ids)”指南，详细了解如何通过 REST API 查找 `node_id` 以及如何在 GraphQL 操作中使用它们。 +请参阅“[使用全局节点 ID](/graphql/guides/using-global-node-ids)”指南，详细了解如何通过 REST API 查找 `node_id` 以及如何在 GraphQL 操作中使用它们。 ### 客户端错误 @@ -262,7 +262,7 @@ API v3 尽可能对每个操作使用适当的 HTTP 请求方法。 ### 分页 -默认情况下，如果请求返回了多个项，将按每页最多 30 项进行分页。 您可以使用 `?page` 参数指定更多页面。 对于某些资源，您还可以使用 `?per_page` 参数设置自定义页面大小，每页最多 100 项。 请注意，由于技术原因，并非所有端点都遵循 `?per_page` 参数，相关示例请参阅[事件](/v3/activity/events/)。 +默认情况下，如果请求返回了多个项，将按每页最多 30 项进行分页。 您可以使用 `?page` 参数指定更多页面。 对于某些资源，您还可以使用 `?per_page` 参数设置自定义页面大小，每页最多 100 项。 请注意，由于技术原因，并非所有端点都遵循 `?per_page` 参数，相关示例请参阅[事件](/rest/reference/activity#events)。 ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' @@ -287,7 +287,7 @@ $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' _该示例包括换行符，以提高可读性。_ -此 `Link` 响应标头包含一个或多个[超媒体](/v3/#hypermedia)链接关系，其中一些可能需要扩展为 [URI 模板](http://tools.ietf.org/html/rfc6570)。 +此 `Link` 响应标头包含一个或多个[超媒体](/rest#hypermedia)链接关系，其中一些可能需要扩展为 [URI 模板](http://tools.ietf.org/html/rfc6570)。 可能的 `rel` 值为： @@ -312,7 +312,7 @@ _该示例包括换行符，以提高可读性。_ {% data reusables.enterprise.rate_limit %} -请注意[搜索 API 具有自定义速率限制规则](/v3/search/#rate-limit)。 +请注意[搜索 API 具有自定义速率限制规则](/rest/reference/search#rate-limit)。 任何 API 请求返回的 HTTP 标头都显示当前速率限制状态： @@ -355,7 +355,7 @@ new Date(1372700873 * 1000) > } ``` -您可以[检查速率限制状态](/v3/rate_limit)，而不会引发 API 命中。 +您可以[检查速率限制状态](/rest/reference/rate-limit)，而不会引发 API 命中。 #### 提高 OAuth 应用程序的未经验证速率限制 @@ -586,9 +586,9 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo #### 明确提供带有时区信息的 ISO 8601 时间戳 -对于允许指定时间戳的 API 调用，我们使用这种明确的时间戳。 这方面的示例是[提交 API](/v3/git/commits)。 +对于允许指定时间戳的 API 调用，我们使用这种明确的时间戳。 这方面的示例是[提交 API](/rest/reference/git#commits)。 -这些时间戳看起来像 `2014-02-27T15:05:06+01:00`。 另请参阅[本示例](/v3/git/commits/#example-input)，了解如何指定这些时间戳。 +这些时间戳看起来像 `2014-02-27T15:05:06+01:00`。 另请参阅[本示例](/rest/reference/git#example-input)，了解如何指定这些时间戳。 #### 使用 `Time-Zone` 标头 @@ -598,7 +598,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -这意味着当您在这个标题定义的时区做出 API 调用时，我们会生成一个时间戳。 例如，[内容 API](/v3/repos/contents/)为每个添加或更改生成 git 提交，并使用当前时间作为时间戳。 此标头将确定用于生成当前时间戳的时区。 +这意味着当您在这个标题定义的时区做出 API 调用时，我们会生成一个时间戳。 例如，[内容 API](/rest/reference/repos#contents)为每个添加或更改生成 git 提交，并使用当前时间作为时间戳。 此标头将确定用于生成当前时间戳的时区。 #### 使用用户的最后一个已知时区 diff --git a/translations/zh-CN/content/rest/overview/troubleshooting.md b/translations/zh-CN/content/rest/overview/troubleshooting.md index 95d294358b..c137e1005a 100644 --- a/translations/zh-CN/content/rest/overview/troubleshooting.md +++ b/translations/zh-CN/content/rest/overview/troubleshooting.md @@ -23,7 +23,7 @@ versions: 大多数访问资源列表（_例如_，用户、议题_等_）的 API 调用都支持分页。 如果您发出了请求但收到了不完整的结果集，您可能只看到第一页。 您需要请求剩余的页面以获取更多结果。 -*切勿*尝试和猜测分页 URL 的格式。 并非每个 API 调用都使用相同的结构。 您应该从随每个请求一起发送的[链接标头](/v3/#pagination)中提取分页信息。 +*切勿*尝试和猜测分页 URL 的格式。 并非每个 API 调用都使用相同的结构。 您应该从随每个请求一起发送的[链接标头](/rest#pagination)中提取分页信息。 {% if currentVersion == "free-pro-team@latest" %} ### 基本身份验证错误 diff --git a/translations/zh-CN/content/rest/reference/apps.md b/translations/zh-CN/content/rest/reference/apps.md index cc84f5763a..783d855680 100644 --- a/translations/zh-CN/content/rest/reference/apps.md +++ b/translations/zh-CN/content/rest/reference/apps.md @@ -18,7 +18,7 @@ GitHub 应用程序 API 使您能够获取有关 GitHub 应用程序的高层次 验证为 GitHub 应用程序后，您可以访问 REST API v3 端点。 这些端点带有“备注”部分，即“与 GitHub 应用程序结合使用”。 验证为用户后也可以访问这些端点。 -某些 REST API v3 端点需要验证为 GitHub 应用程序安装设施。 有关这些端点的列表，请参阅[安装设施](/v3/apps/installations/)。 +某些 REST API v3 端点需要验证为 GitHub 应用程序安装设施。 有关这些端点的列表，请参阅[安装设施](/rest/reference/apps#installations)。 {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -36,7 +36,7 @@ GitHub 应用程序 API 使您能够获取有关 GitHub 应用程序的高层次 安装设施 API 使您能够获取有关 GitHub 应用程序安装设施的信息并在这些安装设施中执行操作。 _安装设施_是指已安装该应用程序的任何用户或组织帐户。 有关如何验证为安装设施和限制访问特定仓库的信息，请参阅“[验证为安装设施](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)”。 -要列出组织的所有 GitHub 应用程序安装设施，请参阅“[列出组织的应用程序安装设施](/v3/orgs/#list-app-installations-for-an-organization)”。 +要列出组织的所有 GitHub 应用程序安装设施，请参阅“[列出组织的应用程序安装设施](/rest/reference/orgs#list-app-installations-for-an-organization)”。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %} @@ -70,4 +70,4 @@ GitHub 应用程序 API 使您能够获取有关 GitHub 应用程序的高层次 {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} 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 8e9906243c..d46f6f7166 100644 --- a/translations/zh-CN/content/rest/reference/codes-of-conduct.md +++ b/translations/zh-CN/content/rest/reference/codes-of-conduct.md @@ -9,6 +9,6 @@ versions: github-ae: '*' --- -您可以使用行为准则 API 检索有关仓库行为准则的信息。 要获取仓库的行为准则，请使用“[获取仓库](/v3/repos/#get-a-repository)”端点。 +您可以使用行为准则 API 检索有关仓库行为准则的信息。 要获取仓库的行为准则，请使用“[获取仓库](/rest/reference/repos#get-a-repository)”端点。 {% 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 51afdab9d8..0b24d3ffb0 100644 --- a/translations/zh-CN/content/rest/reference/enterprise-admin.md +++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md @@ -86,7 +86,7 @@ IdP 必须使用 `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**注：**企业 SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/v3/auth/#authenticating-for-saml-sso) 的企业。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 +**注：**企业 SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的企业。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 {% endnote %} diff --git a/translations/zh-CN/content/rest/reference/git.md b/translations/zh-CN/content/rest/reference/git.md index 3f83540fff..91d34cd8d3 100644 --- a/translations/zh-CN/content/rest/reference/git.md +++ b/translations/zh-CN/content/rest/reference/git.md @@ -34,7 +34,7 @@ Git Blob（二进制大对象）是用于将每个文件的内容存储在仓库 ## 提交 -Git 提交是 Git 仓库中层次结构（[Git 树](/v3/git/trees)）和文件内容 ( +Git 提交是 Git 仓库中层次结构（[Git 树](/rest/reference/git#trees)）和文件内容 ( Git blob {% for operation in currentRestOperations %} @@ -59,7 +59,7 @@ Git 引用 (`git ref`) 只是一个包含 Git 提交 SHA-1 哈希的文件。 ## 标记 -Git 标记类似于 [Git 引用](/v3/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)，而不支持轻量级标记。 +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 %} diff --git a/translations/zh-CN/content/rest/reference/issues.md b/translations/zh-CN/content/rest/reference/issues.md index 28bf669c11..755cf73346 100644 --- a/translations/zh-CN/content/rest/reference/issues.md +++ b/translations/zh-CN/content/rest/reference/issues.md @@ -33,7 +33,7 @@ versions: 议题评论 API 支持列出、查看、编辑和创建对议题和拉取请求的评论。 -议题评论使用[这些自定义媒体类型](#custom-media-types)。 您可以在[此处](/v3/media/)阅读有关 API 中媒体类型使用情况的更多信息。 +议题评论使用[这些自定义媒体类型](#custom-media-types)。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} diff --git a/translations/zh-CN/content/rest/reference/licenses.md b/translations/zh-CN/content/rest/reference/licenses.md index 52a79b630e..4a12e581bd 100644 --- a/translations/zh-CN/content/rest/reference/licenses.md +++ b/translations/zh-CN/content/rest/reference/licenses.md @@ -16,12 +16,12 @@ versions: **注：**这些端点还将返回仓库的许可信息： -- [获取仓库](/v3/repos/#get-a-repository) -- [列出用户的仓库](/v3/repos/#list-repositories-for-a-user) -- [列出组织仓库](/v3/repos/#list-organization-repositories) +- [获取仓库](/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) -- [列出团队仓库](/v3/teams/#list-team-repositories) +- [列出团队仓库](/rest/reference/teams#list-team-repositories) {% warning %} diff --git a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md index 06db546bd4..2752545fd5 100644 --- a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md @@ -19,63 +19,63 @@ GitHub 应用程序默认具有 `Read-only` 元数据权限。 元数据权限 {% data reusables.apps.metadata-permissions %} -- [`GET /`](/v3/#root-endpoint) -- [`GET /codes_of_conduct`](/v3/codes_of_conduct/#get-all-codes-of-conduct) -- [`GET /codes_of_conduct/:key`](/v3/codes_of_conduct/#get-a-code-of-conduct) -- [`GET /emojis`](/v3/emojis/#emojis) +- [`GET /`](/rest#root-endpoint) +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +- [`GET /emojis`](/rest/reference/emojis#emojis) - [`GET /feeds`](/rest/reference/activity#get-feeds) -- [`GET /licenses`](/v3/licenses/#get-all-commonly-used-licenses) -- [`GET /licenses/:key`](/v3/licenses/#get-a-license) -- [`POST /markdown`](/v3/markdown/#render-a-markdown-document) -- [`POST /markdown/raw`](/v3/markdown/#render-a-markdown-document-in-raw-mode) -- [`GET /meta`](/v3/meta/#meta) -- [`GET /organizations`](/v3/orgs/#list-organizations) -- [`GET /orgs/:org`](/v3/orgs/#get-an-organization) -- [`GET /orgs/:org/projects`](/v3/projects/#list-organization-projects) -- [`GET /orgs/:org/repos`](/v3/repos/#list-organization-repositories) -- [`GET /rate_limit`](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) -- [`GET /repos/:owner/:repo`](/v3/repos/#get-a-repository) +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license) +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +- [`GET /meta`](/rest/reference/meta#meta) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization) +- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects) +- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories) +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/community/profile`](/v3/repos/community/#get-community-profile-metrics) +- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics) {% endif %} -- [`GET /repos/:owner/:repo/contributors`](/v3/repos/#list-repository-contributors) +- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors) - [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks) -- [`GET /repos/:owner/:repo/languages`](/v3/repos/#list-repository-languages) -- [`GET /repos/:owner/:repo/license`](/v3/licenses/#get-the-license-for-a-repository) +- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository) - [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers) -- [`GET /repos/:owner/:repo/stats/code_frequency`](/v3/repos/statistics/#get-the-weekly-commit-activity) -- [`GET /repos/:owner/:repo/stats/commit_activity`](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -- [`GET /repos/:owner/:repo/stats/contributors`](/v3/repos/statistics/#get-all-contributor-commit-activity) -- [`GET /repos/:owner/:repo/stats/participation`](/v3/repos/statistics/#get-the-weekly-commit-count) -- [`GET /repos/:owner/:repo/stats/punch_card`](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity) +- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity) +- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity) +- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count) +- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) - [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers) -- [`GET /repos/:owner/:repo/tags`](/v3/repos/#list-repository-tags) -- [`GET /repos/:owner/:repo/topics`](/v3/repos#get-all-repository-topics) -- [`GET /repositories`](/v3/repos/#list-public-repositories) -- [`GET /user/repos`](/v3/repos/#list-repositories-for-the-authenticated-user) +- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) - [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) - [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) -- [`GET /users`](/v3/users/#list-users) -- [`GET /users/:username`](/v3/users/#get-a-user) -- [`GET /users/:username/followers`](/v3/users/followers/#list-followers-of-a-user) -- [`GET /users/:username/following`](/v3/users/followers/#list-the-people-a-user-follows) -- [`GET /users/:username/following/:target_user`](/v3/users/followers/#check-if-a-user-follows-another-user) -- [`GET /users/:username/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) -- [`GET /users/:username/orgs`](/v3/orgs/#list-organizations-for-a-user) +- [`GET /users`](/rest/reference/users#list-users) +- [`GET /users/:username`](/rest/reference/users#get-a-user) +- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user) - [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) - [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) -- [`GET /users/:username/repos`](/v3/repos/#list-repositories-for-a-user) +- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) _协作者_ -- [`GET /repos/:owner/:repo/collaborators`](/v3/repos/collaborators/#list-repository-collaborators) -- [`GET /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) +- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) +- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) _提交注释_ -- [`GET /repos/:owner/:repo/comments`](/v3/repos/comments/#list-commit-comments-for-a-repository) -- [`GET /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#get-a-commit-comment) -- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-commit-comment) -- [`GET /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#list-commit-comments) +- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) +- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) +- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) _事件_ - [`GET /events`](/rest/reference/activity#list-public-events) @@ -86,311 +86,311 @@ _事件_ - [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user) _Git_ -- [`GET /gitignore/templates`](/v3/gitignore/#get-all-gitignore-templates) -- [`GET /gitignore/templates/:key`](/v3/gitignore/#get-a-gitignore-template) +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) +- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) _键_ -- [`GET /users/:username/keys`](/v3/users/keys/#list-public-keys-for-a-user) +- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) _组织成员_ -- [`GET /orgs/:org/members`](/v3/orgs/members/#list-organization-members) -- [`GET /orgs/:org/members/:username`](/v3/orgs/members/#check-organization-membership-for-a-user) -- [`GET /orgs/:org/public_members`](/v3/orgs/members/#list-public-organization-members) -- [`GET /orgs/:org/public_members/:username`](/v3/orgs/members/#check-public-organization-membership-for-a-user) +- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`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) _搜索_ -- [`GET /search/code`](/v3/search/#search-code) -- [`GET /search/commits`](/v3/search/#search-commits) -- [`GET /search/issues`](/v3/search/#search-issues-and-pull-requests) -- [`GET /search/labels`](/v3/search/#search-labels) -- [`GET /search/repositories`](/v3/search/#search-repositories) -- [`GET /search/topics`](/v3/search/#search-topics) -- [`GET /search/users`](/v3/search/#search-users) +- [`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) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) {% if currentVersion == "free-pro-team@latest" %} ### 有关“操作”的权限 -- [`GET /repos/:owner/:repo/actions/artifacts`](/v3/actions/artifacts/#list-artifacts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} ### 有关“管理”的权限 -- [`POST /orgs/:org/repos`](/v3/repos/#create-an-organization-repository) (:write) -- [`PATCH /repos/:owner/:repo`](/v3/repos/#update-a-repository) (:write) -- [`DELETE /repos/:owner/:repo`](/v3/repos/#delete-a-repository) (:write) +- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) +- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) +- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) (:read) -- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) (:write)git +- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write)git {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#enable-automated-security-fixes) (:write) +- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#disable-automated-security-fixes) (:write) +- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:write) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write) {% endif %} -- [`PUT /repos/:owner/:repo/topics`](/v3/repos/#replace-all-repository-topics) (:write) -- [`POST /repos/:owner/:repo/transfer`](/v3/repos/#transfer-a-repository) (:write) +- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write) +- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) +- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#disable-vulnerability-alerts) (:write) +- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write) {% endif %} -- [`PATCH /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#accept-a-repository-invitation) (:write) -- [`DELETE /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#decline-a-repository-invitation) (:write) +- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write) +- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write) _分支_ -- [`GET /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#get-branch-protection) (:read) -- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#update-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#delete-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#get-admin-branch-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#set-admin-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#delete-admin-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#get-pull-request-review-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#update-pull-request-review-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#delete-pull-request-review-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#get-commit-signature-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#create-commit-signature-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#delete-commit-signature-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#get-status-checks-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#update-status-check-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#remove-status-check-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#get-all-status-check-contexts) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#add-status-check-contexts) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#set-status-check-contexts) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#remove-status-check-contexts) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#get-access-restrictions) (:read) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#delete-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#add-team-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#set-team-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#remove-team-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#add-user-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#set-user-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read) +- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) _协作者_ -- [`PUT /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#add-a-repository-collaborator) (:write) -- [`DELETE /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#remove-a-repository-collaborator) (:write) +- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) +- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) _邀请_ -- [`GET /repos/:owner/:repo/invitations`](/v3/repos/invitations/#list-repository-invitations) (:read) -- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#update-a-repository-invitation) (:write) -- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#delete-a-repository-invitation) (:write) +- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) +- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) +- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) _键_ -- [`GET /repos/:owner/:repo/keys`](/v3/repos/keys/#list-deploy-keys) (:read) -- [`POST /repos/:owner/:repo/keys`](/v3/repos/keys/#create-a-deploy-key) (:write) -- [`GET /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#get-a-deploy-key) (:read) -- [`DELETE /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#delete-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) +- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) +- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) _团队_ -- [`GET /repos/:owner/:repo/teams`](/v3/repos/#list-repository-teams) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:write) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) +- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) {% if currentVersion == "free-pro-team@latest" %} _流量_ -- [`GET /repos/:owner/:repo/traffic/clones`](/v3/repos/traffic/#get-repository-clones) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/paths`](/v3/repos/traffic/#get-top-referral-paths) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/v3/repos/traffic/#get-top-referral-sources) (:read) -- [`GET /repos/:owner/:repo/traffic/views`](/v3/repos/traffic/#get-page-views) (:read) +- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) +- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### 有关“阻止”的权限 -- [`GET /user/blocks`](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) (:read) -- [`GET /user/blocks/:username`](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) -- [`PUT /user/blocks/:username`](/v3/users/blocking/#block-a-user) (:write) -- [`DELETE /user/blocks/:username`](/v3/users/blocking/#unblock-a-user) (:write) +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) +- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) +- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (:write) +- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) {% endif %} ### 有关“检查”的权限 -- [`POST /repos/:owner/:repo/check-runs`](/v3/checks/runs/#create-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#update-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`POST /repos/:owner/:repo/check-suites`](/v3/checks/suites/#create-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/v3/checks/suites/#update-repository-preferences-for-check-suites) (:write) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) +- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (:write) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) ### 有关“内容”的权限 -- [`GET /repos/:owner/:repo/:archive_format/:ref`](/v3/repos/contents/#download-a-repository-archive) (:read) +- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:write) +- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#get-a-repository-secret) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) +- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) +- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:write) +- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/commits`](/v3/repos/commits/#list-commits) (:read) -- [`GET /repos/:owner/:repo/commits/:sha`](/v3/repos/commits/#get-a-commit) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/community/code_of_conduct`](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/compare/:base...:head`](/v3/repos/commits/#compare-two-commits) (:read) -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read) +- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`POST /repos/:owner/:repo/dispatches`](/v3/repos/#create-a-repository-dispatch-event) (:write) +- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write) {% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:read) -- [`POST /repos/:owner/:repo/merges`](/v3/repos/merging/#merge-a-branch) (:write) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#merge-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/v3/repos/contents/#get-a-repository-readme) (:read) +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read) +- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read) _分支_ -- [`GET /repos/:owner/:repo/branches`](/v3/repos/branches/#list-branches) (:read) -- [`GET /repos/:owner/:repo/branches/:branch`](/v3/repos/branches/#get-a-branch) (:read) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#list-apps-with-access-to-the-protected-branch) (:write) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#add-app-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#set-app-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#remove-user-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read) +- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) _提交注释_ -- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#update-a-commit-comment) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#delete-a-commit-comment) (:write) -- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-commit-comment) (:read) -- [`POST /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#create-a-commit-comment) (:read) +- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) +- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) +- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read) _Git_ -- [`POST /repos/:owner/:repo/git/blobs`](/v3/git/blobs/#create-a-blob) (:write) -- [`GET /repos/:owner/:repo/git/blobs/:sha`](/v3/git/blobs/#get-a-blob) (:read) -- [`POST /repos/:owner/:repo/git/commits`](/v3/git/commits/#create-a-commit) (:write) -- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/v3/git/commits/#get-a-commit) (:read) -- [`POST /repos/:owner/:repo/git/refs`](/v3/git/refs/#create-a-reference) (:write) -- [`GET /repos/:owner/:repo/git/ref/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/v3/git/refs/#list-matching-references) (:read) -- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#update-a-reference) (:write) -- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#delete-a-reference) (:write) -- [`POST /repos/:owner/:repo/git/tags`](/v3/git/tags/#create-a-tag-object) (:write) -- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/v3/git/tags/#get-a-tag) (:read) -- [`POST /repos/:owner/:repo/git/trees`](/v3/git/trees/#create-a-tree) (:write) -- [`GET /repos/:owner/:repo/git/trees/:sha`](/v3/git/trees/#get-a-tree) (:read) +- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write) +- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (:read) +- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (:write) +- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (:read) +- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (:write) +- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (:read) +- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (:read) +- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (:write) +- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (:write) +- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (:write) +- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (:read) +- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (:write) +- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) {% if currentVersion == "free-pro-team@latest" %} _导入_ -- [`GET /repos/:owner/:repo/import`](/v3/migrations/source_imports/#get-an-import-status) (:read) -- [`PUT /repos/:owner/:repo/import`](/v3/migrations/source_imports/#start-an-import) (:write) -- [`PATCH /repos/:owner/:repo/import`](/v3/migrations/source_imports/#update-an-import) (:write) -- [`DELETE /repos/:owner/:repo/import`](/v3/migrations/source_imports/#cancel-an-import) (:write) -- [`GET /repos/:owner/:repo/import/authors`](/v3/migrations/source_imports/#get-commit-authors) (:read) -- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/v3/migrations/source_imports/#map-a-commit-author) (:write) -- [`GET /repos/:owner/:repo/import/large_files`](/v3/migrations/source_imports/#get-large-files) (:read) -- [`PATCH /repos/:owner/:repo/import/lfs`](/v3/migrations/source_imports/#update-git-lfs-preference) (:write) +- [`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) +- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (:write) +- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (:read) +- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (:write) +- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (:read) +- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) {% endif %} _反应_ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% endif %} _版本发布_ - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read) @@ -419,195 +419,195 @@ _版本发布_ ### 有关“电子邮件”的权限 {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /user/email/visibility`](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) (:write) +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) {% endif %} -- [`GET /user/emails`](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) (:read) -- [`POST /user/emails`](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) (:write) -- [`DELETE /user/emails`](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) (:write) -- [`GET /user/public_emails`](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) (:read) +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (:write) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (:write) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) {% endif %} ### 有关“关注者”的权限 -- [`GET /user/followers`](/v3/users/followers/#list-followers-of-a-user) (:read) -- [`GET /user/following`](/v3/users/followers/#list-the-people-a-user-follows) (:read) -- [`GET /user/following/:username`](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) (:read) -- [`PUT /user/following/:username`](/v3/users/followers/#follow-a-user) (:write) -- [`DELETE /user/following/:username`](/v3/users/followers/#unfollow-a-user) (:write) +- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) +- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) +- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (:read) +- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) +- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) ### 有关“gpg 密钥”的权限 -- [`GET /user/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) (:read) -- [`POST /user/gpg_keys`](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) (:write) -- [`GET /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) (:read) -- [`DELETE /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (:read) +- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) ### 有关“议题”的权限 -议题和拉取请求密切相关。 更多信息请参阅"[列出分配给经身份验证用户的议题](/v3/issues/#list-issues-assigned-to-the-authenticated-user)“。 如果您的 GitHub 应用程序拥有处理议题的权限但没有处理拉取请求的权限，则这些端点将仅限于处理议题。 既返回议题又返回拉取请求的端点将被过滤。 允许对议题和拉取请求进行操作的端点将被限制为仅处理议题。 +议题和拉取请求密切相关。 更多信息请参阅"[列出分配给经身份验证用户的议题](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)“。 如果您的 GitHub 应用程序拥有处理议题的权限但没有处理拉取请求的权限，则这些端点将仅限于处理议题。 既返回议题又返回拉取请求的端点将被过滤。 允许对议题和拉取请求进行操作的端点将被限制为仅处理议题。 -- [`GET /repos/:owner/:repo/issues`](/v3/issues/#list-repository-issues) (:read) -- [`POST /repos/:owner/:repo/issues`](/v3/issues/#create-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#get-an-issue) (:read) -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) +- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (:read) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) _受理人_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _事件_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [Get an issue event](/v3/issues/events/#get-an-issue-event) (:read) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [Get an issue event](/rest/reference/issues#get-an-issue-event) (:read) _标签_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _里程碑_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _反应_ -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} ### 有关“键”的权限 _键_ -- [`GET /user/keys`](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) (:read) -- [`POST /user/keys`](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) (:write) -- [`GET /user/keys/:key_id`](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) (:read) -- [`DELETE /user/keys/:key_id`](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) +- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) ### 有关“成员”的权限 {% if currentVersion == "free-pro-team@latest" %} -- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#list-idp-groups-for-a-team) (:write) +- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#create-or-update-idp-group-connections) (:write) +- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write) {% endif %} -- [`GET /orgs/:org/outside_collaborators`](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) (:read) -- [`PUT /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) (:write) -- [`DELETE /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) (:write) +- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read) +- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write) +- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/team-sync/groups`](/v3/teams/team_sync/#list-idp-groups-for-an-organization) (:write) +- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write) {% endif %} -- [`GET /orgs/:org/team/:team_id`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users`](/v3/scim/#list-scim-provisioned-identities) (:read) +- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`POST /scim/v2/orgs/:org/Users`](/v3/scim/#provision-and-invite-a-scim-user) (:write) +- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#get-scim-provisioning-information-for-a-user) (:read) +- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#set-scim-information-for-a-provisioned-user) (:write) +- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#update-an-attribute-for-a-scim-user) (:write) +- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#delete-a-scim-user-from-an-organization) (:write) +- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} _邀请_ -- [`GET /orgs/:org/invitations`](/v3/orgs/members/#list-pending-organization-invitations) (:read) -- [`POST /orgs/:org/invitations`](/v3/orgs/members/#create-an-organization-invitation) (:write) -- [`GET /orgs/:org/invitations/:invitation_id/teams`](/v3/orgs/members/#list-organization-invitation-teams) (:read) -- [`GET /teams/:team_id/invitations`](/v3/teams/members/#list-pending-team-invitations) (:read) +- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) +- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) +- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) +- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) {% endif %} _组织成员_ -- [`DELETE /orgs/:org/members/:username`](/v3/orgs/members/#remove-an-organization-member) (:write) -- [`GET /orgs/:org/memberships/:username`](/v3/orgs/members/#get-organization-membership-for-a-user) (:read) -- [`PUT /orgs/:org/memberships/:username`](/v3/orgs/members/#set-organization-membership-for-a-user) (:write) -- [`DELETE /orgs/:org/memberships/:username`](/v3/orgs/members/#remove-organization-membership-for-a-user) (:write) -- [`PUT /orgs/:org/public_members/:username`](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) (:write) -- [`DELETE /orgs/:org/public_members/:username`](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) (:write) -- [`GET /user/memberships/orgs`](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) (:read) -- [`GET /user/memberships/orgs/:org`](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) (:read) -- [`PATCH /user/memberships/orgs/:org`](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) +- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) +- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) +- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (:write) +- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (:write) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (:read) +- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) +- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) _团队成员_ -- [`GET /teams/:team_id/members`](/v3/teams/members/#list-team-members) (:read) -- [`GET /teams/:team_id/memberships/:username`](/v3/teams/members/#get-team-membership-for-a-user) (:read) -- [`PUT /teams/:team_id/memberships/:username`](/v3/teams/members/#add-or-update-team-membership-for-a-user) (:write) -- [`DELETE /teams/:team_id/memberships/:username`](/v3/teams/members/#remove-team-membership-for-a-user) (:write) +- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) +- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) +- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) +- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) _团队_ -- [`GET /orgs/:org/teams`](/v3/teams/#list-teams) (:read) -- [`POST /orgs/:org/teams`](/v3/teams/#create-a-team) (:write) -- [`GET /orgs/:org/teams/:team_slug`](/v3/teams/#get-a-team-by-name) (:read) +- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) +- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) +- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} -- [`GET /teams/:team_id`](/v3/teams/#get-a-team) (:read) +- [`GET /teams/:team_id`](/rest/reference/teams#get-a-team) (:read) {% endif %} -- [`PATCH /teams/:team_id`](/v3/teams/#update-a-team) (:write) -- [`DELETE /teams/:team_id`](/v3/teams/#delete-a-team) (:write) +- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write) +- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`GET /teams/:team_id/projects`](/v3/teams/#list-team-projects) (:read) -- [`GET /teams/:team_id/projects/:project_id`](/v3/teams/#check-team-permissions-for-a-project) (:read) -- [`PUT /teams/:team_id/projects/:project_id`](/v3/teams/#add-or-update-team-project-permissions) (:read) -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read) +- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read) +- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% endif %} -- [`GET /teams/:team_id/repos`](/v3/teams/#list-team-repositories) (:read) -- [`GET /teams/:team_id/repos/:owner/:repo`](/v3/teams/#check-team-permissions-for-a-repository) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:read) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) -- [`GET /teams/:team_id/teams`](/v3/teams/#list-child-teams) (:read) +- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read) +- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) +- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) ### 有关“组织管理”的权限 -- [`PATCH /orgs/:org`](/v3/orgs/#update-an-organization) (:write) +- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) {% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/interaction-limits`](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) (:read) +- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`PUT /orgs/:org/interaction-limits`](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) (:write) +- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /orgs/:org/interaction-limits`](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) (:write) +- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) {% endif %} ### 有关“组织挂钩”的权限 @@ -620,7 +620,7 @@ _团队_ - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write) _团队_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if enterpriseServerVersions contains currentVersion %} ### 有关“组织预接收挂钩”的权限 @@ -633,31 +633,31 @@ _团队_ ### 有关“组织项目”的权限 -- [`POST /orgs/:org/projects`](/v3/projects/#create-an-organization-project) (:write) -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) +- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) {% if currentVersion == "free-pro-team@latest" %} ### 有关"组织用户阻止"的权限 -- [`GET /orgs/:org/blocks`](/v3/orgs/blocking/#list-users-blocked-by-an-organization) (:read) -- [`GET /orgs/:org/blocks/:username`](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) (:read) -- [`PUT /orgs/:org/blocks/:username`](/v3/orgs/blocking/#block-a-user-from-an-organization) (:write) -- [`DELETE /orgs/:org/blocks/:username`](/v3/orgs/blocking/#unblock-a-user-from-an-organization) (:write) +- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) +- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) +- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (:write) +- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) {% endif %} ### 有关“页面”的权限 @@ -675,99 +675,99 @@ _团队_ 拉取请求和议题密切相关。 如果您的 GitHub 应用程序拥有处理拉取请求的权限但没有处理议题的权限，则这些端点将仅限于处理拉取请求。 既返回拉取请求又返回议题的端点将被过滤。 允许对拉取请求和议题进行操作的端点将被限制为仅处理拉取请求。 -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls`](/v3/pulls/#list-pull-requests) (:read) -- [`POST /repos/:owner/:repo/pulls`](/v3/pulls/#create-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#get-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#update-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#list-review-comments-on-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/v3/pulls/#list-commits-on-a-pull-request) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/v3/pulls/#list-pull-requests-files) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#check-if-a-pull-request-has-been-merged) (:read) -- [`GET /repos/:owner/:repo/pulls/comments`](/v3/pulls/comments/#list-review-comments-in-a-repository) (:read) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) (:write) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (:read) +- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (:read) +- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (:read) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) _受理人_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) _事件_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [`GET /repos/:owner/:repo/issues/events/:event_id`](/v3/issues/events/#get-an-issue-event) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) _标签_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) _里程碑_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) _反应_ -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) (:read) -- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) (:write) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read) +- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} _请求的审查者_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) _审查_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#list-reviews-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#create-a-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#get-a-review-for-a-pull-request) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#update-a-review-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#delete-a-pending-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) ### 有关“仓库挂钩”的权限 -- [`GET /repos/:owner/:repo/hooks`](/v3/repos/hooks/#list-repository-webhooks) (:read) -- [`POST /repos/:owner/:repo/hooks`](/v3/repos/hooks/#create-a-repository-webhook) (:write) -- [`GET /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#get-a-repository-webhook) (:read) -- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#update-a-repository-webhook) (:write) -- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#delete-a-repository-webhook) (:write) -- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/v3/repos/hooks/#ping-a-repository-webhook) (:read) -- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/v3/repos/hooks/#test-the-push-repository-webhook) (:read) +- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) +- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) +- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read) +- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write) +- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write) +- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read) +- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read) {% if enterpriseServerVersions contains currentVersion %} ### 有关“仓库预接收挂钩”的权限 @@ -780,70 +780,70 @@ _审查_ ### 有关“仓库项目”的权限 -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) -- [`GET /repos/:owner/:repo/projects`](/v3/projects/#list-repository-projects) (:read) -- [`POST /repos/:owner/:repo/projects`](/v3/projects/#create-a-repository-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) +- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) +- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) _团队_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% if currentVersion == "free-pro-team@latest" %} ### 有关“密钥”的权限 -* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:read) -* [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:read) -* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#get-a-repository-secret) (:read) -* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -* [`GET /orgs/:org/actions/secrets/public-key`](/v3/actions/secrets/#get-an-organization-public-key) (:read) -* [`GET /orgs/:org/actions/secrets`](/v3/actions/secrets/#list-organization-secrets) (:read) -* [`GET /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#get-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-an-organization-secret) (:write) -* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) (:write) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-an-organization-secret) (:write) +* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) +* [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) +* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (:read) +* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (:write) +* [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (:read) +* [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (:read) +* [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (:write) +* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (:write) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### 有关“安全事件”的权限 -- [`GET /repos/:owner/:repo/code-scanning/alerts`](/v3/code-scanning/#list-code-scanning-alerts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/v3/code-scanning/#get-a-code-scanning-alert) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) {% endif %} {% if currentVersion == "free-pro-team@latest" %} ### 有关“自托管运行器”的权限 -- [`GET /orgs/:org/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) (:write) -- [`GET /orgs/:org/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) (:read) -- [`GET /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) (:write) -- [`DELETE /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) +- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) +- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) {% endif %} ### 有关“单个文件”的权限 -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -- [`PUT /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#create-or-update-file-contents) (:write) -- [`DELETE /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#delete-a-file) (:write) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) +- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) ### 有关“星标”的权限 @@ -853,23 +853,23 @@ _团队_ ### 有关“状态”的权限 -- [`GET /repos/:owner/:repo/commits/:ref/status`](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/v3/repos/statuses/#list-commit-statuses-for-a-reference) (:read) -- [`POST /repos/:owner/:repo/statuses/:sha`](/v3/repos/statuses/#create-a-commit-status) (:write) +- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) +- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) ### 有关“团队讨论”的权限 -- [`GET /teams/:team_id/discussions`](/v3/teams/discussions/#list-discussions) (:read) -- [`POST /teams/:team_id/discussions`](/v3/teams/discussions/#create-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#get-a-discussion) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#update-a-discussion) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#delete-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#list-discussion-comments) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#create-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#get-a-discussion-comment) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#update-a-discussion-comment) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#delete-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion-comment) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion) (:write) +- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) +- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/zh-CN/content/rest/reference/pulls.md b/translations/zh-CN/content/rest/reference/pulls.md index 1697ac4bd4..ccebc90c9f 100644 --- a/translations/zh-CN/content/rest/reference/pulls.md +++ b/translations/zh-CN/content/rest/reference/pulls.md @@ -10,7 +10,7 @@ versions: 拉取请求 API 允许您列出、查看、编辑、创建甚至合并拉取请求。 可以通过[议题评论 API](/rest/reference/issues#comments) 管理对拉取请求的评论。 -每个拉取请求都是一个议题，但并非每个议题都是拉取请求。 因此，在[议题 API](/v3/issues) 中为这两项功能提供了“共享”操作，如操作受理人、标签和里程碑。 +每个拉取请求都是一个议题，但并非每个议题都是拉取请求。 因此，在[议题 API](/rest/reference/issues) 中为这两项功能提供了“共享”操作，如操作受理人、标签和里程碑。 ### 拉取请求的自定义媒体类型 @@ -33,16 +33,16 @@ versions: 拉取请求具有以下可能的链接关系： -| 名称 | 描述 | -| ----------------- | ---------------------------------------------------------------------------- | -| `self` | 此拉取请求的 API 位置。 | -| `html` | 此拉取请求的 HTML 位置。 | -| `议题` | 此拉取请求的[议题](/v3/issues/)的 API 位置。 | -| `comments` | 此拉取请求的[议题评论](/v3/issues/comments/)的 API 位置。 | -| `review_comments` | 此拉取请求的[审查评论](/v3/pulls/comments/)的 API 位置。 | -| `review_comment` | 用于为此拉取请求仓库中的[审查评论](/v3/pulls/comments/)构建 API 位置的 [URL 模板](/v3/#hypermedia)。 | -| `commits` | 此拉取请求的[提交](#list-commits-on-a-pull-request)的 API 位置。 | -| `statuses` | 此拉取请求的[提交状态](/v3/repos/statuses/)的 API 位置，即其`头部`分支的状态。 | +| 名称 | 描述 | +| ----------------- | ---------------------------------------------------------------------------------------- | +| `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 位置。 | +| `statuses` | 此拉取请求的[提交状态](/rest/reference/repos#statuses)的 API 位置，即其`头部`分支的状态。 | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/zh-CN/content/rest/reference/rate-limit.md b/translations/zh-CN/content/rest/reference/rate-limit.md index 284e36b5b2..f99dc264a1 100644 --- a/translations/zh-CN/content/rest/reference/rate-limit.md +++ b/translations/zh-CN/content/rest/reference/rate-limit.md @@ -13,18 +13,18 @@ REST API 概述文档描述了[速率限制规则](/rest/overview/resources-in-t ### 了解您的速率限制状态 -搜索 API 具有[自定义速率限制](/v3/search/#rate-limit)，与管理 REST API 其余部分的速率限制不同。 GraphQL API 也有[自定义速率限制](/v4/guides/resource-limitations/#rate-limit)，它与 REST API 中的速率限制不同且分开计算。 +搜索 API 具有[自定义速率限制](/rest/reference/search#rate-limit)，与管理 REST API 其余部分的速率限制不同。 GraphQL API 也有[自定义速率限制](/graphql/overview/resource-limitations#rate-limit)，它与 REST API 中的速率限制不同且分开计算。 出于这些原因，速率限制 API 响应对速率限制进行分类。 在`资源`下，您会看到四个 对象： * `核心`对象提供 REST API 中所有非搜索相关资源的速率限制状态。 -* `搜索`对象提供[搜索 API](/v3/search/) 的速率限制状态。 +* `搜索`对象提供[搜索 API](/rest/reference/search) 的速率限制状态。 -* `graphql`对象提供 [GraphQL API](/v4/) 的速率限制状态。 +* `graphql`对象提供 [GraphQL API](/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)端点的速率限制状态。 -有关速率限制响应中标头和值的更多信息，请参阅“[速率限制](/v3/#rate-limiting)”。 +有关速率限制响应中标头和值的更多信息，请参阅“[速率限制](/rest#rate-limiting)”。 {% include rest_operations_at_current_path %} diff --git a/translations/zh-CN/content/rest/reference/repos.md b/translations/zh-CN/content/rest/reference/repos.md index 09fa359efa..fa306aeed9 100644 --- a/translations/zh-CN/content/rest/reference/repos.md +++ b/translations/zh-CN/content/rest/reference/repos.md @@ -29,7 +29,7 @@ versions: ### 提交评论的自定义媒体类型 -以下是提交评论支持的媒体类型。 您可以在[此处](/v3/media/)阅读有关 API 中媒体类型使用情况的更多信息。 +以下是提交评论支持的媒体类型。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。 application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json @@ -65,7 +65,7 @@ versions: ### 仓库内容的自定义媒体类型 -[自述文件](/v3/repos/contents/#get-a-repository-readme)、[文件](/v3/repos/contents/#get-repository-content)和[符号链接](/v3/repos/contents/#get-repository-content)支持以下自定义媒体类型： +[自述文件](/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 @@ -74,13 +74,13 @@ versions: 对于 Markdown 或 AsciiDoc 等标记文件，您可以使用 `.html` 媒体类型检索渲染的 HTML。 使用我们的开源[标记库](https://github.com/github/markup)将标记语言渲染为 HTML。 -[所有对象](/v3/repos/contents/#get-repository-content)都支持以下自定义媒体类型： +[所有对象](/rest/reference/repos#get-repository-content)都支持以下自定义媒体类型： application/vnd.github.VERSION.object 使用 `object` 媒体类型参数以一致的对象格式检索内容，而不考虑内容类型。 例如，响应将是包含对象数组的 `entries` 属性的对象，而不是目录的对象数组。 -您可以在[此处](/v3/media/)阅读有关 API 中媒体类型使用情况的更多信息。 +您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %} diff --git a/translations/zh-CN/content/rest/reference/scim.md b/translations/zh-CN/content/rest/reference/scim.md index 350ed321af..bdb611942b 100644 --- a/translations/zh-CN/content/rest/reference/scim.md +++ b/translations/zh-CN/content/rest/reference/scim.md @@ -12,7 +12,7 @@ SCIM API 由 SCIM 启用的身份提供程序 (IdP) 用来自动预配 {% data v {% note %} -**注：**SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/v3/auth/#authenticating-for-saml-sso) 的组织。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 +**注：**SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的组织。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 {% endnote %} diff --git a/translations/zh-CN/content/rest/reference/search.md b/translations/zh-CN/content/rest/reference/search.md index 929061e2ba..db9ed681d3 100644 --- a/translations/zh-CN/content/rest/reference/search.md +++ b/translations/zh-CN/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: 搜索 API 可帮助您搜索要查找的特定条目。 例如，您可以在仓库中找到用户或特定文件。 就像您在 Google 上执行搜索一样。 它旨在帮助您找到要查找的一个或几个结果。 就像在 Google 上搜索一样，有时您希望查看几页搜索结果，以便找到最能满足您需求的条目。 为了满足这一需求， {% data variables.product.product_name %} 搜索 API **为每个搜索提供最多 1,000 个结果**。 -您可以使用查询缩小搜索范围。 要了解有关搜索查询语法的更多信息，请查看“[构建搜索查询](/v3/search/#constructing-a-search-query)”。 +您可以使用查询缩小搜索范围。 To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." ### 排列搜索结果 @@ -18,7 +18,7 @@ versions: ### 速率限制 -搜索 API 有自定义速率限制。 对于使用[基本身份验证](/v3/#authentication)、[OAuth](/v3/#authentication) 或[客户端 ID 和密码](/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications)的请求，您每分钟最多可以提出 30 个请求。 对于未经身份验证的请求，速率限制允许您每分钟最多提出 10 个请求。 +搜索 API 有自定义速率限制。 For requests using [Basic Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. 对于未经身份验证的请求，速率限制允许您每分钟最多提出 10 个请求。 {% data reusables.enterprise.rate_limit %} diff --git a/translations/zh-CN/content/rest/reference/teams.md b/translations/zh-CN/content/rest/reference/teams.md index ae8519997f..9886f75dca 100644 --- a/translations/zh-CN/content/rest/reference/teams.md +++ b/translations/zh-CN/content/rest/reference/teams.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -此 API 仅适用于团队[组织](/v3/orgs)中经过身份验证的成员。 OAuth 访问令牌需要 `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)。 {% data variables.product.prodname_dotcom %} 从团队 `name` 生成团队的 `slug`。 +此 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 %} @@ -16,7 +16,7 @@ versions: ## 讨论 -团队讨论 API 允许您获取、创建、编辑和删除团队页面上的讨论帖子。 您可以使用团队讨论进行不特定于存储库或项目的对话。 团队[组织](/v3/orgs)的任何成员都可以创建和阅读公共讨论帖子。 有关详细信息，请参阅“[关于团队讨论](https://help.github.com/articles/about-team-discussions/)”。 要详细了解对讨论帖子的评论，请参阅[团队讨论评论 API](/v3/teams/discussion_comments)。 此 API 仅适用于团队组织中经过身份验证的成员。 +团队讨论 API 允许您获取、创建、编辑和删除团队页面上的讨论帖子。 您可以使用团队讨论进行不特定于存储库或项目的对话。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论帖子。 有关详细信息，请参阅“[关于团队讨论](https://help.github.com/articles/about-team-discussions/)”。 要详细了解对讨论帖子的评论，请参阅[团队讨论评论 API](/rest/reference/teams#discussion-comments)。 此 API 仅适用于团队组织中经过身份验证的成员。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -24,7 +24,7 @@ versions: ## 讨论评论 -团队讨论评论 API 允许您在[团队讨论](/v3/teams/discussions)帖子上获取、 创建、编辑和删除讨论评论。 团队[组织](/v3/orgs)的任何成员都可以创建和阅读公共讨论上的评论。 有关详细信息，请参阅“[关于团队讨论](https://help.github.com/articles/about-team-discussions/)”。 此 API 仅适用于团队组织中经过身份验证的成员。 +团队讨论评论 API 允许您在[团队讨论](/rest/reference/teams#discussions)帖子上获取、 创建、编辑和删除讨论评论。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论上的评论。 有关详细信息，请参阅“[关于团队讨论](https://help.github.com/articles/about-team-discussions/)”。 此 API 仅适用于团队组织中经过身份验证的成员。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -58,4 +58,4 @@ versions: {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} \ No newline at end of file +{% endif %} 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 f73100b64d..6f16748e78 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 @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' 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 cce0d56212..b3eff235c3 100644 --- a/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml @@ -1,7 +1,7 @@ --- upcoming_changes: - - location: Migration.uploadUrlTemplate + location: LegacyMigration.uploadUrlTemplate description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' diff --git a/translations/zh-CN/data/reusables/apps/app-ruby-guides.md b/translations/zh-CN/data/reusables/apps/app-ruby-guides.md index 2d06b6ac98..8a844c2323 100644 --- a/translations/zh-CN/data/reusables/apps/app-ruby-guides.md +++ b/translations/zh-CN/data/reusables/apps/app-ruby-guides.md @@ -1,5 +1,5 @@ {% note %} -**注：**本指南演示了使用 Ruby 编程语言的应用程序开发过程。 但有很多[Octokit 风格](/v3/libraries/)。 如果您喜欢 JavaScript，可以使用 [Probot](https://probot.github.io/) 和 [Node.js](https://octokit.github.io/rest.js/) 开发 GitHub 应用程序。 +**注：**本指南演示了使用 Ruby 编程语言的应用程序开发过程。 但有很多[Octokit 风格](/rest/overview/libraries)。 如果您喜欢 JavaScript，可以使用 [Probot](https://probot.github.io/) 和 [Node.js](https://octokit.github.io/rest.js/) 开发 GitHub 应用程序。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/apps/checks-availability.md b/translations/zh-CN/data/reusables/apps/checks-availability.md index a95e1c9e59..c0b3ffd3cd 100644 --- a/translations/zh-CN/data/reusables/apps/checks-availability.md +++ b/translations/zh-CN/data/reusables/apps/checks-availability.md @@ -1 +1 @@ -检查 API 的写入权限仅适用于 GitHub 应用程序。 OAuth 应用程序和经过身份验证的用户可以查看检查运行和检查套件，但无法创建它们。 如果您没有构建 GitHub 应用程序，您可能对[状态 API](/v3/repos/statuses/) 感兴趣。 +检查 API 的写入权限仅适用于 GitHub 应用程序。 OAuth 应用程序和经过身份验证的用户可以查看检查运行和检查套件，但无法创建它们。 如果您没有构建 GitHub 应用程序，您可能对[状态 API](/rest/reference/repos#statuses) 感兴趣。 diff --git a/translations/zh-CN/data/reusables/apps/deletes_ssh_keys.md b/translations/zh-CN/data/reusables/apps/deletes_ssh_keys.md index 5f1c1cd723..00d3e2f3f4 100644 --- a/translations/zh-CN/data/reusables/apps/deletes_ssh_keys.md +++ b/translations/zh-CN/data/reusables/apps/deletes_ssh_keys.md @@ -1,5 +1,5 @@ {% warning %} -**警告**: 从 {% data variables.product.prodname_oauth_app %} 撤销所有权限将会删除应用程序代表用户生成的 SSH 密钥，包括[部署密钥](/v3/guides/managing-deploy-keys/#deploy-keys)。 +**警告**: 从 {% data variables.product.prodname_oauth_app %} 撤销所有权限将会删除应用程序代表用户生成的 SSH 密钥，包括[部署密钥](/developers/overview/managing-deploy-keys#deploy-keys)。 {% endwarning %} diff --git a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md index 358537cb6f..6995459369 100644 --- a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**弃用通知：** {% data variables.product.prodname_dotcom %} 将停止使用查询参数向 API 验证。 向 API 验证应使用 [HTTP 基本身份验证](/v3/auth/#via-oauth-and-personal-access-tokens)完成。{% if currentVersion == "free-pro-team@latest" %} 使用查询参数向 API 验证在 2021 年 5 月 5 日将不再有效。 {% endif %}有关详细信息，包括预定的限电，请参阅[博客文章](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)。 +**弃用通知：** {% data variables.product.prodname_dotcom %} 将停止使用查询参数向 API 验证。 向 API 验证应使用 [HTTP 基本身份验证](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)完成。{% if currentVersion == "free-pro-team@latest" %} 使用查询参数向 API 验证在 2021 年 5 月 5 日将不再有效。 {% endif %}有关详细信息，包括预定的限电，请参阅[博客文章](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)。 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. 相反，我们建议集成商在标头中移动其访问令牌 `client_id` 或 `client_secret`。 {% data variables.product.prodname_dotcom %} 将宣布删除通过查询参数进行身份验证，并且会提前通知。 {% endif %} diff --git a/translations/zh-CN/data/reusables/apps/deprecating_github_services_ghe.md b/translations/zh-CN/data/reusables/apps/deprecating_github_services_ghe.md index a0c505915e..f897e8e050 100644 --- a/translations/zh-CN/data/reusables/apps/deprecating_github_services_ghe.md +++ b/translations/zh-CN/data/reusables/apps/deprecating_github_services_ghe.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} {% note %} -**注：**GitHub Enterprise 2.17 及更高版本不再允许管理员安装新的 GitHub 服务，并且现有服务将在 GitHub Enterprise 2.20 及更高版本中停用。 您可以使用[替换 GitHub 服务指南](/v3/guides/replacing-github-services)帮助您将服务更新到 web 挂钩。 +**注：**GitHub Enterprise 2.17 及更高版本不再允许管理员安装新的 GitHub 服务，并且现有服务将在 GitHub Enterprise 2.20 及更高版本中停用。 您可以使用[替换 GitHub 服务指南](/developers/overview/replacing-github-services)帮助您将服务更新到 web 挂钩。 {% endnote %} {% endif %} diff --git a/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md b/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md index 2b6831112f..0107bd5af7 100644 --- a/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -以下配置文件禁用默认查询，并指定一组要运行的自定义查询。 它还配置 {% data variables.product.prodname_codeql %} 以扫描 _src_ 目录中的文件（相对于根目录），并且排除 _node_modules_ 目录（也相对于根目录）以及名称以 _est.js_ 结尾的任何文件。 +以下配置文件禁用默认查询，并指定一组要运行的自定义查询。 It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. ``` yaml name: "My {% data variables.product.prodname_codeql %} config" @@ -24,9 +24,9 @@ queries: - name: Use a query suite file (run queries from a query suite in this repo) uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls -paths-ignore: - - node_modules - - '**/*.test.js' paths: - src +paths-ignore: + - src/node_modules + - '**/*.test.js' ``` diff --git a/translations/zh-CN/data/reusables/github-actions/matrix-variable-example.md b/translations/zh-CN/data/reusables/github-actions/matrix-variable-example.md new file mode 100644 index 0000000000..9cdd09966e --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/matrix-variable-example.md @@ -0,0 +1,26 @@ +在此示例中， `node-version` 的矩阵条目每个都被配置为对 `site` 和 `datacenter` 环境变量使用不同的值。 `Echo site details` 步骤然后使用 {% raw %}`env: ${{ matrix.env }}`{% endraw %} 引用自定义变量： + +{% raw %} +```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - node-version: 10.x + site: "prod" + datacenter: "site-a" + - node-version: 12.x + site: "dev" + datacenter: "site-b" + steps: + - name: Echo site details + env: + SITE: ${{ matrix.site }} + DATACENTER: ${{ matrix.datacenter }} + run: echo $SITE $DATACENTER +``` +{% endraw %} diff --git a/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-api.md index 0ed18b1711..05219277ea 100644 --- a/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-api.md +++ b/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-api.md @@ -1 +1 @@ -要使用 REST API 创建秘密，您必须有对仓库或管理员访问组织的写入权限。 更多信息请参阅“[{% data variables.product.prodname_actions %} 密码 API](/v3/actions/secrets/)”。 +要使用 REST API 创建秘密，您必须有对仓库或管理员访问组织的写入权限。 更多信息请参阅“[{% data variables.product.prodname_actions %} 密码 API](/rest/reference/actions#secrets)”。 diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 9ac93498fa..21decb40c1 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,12 +1,12 @@ -1. In the **Self-hosted runners** section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. - ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. 在设置页面的 **Self-hosted runners（自托管运行器）**部分，单击要配置的运行器组旁边的 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Edit name and [organization|repository] access（编辑名称和[组织|仓库]权限）**。 ![管理仓库权限](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. {% warning %} - **Warning** + **警告** + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} - For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." + + 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。 {% endwarning %} - diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 564327527e..1e1a9a2251 100644 --- a/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -启用团队同步后，团队维护员和组织所有者可在 {% data variables.product.prodname_dotcom %} 上或通过 API 将团队连接至 IdP 组。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”和“[团队同步](/v3/teams/team_sync/)”。 +启用团队同步后，团队维护员和组织所有者可在 {% data variables.product.prodname_dotcom %} 上或通过 API 将团队连接至 IdP 组。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”和“[团队同步](/rest/reference/teams#team-sync)”。 diff --git a/translations/zh-CN/data/reusables/issue-events/issue-event-common-properties.md b/translations/zh-CN/data/reusables/issue-events/issue-event-common-properties.md index 22bf260d72..5ac15f6c44 100644 --- a/translations/zh-CN/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/zh-CN/data/reusables/issue-events/issue-event-common-properties.md @@ -1,10 +1,10 @@ -| 名称 | 类型 | 描述 | -| ------------ | ----- | -------------------------------------------------------------------- | -| `id` | `整数` | The unique identifier of the event. | -| `node_id` | `字符串` | The [Global Node ID](/v4/guides/using-global-node-ids) of the event. | -| `url` | `字符串` | 用于提取事件的 REST API URL。 | -| `actor` | `对象` | The person who generated the event. | -| `event` | `字符串` | 识别所发生事件的实际类型。 | -| `commit_id` | `字符串` | 引用此议题的提交的 SHA。 | -| `commit_url` | `字符串` | 指向引用此议题的提交的 GitHub REST API 链接。 | -| `created_at` | `字符串` | 指示事件发生时间的时间戳。 | +| 名称 | 类型 | 描述 | +| ------------ | ----- | ------------------------------------------------------------------------- | +| `id` | `整数` | The unique identifier of the event. | +| `node_id` | `字符串` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | +| `url` | `字符串` | 用于提取事件的 REST API URL。 | +| `actor` | `对象` | The person who generated the event. | +| `event` | `字符串` | 识别所发生事件的实际类型。 | +| `commit_id` | `字符串` | 引用此议题的提交的 SHA。 | +| `commit_url` | `字符串` | 指向引用此议题的提交的 GitHub REST API 链接。 | +| `created_at` | `字符串` | 指示事件发生时间的时间戳。 | diff --git a/translations/zh-CN/data/reusables/pre-release-program/corsair-preview.md b/translations/zh-CN/data/reusables/pre-release-program/corsair-preview.md index 093e147002..f9628de118 100644 --- a/translations/zh-CN/data/reusables/pre-release-program/corsair-preview.md +++ b/translations/zh-CN/data/reusables/pre-release-program/corsair-preview.md @@ -1,6 +1,6 @@ {% note %} -**注：**要在预览期间访问 {% data variables.product.prodname_unfurls %} API，您必须在 `Accept` 标头中提供自定义[媒体类型](/v3/media)： +**注：**要在预览期间访问 {% data variables.product.prodname_unfurls %} API，您必须在 `Accept` 标头中提供自定义[媒体类型](/rest/overview/media-types)： ``` application/vnd.github.corsair-preview+json diff --git a/translations/zh-CN/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/zh-CN/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md index 6048631d32..c4e5c8f570 100644 --- a/translations/zh-CN/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md +++ b/translations/zh-CN/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} {% note %} **注：**过期用户令牌目前是用户到服务器令牌过期的一部分，可能会更改。 要选择加入用户到服务器令牌过期测试版功能，请参阅“[激活应用程序的测试版功能](/developers/apps/activating-beta-features-for-apps)”。 更多信息请参阅“[GitHub 应用程序过期用户到服务器访问令牌](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)”。 diff --git a/translations/zh-CN/data/reusables/pre-release-program/fury-pre-release.md b/translations/zh-CN/data/reusables/pre-release-program/fury-pre-release.md index 562f0991ed..5e79132817 100644 --- a/translations/zh-CN/data/reusables/pre-release-program/fury-pre-release.md +++ b/translations/zh-CN/data/reusables/pre-release-program/fury-pre-release.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} {% note %} -**注：**{% data variables.product.prodname_github_app %} 清单目前可供开发者预览。 要在预览期间访问此 API，必须在 `Accept` 标头中提供自定义[媒体类型](/v3/media)： +**注：**{% data variables.product.prodname_github_app %} 清单目前可供开发者预览。 要在预览期间访问此 API，必须在 `Accept` 标头中提供自定义[媒体类型](/rest/overview/media-types)： ``` application/vnd.github.fury-preview+json diff --git a/translations/zh-CN/data/reusables/pre-release-program/machine-man-preview.md b/translations/zh-CN/data/reusables/pre-release-program/machine-man-preview.md index d9e6e56720..5e71a9a8fa 100644 --- a/translations/zh-CN/data/reusables/pre-release-program/machine-man-preview.md +++ b/translations/zh-CN/data/reusables/pre-release-program/machine-man-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**注：**要使用 GitHub 应用程序访问 API，您必须在请求的 `Accept` 标头中提供自定义[媒体类型](/v3/media)。 +**注：**要使用 GitHub 应用程序访问 API，您必须在请求的 `Accept` 标头中提供自定义[媒体类型](/rest/overview/media-types)。 `application/vnd.github.machine-man-preview+json` diff --git a/translations/zh-CN/data/reusables/pre-release-program/sailor-v-preview.md b/translations/zh-CN/data/reusables/pre-release-program/sailor-v-preview.md index e80010badb..666de98e89 100644 --- a/translations/zh-CN/data/reusables/pre-release-program/sailor-v-preview.md +++ b/translations/zh-CN/data/reusables/pre-release-program/sailor-v-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**注：**您现在可以使用 REST API 在锁定议题时添加原因，并且在包含议题或拉取请求的响应中会看到锁定原因。 在 `locked` 事件中也会看到锁定原因。 此功能目前可供开发者预览。 有关完整详情，请参阅[博客文章](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview)。 要访问此功能，必须在 `Accept` 标头中提供自定义[媒体类型](/v3/media)： +**注：**您现在可以使用 REST API 在锁定议题时添加原因，并且在包含议题或拉取请求的响应中会看到锁定原因。 在 `locked` 事件中也会看到锁定原因。 此功能目前可供开发者预览。 有关完整详情，请参阅[博客文章](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview)。 要访问此功能，必须在 `Accept` 标头中提供自定义[媒体类型](/rest/overview/media-types)： ``` application/vnd.github.sailor-v-preview+json diff --git a/translations/zh-CN/data/reusables/pre-release-program/starfox-preview.md b/translations/zh-CN/data/reusables/pre-release-program/starfox-preview.md index 8e65a4b83c..4d5cf6abe9 100644 --- a/translations/zh-CN/data/reusables/pre-release-program/starfox-preview.md +++ b/translations/zh-CN/data/reusables/pre-release-program/starfox-preview.md @@ -2,7 +2,7 @@ **注：**项目卡详细信息现在显示在项目相关议题和时间线事件的 REST API 响应中。 此功能现在可供开发者预览。 有关详细信息，请参阅[博客文章](https://developer.github.com/changes/2018-09-05-project-card-events)。 -要接收 `project_card` 属性，必须为仓库[启用](/articles/disabling-project-boards-in-a-repository)项目板，并且必须在 `Accept` 标头中提供自定义[媒体类型](/v3/media)： +要接收 `project_card` 属性，必须为仓库[启用](/articles/disabling-project-boards-in-a-repository)项目板，并且必须在 `Accept` 标头中提供自定义[媒体类型](/rest/overview/media-types)： ``` application/vnd.github.starfox-preview+json diff --git a/translations/zh-CN/data/reusables/repositories/deploy-keys.md b/translations/zh-CN/data/reusables/repositories/deploy-keys.md index 5890f54b8f..077fc2987a 100644 --- a/translations/zh-CN/data/reusables/repositories/deploy-keys.md +++ b/translations/zh-CN/data/reusables/repositories/deploy-keys.md @@ -1 +1 @@ -您可以使用部署密钥从 {% data variables.product.product_name %} 仓库启动项目到服务器，部署密钥是授予访问单个仓库的 SSH 密钥。 {% data variables.product.product_name %} 将密钥的公共部分直接附加到仓库而不是个人用户帐户，密钥的私有部分仍保留在服务器上。 更多信息请参阅“[交付部署](/v3/guides/delivering-deployments/)”。 +您可以使用部署密钥从 {% data variables.product.product_name %} 仓库启动项目到服务器，部署密钥是授予访问单个仓库的 SSH 密钥。 {% data variables.product.product_name %} 将密钥的公共部分直接附加到仓库而不是个人用户帐户，密钥的私有部分仍保留在服务器上。 更多信息请参阅“[交付部署](/rest/guides/delivering-deployments)”。 diff --git a/translations/zh-CN/data/reusables/webhooks/check_run_properties.md b/translations/zh-CN/data/reusables/webhooks/check_run_properties.md index 706bb10e48..17110f4cef 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_run_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/check_run_properties.md @@ -1,7 +1,7 @@ | 键 | 类型 | 描述 | | --------------------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是以下选项之一：
  • `created` - 创建了新的检查运行。
  • `completed` - 检查运行的“状态”为“已完成”。
  • `rerequested` - 有人请求从拉取请求 UI 重新运行检查。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。 收到 `rerequested` 操作时，您需要[创建新的检查运行](/v3/checks/runs/#create-a-check-run)。 仅当有人请求重新运行检查时，{% data variables.product.prodname_github_app %} 才会收到 `rerequested` 有效负载。
  • `requested_action` - 有人请求执行应用程序提供的操作。 仅当有人请求执行操作时，{% data variables.product.prodname_github_app %} 才会收到 `requested_action` 有效负载。 有关检查运行和请求操作的更多信息，请参阅“[检查运行和请求操作](/v3/checks/runs/#check-runs-and-requested-actions)”。
| -| `check_run` | `对象` | [check_run](/v3/checks/runs/#get-a-check-run)。 | +| `action` | `字符串` | 执行的操作。 可以是以下选项之一：
  • `created` - 创建了新的检查运行。
  • `completed` - 检查运行的“状态”为“已完成”。
  • `rerequested` - 有人请求从拉取请求 UI 重新运行检查。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。 When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). 仅当有人请求重新运行检查时，{% data variables.product.prodname_github_app %} 才会收到 `rerequested` 有效负载。
  • `requested_action` - 有人请求执行应用程序提供的操作。 仅当有人请求执行操作时，{% data variables.product.prodname_github_app %} 才会收到 `requested_action` 有效负载。 To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `check_run` | `对象` | [check_run](/rest/reference/checks#get-a-check-run)。 | | `check_run[status]` | `字符串` | 检查运行的当前状态。 可以是 `queued`、`in_progress` 或 `completed`。 | | `check_run[conclusion]` | `字符串` | 已完成检查运行的结果。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. 此值将为 `null`，直到检查运行 `completed`。 | | `check_run[name]` | `字符串` | 检查运行的名称。 | diff --git a/translations/zh-CN/data/reusables/webhooks/check_run_short_desc.md b/translations/zh-CN/data/reusables/webhooks/check_run_short_desc.md index d04d32eff0..eab069fc6b 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_run_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/check_run_short_desc.md @@ -1 +1 @@ -检查运行活动已发生。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[检查运行](/v3/checks/runs/)”REST API。 +检查运行活动已发生。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[检查运行](/rest/reference/checks#runs)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md index 90f0d5e98e..bb341aa3c0 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md @@ -1,7 +1,7 @@ | 键 | 类型 | 描述 | | ---------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是：
  • `completed` - 检查套件中的所有检查运行已完成。
  • `requested` - 新代码被推送到应用程序的仓库时发生。 收到 `requested` 操作事件时，您需要[创建新的检查运行](/v3/checks/runs/#create-a-check-run)。
  • `rerequested` - 有人请求从拉取请求 UI 重新运行整个检查套件时发生。 收到 `rerequested` 操作事件时，您需要[创建新的检查运行](/v3/checks/runs/#create-a-check-run)。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。
| -| `check_suite` | `对象` | [check_suite](/v3/checks/suites/)。 | +| `action` | `字符串` | 执行的操作。 可以是：
  • `completed` - 检查套件中的所有检查运行已完成。
  • `requested` - 新代码被推送到应用程序的仓库时发生。 When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).
  • `rerequested` - 有人请求从拉取请求 UI 重新运行整个检查套件时发生。 When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。
| +| `check_suite` | `对象` | [check_suite](/rest/reference/checks#suites)。 | | `check_suite[head_branch]` | `字符串` | 更改所在的头部分支的名称。 | | `check_suite[head_sha]` | `字符串` | 此检查套件的最新提交的 SHA。 | | `check_suite[status]` | `字符串` | 检查套件中所有检查运行的摘要状态。 可以是 `requested`、`in_progress` 或 `completed`。 | diff --git a/translations/zh-CN/data/reusables/webhooks/check_suite_short_desc.md b/translations/zh-CN/data/reusables/webhooks/check_suite_short_desc.md index c78ba5295e..03912af221 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_suite_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/check_suite_short_desc.md @@ -1 +1 @@ -检查套件活动已发生。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[检查套件](/v3/checks/suites/)”REST API。 +检查套件活动已发生。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[检查套件](/rest/reference/checks#suites)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/commit_comment_properties.md b/translations/zh-CN/data/reusables/webhooks/commit_comment_properties.md index e002e6bb8c..8c60a240f2 100644 --- a/translations/zh-CN/data/reusables/webhooks/commit_comment_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/commit_comment_properties.md @@ -1,4 +1,4 @@ -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `created`。 | -| `注释，评论` | `对象` | [提交评论](/v3/repos/comments/#get-a-commit-comment)资源。 | +| 键 | 类型 | 描述 | +| -------- | ----- | ----------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是 `created`。 | +| `注释，评论` | `对象` | [提交评论](/rest/reference/repos#get-a-commit-comment)资源。 | diff --git a/translations/zh-CN/data/reusables/webhooks/commit_comment_short_desc.md b/translations/zh-CN/data/reusables/webhooks/commit_comment_short_desc.md index 087dfcc5b2..8346f3ed08 100644 --- a/translations/zh-CN/data/reusables/webhooks/commit_comment_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/commit_comment_short_desc.md @@ -1 +1 @@ -提交评论已创建。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[提交评论](/v3/repos/comments/)”REST API。 +提交评论已创建。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[提交评论](/rest/reference/repos#comments)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/create_properties.md b/translations/zh-CN/data/reusables/webhooks/create_properties.md index c7f6d5f209..c12889d7a2 100644 --- a/translations/zh-CN/data/reusables/webhooks/create_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/create_properties.md @@ -1,6 +1,6 @@ | 键 | 类型 | 描述 | | --------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `字符串` | The [`git ref`](/v3/git/refs/#get-a-reference) 资源。 | +| `ref` | `字符串` | The [`git ref`](/rest/reference/git#get-a-reference) 资源。 | | `ref_type` | `字符串` | 在仓库中创建的 Git ref 对象的类型。 可以是 `branch` 或 `tag`。 | | `master_branch` | `字符串` | 仓库默认分支的名称（通常是 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" %}`main`{% else %}`master`{% endif %}）。 | | `说明` | `字符串` | 仓库的当前描述。 | diff --git a/translations/zh-CN/data/reusables/webhooks/create_short_desc.md b/translations/zh-CN/data/reusables/webhooks/create_short_desc.md index 7f4e070b37..1114a9364f 100644 --- a/translations/zh-CN/data/reusables/webhooks/create_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/create_short_desc.md @@ -1 +1 @@ -Git 分支或标签已创建。 更多信息请参阅“[Git 数据](/v3/git/)”REST API。 +Git 分支或标签已创建。 更多信息请参阅“[Git 数据](/rest/reference/git)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/delete_properties.md b/translations/zh-CN/data/reusables/webhooks/delete_properties.md index 6e97f966e8..8cd4ee0dd5 100644 --- a/translations/zh-CN/data/reusables/webhooks/delete_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ -| 键 | 类型 | 描述 | -| ---------- | ----- | -------------------------------------------------- | -| `ref` | `字符串` | The [`git ref`](/v3/git/refs/#get-a-reference) 资源。 | -| `ref_type` | `字符串` | 在仓库中删除的 Git ref 对象的类型。 可以是 `branch` 或 `tag`。 | +| 键 | 类型 | 描述 | +| ---------- | ----- | -------------------------------------------------------- | +| `ref` | `字符串` | The [`git ref`](/rest/reference/git#get-a-reference) 资源。 | +| `ref_type` | `字符串` | 在仓库中删除的 Git ref 对象的类型。 可以是 `branch` 或 `tag`。 | diff --git a/translations/zh-CN/data/reusables/webhooks/delete_short_desc.md b/translations/zh-CN/data/reusables/webhooks/delete_short_desc.md index 9b8896f556..d97842b647 100644 --- a/translations/zh-CN/data/reusables/webhooks/delete_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/delete_short_desc.md @@ -1 +1 @@ -Git 分支或标签已删除。 更多信息请参阅“[Git 数据](/v3/git/)”REST API。 +Git 分支或标签已删除。 更多信息请参阅“[Git 数据](/rest/reference/git)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/deploy_key_properties.md b/translations/zh-CN/data/reusables/webhooks/deploy_key_properties.md index a1782e632a..a93737fe57 100644 --- a/translations/zh-CN/data/reusables/webhooks/deploy_key_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/deploy_key_properties.md @@ -1,4 +1,4 @@ -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `created` 或 `deleted`。 | -| `键` | `对象` | [`部署密钥`](/v3/repos/keys/#get-a-deploy-key)资源。 | +| 键 | 类型 | 描述 | +| -------- | ----- | --------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是 `created` 或 `deleted`。 | +| `键` | `对象` | [`部署密钥`](/rest/reference/repos#get-a-deploy-key)资源。 | diff --git a/translations/zh-CN/data/reusables/webhooks/deploy_key_short_desc.md b/translations/zh-CN/data/reusables/webhooks/deploy_key_short_desc.md index 2208f286a5..5c074ec323 100644 --- a/translations/zh-CN/data/reusables/webhooks/deploy_key_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/deploy_key_short_desc.md @@ -1 +1 @@ -在仓库中添加或删除部署密钥。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[部署密钥](/v3/repos/keys/)”REST API。 +在仓库中添加或删除部署密钥。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[部署密钥](/rest/reference/repos#keys)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/fork_properties.md b/translations/zh-CN/data/reusables/webhooks/fork_properties.md index 241e51cba6..c558ec7171 100644 --- a/translations/zh-CN/data/reusables/webhooks/fork_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/fork_properties.md @@ -1,3 +1,3 @@ -| 键 | 类型 | 描述 | -| -------- | ---- | --------------------------------------------------- | -| `forkee` | `对象` | 创建的 [`repository`](/v3/repos/#get-a-repository) 资源。 | +| 键 | 类型 | 描述 | +| -------- | ---- | -------------------------------------------------------------- | +| `forkee` | `对象` | 创建的 [`repository`](/rest/reference/repos#get-a-repository) 资源。 | diff --git a/translations/zh-CN/data/reusables/webhooks/fork_short_desc.md b/translations/zh-CN/data/reusables/webhooks/fork_short_desc.md index 821bc1028c..6280c4b6ac 100644 --- a/translations/zh-CN/data/reusables/webhooks/fork_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/fork_short_desc.md @@ -1 +1 @@ -用户复刻仓库。 更多信息请参阅“[复刻](/v3/repos/forks/)”REST API。 +用户复刻仓库。 更多信息请参阅“[复刻](/rest/reference/repos#forks)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/zh-CN/data/reusables/webhooks/installation_repositories_short_desc.md index cce2174940..0bfa25ae43 100644 --- a/translations/zh-CN/data/reusables/webhooks/installation_repositories_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/installation_repositories_short_desc.md @@ -1 +1 @@ -与要添加到 GitHub 应用程序安装中的仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[GitHub 应用程序安装](/v3/apps/)”REST API。 +与要添加到 GitHub 应用程序安装中的仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[GitHub 应用程序安装](/rest/reference/apps)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/installation_short_desc.md b/translations/zh-CN/data/reusables/webhooks/installation_short_desc.md index 0c881c7132..264c870bbb 100644 --- a/translations/zh-CN/data/reusables/webhooks/installation_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/installation_short_desc.md @@ -1 +1 @@ -与 GitHub 应用程序安装相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[GitHub 应用程序安装](/v3/apps/)”REST API。 +与 GitHub 应用程序安装相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[GitHub 应用程序安装](/rest/reference/apps)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/issue_comment_properties.md b/translations/zh-CN/data/reusables/webhooks/issue_comment_properties.md index 7e2bdb5a6e..6483111bc1 100644 --- a/translations/zh-CN/data/reusables/webhooks/issue_comment_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/issue_comment_properties.md @@ -1 +1 @@ -`changes`|`object` | 对评论的更改，如果操作为 `edited`。 `changes[body][from]` |`string` | 正文的前版本，如果操作为 `edited`。 `issue`|`object` | 评论所属的[议题](/v3/issues/)。 `comment`|`object` | [评论](/v3/issues/comments/)本身。 +`changes`|`object` | 对评论的更改，如果操作为 `edited`。 `changes[body][from]` |`string` | 正文的前版本，如果操作为 `edited`。 `issue`|`object` | 评论所属的[议题](/rest/reference/issues)。 `comment`|`object` | [评论](/rest/reference/issues#comments)本身。 diff --git a/translations/zh-CN/data/reusables/webhooks/issue_comment_short_desc.md b/translations/zh-CN/data/reusables/webhooks/issue_comment_short_desc.md index 4aecf69936..1384969111 100644 --- a/translations/zh-CN/data/reusables/webhooks/issue_comment_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/issue_comment_short_desc.md @@ -1 +1 @@ -与议题评论相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[议题评论](/v3/issues/comments/)”REST API。 +与议题评论相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[议题评论](/rest/reference/issues#comments)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/issue_properties.md b/translations/zh-CN/data/reusables/webhooks/issue_properties.md index 482264aeb8..b7b084c534 100644 --- a/translations/zh-CN/data/reusables/webhooks/issue_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/issue_properties.md @@ -1 +1 @@ -`issue`|`object` | [议题](/v3/issues)本身。 `changes`|`object` | 对议题的更改，如果操作为 `edited`。 `changes[title][from]` |`string` | 标题的前版本，如果操作为 `edited`。 `changes[body][from]`|`string` | 正文的前版本，如果操作为 `edited`。 `assignee`|`object` | 为此议题分配或取消分配的可选用户。 `label`|`object` | 为此议题添加或删除的可选标签。 +`issue`|`object` | [议题](/rest/reference/issues)本身。 `changes`|`object` | 对议题的更改，如果操作为 `edited`。 `changes[title][from]` |`string` | 标题的前版本，如果操作为 `edited`。 `changes[body][from]`|`string` | 正文的前版本，如果操作为 `edited`。 `assignee`|`object` | 为此议题分配或取消分配的可选用户。 `label`|`object` | 为此议题添加或删除的可选标签。 diff --git a/translations/zh-CN/data/reusables/webhooks/issues_short_desc.md b/translations/zh-CN/data/reusables/webhooks/issues_short_desc.md index ee50f3a6cf..afc92d15a4 100644 --- a/translations/zh-CN/data/reusables/webhooks/issues_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/issues_short_desc.md @@ -1 +1 @@ -与议题相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[议题](/v3/issues/comments/)”REST API。 +与议题相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[议题](/rest/reference/issues#comments)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/label_short_desc.md b/translations/zh-CN/data/reusables/webhooks/label_short_desc.md index 51f8630979..1d93ebdbc0 100644 --- a/translations/zh-CN/data/reusables/webhooks/label_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/label_short_desc.md @@ -1 +1 @@ -与议题相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[标签](/v3/issues/labels/)”REST API。 +与议题相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[标签](/rest/reference/issues#labels)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/member_properties.md b/translations/zh-CN/data/reusables/webhooks/member_properties.md index bfd42110f5..a189d9eab2 100644 --- a/translations/zh-CN/data/reusables/webhooks/member_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/member_properties.md @@ -1 +1 @@ -`member`|`object` | 已添加的[用户](/v3/users/)。 `changes`|`object`| 对协作者权限的更改，如果操作为 `edited`。 `changes[old_permission][from]`|`string` | 协作者以前的权限，如果操作为 `edited`。 +`member`|`object` | 已添加的[用户](/rest/reference/users)。 `changes`|`object`| 对协作者权限的更改，如果操作为 `edited`。 `changes[old_permission][from]`|`string` | 协作者以前的权限，如果操作为 `edited`。 diff --git a/translations/zh-CN/data/reusables/webhooks/member_short_desc.md b/translations/zh-CN/data/reusables/webhooks/member_short_desc.md index a519776886..a49fdea6c6 100644 --- a/translations/zh-CN/data/reusables/webhooks/member_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/member_short_desc.md @@ -1 +1 @@ -与仓库协作者相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[协作者](/v3/repos/collaborators/)”REST API。 +与仓库协作者相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[协作者](/rest/reference/repos#collaborators)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/membership_properties.md b/translations/zh-CN/data/reusables/webhooks/membership_properties.md index 7e8543da2d..e21ed1e6ff 100644 --- a/translations/zh-CN/data/reusables/webhooks/membership_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/membership_properties.md @@ -1,6 +1,6 @@ -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是 `added` 或 `removed`。 | -| `作用域` | `字符串` | 成员的作用域。 目前只能是 `team`。 | -| `成员` | `对象` | 已添加或删除的[用户](/v3/users/)。 | -| `团队` | `对象` | 成员的[团队](/v3/teams/)。 | +| 键 | 类型 | 描述 | +| -------- | ----- | ----------------------------------- | +| `action` | `字符串` | 执行的操作内容. 可以是 `added` 或 `removed`。 | +| `作用域` | `字符串` | 成员的作用域。 目前只能是 `team`。 | +| `成员` | `对象` | 已添加或删除的[用户](/rest/reference/users)。 | +| `团队` | `对象` | 成员的[团队](/rest/reference/teams)。 | diff --git a/translations/zh-CN/data/reusables/webhooks/membership_short_desc.md b/translations/zh-CN/data/reusables/webhooks/membership_short_desc.md index 91ad7000e5..35f78c80c6 100644 --- a/translations/zh-CN/data/reusables/webhooks/membership_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/membership_short_desc.md @@ -1 +1 @@ -与团队成员相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[团队成员](/v3/teams/members/)”REST API。 +与团队成员相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[团队成员](/rest/reference/teams#members)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/milestone_short_desc.md b/translations/zh-CN/data/reusables/webhooks/milestone_short_desc.md index da6685490f..794399c3f2 100644 --- a/translations/zh-CN/data/reusables/webhooks/milestone_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/milestone_short_desc.md @@ -1 +1 @@ -与里程碑相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[里程碑](/v3/issues/milestones/)”REST API。 +与里程碑相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[里程碑](/rest/reference/issues#milestones)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md b/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md index c7a86e57c4..8918e36a2c 100644 --- a/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -与组织中被阻止人员相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[阻止组织用户](/v3/orgs/blocking/)”REST API。 +与组织中被阻止人员相关的活动。 {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. diff --git a/translations/zh-CN/data/reusables/webhooks/org_desc.md b/translations/zh-CN/data/reusables/webhooks/org_desc.md index 67dae97656..7f3b3d1196 100644 --- a/translations/zh-CN/data/reusables/webhooks/org_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/org_desc.md @@ -1 +1 @@ -`organization` | `object` | 当为组织配置了 web 挂钩或事件是由于组织所拥有仓库中的活动而发生时，web 挂钩有效负载包含 [`organization`](/v3/orgs/#get-an-organization) 对象。 +`organization` | `object` | 当为组织配置了 web 挂钩或事件是由于组织所拥有仓库中的活动而发生时，web 挂钩有效负载包含 [`organization`](/rest/reference/orgs#get-an-organization) 对象。 diff --git a/translations/zh-CN/data/reusables/webhooks/organization_short_desc.md b/translations/zh-CN/data/reusables/webhooks/organization_short_desc.md index f77bf1d99b..7681e5aa10 100644 --- a/translations/zh-CN/data/reusables/webhooks/organization_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/organization_short_desc.md @@ -1 +1 @@ -与组织及其成员相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[组织](/v3/orgs/)”REST API。 +与组织及其成员相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[组织](/rest/reference/orgs)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/project_card_properties.md b/translations/zh-CN/data/reusables/webhooks/project_card_properties.md index e06df58160..63ed34d081 100644 --- a/translations/zh-CN/data/reusables/webhooks/project_card_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/project_card_properties.md @@ -4,4 +4,4 @@ | `changes` | `对象` | 对项目卡的更改，如果操作为 `edited` 或 `converted`。 | | `changes[note][from]` | `字符串` | 备注的先前版本，如果操作为 `edited` 或 `converted`。 | | `after_id` | `整数` | 此卡现在所遵循的卡的 ID，如果操作为 "moved"。 将为 `null`，如果它是列中的第一张卡。 | -| `project_card` | `对象` | [项目卡](/v3/projects/cards)本身。 | +| `project_card` | `对象` | [项目卡](/rest/reference/projects#cards)本身。 | diff --git a/translations/zh-CN/data/reusables/webhooks/project_card_short_desc.md b/translations/zh-CN/data/reusables/webhooks/project_card_short_desc.md index 7f0fd14ad2..78fdfcc85a 100644 --- a/translations/zh-CN/data/reusables/webhooks/project_card_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/project_card_short_desc.md @@ -1 +1 @@ -与项目卡有关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[项目卡](/v3/projects/cards)”REST API。 +与项目卡有关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[项目卡](/rest/reference/projects#cards)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/project_column_properties.md b/translations/zh-CN/data/reusables/webhooks/project_column_properties.md index dc28a20499..80f53b0dc0 100644 --- a/translations/zh-CN/data/reusables/webhooks/project_column_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/project_column_properties.md @@ -4,4 +4,4 @@ | `changes` | `对象` | 对项目列的更改，如果操作为 `edited`。 | | `changes[name][from]` | `字符串` | 名称的先前版本（如果操作为 `edited`）。 | | `after_id` | `整数` | 此列现在所遵循的列的 ID，如果操作为 "moved"。 将为 `null`，如果它是项目中的第一列。 | -| `project_column` | `对象` | [项目列](/v3/projects/columns)本身。 | +| `project_column` | `对象` | [项目列](/rest/reference/projects#columns)本身。 | diff --git a/translations/zh-CN/data/reusables/webhooks/project_column_short_desc.md b/translations/zh-CN/data/reusables/webhooks/project_column_short_desc.md index 04efb55943..7034f508ea 100644 --- a/translations/zh-CN/data/reusables/webhooks/project_column_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/project_column_short_desc.md @@ -1 +1 @@ -与项目板中的列相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[项目列](/v3/projects/columns)”REST API。 +与项目板中的列相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[项目列](/rest/reference/projects#columns)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/project_properties.md b/translations/zh-CN/data/reusables/webhooks/project_properties.md index f9356360e8..2e1976dc0a 100644 --- a/translations/zh-CN/data/reusables/webhooks/project_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/project_properties.md @@ -4,4 +4,4 @@ | `changes` | `对象` | 对项目的更改，如果操作为 `edited`。 | | `changes[name][from]` | `字符串` | 名称的先前版本（如果操作为 `edited`）。 | | `changes[body][from]` | `字符串` | 正文的先前版本，如果操作为 `edited`。 | -| `project` | `对象` | [项目](/v3/projects/)本身。 | +| `project` | `对象` | [项目](/rest/reference/projects)本身。 | diff --git a/translations/zh-CN/data/reusables/webhooks/project_short_desc.md b/translations/zh-CN/data/reusables/webhooks/project_short_desc.md index 4618876133..b938e32bfc 100644 --- a/translations/zh-CN/data/reusables/webhooks/project_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/project_short_desc.md @@ -1 +1 @@ -与项目板有关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[项目](/v3/projects)”REST API。 +与项目板有关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[项目](/rest/reference/projects)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_properties.md b/translations/zh-CN/data/reusables/webhooks/pull_request_properties.md index d54fdab161..89690be3df 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_properties.md @@ -1 +1 @@ -`number`|`integer` | 拉取请求编号。 `changes`|`object`| 对评论的更改，如果操作为 `edited`。 `changes[title][from]` |`string` | 标题的前版本，如果操作为 `edited`。 `changes[body][from]`|`string` | 正文的前版本，如果操作为 `edited`。 `pull_request`|`object` | [拉取请求](/v3/pulls)本身。 +`number`|`integer` | 拉取请求编号。 `changes`|`object`| 对评论的更改，如果操作为 `edited`。 `changes[title][from]` |`string` | 标题的前版本，如果操作为 `edited`。 `changes[body][from]`|`string` | 正文的前版本，如果操作为 `edited`。 `pull_request`|`object` | [拉取请求](/rest/reference/pulls)本身。 diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_properties.md index e0323d5dd2..5805fd0072 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_properties.md @@ -1 +1 @@ -`changes`|`object`| 对评论的更改，如果操作为 `edited`。 `changes[body][from]`|`string` | 正文的前版本，如果操作为 `edited`。 `pull_request`|`object` | 评论所属的[拉取请求](/v3/pulls/)。 `comment`|`object` | [评论](/v3/pulls/comments)本身。 +`changes`|`object`| 对评论的更改，如果操作为 `edited`。 `changes[body][from]`|`string` | 正文的前版本，如果操作为 `edited`。 `pull_request`|`object` | 评论所属的[拉取请求](/rest/reference/pulls)。 `comment`|`object` | [评论](/rest/reference/pulls#comments)本身。 diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_short_desc.md index 848c71256f..5b71fc5cc5 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_review_comment_short_desc.md @@ -1 +1 @@ -与拉取请求统一差异中的拉取请求审查评论相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[拉取请求审查评论](/v3/pulls/comments/)”REST API。 +与拉取请求统一差异中的拉取请求审查评论相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[拉取请求审查评论](/rest/reference/pulls#comments)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_review_properties.md b/translations/zh-CN/data/reusables/webhooks/pull_request_review_properties.md index 827a057767..43fea0a08b 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ | 键 | 类型 | 描述 | | --------------------- | ----- | -------------------------------------------- | | `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
  • `submitted` - 拉取请求审查被提交为非挂起状态。
  • `edited` - 审查的正文被编辑。
  • `dismissed` - 审查被驳回。
| -| `pull_request` | `对象` | 与审查相关的[拉取请求](/v3/pulls/)。 | +| `pull_request` | `对象` | 与审查相关的[拉取请求](/rest/reference/pulls)。 | | `审查` | `对象` | 受影响的审查。 | | `changes[body][from]` | `字符串` | 正文的先前版本，如果操作为 `edited`。 | diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/zh-CN/data/reusables/webhooks/pull_request_review_short_desc.md index e00ca18bd1..c07ec1954d 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_review_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_review_short_desc.md @@ -1 +1 @@ -与拉取请求审查相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[拉取请求审查](/v3/pulls/reviews/)”REST API。 +与拉取请求审查相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[拉取请求审查](/rest/reference/pulls#reviews)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_short_desc.md b/translations/zh-CN/data/reusables/webhooks/pull_request_short_desc.md index 18cbe46c0f..f70797ecdd 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_short_desc.md @@ -1 +1 @@ -与拉取请求相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[拉取请求](/v3/pulls/)”REST API。 +与拉取请求相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[拉取请求](/rest/reference/pulls)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/release_short_desc.md b/translations/zh-CN/data/reusables/webhooks/release_short_desc.md index 7ba263d680..6a63d1b3a4 100644 --- a/translations/zh-CN/data/reusables/webhooks/release_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/release_short_desc.md @@ -1 +1 @@ -与发行版相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[发行版](/v3/repos/releases/)”REST API。 +与发行版相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[发行版](/rest/reference/repos#releases)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/repo_desc.md b/translations/zh-CN/data/reusables/webhooks/repo_desc.md index df26fb3e7a..e0eca4218d 100644 --- a/translations/zh-CN/data/reusables/webhooks/repo_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/repo_desc.md @@ -1 +1 @@ -`repository` | `object` | The [`repository`](/v3/repos/#get-a-repository) where the event occurred. +`repository` | `object` | The [`repository`](/rest/reference/repos#get-a-repository) where the event occurred. diff --git a/translations/zh-CN/data/reusables/webhooks/repository_import_short_desc.md b/translations/zh-CN/data/reusables/webhooks/repository_import_short_desc.md index 41ae6ed3e0..54a4ada40d 100644 --- a/translations/zh-CN/data/reusables/webhooks/repository_import_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/repository_import_short_desc.md @@ -1 +1 @@ -与导入到 GitHub 的仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[源导入](/v3/migrations/source_imports/)”REST API。 +与导入到 GitHub 的仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[源导入](/rest/reference/migrations#source-imports)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/repository_short_desc.md b/translations/zh-CN/data/reusables/webhooks/repository_short_desc.md index f9d71939fb..b8e0f3ff35 100644 --- a/translations/zh-CN/data/reusables/webhooks/repository_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/repository_short_desc.md @@ -1 +1 @@ -与仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[仓库](/v3/repos/)”REST API。 +与仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[仓库](/rest/reference/repos)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/star_short_desc.md b/translations/zh-CN/data/reusables/webhooks/star_short_desc.md index d6558f5023..20450ebdd6 100644 --- a/translations/zh-CN/data/reusables/webhooks/star_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/star_short_desc.md @@ -1 +1 @@ -与标星仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[星标](/v3/activity/starring/)”REST API。 +与标星仓库相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[星标](/rest/reference/activity#starring)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/status_short_desc.md b/translations/zh-CN/data/reusables/webhooks/status_short_desc.md index f8760145ca..4bce79eef4 100644 --- a/translations/zh-CN/data/reusables/webhooks/status_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/status_short_desc.md @@ -1 +1 @@ -当 Git 提交的状态发生更改时。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[状态](/v3/repos/statuses/)”REST API。 +当 Git 提交的状态发生更改时。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[状态](/rest/reference/repos#statuses)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/team_add_short_desc.md b/translations/zh-CN/data/reusables/webhooks/team_add_short_desc.md index cd1a909fb4..f1c9f82819 100644 --- a/translations/zh-CN/data/reusables/webhooks/team_add_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/team_add_short_desc.md @@ -1 +1 @@ -当[仓库被添加到团队](/v3/teams/#add-or-update-team-repository-permissions)时。 +当[仓库被添加到团队](/rest/reference/teams#add-or-update-team-repository-permissions)时。 diff --git a/translations/zh-CN/data/reusables/webhooks/team_short_desc.md b/translations/zh-CN/data/reusables/webhooks/team_short_desc.md index 9051cc86c1..ca5fc7ce67 100644 --- a/translations/zh-CN/data/reusables/webhooks/team_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/team_short_desc.md @@ -1 +1 @@ -与组织的团队相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[团队](/v3/teams/)”REST API。 +与组织的团队相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[团队](/rest/reference/teams)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/watch_short_desc.md b/translations/zh-CN/data/reusables/webhooks/watch_short_desc.md index 1afc08229b..20be0d9b0c 100644 --- a/translations/zh-CN/data/reusables/webhooks/watch_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/watch_short_desc.md @@ -1 +1 @@ -当有人标星仓库时。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[星标](/v3/activity/starring/)”REST API。 +当有人标星仓库时。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[星标](/rest/reference/activity#starring)”REST API。