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 131a590d61f2..f546e9f5e117 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 @@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - potatoqualitee --- {% data reusables.actions.enterprise-beta %} 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 new file mode 100644 index 000000000000..7d2ef5507889 --- /dev/null +++ b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md @@ -0,0 +1,318 @@ +--- +title: Building and testing Ruby +intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Einführung + +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. + +### Vorrausetzungen + +We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. Weitere Informationen findest Du unter: + +- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions) +- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) + +### Starting with the Ruby workflow template + +{% 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). + +Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein. + +{% raw %} +```yaml +name: Ruby + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: 2.6 + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Specifying the Ruby version + +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). + +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. + +The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 # Not needed with a .ruby-version file +- run: bundle install +- run: bundle exec rake +``` +{% 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. + +### Testing with multiple versions of 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. + +{% raw %} +```yaml +strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] +``` +{% 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." + +The full updated workflow with a matrix strategy could look like this: + +{% raw %} +```yaml +name: Ruby CI + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby ${{ matrix.ruby-version }} + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: ${{ matrix.ruby-version }} + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Installing dependencies with 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. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 +- run: bundle install +``` +{% endraw %} + +#### Abhängigkeiten „cachen“ (zwischenspeichern) + +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 +steps: +- uses: ruby/setup-ruby@v1 + with: + bundler-cache: true +``` +{% 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. + +**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)“. + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + ${{ runner.os }}-gems- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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: + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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. + +{% raw %} +```yaml +name: Matrix Testing + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + runs-on: ${{ matrix.os }}-latest + strategy: + fail-fast: false + matrix: + os: [ubuntu, macos] + ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head] + continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }} + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: ${{ matrix.ruby }} + - run: bundle install + - run: bundle exec rake +``` +{% 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. + +{% raw %} +```yaml +name: Linting + +on: [push] + +jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + - name: Rubocop + run: rubocop +``` +{% endraw %} + +### Publishing Gems + +You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. + +You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. + +{% raw %} +```yaml + +name: Ruby Gem + +on: + # Manually publish + workflow_dispatch: + # Alternatively, publish whenever changes are merged to the default branch. + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + build: + name: Build + Publish + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby 2.6 + uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + + - name: Publish to GPR + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem + env: + GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}" + OWNER: ${{ github.repository_owner }} + + - name: Publish to RubyGems + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push *.gem + env: + GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" +``` +{% endraw %} + diff --git a/translations/de-DE/content/actions/guides/index.md b/translations/de-DE/content/actions/guides/index.md index 9cb36676dc57..54857c133718 100644 --- a/translations/de-DE/content/actions/guides/index.md +++ b/translations/de-DE/content/actions/guides/index.md @@ -31,6 +31,7 @@ You can use {% data variables.product.prodname_actions %} to create custom conti {% 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/de-DE/content/actions/guides/publishing-nodejs-packages.md b/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md index 944534e21d85..c8e4b8c16fba 100644 --- a/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/de-DE/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/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 3e47530f79a9..c4f5928c6e8d 100644 --- a/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/de-DE/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/de-DE/content/actions/index.md b/translations/de-DE/content/actions/index.md index dc7833d42286..8249d439734c 100644 --- a/translations/de-DE/content/actions/index.md +++ b/translations/de-DE/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 - date: '2020-10-16' - href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ + title: Removing set-env and add-path commands on November 16 + date: '2020-11-09' + href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - 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: Ubuntu-latest workflows will use 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: 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: MacOS Big Sur Preview + date: '2020-10-29' + href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview - - 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 + title: Self-Hosted Runner Group Access Changes + date: '2020-10-16' + href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ 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 %}
-

More guides

+

Code examples

+ +
+ +
-
- -
-

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 -
- -
+ {% render 'code-example-card' for actionsCodeExamples as example %}
- Show all guides {% octicon "arrow-right" %} + + +
+
{% octicon "search" width="24" %}
+

Sorry, there is no result for

+

It looks like we don't have an example that fits your filter.
Try another filter or add your code example

+ Learn how to add a code example {% octicon "arrow-right" %} +
+{% endif %} diff --git a/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md index 24b55078a7dc..7747872bbbb0 100644 --- a/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -42,7 +42,7 @@ A job is a set of steps that execute on the same runner. By default, a workflow #### Steps -A step is an individual task that can run commands (known as _actions_). Each step in a job executes on the same runner, allowing the actions in that job to share data with each other. +A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. Each step in a job executes on the same runner, allowing the actions in that job to share data with each other. #### Actions @@ -50,7 +50,7 @@ _Actions_ are standalone commands that are combined into _steps_ to create a _jo #### Runners -A runner is a server that has the {% data variables.product.prodname_actions %} runner application installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment. +A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS. For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)." @@ -197,7 +197,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s #### Visualizing the workflow file -In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action. Steps 1 and 2 use prebuilt community actions. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." +In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell command. Steps 1 and 2 use prebuilt community actions. Steps 3 and 4 run shell commands directly on the runner. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." ![Workflow overview](/assets/images/help/images/overview-actions-event.png) diff --git a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md index 11dee1a075dc..09907159f4e8 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/de-DE/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/de-DE/content/actions/quickstart.md b/translations/de-DE/content/actions/quickstart.md index 501739723c6d..0f2ce1770ccf 100644 --- a/translations/de-DE/content/actions/quickstart.md +++ b/translations/de-DE/content/actions/quickstart.md @@ -73,3 +73,69 @@ The super-linter workflow you just added runs any time code is pushed to your re - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial - "[Guides](/actions/guides)" for specific uses cases and examples - [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action + + 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 82b4892eb9cf..ca7513299ac3 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 @@ -327,6 +327,7 @@ The `issue_comment` event occurs for comments on both issues and pull requests. 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 @@ -349,6 +350,7 @@ jobs: - run: | echo "Comment on issue #${{ github.event.issue.number }}" ``` +{% endraw %} #### `Issues (Lieferungen)` @@ -540,7 +542,7 @@ Führt Deinen Workflow aus, wenn das Ereignis `pull_request_review` eintritt. {% {% data reusables.developer-site.limit_workflow_to_activity_types %} -Du kannst einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review bearbeitet (`edited`) oder verworfen (`dismissed`) wurde. +Sie können einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review bearbeitet (`edited`) oder verworfen (`dismissed`) wurde. ```yaml on: @@ -560,7 +562,7 @@ Führt den Workflow aus, wenn ein Kommentar zum vereinheitlichten Diff für eine {% data reusables.developer-site.limit_workflow_to_activity_types %} -Du kannst einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review-Kommentar erstellt (`created`) oder gelöscht (`deleted`) wurde. +Sie können einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review-Kommentar erstellt (`created`) oder gelöscht (`deleted`) wurde. ```yaml on: diff --git a/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md index d81032eca47e..894b1f477a97 100644 --- a/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md @@ -31,7 +31,7 @@ Du kannst in einem Workflow für jeden Job die Art des Runners festlegen. Jeder {% data variables.product.prodname_dotcom %} betreibt Linux- und Windows-Runner auf den virtuellen Maschinen nach Standard_DS2_v2 in Microsoft Azure, auf denen die Runner-Anwendung der {% data variables.product.prodname_actions %} installiert ist. Die Runner-Anwendung auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ist eine Fork-Kopie des Azure-Pipelines-Agenten. Bei Azure werden eingehende ICMP-Pakete werden für alle virtuellen Maschinen blockiert, so dass die Befehle ping und traceroute möglicherweise nicht funktionieren. Weitere Informationen zu den Ressourcen der Standard_DS2_v2-Maschinen findest Du unter „[Serien Dv2 und DSv2](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)“ in der Dokumentation zu Microsoft Azure. -{% data variables.product.prodname_dotcom %} verwendet [MacStadium](https://www.macstadium.com/), um die virtuellen macOS-Runner zu betreiben. +{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud. #### Administrative Rechte von {% data variables.product.prodname_dotcom %}-gehosteten Runnern 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 732091080a7e..ddc7b87f4950 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 @@ -446,7 +446,7 @@ 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`** @@ -492,7 +492,7 @@ 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 @@ -659,7 +659,7 @@ Für integrierte Shell-Stichwörter gelten die folgenden Standards, die durch au - `cmd` - Wenn Du das Fail-Fast-Verhalten uneingeschränkt nutzen möchtest, hast Du anscheinend keine andere Wahl, als Dein Skript so zu schreiben, dass jeder Fehlercode geprüft und eine entsprechende Reaktion eingeleitet wird. Dieses Verhalten kann nicht standardmäßig bereitgestellt werden; Du musst es explizit in Dein Skript schreiben. - - `cmd.exe` wird mit dem Errorlevel des zuletzt ausgeführten Programms beendet, und dieser Fehlercode wird an den Runner übergeben. Dieses Verhalten ist intern mit dem vorherigen Standardverhalten von `sh` und `pwsh` konsistent und ist der Standard für `cmd.exe`, weshalb dieses Verhalten unverändert bleibt. + - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. Dieses Verhalten ist intern mit dem vorherigen Standardverhalten von `sh` und `pwsh` konsistent und ist der Standard für `cmd.exe`, weshalb dieses Verhalten unverändert bleibt. #### **`jobs..steps.with`** @@ -718,7 +718,7 @@ steps: entrypoint: /a/different/executable ``` -Das Schlüsselwort `entrypoint` ist für Docker Container-Aktionen vorgesehen, kann jedoch auch für JavaScript-Aktionen herangezogen werden, in denen keine Eingaben definiert werden. +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. #### **`jobs..steps.env`** diff --git a/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 43c31f32d63e..de2e4815f774 100644 --- a/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -28,16 +28,7 @@ To configure authentication and user provisioning for {% data variables.product. {% 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. - - | Value in Azure AD | Value from {% data variables.product.prodname_ghe_managed %} - |:---------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Identifier (Entity ID) | `https://YOUR-GITHUB-AE-HOSTNAME - - - Reply URL - https://YOUR-GITHUB-AE-HOSTNAME/saml/consume` | - | Sign on URL | https://YOUR-GITHUB-AE-HOSTNAME/sso | +1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. 1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. diff --git a/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md index 4c55c959e74c..bac4474432b7 100644 --- a/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md @@ -38,6 +38,12 @@ After a user successfully authenticates on your IdP, the user's SAML session for {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} +The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | Weitere Informationen | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs | + 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. | Wert | Other names | Beschreibung | Beispiel | diff --git a/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index 7648aabe16be..0187c91f5765 100644 --- a/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -62,7 +62,15 @@ You must have administrative access on your IdP to configure the application for {% 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. Klicke auf **Save** (Speichern). ![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. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. + + The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | Weitere Informationen | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs | + + The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}. | Wert | Other names | Beschreibung | Beispiel | |:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- | diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md b/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md index cafdeb72cd91..fb9334c4e7b8 100644 --- a/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md +++ b/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md @@ -11,7 +11,7 @@ versions: ### Externen `collectd`-Server einrichten -Falls Sie noch keinen externen `collectd`-Server eingerichtet haben, müssen Sie dies erledigen, bevor Sie die `collectd`-Weiterleitung auf {% data variables.product.product_location %} aktivieren. Ihr `collectd`-Server muss `collectd` Version 5.x oder höher ausführen. +Falls Sie noch keinen externen `collectd`-Server eingerichtet haben, müssen Sie dies erledigen, bevor Sie die `collectd`-Weiterleitung auf {% data variables.product.product_location %} aktivieren. Your `collectd` server must be running `collectd` version 5.x or higher. 1. Melden Sie sich bei Ihrem `collectd`-Server an. 2. Erstellen Sie die `collectd`-Konfigurationsdatei, oder bearbeiten Sie sie so, dass das Netzwerk-Plug-in geladen und in die Server- und Portdirektiven die entsprechenden Werte eingetragen werden. Auf den meisten Distributionen befindet sie sich unter `/etc/collectd/collectd.conf`. diff --git a/translations/de-DE/content/admin/packages/configuring-third-party-storage-for-packages.md b/translations/de-DE/content/admin/packages/configuring-third-party-storage-for-packages.md index 523834c7e440..71524f12ae5a 100644 --- a/translations/de-DE/content/admin/packages/configuring-third-party-storage-for-packages.md +++ b/translations/de-DE/content/admin/packages/configuring-third-party-storage-for-packages.md @@ -21,7 +21,10 @@ For the best experience, we recommend using a dedicated bucket for {% data varia {% warning %} -**Warning:** Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. +**Warnungen:** +- 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. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} diff --git a/translations/de-DE/content/admin/packages/index.md b/translations/de-DE/content/admin/packages/index.md index d677721898a2..2c1a7b4d0c1f 100644 --- a/translations/de-DE/content/admin/packages/index.md +++ b/translations/de-DE/content/admin/packages/index.md @@ -1,6 +1,5 @@ --- title: Managing GitHub Packages for your enterprise -shortTitle: GitHub Packages intro: 'You can enable {% data variables.product.prodname_registry %} for your enterprise and manage {% data variables.product.prodname_registry %} settings and allowed packaged types.' redirect_from: - /enterprise/admin/packages diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md index 6ef05edbb3c2..8f9c9a7f1778 100644 --- a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md +++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -36,17 +36,23 @@ Wenn Sie in Ihrem Texteditor Änderungen an Dateien vornehmen und Sie diese loka #### Partiellen Commit erstellen -Wenn eine Datei mehrere Änderungen aufweist, Du aber möchtest, dass nur *einige* dieser Änderungen in einem Commit enthalten sind, kannst Du einen partiellen Commit erstellen. Der Rest Deiner Änderungen bleibt erhalten, sodass Du zusätzliche Änderungen und Commits vornehmen kannst. Dadurch kannst Du separate, aussagekräftige Commits erstellen, beispielsweise kannst Du Änderungen der Zeilenumbrüche in einem Commit vom Code oder von Fließtextänderungen getrennt halten. +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. Der Rest Deiner Änderungen bleibt erhalten, sodass Du zusätzliche Änderungen und Commits vornehmen kannst. Dadurch kannst Du separate, aussagekräftige Commits erstellen, beispielsweise kannst Du Änderungen der Zeilenumbrüche in einem Commit vom Code oder von Fließtextänderungen getrennt halten. -Wenn Du den Diff der Datei überprüfst, werden die Zeilen, die in den Commit aufgenommen werden, blau hervorgehoben. Um die Änderung auszuschließen, klickst Du auf die geänderte Zeile, damit das Blau verschwindet. +{% note %} + +**Note:** Split diff displays are currently in beta and subject to change. + +{% endnote %} -![Zeilen in einer Datei aus der Auswahl entfernen](/assets/images/help/desktop/partial-commit.png) +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. ![Zeilen in einer Datei aus der Auswahl entfernen](/assets/images/help/desktop/partial-commit.png) -#### Änderungen verwerfen +### 3. Änderungen verwerfen +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. -Du kannst alle nicht per Commit übertragenen Änderungen in einer einzelnen Datei, in einer Gruppe von Dateien oder alle Änderungen in allen Dateien seit dem letzten Commit verwerfen. +Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied. -{% mac %} +#### Discarding changes in one or more files {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -54,32 +60,27 @@ Du kannst alle nicht per Commit übertragenen Änderungen in einer einzelnen Dat {% data reusables.desktop.confirm-discard-files %} ![Schaltfläche „Discard Changes“ (Änderungen verwerfen) im Bestätigungsdialogfeld](/assets/images/help/desktop/discard-changes-confirm-mac.png) -{% tip %} +#### Discarding changes in one or more lines +You can discard one or more changed lines that are uncommitted. -**Tipp:** Die von Dir verworfenen Änderungen werden unter „Trash“ (Papierkorb) in einer Datei mit entsprechender Datumsangabe gespeichert. Du kannst diese wiederherstellen, bis der Papierkorb geleert wird. - -{% endtip %} +{% note %} -{% endmac %} +**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. -{% windows %} +{% endnote %} -{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %} - ![Option „Discard Changes“ (Änderungen verwerfen) im Kontextmenü](/assets/images/help/desktop/discard-changes-win.png) -{% data reusables.desktop.confirm-discard-files %} - ![Schaltfläche „Discard Changes“ (Änderungen verwerfen) im Bestätigungsdialogfeld](/assets/images/help/desktop/discard-changes-confirm-win.png) +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**. -{% tip %} + ![Discard single line in the confirmation dialog](/assets/images/help/desktop/discard-single-line.png) -**Tipp:** Die von Dir verworfenen Dateien werden im „Recycle Bin“ (Papierkorb) in einer Datei gespeichert. Du kannst diese wiederherstellen, bis der Papierkorb geleert wird. +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**. -{% endtip %} + ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) -{% endwindows %} -### 3. Eine Commit-Mitteilung schreiben und Deine Änderungen per Push übertragen +### 4. Eine Commit-Mitteilung schreiben und Deine Änderungen per Push übertragen -Sobald Du mit den Änderungen zufrieden bist, die Du in Deinen Commit aufnehmen möchtest, schreibest Du Deine Commit-Mitteilung, und überträgst Deine Änderungen per Push. Wenn Du an einem Commit mitgewirkt hast, kannst Du einen Commit auch mehr als einem Autor zuweisen. +Sobald Sie mit den Änderungen zufrieden sind, die Sie in Ihren Commit aufnehmen möchten, schreiben Sie Ihre Commit-Mitteilung, und übertragen Sie Ihre Änderungen per Push-Vorgang. Wenn Sie an einem Commit mitgewirkt haben, können Sie einen Commit auch mehr als einem Autor zuweisen. {% note %} diff --git a/translations/de-DE/content/developers/apps/rate-limits-for-github-apps.md b/translations/de-DE/content/developers/apps/rate-limits-for-github-apps.md index e25d374ee18c..31607e2e14bb 100644 --- a/translations/de-DE/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/de-DE/content/developers/apps/rate-limits-for-github-apps.md @@ -34,8 +34,6 @@ Different server-to-server request rate limits apply to {% data variables.produc ### User-to-server requests -{% data reusables.apps.deprecating_password_auth %} - {% 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. {% if currentVersion == "free-pro-team@latest" %} @@ -52,7 +50,7 @@ User-to-server requests are rate limited at 5,000 requests per hour and per auth #### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits -When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. +When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. {% endif %} diff --git a/translations/de-DE/content/developers/overview/managing-deploy-keys.md b/translations/de-DE/content/developers/overview/managing-deploy-keys.md index 5e5d4032d8c2..61c9d8151a10 100644 --- a/translations/de-DE/content/developers/overview/managing-deploy-keys.md +++ b/translations/de-DE/content/developers/overview/managing-deploy-keys.md @@ -82,6 +82,32 @@ See [our guide on Git automation with tokens][git-automation]. 7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. 8. Click **Add key**. +##### Using multiple repositories on one server + +If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. + +In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. Ein Beispiel: + +```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 %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias. +* `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias. +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias. + +You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. Ein Beispiel: + +```bash +$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git +``` + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/de-DE/content/developers/overview/secret-scanning.md b/translations/de-DE/content/developers/overview/secret-scanning.md index acd56d27d007..0744a72c4e13 100644 --- a/translations/de-DE/content/developers/overview/secret-scanning.md +++ b/translations/de-DE/content/developers/overview/secret-scanning.md @@ -79,7 +79,7 @@ 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. +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. * **Token**: The value of the secret match. * **Type**: The unique name you provided to identify your regular expression. diff --git a/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md b/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md index f5a34e99c5c3..d151bd6a2101 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md @@ -1,6 +1,7 @@ --- title: Über „secret scanning" (Durchsuchen nach Geheimnissen) intro: '{% data variables.product.product_name %} durchsucht Repositorys nach bekannten Geheimnis-Typen, um die betrügerische Verwendung von Geheimnissen zu verhindern, die versehentlich freigegeben wurden.' +product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /github/administering-a-repository/about-token-scanning - /articles/about-token-scanning diff --git a/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md b/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md index bff3221e784c..131f0ebc296a 100644 --- a/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md +++ b/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md @@ -1,6 +1,7 @@ --- title: '„Secret scanning" (Durchsuchung nach Geheimnissen) für private Repositorys konfigurieren' intro: 'Du kannst konfigurieren, wie {% data variables.product.product_name %} Deine privaten Repositories nach Geheimnissen durchsucht.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'Personen mit Administratorberechtigungen für ein privates Repository können {% data variables.product.prodname_secret_scanning %} für das Repository aktivieren.' versions: free-pro-team: '*' diff --git a/translations/de-DE/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/de-DE/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index 2af823c49d66..e6e30e49301f 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -1,6 +1,7 @@ --- title: Warnungen von „secret scanning" (Durchsuchen nach Geheimnissen) verwalten intro: Du kannst Warnungen für Geheimnisse, welche in Deinem Repository geprüft wurden, anschauen und schließen. +product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' --- diff --git a/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index 6b09d2622322..5617bd73201f 100644 --- a/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -31,7 +31,7 @@ Weitere Informationen findest Du unter „[Deine Commit-E-Mail-Adresse festlegen ### Commits mit Co-Autor mit {% data variables.product.prodname_desktop %} erstellen -Sie können mit {% data variables.product.prodname_desktop %} einen Commit mit einem Co-Autor erstellen. Weitere Informationen findest Du unter „[Commit-Mitteilung schreiben und Deine Änderungen via Push übertragen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)“ und „[{% data variables.product.prodname_desktop %}](https://desktop.github.com)“. +Sie können mit {% data variables.product.prodname_desktop %} einen Commit mit einem Co-Autor erstellen. Weitere Informationen findest Du unter „[Commit-Mitteilung schreiben und Deine Änderungen via Push übertragen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)“ und „[{% data variables.product.prodname_desktop %}](https://desktop.github.com)“. ![Einen Co-Autor zur Commit-Mitteilung hinzufügen](/assets/images/help/desktop/co-authors-demo-hq.gif) @@ -74,4 +74,4 @@ Der neue Commit samt Mitteilung wird auf {% data variables.product.product_locat - „[Eine Zusammenfassung der Repository-Aktivitäten anzeigen](/articles/viewing-a-summary-of-repository-activity)“ - „[Die Mitarbeiter eines Projekts anzeigen](/articles/viewing-a-projects-contributors)“ - „[Eine Commit-Mitteilung ändern](/articles/changing-a-commit-message)“ -- „[Änderungen an Deinem Projekt freigeben und überprüfen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)“ in der {% data variables.product.prodname_desktop %}-Dokumentation +- „[Änderungen an Deinem Projekt freigeben und überprüfen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)“ in der {% data variables.product.prodname_desktop %}-Dokumentation diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md index 6274df0b2847..9a3844abb0b6 100644 --- a/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- title: Using Codespaces in Visual Studio Code -intro: 'Du kannst über {% data variables.product.prodname_vscode %} direkt in Deinem Codespace entwickeln, indem Du die {% data variables.product.prodname_vs_codespaces %}-Erweiterung mit Deinem Konto auf {% data variables.product.product_name %} verbindest.' +intro: 'Du kannst über {% data variables.product.prodname_vscode %} direkt in Deinem Codespace entwickeln, indem Du die {% data variables.product.prodname_github_codespaces %}-Erweiterung mit Deinem Konto auf {% data variables.product.product_name %} verbindest.' 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: ### Vorrausetzungen -Bevor Du über {% data variables.product.prodname_vscode %} direkt in einem Codespace entwickeln kannst, musst Du die {% data variables.product.prodname_vs_codespaces %}-Erweiterung so konfigurieren, dass sie sich zu Deinem {% data variables.product.product_name %}-Konto verbindet. +To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. -1. Du kannst {% data variables.product.prodname_vs %}-Marketplace verwenden, um die [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline)-Erweiterung zu installieren. Weitere Informationen findest Du unter „[Marketplace-Erweiterung](https://code.visualstudio.com/docs/editor/extension-gallery)" in der {% data variables.product.prodname_vscode %}-Dokumentation. -2. Klicke in der linken Seitenleiste in {% data variables.product.prodname_vscode %} auf das Symbol „Extensions" (Erweiterungen). ![Das Symbol „Extensions" (Erweiterungen) in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-extensions-icon-vscode.png) -3. Klicke unterhalb von {% data variables.product.prodname_vs_codespaces %} auf das Symbol „Manage" (Verwalten), und klicke dann auf **Extension Settings** (Erweiterungseinstellungen). ![Option „Extension Settings" (Erweiterungseinstellungen)](/assets/images/help/codespaces/select-extension-settings.png) -4. Verwende das Dropdownmenü „Vsonline: Account Provider" (Vsonline: Kontoanbieter) und wähle {% data variables.product.prodname_dotcom %}. ![Den Kontoanbieter auf {% data variables.product.prodname_dotcom %} setzen](/assets/images/help/codespaces/select-account-provider-vscode.png) +1. Use the + +{% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. Weitere Informationen findest Du unter „[Marketplace-Erweiterung](https://code.visualstudio.com/docs/editor/extension-gallery)" in der {% data variables.product.prodname_vscode %}-Dokumentation. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -6. Wenn {% data variables.product.prodname_codespaces %} in der Kopfzeile noch nicht ausgewählt ist, klicke auf **{% data variables.product.prodname_codespaces %}**. ![Die {% data variables.product.prodname_codespaces %}-Kopfzeile](/assets/images/help/codespaces/codespaces-header-vscode.png) -7. Klicke auf **Sign in to view {% data variables.product.prodname_codespaces %}...** (Anmelden zur Anzeige von...). ![Anmelden, um {% data variables.product.prodname_codespaces %} anzuzeigen](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -8. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen). -9. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen. +2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![Die {% data variables.product.prodname_codespaces %}-Kopfzeile](/assets/images/help/codespaces/codespaces-header-vscode.png) +3. Klicke auf **Sign in to view {% data variables.product.prodname_codespaces %}...** (Anmelden zur Anzeige von...). ![Anmelden, um {% data variables.product.prodname_codespaces %} anzuzeigen](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) +4. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen). +5. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen. ### Creating a codespace in {% data variables.product.prodname_vscode %} @@ -31,8 +30,8 @@ After you connect your {% data variables.product.product_name %} account to the {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) 3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop in. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) - +4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) +5. Click the instance type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) ### Einen Codespace in {% data variables.product.prodname_vscode %} eröffnen {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 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 ff27712b4928..cc2db49628af 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 @@ -12,26 +12,25 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About {% data variables.product.prodname_code_scanning %} +### Informationen zu {% data variables.product.prodname_code_scanning %} -{% data reusables.code-scanning.about-code-scanning %} +With {% data variables.product.prodname_code_scanning %}, developers can quickly and automatically analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. 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. -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)." +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)." -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)." +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. -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)." +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)." -### About {% data variables.product.prodname_codeql %} +### Informationen zu {% 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. +{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}. {% 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. {% 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_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. +For more information about API endpoints for {% data variables.product.prodname_code_scanning %}, see "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)." {% data reusables.code-scanning.supported-languages %} @@ -39,9 +38,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### Informationen zur Abrechnung für {% 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 %} 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 %}. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“ {% endif %} @@ -53,7 +52,7 @@ 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 +### Weiterführende Informationen {% if currentVersion == "free-pro-team@latest" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index bd1b1f43ac7c..fbbf119fb7f9 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -94,7 +94,7 @@ If the `autobuild` command can't build your code, you can run the build steps yo By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command. -Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-an-alert)." +Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-the-alerts-for-a-repository)." ### {% data variables.product.prodname_codeql_runner %} command reference diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index d44cd2e445b5..6a4690f25589 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -17,29 +17,25 @@ versions: ### Options for enabling {% 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)." +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. Weitere Informationen findest Du unter „[ Über {% 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 -{% 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" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% 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) +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. 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. 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) +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**. 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. @@ -62,7 +58,7 @@ After enabling {% data variables.product.prodname_code_scanning %} for your repo 1. Review the logging output from the actions in this workflow as they run. -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. 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-the-alerts-for-a-repository)." {% note %} @@ -106,12 +102,12 @@ There are other situations where there may be no analysis for the latest commit 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 %}. -### Next steps +### Nächste Schritte: After enabling {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: - 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)." +- Set up notifications for completed runs. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/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)." diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index a6c5371b29da..8deaec4e36cb 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -1,7 +1,7 @@ --- title: Managing code scanning alerts for your repository shortTitle: Warnungen verwalten -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: 'From the security view, 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.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: @@ -30,9 +30,11 @@ If you enable {% data variables.product.prodname_code_scanning %} using {% data When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. -### Viewing an alert +### Viewing the alerts for a repository -Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} alerts on pull requests. However, you need write permission to view a summary of alerts for repository on the **Security** tab. By default, alerts are shown for the default branch. +Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. 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)." + +You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -45,7 +47,7 @@ Anyone with read permission for a repository can see {% data variables.product.p Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[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)." -If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing an alert](#viewing-an-alert)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. +If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index 4496efbd1f03..521a9cb1faf7 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -3,7 +3,7 @@ title: Triaging code scanning alerts in pull requests shortTitle: Triaging alerts in pull requests intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.' 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: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -31,9 +31,9 @@ When you look at the **Files changed** tab for a pull request, you see annotatio ![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png) -Some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." +If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." -For more information about an alert, click **Show more details** on the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. +To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code. @@ -41,11 +41,11 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_ ### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request -Anyone with write permission for a repository can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on a pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. +Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. {% if currentVersion == "enterprise-server@2.22" %} -If you don't think that an alert needs to be fixed, you can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. +If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. {% data reusables.code-scanning.false-positive-fix-codeql %} @@ -63,4 +63,4 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler For more information about dismissing alerts, 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#dismissing-or-deleting-alerts)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index fcbe2979c3d9..b383522e984e 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -66,7 +66,7 @@ For more information, see the workflow extract in "[Automatic build for a compil * Building using a distributed build system external to GitHub Actions, using a daemon process. * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. - For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. + For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. For example, the following configuration for C# will pass the flag during the first build step. diff --git a/translations/de-DE/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md b/translations/de-DE/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md index e7e66aab9def..8559c0e75ef4 100644 --- a/translations/de-DE/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md +++ b/translations/de-DE/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md @@ -21,5 +21,5 @@ Die Produkte und Funktionen von {% data variables.product.product_name %} könne Du kannst eine Liste der Funktionen sehen, die in der Beta-Version verfügbar sind, und eine kurze Beschreibung für jede Funktion. Jede Funktion enthält einen Link, um Feedback zu geben. -1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf Dein Profilfoto und dann auf **Feature preview** (Funktions-Vorschau). ![Schaltfläche „Feature preview" (Funktions-Vorschau)](/assets/images/help/settings/feature-preview-button.png) +{% data reusables.feature-preview.feature-preview-setting %} 2. Klicke optional auf der rechten Seite einer Funktion auf **Aktivieren** oder **Deaktivieren**. ![Schaltfläche „Enable" (Aktivieren) in der Funktions-Vorschau](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md index 65b7031ebfdf..64e676a78dd2 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md @@ -1,6 +1,7 @@ --- title: Managing secret scanning for your organization intro: 'You can control which repositories in your organization {% data variables.product.product_name %} will scan for secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'Organization owners can manage {% data variables.product.prodname_secret_scanning %} for repositories in the organization.' versions: free-pro-team: '*' 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 47d05af4f943..a2839954c10c 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 @@ -43,74 +43,77 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben ### Repository-Zugriff der einzelnen Berechtigungsebenen -| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | -|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:| -| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | -| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | -| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** | -| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** | -| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** | -| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** | -| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** | -| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** | -| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** | -| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** |{% endif %} -| 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** | -| 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** | -| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** | -| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** | -| [Ausblenden der Kommentare beliebiger Benutzer](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Blockieren von Unterhaltungen](/articles/locking-conversations) | | | **X** | **X** | **X** | -| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** | -| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/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" %} -| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** | -| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** | -| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** | -| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** | -| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Pakete löschen](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** | -| Aktivieren von Projektboards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** | -| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Interaktionen in einem Repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** |{% endif %} -| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** | -| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** | -| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** | -| Ein Repository zu einem Team hinzufügen (siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** | -| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** | -| Ändern der Einstellungen eines Repositorys | | | | | **X** | -| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** | -| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** | -| Manage webhooks and deploy keys | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** | -| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** | -| [Manage data use settings for your private repository](/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" %}| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %} -| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | | | | | **X** |{% endif %} -| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | +| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | +| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | +| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** | +| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** | +| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** | +| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** | +| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** | +| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** | +| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** | +| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 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** | +| 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** | +| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** | +| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** | +| [Ausblenden der Kommentare beliebiger Benutzer](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Blockieren von Unterhaltungen](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** | +| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/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" %} +| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** | +| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** | +| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** | +| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** | +| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Pakete löschen](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** | +| Aktivieren von Projektboards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** | +| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Interaktionen in einem Repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** |{% endif %} +| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** | +| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** | +| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** | +| Ein Repository zu einem Team hinzufügen (siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** | +| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** | +| Ändern der Einstellungen eines Repositorys | | | | | **X** | +| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** | +| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** | +| Manage webhooks and deploy keys | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** | +| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** | +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | +| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %} +| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | | | | | **X** |{% endif %} +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 61497be9a9dd..12d028716278 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/de-DE/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: - -{% 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) +#### Search based on time of action + +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 %} -##### The `account` category +**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" %} + +#### `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,7 +393,7 @@ 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 |------------------|------------------- @@ -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 +|------------------|------------------- +| `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-dependabot-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 |------------------|------------------- -| `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 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/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index c463b0426263..03908489c36a 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -3,6 +3,7 @@ title: Managing licenses for Visual Studio subscription with GitHub Enterprise intro: 'You can manage {% data variables.product.prodname_enterprise %} licensing for {% 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 diff --git a/translations/de-DE/content/github/site-policy/github-acceptable-use-policies.md b/translations/de-DE/content/github/site-policy/github-acceptable-use-policies.md index 2b190a851048..16c9fca7f210 100644 --- a/translations/de-DE/content/github/site-policy/github-acceptable-use-policies.md +++ b/translations/de-DE/content/github/site-policy/github-acceptable-use-policies.md @@ -37,6 +37,8 @@ Während Sie den Dienst nutzen, dürfen Sie unter keinen Umständen - eine Einzelperson oder Gruppe, einschließlich Ihrer Mitarbeiter, Führungskräfte, Vertreter und anderer Benutzer, belästigen, beleidigen, bedrohen oder zur Gewalt gegen sie aufrufen, +- post off-topic content, or interact with platform features, in a way that significantly or repeatedly disrupts the experience of other users; + - unsere Server für irgendeine Art von übermäßigen automatisierten Massenaktivitäten (beispielsweise Spam oder Kryptowährungs-Mining) verwenden, die unsere Server durch automatisierte Mittel übermäßig belasten, oder irgendeine andere Form von unerwünschter Werbung oder Aufforderungen, z. B. Systeme, die schnellen Reichtum versprechen, über unsere Server verbreiten, - unsere Server nutzen, um Dienste, Geräte, Daten, Konten oder Netzwerke zu stören oder zu versuchen, diese zu stören, oder um unbefugten Zugang zu erlangen oder dies zu versuchen (es sei denn, dies wurde im Rahmen des [GitHub Bug Bounty-Programms](https://bounty.github.com) genehmigt), @@ -48,15 +50,17 @@ Während Sie den Dienst nutzen, dürfen Sie unter keinen Umständen ### 4. Einschränkungen hinsichtlich der Dienstnutzung Sie dürfen keinen Teil des Dienstes, der Nutzung des Dienstes oder des Zugriffs auf den Dienst reproduzieren, duplizieren, kopieren, verkaufen, wiederverkaufen oder ausnutzen. -### 5. Beschränkungen hinsichtlich Scrapings und der API-Nutzung -Der Begriff „Scraping“ bezieht sich auf die Extrahierung von Daten aus unserem Dienst mithilfe automatischer Prozesse wie z. B. Bots oder Webcrawlern. Er umfasst nicht die Erfassung von Informationen über unser API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. Scraping ist Ihnen auf unserer Website für die folgenden Zwecke gestattet: +### 5. Information Usage Restrictions +You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise: + +- Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are [open access](https://en.wikipedia.org/wiki/Open_access). +- Archivists may use public information from the Service for archival purposes. -- Forscher können öffentliche, nicht personenbezogene Daten aus dem Dienst zu Forschungszwecken extrahieren, vorausgesetzt, die sich aus dieser Forschung ergebenden Veröffentlichungen werden öffentlich zugänglich gemacht. -- Archivare können öffentliche Daten zu Archivierungszwecken aus dem Dienst extrahieren. +Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler. Scraping does not refer to the collection of information through our API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. -Sie dürfen keine Daten aus dem Dienst für Spamzwecke extrahieren. Dies gilt auch für den Verkauf von personenbezogenen Daten von Benutzern (gemäß Definition in der [GitHub-Datenschutzerklärung](/articles/github-privacy-statement)) beispielsweise an Personalvermittler, Headhunter und Stellenbörsen. +You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling User Personal Information (as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement)), such as to recruiters, headhunters, and job boards. -Alle Daten, die mittels Scraping gesammelt werden, müssen den Vorgaben der [GitHub-Datenschutzerklärung](/articles/github-privacy-statement) entsprechen. +Your use of information from the Service must comply with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). ### 6. Datenschutz Der Missbrauch personenbezogener Daten von Benutzern ist untersagt. diff --git a/translations/de-DE/content/github/site-policy/github-additional-product-terms.md b/translations/de-DE/content/github/site-policy/github-additional-product-terms.md index d641055588fb..8baf03897be1 100644 --- a/translations/de-DE/content/github/site-policy/github-additional-product-terms.md +++ b/translations/de-DE/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: November 1, 2020 +Version Effective Date: November 13, 2020 Wenn Sie ein Konto erstellen, erhalten Sie Zugriff auf viele verschiedene Features und Produkte, die alle Teil des Dienstes sind. Da viele dieser Features und Produkte unterschiedliche Funktionen bieten, erfordern sie möglicherweise zusätzliche Geschäftsbedingungen, die für dieses Feature oder dieses Produkt spezifisch sind. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -89,7 +89,7 @@ In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors ### 9. GitHub Advanced Security -Mit GitHub Advanced Security können Sie Sicherheitslücken durch anpassbare und automatisierte semantische Codeanalyse identifizieren. GitHub Advanced Security ist pro Benutzer lizenziert. Wenn Sie GitHub Advanced Security als Teil von GitHub Enterprise Cloud verwenden, erfordern viele Funktionen von GitHub Advanced Security, einschließlich des automatisierten Code-Scannens privater Repositorys, auch die Verwendung von GitHub Actions. Die Abrechnung für die Nutzung von GitHub Actions erfolgt nutzungsbasiert und unterliegt den [GitHub Actions-Bedingungen](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages). +GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. Wenn Sie GitHub Advanced Security als Teil von GitHub Enterprise Cloud verwenden, erfordern viele Funktionen von GitHub Advanced Security, einschließlich des automatisierten Code-Scannens privater Repositorys, auch die Verwendung von GitHub Actions. ### 10. Dependabot Preview @@ -108,4 +108,3 @@ We need the legal right to submit your contributions to the GitHub Advisory Data #### b. Lizenz für das GitHub Advisory Database The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by . - diff --git a/translations/de-DE/content/github/site-policy/github-community-guidelines.md b/translations/de-DE/content/github/site-policy/github-community-guidelines.md index ec8c17a1728f..158f17fe13b5 100644 --- a/translations/de-DE/content/github/site-policy/github-community-guidelines.md +++ b/translations/de-DE/content/github/site-policy/github-community-guidelines.md @@ -11,7 +11,7 @@ Millionen von Entwicklern hosten Millionen von Projekten auf GitHub – sowohl O Die weltweiten GitHub-Benutzer verfügen über völlig unterschiedliche Perspektiven, Ideen und Erfahrungen und umfassen sowohl Personen, die letzte Woche ihr erstes "Hello World"-Projekt ins Leben gerufen haben, als auch die bekanntesten Software-Entwickler der Welt. Wir sind bestrebt, GitHub zu einem einladenden Umfeld für all die verschiedenen Stimmen und Perspektiven in unserer Community zu machen und gleichzeitig einen Raum zu bieten, in dem sich Personen frei äußern können. -Wir sind darauf angewiesen, dass unsere Community-Mitglieder Erwartungen kommunizieren, ihre Projekte [moderieren ](#what-if-something-or-someone-offends-you)und {% data variables.contact.report_abuse %} oder {% data variables.contact.report_content %}. Wir durchsuchen nicht aktiv die Inhalte, um sie zu moderieren. Wir hoffen, Ihnen durch die Darstellung unserer Erwartungen an unsere Community verständlich zu machen, wie Sie am besten auf GitHub mitwirken können und welche Art von Handlungen oder Inhalten möglicherweise gegen unsere [Nutzungsbedingungen](#legal-notices) verstoßen. Wir werden allen Meldungen über Missbrauch nachgehen und können öffentliche Inhalte auf unserer Website moderieren, bei denen wir feststellen, dass sie gegen unsere Nutzungsbedingungen verstoßen. +Wir sind darauf angewiesen, dass unsere Community-Mitglieder Erwartungen kommunizieren, ihre Projekte [moderieren ](#what-if-something-or-someone-offends-you)und {% data variables.contact.report_abuse %} oder {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). Wir werden allen Meldungen über Missbrauch nachgehen und können öffentliche Inhalte auf unserer Website moderieren, bei denen wir feststellen, dass sie gegen unsere Nutzungsbedingungen verstoßen. ### Eine starke Community aufbauen @@ -47,23 +47,25 @@ Selbstverständlich können Sie uns jederzeit kontaktieren, um {% data variables Wir setzen uns für die Aufrechterhaltung einer Community ein, in der es den Benutzer freisteht, sich auszudrücken und die Ideen des anderen in Frage zu stellen, sowohl technisch als auch anderweitig. Solche Diskussionen fördern jedoch keinen fruchtbaren Dialog, wenn Ideen zum Schweigen gebracht werden, weil Community-Mitglieder niedergeschrien werden oder Angst haben, sich zu äußern. Das bedeutet, dass Sie jederzeit respektvoll und höflich sein und andere nicht auf der Grundlage ihrer Identität angreifen sollten. Wir tolerieren kein Verhalten, das Grenzen in den folgenden Bereichen überschreitet: -* **Gewaltandrohungen** - Sie dürfen nicht mit Gewalt gegen andere drohen oder die Website nutzen, um Akte realer Gewalt oder Terrorismus zu organisieren, zu fördern oder anzustiften. Denken Sie sorgfältig über Ihre Wortwahl, von Ihnen gepostete Bilder sowie auch über die Software, die Sie verfassen, nach und wie diese von anderen interpretiert werden können. Selbst wenn Sie etwas als Scherz gemeint haben, wird es möglicherweise nicht auf diese Weise aufgenommen. Wenn Sie glauben, dass jemand anderes die Inhalte, die Sie posten, als Bedrohung oder als Förderung von Gewalt oder Terrorismus interpretieren *könnte*, hören Sie auf. Veröffentlichen Sie sie nicht auf GitHub. In außergewöhnlichen Fällen können wir Gewaltandrohungen an die Strafverfolgungsbehörden melden, wenn wir der Meinung sind, dass ein echtes Risiko körperlicher Schäden oder eine Bedrohung der öffentlichen Sicherheit besteht. +- #### Threats of violence You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. Denken Sie sorgfältig über Ihre Wortwahl, von Ihnen gepostete Bilder sowie auch über die Software, die Sie verfassen, nach und wie diese von anderen interpretiert werden können. Selbst wenn Sie etwas als Scherz gemeint haben, wird es möglicherweise nicht auf diese Weise aufgenommen. Wenn Sie glauben, dass jemand anderes die Inhalte, die Sie posten, als Bedrohung oder als Förderung von Gewalt oder Terrorismus interpretieren *könnte*, hören Sie auf. Veröffentlichen Sie sie nicht auf GitHub. In außergewöhnlichen Fällen können wir Gewaltandrohungen an die Strafverfolgungsbehörden melden, wenn wir der Meinung sind, dass ein echtes Risiko körperlicher Schäden oder eine Bedrohung der öffentlichen Sicherheit besteht. -* **Hassreden und Diskriminierung.** - Obwohl es nicht verboten ist, Themen wie Alter, Körpergröße, ethnische Zugehörigkeit, Geschlechtsidentität und Ausdruck, Erfahrungsgrad, Nationalität, persönliches Aussehen, Rasse, Religion oder sexuelle Identität und Orientierung anzusprechen, tolerieren wir keine Sprache, die eine Person oder eine Gruppe von Menschen auf der Grundlage dessen angreift, wer sie sind. Machen Sie sich einfach bewusst, dass diese (und andere) heikle Themen, wenn sie auf aggressive oder beleidigende Weise angegangen werden, dazu führen können, dass sich andere unwillkommen oder gar unsicher fühlen. Obwohl es immer das Potenzial für Missverständnisse gibt, erwarten wir von unseren Community-Mitgliedern, dass sie respektvoll und zivil bleiben, wenn sie sensible Themen diskutieren. +- #### Hate speech and discrimination While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. Machen Sie sich einfach bewusst, dass diese (und andere) heikle Themen, wenn sie auf aggressive oder beleidigende Weise angegangen werden, dazu führen können, dass sich andere unwillkommen oder gar unsicher fühlen. Obwohl es immer das Potenzial für Missverständnisse gibt, erwarten wir von unseren Community-Mitgliedern, dass sie respektvoll und zivil bleiben, wenn sie sensible Themen diskutieren. -* **Mobbing und Belästigung** - Wir tolerieren kein Mobbing und keine Belästigung. Dazu gehört jede Form der Belästigung oder Einschüchterung, die auf eine bestimmte Person oder Personengruppe abzielt. Wenn Ihre Handlungen unerwünscht sind und Sie diese dennoch fortsetzen, ist die Wahrscheinlichkeit groß, dass Sie auf Mobbing oder Belästigung ausgerichtet sind. +- #### Bullying and harassment We do not tolerate bullying or harassment. Dazu gehört jede Form der Belästigung oder Einschüchterung, die auf eine bestimmte Person oder Personengruppe abzielt. Wenn Ihre Handlungen unerwünscht sind und Sie diese dennoch fortsetzen, ist die Wahrscheinlichkeit groß, dass Sie auf Mobbing oder Belästigung ausgerichtet sind. -* **Impersonifizierung** - Sie dürfen nicht versuchen, andere bezüglich Ihrer Identität zu täuschen, indem Sie einen Avatar einer anderen Person kopieren, Inhalte unter deren E-Mail-Adresse posten, absichtlich einen täuschend ähnlichen Benutzernamen verwenden oder sich anderweitig als jemand anderes ausgeben. Impersonifizierung ist eine Form der Belästigung. +- #### Disrupting the experience of other users Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on. Behaviors such as repeatedly posting off-topic comments, opening empty or meaningless issues or pull requests, or using any other platform feature in a way that continually disrupts the experience of other users are not allowed. While we encourage maintainers to moderate their own projects on an individual basis, GitHub staff may take further restrictive action against accounts that are engaging in these types of behaviors. -* **Doxxing und Eingriff in die Privatsphäre ** - Posten Sie keine persönlichen Daten anderer Personen, z. B. Telefonnummern, private E-Mail-Adressen, physische Adressen, Kreditkartennummern, Sozialversicherungs-/Nationale Identitätsnummern oder Kennwörter. Je nach Kontext, z. B. bei Einschüchterung oder Belästigung, können wir andere Informationen, wie Fotos oder Videos, die ohne Zustimmung des Betreffenden aufgenommen oder verbreitet wurden, als Eingriff in die Privatsphäre betrachten, insbesondere wenn dieses Material ein Sicherheitsrisiko für das Thema darstellt. +- #### Impersonation You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonifizierung ist eine Form der Belästigung. -* **Sexuell obszöne Inhalte** - Posten Sie keine pornographischen Inhalte. Das bedeutet nicht, dass Nacktheit oder jeder Kodex und Inhalt im Zusammenhang mit Sexualität verboten ist. Wir erkennen an, dass Sexualität ein Teil des Lebens ist und nicht-pornografische sexuelle Inhalte ein Teil Ihres Projekts sein können oder zu pädagogischen oder künstlerischen Zwecken präsentiert werden können. Wir erlauben keine obszönen sexuellen Inhalte oder Inhalte, die die Ausbeutung oder Sexualisierung von Minderjährigen beinhalten können. +- #### Doxxing and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. Je nach Kontext, z. B. bei Einschüchterung oder Belästigung, können wir andere Informationen, wie Fotos oder Videos, die ohne Zustimmung des Betreffenden aufgenommen oder verbreitet wurden, als Eingriff in die Privatsphäre betrachten, insbesondere wenn dieses Material ein Sicherheitsrisiko für das Thema darstellt. -* **Gewalttätige Inhalte** - Posten Sie keine gewalttätigen Bilder, Texte oder andere Inhalte ohne angemessenen Kontext oder Warnungen. Obwohl es oft in Ordnung ist, gewalttätige Inhalte in Videospiele, Nachrichtenberichte und Beschreibungen historischer Ereignisse aufzunehmen, erlauben wir keine gewalttätigen Inhalte, die wahllos gepostet werden oder die in einer Weise gepostet werden, dass es für andere Benutzer schwierig ist, sie zu vermeiden (z. B. einen Profil-Avatar oder einen Issue-Kommentar). Eine klare Warnung oder ein Haftungsausschluss in anderen Kontexten hilft Benutzern, eine fundierte Entscheidung darüber zu treffen, ob sie sich mit solchen Inhalten beschäftigen möchten oder nicht. +- #### Sexually obscene content Don’t post content that is pornographic. Das bedeutet nicht, dass Nacktheit oder jeder Kodex und Inhalt im Zusammenhang mit Sexualität verboten ist. Wir erkennen an, dass Sexualität ein Teil des Lebens ist und nicht-pornografische sexuelle Inhalte ein Teil Ihres Projekts sein können oder zu pädagogischen oder künstlerischen Zwecken präsentiert werden können. Wir erlauben keine obszönen sexuellen Inhalte oder Inhalte, die die Ausbeutung oder Sexualisierung von Minderjährigen beinhalten können. -* **Irreführung und Fehlinformationen** - Sie dürfen keine Inhalte posten, die ein verzerrtes Bild der Realität vermitteln, unabhängig davon, ob es sich um ungenaue oder falsche (Fehlinformationen) oder absichtlich täuschende (Irreführung) Inhalte handelt, weil solche Inhalte der Öffentlichkeit Schaden zufügen oder faire und gleiche Chancen für alle zur Teilnahme am öffentlichen Leben beeinträchtigen könnten. Zum Beispiel lassen wir keine Inhalte zu, die das Wohlergehen von Personengruppen gefährden oder ihre Fähigkeit einschränken, an einer freien und offenen Gesellschaft teilzunehmen. Wir ermutigen zur aktiven Teilnahme am Austausch von Ideen, Perspektiven und Erfahrungen und sind möglicherweise nicht in der Lage, persönliche Berichte oder Feststellungen anzufechten. Wir erlauben in der Regel Parodie und Satire, die mit unseren akzeptablen Nutzungsrichtlinien übereinstimmen, und wir halten den Kontext für wichtig, wie Informationen empfangen und verstanden werden; Daher kann es angemessen sein, Ihre Absichten durch Haftungsausschluss oder andere Mittel sowie die Quelle(n) Ihrer Informationen zu klären. +- #### Gratuitously violent content Don’t post violent images, text, or other content without reasonable context or warnings. Obwohl es oft in Ordnung ist, gewalttätige Inhalte in Videospiele, Nachrichtenberichte und Beschreibungen historischer Ereignisse aufzunehmen, erlauben wir keine gewalttätigen Inhalte, die wahllos gepostet werden oder die in einer Weise gepostet werden, dass es für andere Benutzer schwierig ist, sie zu vermeiden (z. B. einen Profil-Avatar oder einen Issue-Kommentar). Eine klare Warnung oder ein Haftungsausschluss in anderen Kontexten hilft Benutzern, eine fundierte Entscheidung darüber zu treffen, ob sie sich mit solchen Inhalten beschäftigen möchten oder nicht. -* **Active malware or exploits** - Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Beachten Sie jedoch, dass wir die Veröffentlichung von Quellcode, der zur Entwicklung von Malware oder Exploits verwendet werden könnte, nicht verbieten, da die Veröffentlichung und Verbreitung eines solchen Quellcodes einen lehrreichen Wert hat und für die Sicherheits-Community einen klaren Nutzen darstellt. +- #### Misinformation and disinformation You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. Zum Beispiel lassen wir keine Inhalte zu, die das Wohlergehen von Personengruppen gefährden oder ihre Fähigkeit einschränken, an einer freien und offenen Gesellschaft teilzunehmen. Wir ermutigen zur aktiven Teilnahme am Austausch von Ideen, Perspektiven und Erfahrungen und sind möglicherweise nicht in der Lage, persönliche Berichte oder Feststellungen anzufechten. Wir erlauben in der Regel Parodie und Satire, die mit unseren akzeptablen Nutzungsrichtlinien übereinstimmen, und wir halten den Kontext für wichtig, wie Informationen empfangen und verstanden werden; Daher kann es angemessen sein, Ihre Absichten durch Haftungsausschluss oder andere Mittel sowie die Quelle(n) Ihrer Informationen zu klären. + +- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Beachten Sie jedoch, dass wir die Veröffentlichung von Quellcode, der zur Entwicklung von Malware oder Exploits verwendet werden könnte, nicht verbieten, da die Veröffentlichung und Verbreitung eines solchen Quellcodes einen lehrreichen Wert hat und für die Sicherheits-Community einen klaren Nutzen darstellt. ### Was passiert, wenn jemand die Regeln verletzt? diff --git a/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md b/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md index 9f37c553b335..c539c35434b8 100644 --- a/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md @@ -9,7 +9,7 @@ versions: VIELEN DANK, DASS SIE SICH FÜR GITHUB ENTSCHIEDEN HABEN, UM DIE ANFORDERUNGEN IHRES UNTERNEHMENS ZU ERFÜLLEN. BITTE LESEN SIE DIESE VEREINBARUNG SORGFÄLTIG DURCH; SIE REGELT DIE VERWENDUNG DER PRODUKTE (WIE UNTEN DEFINIERT), ES SEI DENN, GITHUB HAT ZU DIESEM ZWECK EINE SEPARATE SCHRIFTLICHE VEREINBARUNG MIT DEM KUNDEN ABGESCHLOSSEN. WENN DER KUNDE AUF „I AGREE“ („ICH STIMME ZU“) ODER EINE ÄHNLICHE SCHALTFLÄCHE KLICKT ODER EINES DER PRODUKTE VERWENDET, AKZEPTIERT ER ALLE GESCHÄFTSBEDINGUNGEN DIESER VEREINBARUNG. WENN DER KUNDE DIESE VEREINBARUNG IM NAMEN EINES UNTERNEHMENS ODER EINER ANDEREN JURISTISCHEN PERSON ABSCHLIESST, SICHERT ER ZU, DASS ER RECHTLICH DAZU BEFUGT IST, DIESE VEREINBARUNG FÜR DAS UNTERNEHMEN ODER DIE JURISTISCHE PERSON ZU SCHLIESSEN. ### Unternehmensnutzungsbedingungen für GitHub -Datum des Inkrafttretens dieser Fassung: 20. Juli 2020 +Version Effective Date: November 16, 2020 Diese Vereinbarung gilt für die folgenden Angebote von GitHub, die nachfolgend genauer definiert werden (zusammen die **„Produkte“**): - der Dienst; @@ -133,13 +133,13 @@ Kunden können im Rahmen der Nutzung des Dienstes benutzergenerierte Inhalte ers Der Kunde behält die Eigentumsrechte an Kundeninhalten, die der Kunde erstellt oder die sein Eigentum sind. Der Kunde erklärt sich einverstanden, dass er (a) für die Kundeninhalte haftet, (b) ausschließlich Kundeninhalte sendet, für die er über das Recht zur Veröffentlichung verfügt (einschließlich Inhalten von Dritten und benutzergenerierter Inhalte), und (c) in vollem Umfang alle Bedingungen für Lizenzen Dritter im Zusammenhang mit Kundeninhalten erfüllt, die der Kunde veröffentlicht. Der Kunde gewährt die Rechte nach den Abschnitten D.3 bis D.6 kostenlos und zu den in den entsprechenden Abschnitten angegebenen Zwecken, bis der Kunde die Kundeninhalte von den GitHub-Servern entfernt. Davon ausgenommen sind Inhalte, die der Kunde öffentlich veröffentlicht hat und für die externe Benutzer ein Forking vorgenommen haben. In diesem Fall gilt die Lizenz unbefristet, bis alle Forks von Kundeninhalten von den GitHub-Servern entfernt wurden. Lädt der Kunde Kundeninhalte hoch, für die bereits eine Lizenz besteht, die GitHub die erforderlichen Rechte zur Ausführung des Dienstes gewährt, ist keine weitere Lizenz erforderlich. #### 3. Lizenzvergabe an uns -Der Kunde gewährt GitHub das Recht, Kundeninhalte zu speichern, zu analysieren und anzuzeigen und gelegentlich Kopien zu erstellen, insoweit dies zur Bereitstellung des Dienstes erforderlich ist. Dazu zählt das Recht, Kundeninhalte in die GitHub-Datenbank zu kopieren und Sicherungen zu erstellen, Kundeninhalte dem Kunden und anderen anzuzeigen, denen der Kunde die Inhalte anzeigen möchte, Kundeninhalte für einen Suchindex oder auf andere Weise auf den GitHub-Servern zu analysieren, Kundeninhalte für externe Benutzer freizugeben, für die der Kunde die Inhalte freigeben möchte, und Kundeninhalte wiederzugeben, insoweit es sich um Musik, Videos usw. handelt. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Dienstes zu verwenden. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist. +Customer grants to GitHub the right to store, archive, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service, including improving the Service over time. This license includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. This license does not grant GitHub the right to sell Customer Content. It also does not grant GitHub the right to otherwise distribute or use Customer Content outside of our provision of the Service, except that as part of the right to archive Customer Content, GitHub may permit our partners to store and archive Customer Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist. #### 4. Lizenzgewährung für externe Benutzer Inhalte, die der Kunde öffentlich postet, darunter Issues, Kommentare und Beiträge in Repositorys externer Benutzer, können von anderen angezeigt werden. Indem der Kunde seine Repositorys für die öffentliche Anzeige konfiguriert, stimmt er zu, dass externe Benutzer die Repositorys des Kunden anzeigen und kopieren können. Konfiguriert der Kunde seine Pages und Repositorys für die öffentliche Anzeige, gewährt der Kunde externen Benutzern eine nicht exklusive, weltweite Lizenz zur Verwendung, Anzeige und Wiedergabe von Kundeninhalten über den Dienst und zur Reproduktion von Kundeninhalten ausschließlich im Dienst, insoweit dies nach den von GitHub bereitgestellten Funktionen zulässig ist (beispielsweise durch Forking). Der Kunde kann weitere Rechte an Kundeninhalten gewähren, wenn der Kunde eine Lizenz einführt. Wenn der Kunde Kundeninhalte hochlädt, die er nicht erstellt hat oder die ihm nicht gehören, haftet der Kunde dafür sicherzustellen, dass die hochgeladenen Kundeninhalte nach den Bedingungen lizenziert sind, mit denen diese Rechte externen Benutzern gewährt werden #### 5. Beiträge im Rahmen einer Repository-Lizenz -Macht der Kunde einen Beitrag zu einem Repository mit einem Lizenzhinweis, lizenziert der Kunde seinen Beitrag zu denselben Bedingungen und erklärt, dass er das Recht hat, den entsprechenden Beitrag zu diesen Bedingungen zu lizenzieren. Verfügt der Kunde über eine gesonderte Vereinbarung zur Lizenzierung seiner Beiträge nach anderen Bedingungen wie z. B. einer Mitwirkungslizenzvereinbarung, hat die entsprechende Vereinbarung Vorrang. +Whenever Customer adds Content to a repository containing notice of a license, it licenses that Content under the same terms and agrees that it has the right to license that Content under those terms. If Customer has a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. #### 6. Urheberpersönlichkeitsrechte Der Kunde behält alle Urheberpersönlichkeitsrechte an Kundeninhalten, die er hochlädt, veröffentlicht oder an einen Teil des Dienstes sendet, die Rechte auf Unantastbarkeit und Namensnennung eingeschlossen. Der Kunde verzichtet jedoch auf diese Rechte und stimmt zu, diese gegenüber GitHub nicht geltend zu machen, um GitHub die angemessene Ausübung der Rechte nach Abschnitt D zu ermöglichen, wobei dies jedoch ausschließlich zu diesem Zweck gilt. @@ -153,10 +153,13 @@ Der Kunde haftet für die Verwaltung des Zugriffs auf seine privaten Repositorys GitHub betrachtet Kundeninhalte in den privaten Repositorys des Kunden als vertrauliche Informationen des Kunden. GitHub sorgt nach Abschnitt P für den Schutz und die strikte Wahrung der Vertraulichkeit von Kundeninhalten in privaten Repositorys. #### 3. Zugriff -GitHub-Mitarbeiter können ausschließlich in folgenden Fällen auf private Repositorys des Kunden zugreifen: (i) aus Gründen des Supports mit dem Wissen und unter Zustimmung des Kunden oder (ii) wenn der Zugriff aus Sicherheitsgründen erforderlich ist. Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte. +GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 4. Ausnahmen -Hat GitHub Grund zu der Annahme, dass Inhalte eines privaten Repositorys gegen Gesetze oder diese Vereinbarung verstoßen, hat GitHub das Recht, auf die betreffenden Inhalte zuzugreifen und sie zu prüfen sowie zu entfernen. Darüber hinaus kann GitHub [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte der privaten Repositorys des Kunden offenzulegen. Sofern GitHub nicht durch gesetzliche Auflagen oder in Reaktion auf eine Sicherheitsbedrohung oder ein sonstiges Sicherheitsrisiko anders gebunden ist, informiert GitHub über entsprechende Maßnahmen. +Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte. + +Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. Richtlinien bezüglich geistigem Eigentum @@ -270,12 +273,12 @@ Keine Partei verwendet die vertraulichen Informationen der jeweils anderen Parte Fordert der Kunde Dienstleistungen an, legt GitHub eine Leistungsbeschreibung zu den entsprechenden Dienstleistungen vor. GitHub erbringt die in der jeweiligen Leistungsbeschreibung beschriebenen Dienstleistungen. GitHub steuert die Art und die Mittel zur Erbringung der Dienstleistungen und behält sich das Recht vor, die beauftragten Mitarbeiter auszuwählen. GitHub kann die Dienstleistungen durch Dritte erbringen lassen, sofern GitHub für deren Handlungen und Unterlassungen haftet. Der Kunde ist einverstanden und akzeptiert, dass GitHub alle Rechte, Ansprüche und Anteile an allen Elementen behält, die in Zusammenhang mit der Erbringung der Dienstleistungen genutzt oder entwickelt werden, unter anderem Software, Tools, Spezifikationen, Ideen, Entwürfe, Erfindungen, Prozesse, Verfahren und Know-how. Insoweit GitHub dem Kunden während der Erbringung der Dienstleistungen Elemente bereitstellt, gewährt GitHub dem Kunden eine nicht exklusive, nicht übertragbare, weltweite, unentgeltliche, zeitlich beschränkte Lizenz zur Nutzung dieser Elemente über die Laufzeit dieser Vereinbarung, die ausschließlich in Verbindung mit der Nutzung des Dienstes durch den Kunden gilt. ### R. Änderungen des Dienstes oder der Nutzungsbedingungen -GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub informiert den Kunden durch Veröffentlichung einer Mitteilung im Dienst über wesentliche Änderungen dieser Vereinbarung wie z. B. Preisänderungen mindestens 30 Tage vor Inkrafttreten der Änderung. Bei geringfügigen Änderungen stellt die fortgesetzte Nutzung des Dienstes durch den Kunden die Zustimmung zu den Änderungen dieser Vereinbarung dar. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen. +GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen. Die Änderung des Dienstes durch GitHub erfolgt durch Updates und Hinzufügen neuer Funktionen. Ungeachtet des Vorstehenden behält sich GitHub das Recht vor, den Dienst (oder einen Teil davon) jederzeit mit oder ohne vorherige Ankündigung vorübergehend oder dauerhaft zu ändern oder einzustellen. ### S. Unterstützung -GitHub leistet mit Ausnahme von Wochenenden und US-Feiertagen an fünf (5) Tagen pro Woche rund um die Uhr kostenlosen technischen Standard-Support für den Dienst. holidays. Standard-Support wird ausschließlich über webgestützte Ticketeinreichung über den GitHub-Support erbracht, und Supportanfragen müssen von einem Benutzer stammen, mit dem das GitHub-Supportteam interagieren kann. GitHub kann Premium-Support (gemäß den Bedingungen von [GitHub-Premium-Support für Enterprise](/articles/about-github-premium-support)) oder besonderen technischen Support für den Dienst mit der Supportstufe zu den Gebühren über die Abonnementlaufzeit gewähren, die in einem Auftragsformular oder einer Leistungsbeschreibung angegeben sind. +GitHub leistet mit Ausnahme von Wochenenden und US-Feiertagen an fünf (5) Tagen pro Woche rund um die Uhr kostenlosen technischen Standard-Support für den Dienst. holidays. Standard-Support wird ausschließlich über webgestützte Ticketeinreichung über den GitHub-Support erbracht, und Supportanfragen müssen von einem Benutzer stammen, mit dem das GitHub-Supportteam interagieren kann. GitHub may provide premium Support (subject to the [GitHub Premium Support for Enterprise Cloud](/articles/about-github-premium-support) terms) or dedicated technical Support for the Service at the Support level, Fees, and Subscription Term specified in an Order Form or SOW. ### T. Sonstiges diff --git a/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md index 6aa8d2758a85..15059a6ed8f0 100644 --- a/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -26,6 +26,6 @@ For definitions of each Service feature (“**Service Feature**”) and to revi Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption -If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption should be sent to [GitHub Support](https://support.github.com/contact). +If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). Service Credits may take the form of a refund or credit to Customer’s account, cannot be exchanged into a cash amount, are limited to a maximum of ninety (90) days of paid service per calendar quarter, require Customer to have paid any outstanding invoices, and expire upon termination of Customer’s agreement with GitHub. Service Credits are the sole and exclusive remedy for any failure by GitHub to meet any obligations in this SLA. diff --git a/translations/de-DE/content/github/site-policy/github-enterprise-subscription-agreement.md b/translations/de-DE/content/github/site-policy/github-enterprise-subscription-agreement.md index 8f096ce814fe..65041e470807 100644 --- a/translations/de-DE/content/github/site-policy/github-enterprise-subscription-agreement.md +++ b/translations/de-DE/content/github/site-policy/github-enterprise-subscription-agreement.md @@ -7,7 +7,7 @@ versions: free-pro-team: '*' --- -Datum des Inkrafttretens dieser Fassung: 20. Juli 2020 +Version Effective Date: November 16, 2020 WENN DER KUNDE AUF „I AGREE“ („ICH STIMME ZU“) ODER EINE ÄHNLICHE SCHALTFLÄCHE KLICKT ODER EINES DER (NACHFOLGEND DEFINIERTEN) PRODUKTE VERWENDET, AKZEPTIERT ER DIE GESCHÄFTSBEDINGUNGEN DIESER VEREINBARUNG. WENN DER KUNDE DIESE VEREINBARUNG IM NAMEN EINER JURISTISCHEN PERSON SCHLIESST, SICHERT ER ZU, DASS ER RECHTLICH DAZU BEFUGT IST, DIESE VEREINBARUNG FÜR DIE JURISTISCHE PERSON ZU SCHLIESSEN. @@ -197,7 +197,7 @@ Diese Vereinbarung bildet zusammen mit den Anhängen und den einzelnen Auftragsf #### 1.13.11 Änderungen, Vorrang -GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub informiert den Kunden durch Veröffentlichung einer Mitteilung im Dienst über wesentliche Änderungen dieser Vereinbarung wie z. B. Preisänderungen mindestens 30 Tage vor Inkrafttreten der Änderung. Bei geringfügigen Änderungen stellt die fortgesetzte Nutzung des Dienstes durch den Kunden die Zustimmung zu den Änderungen dieser Vereinbarung dar. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen. Bei Widersprüchen zwischen den Bestimmungen dieser Vereinbarung und einem Auftragsformular oder einer Leistungsbeschreibung haben die Bestimmungen des Auftragsformulars oder der Leistungsbeschreibung Vorrang, jedoch nur für das entsprechende Auftragsformular bzw. die entsprechende Leistungsbeschreibung. +GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen. Bei Widersprüchen zwischen den Bestimmungen dieser Vereinbarung und einem Auftragsformular oder einer Leistungsbeschreibung haben die Bestimmungen des Auftragsformulars oder der Leistungsbeschreibung Vorrang, jedoch nur für das entsprechende Auftragsformular bzw. die entsprechende Leistungsbeschreibung. #### 1.13.12 Salvatorische Klausel @@ -296,7 +296,7 @@ Kunden können im Rahmen der Nutzung des Dienstes benutzergenerierte Inhalte ers **(ii)** Der Kunde gewährt die Rechte nach den Abschnitten 3.3.3 bis 3.3.6 kostenlos und zu den in den entsprechenden Abschnitten angegebenen Zwecken, bis der Kunde die Kundeninhalte von den GitHub-Servern entfernt. Davon ausgenommen sind Inhalte, die der Kunde öffentlich veröffentlicht hat und für die externe Benutzer ein Forking vorgenommen haben. In diesem Fall gilt die Lizenz unbefristet, bis alle Forks von Kundeninhalten von den GitHub-Servern entfernt wurden. Lädt der Kunde Kundeninhalte hoch, für die bereits eine Lizenz besteht, die GitHub die erforderlichen Rechte zur Ausführung des Dienstes gewährt, ist keine weitere Lizenz erforderlich. #### 3.3.3 Lizenzgewährung für GitHub -Der Kunde gewährt GitHub das Recht, Kundeninhalte zu speichern, zu analysieren und anzuzeigen und gelegentlich Kopien zu erstellen, insoweit dies zur Bereitstellung des Dienstes erforderlich ist. Dazu zählt das Recht, Kundeninhalte in die GitHub-Datenbank zu kopieren und Sicherungen zu erstellen, Kundeninhalte dem Kunden und anderen anzuzeigen, denen der Kunde die Inhalte anzeigen möchte, Kundeninhalte für einen Suchindex oder auf andere Weise auf den GitHub-Servern zu analysieren, Kundeninhalte für externe Benutzer freizugeben, für die der Kunde die Inhalte freigeben möchte, und Kundeninhalte wiederzugeben, insoweit es sich um Musik, Videos usw. handelt. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Dienstes zu verwenden. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist. +Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service. Dazu zählt das Recht, Kundeninhalte in die GitHub-Datenbank zu kopieren und Sicherungen zu erstellen, Kundeninhalte dem Kunden und anderen anzuzeigen, denen der Kunde die Inhalte anzeigen möchte, Kundeninhalte für einen Suchindex oder auf andere Weise auf den GitHub-Servern zu analysieren, Kundeninhalte für externe Benutzer freizugeben, für die der Kunde die Inhalte freigeben möchte, und Kundeninhalte wiederzugeben, insoweit es sich um Musik, Videos usw. handelt. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Dienstes zu verwenden. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist. #### 3.3.4 Lizenzgewährung für externe Benutzer **(i)** Inhalte, die der Kunde öffentlich postet, darunter Issues, Kommentare und Beiträge in Repositorys externer Benutzer, können von anderen angezeigt werden. Indem der Kunde seine Repositorys für die öffentliche Anzeige konfiguriert, stimmt er zu, dass externe Benutzer die Repositorys des Kunden anzeigen und kopieren können. @@ -318,10 +318,13 @@ Der Kunde haftet für die Verwaltung des Zugriffs auf seine privaten Repositorys GitHub betrachtet Kundeninhalte in den privaten Repositorys des Kunden als vertrauliche Informationen des Kunden. GitHub sorgt nach Abschnitt 1.4 für den Schutz und die strikte Wahrung der Vertraulichkeit von Kundeninhalten in privaten Repositorys. #### 3.4.3 Zugriff -GitHub kann ausschließlich in folgenden Fällen auf private Repositorys des Kunden zugreifen: (i) aus Gründen des Supports mit dem Wissen und unter Zustimmung des Kunden oder (ii) wenn der Zugriff aus Sicherheitsgründen erforderlich ist. Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte. +GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 3.4.4 Ausschlüsse -Hat GitHub Grund zu der Annahme, dass Inhalte eines privaten Repositorys gegen Gesetze oder diese Vereinbarung verstoßen, hat GitHub das Recht, auf die betreffenden Inhalte zuzugreifen und sie zu prüfen sowie zu entfernen. Darüber hinaus kann GitHub gesetzlich verpflichtet sein, Inhalte in privaten Repositorys des Kunden offenzulegen. Sofern GitHub nicht durch gesetzliche Auflagen oder in Reaktion auf eine Sicherheitsbedrohung oder ein sonstiges Sicherheitsrisiko anders gebunden ist, informiert GitHub über entsprechende Maßnahmen. +Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte. + +Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 3.5. Urheberrechtsvermerke 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 cc880475f359..5d4fd4b8c2cf 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 @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Effective date: July 22, 2020 +Effective date: November 16, 2020 Vielen Dank, dass Sie GitHub Inc. ("GitHub", "wir") Ihren Quellcode, Ihre Projekte und Ihre persönlichen Informationen anvertrauen. Die Speicherung Ihrer persönlichen Daten ist eine große Verantwortung, und wir möchten, dass Sie wissen, wie wir diese handhaben. @@ -150,23 +150,39 @@ Wir verkaufen Ihre personenbezogenen Benutzerinformationen **nicht** gegen eine Bitte beachten Sie: Der California Consumer Privacy Act of 2018 ("CCPA") verpflichtet Unternehmen, in ihren Datenschutzrichtlinien anzugeben, ob sie personenbezogene Daten gegen eine finanzielle oder sonstige Gegenleistung offenlegen. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. Weitere Informationen über den CCPA und wie wir diesen umsetzen, finden Sie [hier](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act). -### Weitere wichtige Informationen +### Repository-Inhalt + +#### Access to private repositories + +If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for +- security purposes +- to assist the repository owner with a support matter +- to maintain the integrity of the Service +- to comply with our legal obligations +- if we have reason to believe the contents are in violation of the law, or +- mit Ihrer Zustimmung. + +However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories). -#### Repository-Inhalt +Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts). -Personal von GitHub [haben keinen Zugang zu privaten Repositorys](/github/site-policy/github-terms-of-service#e-private-repositories), es sei denn, dies ist aus Sicherheitsgründen, zur Unterstützung des Repository-Eigentümers bei einer Supportanfrage, zur Aufrechterhaltung der Integrität des Dienstes oder zur Erfüllung unserer rechtlichen Verpflichtungen erforderlich. However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, or other content known to violate our Terms, such as violent extremist or terrorist content or child exploitation imagery based on algorithmic fingerprinting techniques. Unsere Nutzungsbedingungen enthalten [weitere Details](/github/site-policy/github-terms-of-service#e-private-repositories). +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. -Wenn Ihr Repository öffentlich ist, kann jeder seinen Inhalt anzeigen. Wenn Sie private, vertrauliche oder [Sensible personenbezogene Daten](https://gdpr-info.eu/art-9-gdpr/), wie z.B. E-Mail-Adressen oder Passwörter, in Ihr öffentliches Repository eingeben, können diese Informationen von Suchmaschinen indexiert oder von Dritten verwendet werden. +#### Public repositories + +Wenn Ihr Repository öffentlich ist, kann jeder seinen Inhalt anzeigen. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. Weitere Informationen finden Sie unter [Personenbezogene Benutzerdaten in öffentlichen Repositorys](/github/site-policy/github-privacy-statement#public-information-on-github). +### Weitere wichtige Informationen + #### Öffentliche Informationen auf GitHub Viele GitHub-Dienste und -Funktionen sind öffentlich zugänglich. Wenn Ihre Inhalte öffentlich zugänglich sind, können Dritte auf diese in Übereinstimmung mit unseren Nutzungsbedingungen zugreifen und diese verwenden, z. B. indem Sie Ihr Profil oder Ihre Repositorys anzeigen oder Daten über unser API abrufen. Wir verkaufen diese Inhalte nicht; sie gehören Ihnen. Wir gestatten es jedoch Dritten, wie z.B. Forschungsorganisationen oder Archiven, öffentlich zugängliche GitHub-Informationen zu sammeln. Es ist bekannt, dass andere Dritte, wie z.B. Datenbroker, ebenfalls mittels Scraping auf GitHub zurückgreifen und Daten sammeln. Ihre personenbezogenen Benutzerdaten in Verbindung mit Ihren Inhalten könnten von Dritten im Rahmen dieser Erfassungen von GitHub-Daten gesammelt werden. Wenn Sie nicht möchten, dass Ihre personenbezogenen Benutzerdaten in den GitHub-Datensammlungen von Dritten erscheinen, machen Sie Ihre personenbezogenen Benutzerdaten bitte nicht öffentlich zugänglich und stellen Sie sicher, dass [Ihre E-Mail-Adresse in Ihrem Benutzerprofil](https://github.com/settings/emails) und in Ihren [Git Commit-Einstellungen als privat konfiguriert ist](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Wir setzen derzeit standardmäßig die E-Mail-Adresse der Benutzer auf privat, aber alte GitHub-Benutzer müssen möglicherweise ihre Einstellungen aktualisieren. -Wenn Sie GitHub-Daten zusammenstellen möchten, müssen Sie unsere Nutzungsbedingungen in Bezug auf [Scraping](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions) und [Datenschutz](/github/site-policy/github-acceptable-use-policies#6-privacy) erfüllen, und Sie dürfen alle öffentlich zugänglichen personenbezogenen Daten, die Sie sammeln, nur für den Zweck verwenden, für den unser Benutzer dies autorisiert hat. Wenn z. B. ein GitHub-Benutzer eine E-Mail-Adresse zum Zwecke der Identifizierung und Zuordnung öffentlich zugänglich gemacht hat, dürfen Sie Sie diese E-Mail-Adresse nicht für kommerzielle Werbung verwenden. Wir erwarten von Ihnen, dass Sie einen angemessenen Schutz aller personenbezogenen Daten von Benutzern, die Sie von dem Dienst erfasst haben garantieren, und Beschwerden, Aufforderungen zur Löschung und Kontaktverbote von uns oder anderen Benutzern umgehend beantworten. +If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. Wir erwarten von Ihnen, dass Sie einen angemessenen Schutz aller personenbezogenen Daten von Benutzern, die Sie von dem Dienst erfasst haben garantieren, und Beschwerden, Aufforderungen zur Löschung und Kontaktverbote von uns oder anderen Benutzern umgehend beantworten. Ebenso können Projekte auf GitHub öffentlich zugängliche personenbezogene Benutzerdaten enthalten, die im Rahmen des kollaborativen Prozesses erfasst werden. Wenn Sie eine Beschwerde über persönliche Benutzerdaten auf GitHub haben, lesen Sie bitte unseren Abschnitt [Beilegung von Beschwerden](/github/site-policy/github-privacy-statement#resolving-complaints). @@ -219,7 +235,7 @@ Die von Ihnen angegebene E-Mail-Adresse [über Ihre Git-Commit-Einstellungen](/g #### Cookies -GitHub verwendet Cookies, um die Interaktion mit unserem Dienst einfach und sinnvoll zu machen. Cookies sind kleine Textdateien, die oft von Websites auf Computer-Festplatten oder mobilen Geräten von Besuchern gespeichert werden. Wir verwenden Cookies (und ähnliche Technologien wie HTML5 localStorage), um Sie eingeloggt zu halten, Ihre Präferenzen zu speichern und Informationen für die zukünftige Entwicklung von GitHub bereitzustellen. Wir verwenden Cookies aus Sicherheitsgründen, um ein Gerät zu identifizieren. Durch die Nutzung unserer Website erklären Sie sich damit einverstanden, dass wir diese Arten von Cookies auf Ihrem Computer oder Gerät speichern. Wenn Sie die Speicherung von Cookies auf Ihrem Browser oder Gerät deaktivieren, können Sie sich weder anmelden noch die Dienste von GitHub nutzen. +GitHub uses cookies and similar technologies (e.g., HTML5 localStorage) to make interactions with our service easy and meaningful. Cookies sind kleine Textdateien, die oft von Websites auf Computer-Festplatten oder mobilen Geräten von Besuchern gespeichert werden. We use cookies and similar technologies (hereafter collectively "cookies") to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. Durch die Nutzung unserer Website erklären Sie sich damit einverstanden, dass wir diese Arten von Cookies auf Ihrem Computer oder Gerät speichern. Wenn Sie die Speicherung von Cookies auf Ihrem Browser oder Gerät deaktivieren, können Sie sich weder anmelden noch die Dienste von GitHub nutzen. Auf unserer Webseite [Cookies und Tracking](/github/site-policy/github-subprocessors-and-cookies) beschreiben wir die von uns gesetzten Cookies, die Voraussetzungen für diese Cookies und die unterschiedlichen Arten von Cookies (temporär oder permanent). Die Website enthält außerdem eine Liste unserer externen Analyse- und Dienstanbieter sowie genaue Angaben darüber, welche Teile unserer Website von diesen Anbietern erfasst werden dürfen. @@ -300,7 +316,7 @@ Im unwahrscheinlichen Fall, dass es zu einem Streit zwischen Ihnen und GitHub ü ### Änderungen an unserer Datenschutzerklärung -GitHub kann unsere Datenschutzerklärung von Zeit zu Zeit ändern, wobei die meisten Änderungen eher geringfügig sein dürften. Wir werden die Benutzer über unsere Website mindestens 30 Tage vor Inkrafttreten der Änderung über wesentliche Änderungen dieser Datenschutzerklärung informieren, indem wir eine Benachrichtigung auf unserer Homepage veröffentlichen oder E-Mails an die primäre E-Mail-Adresse versenden, die in Ihrem GitHub-Konto angegeben ist. Wir werden auch unser [Websiterichtlinien-Repository](https://github.com/github/site-policy/) aktualisieren, das alle Änderungen an dieser Richtlinie nachverfolgt. Für Änderungen an dieser Datenschutzerklärung, die keine wesentlichen Änderungen sind oder ihre Rechte nicht beeinträchtigen, empfehlen wir Benutzern, regelmäßig unser Websiterichtlinien-Repository zu besuchen. +GitHub kann unsere Datenschutzerklärung von Zeit zu Zeit ändern, wobei die meisten Änderungen eher geringfügig sein dürften. Wir werden die Benutzer über unsere Website mindestens 30 Tage vor Inkrafttreten der Änderung über wesentliche Änderungen dieser Datenschutzerklärung informieren, indem wir eine Benachrichtigung auf unserer Homepage veröffentlichen oder E-Mails an die primäre E-Mail-Adresse versenden, die in Ihrem GitHub-Konto angegeben ist. Wir werden auch unser [Websiterichtlinien-Repository](https://github.com/github/site-policy/) aktualisieren, das alle Änderungen an dieser Richtlinie nachverfolgt. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### Lizenz diff --git a/translations/de-DE/content/github/site-policy/github-terms-of-service.md b/translations/de-DE/content/github/site-policy/github-terms-of-service.md index 455bee56b452..0e29da26c3c2 100644 --- a/translations/de-DE/content/github/site-policy/github-terms-of-service.md +++ b/translations/de-DE/content/github/site-policy/github-terms-of-service.md @@ -32,11 +32,11 @@ Vielen Dank für die Nutzung von GitHub! Wir freuen uns, dass Sie hier sind. Bit | [N. Gewährleistungsausschluss](#n-disclaimer-of-warranties) | Wir bieten unseren Service so an, wie er ist, und wir geben keine Versprechungen oder Garantien für diesen Service. **Bitte lesen Sie diesen Abschnitt sorgfältig durch; es sollte Ihnen klar sein, was Sie erwartet.** | | [O. Haftungsbeschränkung](#o-limitation-of-liability) | Wir sind nicht haftbar für Schäden oder Verluste, die sich aus Ihrer Nutzung oder der Unfähigkeit zur Nutzung des Dienstes oder anderweitig aus dieser Vereinbarung ergeben. **Bitte lesen Sie diesen Abschnitt sorgfältig durch; er schränkt unsere Verpflichtungen Ihnen gegenüber ein.** | | [P. Freistellung und Schadloshaltung](#p-release-and-indemnification) | Sie tragen die volle Verantwortung für Ihre Nutzung des Dienstes. | -| [Q. Änderungen an diesen Nutzungsbedingungen](#q-changes-to-these-terms) | Wir können diese Vereinbarung ändern, aber wir werden Sie 30 Tage vorher über Änderungen informieren, die Ihre Rechte beeinträchtigen. | +| [Q. Änderungen an diesen Nutzungsbedingungen](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. | | [R. Sonstiges](#r-miscellaneous) | Bitte beachten Sie diesen Abschnitt für rechtliche Einzelheiten einschließlich unserer Rechtswahl. | ### Die GitHub-Nutzungsbedingungen -Datum des Inkrafttretens: 2. April 2020 +Effective date: November 16, 2020 ### A. Definitionen @@ -98,7 +98,7 @@ Sie erklären sich damit einverstanden, dass Sie unter keinen Umständen gegen u Sie können im Rahmen der Nutzung des Dienstes benutzergenerierte Inhalte erstellen oder hochladen. Sie sind allein verantwortlich für den Inhalt und für Schäden, die sich aus nutzergenerierten Inhalten ergeben, die Sie veröffentlichen, hochladen, verlinken oder anderweitig über den Dienst zur Verfügung stellen, unabhängig von der Form dieser Inhalte. Wir haften nicht für die Veröffentlichung oder den falschen Gebrauch benutzergenerierter Inhalte. #### 2. GitHub kann Inhalte entfernen -We do not pre-screen User-Generated Content, but we have the right (though not the obligation) to refuse or remove any User-Generated Content that, in our sole discretion, violates any [GitHub terms or policies](/github/site-policy). +We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub for mobile may be subject to mobile app stores' additional terms. #### 3. Eigentumsrechte an Inhalten, Recht auf Veröffentlichung und Lizenzgewährung Sie verbleiben Eigentümer Ihrer Inhalte und sind für diese verantwortlich. Wenn Sie etwas veröffentlichen, das Sie nicht selbst erstellt haben oder für das Sie nicht die Rechte besitzen, erklären Sie sich damit einverstanden, dass Sie für alle Inhalte, die Sie veröffentlichen, verantwortlich sind; dass Sie nur Inhalte einreichen, zu deren Veröffentlichung Sie berechtigt sind; und dass Sie alle Lizenzen Dritter in Bezug auf Inhalte, die Sie veröffentlichen vollständig einhalten werden. @@ -106,9 +106,9 @@ Sie verbleiben Eigentümer Ihrer Inhalte und sind für diese verantwortlich. Wen Da Sie weiterhin das Eigentum und die Verantwortung für Ihre Inhalte behalten, müssen Sie uns – und anderen GitHub-Benutzern – bestimmte Berechtigungen erteilen, die in den Abschnitten D.4 - D7. Diese Lizenzerteilungen gelten für Ihre Inhalte. Laden Sie Inhalte hoch, für die bereits eine Lizenz besteht, die GitHub die erforderlichen Rechte zur Ausführung des Dienstes gewährt, ist keine weitere Lizenz erforderlich. Sie verstehen, dass Sie keine Zahlung für eines der in den Abschnitten D.4 — D.7 gewährten Rechte erhalten. Die Lizenzen, die Sie uns gewähren, enden, wenn Sie Ihre Inhalte von unseren Servern entfernen, es sei denn er wurde von anderen Benutzern geforkt. #### 4. Lizenzvergabe an uns -Wir müssen gesetzlich befugt sein, Dinge wie das Hosten Ihrer Inhalte, deren Veröffentlichung und Weitergabe durchzuführen. Sie gewähren uns und unseren Rechtsnachfolgern das Recht, Ihre Inhalte zu speichern, zu analysieren und anzuzeigen und bei Bedarf Nebenkopien anzustellen, um die Website zu erstellen und den Dienst bereitzustellen. Dies schließt das Recht ein, Aktivitäten wie das Kopieren in unsere Datenbank und die Anfertigung von Sicherungskopien durchzuführen, sie Ihnen und anderen Benutzern zu zeigen, sie in einen Suchindex zu übernehmen oder anderweitig auf unseren Servern zu analysieren, sie mit anderen Benutzern zu teilen und sie vorzuführen, falls es sich bei Ihren Inhalten um Musik oder Videos handelt. +Wir müssen gesetzlich befugt sein, Dinge wie das Hosten Ihrer Inhalte, deren Veröffentlichung und Weitergabe durchzuführen. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. -Diese Lizenz gewährt GitHub nicht das Recht, Ihre Inhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb unseres bereitgestellten Dienstes zu verwenden. +This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/). #### 5. Lizenzgewährung für andere Benutzer Benutzergenerierte Inhalte, die Sie öffentlich posten, darunter Issues, Kommentare und Beiträge in Repositorys externer Benutzer, können von anderen angezeigt werden. Indem Sie festlegen, dass Ihre Repositorys öffentlich angezeigt werden, erklären Sie sich damit einverstanden, dass andere Ihre Repositorys anzeigen und „forken" können (das bedeutet, dass andere ihre eigenen Kopien von Inhalten aus Ihren Repositorys in von ihnen kontrollierte Repositorys erstellen können). @@ -116,7 +116,7 @@ Benutzergenerierte Inhalte, die Sie öffentlich posten, darunter Issues, Komment Konfigurieren Sie Ihre Pages und Repositorys für die öffentliche Anzeige, gewähren Sie allen GitHub-Benutzern eine nicht exklusive, weltweite Lizenz zur Verwendung, Anzeige und Wiedergabe Ihrer Inhalte über den GitHub-Dienst und zur Reproduktion von Ihrer Inhalte ausschließlich auf GitHub, insoweit dies nach den von GitHub bereitgestellten Funktionen zulässig ist (beispielsweise durch Forking). Sie können weitere Rechte gewähren, wenn der Sie [eine Lizenz einführen](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Wenn Sie Inhalte hochladen, die Sie nicht selber erstellt haben oder die Ihnen nicht gehören, haften Sie dafür sicherzustellen, dass die von Ihnen hochgeladenen Inhalte nach den Bedingungen lizenziert sind, mit denen diese Rechte GitHub-Benutzern gewährt werden. #### 6. Beiträge im Rahmen einer Repository-Lizenz -Jedesmal wenn Sie einen Beitrag zu einem Repository mit einem Lizenzhinweis machen, lizenzieren Sie Ihren Beitrag zu denselben Bedingungen und erklären, dass Sie das Recht haben, den entsprechenden Beitrag zu diesen Bedingungen zu lizenzieren. Wenn Sie über eine gesonderte Vereinbarung zur Lizenzierung Ihrer Beiträge nach anderen Bedingungen wie z. B. einer Mitwirkungslizenzvereinbarung verfügen, hat die entsprechende Vereinbarung Vorrang. +Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. Funktioniert das nicht bereits so? Ja. Dies wird weithin als die Norm in der Open-Source-Community akzeptiert; es wird üblicherweise mit der Abkürzung "inbound=outbound" bezeichnet. Wir machen es nur explizit. @@ -126,7 +126,7 @@ Sie behalten alle Urheberpersönlichkeitsrechte an Ihren Inhalten, die Sie hochl Soweit diese Vereinbarung durch anwendbares Recht nicht durchsetzbar ist gewähren Sie GitHub die Rechte, die wir benötigen, um Ihren Inhalt ohne Nennung zu nutzen und angemessene Anpassungen an Ihren Inhalten vorzunehmen, wenn dies für die Darstellung der Website und die Bereitstellung der Dienste erforderlich ist. ### E. Private Repositorys -**Kurzversion:** *Sie haben möglicherweise Zugriff auf private Repositorys. Wir behandeln den Inhalt privater Repositorys vertraulich und greifen nur aus Supportgründen, mit Ihrer Zustimmung oder wenn dies aus Sicherheitsgründen erforderlich ist, darauf zu.* +**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.* #### 1. Kontrolle privater Repositorys Einige Konten verfügen möglicherweise über private Repositorys, die es dem Benutzer ermöglichen, den Zugriff auf Inhalte zu steuern. @@ -135,15 +135,14 @@ Einige Konten verfügen möglicherweise über private Repositorys, die es dem Be GitHub betrachtet den Inhalt privater Repositorys als vertraulich. GitHub schützt die Inhalte privater Repositorys vor unbefugter Nutzung, Unbefugtem Zugriff oder Offenlegung in der gleichen Weise, die wir verwenden würden, um unsere eigenen vertraulichen Informationen ähnlicher Art, und in keinem Fall mit weniger als einem angemessenen Maß an Sorgfalt, zu schützen. #### 3. Zugriff -GitHub-Mitarbeiter dürfen nur in den folgenden Situationen auf den Inhalt Ihrer privaten Repositorys zugreifen: -- Mit Ihrer Zustimmung und Ihrem Wissen, aus Supportgründen. Wenn GitHub aus Supportgründen auf ein privates Repository zugreift, tun wir dies nur mit der Zustimmung und dem Wissen des Eigentümers. -- Wenn der Zugriff aus Sicherheitsgründen erforderlich ist, einschließlich wenn dies zur Aufrechterhaltung der kontinuierlichen Vertraulichkeit, Integrität, Verfügbarkeit und Belastbarkeit der Systeme und Dienste von GitHub erforderlich ist. +GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). Sie können zusätzlichen Zugriff auf Ihre privaten Repositorys aktivieren. Ein Beispiel: - Sie können beispielsweise mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Ihre Inhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Service oder Funktion variieren, aber GitHub wird Ihre privaten Repository-Inhalte weiterhin vertraulich behandeln. Sind für diese Dienste oder Features neben den Rechten, die für die Bereitstellung des GitHub-Dienstes erforderlich sind, zusätzliche Rechte erforderlich, geben wir eine Erläuterung dieser Rechte. -#### 4. Ausnahmen -Haben wir Grund zu der Annahme, dass Inhalte eines privaten Repositorys gegen Gesetze oder diese Bedingungen verstoßen, haben wir das Recht, auf die betreffenden Inhalte zuzugreifen und sie zu prüfen sowie zu entfernen. Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen. +Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. Urheberrechtsverletzungen und DMCA-Richtlinie Wenn Sie glauben, dass Inhalte auf unserer Website gegen Ihr Urheberrecht verstoßen kontaktieren Sie uns bitte in Übereinstimmung mit unserer [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). Wenn Sie ein Urheberrechtsinhaber sind und der Meinung sind, dass Inhalte auf GitHub Ihre Rechte verletzen, kontaktieren Sie uns bitte über [unser dafür vorgesehenes DMCA-Formular](https://github.com/contact/dmca) oder per E-Mail unter copyright@github.com. Die Zusendung einer falschen oder leichtfertigen Takedown-Mitteilung kann rechtliche Konsequenzen haben. Bevor Sie eine Takedown-Anfrage senden, müssen Sie rechtliche Verwendungszwecke wie faire Nutzung und lizenzierte Nutzungen in Betracht ziehen. @@ -286,9 +285,9 @@ Wenn Sie eine Streitigkeit mit einem oder mehreren Benutzer haben, entbinden Sie Sie erklären sich damit einverstanden, uns in Bezug auf alle Ansprüche, Verbindlichkeiten und Ausgaben, einschließlich Anwaltskosten, die sich aus Ihrer Nutzung der Website und des Dienstes ergeben, zu befreien, zu verteidigen und schadlos zu halten, unter anderem aufgrund Ihrer Verletzung diesen Nutzungsbedingungen, vorausgesetzt, dass GitHub (1) Sie unverzüglich schriftlich über den Anspruch, die Forderung, die Klage oder das Verfahren informiert; (2) Ihnen die alleinige Kontrolle über die Verteidigung und Beilegung des Anspruchs, der Forderung, der Klage oder des Verfahrens gibt (vorausgesetzt, dass Sie keinen Anspruch, keine Forderung, keine Klage oder kein Verfahren beilegen dürfen, solange diese Beilegung GitHub nicht bedingungslos von jeglicher Haftung entbindet); und (3) Ihnen auf Ihre Kosten jede angemessene Unterstützung gewährt. ### Q. Änderungen dieser Bedingungen -**Kurzversion:** *Wir möchten, dass unsere Benutzer über wichtige Änderungen unserer Bedingungen informiert werden, aber einige Änderungen sind nicht so wichtig – wir wollen Sie nicht jedes Mal stören, wenn wir einen Tippfehler korrigieren. Obwohl wir diese Vereinbarung jederzeit ändern können, werden wir die Benutzer über alle Änderungen informieren, die Ihre Rechte beeinträchtigen, und Ihnen Zeit geben, sich darauf einzustellen.* +**Kurzversion:** *Wir möchten, dass unsere Benutzer über wichtige Änderungen unserer Bedingungen informiert werden, aber einige Änderungen sind nicht so wichtig – wir wollen Sie nicht jedes Mal stören, wenn wir einen Tippfehler korrigieren. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.* -Wir behalten uns das Recht vor, diese Nutzungsbedingungen jederzeit nach unserem alleinigem Ermessen zu ändern, und aktualisieren diese Vereinbarung im Fall entsprechender Änderungen. Wir informieren unsere Benutzer über wesentliche Änderungen dieser Vereinbarung wie z. B. Preisänderungen mindestens 30 Tage vor Inkrafttreten der Änderung durch Veröffentlichung einer Mitteilung auf unserer Website. Bei geringfügigen Änderungen stellt Ihre fortgesetzte Nutzung der Website die Zustimmung zu den Änderungen dieser Nutzungsbedingungen dar. Alle Änderungen dieser Bedingungen können Sie in unserem Repository [Site Policy](https://github.com/github/site-policy) einsehen. +Wir behalten uns das Recht vor, diese Nutzungsbedingungen jederzeit nach unserem alleinigem Ermessen zu ändern, und aktualisieren diese Vereinbarung im Fall entsprechender Änderungen. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. Alle Änderungen dieser Bedingungen können Sie in unserem Repository [Site Policy](https://github.com/github/site-policy) einsehen. Wir behalten uns das Recht vor, die Website (oder einen Teil davon) zu gegebener Zeit und ohne Ankündigung vorübergehend oder dauerhaft zu modifizieren oder einzustellen. diff --git a/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md index a128b1256b94..a51a00295203 100644 --- a/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md +++ b/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md @@ -41,12 +41,12 @@ In Unterhaltungen auf {% data variables.product.product_name %} werden Verweise Verweise auf den SHA-Hash eines Commits werden zum Committen auf {% data variables.product.product_name %} automatisch in verkürzte Links umgewandelt. -| Verweistyp | Rohverweis | Kurzlink | -| --------------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | -| Commit-URL | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| Benutzer@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| Benutzername/Repository@SHA | jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| Verweistyp | Rohverweis | Kurzlink | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | +| Commit-URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| Benutzer@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| `Benutzername/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | ### Benutzerdefinierte automatische Verknüpfungen von externen Ressourcen diff --git a/translations/de-DE/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md b/translations/de-DE/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md index 72f35ed57037..b6bc4413d98a 100644 --- a/translations/de-DE/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md +++ b/translations/de-DE/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md @@ -8,19 +8,24 @@ versions: {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% endnote %} - {% data reusables.package_registry.container-registry-feature-highlights %} To share context about your package's use, you can link a repository to your container image on {% data variables.product.prodname_dotcom %}. For more information, see "[Connecting a repository to a container image](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)." ### Unterstützte Formate -The {% data variables.product.prodname_container_registry %} currently only supports Docker images. +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +#### Manifest Lists/Image Indexes +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. ### Visibility and access permissions for container images diff --git a/translations/de-DE/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md b/translations/de-DE/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md new file mode 100644 index 000000000000..9803263ee3f7 --- /dev/null +++ b/translations/de-DE/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md @@ -0,0 +1,37 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)“. + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + + ![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/de-DE/content/packages/getting-started-with-github-container-registry/index.md b/translations/de-DE/content/packages/getting-started-with-github-container-registry/index.md index 46849f39a609..f07fd0941c04 100644 --- a/translations/de-DE/content/packages/getting-started-with-github-container-registry/index.md +++ b/translations/de-DE/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 %} For more information about configuring, deleting, pushing, or pulling container images, see "[Managing container images with {% data variables.product.prodname_github_container_registry %}](/packages/managing-container-images-with-github-container-registry)." diff --git a/translations/de-DE/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md b/translations/de-DE/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md index 3742e6aed285..f983b83cb3f6 100644 --- a/translations/de-DE/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md +++ b/translations/de-DE/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md @@ -31,6 +31,8 @@ The domain for the {% data variables.product.prodname_container_registry %} is ` ### Authenticating with the container registry +{% data reusables.package_registry.feature-preview-for-container-registry %} + You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}. {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} @@ -72,6 +74,8 @@ To move Docker images that you host on {% data variables.product.prodname_regist ### Updating your {% data variables.product.prodname_actions %} workflow +{% data reusables.package_registry.feature-preview-for-container-registry %} + If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers. 1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)." diff --git a/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md b/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md index 05fc53b92d0a..81110a4ffcf7 100644 --- a/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md +++ b/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md @@ -24,7 +24,7 @@ If you have admin permissions to an organization-owned container image, you can If your package is owned by an organization and private, then you can only give access to other organization members or teams. -For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) @@ -54,7 +54,7 @@ When you first publish a package, the default visibility is private and only you A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. -For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 5. Under "Danger Zone", choose a visibility setting: diff --git a/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md b/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md index 0d4d0873d2d1..ddf6eae62764 100644 --- a/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md +++ b/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md @@ -16,8 +16,6 @@ To delete a container image, you must have admin permissions to the container im When deleting public packages, be aware that you may break projects that depend on your package. - - ### Reserved package versions and names {% data reusables.package_registry.package-immutability %} diff --git a/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md index 278fb66f7e85..0f97119f7969 100644 --- a/translations/de-DE/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ b/translations/de-DE/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 %} -To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." ### Bei {% data variables.product.prodname_github_container_registry %} authentifizieren 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 b37386ead306..a0117236724b 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 @@ -26,6 +26,8 @@ When you create a {% data variables.product.prodname_actions %} workflow, you ca {% data reusables.package_registry.container-registry-beta %} +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + {% endif %} #### Pakete anzeigen @@ -34,17 +36,17 @@ You can configure webhooks to subscribe to package-related events, such as when #### About package permissions and visibility {% if currentVersion == "free-pro-team@latest" %} -| | Package registries | {% data variables.product.prodname_github_container_registry %} -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. | -| Permissions | {{ 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. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. | +| | Package registries | {% data variables.product.prodname_github_container_registry %} +| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. | +| Permissions | {% 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. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. | Visibility | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | Anonymous access | N/A | You can access public container images anonymously. {% else %} -| | Package registries | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Hosting locations | You can host multiple packages in one repository. | -| Permissions | {{ 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. | +| | Package registries | +| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Hosting locations | You can host multiple packages in one repository. | +| Permissions | {% 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. | | Visibility | {% data reusables.package_registry.public-or-private-packages %} {% endif %} 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 c95e320b544c..abfdebe4a248 100644 --- a/translations/de-DE/content/rest/overview/other-authentication-methods.md +++ b/translations/de-DE/content/rest/overview/other-authentication-methods.md @@ -37,12 +37,22 @@ $ curl -u username:token {% data variables.product.api_url_pre This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. -{% if enterpriseServerVersions contains currentVersion %} #### Via username and password -{% data reusables.apps.deprecating_password_auth %} +{% if currentVersion == "free-pro-team@latest" %} + +{% 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 %} -To use Basic Authentication with the {% data variables.product.product_name %} API, simply send the username and password associated with the account. +{% 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. For example, if you're accessing the API via [cURL][curl], the following command would authenticate you if you replace `` with your {% data variables.product.product_name %} username. (cURL will prompt you to enter the password.) @@ -88,14 +98,13 @@ The value `organizations` is a comma-separated list of organization IDs for orga {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ### Working with two-factor authentication -{% data reusables.apps.deprecating_password_auth %} - -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 or OAuth token instead of your username and password. - -You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}with [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %} or use the "[Create a new authorization][create-access]" endpoint in the OAuth Authorizations API to generate a new OAuth token. 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)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the GitHub API. 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. +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 %}. 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)". 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 %} #### Using the OAuth Authorizations API with two-factor authentication When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code: @@ -114,7 +123,6 @@ $ curl --request POST \ ``` {% endif %} -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization [curl]: http://curl.haxx.se/ [oauth-auth]: /v3/#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line 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 88c4163b7811..0810b401dc02 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 @@ -135,9 +135,9 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar 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" @@ -165,19 +165,10 @@ $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product. 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 %} - -{% note %} - -**Note:** For {% data variables.product.prodname_ghe_server %}, [as with all other endpoints](/v3/enterprise-admin/#endpoint-urls), you'll need to pass your username and password. - -{% endnote %} - -{% endif %} - ### 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. diff --git a/translations/de-DE/content/rest/overview/troubleshooting.md b/translations/de-DE/content/rest/overview/troubleshooting.md index cd3d08c43da9..2e9e3993b876 100644 --- a/translations/de-DE/content/rest/overview/troubleshooting.md +++ b/translations/de-DE/content/rest/overview/troubleshooting.md @@ -13,16 +13,53 @@ versions: If you're encountering some oddities in the API, here's a list of resolutions to some of the problems you may be experiencing. -### Why am I getting a `404` error on a repository that exists? +### `404` error for an existing repository Typically, we send a `404` error when your client isn't properly authenticated. You might expect to see a `403 Forbidden` in these cases. However, since we don't want to provide _any_ information about private repositories, the API returns a `404` error instead. To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), and [third-party application restrictions][oap-guide] are not blocking access. -### Why am I not seeing all my results? +### Not all results returned 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. +{% 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. Ein Beispiel: + +```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/de-DE/content/rest/reference/interactions.md b/translations/de-DE/content/rest/reference/interactions.md index 9f3d4c2de5d7..683dc4155fff 100644 --- a/translations/de-DE/content/rest/reference/interactions.md +++ b/translations/de-DE/content/rest/reference/interactions.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -Users interact with repositories by commenting, opening issues, and creating pull requests. The Interactions APIs allow people with owner or admin access to temporarily restrict certain users from interacting with public repositories. +Users interact with repositories by commenting, opening issues, and creating 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 @@ Users interact with repositories by commenting, opening issues, and creating pul ## Organisation -The Organization Interactions API allows organization owners to temporarily restrict which users can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users: +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 %} in the organization. * {% data reusables.interactions.contributor-user-limit-definition %} in the organization. * {% data reusables.interactions.collaborator-user-limit-definition %} in the organization. +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 %} ## Repository -The Repository Interactions API allows people with owner or admin access to temporarily restrict which users can comment, open issues, or create pull requests in a public repository. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users: +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 repository. * {% data reusables.interactions.contributor-user-limit-definition %} in the repository. * {% data reusables.interactions.collaborator-user-limit-definition %} in the repository. +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 %} + +## Benutzer + +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/de-DE/content/rest/reference/oauth-authorizations.md b/translations/de-DE/content/rest/reference/oauth-authorizations.md index 8bb3e8fa72cc..356309baff03 100644 --- a/translations/de-DE/content/rest/reference/oauth-authorizations.md +++ b/translations/de-DE/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 %} - You can use this API to manage the access OAuth applications have to your account. You can only access this API via [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) using your username and password, not tokens. If you or your users 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). diff --git a/translations/de-DE/content/rest/reference/search.md b/translations/de-DE/content/rest/reference/search.md index 5d54615b9d4d..4425c5879d90 100644 --- a/translations/de-DE/content/rest/reference/search.md +++ b/translations/de-DE/content/rest/reference/search.md @@ -31,13 +31,19 @@ Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is: ``` -q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N +SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N ``` For example, if you wanted to search for all _repositories_ owned by `defunkt` that contained the word `GitHub` and `Octocat` in the README file, you would use the following query with the _search repositories_ endpoint: ``` -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. Ein Beispiel: +```javascript +// JavaScript +const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax/)." diff --git a/translations/de-DE/data/graphql/ghae/graphql_previews.ghae.yml b/translations/de-DE/data/graphql/ghae/graphql_previews.ghae.yml index 7f972f318e5b..278487e18981 100644 --- a/translations/de-DE/data/graphql/ghae/graphql_previews.ghae.yml +++ b/translations/de-DE/data/graphql/ghae/graphql_previews.ghae.yml @@ -85,7 +85,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Pinned Issues Preview description: This preview adds support for pinned issues. 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 7ad2acba5901..10f9989a1239 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 @@ -2,112 +2,112 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/de-DE/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml b/translations/de-DE/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml index 4cb2fcaddf2d..cff46f0627fe 100644 --- a/translations/de-DE/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/de-DE/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml @@ -2,63 +2,63 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/de-DE/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/de-DE/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml index dcf3d7d79244..76ece32029eb 100644 --- a/translations/de-DE/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/de-DE/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml @@ -2,560 +2,560 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` will be removed. Use the `Package` object instead." + description: '`color` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` will be removed. Use the `Package` object instead." + description: '`latestVersion` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` will be removed. Use the `Package` object instead." + description: '`name` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` will be removed. Use the `Package` object instead." + description: '`nameWithOwner` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` will be removed. Use the `Package` object." + description: '`packageFileByGuid` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` will be removed. Use the `Package` object." + description: '`packageFileBySha256` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` will be removed. Use the `Package` object instead." + description: '`packageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` will be removed. Use the `Package` object instead." + description: '`preReleaseVersions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` will be removed. Use the `Package` object instead." + description: '`registryPackageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` will be removed. Use the `Package` object instead." + description: '`repository` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` will be removed. Use the `Package` object instead." + description: '`statistics` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` will be removed. Use the `Package` object." + description: '`tags` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` will be removed. Use the `Package` object." + description: '`topics` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` will be removed. Use the `Package` object instead." + description: '`version` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` will be removed. Use the `Package` object instead." + description: '`versionByPlatform` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` will be removed. Use the `Package` object instead." + description: '`versionBySha256` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` will be removed. Use the `Package` object instead." + description: '`versions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` will be removed. Use the `Package` object instead." + description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` will be removed. Use the `PackageDependency` object instead." + description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` will be removed. Use the `PackageDependency` object instead." + description: '`name` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` will be removed. Use the `PackageDependency` object instead." + description: '`version` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` will be removed. Use the `PackageFile` object instead." + description: '`guid` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` will be removed. Use the `PackageFile` object instead." + description: '`md5` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` will be removed. Use the `PackageFile` object instead." + description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` will be removed. Use the `PackageFile` object instead." + description: '`name` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` will be removed. Use the `PackageFile` object instead." + description: '`packageVersion` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` will be removed. Use the `PackageFile` object instead." + description: '`sha1` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` will be removed. Use the `PackageFile` object instead." + description: '`sha256` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` will be removed. Use the `PackageFile` object instead." + description: '`size` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` will be removed. Use the `PackageFile` object instead." + description: '`url` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` will be removed. Use the `PackageTag` object instead." + description: '`name` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` will be removed. Use the `PackageTag` object instead." + description: '`version` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` will be removed. Use the `PackageVersion` object instead." + description: '`dependencies` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` will be removed. Use the `PackageVersion` object instead." + description: '`fileByName` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` will be removed. Use the `PackageVersion` object instead." + description: '`files` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` will be removed. Use the `PackageVersion` object instead." + description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` will be removed. Use the `PackageVersion` object instead." + description: '`manifest` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` will be removed. Use the `PackageVersion` object instead." + description: '`platform` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` will be removed. Use the `PackageVersion` object instead." + description: '`preRelease` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` will be removed. Use the `PackageVersion` object instead." + description: '`readme` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead." + description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` will be removed. Use the `PackageVersion` object instead." + description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` will be removed. Use the `PackageVersion` object instead." + description: '`release` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` will be removed. Use the `PackageVersion` object instead." + description: '`sha256` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` will be removed. Use the `PackageVersion` object instead." + description: '`size` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` will be removed. Use the `PackageVersion` object instead." + description: '`statistics` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` will be removed. Use the `PackageVersion` object instead." + description: '`summary` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` will be removed. Use the `PackageVersion` object instead." + description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` will be removed. Use the `PackageVersion` object instead." + description: '`version` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead." + description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking diff --git a/translations/de-DE/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/de-DE/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml index 4b56579d9316..5341a42e26e0 100644 --- a/translations/de-DE/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/de-DE/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml @@ -2,568 +2,568 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` will be removed. Use the `Package` object instead." + description: '`color` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` will be removed. Use the `Package` object instead." + description: '`latestVersion` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` will be removed. Use the `Package` object instead." + description: '`name` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` will be removed. Use the `Package` object instead." + description: '`nameWithOwner` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` will be removed. Use the `Package` object." + description: '`packageFileByGuid` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` will be removed. Use the `Package` object." + description: '`packageFileBySha256` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` will be removed. Use the `Package` object instead." + description: '`packageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` will be removed. Use the `Package` object instead." + description: '`preReleaseVersions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` will be removed. Use the `Package` object instead." + description: '`registryPackageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` will be removed. Use the `Package` object instead." + description: '`repository` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` will be removed. Use the `Package` object instead." + description: '`statistics` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` will be removed. Use the `Package` object." + description: '`tags` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` will be removed. Use the `Package` object." + description: '`topics` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` will be removed. Use the `Package` object instead." + description: '`version` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` will be removed. Use the `Package` object instead." + description: '`versionByPlatform` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` will be removed. Use the `Package` object instead." + description: '`versionBySha256` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` will be removed. Use the `Package` object instead." + description: '`versions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` will be removed. Use the `Package` object instead." + description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` will be removed. Use the `PackageDependency` object instead." + description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` will be removed. Use the `PackageDependency` object instead." + description: '`name` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` will be removed. Use the `PackageDependency` object instead." + description: '`version` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` will be removed. Use the `PackageFile` object instead." + description: '`guid` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` will be removed. Use the `PackageFile` object instead." + description: '`md5` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` will be removed. Use the `PackageFile` object instead." + description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` will be removed. Use the `PackageFile` object instead." + description: '`name` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` will be removed. Use the `PackageFile` object instead." + description: '`packageVersion` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` will be removed. Use the `PackageFile` object instead." + description: '`sha1` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` will be removed. Use the `PackageFile` object instead." + description: '`sha256` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` will be removed. Use the `PackageFile` object instead." + description: '`size` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` will be removed. Use the `PackageFile` object instead." + description: '`url` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` will be removed. Use the `PackageTag` object instead." + description: '`name` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` will be removed. Use the `PackageTag` object instead." + description: '`version` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.deleted - description: "`deleted` will be removed. Use the `PackageVersion` object instead." + description: '`deleted` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` will be removed. Use the `PackageVersion` object instead." + description: '`dependencies` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` will be removed. Use the `PackageVersion` object instead." + description: '`fileByName` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` will be removed. Use the `PackageVersion` object instead." + description: '`files` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` will be removed. Use the `PackageVersion` object instead." + description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` will be removed. Use the `PackageVersion` object instead." + description: '`manifest` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` will be removed. Use the `PackageVersion` object instead." + description: '`platform` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` will be removed. Use the `PackageVersion` object instead." + description: '`preRelease` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` will be removed. Use the `PackageVersion` object instead." + description: '`readme` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead." + description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` will be removed. Use the `PackageVersion` object instead." + description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` will be removed. Use the `PackageVersion` object instead." + description: '`release` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` will be removed. Use the `PackageVersion` object instead." + description: '`sha256` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` will be removed. Use the `PackageVersion` object instead." + description: '`size` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` will be removed. Use the `PackageVersion` object instead." + description: '`statistics` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` will be removed. Use the `PackageVersion` object instead." + description: '`summary` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` will be removed. Use the `PackageVersion` object instead." + description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` will be removed. Use the `PackageVersion` object instead." + description: '`version` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead." + description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea diff --git a/translations/de-DE/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/de-DE/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml index f5fb1765b079..977c97a5785e 100644 --- a/translations/de-DE/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/de-DE/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml @@ -2,71 +2,71 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea @@ -86,15 +86,15 @@ upcoming_changes: owner: oneill38 - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden @@ -107,21 +107,21 @@ upcoming_changes: owner: oneill38 - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/de-DE/data/graphql/graphql_previews.yml b/translations/de-DE/data/graphql/graphql_previews.yml index e248380363e5..788bb92a3c60 100644 --- a/translations/de-DE/data/graphql/graphql_previews.yml +++ b/translations/de-DE/data/graphql/graphql_previews.yml @@ -102,7 +102,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Pinned Issues Preview description: This preview adds support for pinned issues. 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 c8040777f133..f12ecd03316b 100644 --- a/translations/de-DE/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/de-DE/data/graphql/graphql_upcoming_changes.public.yml @@ -2,119 +2,119 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Query.sponsorsListing - description: "`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead." - reason: "`Query.sponsorsListing` will be removed." + description: '`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead.' + reason: '`Query.sponsorsListing` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/de-DE/data/reusables/feature-preview/feature-preview-setting.md b/translations/de-DE/data/reusables/feature-preview/feature-preview-setting.md new file mode 100644 index 000000000000..56ba031373d5 --- /dev/null +++ b/translations/de-DE/data/reusables/feature-preview/feature-preview-setting.md @@ -0,0 +1 @@ +1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf Dein Profilfoto und dann auf **Feature preview** (Funktions-Vorschau). ![Schaltfläche „Feature preview" (Funktions-Vorschau)](/assets/images/help/settings/feature-preview-button.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/gated-features/secret-scanning.md b/translations/de-DE/data/reusables/gated-features/secret-scanning.md new file mode 100644 index 000000000000..bd279034eee8 --- /dev/null +++ b/translations/de-DE/data/reusables/gated-features/secret-scanning.md @@ -0,0 +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 %} diff --git a/translations/de-DE/data/reusables/interactions/interactions-detail.md b/translations/de-DE/data/reusables/interactions/interactions-detail.md index 9193cd04e704..187a3e73074d 100644 --- a/translations/de-DE/data/reusables/interactions/interactions-detail.md +++ b/translations/de-DE/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -When restrictions are enabled, only the specified group of {% data variables.product.product_name %} users will be able to participate in interactions. Restrictions expire 24 hours from the time they are set. +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. diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-beta.md b/translations/de-DE/data/reusables/package_registry/container-registry-beta.md index c69375d5deb8..24313880baea 100644 --- a/translations/de-DE/data/reusables/package_registry/container-registry-beta.md +++ b/translations/de-DE/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)“. +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. 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)." {% endnote %} diff --git a/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md new file mode 100644 index 000000000000..b0cddc8bcb84 --- /dev/null +++ b/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% endnote %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/secret-scanning/beta.md b/translations/de-DE/data/reusables/secret-scanning/beta.md index ac6f249279e1..f6e29075319f 100644 --- a/translations/de-DE/data/reusables/secret-scanning/beta.md +++ b/translations/de-DE/data/reusables/secret-scanning/beta.md @@ -1,5 +1,5 @@ {% note %} -**Hinweis:** {% data variables.product.prodname_secret_scanning_caps %} für private Repositorys befindet sich derzeit in der Beta-Version und kann sich jederzeit verändern. Um Zugriff auf die Beta-Version zu erhalten, [tritt der Warteliste bei](https://github.com/features/security/advanced-security/signup). +**Hinweis:** {% data variables.product.prodname_secret_scanning_caps %} für private Repositorys befindet sich derzeit in der Beta-Version und kann sich jederzeit verändern. {% endnote %} diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml index b962e3042fa5..a1fbeca8d7a4 100644 --- a/translations/de-DE/data/ui.yml +++ b/translations/de-DE/data/ui.yml @@ -4,9 +4,10 @@ header: contact: Kontakt notices: ghae_silent_launch: GitHub AE is currently under limited release. Please contact our Sales Team to find out more. + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: Wir veröffentlichen regelmäßig Aktualisierungen unserer Dokumentation, und die Übersetzung dieser Seite kann noch im Gange sein. Die neuesten Informationen findest Du in der englischsprachigen Dokumentation. Informieren Sie uns bitte, falls auf dieser Seite ein Problem mit den Übersetzungen vorliegt. localization_in_progress: Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet, oder sie wird noch übersetzt. Die neuesten und genauesten Informationen findest Du in unserer englischsprachigen Dokumentation. - product_in_progress: '👋 Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet. Die neuesten und genauesten Informationen findest du in unserer Entwicklerdokumentation.' + early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' search: need_help: Benötigen Sie Hilfe? placeholder: Themen, Produkte suchen … @@ -19,7 +20,7 @@ toc: guides: Leitfäden whats_new: What's new pages: - article_version: "Artikelversion:" + article_version: 'Artikelversion:' miniToc: Inhalt dieses Artikels errors: oops: Hoppla! diff --git a/translations/de-DE/data/variables/action_code_examples.yml b/translations/de-DE/data/variables/action_code_examples.yml new file mode 100644 index 000000000000..e7c5decbd2f5 --- /dev/null +++ b/translations/de-DE/data/variables/action_code_examples.yml @@ -0,0 +1,149 @@ +--- +- + title: Starter workflows + description: Workflow files for helping people get started with GitHub Actions + languages: TypeScript + href: actions/starter-workflows + tags: + - official + - workflows +- + title: Example services + description: Example workflows using service containers + languages: JavaScript + href: actions/example-services + tags: + - service containers +- + title: Declaratively setup GitHub Labels + description: GitHub Action to declaratively setup labels across repos + languages: JavaScript + href: lannonbr/issue-label-manager-action + tags: + - Issues (Lieferungen) + - labels +- + title: Declaratively sync GitHub labels + description: GitHub Action to sync GitHub labels in the declarative way + languages: 'Go, Dockerfile' + href: micnncim/action-label-syncer + tags: + - Issues (Lieferungen) + - labels +- + title: Add releases to GitHub + description: Publish Github releases in an action + languages: 'Dockerfile, Shell' + href: elgohr/Github-Release-Action + tags: + - veröffentlichungen + - publishing +- + title: Publish a docker image to Dockerhub + description: A Github Action used to build and publish Docker images + languages: 'Dockerfile, Shell' + href: elgohr/Publish-Docker-Github-Action + tags: + - docker + - publishing + - build +- + title: Create an issue using content from a file + description: A GitHub action to create an issue using content from a file + languages: 'JavaScript, Python' + href: peter-evans/create-issue-from-file + tags: + - Issues (Lieferungen) +- + title: Publish GitHub Releases with Assets + description: GitHub Action for creating GitHub Releases + languages: 'TypeScript, Shell, JavaScript' + href: softprops/action-gh-release + tags: + - veröffentlichungen + - publishing +- + title: GitHub Project Automation+ + description: Automate GitHub Project cards with any webhook event. + languages: JavaScript + href: alex-page/github-project-automation-plus + tags: + - projects + - automation + - Issues (Lieferungen) + - pull requests +- + title: Run GitHub Actions Locally with a web interface + description: Runs GitHub Actions workflows locally (local) + languages: 'JavaScript, HTML, Dockerfile, CSS' + href: phishy/wflow + tags: + - local-development + - devops + - docker +- + title: Run your GitHub Actions locally + description: Run GitHub Actions Locally in Terminal + languages: 'Go, Shell' + href: nektos/act + tags: + - local-development + - devops + - docker +- + title: Build and Publish Android debug APK + description: Build and release debug APK from your Android project + languages: 'Shell, Dockerfile' + href: ShaunLWM/action-release-debugapk + tags: + - android + - build +- + title: Generate sequential build numbers for GitHub Actions + description: GitHub action for generating sequential build numbers. + languages: JavaScript + href: einaregilsson/build-number + tags: + - build + - automation +- + title: GitHub actions to push back to repository + description: Push Git changes to GitHub repository without authentication difficulties + languages: 'JavaScript, Shell' + href: ad-m/github-push-action + tags: + - publishing +- + title: Generate release notes based on your events + description: Action to auto generate a release note based on your events + languages: 'Shell, Dockerfile' + href: Decathlon/release-notes-generator-action + tags: + - veröffentlichungen + - publishing +- + title: Create a GitHub wiki page based on the provided markdown file + description: Create a GitHub wiki page based on the provided markdown file + languages: 'Shell, Dockerfile' + href: Decathlon/wiki-page-creator-action + tags: + - wiki + - publishing +- + title: 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: + - projects + - Issues (Lieferungen) + - labels +- + title: Add Label to your Pull Requests based on the author team name + description: Github action to label your pull requests based on the author name + languages: 'TypeScript, JavaScript' + href: JulienKode/team-labeler-action + tags: + - Pull Request + - labels diff --git a/translations/de-DE/data/variables/contact.yml b/translations/de-DE/data/variables/contact.yml index eb63d6ca991b..6028e9f928aa 100644 --- a/translations/de-DE/data/variables/contact.yml +++ b/translations/de-DE/data/variables/contact.yml @@ -10,7 +10,7 @@ contact_dmca: >- {% if currentVersion == "free-pro-team@latest" %}[Copyright claims form](https://github.com/contact/dmca){% endif %} contact_privacy: >- {% if currentVersion == "free-pro-team@latest" %}[Privacy contact form](https://github.com/contact/privacy){% endif %} -contact_enterprise_sales: '[GitHub''s Vertriebsteam](https://enterprise.github.com/contact)' +contact_enterprise_sales: "[GitHub's Vertriebsteam](https://enterprise.github.com/contact)" contact_feedback_actions: '[Feedback-Formular für GitHub Actions](https://support.github.com/contact/feedback?contact[category]=actions)' #The team that provides Standard Support enterprise_support: 'GitHub Enterprise-Support' diff --git a/translations/de-DE/data/variables/release_candidate.yml b/translations/de-DE/data/variables/release_candidate.yml new file mode 100644 index 000000000000..ec65ef6f9445 --- /dev/null +++ b/translations/de-DE/data/variables/release_candidate.yml @@ -0,0 +1,2 @@ +--- +version: '' 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 250c06b3aa16..a6f61f21845a 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 @@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - potatoqualitee --- {% data variables.product.prodname_actions %} の支払いを管理する 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 new file mode 100644 index 000000000000..6412735291c6 --- /dev/null +++ b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md @@ -0,0 +1,318 @@ +--- +title: Building and testing Ruby +intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data variables.product.prodname_actions %} の支払いを管理する +{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 + +### はじめに + +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. + +### 必要な環境 + +We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. 詳しい情報については、以下を参照してください。 + +- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions) +- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) + +### Starting with the Ruby workflow template + +{% 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). + +手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。 + +{% raw %} +```yaml +name: Ruby + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: 2.6 + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Specifying the Ruby version + +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). + +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. + +The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 # Not needed with a .ruby-version file +- run: bundle install +- run: bundle exec rake +``` +{% 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. + +### Testing with multiple versions of 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. + +{% raw %} +```yaml +strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] +``` +{% 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." + +The full updated workflow with a matrix strategy could look like this: + +{% raw %} +```yaml +name: Ruby CI + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby ${{ matrix.ruby-version }} + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: ${{ matrix.ruby-version }} + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Installing dependencies with 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. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 +- run: bundle install +``` +{% endraw %} + +#### 依存関係のキャッシング + +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 +steps: +- uses: ruby/setup-ruby@v1 + with: + bundler-cache: true +``` +{% 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. + +**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)」を参照してください。 + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + ${{ runner.os }}-gems- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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: + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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. + +{% raw %} +```yaml +name: Matrix Testing + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + runs-on: ${{ matrix.os }}-latest + strategy: + fail-fast: false + matrix: + os: [ubuntu, macos] + ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head] + continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }} + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: ${{ matrix.ruby }} + - run: bundle install + - run: bundle exec rake +``` +{% 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. + +{% raw %} +```yaml +name: Linting + +on: [push] + +jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + - name: Rubocop + run: rubocop +``` +{% endraw %} + +### Publishing Gems + +You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. + +パッケージを公開するのに必要なアクセストークンやクレデンシャルは、リポジトリシークレットを使って保存できます。 The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. + +{% raw %} +```yaml + +name: Ruby Gem + +on: + # Manually publish + workflow_dispatch: + # Alternatively, publish whenever changes are merged to the default branch. + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + build: + name: Build + Publish + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby 2.6 + uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + + - name: Publish to GPR + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem + env: + GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}" + OWNER: ${{ github.repository_owner }} + + - name: Publish to RubyGems + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push *.gem + env: + GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" +``` +{% endraw %} + diff --git a/translations/ja-JP/content/actions/guides/index.md b/translations/ja-JP/content/actions/guides/index.md index 552ae4f2df75..8d4e47d0ee8a 100644 --- a/translations/ja-JP/content/actions/guides/index.md +++ b/translations/ja-JP/content/actions/guides/index.md @@ -31,6 +31,7 @@ versions: {% 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/ja-JP/content/actions/guides/publishing-nodejs-packages.md b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md index 7bde7bd386e3..612853d6efd7 100644 --- a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md @@ -8,6 +8,8 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - GitHub --- {% data variables.product.prodname_actions %} の支払いを管理する diff --git a/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 9bf8f04fcda0..9b9bf3610daa 100644 --- a/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ja-JP/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 variables.product.prodname_actions %} の支払いを管理する diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md index ef78632b6180..7b7d410a0ca5 100644 --- a/translations/ja-JP/content/actions/index.md +++ b/translations/ja-JP/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 - date: '2020-10-16' - href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ + title: Removing set-env and add-path commands on November 16 + date: '2020-11-09' + href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - 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: Ubuntu-latest workflows will use 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: 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: MacOS Big Sur Preview + date: '2020-10-29' + href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview - - 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 + title: Self-Hosted Runner Group Access Changes + date: '2020-10-16' + href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ 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 %}
-

その他のガイド

+

Code examples

+ +
+ +
-
- -
-

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 -
- -
+ {% render 'code-example-card' for actionsCodeExamples as example %}
- すべてのガイド表示 {% octicon "arrow-right" %} + + +
+
{% octicon "search" width="24" %}
+

Sorry, there is no result for

+

It looks like we don't have an example that fits your filter.
Try another filter or add your code example

+ Learn how to add a code example {% octicon "arrow-right" %} +
+{% endif %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/introduction-to-github-actions.md index 014130523808..942a486a05aa 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/ja-JP/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. ジョブの各ステップは同じランナーで実行され、そのジョブのアクションが互いにデータを共有できるようにします。 #### アクション @@ -50,7 +50,7 @@ _アクション_は、_ジョブ_を作成するために_ステップ_に結 #### ランナー -ランナーは、{% data variables.product.prodname_actions %} ランナーアプリケーションがインストールされているサーバーです。 {% data variables.product.prodname_dotcom %} がホストするランナーを使用することも、自分でランナーをホストすることもできます。 ランナーは、使用可能なジョブをリッスンし、一度に 1 つのジョブを実行し、進行状況、ログ、および結果を {% data variables.product.prodname_dotcom %} に返します。 {% data variables.product.prodname_dotcom %}ホストランナーでは、ワークフロー内の各ジョブは新しい仮想環境で実行されます。 +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 %} がホストするランナーを使用することも、自分でランナーをホストすることもできます。 ランナーは、使用可能なジョブをリッスンし、一度に 1 つのジョブを実行し、進行状況、ログ、および結果を {% 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 @@ YAML 構文を使用してワークフローファイルを作成する方法を #### ワークフローファイルの視覚化 -この図では、作成したワークフローファイルと、{% data variables.product.prodname_actions %} コンポーネントが階層にどのように整理されているかを確認できます。 各ステップでは、単一のアクションが実行されます。 ステップ 1 と 2 は、ビルド済みのコミュニティアクションを使用します。 ワークフローのビルド済みアクションの詳細については、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-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)」を参照してください。 ![ワークフローの概要](/assets/images/help/images/overview-actions-event.png) diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md index e4794d650a4d..c7f511cd5206 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -10,7 +10,7 @@ versions: {% data variables.product.prodname_actions %} の支払いを管理する {% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 -{% 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/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md index e62b5c554209..a384b01cfdf9 100644 --- a/translations/ja-JP/content/actions/quickstart.md +++ b/translations/ja-JP/content/actions/quickstart.md @@ -73,3 +73,69 @@ versions: - 詳細なチュートリアルは、「[{% data variables.product.prodname_actions %}を学ぶ](/actions/learn-github-actions)」 - 特定の使用例とサンプルについては、「[ガイド](/actions/guides)」 - Super-Linter アクションの設定の詳細については、[github/super-linter](https://github.com/github/super-linter) + + 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 fa527efb1e17..1250ae66e5e9 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 @@ -390,6 +390,7 @@ The `issue_comment` event occurs for comments on both issues and pull requests. 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 @@ -416,6 +417,8 @@ jobs: ``` +{% endraw %} + #### `issues` diff --git a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md index 3885d4601c98..4f1bccce8284 100644 --- a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md @@ -31,7 +31,7 @@ versions: {% data variables.product.prodname_dotcom %}は、Microsoft AzureのStandard_DS2_v2仮想マシン上で{% data variables.product.prodname_actions %}ランナーアプリケーションがインストールされたLinux及びWindowsランナーをホストします。 {% data variables.product.prodname_dotcom %}ホストランナーアプリケーションは、Azure Pipelines Agentのフォークです。 インバウンドのICMPパケットはすべてのAzure仮想マシンでブロックされるので、pingやtracerouteコマンドは動作しないでしょう。 For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation. -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud. #### {% data variables.product.prodname_dotcom %}ホストランナーの管理権限 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 151efca57250..b7d6cd8a76fb 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 @@ -446,7 +446,7 @@ 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`** @@ -491,10 +491,10 @@ jobs: my_first_job: steps: - name: My first step - # 公開リポジトリのデフォルトブランチを使用する - uses: actions/heroku@master + # Uses the default branch of a public repository + 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 ``` @@ -659,7 +659,7 @@ steps: - `cmd` - 各エラーコードをチェックしてそれぞれに対応するスクリプトを書く以外、フェイルファースト動作を完全にオプトインする方法はないようです。 デフォルトでその動作を指定することはできないため、この動作はスクリプトに記述する必要があります。 - - `cmd.exe`は、実行した最後のプログラムのエラーレベルで終了し、runnerにそのエラーコードを返します。 この動作は、これ以前の`sh`および`pwsh`のデフォルト動作と内部的に一貫しており、`cmd.exe`のデフォルトなので、この動作には影響しません。 + - `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`のデフォルトなので、この動作には影響しません。 #### **`jobs..steps.with`** @@ -718,7 +718,7 @@ steps: entrypoint: /a/different/executable ``` -この`entrypoint`キーワードはDockerコンテナのアクションを使おうとしていますが、これは入力を定義しないJavaScriptのアクションにも使えます。 +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. #### **`jobs..steps.env`** diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index dc020454c6f3..4f3049902c0a 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -28,16 +28,7 @@ To configure authentication and user provisioning for {% data variables.product. {% 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. - - | Value in Azure AD | Value from {% data variables.product.prodname_ghe_managed %} - |:---------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Identifier (Entity ID) | `https://YOUR-GITHUB-AE-HOSTNAME - - - Reply URL - https://YOUR-GITHUB-AE-HOSTNAME/saml/consume` | - | Sign on URL | https://YOUR-GITHUB-AE-HOSTNAME/sso | +1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. 1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. diff --git a/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md index b12fa2c78a98..321824111fa6 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md @@ -38,6 +38,12 @@ After a user successfully authenticates on your IdP, the user's SAML session for {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} +The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | 詳細情報 | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs | + 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. | 値 | Other names | 説明 | サンプル | diff --git a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index d40cbf503bde..ab43453330dc 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -62,7 +62,15 @@ You must have administrative access on your IdP to configure the application for {% 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. [**Save**] をクリックします。 ![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. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. + + The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | 詳細情報 | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs | + + The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}. | 値 | Other names | 説明 | サンプル | |:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- | diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md b/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md index 4d46723d94c5..dc84d5467934 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md @@ -11,7 +11,7 @@ versions: ### 外部 `collectd` サーバーを設置 -{% data variables.product.product_location %}に`collectd` の転送をまだ有効にしていない場合は、外部の `collectd` サーバを設置する必要があります。 `collectd` サーバは、`collectd` 5.x以上のバージョンを使わなければなりません。 +{% data variables.product.product_location %}に`collectd` の転送をまだ有効にしていない場合は、外部の `collectd` サーバを設置する必要があります。 Your `collectd` server must be running `collectd` version 5.x or higher. 1. `collectd` サーバにログインする 2. `collectd` を作成、または編集することで、ネットワークプラグインをロードし、適切な値をサーバとポートのディレクティブに追加する。 たいていのディストリビューションでは、これは `/etc/collectd/collectd.conf` にあります。 diff --git a/translations/ja-JP/content/admin/packages/configuring-third-party-storage-for-packages.md b/translations/ja-JP/content/admin/packages/configuring-third-party-storage-for-packages.md index 55dae8e0d48f..baa3a136f49e 100644 --- a/translations/ja-JP/content/admin/packages/configuring-third-party-storage-for-packages.md +++ b/translations/ja-JP/content/admin/packages/configuring-third-party-storage-for-packages.md @@ -21,7 +21,10 @@ versions: {% warning %} -**警告:** 今後使用するバケットを必ず設定してください。 {% data variables.product.prodname_registry %} の使用開始後にストレージを変更することはお勧めしません。 +**警告:** +- 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 %} の使用開始後にストレージを変更することはお勧めしません。 {% endwarning %} diff --git a/translations/ja-JP/content/admin/packages/index.md b/translations/ja-JP/content/admin/packages/index.md index fbb469e43c73..b3060eb8b17b 100644 --- a/translations/ja-JP/content/admin/packages/index.md +++ b/translations/ja-JP/content/admin/packages/index.md @@ -1,6 +1,5 @@ --- title: Enterprise 向けの GitHub Packages を管理する -shortTitle: GitHub Packages intro: 'Enterprise で {% data variables.product.prodname_registry %} を有効にして、{% data variables.product.prodname_registry %} 設定と許可されたパッケージタイプを管理できます。' redirect_from: - /enterprise/admin/packages 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 15c19e772b5d..e88fe761da7b 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,17 +36,23 @@ versions: #### 部分的なコミットの作成方法 -1つのファイルに複数の変更があり、*一部*だけをコミットに含めたい場合は、部分的なコミットを作成できます。 追加変更やコミットできるように、他の変更はそのまま残ります。 これにより、改行の変更をコードや構文の変更から区別するなど、個別で有意義なコミットの作成が可能になります。 +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. 追加変更やコミットできるように、他の変更はそのまま残ります。 これにより、改行の変更をコードや構文の変更から区別するなど、個別で有意義なコミットの作成が可能になります。 -ファイルのdiffを確認するとき、コミットに含まれる行は青色で強調表示されます。 変更を除外するには、青色が消えるように変更された行をクリックします。 +{% note %} + +**Note:** Split diff displays are currently in beta and subject to change. + +{% endnote %} -![ファイルで選択解除された行](/assets/images/help/desktop/partial-commit.png) +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) -#### 変更の廃棄 +### 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. -1つのファイルや複数のファイルのコミットされていない全ての変更の廃棄、または最新コミット以降の全てのファイルの全ての変更の廃棄ができます。 +Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied. -{% mac %} +#### Discarding changes in one or more files {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -54,30 +60,25 @@ versions: {% data reusables.desktop.confirm-discard-files %} ![確定ダイアログ内の [Discard Changes] ボタン](/assets/images/help/desktop/discard-changes-confirm-mac.png) -{% tip %} +#### Discarding changes in one or more lines +You can discard one or more changed lines that are uncommitted. -**ヒント：**廃棄した変更は、Trash内の日付付きファイルに保存され、Trashが空になるまでは復元できます。 - -{% endtip %} +{% note %} -{% endmac %} +**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. -{% windows %} +{% endnote %} -{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %} - ![コンテキストメニュー内の [Discard Changes] オプション](/assets/images/help/desktop/discard-changes-win.png) -{% data reusables.desktop.confirm-discard-files %} - ![確定ダイアログ内の [Discard Changes] ボタン](/assets/images/help/desktop/discard-changes-confirm-win.png) +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**. -{% tip %} + ![Discard single line in the confirmation dialog](/assets/images/help/desktop/discard-single-line.png) -**ヒント：**廃棄した変更は、Recycle Bin内のファイルに保存され、空になるまでは復元できます。 +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**. -{% endtip %} + ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) -{% endwindows %} -### 3. コミットメッセージの入力と変更のプッシュ +### 4. コミットメッセージの入力と変更のプッシュ コミットに含めたい変更を決めたら、コミットメッセージを入力して変更をプッシュします。 コミットで共同作業した場合、コミットに 1 人以上の作者を追加できます。 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 1fd6c308d6b7..fde1e38f58e4 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 @@ -351,7 +351,7 @@ Checks API を使用すると、ステータス、画像、要約、アノテー ### ステップ 2.1. Ruby ファイルを追加する -RuboCop がチェックするため、特定のファイルまたはディレクトリ全体を渡すことができます。 このクイックスタートでは、ディレクトリ全体で RuboCop を実行します。 RuboCop がチェックするのは Ruby のコードのみなので、エラーが含まれる Ruby ファイルをリポジトリ内に最低 1 つ置くとよいでしょう。 以下に示すサンプルのファイルには、いくつかのエラーが含まれています。 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 ファイルをリポジトリ内に最低 1 つ置くとよいでしょう。 以下に示すサンプルのファイルには、いくつかのエラーが含まれています。 このサンプルの Ruby ファイルを、アプリケーションがインストールされているリポジトリに追加します (`myfile.rb` などのように、ファイル名には `.rb` の拡張子を必ず付けてください)。 ```ruby # The Octocat class tells you about different breeds of Octocat @@ -375,15 +375,15 @@ m.display ### ステップ 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 はコマンドラインユーティリティとして使用できます。 これはつまり、RuboCop がファイルを解析するためには、GitHub App が CI サーバー上のリポジトリのローカルコピーをクローンする必要があるということです。 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. アプリケーションの権限を更新するには、以下の手順に従います。 +リポジトリをクローンするには、アプリケーションに「リポジトリコンテンツ」の読み取り権限が必要です。 このクイックスタートでは、後ほどコンテンツを GitHub にプッシュする必要がありますが、そのためには書き込み権限が必要です。 Go ahead and set your app's "Repository contents" permission to **Read & write** now so you don't need to update it again later. アプリケーションの権限を更新するには、以下の手順に従います。 1. [アプリケーションの設定ページ](https://github.com/settings/apps)からアプリケーションを選択肢、サイドバーの [**Permissions & Webhooks**] をクリックします。 1. In the "Permissions" section, find "Repository contents", and select **Read & write** in the "Access" dropdown next to it. diff --git a/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md b/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md index e25d374ee18c..31607e2e14bb 100644 --- a/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md @@ -34,8 +34,6 @@ Different server-to-server request rate limits apply to {% data variables.produc ### User-to-server requests -{% data reusables.apps.deprecating_password_auth %} - {% 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. {% if currentVersion == "free-pro-team@latest" %} @@ -52,7 +50,7 @@ User-to-server requests are rate limited at 5,000 requests per hour and per auth #### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits -When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. +When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. {% endif %} diff --git a/translations/ja-JP/content/developers/github-marketplace/security-review-process-for-submitted-apps.md b/translations/ja-JP/content/developers/github-marketplace/security-review-process-for-submitted-apps.md index 40f7032bae7d..d2a44a343072 100644 --- a/translations/ja-JP/content/developers/github-marketplace/security-review-process-for-submitted-apps.md +++ b/translations/ja-JP/content/developers/github-marketplace/security-review-process-for-submitted-apps.md @@ -27,67 +27,67 @@ OAuth Appよりは、GitHub Appをサブミットすることをおすすめし - アプリケーションは、SaaSサービスを管理するためのメールやデータベースサービスのようなサービスアカウントを共有するべきではありません。 - アプリケーションで使用されるすべてのサービスは、固有のログインとパスワードクレデンシャルを持たなければなりません。 - プロダクションのホスティングインフラストラクチャへの管理権限でのアクセスは、管理業務を持つエンジニアや従業員にのみ与えられるべきです。 -- Apps cannot use personal access tokens to authenticate and must authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or [GitHub App](/apps/about-apps/#about-github-apps): +- アプリケーションは、認証に個人アクセストークンを使うことはできず、[OAuth App](/apps/about-apps/#about-oauth-apps)あるいは[GitHub App](/apps/about-apps/#about-github-apps)として認証されなければなりません。 - OAuth Appsは、[OAuthトークン](/apps/building-oauth-apps/authorizing-oauth-apps/)を使って認証を受けなければなりません。 - - GitHub Apps must authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + - GitHub Appは、[JSON Webトークン (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)、[OAuthトークン](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)、[インストールアクセストークン](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)のいずれかで認証を受けなければなりません。 -#### Data protection +#### データの保護 -- Apps must encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. -- Apps must store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). -- Apps must delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. -- Apps cannot require the user to provide their GitHub password. -- Apps should encrypt tokens, client IDs, and client secrets. +- アプリケーションは、パブリックなインターネット上で転送されるデータを、有効なTLS証明書を用いたHTTPSもしくはSSH for Gitで暗号化しなければなりません。 +- アプリケーションは、クライアントIDとクライアントシークレットキーをセキュアに保存しなければなりません。 それらは[環境変数](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables)に保存することをおすすめします。 +- アプリケーションは、ユーザからの要求を受けてから30日以内、あるいはユーザのGitHubとの法的な関係が終了してから30日以内に、すべてのGitHubユーザデータを削除しなければなりません。 +- アプリケーションは、ユーザにGitHubパスワードの提供を求めてはなりません。 +- アプリケーションは、トークン、クライアントID、クライアントシークレットを暗号化すべきです。 -#### Logging and monitoring +#### ロギング及びモニタリング -- Apps must have logging and monitoring capabilities. App logs must be retained for at least 30 days and archived for at least one year. A security log should include: - - Authentication and authorization events - - Service configuration changes - - Object reads and writes - - All user and group permission changes - - Elevation of role to admin - - Consistent timestamping for each event - - Source users, IP addresses, and/or hostnames for all logged actions +- アプリケーションは、ロギング及びモニタリングの機能を持たなければなりません。 アプリケーションのログは最低でも30日間保存され、最低でも1年間アーカイブされていなければなりません。 セキュリティログは以下を含まなければなりません。 + - 認証及び認可イベント + - サービス設定の変更 + - オブジェクトの読み書き + - すべてのユーザ及びグループの権限変更 + - ロールの管理者への昇格 + - 各イベントに対する一貫したタイムスタンプ + - 記録されたすべてのアクションのソースユーザ、IPアドレス及びホスト名 -#### Incident response workflow +#### インシデントレスポンスのワークフロー -- To partner with GitHub, you are required to have an [incident response plan](#incident-response-plan) in place before submitting your {% data variables.product.prodname_marketplace %} app listing. -- We recommend having a security and operations incident response team in your company rather than using a third-party vendor. -- You should have the capability to notify GitHub within 24 hours of a confirmed incident. -- You should familiarize yourself with sections 3.7.5 - 3.7.5.6 of the [{% data variables.product.prodname_marketplace %} Developer Agreement](/github/site-policy/github-marketplace-developer-agreement#3-restrictions-and-responsibilities), which include additional details on incident response workflow requirements. +- GitHubと連携するには、{% data variables.product.prodname_marketplace %}アプリケーションのリストをサブミットする前に、[インシデントレスポンスプラン](#incident-response-plan)を用意しておかなければなりません。 +- サードパーティのベンダを利用するよりは、自社内にセキュリティ及び運用インシデントレスポンスチームを持つことをおすすめします。 +- インシデントの確認後24時間以内にGitHubに通知する機能を持っていなければなりません。 +- インシデントレスポンスワークフローの要件に関する追加の詳細を含む、[{% data variables.product.prodname_marketplace %}開発者契約](/github/site-policy/github-marketplace-developer-agreement#3-restrictions-and-responsibilities)のセクション3.7.5 - 3.7.5.6に馴染んでおかなければなりません。 -#### Vulnerability management and patching workflow +#### 脆弱性管理とパッチ適用ワークフロー -- You should conduct regular vulnerability scans of production infrastructure. -- You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. -- You should familiarize yourself with section 3.7.3 of the [{% data variables.product.prodname_marketplace %} Developer Agreement](/github/site-policy/github-marketplace-developer-agreement#3-restrictions-and-responsibilities), which includes additional details on vulnerability management and patching workflows requirements. +- プロダクションインフラストラクチャーの定期的な脆弱性スキャンを行わなければなりません。 +- 脆弱性スキャンの結果をトリアージし、脆弱性の修正までの期間を定義して同意しなければなりません。 +- 脆弱性管理とパッチ適用ワークフローの要件に関する追加の詳細を含む、[{% data variables.product.prodname_marketplace %}開発者契約](/github/site-policy/github-marketplace-developer-agreement#3-restrictions-and-responsibilities)のセクション3.7.3に馴染んでおかなければなりません。 -### Security program documentation +### セキュリティプログラムのドキュメンテーション -During the Marketplace security review, you will be asked to submit your incident response plan and vulnerability management workflow. Each document must include a company-branded statement signed by management with a date stamp. +Marketplaceのセキュリティレビューの間に、インシデントレスポンスプランと脆弱性管理のワークフローの提出を求められます。 それぞれのドキュメントには、日付スタンプ付きの経営陣が署名した会社ブランドでの声明が含まれていなければなりません。 -#### Incident response plan -Your incident response plan documentation must include the current process that your company follows, who is accountable, and the person to contact or expect contact from if an incident occurs. The "[NIST Computer Security Incident Handling Guide](http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf)" is a great example of a document that covers incident response in general. Section 2.3 "Incident Response Policy, Plan, and Procedure Creation" specifically covers the policy. Another great example is the "[SANS Data Breach Response Policy](https://www.sans.org/security-resources/policies/general/pdf/data-breach-response)." +#### インシデントレスポンスプラン +インシデントレスポンスプランのドキュメンテーションには、会社が従う現在のプロセス、責任者、連絡先の人物もしくはインシデント発生時に想定される連絡先の人物が含まれていなければなりません。 「[NIST Computer Security Incident Handling Guide](http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf)」は、インシデントレスポンスを全般的に取り上げたドキュメントの素晴らしい例です。 セクション2.3の"Incident Response Policy, Plan, and Procedure Creation"は、特にこのポリシーを取り上げています。 もう1つの素晴らしい例としては「[SANS Data Breach Response Policy](https://www.sans.org/security-resources/policies/general/pdf/data-breach-response)」があります。 -#### Vulnerability management workflow -Your vulnerability management workflow documentation must include the current process that your company follows for vulnerability management and the patching process used. If you don't have a full vulnerability management program, it might help to start by creating a patching process. For guidance in creating a patch management policy, read the article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." +#### 脆弱性管理のワークフロー +脆弱性管理のワークフロードキュメンテーションには、使用されている脆弱性管理及びパッチ適用プロセスについて会社が従う現在のプロセスが含まれていなければなりません。 完全な脆弱性管理のプログラムがないなら、パッチ適用のプロセスの作成から始めると役立つでしょう。 パッチ管理ポリシーの作成のガイダンスとしては、「[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)」を読んでください。 {% note %} -**Note:** The incident response and vulnerability management workflow documents aren't expected to be massive formal policy or program documents. A page or two about what you do is more valuable than a lengthy policy template. +**ノート:** インシデントレスポンス及び脆弱性管理ワークフローのドキュメントは、大規模な正式のポリシーあるいはプログラムドキュメントだとは想定されていません。 やることを書いた1〜2ページのドキュメントには、長いポリシーテンプレートよりも価値があります。 {% endnote %} -#### GitHub Marketplace security program questionnaire +#### GitHub Marketplaceセキュリティプログラムアンケート -During the app submission process, our {% data variables.product.prodname_marketplace %} onboarding team will also send you a questionnaire requesting information about your security practices. This document will serve as a written record attesting: +アプリケーションのサブミットの過程で、弊社の{% data variables.product.prodname_marketplace %}オンボーディングチームからセキュリティプラクティスに関する情報を求めるアンケートが送られてきます。 このドキュメントは、以下を証明する書面による記録となります。 -- The authentication method and scopes required by your app. -- That you're not requesting more scopes or {% data variables.product.product_name %} access than is needed for the app to perform its intended functionality, taking OAuth limitations and use of {% data variables.product.prodname_github_app %}s into account. -- The use of any third-party services or infrastructure, such as SaaS, PaaS, or IaaS. -- An incident response procedure exists. -- Your app's method of key/token handling. -- That a responsible disclosure policy and process in place or plans to implement one within six months. -- Your vulnerability management workflow or program. -- That you have logging and monitoring capabilities. You must also provide evidence that any relevant app logs are retained for at least 30 days and archived for at least one year. +- アプリケーションが必要とする認証方式とスコープ。 +- OAuthの制限と{% data variables.product.prodname_github_app %}の利用を考慮した上で、アプリケーションが意図された機能を実行するのに必要となる以上のスコープや{% data variables.product.product_name %}のアクセスを要求していないこと。 +- SaaS、PaaS、IaaSといったサードパーティのサービスあるいはインフラストラクチャの利用。 +- インシデントレスポンスの手順が存在すること。 +- アプリケーションによるキー／トークンの処理方法。 +- 責任ある開示方針及び手続きがあること、もしくは6ヶ月以内に実施されること。 +- 脆弱性管理のワークフローもしくはプログラム。 +- ロギング及びモニタリングの機能があること。 関連するアプリケーションのログが少なくとも30日間保持され、少なくとも1年間アーカイブされるという証拠も提供しなければなりません。 diff --git a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md index e468593f58f7..fc184ca895df 100644 --- a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md +++ b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md @@ -1,6 +1,6 @@ --- -title: Selling your app on GitHub Marketplace -intro: 'Learn about requirements and best practices for selling your app on {% data variables.product.prodname_marketplace %}.' +title: GitHub Marketplaceでのアプリケーションの販売 +intro: 'アプリケーションを{% data variables.product.prodname_marketplace %}販売するための要件とベストプラクティスについて学んでください。' mapTopic: true redirect_from: - /apps/marketplace/administering-listing-plans-and-user-accounts/ diff --git a/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 205978a5f65e..e135da2504bb 100644 --- a/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,6 +1,6 @@ --- -title: Setting pricing plans for your listing -intro: 'When [listing your app on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/), you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' +title: リストに対する価格プランの設定 +intro: '[アプリケーションを{% data variables.product.prodname_marketplace %}上でリストする](/marketplace/listing-on-github-marketplace/)際に、アプリケーションを無料のサービスとして提供するか、アプリケーションを販売するかを選択できます。 アプリケーションを販売することを計画するなら、様々な機能レベルに対して異なる価格プランを作成できます。' redirect_from: - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ @@ -19,64 +19,64 @@ versions: -### Creating pricing plans +### 価格プランの作成 -To learn about the types of pricing plans that {% data variables.product.prodname_marketplace %} offers, see "[{% data variables.product.prodname_marketplace %} Pricing Plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." You'll also find helpful billing guidelines in "[Selling your app](/marketplace/selling-your-app/)." +{% data variables.product.prodname_marketplace %}が提供する価格プランの種類について学ぶには、「[{% data variables.product.prodname_marketplace %}の価格プラン](/marketplace/selling-your-app/github-marketplace-pricing-plans/)」を参照してください。 有益な支払いのガイドラインが「[アプリケーションの販売](/marketplace/selling-your-app/)」にもあります。 -Pricing plans can be in the draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published listing will function the same way as draft listings until your app is approved and listed on {% data variables.product.prodname_marketplace %}. Draft listings allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish the pricing plan, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. +価格プランは、ドラフトまたは公開状態にできます。 {% data variables.product.prodname_marketplace %}のリストを承認のためにサブミットしていない場合、公開されたリストはアプリケーションが承認され、{% data variables.product.prodname_marketplace %}上でリストされるまではドラフトのリストと同様に機能します。 ドラフトのリストを利用すると、{% data variables.product.prodname_marketplace %}リストページで利用できるようにすることなく、新しい価格プランを作成して保存できます。 価格プランを公開すると、すぐに顧客が購入できるようになります。 最大で10の価格プランを公開できます。 -To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). If you haven't created a {% data variables.product.prodname_marketplace %} listing yet, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how. +{% data variables.product.prodname_marketplace %}リストの価格プランを作成するには、[{% data variables.product.prodname_marketplace %}リストページ](https://github.com/marketplace/manage)の左のサイドバーで**Plans and pricing（プラント価格）**をクリックしてください。 まだ{% data variables.product.prodname_marketplace %}リストを作成していないなら、「[ドラフトの{% data variables.product.prodname_marketplace %}リストの作成](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)」を読んで、作成方法を学んでください。 -When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan: +**New draft plan（新規ドラフトプラン）**をクリックすると、価格プランをカスタマイズできるフォームが表示されます。 価格プランを作成するには、以下のフィールドを設定しなければなりません。 -#### Plan name +#### Plan name（プラン名） -Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align to the plan's resources, the size of the company that will use the plan, or anything you'd like. +価格プランの名前は{% data variables.product.prodname_marketplace %}アプリケーションのランディングページに表示されます。 プランのリソース、プランを利用する企業の規模、あるいは好きなもの何にでもあわせて価格プランの名前をカスタマイズできます。 -#### Pricing models +#### Pricing models（価格モデル） -##### Free plans +##### Free plans（無料プラン） -{% data reusables.marketplace.free-apps-encouraged %} A free plan still requires you to handle [new purchase](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/) and [cancellation](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/) billing flows. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" for more details. +{% data reusables.marketplace.free-apps-encouraged %} 無料プランでも、[新規購入](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)や[キャンセル](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)の支払いフローを処理する必要があります。 詳細については「[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)」を参照してください。 -##### Flat-rate plans +##### Flat-rate plans（定額プラン） -Flat-rate pricing plans allow you to offer your service to customers for a flat-rate fee. {% data reusables.marketplace.marketplace-pricing-free-trials %} +定額プランを使うと、顧客に対して定額でサービスを提供できます。 {% data reusables.marketplace.marketplace-pricing-free-trials %} -You must set a price for both monthly and yearly subscriptions in U.S. Dollars for flat-rate plans. +定額料金では、米ドルで月額及び年額のサブスクリプションに対して 価格を設定しなければなりません。 -##### Per-unit plans +##### Per-unit plans（ユニット単位プラン） -Per-unit pricing allows you to offer your app in units. For example, a unit can be a person, seat, or user. You'll need to provide a name for the unit and set a price for both monthly and yearly subscriptions, in U.S. Dollars. +ユニット単位での価格を利用すると、ユニットごとにアプリケーションを提供できます。 たとえば、ユニットには人、シート、ユーザが使えます。 ユニットの名前を提供し、月額及び年額のサブスクリプションを米ドルで 設定しなければなりません。 -#### Available for +#### Available for（利用の対象） -{% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. +{% data variables.product.prodname_marketplace %}の価格プランは、**Personal and organization accounts（個人及びOrganizationのアカウント）**、**Personal accounts only（個人アカウントのみ）**、**Organization accounts only（Organizationアカウントのみ）**のいずれかに適用できます。 たとえば、価格プランがユニット単位であり、複数のシートを提供するなら、個人アカウントからOrganization内の人にシートを割り当てる方法はないので、**Organization accounts only（Organizationアカウントのみ）**が選択できるでしょう。 -#### Short description +#### Short description（短い説明） -Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. +価格プランの詳細に関する簡単な概要を書いてください。 この説明には、そのプランが意図している顧客の種類や、プランに含まれるリソースなどが含まれることがあります。 -#### Bullets +#### Bullets（箇条書き） -You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. +最大で4項目の箇条書きをして、価格プランに関する詳細を含めることができます。 この箇条書きでは、アプリケーションのユースケースを含めたり、プランに含まれるリソースや機能に関するさらなる詳細をリストしたりすることができます。 -### Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan +### {% data variables.product.prodname_marketplace %}リストの価格プランの変更 -If a pricing plan for your {% data variables.product.prodname_marketplace %} plan is no longer needed or if you need to adjust pricing details, you can remove it. +{% data variables.product.prodname_marketplace %}プランの価格プランが不要になった場合、あるいは価格の細部を調整する必要が生じた場合、その価格プランを削除できます。 ![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png) -Once you publish a pricing plan for an app already listed in the {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." +{% data variables.product.prodname_marketplace %}にリスト済みのアプリケーションの価格プランを公開すると、そのプランは変更できなくなります。 その代わりに、その価格プランを削除しなければなりません。 削除された価格プランを購入済みの顧客は、オプトアウトして新しい価格プランに移行するまでは、そのプランを使い続けます。 価格プランの詳細については、「[{% data variables.product.prodname_marketplace %}の価格プラン](/marketplace/selling-your-app/github-marketplace-pricing-plans/)」を参照してください。 -Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription. +価格プランを削除すると、ユーザはそのプランを使ってアプリケーションを購入することはできなくなります。 削除されたプランの既存ユーザは、プランのサブスクリプションをキャンセルするまではそのプランに留まり続けます。 {% note %} -**Note:** {% data variables.product.product_name %} can't remove users from a removed pricing plan. You can run a campaign to encourage users to upgrade or downgrade from the removed pricing plan onto a new pricing plan. +**ノート:** {% data variables.product.product_name %}は、削除された価格プランからユーザを削除することはできません。 削除された価格プランから新しい価格プランへ、アップグレードもしくはダウングレードするようユーザに促すキャンペーンを実行できます。 {% endnote %} -You can disable GitHub Marketplace free trials without retiring the pricing plan, but this prevents you from initiating future free trials for that plan. If you choose to disable free trials for a pricing plan, users already signed up can complete their free trial. +価格プランを取り下げることなくGitHub Marketplaceの無料トライアルを無効化することはできますが、そうすると将来的にそのプランの無料トライアルを開始できなくなります。 価格プランに対する無料トライアルを無効にすることにした場合、サインアップ済みのユーザは無料トライアルを最後まで利用できます。 -After retiring a pricing plan, you can create a new pricing plan with the same name as the removed pricing plan. For instance, if you have a "Pro" pricing plan but need to change the flat rate price, you can remove the "Pro" pricing plan and create a new "Pro" pricing plan with an updated price. Users will be able to purchase the new pricing plan immediately. +価格プランを終了した後には、削除した価格プランと同じ名前で新しい価格プランを作成できます。 たとえば、「Pro」価格プランがあるものの、定額料金を変更する必要がある場合、その「Pro」価格プランを削除し、更新された価格で新しい「Pro」価格プランを作成できます。 ユーザは、すぐに新しい価格プランで購入できるようになります。 diff --git a/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-review.md b/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-review.md index 98a838e1f912..3477db2ef586 100644 --- a/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-review.md +++ b/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-review.md @@ -1,6 +1,6 @@ --- -title: Submitting your listing for review -intro: 'You can submit your listing as a verified or unverified app for the {% data variables.product.prodname_dotcom %} community to use.' +title: レビューのためのリストのサブミット +intro: '{% data variables.product.prodname_dotcom %}コミュニティに利用してもらうための検証済みあるいは未検証のアプリケーションとして、リストをサブミットできます。' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review versions: @@ -9,14 +9,14 @@ versions: -Once you've completed your app listing, you'll see two buttons that allow you to submit an unverified and verified app. The Publish without Verification **Request** button will not be available if you have published any paid pricing plans. +アプリケーションのリストが完成すると、未検証あるいは検証済みのアプリケーションとしてサブミットするための2つのボタンが表示されます。 検証**リクエスト**なしでの公開ボタンは、有料の価格プランを公開していなければ使用できません。 -![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) +![未検証及び検証済みリクエストボタン](/assets/images/marketplace/marketplace-request-button.png) {% data reusables.marketplace.launch-with-free %} -Before you can submit a verified app, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your existing app. See [Verified apps](/marketplace/#verified-apps) for the steps required to submit your app. +検証済みのアプリケーションをサブミットする前に、既存のアプリケーションに{% data variables.product.prodname_marketplace %}の支払いフローとwebhookを統合する必要があります。 アプリケーションをサブミットするのに必要なステップについては[検証済みのアプリケーション](/marketplace/#verified-apps)を参照してください。 -If you've met the [requirements](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) for a verified {% data variables.product.prodname_marketplace %} listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing! +検証済みの{% data variables.product.prodname_marketplace %}リストの[要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)を満たし、{% data variables.product.prodname_marketplace %} APIを統合したなら、先へ進んでリストをサブミットしてください！ -After you submit your listing for review, the {% data variables.product.prodname_marketplace %} onboarding team will reach out to you with additional information. +リストをレビューのためにサブミットすると、{% data variables.product.prodname_marketplace %}のオンボーディングチームから追加情報と併せて連絡が来ます。 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 8fa8b0d0c98b..d798e1145d44 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 @@ -1,6 +1,6 @@ --- title: アプリをテストする -intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before the {% data variables.product.prodname_marketplace %} onboarding team approves your app, it must adequately handle the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows).' +intro: 'リストを{% data variables.product.prodname_marketplace %}にサブミットする前に、APIとwebhookを使ってアプリケーションをテストし、顧客に理想的な体験を提供できるようにすることをGitHubはおすすめします。 {% data variables.product.prodname_marketplace %}オンボーディングチームによる承認の前に、アプリケーションは[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)を十分に処理できなければなりません。' redirect_from: - /apps/marketplace/testing-apps-apis-and-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ @@ -11,34 +11,34 @@ versions: -### Testing apps +### アプリケーションのテスト -You can use a [draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) to simulate each of the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows). A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. +[ドラフトの{% data variables.product.prodname_marketplace %}リスト](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)を使って、各[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)をシミュレートできます。 リストがドラフト状態にあるということは、まだそれが承認のためにサブミットされていないということです。 ドラフトの{% data variables.product.prodname_marketplace %}リストを使って行った購入は、実際の取引には_ならず_、GitHubはクレジットカードへの課金をしません。 -#### Using a development app with a draft listing to test changes +#### 変更のテストのために開発アプリケーションをドラフトリストと使用する -A {% data variables.product.prodname_marketplace %} listing can only be associated with a single app registration, and each app can only access its own {% data variables.product.prodname_marketplace %} listing. For these reasons, we recommend configuring a separate development app, with the same configuration as your production app, and creating a _draft_ {% data variables.product.prodname_marketplace %} listing that you can use for testing. The draft {% data variables.product.prodname_marketplace %} listing allows you to test changes without affecting the active users of your production app. You will never have to submit your development {% data variables.product.prodname_marketplace %} listing, since you will only use it for testing. +{% data variables.product.prodname_marketplace %}リストは、1つのアプリケーションの登録とのみ関連づけることができ、それぞれのアプリケーションは自身の{% data variables.product.prodname_marketplace %}リストにのみアクセスできます。 そのため、プロダクションのアプリケーションと同じ設定で別個の開発アプリケーションを設定し、テストに使用できる_ドラフト_の{% data variables.product.prodname_marketplace %}リストを作成することをおすすめします。 ドラフトの{% data variables.product.prodname_marketplace %}リストを使えば、プロダクションのアプリケーションのアクティブなユーザに影響することなく変更をテストできます。 開発の{% data variables.product.prodname_marketplace %}リストはテストにのみ使われるので、サブミットする必要はありません。 -Because you can only create draft {% data variables.product.prodname_marketplace %} listings for public apps, you must make your development app public. Public apps are not discoverable outside of published {% data variables.product.prodname_marketplace %} listings as long as you don't share the app's URL. A Marketplace listing in the draft state is only visible to the app's owner. +ドラフトの{% data variables.product.prodname_marketplace %}リストは公開アプリケーションに対してのみ作成できるので、開発アプリケーションは公開しなければなりません。 公開アプリケーションは、アプリケーションのURLを共有しないかぎり、公開された{% data variables.product.prodname_marketplace %}リスト外で見つかることはありません。 ドラフト状態のMarketplaceリストは、アプリケーションの所有者にしか見えません。 -Once you have a development app with a draft listing, you can use it to test changes you make to your app while integrating with the {% data variables.product.prodname_marketplace %} API and webhooks. +ドラフトリストと共に開発アプリケーションができたら、{% data variables.product.prodname_marketplace %} APIやwebhookと統合しながらそれを使ってアプリケーションの変更をテストできます。 {% warning %} -Do not make test purchases with an app that is live in {% data variables.product.prodname_marketplace %}. +{% data variables.product.prodname_marketplace %}で公開されているアプリケーションでは、購入のテストを行わないでください。 {% endwarning %} -#### Simulating Marketplace purchase events +#### Marketplaceの購入イベントのシミュレーション -Your testing scenarios may require setting up listing plans that offer free trials and switching between free and paid subscriptions. Because downgrades and cancellations don't take effect until the next billing cycle, GitHub provides a developer-only feature to "Apply Pending Change" to force `changed` and `cancelled` plan actions to take effect immediately. You can access **Apply Pending Change** for apps with _draft_ Marketplace listings in https://github.com/settings/billing#pending-cycle: +テストのシナリオでは、無料トライアルを提供するリストプランをセットアップし、無料と有料のサブスクリプション間の切り替えが必要になるかもしれません。 ダウングレードやキャンセルは、次回の支払いサイクルまでは有効にならないので、GitHubは開発者のみの機能として、`changed`及び`cancelled`のプランアクションを強制的にすぐに有効にする「保留中の変更の適用」機能を提供しています。 _ドラフト_Marketplaceリストのアプリケーションのための**保留中の変更の適用**には、https://github.com/settings/billing#pending-cycleでアクセスできます。 -![Apply pending change](/assets/images/github-apps/github-apps-apply-pending-changes.png) +![保留中の変更の適用](/assets/images/github-apps/github-apps-apply-pending-changes.png) -### Testing APIs +### APIのテスト -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). +ほとんどの{% data variables.product.prodname_marketplace %} APIエンドポイントに対しては、テストに利用できるハードコーディングされた偽のデータを返すスタブのAPIエンドポイントも提供されています。 スタブのデータを受信するには、ルートに`/stubbed`を含むスタブURL（たとえば`/user/marketplace_purchases/stubbed`）を指定してください。 スタブデータのアプローチをサポートしているエンドポイントのリストは、[{% data variables.product.prodname_marketplace %}エンドポイント](/v3/apps/marketplace/#github-marketplace)を参照してください。 -### Testing webhooks +### webhookのテスト -GitHub provides tools for testing your deployed payloads. For more information, see "[Testing webhooks](/webhooks/testing/)." +GitHubは、デプロイされたペイロードをテストするためのツールを提供しています。 詳しい情報については「[webhookのテスト](/webhooks/testing/)」を参照してください。 diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md index 79b8ccfe4321..823126cfe4b3 100644 --- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md @@ -1,10 +1,10 @@ --- -title: Using the GitHub Marketplace API in your app -intro: 'Learn how to integrate the {% data variables.product.prodname_marketplace %} API and webhook events into your app for the {% data variables.product.prodname_marketplace %} .' +title: アプリケーション内でのGitHub marketplace APIの使用 +intro: '{% data variables.product.prodname_marketplace %}用に、アプリケーションに{% data variables.product.prodname_marketplace %} APIとwebhookイベントを統合する方法を学んでください。' mapTopic: true redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/ + - /apps/marketplace/setting-up-github-marketplace-webhooks/ - /marketplace/integrating-with-the-github-marketplace-api versions: free-pro-team: '*' diff --git a/translations/ja-JP/content/developers/github-marketplace/viewing-metrics-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/viewing-metrics-for-your-listing.md index f5c01d6a33de..597033d417f9 100644 --- a/translations/ja-JP/content/developers/github-marketplace/viewing-metrics-for-your-listing.md +++ b/translations/ja-JP/content/developers/github-marketplace/viewing-metrics-for-your-listing.md @@ -1,6 +1,6 @@ --- -title: Viewing metrics for your listing -intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.' +title: リストのメトリクスの参照 +intro: '{% data variables.product.prodname_marketplace %} インサイトのページは、{% data variables.product.prodname_github_app %}のメトリクスを表示します。 このメトリクスを使って{% data variables.product.prodname_github_app %}のパフォーマンスを追跡し、価格、プラン、無料トライアル、マーケティングキャンペーンの効果の可視化の方法に関する判断を、より多くの情報に基づいて行えます。' redirect_from: - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing/ - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing/ @@ -12,7 +12,7 @@ versions: -You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed. +過去の日（24時間）、週、月、あるいは{% data variables.product.prodname_github_app %}がリストされた期間全体に対するメトリクスを見ることができます。 {% note %} diff --git a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md index fecb60456cd4..28b333458057 100644 --- a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md +++ b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md @@ -82,6 +82,32 @@ See [our guide on Git automation with tokens][git-automation]. 7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. 8. Click **Add key**. +##### Using multiple repositories on one server + +If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. + +In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. 例: + +```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 %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias. +* `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias. +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias. + +You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. 例: + +```bash +$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git +``` + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/ja-JP/content/developers/overview/secret-scanning.md b/translations/ja-JP/content/developers/overview/secret-scanning.md index b55c982bfcac..bf0a60000a02 100644 --- a/translations/ja-JP/content/developers/overview/secret-scanning.md +++ b/translations/ja-JP/content/developers/overview/secret-scanning.md @@ -79,7 +79,7 @@ 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. +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. * **Token**: The value of the secret match. * **Type**: The unique name you provided to identify your regular expression. diff --git a/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md index d30c497346f2..1a3b1fb164a4 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md @@ -1,5 +1,5 @@ --- -title: Testing webhooks +title: webhookのテスト intro: 'Review your webhook deliveries on {% data variables.product.prodname_dotcom %}, including the HTTP Request and payload as well as the response.' redirect_from: - /webhooks/testing diff --git a/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md b/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md index 18649a6964e4..95f5032fb513 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md @@ -1,6 +1,7 @@ --- title: シークレットスキャンニングについて intro: '{% data variables.product.product_name %} はリポジトリをスキャンして既知のシークレットのタイプを探し、誤ってコミットされたシークレットの不正使用を防止します。' +product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /github/administering-a-repository/about-token-scanning - /articles/about-token-scanning diff --git a/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md b/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md index 025506ca496a..5ea11e6225d3 100644 --- a/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md +++ b/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md @@ -1,6 +1,7 @@ --- title: プライベートリポジトリのシークレットスキャンの設定 intro: '{% data variables.product.product_name %} のプライベートリポジトリでのシークレットのスキャン方法を設定できます。' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'プライベートリポジトリの管理者権限を持つユーザは、リポジトリの {% data variables.product.prodname_secret_scanning %} を有効にできます。' versions: free-pro-team: '*' diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/ja-JP/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index 036edc765f3b..4e268a239443 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -1,6 +1,7 @@ --- title: シークレットスキャンからのアラートを管理する intro: リポジトリにチェックインしたシークレットのアラートを表示したりクローズしたりすることができます。 +product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' --- diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index 0c10572a1aea..5fab151dec97 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -31,7 +31,7 @@ versions: ### {% data variables.product.prodname_desktop %} で co-authored コミットを作成する -{% data variables.product.prodname_desktop %} で、共作者を持つコミットを作成できます。 詳細は「[コミットメッセージの入力と変更のプッシュ](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)」および [{% data variables.product.prodname_desktop %}](https://desktop.github.com) を参照してください。 +{% data variables.product.prodname_desktop %} で、共作者を持つコミットを作成できます。 詳細は「[コミットメッセージの入力と変更のプッシュ](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)」および [{% data variables.product.prodname_desktop %}](https://desktop.github.com) を参照してください。 ![コミットメッセージに共作者を追加](/assets/images/help/desktop/co-authors-demo-hq.gif) @@ -74,4 +74,4 @@ versions: - [リポジトリアクティビティの概要を表示する](/articles/viewing-a-summary-of-repository-activity) - [プロジェクトのコントリビューターを表示する](/articles/viewing-a-projects-contributors) - [コミットメッセージの変更](/articles/changing-a-commit-message) -- {% data variables.product.prodname_desktop %} ドキュメンテーションの「[プロジェクトへの変更をコミットまたはレビューする](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)」 +- {% data variables.product.prodname_desktop %} ドキュメンテーションの「[プロジェクトへの変更をコミットまたはレビューする](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)」 diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md index 871388bfb37a..5814e4cdc19a 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- title: Using Codespaces in Visual Studio Code -intro: '{% data variables.product.product_name %} のアカウントに {% data variables.product.prodname_vs_codespaces %} 機能拡張を接続することにより、{% data variables.product.prodname_vscode %} で codespace を直接開発できます。' +intro: '{% data variables.product.product_name %} のアカウントに {% data variables.product.prodname_github_codespaces %} 機能拡張を接続することにより、{% data variables.product.prodname_vscode %} で codespace を直接開発できます。' 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: ### 必要な環境 -{% data variables.product.prodname_vscode %} の codespace で直接開発する前に、{% data variables.product.product_name %} アカウントに接続するように {% data variables.product.prodname_vs_codespaces %} の機能拡張を設定する必要があります。 +To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. -1. {% data variables.product.prodname_vs %} Marketplace を使用して、[{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline) 機能拡張をインストールします。 詳しい情報については、{% data variables.product.prodname_vscode %} ドキュメントの「[Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)」を参照してください。 -2. {% data variables.product.prodname_vscode %} の左サイドバーで、[Extensions] アイコンをクリックします。 ![{% data variables.product.prodname_vscode %} の [Extensions] アイコン](/assets/images/help/codespaces/click-extensions-icon-vscode.png) -3. {% data variables.product.prodname_vs_codespaces %} の下で、[Manage] アイコンをクリックしてから、[**Extension Settings**] をクリックします。 ![[Extension Settings] オプション](/assets/images/help/codespaces/select-extension-settings.png) -4. [Vsonline: Account Provider] ドロップダウンメニューを使用して、{% data variables.product.prodname_dotcom %} を選択します。 ![アカウントプロバイダを {% data variables.product.prodname_dotcom %} に設定する](/assets/images/help/codespaces/select-account-provider-vscode.png) +1. Use the + +{% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. 詳しい情報については、{% data variables.product.prodname_vscode %} ドキュメントの「[Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)」を参照してください。 {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -6. ヘッダで {% data variables.product.prodname_codespaces %} がまだ選択されていない場合は、[**{% data variables.product.prodname_codespaces %}**] をクリックします。 ![{% data variables.product.prodname_codespaces %} ヘッダ](/assets/images/help/codespaces/codespaces-header-vscode.png) -7. [**Sign in to view {% data variables.product.prodname_codespaces %}...**] をクリックします。 ![[Signing in to view {% data variables.product.prodname_codespaces %}]](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -8. {% data variables.product.prodname_vscode %} からの {% data variables.product.product_name %} のアカウントへのアクセスを承認するには、[**Allow**] をクリックします。 -9. 機能拡張を承認するには、{% data variables.product.product_name %} にサインインします。 +2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![{% data variables.product.prodname_codespaces %} ヘッダ](/assets/images/help/codespaces/codespaces-header-vscode.png) +3. [**Sign in to view {% data variables.product.prodname_codespaces %}...**] をクリックします。 ![[Signing in to view {% data variables.product.prodname_codespaces %}]](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) +4. {% data variables.product.prodname_vscode %} からの {% data variables.product.product_name %} のアカウントへのアクセスを承認するには、[**Allow**] をクリックします。 +5. 機能拡張を承認するには、{% data variables.product.product_name %} にサインインします。 ### Creating a codespace in {% data variables.product.prodname_vscode %} @@ -31,8 +30,8 @@ After you connect your {% data variables.product.product_name %} account to the {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) 3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop in. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) - +4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) +5. Click the instance type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) ### {% data variables.product.prodname_vscode %} で codespace を開く {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 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 ff27712b4928..fa6ce7cdf080 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 @@ -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: コードスキャンニングについて +intro: '{% data variables.product.prodname_code_scanning %} を使用して、{% 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 %} +### {% 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. +{% data variables.product.prodname_code_scanning %} を使用して、コード内の既存の問題の修正を検索し、トリアージして、優先順位を付けることができます。 また、{% data variables.product.prodname_code_scanning_capc %} は、開発者による新しい問題の発生も防ぎます。 スキャンを特定の日時にスケジュールしたり、プッシュなどの特定のイベントがリポジトリで発生したときにスキャンをトリガーしたりすることができます。 -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)." +{% 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)." -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 %} は {% data variables.product.prodname_actions %} を使用します。 詳細については、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。 -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)." +{% data variables.product.prodname_code_scanning %} を始めるには、「[{% data variables.product.prodname_code_scanning %} の有効化](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)」を参照してください。 -### About {% data variables.product.prodname_codeql %} +### {% 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. +デフォルトでは、{% data variables.product.prodname_code_scanning %} はセマンティックコード分析エンジンである {% data variables.product.prodname_codeql %} を使用します。 {% data variables.product.prodname_codeql %} はコードをデータとして扱い、コードの潜在的な脆弱性を従来の静的分析よりも高い精度で見つけることができます。 -{% 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 %} は {% data variables.product.prodname_codeql %} を動作させるクエリ言語です。 {% data variables.product.prodname_ql %} はオブジェクト指向ロジックプログラミング言語です。 {% data variables.product.company_short %}、言語の専門家、セキュリティ研究者が {% data variables.product.prodname_code_scanning %} に使用するクエリを作成します。クエリはオープンソースです。 コミュニティはクエリを維持および更新して、分析を改善し、誤検出を減らします。 詳しい情報については、GitHub Security Lab Web サイトの「[{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)」を参照してください。 -{% 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. +{% data variables.product.prodname_code_scanning %} の API エンドポイントについての詳細は、「[{% 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. +[`github/codeql`](https://github.com/github/codeql)リポジトリで {% data variables.product.prodname_code_scanning %} のクエリを表示して貢献できます。 詳しい情報については、 {% data variables.product.prodname_codeql %} ドキュメントの「[{% data variables.product.prodname_codeql %} クエリ](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### {% 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 %} は {% data variables.product.prodname_actions %} を使用し、{% data variables.product.prodname_code_scanning %} ワークフローの実行ごとに {% data variables.product.prodname_actions %} に数分かかります。 詳しい情報については、[{% 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 +### サードパーティのコードスキャンツールについて {% 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 +### 参考リンク {% 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 +- OASIS 委員会 の Web サイトの「[OASIS Static Analysis Results Interchange Format (SARIF) 」TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 68d69e005ae7..d99e3e65688d 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -94,7 +94,7 @@ If the `autobuild` command can't build your code, you can run the build steps yo By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command. -Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-an-alert)." +Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-the-alerts-for-a-repository)." ### {% data variables.product.prodname_codeql_runner %} command reference diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index d44cd2e445b5..855a318c4a14 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -1,7 +1,7 @@ --- 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.' +shortTitle: コードスキャンを有効化する +intro: 'プロジェクトのリポジトリで {% data variables.product.prodname_code_scanning %} を有効化できます。' 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.' redirect_from: @@ -23,24 +23,20 @@ You decide how you generate {% data variables.product.prodname_code_scanning %} ### Enabling {% data variables.product.prodname_code_scanning %} using actions -{% 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" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. 詳しい情報については、「[{% 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) +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. 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. - 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**. + 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。 +6. [**Start commit**] ドロップダウンを使用して、コミットメッセージを入力します。 ![コミットを開始する](/assets/images/help/repository/start-commit-commit-new-file.png) +7. デフォルトブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択します。 ![コミット先を選択する](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. [**Commit new file**] または [**Propose new file**] をクリックします。 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. @@ -62,7 +58,7 @@ After enabling {% data variables.product.prodname_code_scanning %} for your repo 1. Review the logging output from the actions in this workflow as they run. -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. 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-the-alerts-for-a-repository)." {% note %} @@ -106,12 +102,12 @@ There are other situations where there may be no analysis for the latest commit 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 %}. -### Next steps +### 次のステップ After enabling {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: - 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)." +- Set up notifications for completed runs. 詳しい情報については、「[通知を設定する](/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)." +- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。 diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index f496c07b7164..a2eb453614fc 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -1,7 +1,7 @@ --- title: Managing code scanning alerts for your repository shortTitle: アラートを管理する -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: 'From the security view, 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.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: @@ -30,9 +30,11 @@ If you enable {% data variables.product.prodname_code_scanning %} using {% data {% data variables.product.prodname_code_scanning %} がデータフローアラートを報告すると、{% data variables.product.prodname_dotcom %} はデータがコードを通してどのように移動するかを示します。 {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. -### アラートを表示する +### Viewing the alerts for a repository -Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} alerts on pull requests. However, you need write permission to view a summary of alerts for repository on the **Security** tab. By default, alerts are shown for the default branch. +Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. 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)." + +You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -45,7 +47,7 @@ Anyone with read permission for a repository can see {% data variables.product.p Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[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)." -If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing an alert](#viewing-an-alert)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. +If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index 9b373b7a2102..721b4060208d 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -3,7 +3,7 @@ title: Triaging code scanning alerts in pull requests shortTitle: Triaging alerts in pull requests intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.' 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: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -31,9 +31,9 @@ When you look at the **Files changed** tab for a pull request, you see annotatio ![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png) -Some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." +If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." -For more information about an alert, click **Show more details** on the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. +To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code. @@ -41,11 +41,11 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_ ### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request -Anyone with write permission for a repository can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on a pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. +Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. {% if currentVersion == "enterprise-server@2.22" %} -If you don't think that an alert needs to be fixed, you can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. +If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. {% data reusables.code-scanning.false-positive-fix-codeql %} @@ -63,4 +63,4 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler For more information about dismissing alerts, 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#dismissing-or-deleting-alerts)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index 17adbfc0670f..9cd2e1346493 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -66,7 +66,7 @@ For more information, see the workflow extract in "[Automatic build for a compil * Building using a distributed build system external to GitHub Actions, using a daemon process. * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. - .NET Core 2 をターゲットとする `dotnet build` または `msbuild` を使用する C# プロジェクトでは、コードをビルドするときに、ワークフローの `run` ステップで `/p:UseSharedCompilation=false` を指定する必要があります。 .NET Core 3.0 以降では、`UseSharedCompilation` フラグは必要ありません。 + For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. .NET Core 3.0 以降では、`UseSharedCompilation` フラグは必要ありません。 For example, the following configuration for C# will pass the flag during the first build step. diff --git a/translations/ja-JP/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md b/translations/ja-JP/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md index 08acb96f3711..49fb8f25fadc 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md +++ b/translations/ja-JP/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md @@ -21,5 +21,5 @@ versions: ベータ版で利用可能な機能のリストと各機能の簡単な説明を確認することができます。 各機能には、フィードバックを提供するリンクが含まれています。 -1. 任意のページの右上隅で、プロフィール画像をクリックし、続いて [**Feature preview（機能プレビュー）**] をクリックします。 ![[Feature preview] ボタン](/assets/images/help/settings/feature-preview-button.png) +{% data reusables.feature-preview.feature-preview-setting %} 2. 必要に応じて、機能の右側で、[**Enable**] または [**Disable**] をクリックします。 ![機能プレビューの [Enable] ボタン](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md index 9fd496df5475..32d29e2227cf 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md @@ -1,6 +1,7 @@ --- title: Organization のシークレットスキャンの管理 intro: 'Organization のどのリポジトリで {% data variables.product.product_name %} がシークレットをスキャンするかを制御することができます。' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'Organization のオーナーは、Organization のリポジトリに対する {% data variables.product.prodname_secret_scanning %} を管理できます。' versions: free-pro-team: '*' 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 5044d66a8942..4912c1f95cfa 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 @@ -43,74 +43,77 @@ Organization レベルの設定を管理することに加え、Organization の ### 各権限レベルが可能なリポジトリへのアクセス -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:| -| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | -| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | -| Issue のオープン | **X** | **X** | **X** | **X** | **X** | -| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | -| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | -| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | -| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | -| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | -| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** |{% endif %} -| 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** | -| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** | -| マイルストーンの適用 | | **X** | **X** | **X** | **X** | -| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | -| [プルリクエストのレビュー](/articles/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | -| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | -| [他者によるコメントの非表示](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [会話のロック](/articles/locking-conversations) | | | **X** | **X** | **X** | -| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | -| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/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" %} -| [プルリクエストをドラフトに変換する](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | -| プルリクエストに[提案された変更を適用する](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| [ステータスチェック](/articles/about-status-checks)の作成 | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** |{% endif %} -| リリースの作成と編集 | | | **X** | **X** | **X** | -| ドラフトリリースの表示 | | | **X** | **X** | **X** | -| リポジトリの説明の編集 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | -| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | -| プロジェクトボードの有効化 | | | | **X** | **X** | -| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | -| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | -| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | -| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [リポジトリでのインタラクション](/github/building-a-strong-community/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** |{% endif %} -| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | -| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** | -| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | -| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | -| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | -| リポジトリ設定の変更 | | | | | **X** | -| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | -| リポジトリのデフォルトブランチ編集 | | | | | **X** | -| Webhookおよびデプロイキーの管理 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| プライベートリポジトリの[依存関係グラフの有効化](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | -| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | -| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| 脆弱な依存関係についての[{% data variables.product.prodname_dependabot_alerts %}を受信する個人または Team の追加指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) | | | | | **X** | -| [プライベートリポジトリ用のデータ利用設定を管理する](/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" %}| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** |{% endif %} -| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** |{% endif %} -| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** | +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | +| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | +| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | +| Issue のオープン | **X** | **X** | **X** | **X** | **X** | +| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | +| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | +| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | +| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | +| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | +| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 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** | +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** | +| マイルストーンの適用 | | **X** | **X** | **X** | **X** | +| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | +| [プルリクエストのレビュー](/articles/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | +| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | +| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | +| [他者によるコメントの非表示](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [会話のロック](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | +| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/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" %} +| [プルリクエストをドラフトに変換する](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | +| プルリクエストに[提案された変更を適用する](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | +| [ステータスチェック](/articles/about-status-checks)の作成 | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** |{% endif %} +| リリースの作成と編集 | | | **X** | **X** | **X** | +| ドラフトリリースの表示 | | | **X** | **X** | **X** | +| リポジトリの説明の編集 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | +| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | +| プロジェクトボードの有効化 | | | | **X** | **X** | +| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | +| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | +| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | +| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [リポジトリでのインタラクション](/github/building-a-strong-community/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** |{% endif %} +| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | +| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** | +| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | +| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | +| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | +| リポジトリ設定の変更 | | | | | **X** | +| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | +| リポジトリのデフォルトブランチ編集 | | | | | **X** | +| Webhookおよびデプロイキーの管理 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| プライベートリポジトリの[依存関係グラフの有効化](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | +| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | +| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| 脆弱な依存関係についての[{% data variables.product.prodname_dependabot_alerts %}を受信する個人または Team の追加指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) | | | | | **X** | +| [プライベートリポジトリ用のデータ利用設定を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | +| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %} +| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** |{% endif %} +| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** | ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index 5d8cba741b58..671edbda8e93 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -3,6 +3,7 @@ title: Managing licenses for Visual Studio subscription with GitHub Enterprise intro: 'You can manage {% data variables.product.prodname_enterprise %} licensing for {% 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 diff --git a/translations/ja-JP/content/github/site-policy/github-acceptable-use-policies.md b/translations/ja-JP/content/github/site-policy/github-acceptable-use-policies.md index c1990d4350d1..244db106673b 100644 --- a/translations/ja-JP/content/github/site-policy/github-acceptable-use-policies.md +++ b/translations/ja-JP/content/github/site-policy/github-acceptable-use-policies.md @@ -37,6 +37,8 @@ versions: - 当社従業員、役員、代理店、その他ユーザを含む、あらゆる個人またはグループに対する嫌がらせ、罵倒、脅迫、または暴力の誘発、 +- post off-topic content, or interact with platform features, in a way that significantly or repeatedly disrupts the experience of other users; + - あらゆる自動化された過剰な大規模活動 (スパムや暗号通貨のマイニングなど) に当社サーバーを利用すること、自動化された手段により当社サーバーに不当な負荷を加えること、または当社サーバーを経由して、あらゆる未承諾広告や勧誘行為 (攻略法詐欺など) を中継すること、 - 当社サーバーを使用して、何らかのサービス、デバイス、データ、アカウントまたはネットワークを妨害するかあるいはこれを試みること、またはこれらに不正アクセスするかあるいはこれを試みること ([GitHub Bug Bounty program](https://bounty.github.com) により許可されている場合を除く)、 @@ -48,15 +50,17 @@ versions: ### 4. サービス利用の制限 当社が書面により明示的に許可する場合を除き、「サービス」のいずれか一部、「サービス」の使用、または「サービス」へのアクセスを複製、複写、コピー、販売、再販売、または活用してはなりません。 -### 5. スクレイピングおよび API 利用の制限 -スクレイピングとは、ボットやウェブクローラーなどの自動的な処理により、当社「サービス」からデータを抽出することを指します。 API を介した情報の収集は指していません。 Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. 本ウェブサイトをスクレイピングできるのは次を理由とする場合のみです。 +### 5. Information Usage Restrictions +You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise: + +- Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are [open access](https://en.wikipedia.org/wiki/Open_access). +- Archivists may use public information from the Service for archival purposes. -- 研究者は、公開された研究結果が自由にアクセスできる場合にのみ、非個人的なパブリック情報を「サービス」から研究目的でスクレイピングすることができます。 -- アーキビストは、データを保管する目的で「サービス」のパブリックデータをスクレイピングすることができます。 +Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler. Scraping does not refer to the collection of information through our API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. -(「[GitHub のプライバシーについての声明](/articles/github-privacy-statement)」の定義による) 「ユーザ個人情報」を、人事採用担当者、ヘッドハンター、求人掲示板などに販売する目的を含め、スパム目的で本「サービス」をスクレイピングすることはできません。 +You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling User Personal Information (as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement)), such as to recruiters, headhunters, and job boards. -スクレイピングにより収集したデータの利用はすべて、「 [GitHub のプライバシーについての声明](/articles/github-privacy-statement)」に従う必要があります。 +Your use of information from the Service must comply with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). ### 6. プライバシー 「ユーザ個人情報」の悪用は禁じられています diff --git a/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md b/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md index e7b54fc5b60e..573c1783dc1d 100644 --- a/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -このバージョンの発効日: 2020 年 11 月 1 日 +このバージョンの発効日: 2020 年 11 月 13 日 アカウントを作成すると利用できるようになる各種の機能と製品は、すべて本サービスの一部です。 このような機能と製品の多くは機能性が異なるため、その機能や製品に固有の利用規約が必要になる場合があります。 Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -89,7 +89,7 @@ In order to access GitHub Connect, Customer must have at least one (1) Account o ### 9. GitHub Advanced Security -GitHub Advanced Security enables you to identify security vulnerabilities through customizable and automated semantic code analysis. GitHub Advanced Security is licensed on a per User basis. If you are using GitHub Advanced Security as part of GitHub Enterprise Cloud, many features of GitHub Advanced Security, including automated code scanning of private repositories, also require the use of GitHub Actions. Billing for usage of GitHub Actions is usage-based and is subject to the [GitHub Actions terms](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages). +GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. If you are using GitHub Advanced Security as part of GitHub Enterprise Cloud, many features of GitHub Advanced Security, including automated code scanning of private repositories, also require the use of GitHub Actions. ### 10. Dependabot Preview @@ -108,4 +108,3 @@ Your use of Spectrum is governed by the GitHub [Terms of Service](/github/site-p #### b. GitHub Advisory Databaseのライセンス GitHub Advisory Databaseは、[Creative Commons Attribution 4.0ライセンス](https://creativecommons.org/licenses/by/4.0/)の下でライセンスされています。 帰属条件は、のGitHub Advisory Databaseまたは使用される個々のGitHub Advisory Databaseレコード（で始まる）にリンクすることで満たすことができます。 - diff --git a/translations/ja-JP/content/github/site-policy/github-community-guidelines.md b/translations/ja-JP/content/github/site-policy/github-community-guidelines.md index c77cb6aa4cf2..ae4195ac681e 100644 --- a/translations/ja-JP/content/github/site-policy/github-community-guidelines.md +++ b/translations/ja-JP/content/github/site-policy/github-community-guidelines.md @@ -11,7 +11,7 @@ GitHub では、何百万人もの開発者が何百万ものプロジェクト 世界中の GitHub ユーザたちの持つ視点、アイデア、経験は十人十色。数日前に初めて「Hello World」プロジェクトを作った人から、世界で最も有名なソフトウェア開発者まで、さまざまなユーザがいます。 私たちは、GitHub をコミュニティ内のさまざまな意見や視点に対応した快適な環境にし、人々が自由に自分を表現できるスペースになるよう取り組んでいます。 -We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. 当社がモデレートするコンテンツを積極的に探すことはありません。 GitHub でコラボレーションする最適な方法や、どんな行為やコンテンツが[利用規約](#legal-notices)に違反する恐れがあるのかを皆様に理解していただくために、ここではコミュニティ内では何が期待されるのかを説明いたします。 当社は不正行為の報告を調査し、利用規約に違反していると判断したサイトの公開コンテンツをモデレートする場合があります。 +We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). 当社は不正行為の報告を調査し、利用規約に違反していると判断したサイトの公開コンテンツをモデレートする場合があります。 ### 強いコミュニティを作る @@ -47,23 +47,25 @@ Of course, you can always contact us to {% data variables.contact.report_abuse % 私たちは、ユーザが自由に自己表現し、それが技術的な内容であろうがそうでなかろうが、お互いのアイデアについて意見を交換できるコミュニティを維持できるように取り組んでいます。 しかし、コミュニティのメンバーが怒鳴られたり、発言するのが怖いためにアイデアが出てこない場合、このようなディスカッションから実りある対話が生まれることは少ないでしょう。 このため、常に敬意を払い、礼儀正しく振る舞うべきで、相手が何者かであるかを根拠にして他人を攻撃することは控えるべきです。 当社は、一線を越えた次のような行為を許容しません。 -* **暴力の脅威** - 他人を脅したり、サイトを利用して現実世界の暴力やテロ行為を組織、促進、または扇動することはできません。 言葉を発する場合や画像を投稿する場合はもちろん、ソフトウェアを作成する場合でさえも、それが他人からどのように解釈される可能性があるかを慎重に考えてください。 あなたが冗談のつもりでも、そのように受け取られないかもしれません。 自分が投稿したコンテンツが脅しである、または暴力やテロを助長していると他の誰かが解釈する*かもしれない*と思われる場合は、 それをGitHubに投稿するのを止めましょう。 場合によっては、当社が身体的危害のリスクや公共の安全に対する脅威だと判断し、暴力の脅威として法執行機関に報告する場合があります。 +- #### Threats of violence You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. 言葉を発する場合や画像を投稿する場合はもちろん、ソフトウェアを作成する場合でさえも、それが他人からどのように解釈される可能性があるかを慎重に考えてください。 あなたが冗談のつもりでも、そのように受け取られないかもしれません。 自分が投稿したコンテンツが脅しである、または暴力やテロを助長していると他の誰かが解釈する*かもしれない*と思われる場合は、 それをGitHubに投稿するのを止めましょう。 場合によっては、当社が身体的危害のリスクや公共の安全に対する脅威だと判断し、暴力の脅威として法執行機関に報告する場合があります。 -* **差別的発言と差別** - 年齢、体の大きさ、障害、民族性、性自認、性表現、経験の度合い、国籍、容姿、人種、宗教、性同一性、性的指向などのトピックを持ち出すこと自体は禁止されていませんが、相手が何者かであるかを根拠にして個人またはグループを攻撃する発言を当社は許容しません。 攻撃的または侮辱的なアプローチでこうしたデリケートなトピックを扱った場合、他の人を不快に感じさせたり、場合によっては危険にさえ感じさせたりすることがあることを認識してください。 誤解が生まれる可能性を完全に排除することはできませんが、デリケートなトピックを議論するときは、常に敬意を払い、礼儀正しく振る舞うことがコミュニティメンバーに期待されます。 +- #### Hate speech and discrimination While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. 攻撃的または侮辱的なアプローチでこうしたデリケートなトピックを扱った場合、他の人を不快に感じさせたり、場合によっては危険にさえ感じさせたりすることがあることを認識してください。 誤解が生まれる可能性を完全に排除することはできませんが、デリケートなトピックを議論するときは、常に敬意を払い、礼儀正しく振る舞うことがコミュニティメンバーに期待されます。 -* **いじめと嫌がらせ** - 私たちは、いじめや嫌がらせを容認しません。 これは、特定の個人またはグループを標的とする常習的な煽りや脅迫のことです。 一般的に、迷惑な行動を続けた場合、いじめや嫌がらせになる恐れが高くなります。 +- #### Bullying and harassment We do not tolerate bullying or harassment. これは、特定の個人またはグループを標的とする常習的な煽りや脅迫のことです。 一般的に、迷惑な行動を続けた場合、いじめや嫌がらせになる恐れが高くなります。 -* **なりすまし** - 他人のアバターをコピーしたり、他人のメールアドレスを使ってコンテンツを投稿したり、類似するユーザ名を使用したりするなど、他人になりすまして自分の身元を誤解させようとしてはいけません。 なりすましは嫌がらせの一つです。 +- #### Disrupting the experience of other users Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on. Behaviors such as repeatedly posting off-topic comments, opening empty or meaningless issues or pull requests, or using any other platform feature in a way that continually disrupts the experience of other users are not allowed. While we encourage maintainers to moderate their own projects on an individual basis, GitHub staff may take further restrictive action against accounts that are engaging in these types of behaviors. -* **晒しとプライバシーの侵害** - 電話番号、プライベート用のメールアドレス、住所、クレジットカード番号、社会保障番号、国民識別番号、パスワードなど、他の人の個人情報は投稿しないでください。 脅迫や嫌がらせに該当するなど状況次第では、当社は対象の同意なしに撮影または配信された写真やビデオなどの他の情報をプライバシーの侵害とみなす場合があります。その情報が対象の安全リスクになる場合は特にです。 +- #### Impersonation You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. なりすましは嫌がらせの一つです。 -* **わいせつなコンテンツ** - ポルノに該当するコンテンツは投稿しないでください。 これは、すべてのヌード、または性に関するすべてのコードやコンテンツが禁止されていることを意味するものではありません。 セクシュアリティは生活の一部であり、ポルノ以外の性的コンテンツがプロジェクトの一部になったり、教育的または芸術的な目的で提示され得るものであることを当社は認識しています。 ただし、わいせつな性的コンテンツや未成年者の搾取や性的関与を含むコンテンツは許可されません。 +- #### Doxxing and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. 脅迫や嫌がらせに該当するなど状況次第では、当社は対象の同意なしに撮影または配信された写真やビデオなどの他の情報をプライバシーの侵害とみなす場合があります。その情報が対象の安全リスクになる場合は特にです。 -* **脈絡のない暴力的コンテンツ** - 合理的な状況や警告なしに暴力的な画像やテキストなどのコンテンツを投稿しないでください。 ビデオゲーム、ニュースレポート、過去の出来事の説明に暴力的なコンテンツを含めることは多くの場合問題ありませんが、無差別に投稿された暴力的コンテンツや、他のユーザにとって回避が困難な方法（例えば、プロフィールアバターや Issue のコメントとして）で投稿された暴力的コンテンツは許可されません。 他のコンテキスト内に明確な警告や断りがあれば、ユーザはそのようなコンテンツに関与したいかどうかについて知識に基づいて判断を下すことができるでしょう。 +- #### Sexually obscene content Don’t post content that is pornographic. これは、すべてのヌード、または性に関するすべてのコードやコンテンツが禁止されていることを意味するものではありません。 セクシュアリティは生活の一部であり、ポルノ以外の性的コンテンツがプロジェクトの一部になったり、教育的または芸術的な目的で提示され得るものであることを当社は認識しています。 ただし、わいせつな性的コンテンツや未成年者の搾取や性的関与を含むコンテンツは許可されません。 -* **Misinformation and disinformation** - You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) because such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information. +- #### Gratuitously violent content Don’t post violent images, text, or other content without reasonable context or warnings. ビデオゲーム、ニュースレポート、過去の出来事の説明に暴力的なコンテンツを含めることは多くの場合問題ありませんが、無差別に投稿された暴力的コンテンツや、他のユーザにとって回避が困難な方法（例えば、プロフィールアバターや Issue のコメントとして）で投稿された暴力的コンテンツは許可されません。 他のコンテキスト内に明確な警告や断りがあれば、ユーザはそのようなコンテンツに関与したいかどうかについて知識に基づいて判断を下すことができるでしょう。 -* **アクティブなマルウェアやエクスプロイト** - コミュニティの一員になる以上、コミュニティの他のメンバーにつけ込むような行為を行ってはいけません。 悪意のある実行可能ファイルを配信する手段としてや、サービス拒否攻撃を組織したりコマンドアンドコントロールサーバーを管理したりといった攻撃インフラとして GitHub を使用するなど、当社のプラットフォームをエクスプロイトの配信に使用することは許されません。 ただし、マルウェアやエクスプロイトの開発に使用される可能性のあるソースコードの投稿は禁止していません。そのようなソースコードの公開と配布には教育的価値があり、セキュリティコミュニティに純粋な利益をもたらすためです。 +- #### Misinformation and disinformation You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information. + +- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. 悪意のある実行可能ファイルを配信する手段としてや、サービス拒否攻撃を組織したりコマンドアンドコントロールサーバーを管理したりといった攻撃インフラとして GitHub を使用するなど、当社のプラットフォームをエクスプロイトの配信に使用することは許されません。 ただし、マルウェアやエクスプロイトの開発に使用される可能性のあるソースコードの投稿は禁止していません。そのようなソースコードの公開と配布には教育的価値があり、セキュリティコミュニティに純粋な利益をもたらすためです。 ### 誰かがルールに違反した場合は diff --git a/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md index 0ca811f3c855..a81d1c16a2ad 100644 --- a/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md @@ -9,7 +9,7 @@ versions: 貴社のビジネスにおけるニーズを満たすために GitHub をお選びいただき、ありがとうございます。 本契約を注意深くお読みください。GitHub がお客様と書面による合意を別途行わない限り、本製品 (以下に定義) の利用に対しては、この契約が適用されます。 「同意する」またはそれに類似するボタンをクリックするか、本製品を利用することにより、お客様は本契約の規約および条件の全てに同意することになります。 お客様が、企業またはその他の法人を代表して契約を締結しようとする場合、お客様は、本契約を締結するためにその企業またはその他の法人に義務を負担させる法的権限を持つことを表明するものとします。 ### GitHub企業向け利用規約 -Version Effective Date: July 20, 2020 +Version Effective Date: November 16, 2020 本契約は、以下に詳述する GitHub の提供品 (併せて「**製品**」) に対して適用されます。 - 「サービス」、 @@ -133,13 +133,13 @@ The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitH お客様が作成または所有する「お客様のコンテンツ」の所有権は、お客様が保持します。 お客様は、 (a)「お客様のコンテンツ」に責任を負うこと、 (b) お客様が投稿する権利を有する「お客様のコンテンツ」(サードパーティまたはユーザーが生成したコンテンツを含む) に限って送信すること、(c) お客様が投稿する「お客様のコンテンツ」に関サードパーティのライセンスに完全に従うことに同意するものとします。 お客様は、セクション D.3 から D.6 で規定されている権利を、無料で、かつ同セクションに記された目的のために付与します。これは、お客様が「お客様のコンテンツ」を GitHub サーバから削除するまで続きますが、お客様が公に投稿し「外部ユーザ」がフォークしたコンテンツは例外となり、その場合は「お客様のコンテンツ」のすべてのフォークが GitHub サーバから削除されるまで続きます。 お客様が、「サービス」を実行するために必要な権限をGitHubに付与するライセンスをあらかじめ伴うような「お客様のコンテンツ」をアップロードする場合、追加のライセンスは必要ありません。 #### 3. 当社へのライセンス許可 -お客様は、「お客様のコンテンツ」を保存、解析、表示し、「サービス」の提供に必要な限りにおいて付随的な複製を作成する権利をGitHubに付与します。 これには、「お客様のコンテンツ」をGitHubのデータベースにコピーし、バックアップを作成する権利、お客様およびお客様が閲覧者として選択した相手に「お客様のコンテンツ」を表示する権利、「お客様のコンテンツ」を解析して検索インデックスを作成するなどの形でGitHubのサーバ上で分析する権利、お客様がコンテンツの共有相手として選択した外部ユーザーと「お客様のコンテンツ」を共有する権利、および音楽や動画のような場合に「お客様のコンテンツ」を実演する権利が含まれます。 これらの権利は、パブリックリポジトリとプライベートリポジトリの両方に適用されます。 このライセンスは、「お客様のコンテンツ」を販売またはその他の方法で配布する、あるいは「サービス」以外で使用する権利をGitHubに付与するものではありません。 お客様は、帰属先を明示せず、また「サービス」の提供に必要な限りにおいて「お客様のコンテンツ」を合理的に適応させる目的で、「お客様のコンテンツ」に必要な権利をGitHubに付与します。 +Customer grants to GitHub the right to store, archive, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service, including improving the Service over time. This license includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. これらの権利は、パブリックリポジトリとプライベートリポジトリの両方に適用されます。 This license does not grant GitHub the right to sell Customer Content. It also does not grant GitHub the right to otherwise distribute or use Customer Content outside of our provision of the Service, except that as part of the right to archive Customer Content, GitHub may permit our partners to store and archive Customer Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. お客様は、帰属先を明示せず、また「サービス」の提供に必要な限りにおいて「お客様のコンテンツ」を合理的に適応させる目的で、「お客様のコンテンツ」に必要な権利をGitHubに付与します。 #### 4. 外部ユーザへのライセンス付与 Issue、コメント、外部ユーザのリポジトリへのコントリビューションなど、お客様が公に投稿するコンテンツは、他のユーザーが閲覧することができます。 リポジトリを公開表示に設定することで、お客様は外部ユーザがお客様のリポジトリを閲覧しフォークすることを許可するものとします。 お客様がそのページおよびリポジトリを一般に公開表示に設定する場合、お客様は「サービス」を通じて「お客様のコンテンツ」を使用、表示、および実演し、またGitHub が提供する機能を通じて許可される限りにおいて (フォークなど) のみ「サービス」上でお客様のコンテンツを複製する、非独占的かつ世界的ライセンスを外部ユーザーに付与します。 お客様がライセンスを採用した場合、他の権利を付与することができます。 お客様が作成または所有していない「お客様のコンテンツ」をアップロードする場合には、アップロードする「お客様のコンテンツ」が、これらの権限を外部ユーザーに付与する条項に基づいて必ずライセンスされるよう図る責任をお客様は負います。 #### 5. リポジトリのライセンス下でのコントリビューション -お客様がライセンスの通知を含むリポジトリに対してコントリビューションを行う際、お客様は必ず同じ条件のもとでそのコントリビューションをライセンスし、それらの条件下でかかるコントリビューションをライセンスする権利を有することに同意するものとします。 お客様が、コントリビューターライセンス契約など、異なる条件のもとでコントリビューションのライセンスを別途締結している場合は、その契約が優先されます。 +Whenever Customer adds Content to a repository containing notice of a license, it licenses that Content under the same terms and agrees that it has the right to license that Content under those terms. If Customer has a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. #### 6. 人格権 お客様は、完全性と帰属の権利も含めて、「サービス」の任意の部分に対してアップロード、公開、またはサブミットする「お客様のコンテンツ」について、すべての人格権を保持します。 ただしお客様は、GitHubがセクション Dで付与された権利を合理的に行使できるようにする目的に限り、これらの権利を放棄し、GitHubに対してこれらの権利を主張しないことに同意するものとしますが、その目的以外ではこの限りではありません。 @@ -153,10 +153,13 @@ Issue、コメント、外部ユーザのリポジトリへのコントリビュ GitHubは、お客様のプライベートリポジトリにある「お客様のコンテンツ」をお客様の機密情報と見なします。 GitHubは、プライベートリポジトリの「お客様のコンテンツ」を、セクション Pに従って保護し、厳密に機密扱いします。 #### 3. アクセス -GitHub personnel may only access Customer’s Private Repositories (i) with Customer’s consent and knowledge, for support reasons or (ii) when access is required for security reasons. お客様は、プライベートリポジトリへのアクセスを追加することもできます。 たとえば、プライベートリポジトリにある「お客様のコンテンツ」への追加の権利を必要とするGitHubの各種サービスまたは機能を有効にするなどが考えられます。 これらの権利はサービスまたは機能によって異なりますが、GitHubは引き続き、お客様のプライベートリポジトリにある「お客様のコンテンツ」をお客様の機密情報として扱います。 これらのサービスが、「サービス」の提供に必要な以上の権利を追加で必要とする場合、GitHubはその件について説明を行います。 +GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 4. 除外 -プライベートリポジトリのコンテンツが法律または本契約に違反していると考えられる理由がある場合、GitHubはそのコンテンツにアクセスし、レビューして削除する権利を有します。 また、[法律により強制された](/github/site-policy/github-privacy-statement#for-legal-disclosure)場合、GitHubは「プライベートリポジトリ」の「コンテンツ」を開示する場合があります。 法律に基づく要件で別段拘束されていない限り、またはセキュリティ上の脅威などセキュリティに対するリスクに対応する目的で、GitHubはかかる行動について通知します。 +お客様は、プライベートリポジトリへのアクセスを追加することもできます。 たとえば、プライベートリポジトリにある「お客様のコンテンツ」への追加の権利を必要とするGitHubの各種サービスまたは機能を有効にするなどが考えられます。 これらの権利はサービスまたは機能によって異なりますが、GitHubは引き続き、お客様のプライベートリポジトリにある「お客様のコンテンツ」をお客様の機密情報として扱います。 これらのサービスが、「サービス」の提供に必要な以上の権利を追加で必要とする場合、GitHubはその件について説明を行います。 + +また、[法律により強制された](/github/site-policy/github-privacy-statement#for-legal-disclosure)場合は、当社はプライベートリポジトリのコンテンツを開示する場合があります。 + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. 知的財産に関する通知 @@ -188,7 +191,7 @@ GitHub personnel may only access Customer’s Private Repositories (i) with Cust #### 1. 価格、料金 -**支払い条件** 料金については、[github.com/pricing](https://github.com/pricing) に掲載されているものが適用されます (ただし、関係者による協議を行い、「注文書」に記載されている場合を除きます)。 お客様は、減額や相殺などに類することを行わず、アメリカ合衆国ドルにより「料金」の全額を前払いで支払うことに同意します。 Dollars. お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 本「契約」に基づいて支払われる金額は、本「契約」に別段の定めがある場合を除き、返金できません。 お客様が定められた期限に「料金」を支払わなかった場合、普通法または衡平法に基づく法的措置を取ることに加え、GitHub は次の権利を留保します。(i) 過去の未払い金に対して毎月 1.0% か、法律により許容される最高額の金利のうち、いずれか低い額の金利を課し、かつ回収に要するあらゆる費用を課すこと、および (ii) 該当する「注文書」または SOW を解約すること。 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 +**支払い条件** 料金については、[github.com/pricing](https://github.com/pricing) に掲載されているものが適用されます (ただし、関係者による協議を行い、「注文書」に記載されている場合を除きます)。 お客様は、減額や相殺などに類することを行わず、アメリカ合衆国ドルにより「料金」の全額を前払いで支払うことに同意します。 設定しなければなりません。 お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 本「契約」に基づいて支払われる金額は、本「契約」に別段の定めがある場合を除き、返金できません。 お客様が定められた期限に「料金」を支払わなかった場合、普通法または衡平法に基づく法的措置を取ることに加え、GitHub は次の権利を留保します。(i) 過去の未払い金に対して毎月 1.0% か、法律により許容される最高額の金利のうち、いずれか低い額の金利を課し、かつ回収に要するあらゆる費用を課すこと、および (ii) 該当する「注文書」または SOW を解約すること。 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 **従量制支払い:** 「サービス」の一部の機能は、使用量に基づいて請求されます。 かかる「サービス」機能は、限られた使用量および期間であれば、追加料金なしでご利用のプランで使用できる場合があります。 ご利用のプランに含まれる数量を超えて有料の「サービス」機能を購入することを選択した場合、お客様は前月の実際の使用量に基づいてかかる「サービス」機能の料金を支払います。 かかる購入に対する毎月の支払いは、後払いで定期的に請求されます。ただし、請求書払いのお客様については、有料の「サービス」機能は前払いとなります。 詳しくは、[GitHub 追加製品の利用規約](/github/site-policy/github-additional-product-terms)を参照してください。 @@ -270,12 +273,12 @@ GitHub は、関係会社以外の第三者による、お客様に対する訴 お客様の「プロフェッショナルサービス」の要請に応じ、GitHub は「プロフェッショナルサービス」に記載されている「SOW」を提供するものとします。 GitHub は、それぞれの「SOW」に記載されている「プロフェッショナルサービス」を実施するものとします。 GitHub は、「プロフェッショナルサービス」が実施される方法および手段を管理するとともに、割り当てる担当者を決定する権利を留保するものとします。 GitHub は、GitHub がその行為および怠慢に対して責任を負うことを条件に、第三者を用いて「プロフェッショナルサービス」を実施できるものとします。 お客様は、ソフトウェア、ツール、仕様、アイデア、概念、発明、プロセス、テクニック、ノウハウを含む、「プロフェッショナルサービス」の実施に関連して使用または開発されたすべての権利、権原、および利益を GitHub が保持することを認め、これに同意するものとします。 「プロフェッショナルサービス」の実施中に、GitHub がお客様に提供する成果物について、お客様が「サービス」と併用する目的に限り、本契約の期間中、お客様に対して非独占的、譲渡不可、世界的規模、使用料無料の期間限定ライセンスを付与するものとします。 ### R. 本規約またはサービスの変更 -GitHub は、独自の裁量により、いつでも本契約を修正する権利を留保し、かかる修正があった場合には本契約を更新します。 GitHub は、独自の裁量により、いつでも本契約を修正する権利を留保し、かかる修正があった場合には本契約を更新します。 重要でない変更については、お客様が「サービス」を継続して利用することをもって、本契約の改訂に同意したものとみなされます。 お客様は、本契約に対するすべての変更を「[サイトポリシー](https://github.com/github/site-policy)」リポジトリで確認できます。 +GitHub は、独自の裁量により、いつでも本契約を修正する権利を留保し、かかる修正があった場合には本契約を更新します。 GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. お客様は、本契約に対するすべての変更を「[サイトポリシー](https://github.com/github/site-policy)」リポジトリで確認できます。 GitHub は、「アップデート」および新機能の追加により、サービスを変更します。 上記にかかわらず、GitHubは通知の有無にかかわらず、「サービス」(またはその一部) をいつでも変更する、あるいは一時的または恒久的に停止する権利を留保するものとします。 ### S. サポート -GitHub は、週末および米国の休日を除き、1 日 24時間、週 5 日の標準的な技術「サポート」を、「サービス」に対して無料で提供するものとします。 （アメリカの祝日は除く） 「Standard Support」は、「GitHub Support」を通じたウェブベースのチケット発行によってのみ提供され、「サポート」の要請は、GitHub の「サポート」チームがやり取りできる「ユーザ」から行う必要があります。 GitHub は、「注文書」または「SOW」に記載されている「サポート」レベル、「料金」、および「プラン契約期間」で、「サービス」に対してプレミアム「サポート」 (「[GitHub Enterprise Cloud の GitHub Premium Support](/articles/about-github-premium-support)」の規定に従う) または専用技術「サポート」を提供することができます。 +GitHub は、週末および米国の休日を除き、1 日 24時間、週 5 日の標準的な技術「サポート」を、「サービス」に対して無料で提供するものとします。 （アメリカの祝日は除く） 「Standard Support」は、「GitHub Support」を通じたウェブベースのチケット発行によってのみ提供され、「サポート」の要請は、GitHub の「サポート」チームがやり取りできる「ユーザ」から行う必要があります。 GitHub may provide premium Support (subject to the [GitHub Premium Support for Enterprise Cloud](/articles/about-github-premium-support) terms) or dedicated technical Support for the Service at the Support level, Fees, and Subscription Term specified in an Order Form or SOW. ### T. 雑則 @@ -307,4 +310,4 @@ GitHub は、週末および米国の休日を除き、1 日 24時間、週 5 各「当事者」は、本契約の主題に関して独立契約者です。 本契約に含まれるいかなる規定も、法的関係、パートナーシップ、合弁事業、雇用、代理、受託、その他これらに類する関係を両「当事者」間に構築するものとはいかなる場合にも見なされるまたは解釈されるものではなく、またいずれの「当事者」も、他方を契約上拘束することはできません。 #### 10. 質問 -「利用規約」について質問がございましたら、 [お問い合わせください](https://github.com/contact/)。 +「利用規約」について質問がございましたら、 [Contact us](https://github.com/contact/). diff --git a/translations/ja-JP/content/github/site-policy/github-enterprise-server-license-agreement.md b/translations/ja-JP/content/github/site-policy/github-enterprise-server-license-agreement.md index eceec1f95bc2..12e8925558f0 100644 --- a/translations/ja-JP/content/github/site-policy/github-enterprise-server-license-agreement.md +++ b/translations/ja-JP/content/github/site-policy/github-enterprise-server-license-agreement.md @@ -88,7 +88,7 @@ If Customer has purchased the Products from a GitHub Partner, the following prov **8. 支払い** -**8.1** *Fees.* Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 Amounts payable under this Agreement are non-refundable, except as provided in Sections 13 and 14.1. 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 +**8.1** *Fees.* Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. 設定しなければなりません。 お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 Amounts payable under this Agreement are non-refundable, except as provided in Sections 13 and 14.1. 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 **8.2** *Purchasing Additional Subscription Licenses.* Customer may obtain additional Subscription Licenses under this Agreement by submitting a request through GitHub’s website or via its sales team. A new Order Form will then be generated and if Customer purchases the additional Subscription Licenses, Customer must pay the then-currently applicable Fees for them, prorated for the balance of the applicable Subscription Term. 「注文書」に特に記載されている場合を除き、お客様が「プランライセンス」を 次の「プラン契約期間」まで更新した際、GitHub は毎年 1 回、すべての「プランライセンス」に対する請求を同時に行います。 diff --git a/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md index c44a2d65179f..f4ac26aacc76 100644 --- a/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -26,6 +26,6 @@ For definitions of each Service feature (“**Service Feature**”) and to revi Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption -If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption should be sent to [GitHub Support](https://support.github.com/contact). +If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). Service Credits may take the form of a refund or credit to Customer’s account, cannot be exchanged into a cash amount, are limited to a maximum of ninety (90) days of paid service per calendar quarter, require Customer to have paid any outstanding invoices, and expire upon termination of Customer’s agreement with GitHub. Service Credits are the sole and exclusive remedy for any failure by GitHub to meet any obligations in this SLA. diff --git a/translations/ja-JP/content/github/site-policy/github-enterprise-subscription-agreement.md b/translations/ja-JP/content/github/site-policy/github-enterprise-subscription-agreement.md index d54791e2ab83..125ec9425835 100644 --- a/translations/ja-JP/content/github/site-policy/github-enterprise-subscription-agreement.md +++ b/translations/ja-JP/content/github/site-policy/github-enterprise-subscription-agreement.md @@ -7,7 +7,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: July 20, 2020 +Version Effective Date: November 16, 2020 「同意する」またはそれに類似するボタンをクリックするか、(以下に定義する) 本製品を利用することにより、お客様は本契約の規約および条件に同意することになります。 お客様が、法人を代表して契約を締結する場合、お客様は、本契約を締結するためにその法人に義務を負担させる法的権限を持つことを表明するものとします。 @@ -59,7 +59,7 @@ Version Effective Date: July 20, 2020 #### 1.2.1 料金 -お客様は、減額や相殺などに類することを行わず、アメリカ合衆国ドルにより「料金」の全額を前払いで支払うことに同意します。 Dollars. お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 本契約により支払われる金額は、セクション 1.5.1 および 1.6.2 に定める場合を除き返金できません。 Amounts payable under this Agreement are non-refundable, except as provided in Sections 13 and 14.1. 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 +お客様は、減額や相殺などに類することを行わず、アメリカ合衆国ドルにより「料金」の全額を前払いで支払うことに同意します。 設定しなければなりません。 お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 本契約により支払われる金額は、セクション 1.5.1 および 1.6.2 に定める場合を除き返金できません。 Amounts payable under this Agreement are non-refundable, except as provided in Sections 13 and 14.1. 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 #### 1.2.2 プランライセンスの追加購入 @@ -197,7 +197,7 @@ GitHub は、お客様を、現在または将来的な顧客に対する顧客 #### 1.13.11 修正、優先順位 -GitHub は、独自の裁量により、いつでも本契約を修正する権利を留保し、かかる修正があった場合には本契約を更新します。 GitHub は、独自の裁量により、いつでも本契約を修正する権利を留保し、かかる修正があった場合には本契約を更新します。 重要でない変更については、お客様が「サービス」を継続して利用することをもって、本契約の改訂に同意したものとみなされます。 お客様は、本契約に対するすべての変更を「[サイトポリシー](https://github.com/github/site-policy)」リポジトリで確認できます。 本契約の規定と、あらゆる「注文書」または「SOW」との間に万が一矛盾がある場合、その「注文書」または「SOW」に関してのみ、「注文書」または「SOW」の規定が支配するものとします。 +GitHub は、独自の裁量により、いつでも本契約を修正する権利を留保し、かかる修正があった場合には本契約を更新します。 GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. お客様は、本契約に対するすべての変更を「[サイトポリシー](https://github.com/github/site-policy)」リポジトリで確認できます。 本契約の規定と、あらゆる「注文書」または「SOW」との間に万が一矛盾がある場合、その「注文書」または「SOW」に関してのみ、「注文書」または「SOW」の規定が支配するものとします。 #### 1.13.12 分離可能性 @@ -296,7 +296,7 @@ If Customer is a U.S. federal government agency or otherwise accessing or using **(ii)** お客様は、セクション3.3.3から3.3.6で規定されている権利を、無料で、かつ同セクションに記された目的のために付与します。これは、お客様が「お客様のコンテンツ」をGitHubサーバから削除するまで続きますが、お客様が公に投稿し「外部ユーザ」がフォークしたコンテンツは例外となり、その場合は「お客様のコンテンツ」のすべてのフォークがGitHubサーバから削除されるまで続きます。 お客様が、「サービス」を実行するために必要な権限をGitHubに付与するライセンスをあらかじめ伴うような「お客様のコンテンツ」をアップロードする場合、追加のライセンスは必要ありません。 #### 3.3.3 GitHubへのライセンス付与 -お客様は、「お客様のコンテンツ」を保存、解析、表示し、「サービス」の提供に必要な限りにおいて付随的な複製を作成する権利をGitHubに付与します。 これには、「お客様のコンテンツ」をGitHubのデータベースにコピーし、バックアップを作成する権利、お客様およびお客様が閲覧者として選択した相手に「お客様のコンテンツ」を表示する権利、「お客様のコンテンツ」を解析して検索インデックスを作成するなどの形でGitHubのサーバ上で分析する権利、お客様がコンテンツの共有相手として選択した外部ユーザーと「お客様のコンテンツ」を共有する権利、および音楽や動画のような場合に「お客様のコンテンツ」を実演する権利が含まれます。 これらの権利は、パブリックリポジトリとプライベートリポジトリの両方に適用されます。 このライセンスは、「お客様のコンテンツ」を販売またはその他の方法で配布する、あるいは「サービス」以外で使用する権利をGitHubに付与するものではありません。 お客様は、帰属先を明示せず、また「サービス」の提供に必要な限りにおいて「お客様のコンテンツ」を合理的に適応させる目的で、「お客様のコンテンツ」に必要な権利をGitHubに付与します。 +Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service. これには、「お客様のコンテンツ」をGitHubのデータベースにコピーし、バックアップを作成する権利、お客様およびお客様が閲覧者として選択した相手に「お客様のコンテンツ」を表示する権利、「お客様のコンテンツ」を解析して検索インデックスを作成するなどの形でGitHubのサーバ上で分析する権利、お客様がコンテンツの共有相手として選択した外部ユーザーと「お客様のコンテンツ」を共有する権利、および音楽や動画のような場合に「お客様のコンテンツ」を実演する権利が含まれます。 これらの権利は、パブリックリポジトリとプライベートリポジトリの両方に適用されます。 このライセンスは、「お客様のコンテンツ」を販売またはその他の方法で配布する、あるいは「サービス」以外で使用する権利をGitHubに付与するものではありません。 お客様は、帰属先を明示せず、また「サービス」の提供に必要な限りにおいて「お客様のコンテンツ」を合理的に適応させる目的で、「お客様のコンテンツ」に必要な権利をGitHubに付与します。 #### 3.3.3 外部ユーザへのライセンス付与 **(i)** Issue、コメント、外部ユーザのリポジトリへのコントリビューションなど、お客様が公に投稿するコンテンツは、他のユーザーが閲覧することができます。 リポジトリを公開表示に設定することで、お客様は外部ユーザがお客様のリポジトリを閲覧しフォークすることを許可するものとします。 @@ -318,10 +318,13 @@ If Customer is a U.S. federal government agency or otherwise accessing or using GitHubは、お客様のプライベートリポジトリにある「お客様のコンテンツ」をお客様の機密情報と見なします。 GitHubは、プライベートリポジトリの「お客様のコンテンツ」を、セクション1.4に従って保護し、厳密に機密扱いします。 #### 3.4.3 アクセス -GitHubがお客様のプライベートリポジトリにアクセスするのは、(i) サポート上の理由からお客様の同意と承認を得ている、または (ii) セキュリティ上の理由からアクセスが必須となっている場合だけです。 お客様は、プライベートリポジトリへのアクセスを追加することもできます。 たとえば、プライベートリポジトリにある「お客様のコンテンツ」への追加の権利を必要とするGitHubの各種サービスまたは機能を有効にするなどが考えられます。 これらの権利はサービスまたは機能によって異なりますが、GitHubは引き続き、お客様のプライベートリポジトリにある「お客様のコンテンツ」をお客様の機密情報として扱います。 これらのサービスが、「サービス」の提供に必要な以上の権利を追加で必要とする場合、GitHubはその件について説明を行います。 +GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 3.4.4 免責 -プライベートリポジトリのコンテンツが法律または本契約に違反していると考えられる理由がある場合、GitHubはそのコンテンツにアクセスし、レビューして削除する権利を有します。 また、GitHubはお客様のプライベートリポジトリのコンテンツを開示するよう法律で強制される場合があります。 法律に基づく要件で別段拘束されていない限り、またはセキュリティ上の脅威などセキュリティに対するリスクに対応する目的で、GitHubはかかる行動について通知します。 +お客様は、プライベートリポジトリへのアクセスを追加することもできます。 たとえば、プライベートリポジトリにある「お客様のコンテンツ」への追加の権利を必要とするGitHubの各種サービスまたは機能を有効にするなどが考えられます。 これらの権利はサービスまたは機能によって異なりますが、GitHubは引き続き、お客様のプライベートリポジトリにある「お客様のコンテンツ」をお客様の機密情報として扱います。 これらのサービスが、「サービス」の提供に必要な以上の権利を追加で必要とする場合、GitHubはその件について説明を行います。 + +また、[法律により強制された](/github/site-policy/github-privacy-statement#for-legal-disclosure)場合は、当社はプライベートリポジトリのコンテンツを開示する場合があります。 + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 3.5. 知的財産に関する通知 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 530c3e284add..7f8ee21b28c6 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 @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Effective date: October 2, 2020 +発効日：2020年11月16日 お客様のソースコードやプロジェクト、個人情報について、GitHub Inc （以下、「GitHub」「当社」と称します）をご信頼いただき、ありがとうございます。 お客様の個人情報を保持することは重大な責務であり、当社がどのように取り扱っているのかを知っていただければと思います。 @@ -150,23 +150,39 @@ GitHubは、法的手続きおよび法的義務を遵守するために透明 備考：2018年カリフォルニア州消費者プライバシー法（「CCPA」）では、事業体が自らのプライバシーポリシーにおいて、お客様の個人情報を金銭または他の対価と交換で、個人情報を公開するかどうかを記述することを要求しています。 While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. CCPAおよび当社の遵守についての詳細は[こちら](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act)を参照してください。 -### その他の重要なお知らせ +### リポジトリコンテンツ + +#### Access to private repositories + +If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for +- security purposes +- to assist the repository owner with a support matter +- to maintain the integrity of the Service +- to comply with our legal obligations +- if we have reason to believe the contents are in violation of the law, or +- お客様の同意を得た場合. + +However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories). -#### リポジトリコンテンツ +Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts). -GitHub personnel [do not access private repositories unless required to](/github/site-policy/github-terms-of-service#e-private-repositories) for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, or to comply with our legal obligations. However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, or other content known to violate our Terms, such as violent extremist or terrorist content or child exploitation imagery based on algorithmic fingerprinting techniques. 当社の利用規約について、[より詳細な内容](/github/site-policy/github-terms-of-service#e-private-repositories)を提供します。 +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. -リポジトリが公開されている場合、誰でもそのコンテンツを閲覧できます。 公開リポジトリにメールアドレスまたはパスワードなどのプライベート、秘密または[センシティブな個人情報](https://gdpr-info.eu/art-9-gdpr/)が含まれる場合、その情報はサーチエンジンによりインデックス化されることがあります。または、第三者に利用されることもあります。 +#### Public repositories + +リポジトリが公開されている場合、誰でもそのコンテンツを閲覧できます。 If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. [公開リポジトリのユーザ個人情報](/github/site-policy/github-privacy-statement#public-information-on-github)を参照してください。 +### その他の重要なお知らせ + #### GitHub上の公開情報 GitHubサービスおよび機能の多くは公開向けです。 お客様のコンテンツが公開向けの場合、第三者が、お客様のプロフィールもしくはリポジトリの閲覧または当社のAPIを介してデータをプルするなど、当社の利用規約にもとづきアクセスかつ利用できます。 当社は、そのコンテンツを販売しません。これはお客様の所有物です。 しかし、当社は、研究機関やアーカイブなどの第三者に対して、公開向けのGitHub情報をコンパイルすることを認めています。 データブローカーなどの他の第三者も、GitHubをスクレイプし、データをコンパイルしていることは知られています。 お客様のコンテンツに関係するユーザ個人情報はGitHubデータのコンパイルによって第三者が収集する場合があります。 お客様が第三者によるGitHubデータのコンパイルにユーザ個人情報が含まれることを望まない場合、ユーザ個人情報を公開しないようにしてください。そして、[gitコミット設定](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)で、[ユーザプロフィールでメールアドレスを非公開に設定してください](https://github.com/settings/emails)。 当社は現在、デフォルト設定ではユーザのメールアドレスを非公開に設定しています。ただし、レガシーのGitHubユーザは設定をアップデートしなくてはならない場合があります。 -GitHubデータをコンパイルしたい場合、お客様は、[スクレイピング](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions)および[プライバシー](/github/site-policy/github-acceptable-use-policies#6-privacy)に関する当社の利用規約を遵守しなければなりません。ならびに、お客様は、収集した公開向けユーザ個人情報を、当社のユーザが許可した目的に限り利用できるものとします。 たとえば、GitHubユーザが識別および属性用途のためにメールアドレスを公開向けとした場合、当該メールアドレスを商業広告に利用しないものとします。 当社は、お客様が、GitHubから収集したあらゆるユーザ個人情報を合理的に保護すること、ならびに、 GitHubまたは他のユーザからの苦情、削除要請および連絡拒否のリクエストに速やかに対応することを要求します。 +If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. 当社は、お客様が、GitHubから収集したあらゆるユーザ個人情報を合理的に保護すること、ならびに、 GitHubまたは他のユーザからの苦情、削除要請および連絡拒否のリクエストに速やかに対応することを要求します。 これに類して、GitHub上のプロジェクトは、コラボレーティブ処理の一部として収集した公開されている利用可能なユーザ個人情報を含むことがあります。 GitHub上のユーザ個人情報について苦情がある場合、[苦情の解決](/github/site-policy/github-privacy-statement#resolving-complaints)を参照してください。 @@ -219,7 +235,7 @@ GitHubは、一般的に、ユーザ個人情報をアカウントがアクテ #### クッキー -GitHub uses cookies and similar technologies (collectively, “cookies”) to make interactions with our service easy and meaningful. Cookie は、ウェブサイトが訪問者のコンピュータまたはモバイルデバイスに度々格納する小さなテキストファイルです。 We use cookies to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. 当社のウェブサイトを利用することで、お客様は、お客様のコンピュータまたはデバイスにこれらの種類のクッキーを当社が保管することに同意したものとされます。 お客様がこれらのクッキーを許可するブラウザまたはデバイスの能力を無効にした場合、GitHubのサービスにログインまたは利用することはできなくなります。 +GitHub uses cookies and similar technologies (e.g., HTML5 localStorage) to make interactions with our service easy and meaningful. Cookie は、ウェブサイトが訪問者のコンピュータまたはモバイルデバイスに度々格納する小さなテキストファイルです。 We use cookies and similar technologies (hereafter collectively "cookies") to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. 当社のウェブサイトを利用することで、お客様は、お客様のコンピュータまたはデバイスにこれらの種類のクッキーを当社が保管することに同意したものとされます。 お客様がこれらのクッキーを許可するブラウザまたはデバイスの能力を無効にした場合、GitHubのサービスにログインまたは利用することはできなくなります。 We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies. It also lists our third-party analytics providers and how you can control your cookie preference settings for such cookies. @@ -300,7 +316,7 @@ GitHub processes personal information both inside and outside of the United Stat ### プライバシーステートメントの変更 -ほとんどの変更は軽微ですが、GitHubは、随時、プライバシーステートメントを変更することがあります。 当社は、ホームページに通知を掲載すること、または、GitHubアカウントで指定するプライマリメールアドレスにemailを送信することで、変更が発効する遅くとも30日前にウェブサイト上で、このプライバシーステートメントの重要な変更についてユーザへの通知を提供します。 また、当社は、このポリシーの変更を追跡している[サイトポリシーリポジトリ](https://github.com/github/site-policy/)をアップデートします。 重要ではない変更またはお客様に影響を与えない、このプライバシーステートメントの変更について、当社は、サイトポリシーリポジトリを頻繁に確認することを推奨します。 +ほとんどの変更は軽微ですが、GitHubは、随時、プライバシーステートメントを変更することがあります。 当社は、ホームページに通知を掲載すること、または、GitHubアカウントで指定するプライマリメールアドレスにemailを送信することで、変更が発効する遅くとも30日前にウェブサイト上で、このプライバシーステートメントの重要な変更についてユーザへの通知を提供します。 また、当社は、このポリシーの変更を追跡している[サイトポリシーリポジトリ](https://github.com/github/site-policy/)をアップデートします。 For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### ライセンス diff --git a/translations/ja-JP/content/github/site-policy/github-terms-of-service.md b/translations/ja-JP/content/github/site-policy/github-terms-of-service.md index a8ae684d9090..48d1154e641a 100644 --- a/translations/ja-JP/content/github/site-policy/github-terms-of-service.md +++ b/translations/ja-JP/content/github/site-policy/github-terms-of-service.md @@ -32,11 +32,11 @@ GitHubをご利用いただきありがとうございます。 また、こち | [N. 保証免責](#n-disclaimer-of-warranties) | 当社は、サービスを現状有姿で提供し、本サービスについて一切の約束も保証も行いません。 **このセクションは特によくお読みください。何を期待できるかを理解しておく必要があります。** | | [O. 責任の制限](#o-limitation-of-liability) | 当社は、サービスを利用するかもしくは利用できないことに起因する損害または損失、あるいはその他本契約に基づいて発生する損害または損失については責任を負いません。 **このセクションは特によくお読みください。お客様に対する当社の義務を制限する内容になっています。** | | [P. 免責・補償](#p-release-and-indemnification) | あなたはサービスの利用に対するすべての責任を負います。 | -| [Q. 本利用規約の変更](#q-changes-to-these-terms) | 当社は本契約を変更する場合がありますが、お客様の権利に影響する変更を行う場合は30日前に通知します。 | +| [Q. 本利用規約の変更](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. | | [R. 雑則](#r-miscellaneous) | 法の選択を含む法的詳細については、このセクションをご覧ください。 | ### GitHub 利用規約 -Effective date: April 2, 2020 +発効日：2020年11月16日 ### A. 定義 @@ -98,7 +98,7 @@ GitHub の「サービス」の「ユーザアカウント」には、いくつ 「サービス」の利用中に、お客様は「ユーザ生成コンテンツ」を作成またはアップロードすることができます。 お客様は、「コンテンツ」の形式に関係なく、お客様が「サービス」に投稿、アップロード、リンクするか、またはその他「サービス」を介して利用可能にする「ユーザ生成コンテンツ」のコンテンツおよびその結果生じる損害に対して単独で責任を負います。 当社は、お客様の「ユーザ生成コンテンツ」のいかなる公開表示または悪用に対しても責任を負いません。 #### 2. GitHub によるコンテンツの削除 -We do not pre-screen User-Generated Content, but we have the right (though not the obligation) to refuse or remove any User-Generated Content that, in our sole discretion, violates any [GitHub terms or policies](/github/site-policy). +We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub for mobile may be subject to mobile app stores' additional terms. #### 3. コンテンツの所有権、投稿する権利、ライセンスの付与 お客様は、「あなたのコンテンツ」の所有権および責任を保持します。 お客様が自身で作成していないものや権利を所有していないものを投稿する場合、お客様は投稿する「コンテンツ」に責任を負うこと、お客様に投稿する権利がある「コンテンツ」のみを送信すること、および投稿する「コンテンツ」に関連する第三者のライセンスを完全に遵守することに同意するものとします。 @@ -106,9 +106,9 @@ We do not pre-screen User-Generated Content, but we have the right (though not t お客様は「あなたのコンテンツ」の所有権と責任を保持しているため、当社は、セクション D.4〜D.7 に記載されている特定の法的権限を当社および GitHub の他の「ユーザ」に付与することを求めます。 かかるライセンス付与は、「あなたのコンテンツ」に適用されます。 お客様が、当社が「サービス」を実行するために必要な権限を GitHub に付与するライセンスをあらかじめ伴うような「コンテンツ」をアップロードする場合、追加のライセンスは必要ありません。 お客様は、セクション D.4〜D.7 で付与された権利のいずれに対しても支払いを受け取らないことを理解するものとします。 他の「ユーザ」がフォークした場合を除き、当社のサーバーから「あなたのコンテンツ」を削除すると、当社に付与したライセンスは終了します。 #### 4. 当社へのライセンス許可 -当社には、「あなたのコンテンツ」のホスト、公開および共有などを行うための法的権利が必要です。 お客様は、当社およびその後継者に、「あなたのコンテンツ」を保存、解析、および表示し、「ウェブサイト」のレンダリングおよび「サービス」の提供のために必要に応じて付随的な複製を作成する権利を付与します。 これには、「あなたのコンテンツ」が音楽やビデオなどのものである場合、データベースにコピーしてバックアップを作成する、お客様および他のユーザに表示する、検索インデックスに解析するか、またはその他サーバー上で分析する、他のユーザと共有する、並びに実行するなどの操作を行う権利が含まれます。 +当社には、「あなたのコンテンツ」のホスト、公開および共有などを行うための法的権利が必要です。 You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. -このライセンスは、「あなたのコンテンツ」を販売またはその他の方法で配布する、あるいは「サービス」の提供以外で使用する権利を GitHub に付与するものではありません。 +This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/). #### 5. 他のユーザへのライセンス許可 Issue、コメント、他の「ユーザ」のリポジトリへのコントリビューションなど、お客様が公に投稿する「ユーザ生成コンテンツ」は、他者によって閲覧される場合があります。 リポジトリを公に表示するように設定することにより、お客様は、他者がリポジトリを表示および「フォーク」できるようになることに同意するものとします (これは、他者が管理するリポジトリ内のお客様のリポジトリから他者が「コンテンツ」の独自の複製を作成できることを意味します)。 @@ -116,7 +116,7 @@ Issue、コメント、他の「ユーザ」のリポジトリへのコントリ お客様が自身のページおよびリポジトリを公に表示するように設定した場合、お客様は GitHub の「サービス」を通じて「あなたのコンテンツ」を使用、表示、および実演し、また GitHub の機能を通じて許可される限りにおいて (フォークなど) のみ GitHub 上で「あなたのコンテンツ」を複製する、非独占的かつ世界的ライセンスを GitHub の各「ユーザ」に付与します。 お客様が[ライセンスを採用](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository)した場合、他の権利を付与することができます。 お客様が作成または所有していない「コンテンツ」をアップロードする場合には、アップロードする「コンテンツ」が、これらの権限を GitHub の他の「ユーザ」に付与する条項に基づいて必ずライセンスされるよう図る責任を負います。 #### 6. リポジトリのライセンス下でのコントリビューション -お客様がライセンスの通知を含むリポジトリに対してコントリビューションを行う際、お客様は必ず同じ条件のもとで自身のコントリビューションをライセンスし、それらの条件下で自身のコントリビューションをライセンスする権利を有することに同意するものとします。 お客様が、コントリビューターライセンス契約など、異なる条件のもとでコントリビューションのライセンスを別途締結している場合は、その契約が優先されます。 +Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. おそらくこれはすでに当たり前のことでしょう。 実際、 これはオープンソースコミュニティの規範として広く受け入れられています。一般的には、「インバウンド=アウトバウンド」という短縮形で呼ばれます。 このことを明示的にしているにすぎません。 @@ -126,7 +126,7 @@ Issue、コメント、他の「ユーザ」のリポジトリへのコントリ 本契約が適用法で強制できない範囲において、帰属なしで「あなたのコンテンツ」を使用し、「ウェブサイト」のレンダリングと「サービス」の提供に必要な「あなたのコンテンツ」の合理的な適応を行うために必要な権利を GitHub に付与します。 ### E. プライベートリポジトリ -**趣旨の要約:** *お客様は、プライベートリポジトリにアクセスできます。 当社はプライベートリポジトリのコンテンツを機密として扱い、サポート上の理由がある場合、同意がある場合、またはセキュリティ上の理由で必要な場合にのみこれにアクセスします。* +**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.* #### 1. プライベートリポジトリの制御 一部の「アカウント」には、「ユーザ」が「コンテンツ」へのアクセスを制御することを可能にするプライベートリポジトリがある場合があります。 @@ -135,15 +135,14 @@ Issue、コメント、他の「ユーザ」のリポジトリへのコントリ GitHub は、プライベートリポジトリのコンテンツを機密情報とみなします。 GitHub は、プライベートリポジトリのコンテンツを不正な使用、アクセス、または開示から保護します。これは、同様の性質の独自の機密情報を保護するために使用する方法と同じで、いかなる場合も一定以上の合理的な注意が払われるものとします。 #### 3. アクセス -GitHub personnel may only access the content of your private repositories in the following situations: -- サポート上の理由で、お客様の同意と認識がある場合。 サポート上の理由で GitHub がプライベートリポジトリにアクセスする場合、所有者の同意と認識がある場合にのみアクセスします。 -- GitHub のシステムおよび「サービス」の継続的な機密性、整合性、可用性、復元力を維持するためにアクセスが必要な場合など、セキュリティ上の理由でアクセスが必要な場合。 +GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). お客様は、自身のプライベートリポジトリへのアクセスを追加することもできます。 例: - プライベートリポジトリにある「あなたのコンテンツ」への追加の権利を必要とする GitHub の各種サービスまたは機能を有効にするなどが考えられます。 こうした権利はサービスまたは機能によって異なる場合がありますが、GitHub は引き続きプライベートリポジトリの「コンテンツ」を機密として扱います。 これらのサービスまたは機能が、GitHub の「サービス」の提供に必要な以上の権利を追加で必要とする場合、当社はその件について説明を行います。 -#### 4. 除外 -プライベートリポジトリのコンテンツが法律または本「規約」に違反していると考えられる理由がある場合、当社はそのコンテンツにアクセスし、レビューして削除する権利を有します。 また、[法律により強制された](/github/site-policy/github-privacy-statement#for-legal-disclosure)場合は、当社はプライベートリポジトリのコンテンツを開示する場合があります。 +また、[法律により強制された](/github/site-policy/github-privacy-statement#for-legal-disclosure)場合は、当社はプライベートリポジトリのコンテンツを開示する場合があります。 + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. 著作権侵害と DMCA ポリシー 当社のウェブサイトのコンテンツが著作権を侵害していると思われる場合は、[デジタルミレニアム著作権法ポリシー](/articles/dmca-takedown-policy/)に従ってご連絡ください。 あなたが著作権所有者であり、GitHub のコンテンツがあなたの権利を侵害していると思われる場合は、[便利な DMCA フォーム](https://github.com/contact/dmca)またはメール (copyright@github.com) でお問い合わせください。 虚偽または根拠のない削除通知を送信すると、法的責任が生じる場合があります。 削除リクエストを送信する前に、フェアユースやライセンス使用などの法的使用を検討する必要があります。 @@ -216,7 +215,7 @@ GitHub は、高スループットアクセスまたは GitHub の「サービ **使用量に基づく支払い:** 「サービス」の一部の機能は、使用量に基づいて請求されます。 かかる「サービス」機能は、限られた使用量および期間であれば、追加料金なしでご利用のプランで使用できる場合があります。 ご利用のプランに含まれる数量を超えて有料の「サービス」機能を購入することを選択した場合、お客様は前月の実際の使用量に基づいてかかる「サービス」機能の料金を支払います。 かかる購入に対する毎月の支払いは、後払いで定期的に請求されます。 詳しくは、[GitHub 追加製品の利用規約](/github/site-policy/github-additional-product-terms)を参照してください。 -**請求:** 請求書払いの「ユーザ」の場合、「ユーザ」は、いかなる種類の控除も相殺もなく料金の全額を米ドルの前払いで支払うことに同意するものとします。 Dollars. 「ユーザ」は、GitHub による請求日から 30 日以内に料金を支払う必要があります。 本「契約」に基づいて支払われる金額は、本「契約」に別段の定めがある場合を除き、返金できません。 「ユーザ」が定められた期限に料金を支払わなかった場合、普通法または衡平法に基づく法的措置を取ることに加え、GitHub は次の権利を留保します。(i) 過去の未払い金に対して毎月 1.0% か、法律により許容される最高額の金利のうち、いずれか低い額の金利を課し、かつ回収に要するあらゆる費用を課すこと、および (ii) 該当する注文書を解約すること。 本「契約」に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 +**請求:** 請求書払いの「ユーザ」の場合、「ユーザ」は、いかなる種類の控除も相殺もなく料金の全額を米ドルの前払いで支払うことに同意するものとします。 設定しなければなりません。 「ユーザ」は、GitHub による請求日から 30 日以内に料金を支払う必要があります。 本「契約」に基づいて支払われる金額は、本「契約」に別段の定めがある場合を除き、返金できません。 「ユーザ」が定められた期限に料金を支払わなかった場合、普通法または衡平法に基づく法的措置を取ることに加え、GitHub は次の権利を留保します。(i) 過去の未払い金に対して毎月 1.0% か、法律により許容される最高額の金利のうち、いずれか低い額の金利を課し、かつ回収に要するあらゆる費用を課すこと、および (ii) 該当する注文書を解約すること。 本「契約」に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 #### 4. 認可 本「規約」に同意することにより、お客様は GitHub に対して承認した料金について、登録されたクレジットカード、PayPal アカウント、またはその他の承認された支払い方法に請求する許可を当社に与えるものとします。 @@ -286,9 +285,9 @@ GitHub は、「サービス」がお客様の要件を満たすこと、「サ お客様は、本「契約」のお客様の違反を含むがこれに限定されない、「ウェブサイト」および「サービス」の利用に起因する、弁護士費用を含むあらゆる請求、負債、および費用から当社を補償し、弁護し、無害に保つことに同意します。ただし、GitHub が (1) 請求、要求、訴訟または法的手続きの書面による通知を速やかにあなたに提供する、(2) 請求、要求、訴訟または法的手続きの弁護および和解の単独の支配権をお客様に与える (ただし、和解によって GitHub のすべての責任が無条件に解除されない限り、お客様は請求、要求、訴訟または法的手続きを和解できないことを条件とします)、並びに (3) お客様の費用負担により、合理的なあらゆる支援をお客様に提供することを条件とします。 ### Q. 本規約の変更 -**趣旨の要約:** *当社は規約に重要な変更があった場合にそれをユーザに知らせたいと思う一方、それほど重要ではない変更があることも事実で、たとえば誤字を修正するたびにお客様の手を焼かせるのは不本意です。 そのため、本契約は適宜変更される場合がありますが、当社がユーザに通知を行うのは、お客様の権利に影響する変更があった場合で、この場合、当社はかかる変更に慣れるための時間を提供します。* +**趣旨の要約:** *当社は規約に重要な変更があった場合にそれをユーザに知らせたいと思う一方、それほど重要ではない変更があることも事実で、たとえば誤字を修正するたびにお客様の手を焼かせるのは不本意です。 So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.* -当社は、独自の裁量により、いつでも本「利用規約」を修正する権利を留保し、かかる修正があった場合には本「利用規約」を更新します。 価格の変更などの本「契約」の重要な変更があった場合、当社は、変更が有効になる 30 日以上前に、「ウェブサイト」に通知を掲載することで、その旨を「ユーザ」に通知します。 重要でない変更については、お客様が「ウェブサイト」を継続して利用することをもって、本「利用規約」の改訂に同意したものとみなされます。 これらの「条項」におけるすべての変更は、[サイトポリシー](https://github.com/github/site-policy)リポジトリで確認できます。 +当社は、独自の裁量により、いつでも本「利用規約」を修正する権利を留保し、かかる修正があった場合には本「利用規約」を更新します。 We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. これらの「条項」におけるすべての変更は、[サイトポリシー](https://github.com/github/site-policy)リポジトリで確認できます。 当社は予告の有無にかかわらず、「ウェブサイト」(またはその一部) を常時およびその時々に変更し、一時的または永続的に停止する権利を留保します。 diff --git a/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md index f796a57aaea2..8381cfce3959 100644 --- a/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md +++ b/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md @@ -41,12 +41,12 @@ versions: コミットの SHA ハッシュへの参照は、{% data variables.product.product_name %}上のコミットへの短縮リンクに自動的に変換されます。 -| 参照タイプ | RAW 参照 | 短縮リンク | -| -------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | -| コミット URL | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| ユーザ@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| ユーザ名/リポジトリ@SHA | jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| 参照タイプ | RAW 参照 | 短縮リンク | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | +| コミット URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| ユーザ@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| `ユーザ名/リポジトリ@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | ### 外部リソースへのカスタム自動リンク diff --git a/translations/ja-JP/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md b/translations/ja-JP/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md index 82b237ff476d..87dd557055c5 100644 --- a/translations/ja-JP/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md +++ b/translations/ja-JP/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md @@ -8,19 +8,24 @@ versions: {% note %} -**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 現在のところ、{% data variables.product.prodname_github_container_registry %} がサポートしているのは Docker イメージフォーマットのみです。 ベータ期間中は、ストレージおよび帯域幅の制限はありません。 +**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% endnote %} - {% data reusables.package_registry.container-registry-feature-highlights %} パッケージの使用についてのコンテキストを共有するには、{% data variables.product.prodname_dotcom %} でコンテナイメージをリポジトリにリンクできます。 詳しい情報については、「[リポジトリをコンテナイメージに接続する](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)」を参照してください。 ### サポートされているフォーマット -{% data variables.product.prodname_container_registry %} は、現在のところ Docker イメージのみをサポートしています。 +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +#### Manifest Lists/Image Indexes +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. ### コンテナイメージの可視性とアクセス権限 diff --git a/translations/ja-JP/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md b/translations/ja-JP/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md new file mode 100644 index 000000000000..db99c9b07422 --- /dev/null +++ b/translations/ja-JP/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md @@ -0,0 +1,37 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 During the beta, storage and bandwidth are free. 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/getting-started-with-github-container-registry/about-github-container-registry)」を参照してください。 + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. 詳しい情報については、「[コンテナイメージにアクセス制御と可視性を設定する](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)」を参照してください。 + + ![パブリックまたはプライベートパッケージを有効にするオプション ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/ja-JP/content/packages/getting-started-with-github-container-registry/index.md b/translations/ja-JP/content/packages/getting-started-with-github-container-registry/index.md index 6ba81af8fed6..16b6f7f4b41a 100644 --- a/translations/ja-JP/content/packages/getting-started-with-github-container-registry/index.md +++ b/translations/ja-JP/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 %} コンテナイメージの設定、削除、プッシュ、プルに関する詳しい情報については、「[{% data variables.product.prodname_github_container_registry %} でのコンテナイメージ管理](/packages/managing-container-images-with-github-container-registry)」を参照してください。 diff --git a/translations/ja-JP/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md b/translations/ja-JP/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md index 14b98434cb70..ca46a7f962fc 100644 --- a/translations/ja-JP/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md +++ b/translations/ja-JP/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md @@ -31,6 +31,8 @@ versions: ### コンテナレジストリで認証する +{% data reusables.package_registry.feature-preview-for-container-registry %} + {% data variables.product.prodname_container_registry %} は、 ベース URL `ghcr.io` で認証する必要があります。 {% data variables.product.prodname_container_registry %} を使用するために、新しいアクセストークンの作成をお勧めします。 {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} @@ -72,6 +74,8 @@ versions: ### {% data variables.product.prodname_actions %} ワークフローを更新する +{% data reusables.package_registry.feature-preview-for-container-registry %} + {% data variables.product.prodname_registry %} Docker レジストリから Docker イメージを使用する {% data variables.product.prodname_actions %} ワークフローがある場合、ワークフローを {% data variables.product.prodname_container_registry %} に更新するといいでしょう。そうすればパブリックコンテナのイメージへの匿名アクセスが可能になり、きめ細かいアクセス権限を設定でき、コンテナに対するストレージと帯域幅が向上します。 1. `ghcr.io` にある新しい {% data variables.product.prodname_container_registry %} に Docker イメージを移行します。 例については、「[Docker CLI を使用して Docker イメージを移行する](#migrating-a-docker-image-using-the-docker-cli)」を参照してください。 diff --git a/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md b/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md index 914fcf10de60..5a6dc5110c43 100644 --- a/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md +++ b/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md @@ -24,7 +24,7 @@ Organization が所有するコンテナイメージに対する管理者権限 パッケージが Organization の所有でかつプライベートである場合、他の Organization のメンバーまたは Team にのみアクセス権を付与できます。 -Organization イメージコンテナに対しては、Organization の管理者がパッケージを有効にしないと、可視性をパブリックに設定できません。 詳しい情報については、「[GitHub Container Registry を Organization に対して有効化する](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)」を参照してください。 +Organization イメージコンテナに対しては、Organization の管理者がパッケージを有効にしないと、可視性をパブリックに設定できません。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 1. パッケージ設定ページで [**Invite teams or people**] をクリックして、アクセス権を付与するユーザの名前、ユーザ名、またはメールアドレスを入力します。 また、Organization から Team 名を入力して、全 Team メンバーにアクセスを付与することもできます。 ![コンテナアクセス権の招待ボタン](/assets/images/help/package-registry/container-access-invite.png) @@ -54,7 +54,7 @@ Organization イメージコンテナに対しては、Organization の管理者 パブリックパッケージは認証なしに匿名でアクセスできます。 いったんパッケージをパブリックに設定すると、そのパッケージをプライベートに戻すことはできません。 -Organization イメージコンテナに対しては、Organization の管理者がパブリックパッケージを有効にしないと、可視性をパブリックに設定できません。 詳しい情報については、「[GitHub Container Registry を Organization に対して有効化する](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)」を参照してください。 +Organization イメージコンテナに対しては、Organization の管理者がパブリックパッケージを有効にしないと、可視性をパブリックに設定できません。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 5. [Danger Zone] の下で、可視性の設定を選択します。 diff --git a/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md b/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md index 5e9526ee59a4..e795078ea3d0 100644 --- a/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md +++ b/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md @@ -16,8 +16,6 @@ versions: パブリックパッケージを削除する場合、そのパッケージに依存するプロジェクトを破壊する可能性があることに注意してください。 - - ### 予約されているパッケージのバージョンと名前 {% data reusables.package_registry.package-immutability %} diff --git a/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md index 53e30f040795..bbaf32a1b528 100644 --- a/translations/ja-JP/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ b/translations/ja-JP/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 %} -Organization が所有するコンテナイメージをプッシュまたはプルするには、{% data variables.product.prodname_github_container_registry %} を Organization に対して有効化する必要があります。 詳しい情報については、「[GitHub Container Registry を Organization に対して有効化する](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)」を参照してください。 +Organization が所有するコンテナイメージをプッシュまたはプルするには、{% data variables.product.prodname_github_container_registry %} を Organization に対して有効化する必要があります。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." ### {% data variables.product.prodname_github_container_registry %} への認証を行う 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 55642784fb33..9b23fe94cc5e 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 @@ -26,6 +26,8 @@ versions: {% data reusables.package_registry.container-registry-beta %} +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + {% endif %} #### パッケージの表示 @@ -34,17 +36,17 @@ versions: #### パッケージの権限と可視性について {% if currentVersion == "free-pro-team@latest" %} -| | パッケージレジストリ | {% data variables.product.prodname_github_container_registry %} -| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- | -| ホスト場所 | 1 つのリポジトリに複数のパッケージをホストできます。 | 1 つの Organization またはユーザアカウントに複数のコンテナをホストできます。 | -| 権限 | {{ site.data.reusables.package_registry.public-or-private-packages }} パッケージはリポジトリの権限を継承するので、{{ site.data.variables.product.prodname_dotcom }}のロールとTeamを使い、各パッケージをインストールしたり公開したりできる人を制限できます。 リポジトリの読み取り権限を持っている人は、パッケージを依存関係としてプロジェクトにインストールでき、書き込み権限を持っている人は新しいパッケージのバージョンを公開できます。 | コンテナイメージごとに、他のユーザが持つアクセスレベルを選択できます。 コンテナイメージへのアクセス権限は、Organization およびリポジトリの権限とは別になります。 | +| | パッケージレジストリ | {% data variables.product.prodname_github_container_registry %} +| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | +| ホスト場所 | 1 つのリポジトリに複数のパッケージをホストできます。 | 1 つの Organization またはユーザアカウントに複数のコンテナをホストできます。 | +| 権限 | {% data reusables.package_registry.public-or-private-packages %} パッケージはリポジトリの権限を継承するので、{% data variables.product.prodname_dotcom %}のロールとTeamを使い、各パッケージをインストールしたり公開したりできる人を制限できます。 リポジトリの読み取り権限を持っている人は、パッケージを依存関係としてプロジェクトにインストールでき、書き込み権限を持っている人は新しいパッケージのバージョンを公開できます。 | コンテナイメージごとに、他のユーザが持つアクセスレベルを選択できます。 コンテナイメージへのアクセス権限は、Organization およびリポジトリの権限とは別になります。 | 可視性 | {% data reusables.package_registry.public-or-private-packages %} | それぞれのコンテナイメージに可視性を設定できます。 プライベートコンテナイメージは、Organization 内でアクセス権を付与されたユーザおよび Team のみに表示されます。 パブリックコンテナは誰でも表示できます。 | 匿名アクセス | 該当なし | パブリックコンテナイメージには匿名でアクセスできます。 {% else %} -| | パッケージレジストリ | -| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| ホスト場所 | 1 つのリポジトリに複数のパッケージをホストできます。 | -| 権限 | {{ site.data.reusables.package_registry.public-or-private-packages }} パッケージはリポジトリの権限を継承するので、{{ site.data.variables.product.prodname_dotcom }}のロールとTeamを使い、各パッケージをインストールしたり公開したりできる人を制限できます。 リポジトリの読み取り権限を持っている人は、パッケージを依存関係としてプロジェクトにインストールでき、書き込み権限を持っている人は新しいパッケージのバージョンを公開できます。 | +| | パッケージレジストリ | +| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| ホスト場所 | 1 つのリポジトリに複数のパッケージをホストできます。 | +| 権限 | {% data reusables.package_registry.public-or-private-packages %} パッケージはリポジトリの権限を継承するので、{% data variables.product.prodname_dotcom %}のロールとTeamを使い、各パッケージをインストールしたり公開したりできる人を制限できます。 リポジトリの読み取り権限を持っている人は、パッケージを依存関係としてプロジェクトにインストールでき、書き込み権限を持っている人は新しいパッケージのバージョンを公開できます。 | | 可視性 | {% data reusables.package_registry.public-or-private-packages %} {% endif %} 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 94c908c42937..6bb455bb12bf 100644 --- a/translations/ja-JP/content/rest/overview/other-authentication-methods.md +++ b/translations/ja-JP/content/rest/overview/other-authentication-methods.md @@ -37,12 +37,22 @@ $ curl -u username:token {% data variables.product.api_url_pre このアプローチは、ツールが Basic 認証のみをサポートしているが、OAuth アクセストークンのセキュリティ機能を利用したい場合に役立ちます。 -{% if enterpriseServerVersions contains currentVersion %} #### ユーザ名とパスワードを使用する -{% data reusables.apps.deprecating_password_auth %} +{% if currentVersion == "free-pro-team@latest" %} + +{% 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 %} -{% data variables.product.product_name %} API で Basic 認証を使用するには、アカウントに関連付けられているユーザ名とパスワードを送信します。 +{% 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. たとえば、[cURL][curl] を介して API にアクセスしている場合、`` を {% data variables.product.product_name %} のユーザ名に置き換えると、次のコマンドで認証されます。 （cURL からパスワードの入力を求められます。） @@ -88,14 +98,13 @@ $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ### 2 要素認証を使用する -{% data reusables.apps.deprecating_password_auth %} - -2 要素認証を有効にしている場合、REST API の_ほとんど_のエンドポイントの [Basic 認証](#basic-authentication)では、ユーザ名とパスワードの代わりに個人アクセストークンまたは OAuth トークンを使用する必要があります。 - -You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}with [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %} or use the "[Create a new authorization][create-access]" endpoint in the OAuth Authorizations API to generate a new OAuth token. 詳しい情報については、「[コマンドラインの個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)」を参照してください。 次に、これらのトークンを使って、GitHub API で [OAuth トークンを使用して認証][oauth-auth]します。 ユーザ名とパスワードで認証する必要があるのは、OAuth トークンを作成するとき、または OAuth Authorizations API を使用するときだけです。 +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 %}. 詳しい情報については、「[コマンドラインの個人アクセストークンを作成する](/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 %} #### 2 要素認証で OAuth Authorizations API を使用する OAuth Authorizations API を呼び出す場合、Basic 認証では、トークンの代わりにワンタイムパスワード（OTP）とユーザ名とパスワードを使用する必要があります。 OAuth Authorizations API で認証しようとすると、サーバは `401 Unauthorized` とこれらのヘッダの 1 つで応答し、2 要素認証コードが必要であることを通知します。 @@ -114,7 +123,6 @@ $ curl --request POST \ ``` {% endif %} -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization [curl]: http://curl.haxx.se/ [oauth-auth]: /v3/#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line 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 9bcbc212df3d..8876a806c8ac 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 @@ -135,9 +135,9 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar API は、無効な認証情報を含むリクエストを短期間に複数回検出すると、`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" @@ -165,19 +165,10 @@ $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product. ルートエンドポイントに `GET` リクエストを発行して、REST API がサポートするすべてのエンドポイントカテゴリを取得できます。 ```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 %} - -{% note %} - -**注釈:** {% data variables.product.prodname_ghe_server %} では、[他のすべてのエンドポイントと同様に](/v3/enterprise-admin/#endpoint-urls)、ユーザ名とパスワードを渡す必要があります。 - -{% endnote %} - -{% endif %} - ### GraphQL グローバルノード ID REST API を介して `node_id` を検索し、それらを GraphQL 操作で使用する方法について詳しくは、「[グローバルノード ID を使用する](/v4/guides/using-global-node-ids)」のガイドを参照してください。 diff --git a/translations/ja-JP/content/rest/overview/troubleshooting.md b/translations/ja-JP/content/rest/overview/troubleshooting.md index 6bf8359d14b3..8661577e8e04 100644 --- a/translations/ja-JP/content/rest/overview/troubleshooting.md +++ b/translations/ja-JP/content/rest/overview/troubleshooting.md @@ -13,16 +13,53 @@ versions: API で不可解な問題が発生した場合、発生したと思われる問題の解決策をこちらの一覧から確認できます。 -### 存在しているリポジトリで `404` エラーが発生するのはなぜですか？ +### `404` error for an existing repository 通常、クライアントが正しく認証されていない場合、`404` エラーが送信されます。 このような場合、`403 Forbidden` が表示されるはずであると考えるかもしれません。 しかし、プライベートリポジトリに関する_いずれの_情報も提供されないため、API は代わりに `404` エラーを返します。 トラブルシューティングを行うには、[正しく認証されていること](/guides/getting-started/)、[OAuth アクセストークンに必要なスコープがあること](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)、そして[サードパーティアプリケーションの制限][oap-guide]によってアクセスがブロックされていないことを確認してください。 -### すべての結果が表示されないのはなぜですか？ +### Not all results returned リソース（_例:_ ユーザ、Issue _など_）のリストにアクセスするほとんどの API 呼び出しは、ページネーションをサポートしています。 リクエストをして、すべての結果を受け取っていない場合は、おそらく最初のページしか表示されていません。 より多くの結果を受け取るには、残りのページをリクエストする必要があります。 ページネーション URL のフォーマットを推測*しない*ことが重要です。 すべての API 呼び出しで同じ構造が使用されるわけではありません。 代わりに、すべてのリクエストで送信される [Link Header](/v3/#pagination) からページネーション情報を抽出します。 +{% 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. 例: + +```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/ja-JP/content/rest/reference/interactions.md b/translations/ja-JP/content/rest/reference/interactions.md index f99aceb5e783..98c87db3d9ab 100644 --- a/translations/ja-JP/content/rest/reference/interactions.md +++ b/translations/ja-JP/content/rest/reference/interactions.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -リポジトリに対するインタラクションには、コミット、Issueのオープン、プルリクエストの作成があります。 インタラクションAPIを使用すると、オーナーまたは管理者アクセス権のあるユーザは特定のユーザによるパブリックリポジトリの操作を一時的に制限することができます。 +リポジトリに対するインタラクションには、コミット、Issueのオープン、プルリクエストの作成があります。 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 @@ versions: ## Organization -OrganizationのインタラクションAPIを使用すると、OrganizationのオーナーはOrganizationのパブリックリポジトリでコメント、Issueのオープン、プルリクエストの作成ができるユーザを一時的に制限することができます。 {% data reusables.interactions.interactions-detail %} {% 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: * Organizationの{% data reusables.interactions.existing-user-limit-definition %} * Organizationの{% data reusables.interactions.contributor-user-limit-definition %} * Organizationの{% data reusables.interactions.collaborator-user-limit-definition %} +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 %} ## Repository -リポジトリのインタラクションAPIを使用すると、オーナーまたは管理者アクセス権のあるユーザはパブリックリポジトリでコメント、Issueのオープン、プルリクエストの作成ができるユーザを一時的に制限することができます。 {% data reusables.interactions.interactions-detail %} {% 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 repository. * {% data reusables.interactions.contributor-user-limit-definition %} in the repository. * {% data reusables.interactions.collaborator-user-limit-definition %} in the repository. +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 %} + +## ユーザ + +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/ja-JP/content/rest/reference/oauth-authorizations.md b/translations/ja-JP/content/rest/reference/oauth-authorizations.md index 8851b842d021..b2fb71ddf67c 100644 --- a/translations/ja-JP/content/rest/reference/oauth-authorizations.md +++ b/translations/ja-JP/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 %} - この API を使用すると、OAuth アプリケーションから自分のアカウントへのアクセスを管理することができます。 この API にアクセスするには、ユーザ名とパスワードを使用する [Basic 認証](/rest/overview/other-authentication-methods#basic-authentication) が必要であり、トークンは使用できません。 自分または自分のユーザが 2 要素認証を有効にしている場合は、必ず [2 要素認証の使用方法](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)を理解していることを確認してください。 diff --git a/translations/ja-JP/content/rest/reference/search.md b/translations/ja-JP/content/rest/reference/search.md index dbc87c3ab4ae..0313b752ba40 100644 --- a/translations/ja-JP/content/rest/reference/search.md +++ b/translations/ja-JP/content/rest/reference/search.md @@ -31,13 +31,19 @@ Search API の各エンドポイントでは、{% data variables.product.product A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. 検索クエリの形式は次のとおりです。 ``` -q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N +SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N ``` たとえば、README ファイルに `GitHub` と `Octocat` という言葉が含まれている、`defunkt` が所有する_リポジトリ_をすべて検索する場合、_検索リポジトリ_エンドポイントに次のクエリを使用します。 ``` -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. 例: +```javascript +// JavaScript +const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` 使用可能な修飾子の完全な一覧、フォーマット、使用例については、「[GitHub での検索](/articles/searching-on-github/)」を参照してください。 特定の数量、日付に一致させたり、検索結果から除外したりするために演算子を使う方法の詳細については、「[検索構文を理解する](/articles/understanding-the-search-syntax/)」を参照してください。 diff --git a/translations/ja-JP/data/graphql/ghae/graphql_previews.ghae.yml b/translations/ja-JP/data/graphql/ghae/graphql_previews.ghae.yml index 5e5c02dc78e3..9354a47f0224 100644 --- a/translations/ja-JP/data/graphql/ghae/graphql_previews.ghae.yml +++ b/translations/ja-JP/data/graphql/ghae/graphql_previews.ghae.yml @@ -85,7 +85,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: ピン止めされたIssueのプレビュー description: このプレビューは、ピン止めされたIssueのサポートを追加します。 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 e37f1e71dfac..f90a51675b93 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 @@ -2,112 +2,112 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。" - reason: "`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。" + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: AssignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。" - reason: "`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。" + description: '`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。' + reason: '`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。" - reason: "`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。" + description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。' + reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: Sponsorship.maintainer - description: "`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。" - reason: "`Sponsorship.maintainer`は削除されます。" + description: '`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。' + reason: '`Sponsorship.maintainer`は削除されます。' date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators`は削除されます。代わりに`pendingCollaboratorInvitations`フィールドを使用してください。" + description: '`pendingCollaborators`は削除されます。代わりに`pendingCollaboratorInvitations`フィールドを使用してください。' reason: リポジトリの招待は、招待者だけではなくメールにも関連づけられるようになりました。 date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Issue.timeline - description: "`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: PullRequest.timeline - description: "`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN`は削除されます。" - reason: "`INVITEE_LOGIN` は有効なフィールド値ではなくなりました。リポジトリの招待は、招待者だけではなく、メールにも関連付けられるようになりました。" + description: '`INVITEE_LOGIN`は削除されます。' + reason: '`INVITEE_LOGIN` は有効なフィールド値ではなくなりました。リポジトリの招待は、招待者だけではなく、メールにも関連付けられるようになりました。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor`は削除されます。代わりに`Sponsorship.sponsorEntity`を使ってください。" - reason: "`Sponsorship.sponsor`は削除されます。" + description: '`sponsor`は削除されます。代わりに`Sponsorship.sponsorEntity`を使ってください。' + reason: '`Sponsorship.sponsor`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 diff --git a/translations/ja-JP/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml index 9381fcfe7997..45f38f5db6d6 100644 --- a/translations/ja-JP/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ja-JP/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml @@ -2,63 +2,63 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。" - reason: "`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。" + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: ContributionOrder.field - description: "`field`は削除されます。orderフィールドは1つだけしかサポートされません。" - reason: "`field`は削除されます。" + description: '`field`は削除されます。orderフィールドは1つだけしかサポートされません。' + reason: '`field`は削除されます。' date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Issue.timeline - description: "`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: PullRequest.timeline - description: "`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: AssignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: UnassignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 diff --git a/translations/ja-JP/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml index e74123b0e930..58eb89223aea 100644 --- a/translations/ja-JP/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ja-JP/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml @@ -2,560 +2,560 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。" - reason: "`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。" + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: ContributionOrder.field - description: "`field`は削除されます。orderフィールドは1つだけしかサポートされません。" - reason: "`field`は削除されます。" + description: '`field`は削除されます。orderフィールドは1つだけしかサポートされません。' + reason: '`field`は削除されます。' date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Issue.timeline - description: "`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: PullRequest.timeline - description: "`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: AssignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。" - reason: "`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。" + description: '`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。' + reason: '`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。" - reason: "`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。" + description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。' + reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: Organization.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.color - description: "`color`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`color`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`latestVersion`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.name - description: "`name`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`nameWithOwner`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`packageFileByGuid`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256`は削除されます。`Package`オブジェクトを使ってください。" + description: '`packageFileBySha256`は削除されます。`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`packageType`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`preReleaseVersions`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`registryPackageType`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.repository - description: "`repository`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`repository`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`statistics`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.tags - description: "`tags`は削除されます。`Package`オブジェクトを使ってください。" + description: '`tags`は削除されます。`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.topics - description: "`topics`は削除されます。`Package`オブジェクトを使ってください。" + description: '`topics`は削除されます。`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.version - description: "`version`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versionByPlatform`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versionBySha256`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versions - description: "`versions`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versions`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versionsByMetadatum`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。" + description: '`dependencyType`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageDependency.name - description: "`name`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageDependency.version - description: "`version`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`guid`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`md5`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`metadataUrl`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.name - description: "`name`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`packageVersion`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`sha1`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`sha256`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.size - description: "`size`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`size`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.url - description: "`url`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`url`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsThisMonth`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsThisWeek`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsThisYear`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsToday`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsTotalCount`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageTag.name - description: "`name`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageTag.version - description: "`version`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`dependencies`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`fileByName`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.files - description: "`files`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`files`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`installationCommand`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`manifest`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`platform`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`preRelease`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`readme`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`readmeHtml`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`registryPackage`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.release - description: "`release`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`release`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`sha256`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.size - description: "`size`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`size`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`statistics`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`summary`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`updatedAt`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.version - description: "`version`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`viewerCanEdit`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsThisMonth`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsThisWeek`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsThisYear`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsToday`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsTotalCount`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。" - reason: "`Sponsorship.maintainer`は削除されます。" + description: '`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。' + reason: '`Sponsorship.maintainer`は削除されます。' date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: antn - location: User.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 diff --git a/translations/ja-JP/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml index 25db060024ec..012ce7cf11cf 100644 --- a/translations/ja-JP/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ja-JP/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml @@ -2,568 +2,568 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。" - reason: "`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。" + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: ContributionOrder.field - description: "`field`は削除されます。orderフィールドは1つだけしかサポートされません。" - reason: "`field`は削除されます。" + description: '`field`は削除されます。orderフィールドは1つだけしかサポートされません。' + reason: '`field`は削除されます。' date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Organization.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。" + description: '`pinnedRepositories`は削除されます。代わりにProfileOwner.pinnedItemsを使ってください。' reason: pinnedRepositoriesは削除されます date: '2019-10-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: AssignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。" - reason: "`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。" + description: '`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。' + reason: '`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。" - reason: "`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。" + description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。' + reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: Organization.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.color - description: "`color`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`color`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`latestVersion`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.name - description: "`name`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`nameWithOwner`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`packageFileByGuid`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256`は削除されます。`Package`オブジェクトを使ってください。" + description: '`packageFileBySha256`は削除されます。`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`packageType`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`preReleaseVersions`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`registryPackageType`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.repository - description: "`repository`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`repository`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`statistics`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.tags - description: "`tags`は削除されます。`Package`オブジェクトを使ってください。" + description: '`tags`は削除されます。`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.topics - description: "`topics`は削除されます。`Package`オブジェクトを使ってください。" + description: '`topics`は削除されます。`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.version - description: "`version`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versionByPlatform`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versionBySha256`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versions - description: "`versions`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versions`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum`は削除されます。代わりに`Package`オブジェクトを使ってください。" + description: '`versionsByMetadatum`は削除されます。代わりに`Package`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。" + description: '`dependencyType`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageDependency.name - description: "`name`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageDependency.version - description: "`version`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`PackageDependency`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`guid`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`md5`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`metadataUrl`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.name - description: "`name`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`packageVersion`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`sha1`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`sha256`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.size - description: "`size`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`size`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageFile.url - description: "`url`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。" + description: '`url`は削除されます。代わりに`PackageFile`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsThisMonth`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsThisWeek`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsThisYear`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsToday`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。" + description: '`downloadsTotalCount`は削除されます。代わりに`PackageStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageTag.name - description: "`name`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。" + description: '`name`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageTag.version - description: "`version`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`PackageTag`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.deleted - description: "`deleted`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`deleted`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`dependencies`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`fileByName`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.files - description: "`files`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`files`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`installationCommand`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`manifest`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`platform`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`preRelease`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`readme`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`readmeHtml`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`registryPackage`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.release - description: "`release`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`release`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`sha256`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.size - description: "`size`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`size`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`statistics`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`summary`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`updatedAt`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.version - description: "`version`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`version`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。" + description: '`viewerCanEdit`は削除されます。代わりに`PackageVersion`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsThisMonth`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsThisWeek`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsThisYear`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsToday`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。" + description: '`downloadsTotalCount`は削除されます。代わりに`PackageVersionStatistics`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。" - reason: "`Sponsorship.maintainer`は削除されます。" + description: '`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。' + reason: '`Sponsorship.maintainer`は削除されます。' date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: antn - location: User.registryPackages - description: "`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。" + description: '`registryPackages`は削除されます。代わりに`PackageOwner`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。" + description: '`registryPackagesForQuery`は削除されます。代わりに`PackageSearch`オブジェクトを使ってください。' reason: GitHub Packagesのフィールドとオブジェクトの名前の変更。 date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: dinahshi - location: Issue.timeline - description: "`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: PullRequest.timeline - description: "`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea diff --git a/translations/ja-JP/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml index fa7d890391a2..b92211acfc18 100644 --- a/translations/ja-JP/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ja-JP/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml @@ -2,71 +2,71 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。" - reason: "`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。" + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: AssignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。" - reason: "`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。" + description: '`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。' + reason: '`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。" - reason: "`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。" + description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。' + reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: Sponsorship.maintainer - description: "`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。" - reason: "`Sponsorship.maintainer`は削除されます。" + description: '`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。' + reason: '`Sponsorship.maintainer`は削除されます。' date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators`は削除されます。代わりに`pendingCollaboratorInvitations`フィールドを使用してください。" + description: '`pendingCollaborators`は削除されます。代わりに`pendingCollaboratorInvitations`フィールドを使用してください。' reason: リポジトリの招待は、招待者だけではなくメールにも関連づけられるようになりました。 date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Issue.timeline - description: "`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: PullRequest.timeline - description: "`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea @@ -86,15 +86,15 @@ upcoming_changes: owner: oneill38 - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN`は削除されます。" - reason: "`INVITEE_LOGIN` は有効なフィールド値ではなくなりました。リポジトリの招待は、招待者だけではなく、メールにも関連付けられるようになりました。" + description: '`INVITEE_LOGIN`は削除されます。' + reason: '`INVITEE_LOGIN` は有効なフィールド値ではなくなりました。リポジトリの招待は、招待者だけではなく、メールにも関連付けられるようになりました。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor`は削除されます。代わりに`Sponsorship.sponsorEntity`を使ってください。" - reason: "`Sponsorship.sponsor`は削除されます。" + description: '`sponsor`は削除されます。代わりに`Sponsorship.sponsorEntity`を使ってください。' + reason: '`Sponsorship.sponsor`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: nholden @@ -107,21 +107,21 @@ upcoming_changes: owner: oneill38 - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 diff --git a/translations/ja-JP/data/graphql/graphql_previews.yml b/translations/ja-JP/data/graphql/graphql_previews.yml index b5e4e17871e9..b4e4560a89d5 100644 --- a/translations/ja-JP/data/graphql/graphql_previews.yml +++ b/translations/ja-JP/data/graphql/graphql_previews.yml @@ -102,7 +102,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: ピン止めされたIssueのプレビュー description: このプレビューは、ピン止めされたIssueのサポートを追加します。 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 3bd2d3df4d9f..95775c388bf6 100644 --- a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml @@ -2,119 +2,119 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。" - reason: "`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。" + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' date: '2019-04-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: AssignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。" - reason: "`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。" + description: '`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。' + reason: '`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。" - reason: "`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。" + description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。' + reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。' date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user`は削除されます。代わりに`assignee`フィールドを使ってください。" + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' reason: アサインされた人を、マネキンにできるようになりました。 date: '2020-01-01T00:00:00+00:00' criticality: 破壊的 owner: tambling - location: Query.sponsorsListing - description: "`sponsorsListing`は削除されます。代わりに `Sponsorable.sponsorsListing`を使ってください。" - reason: "`Query.sponsorsListing`は削除されます。" + description: '`sponsorsListing`は削除されます。代わりに `Sponsorable.sponsorsListing`を使ってください。' + reason: '`Query.sponsorsListing`は削除されます。' date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: antn - location: Sponsorship.maintainer - description: "`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。" - reason: "`Sponsorship.maintainer`は削除されます。" + description: '`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。' + reason: '`Sponsorship.maintainer`は削除されます。' date: '2020-04-01T00:00:00+00:00' criticality: 破壊的 owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators`は削除されます。代わりに`pendingCollaboratorInvitations`フィールドを使用してください。" + description: '`pendingCollaborators`は削除されます。代わりに`pendingCollaboratorInvitations`フィールドを使用してください。' reason: リポジトリの招待は、招待者だけではなくメールにも関連づけられるようになりました。 date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Issue.timeline - description: "`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: PullRequest.timeline - description: "`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。" - reason: "`timeline`は削除されます。" + description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN`は削除されます。" - reason: "`INVITEE_LOGIN` は有効なフィールド値ではなくなりました。リポジトリの招待は、招待者だけではなく、メールにも関連付けられるようになりました。" + description: '`INVITEE_LOGIN`は削除されます。' + reason: '`INVITEE_LOGIN` は有効なフィールド値ではなくなりました。リポジトリの招待は、招待者だけではなく、メールにも関連付けられるようになりました。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor`は削除されます。代わりに`Sponsorship.sponsorEntity`を使ってください。" - reason: "`Sponsorship.sponsor`は削除されます。" + description: '`sponsor`は削除されます。代わりに`Sponsorship.sponsorEntity`を使ってください。' + reason: '`Sponsorship.sponsor`は削除されます。' date: '2020-10-01T00:00:00+00:00' criticality: 破壊的 owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: 破壊的 diff --git a/translations/ja-JP/data/reusables/feature-preview/feature-preview-setting.md b/translations/ja-JP/data/reusables/feature-preview/feature-preview-setting.md new file mode 100644 index 000000000000..50e75eab0bd9 --- /dev/null +++ b/translations/ja-JP/data/reusables/feature-preview/feature-preview-setting.md @@ -0,0 +1 @@ +1. 任意のページの右上隅で、プロフィール画像をクリックし、続いて [**Feature preview（機能プレビュー）**] をクリックします。 ![[Feature preview] ボタン](/assets/images/help/settings/feature-preview-button.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/gated-features/secret-scanning.md b/translations/ja-JP/data/reusables/gated-features/secret-scanning.md new file mode 100644 index 000000000000..bd279034eee8 --- /dev/null +++ b/translations/ja-JP/data/reusables/gated-features/secret-scanning.md @@ -0,0 +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 %} diff --git a/translations/ja-JP/data/reusables/interactions/interactions-detail.md b/translations/ja-JP/data/reusables/interactions/interactions-detail.md index 9193cd04e704..187a3e73074d 100644 --- a/translations/ja-JP/data/reusables/interactions/interactions-detail.md +++ b/translations/ja-JP/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -When restrictions are enabled, only the specified group of {% data variables.product.product_name %} users will be able to participate in interactions. Restrictions expire 24 hours from the time they are set. +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. diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md b/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md index 03ca5504b82f..77cc289fcef6 100644 --- a/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md +++ b/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 現在のところ、{% data variables.product.prodname_github_container_registry %} がサポートしているのは Docker イメージフォーマットのみです。 ベータ期間中は、ストレージおよび帯域幅の制限はありません。 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/getting-started-with-github-container-registry/about-github-container-registry)」を参照してください。 +**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 During the beta, storage and bandwidth are free. 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)." {% endnote %} diff --git a/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md new file mode 100644 index 000000000000..b0cddc8bcb84 --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/secret-scanning/beta.md b/translations/ja-JP/data/reusables/secret-scanning/beta.md index 37ef8d5b7f2f..c968a25d6f56 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/beta.md +++ b/translations/ja-JP/data/reusables/secret-scanning/beta.md @@ -1,5 +1,5 @@ {% note %} -**ノート:** プライベートリポジトリのための{% data variables.product.prodname_secret_scanning_caps %}は現在ベータで、変更されることがあります。 ベータへのアクセスをリクエストするには、[待ちリストに参加](https://github.com/features/security/advanced-security/signup)してください。 +**ノート:** プライベートリポジトリのための{% data variables.product.prodname_secret_scanning_caps %}は現在ベータで、変更されることがあります。 {% endnote %} diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml index 0353edc0c27a..43750c86fe5e 100644 --- a/translations/ja-JP/data/ui.yml +++ b/translations/ja-JP/data/ui.yml @@ -4,9 +4,10 @@ header: contact: お問い合わせ notices: ghae_silent_launch: GitHub AE is currently under limited release. Please contact our Sales Team to find out more. + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。 localization_in_progress: こんにちは！このページは開発中か、まだ翻訳中です。最新の正しい情報を得るには、英語のドキュメンテーションにアクセスしてください。 - product_in_progress: こんにちは！このページは活発に開発中です。最新の正しい情報を得るには、開発者のドキュメンテーションにアクセスしてください。 + early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' search: need_help: お困りですか？ placeholder: トピックや製品などの検索 @@ -19,7 +20,7 @@ toc: guides: ガイド whats_new: 更新情報 pages: - article_version: "記事のバージョン：" + article_version: '記事のバージョン：' miniToc: 'ここには以下の内容があります:' errors: oops: 問題が発生しています。 diff --git a/translations/ja-JP/data/variables/action_code_examples.yml b/translations/ja-JP/data/variables/action_code_examples.yml new file mode 100644 index 000000000000..24571dbda3a1 --- /dev/null +++ b/translations/ja-JP/data/variables/action_code_examples.yml @@ -0,0 +1,149 @@ +--- +- + title: Starter workflows + description: Workflow files for helping people get started with GitHub Actions + languages: TypeScript + href: actions/starter-workflows + tags: + - official + - ワークフロー +- + title: Example services + description: Example workflows using service containers + languages: JavaScript + href: actions/example-services + tags: + - service containers +- + title: Declaratively setup GitHub Labels + description: GitHub Action to declaratively setup labels across repos + languages: JavaScript + href: lannonbr/issue-label-manager-action + tags: + - issues + - labels +- + title: Declaratively sync GitHub labels + description: GitHub Action to sync GitHub labels in the declarative way + languages: 'Go, Dockerfile' + href: micnncim/action-label-syncer + tags: + - issues + - labels +- + title: Add releases to GitHub + description: Publish Github releases in an action + languages: 'Dockerfile, Shell' + href: elgohr/Github-Release-Action + tags: + - releases + - publishing +- + title: Publish a docker image to Dockerhub + description: A Github Action used to build and publish Docker images + languages: 'Dockerfile, Shell' + href: elgohr/Publish-Docker-Github-Action + tags: + - docker + - publishing + - ビルド +- + title: Create an issue using content from a file + description: A GitHub action to create an issue using content from a file + languages: 'JavaScript, Python' + href: peter-evans/create-issue-from-file + tags: + - issues +- + title: Publish GitHub Releases with Assets + description: GitHub Action for creating GitHub Releases + languages: 'TypeScript, Shell, JavaScript' + href: softprops/action-gh-release + tags: + - releases + - publishing +- + title: GitHub Project Automation+ + description: Automate GitHub Project cards with any webhook event. + languages: JavaScript + href: alex-page/github-project-automation-plus + tags: + - projects + - automation + - issues + - プルリクエスト +- + title: Run GitHub Actions Locally with a web interface + description: Runs GitHub Actions workflows locally (local) + languages: 'JavaScript, HTML, Dockerfile, CSS' + href: phishy/wflow + tags: + - local-development + - devops + - docker +- + title: Run your GitHub Actions locally + description: Run GitHub Actions Locally in Terminal + languages: 'Go, Shell' + href: nektos/act + tags: + - local-development + - devops + - docker +- + title: Build and Publish Android debug APK + description: Build and release debug APK from your Android project + languages: 'Shell, Dockerfile' + href: ShaunLWM/action-release-debugapk + tags: + - android + - ビルド +- + title: Generate sequential build numbers for GitHub Actions + description: GitHub action for generating sequential build numbers. + languages: JavaScript + href: einaregilsson/build-number + tags: + - ビルド + - automation +- + title: GitHub actions to push back to repository + description: Push Git changes to GitHub repository without authentication difficulties + languages: 'JavaScript, Shell' + href: ad-m/github-push-action + tags: + - publishing +- + title: Generate release notes based on your events + description: Action to auto generate a release note based on your events + languages: 'Shell, Dockerfile' + href: Decathlon/release-notes-generator-action + tags: + - releases + - publishing +- + title: Create a GitHub wiki page based on the provided markdown file + description: Create a GitHub wiki page based on the provided markdown file + languages: 'Shell, Dockerfile' + href: Decathlon/wiki-page-creator-action + tags: + - wiki + - publishing +- + title: 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: + - projects + - issues + - labels +- + title: Add Label to your Pull Requests based on the author team name + description: Github action to label your pull requests based on the author name + languages: 'TypeScript, JavaScript' + href: JulienKode/team-labeler-action + tags: + - プルリクエスト + - labels diff --git a/translations/ja-JP/data/variables/contact.yml b/translations/ja-JP/data/variables/contact.yml index 2de59c931377..4c26836d8e5d 100644 --- a/translations/ja-JP/data/variables/contact.yml +++ b/translations/ja-JP/data/variables/contact.yml @@ -10,7 +10,7 @@ contact_dmca: >- {% if currentVersion == "free-pro-team@latest" %}[Copyright claims form](https://github.com/contact/dmca){% endif %} contact_privacy: >- {% if currentVersion == "free-pro-team@latest" %}[Privacy contact form](https://github.com/contact/privacy){% endif %} -contact_enterprise_sales: '[GitHubの営業チーム](https://enterprise.github.com/contact)' +contact_enterprise_sales: "[GitHubの営業チーム](https://enterprise.github.com/contact)" contact_feedback_actions: '[GitHub Actionsのフィードバックフォーム](https://support.github.com/contact/feedback?contact[category]=actions)' #The team that provides Standard Support enterprise_support: 'GitHub Enterprise Support' diff --git a/translations/ja-JP/data/variables/release_candidate.yml b/translations/ja-JP/data/variables/release_candidate.yml new file mode 100644 index 000000000000..ec65ef6f9445 --- /dev/null +++ b/translations/ja-JP/data/variables/release_candidate.yml @@ -0,0 +1,2 @@ +--- +version: '' 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 8e985f521e00..13a946fb3897 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 @@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - potatoqualitee --- {% data reusables.actions.enterprise-beta %} 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 new file mode 100644 index 000000000000..44df05f98f01 --- /dev/null +++ b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md @@ -0,0 +1,318 @@ +--- +title: Building and testing Ruby +intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introduction + +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. + +### 빌드전 요구 사양 + +We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. For more information, see: + +- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions) +- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) + +### Starting with the Ruby workflow template + +{% 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). + +To get started quickly, add the template to the `.github/workflows` directory of your repository. + +{% raw %} +```yaml +name: Ruby + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: 2.6 + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Specifying the Ruby version + +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). + +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. + +The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 # Not needed with a .ruby-version file +- run: bundle install +- run: bundle exec rake +``` +{% 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. + +### Testing with multiple versions of 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. + +{% raw %} +```yaml +strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] +``` +{% 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." + +The full updated workflow with a matrix strategy could look like this: + +{% raw %} +```yaml +name: Ruby CI + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby ${{ matrix.ruby-version }} + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: ${{ matrix.ruby-version }} + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Installing dependencies with 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. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 +- run: bundle install +``` +{% endraw %} + +#### Caching dependencies + +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 +steps: +- uses: ruby/setup-ruby@v1 + with: + bundler-cache: true +``` +{% 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. + +**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)." + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + ${{ runner.os }}-gems- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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: + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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. + +{% raw %} +```yaml +name: Matrix Testing + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + runs-on: ${{ matrix.os }}-latest + strategy: + fail-fast: false + matrix: + os: [ubuntu, macos] + ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head] + continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }} + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: ${{ matrix.ruby }} + - run: bundle install + - run: bundle exec rake +``` +{% 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. + +{% raw %} +```yaml +name: Linting + +on: [push] + +jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + - name: Rubocop + run: rubocop +``` +{% endraw %} + +### Publishing Gems + +You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. + +You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. + +{% raw %} +```yaml + +name: Ruby Gem + +on: + # Manually publish + workflow_dispatch: + # Alternatively, publish whenever changes are merged to the default branch. + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + build: + name: Build + Publish + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby 2.6 + uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + + - name: Publish to GPR + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem + env: + GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}" + OWNER: ${{ github.repository_owner }} + + - name: Publish to RubyGems + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push *.gem + env: + GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" +``` +{% endraw %} + diff --git a/translations/ko-KR/content/actions/guides/index.md b/translations/ko-KR/content/actions/guides/index.md index 4b0c15412878..64a7ff00c5a1 100644 --- a/translations/ko-KR/content/actions/guides/index.md +++ b/translations/ko-KR/content/actions/guides/index.md @@ -31,6 +31,7 @@ You can use {% data variables.product.prodname_actions %} to create custom conti {% 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/ko-KR/content/actions/guides/publishing-nodejs-packages.md b/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md index 3a402d35a1a2..89cb5d334de2 100644 --- a/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ko-KR/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/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index deaf7f498a01..75f673d9791b 100644 --- a/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ko-KR/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/ko-KR/content/actions/index.md b/translations/ko-KR/content/actions/index.md index 0f0516da0816..a52b17016f01 100644 --- a/translations/ko-KR/content/actions/index.md +++ b/translations/ko-KR/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 - date: '2020-10-16' - href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ + title: Removing set-env and add-path commands on November 16 + date: '2020-11-09' + href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - 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: Ubuntu-latest workflows will use 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: 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: MacOS Big Sur Preview + date: '2020-10-29' + href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview - - 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 + title: Self-Hosted Runner Group Access Changes + date: '2020-10-16' + href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ 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 %}
-

More guides

+

Code examples

+ +
+ +
-
- -
-

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 -
- -
+ {% render 'code-example-card' for actionsCodeExamples as example %}
- Show all guides {% octicon "arrow-right" %} + + +
+
{% octicon "search" width="24" %}
+

Sorry, there is no result for

+

It looks like we don't have an example that fits your filter.
Try another filter or add your code example

+ Learn how to add a code example {% octicon "arrow-right" %} +
+{% endif %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md index f326710453bb..6131f65296c0 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -42,7 +42,7 @@ A job is a set of steps that execute on the same runner. By default, a workflow #### Steps -A step is an individual task that can run commands (known as _actions_). Each step in a job executes on the same runner, allowing the actions in that job to share data with each other. +A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. Each step in a job executes on the same runner, allowing the actions in that job to share data with each other. #### Actions @@ -50,7 +50,7 @@ _Actions_ are standalone commands that are combined into _steps_ to create a _jo #### Runners -A runner is a server that has the {% data variables.product.prodname_actions %} runner application installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment. +A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS. For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)." @@ -197,7 +197,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s #### Visualizing the workflow file -In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action. Steps 1 and 2 use prebuilt community actions. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." +In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell command. Steps 1 and 2 use prebuilt community actions. Steps 3 and 4 run shell commands directly on the runner. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." ![Workflow overview](/assets/images/help/images/overview-actions-event.png) diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md index 14b5d9226820..5c46ed4da575 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ko-KR/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/ko-KR/content/actions/quickstart.md b/translations/ko-KR/content/actions/quickstart.md index 32ca2a56db85..45613e542766 100644 --- a/translations/ko-KR/content/actions/quickstart.md +++ b/translations/ko-KR/content/actions/quickstart.md @@ -73,3 +73,69 @@ The super-linter workflow you just added runs any time code is pushed to your re - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial - "[Guides](/actions/guides)" for specific uses cases and examples - [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action + + 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 ba576ca204af..b73aa98a496a 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 @@ -327,6 +327,7 @@ The `issue_comment` event occurs for comments on both issues and pull requests. 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 @@ -349,6 +350,7 @@ jobs: - run: | echo "Comment on issue #${{ github.event.issue.number }}" ``` +{% endraw %} #### `issues` diff --git a/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md index 88021e0a57ae..f220d10e258c 100644 --- a/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md @@ -31,7 +31,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl {% data variables.product.prodname_dotcom %} hosts Linux and Windows runners on Standard_DS2_v2 virtual machines in Microsoft Azure with the {% data variables.product.prodname_actions %} runner application installed. The {% data variables.product.prodname_dotcom %}-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation. -{% data variables.product.prodname_dotcom %} uses [MacStadium](https://www.macstadium.com/) to host the macOS runners. +{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud. #### Administrative privileges of {% data variables.product.prodname_dotcom %}-hosted runners 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 74c04380da0b..636aa0364e54 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 @@ -446,7 +446,7 @@ 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`** @@ -492,7 +492,7 @@ 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 @@ -659,7 +659,7 @@ For built-in shell keywords, we provide the following defaults that are executed - `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. + - `cmd.exe` will exit with the error level of the last program it executed, and it will 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. #### **`jobs..steps.with`** @@ -718,7 +718,7 @@ 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. +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. #### **`jobs..steps.env`** diff --git a/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 51d9a7d1c95c..e6360decf707 100644 --- a/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -28,16 +28,7 @@ To configure authentication and user provisioning for {% data variables.product. {% 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. - - | Value in Azure AD | Value from {% data variables.product.prodname_ghe_managed %} - |:---------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Identifier (Entity ID) | `https://YOUR-GITHUB-AE-HOSTNAME - - - Reply URL - https://YOUR-GITHUB-AE-HOSTNAME/saml/consume` | - | Sign on URL | https://YOUR-GITHUB-AE-HOSTNAME/sso | +1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. 1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. diff --git a/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md index 30201c8a735b..5ae4ba69e8f9 100644 --- a/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md @@ -38,6 +38,12 @@ After a user successfully authenticates on your IdP, the user's SAML session for {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} +The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | More information | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs | + 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. | Value | Other names | 설명 | 예시 | diff --git a/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index c920a3a5b1db..030a54716236 100644 --- a/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -62,7 +62,15 @@ You must have administrative access on your IdP to configure the application for {% 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. Click **Save**. ![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. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. + + The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | More information | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs | + + The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}. | Value | Other names | 설명 | 예시 | |:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- | diff --git a/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md b/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md index 647d5388669d..2a079f56ffda 100644 --- a/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md +++ b/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md @@ -11,7 +11,7 @@ versions: ### Set up an external `collectd` server -If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.product.product_location %}. Your `collectd` server must by running `collectd` version 5.x or higher. +If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.product.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher. 1. Log into your `collectd` server. 2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf` diff --git a/translations/ko-KR/content/admin/packages/configuring-third-party-storage-for-packages.md b/translations/ko-KR/content/admin/packages/configuring-third-party-storage-for-packages.md index 523834c7e440..2a7e32e8c90d 100644 --- a/translations/ko-KR/content/admin/packages/configuring-third-party-storage-for-packages.md +++ b/translations/ko-KR/content/admin/packages/configuring-third-party-storage-for-packages.md @@ -21,7 +21,10 @@ For the best experience, we recommend using a dedicated bucket for {% data varia {% warning %} -**Warning:** Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. +**Warnings:** +- 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. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} diff --git a/translations/ko-KR/content/admin/packages/index.md b/translations/ko-KR/content/admin/packages/index.md index d677721898a2..2c1a7b4d0c1f 100644 --- a/translations/ko-KR/content/admin/packages/index.md +++ b/translations/ko-KR/content/admin/packages/index.md @@ -1,6 +1,5 @@ --- title: Managing GitHub Packages for your enterprise -shortTitle: GitHub Packages intro: 'You can enable {% data variables.product.prodname_registry %} for your enterprise and manage {% data variables.product.prodname_registry %} settings and allowed packaged types.' redirect_from: - /enterprise/admin/packages diff --git a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md index 5c4c09ad2789..5a1b29c18f25 100644 --- a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md +++ b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -36,17 +36,23 @@ As you make changes to files in your text editor and save them locally, you will #### Creating a partial commit -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. The rest of your changes will remain intact, so that you can make additional modifications and commits. This allows you to make separate, meaningful commits, such as keeping line break changes in a commit separate from code or prose changes. +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. The rest of your changes will remain intact, so that you can make additional modifications and commits. This allows you to make separate, meaningful commits, such as keeping line break changes in a commit separate from code or prose changes. -When you review the diff of the file, the lines that will be included in the commit are highlighted in blue. To exclude the change, click the changed line so the blue disappears. +{% note %} + +**Note:** Split diff displays are currently in beta and subject to change. + +{% endnote %} -![Unselected lines in a file](/assets/images/help/desktop/partial-commit.png) +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. ![Unselected lines in a file](/assets/images/help/desktop/partial-commit.png) -#### Discarding changes +### 3. Discarding changes +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. -You can discard all the uncommitted changes in one file, a range of files, or discard all changes in all files since the last commit. +Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied. -{% mac %} +#### Discarding changes in one or more files {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -54,30 +60,25 @@ You can discard all the uncommitted changes in one file, a range of files, or di {% data reusables.desktop.confirm-discard-files %} ![Discard Changes button in the confirmation dialog](/assets/images/help/desktop/discard-changes-confirm-mac.png) -{% tip %} +#### Discarding changes in one or more lines +You can discard one or more changed lines that are uncommitted. -**Tip:** The changes you discarded are saved in a dated file in the Trash and you can recover them until the Trash is emptied. - -{% endtip %} +{% note %} -{% endmac %} +**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. -{% windows %} +{% endnote %} -{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %} - ![Discard Changes option in context menu](/assets/images/help/desktop/discard-changes-win.png) -{% data reusables.desktop.confirm-discard-files %} - ![Discard Changes button in the confirmation dialog](/assets/images/help/desktop/discard-changes-confirm-win.png) +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**. -{% tip %} + ![Discard single line in the confirmation dialog](/assets/images/help/desktop/discard-single-line.png) -**Tip:** The changes you discarded are saved in a file in the Recycle Bin and you can recover them until it is emptied. +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**. -{% endtip %} + ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) -{% endwindows %} -### 3. Write a commit message and push your changes +### 4. Write a commit message and push your changes Once you're satisfied with the changes you've chosen to include in your commit, write your commit message and push your changes. If you've collaborated on a commit, you can also attribute a commit to more than one author. diff --git a/translations/ko-KR/content/developers/apps/rate-limits-for-github-apps.md b/translations/ko-KR/content/developers/apps/rate-limits-for-github-apps.md index e25d374ee18c..31607e2e14bb 100644 --- a/translations/ko-KR/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/ko-KR/content/developers/apps/rate-limits-for-github-apps.md @@ -34,8 +34,6 @@ Different server-to-server request rate limits apply to {% data variables.produc ### User-to-server requests -{% data reusables.apps.deprecating_password_auth %} - {% 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. {% if currentVersion == "free-pro-team@latest" %} @@ -52,7 +50,7 @@ User-to-server requests are rate limited at 5,000 requests per hour and per auth #### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits -When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. +When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. {% endif %} diff --git a/translations/ko-KR/content/developers/overview/managing-deploy-keys.md b/translations/ko-KR/content/developers/overview/managing-deploy-keys.md index dad75176db2c..e6ed78de8f0c 100644 --- a/translations/ko-KR/content/developers/overview/managing-deploy-keys.md +++ b/translations/ko-KR/content/developers/overview/managing-deploy-keys.md @@ -82,6 +82,32 @@ See [our guide on Git automation with tokens][git-automation]. 7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. 8. Click **Add key**. +##### Using multiple repositories on one server + +If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. + +In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. 예시: + +```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 %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias. +* `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias. +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias. + +You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. 예시: + +```bash +$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git +``` + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/ko-KR/content/developers/overview/secret-scanning.md b/translations/ko-KR/content/developers/overview/secret-scanning.md index b55c982bfcac..bf0a60000a02 100644 --- a/translations/ko-KR/content/developers/overview/secret-scanning.md +++ b/translations/ko-KR/content/developers/overview/secret-scanning.md @@ -79,7 +79,7 @@ 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. +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. * **Token**: The value of the secret match. * **Type**: The unique name you provided to identify your regular expression. diff --git a/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md b/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md index 4b8b56f5e9f3..12e54afd4af9 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md @@ -1,6 +1,7 @@ --- title: About secret scanning intro: '{% data variables.product.product_name %} scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.' +product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /github/administering-a-repository/about-token-scanning - /articles/about-token-scanning diff --git a/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md b/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md index 5af15588d24b..d2357941d1fd 100644 --- a/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md +++ b/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md @@ -1,6 +1,7 @@ --- title: Configuring secret scanning for private repositories intro: 'You can configure how {% data variables.product.product_name %} scans your private repositories for secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'People with admin permissions to a private repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' versions: free-pro-team: '*' diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/ko-KR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index 10f410a5d36e..9127ad2090f0 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -1,6 +1,7 @@ --- title: Managing alerts from secret scanning intro: You can view and close alerts for secrets checked in to your repository. +product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' --- diff --git a/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index e69def6dae36..02095f93753c 100644 --- a/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -31,7 +31,7 @@ For more information, see "[Setting your commit email address](/articles/setting ### Creating co-authored commits using {% 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). +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#4-write-a-commit-message-and-push-your-changes)" and [{% 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) @@ -74,4 +74,4 @@ The new commit and message will appear on {% data variables.product.product_loca - "[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 +- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md index 5e5d0ddf422f..ddbcfdbea51a 100644 --- a/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- title: Using Codespaces in Visual Studio Code -intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_vs_codespaces %} extension with your account on {% data variables.product.product_name %}.' +intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% 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: ### 빌드전 요구 사양 -Before you can develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must configure the {% data variables.product.prodname_vs_codespaces %} extension to connect to your {% data variables.product.product_name %} account. +To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. -1. Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. -2. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Extensions icon. ![The Extensions icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-extensions-icon-vscode.png) -3. Below {% data variables.product.prodname_vs_codespaces %}, click the Manage icon, then click **Extension Settings**. ![The Extension Settings option](/assets/images/help/codespaces/select-extension-settings.png) -4. Use the Codespaces: Account Provider drop-down menu, and click **{% data variables.product.prodname_dotcom %}**. ![Setting the Account Provider to {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/select-account-provider-vscode.png) +1. Use the + +{% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -6. If {% data variables.product.prodname_codespaces %} is not already selected in the header, click **{% data variables.product.prodname_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) -7. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -8. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -9. Sign in to {% data variables.product.product_name %} to approve the extension. +2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) +3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) +4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +5. Sign in to {% data variables.product.product_name %} to approve the extension. ### Creating a codespace in {% data variables.product.prodname_vscode %} @@ -31,8 +30,8 @@ After you connect your {% data variables.product.product_name %} account to the {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) 3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop in. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) - +4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) +5. Click the instance type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) ### Opening a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index b16824a21d4a..35ca124ad3cf 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -94,7 +94,7 @@ If the `autobuild` command can't build your code, you can run the build steps yo By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command. -Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-an-alert)." +Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-the-alerts-for-a-repository)." ### {% data variables.product.prodname_codeql_runner %} command reference diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index e7c8e8302082..da95b53eef48 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -58,7 +58,7 @@ After enabling {% data variables.product.prodname_code_scanning %} for your repo 1. Review the logging output from the actions in this workflow as they run. -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. 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-the-alerts-for-a-repository)." {% note %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 1128480098b3..74dc2ffaf88e 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -1,7 +1,7 @@ --- title: Managing code scanning alerts for your repository shortTitle: Managing alerts -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: 'From the security view, 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.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: @@ -30,9 +30,11 @@ If you enable {% data variables.product.prodname_code_scanning %} using {% data When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. -### Viewing an alert +### Viewing the alerts for a repository -Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} alerts on pull requests. However, you need write permission to view a summary of alerts for repository on the **Security** tab. By default, alerts are shown for the default branch. +Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. 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)." + +You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -45,7 +47,7 @@ Anyone with read permission for a repository can see {% data variables.product.p Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[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)." -If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing an alert](#viewing-an-alert)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. +If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index 9b373b7a2102..721b4060208d 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -3,7 +3,7 @@ title: Triaging code scanning alerts in pull requests shortTitle: Triaging alerts in pull requests intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.' 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: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -31,9 +31,9 @@ When you look at the **Files changed** tab for a pull request, you see annotatio ![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png) -Some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." +If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." -For more information about an alert, click **Show more details** on the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. +To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code. @@ -41,11 +41,11 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_ ### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request -Anyone with write permission for a repository can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on a pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. +Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. {% if currentVersion == "enterprise-server@2.22" %} -If you don't think that an alert needs to be fixed, you can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. +If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. {% data reusables.code-scanning.false-positive-fix-codeql %} @@ -63,4 +63,4 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler For more information about dismissing alerts, 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#dismissing-or-deleting-alerts)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index 120f8640c163..43c891b98ffa 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -66,7 +66,7 @@ For more information, see the workflow extract in "[Automatic build for a compil * Building using a distributed build system external to GitHub Actions, using a daemon process. * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. - For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. + For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. For example, the following configuration for C# will pass the flag during the first build step. diff --git a/translations/ko-KR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md b/translations/ko-KR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md index a092487424cb..e2d7ad987b32 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md +++ b/translations/ko-KR/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md @@ -21,5 +21,5 @@ versions: You can see a list of features that are available in beta and a brief description for each feature. Each feature includes a link to give feedback. -1. In the upper-right corner of any page, click your profile photo, then click **Feature preview**. ![Feature preview button](/assets/images/help/settings/feature-preview-button.png) +{% data reusables.feature-preview.feature-preview-setting %} 2. Optionally, to the right of a feature, click **Enable** or **Disable**. ![Enable button in feature preview](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md index 105edf9cf365..ae996656b559 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md @@ -1,6 +1,7 @@ --- title: Managing secret scanning for your organization intro: 'You can control which repositories in your organization {% data variables.product.product_name %} will scan for secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'Organization owners can manage {% data variables.product.prodname_secret_scanning %} for repositories in the organization.' versions: free-pro-team: '*' 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 a461b3642e08..bc5cf4609ea2 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 @@ -43,74 +43,77 @@ In addition to managing organization-level settings, organization owners have ad ### Repository access for each permission level -| Repository action | Read | 심사 | Write | Maintain | Admin | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:--------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:| -| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | -| Open issues | **X** | **X** | **X** | **X** | **X** | -| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | -| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | -| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | -| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | -| View published releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| 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** | -| 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** | -| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | -| [Hide anyone's comments](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/articles/locking-conversations) | | | **X** | **X** | **X** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Mark a draft pull request as ready for review](/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" %} -| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| Create and edit releases | | | **X** | **X** | **X** | -| View draft releases | | | **X** | **X** | **X** | -| Edit a repository's description | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Limit [interactions in a repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | -| Add a repository to a team (see "[Managing team access to an organization repository](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | -| Change a repository's settings | | | | | **X** | -| Manage team and collaborator access to the repository | | | | | **X** | -| Edit the repository's default branch | | | | | **X** | -| Manage webhooks and deploy keys | | | | | **X** |{% 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 | | | | | **X** | -| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** | -| [Manage data use settings for your private repository](/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" %}| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} -| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | +| Repository action | Read | 심사 | Write | Maintain | Admin | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | +| Open issues | **X** | **X** | **X** | **X** | **X** | +| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | +| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | +| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | +| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | +| View published releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 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** | +| 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** | +| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | +| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | +| [Hide anyone's comments](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | +| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Mark a draft pull request as ready for review](/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" %} +| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | +| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | +| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| Create and edit releases | | | **X** | **X** | **X** | +| View draft releases | | | **X** | **X** | **X** | +| Edit a repository's description | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Enable wikis and restrict wiki editors | | | | **X** | **X** | +| Enable project boards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | +| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Limit [interactions in a repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} +| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | +| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | +| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | +| Add a repository to a team (see "[Managing team access to an organization repository](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | +| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | +| Change a repository's settings | | | | | **X** | +| Manage team and collaborator access to the repository | | | | | **X** | +| Edit the repository's default branch | | | | | **X** | +| Manage webhooks and deploy keys | | | | | **X** |{% 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 | | | | | **X** | +| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** | +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %} +| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index 5713a073bc26..cf50de80748b 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -3,6 +3,7 @@ title: Managing licenses for Visual Studio subscription with GitHub Enterprise intro: 'You can manage {% data variables.product.prodname_enterprise %} licensing for {% 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 diff --git a/translations/ko-KR/content/github/site-policy/github-acceptable-use-policies.md b/translations/ko-KR/content/github/site-policy/github-acceptable-use-policies.md index a9ce81a8bb9d..8ec0fdec0354 100644 --- a/translations/ko-KR/content/github/site-policy/github-acceptable-use-policies.md +++ b/translations/ko-KR/content/github/site-policy/github-acceptable-use-policies.md @@ -37,6 +37,8 @@ While using the Service, under no circumstances will you: - harass, abuse, threaten, or incite violence towards any individual or group, including our employees, officers, and agents, or other users; +- post off-topic content, or interact with platform features, in a way that significantly or repeatedly disrupts the experience of other users; + - use our servers for any form of excessive automated bulk activity (for example, spamming or cryptocurrency mining), to place undue burden on our servers through automated means, or to relay any form of unsolicited advertising or solicitation through our servers, such as get-rich-quick schemes; - use our servers to disrupt or to attempt to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network (unless authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); @@ -48,15 +50,17 @@ While using the Service, under no circumstances will you: ### 4. Services Usage Limits You will not reproduce, duplicate, copy, sell, resell or exploit any portion of the Service, use of the Service, or access to the Service without our express written permission. -### 5. Scraping and API Usage Restrictions -Scraping refers to extracting data from our Service via an automated process, such as a bot or webcrawler. It does not refer to the collection of information through our API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. You may scrape the website for the following reasons: +### 5. Information Usage Restrictions +You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise: + +- Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are [open access](https://en.wikipedia.org/wiki/Open_access). +- Archivists may use public information from the Service for archival purposes. -- Researchers may scrape public, non-personal information from the Service for research purposes, only if any publications resulting from that research are open access. -- Archivists may scrape the Service for public data for archival purposes. +Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler. Scraping does not refer to the collection of information through our API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. -You may not scrape the Service for spamming purposes, including for the purposes of selling User Personal Information (as defined in the [GitHub Privacy Statement](/articles/github-privacy-statement)), such as to recruiters, headhunters, and job boards. +You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling User Personal Information (as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement)), such as to recruiters, headhunters, and job boards. -All use of data gathered through scraping must comply with the [GitHub Privacy Statement](/articles/github-privacy-statement). +Your use of information from the Service must comply with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). ### 6. 개인 정보 보호 Misuse of User Personal Information is prohibited. diff --git a/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md b/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md index 1c48121fdefe..34d99f176a1b 100644 --- a/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: November 1, 2020 +Version Effective Date: November 13, 2020 When you create an Account, you're given access to lots of different features and products that are all a part of the Service. Because many of these features and products offer different functionality, they may require additional terms and conditions specific to that feature or product. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -89,7 +89,7 @@ In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors ### 9. GitHub Advanced Security -GitHub Advanced Security enables you to identify security vulnerabilities through customizable and automated semantic code analysis. GitHub Advanced Security is licensed on a per User basis. If you are using GitHub Advanced Security as part of GitHub Enterprise Cloud, many features of GitHub Advanced Security, including automated code scanning of private repositories, also require the use of GitHub Actions. Billing for usage of GitHub Actions is usage-based and is subject to the [GitHub Actions terms](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages). +GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. If you are using GitHub Advanced Security as part of GitHub Enterprise Cloud, many features of GitHub Advanced Security, including automated code scanning of private repositories, also require the use of GitHub Actions. ### 10. Dependabot Preview @@ -108,4 +108,3 @@ We need the legal right to submit your contributions to the GitHub Advisory Data #### b. License to the GitHub Advisory Database The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by . - diff --git a/translations/ko-KR/content/github/site-policy/github-community-guidelines.md b/translations/ko-KR/content/github/site-policy/github-community-guidelines.md index 1ddfde17ac06..4e1af8927df0 100644 --- a/translations/ko-KR/content/github/site-policy/github-community-guidelines.md +++ b/translations/ko-KR/content/github/site-policy/github-community-guidelines.md @@ -11,7 +11,7 @@ Millions of developers host millions of projects on GitHub — both open and clo GitHub users worldwide bring wildly different perspectives, ideas, and experiences, and range from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub a welcoming environment for all the different voices and perspectives in our community, while maintaining a space where people are free to express themselves. -We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. We do not actively seek out content to moderate. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service. +We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service. ### Building a strong community @@ -47,23 +47,25 @@ Of course, you can always contact us to {% data variables.contact.report_abuse % We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. Such discussions, however, are unlikely to foster fruitful dialog when ideas are silenced because community members are being shouted down or are afraid to speak up. That means you should be respectful and civil at all times, and refrain from attacking others on the basis of who they are. We do not tolerate behavior that crosses the line into the following: -* **Threats of violence** - You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety. +- #### Threats of violence You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety. -* **Hate speech and discrimination** - While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics. +- #### Hate speech and discrimination While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics. -* **Bullying and harassment** - We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory. +- #### Bullying and harassment We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory. -* **Impersonation** - You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment. +- #### Disrupting the experience of other users Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on. Behaviors such as repeatedly posting off-topic comments, opening empty or meaningless issues or pull requests, or using any other platform feature in a way that continually disrupts the experience of other users are not allowed. While we encourage maintainers to moderate their own projects on an individual basis, GitHub staff may take further restrictive action against accounts that are engaging in these types of behaviors. -* **Doxxing and invasion of privacy** - Don't post other people's personal information, such as phone numbers, private email addresses, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject. +- #### Impersonation You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment. -* **Sexually obscene content** - Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors. +- #### Doxxing and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject. -* **Gratuitously violent content** - Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content. +- #### Sexually obscene content Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors. -* **Misinformation and disinformation** - You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) because such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information. +- #### Gratuitously violent content Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content. -* **Active malware or exploits** - Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Note, however, that we do not prohibit the posting of source code which could be used to develop malware or exploits, as the publication and distribution of such source code has educational value and provides a net benefit to the security community. +- #### Misinformation and disinformation You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information. + +- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Note, however, that we do not prohibit the posting of source code which could be used to develop malware or exploits, as the publication and distribution of such source code has educational value and provides a net benefit to the security community. ### What happens if someone breaks the rules? diff --git a/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md index f85d6a2c5391..0e378a5dffd8 100644 --- a/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md @@ -9,7 +9,7 @@ versions: THANK YOU FOR CHOOSING GITHUB FOR YOUR COMPANY’S BUSINESS NEEDS. PLEASE READ THIS AGREEMENT CAREFULLY AS IT GOVERNS USE OF THE PRODUCTS (AS DEFINED BELOW), UNLESS GITHUB HAS EXECUTED A SEPARATE WRITTEN AGREEMENT WITH CUSTOMER FOR THAT PURPOSE. BY CLICKING ON THE "I AGREE" OR SIMILAR BUTTON OR BY ACCESSING THE PRODUCTS, CUSTOMER ACCEPTS ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF CUSTOMER IS ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, CUSTOMER REPRESENTS THAT IT HAS THE LEGAL AUTHORITY TO BIND THE COMPANY OR OTHER LEGAL ENTITY TO THIS AGREEMENT. ### GitHub Corporate Terms of Service -Version Effective Date: July 20, 2020 +Version Effective Date: November 16, 2020 This Agreement applies to the following GitHub offerings, as further defined below (collectively, the **“Products”**): - The Service; @@ -133,13 +133,13 @@ Customer may create or upload User-Generated Content while using the Service. Cu Customer retains ownership of Customer Content that Customer creates or owns. Customer acknowledges that it: (a) is responsible for Customer Content, (b) will only submit Customer Content that Customer has the right to post (including third party or User-Generated Content), and (c) Customer will fully comply with any third-party licenses relating to Customer Content that Customer posts. Customer grants the rights set forth in Sections D.3 through D.6, free of charge and for the purposes identified in those sections until such time as Customer removes Customer Content from GitHub servers, except for Content Customer has posted publicly and that External Users have Forked, in which case the license is perpetual until such time as all Forks of Customer Content have been removed from GitHub servers. If Customer uploads Customer Content that already comes with a license granting GitHub the permissions it needs to run the Service, no additional license is required. #### 3. License Grant to Us -Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies only as necessary to provide the Service. This includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content or otherwise distribute or use it outside of the Service. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. +Customer grants to GitHub the right to store, archive, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service, including improving the Service over time. This license includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content. It also does not grant GitHub the right to otherwise distribute or use Customer Content outside of our provision of the Service, except that as part of the right to archive Customer Content, GitHub may permit our partners to store and archive Customer Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. #### 4. License Grant to External Users Any Content that Customer posts publicly, including issues, comments, and contributions to External Users' repositories, may be viewed by others. By setting its repositories to be viewed publicly, Customer agree to allow External Users to view and Fork Customer’s repositories. If Customer sets its pages and repositories to be viewed publicly, Customer grants to External Users a nonexclusive, worldwide license to use, display, and perform Customer Content through the Service and to reproduce Customer Content solely on the Service as permitted through functionality provided by GitHub (for example, through Forking). Customer may grant further rights to Customer Content if Customer adopts a license. If Customer is uploading Customer Content that it did not create or own, Customer is responsible for ensuring that the Customer Content it uploads is licensed under terms that grant these permissions to External Users #### 5. Contributions Under Repository License -Whenever Customer makes a contribution to a repository containing notice of a license, it licenses such contributions under the same terms and agrees that it has the right to license such contributions under those terms. If Customer has a separate agreement to license its contributions under different terms, such as a contributor license agreement, that agreement will supersede. +Whenever Customer adds Content to a repository containing notice of a license, it licenses that Content under the same terms and agrees that it has the right to license that Content under those terms. If Customer has a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. #### 6. Moral Rights Customer retains all moral rights to Customer Content that it uploads, publishes, or submits to any part of the Service, including the rights of integrity and attribution. However, Customer waives these rights and agrees not to assert them against GitHub, solely to enable GitHub to reasonably exercise the rights granted in Section D, but not otherwise. @@ -153,10 +153,13 @@ Customer is responsible for managing access to its Private Repositories, includi GitHub considers Customer Content in Customer’s Private Repositories to be Customer’s Confidential Information. GitHub will protect and keep strictly confidential the Customer Content of Private Repositories in accordance with Section P. #### 3. 액세스 -GitHub personnel may only access Customer’s Private Repositories (i) with Customer’s consent and knowledge, for support reasons or (ii) when access is required for security reasons. Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. +GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 4. Exclusions -If GitHub has reason to believe the Content of a Private Repository is in violation of the law or of this Agreement, GitHub has the right to access, review, and remove that Content. Additionally, GitHub may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the Content of Customer’s Private Repositories. Unless otherwise bound by requirements under law or if in response to a security threat or other risk to security, GitHub will provide notice of such actions. +Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. + +Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. Intellectual Property Notice @@ -270,7 +273,7 @@ Neither Party will use the other Party's Confidential Information, except as per Upon Customer’s request for Professional Services, GitHub will provide an SOW detailing such Professional Services. GitHub will perform the Professional Services described in each SOW. GitHub will control the manner and means by which the Professional Services are performed and reserves the right to determine personnel assigned. GitHub may use third parties to perform the Professional Services, provided that GitHub remains responsible for their acts and omissions. Customer acknowledges and agrees that GitHub retains all right, title and interest in and to anything used or developed in connection with performing the Professional Services, including software, tools, specifications, ideas, concepts, inventions, processes, techniques, and know-how. To the extent GitHub delivers anything to Customer while performing the Professional Services, GitHub grants to Customer a non-exclusive, non-transferable, worldwide, royalty-free, limited-term license to use those deliverables during the term of this Agreement, solely in conjunction with Customer’s use of the Service. ### R. Changes to the Service or Terms -GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price changes, at least 30 days prior to the change taking effect by posting a notice on the Service. For non-material modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. +GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. GitHub changes the Service via Updates and addition of new features. Nothwithstanding the foregoing, GitHub reserves the right at any time to modify or discontinue, temporarily or permanently, the Service (or any part of it) with or without notice. diff --git a/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md index 7b9e3dca807c..eeeeaad115e4 100644 --- a/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -26,6 +26,6 @@ For definitions of each Service feature (“**Service Feature**”) and to revi Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption -If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption should be sent to [GitHub Support](https://support.github.com/contact). +If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). Service Credits may take the form of a refund or credit to Customer’s account, cannot be exchanged into a cash amount, are limited to a maximum of ninety (90) days of paid service per calendar quarter, require Customer to have paid any outstanding invoices, and expire upon termination of Customer’s agreement with GitHub. Service Credits are the sole and exclusive remedy for any failure by GitHub to meet any obligations in this SLA. diff --git a/translations/ko-KR/content/github/site-policy/github-enterprise-subscription-agreement.md b/translations/ko-KR/content/github/site-policy/github-enterprise-subscription-agreement.md index 50ad30b4a792..fcd2d9ec34ec 100644 --- a/translations/ko-KR/content/github/site-policy/github-enterprise-subscription-agreement.md +++ b/translations/ko-KR/content/github/site-policy/github-enterprise-subscription-agreement.md @@ -7,7 +7,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: July 20, 2020 +Version Effective Date: November 16, 2020 BY CLICKING THE "I AGREE" OR SIMILAR BUTTON OR BY USING ANY OF THE PRODUCTS (DEFINED BELOW), CUSTOMER ACCEPTS THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF CUSTOMER IS ENTERING INTO THIS AGREEMENT ON BEHALF OF A LEGAL ENTITY, CUSTOMER REPRESENTS THAT IT HAS THE LEGAL AUTHORITY TO BIND THE LEGAL ENTITY TO THIS AGREEMENT. @@ -197,7 +197,7 @@ This Agreement, together with the Exhibits and each Order Form and SOW, constitu #### 1.13.11 Amendments; Order of Precedence. -GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price changes, at least 30 days prior to the change taking effect by posting a notice on the Service. For non-material modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. In the event of any conflict between the terms of this Agreement and any Order Form or SOW, the terms of the Order Form or SOW will control with respect to that Order Form or SOW only. +GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. In the event of any conflict between the terms of this Agreement and any Order Form or SOW, the terms of the Order Form or SOW will control with respect to that Order Form or SOW only. #### 1.13.12 Severability. @@ -296,7 +296,7 @@ Customer may create or upload User-Generated Content while using the Service. Cu **(ii)** Customer grants the rights set forth in Sections 3.3.3 through 3.3.6, free of charge and for the purposes identified in those sections until such time as Customer removes Customer Content from GitHub servers, except for Content Customer has posted publicly and that External Users have Forked, in which case the license is perpetual until such time as all Forks of Customer Content have been removed from GitHub servers. If Customer uploads Customer Content that already comes with a license granting GitHub the permissions it needs to run the Service, no additional license is required. #### 3.3.3 License Grant to GitHub. -Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies only as necessary to provide the Service. This includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content or otherwise distribute or use it outside of the Service. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. +Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service. This includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content or otherwise distribute or use it outside of the Service. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. #### 3.3.4 License Grant to External Users. **(i)** Any Content that Customer posts publicly, including issues, comments, and contributions to External Users' repositories, may be viewed by others. By setting its repositories to be viewed publicly, Customer agree to allow External Users to view and Fork Customer’s repositories. @@ -318,10 +318,13 @@ Customer is responsible for managing access to its Private Repositories, includi GitHub considers Customer Content in Customer’s Private Repositories to be Customer’s Confidential Information. GitHub will protect and keep strictly confidential the Customer Content of Private Repositories in accordance with Section 1.4. #### 3.4.3 Access. -GitHub may only access Customer’s Private Repositories (i) with Customer’s consent and knowledge, for support reasons, or (ii) when access is required for security reasons. Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. +GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 3.4.4 Exclusions. -If GitHub has reason to believe the Content of a Private Repository is in violation of the law or of this Agreement, GitHub has the right to access, review, and remove that Content. Additionally, GitHub may be compelled by law to disclose the Content of Customer’s Private Repositories. Unless otherwise bound by requirements under law or if in response to a security threat or other risk to security, GitHub will provide notice of such actions. +Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. + +Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 3.5. Intellectual Property Notices. 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 9e25fc9ada40..d7613d36fdb2 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 @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Effective date: October 2, 2020 +Effective date: November 16, 2020 Thanks for entrusting GitHub Inc. (“GitHub”, “we”) with your source code, your projects, and your personal information. Holding on to your private information is a serious responsibility, and we want you to know how we're handling it. @@ -150,23 +150,39 @@ We **do not** sell your User Personal Information for monetary or other consider Please note: The California Consumer Privacy Act of 2018 (“CCPA”) requires businesses to state in their privacy policy whether or not they disclose personal information in exchange for monetary or other valuable consideration. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. You can learn more about the CCPA and how we comply with it [here](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act). -### Other important information +### Repository contents + +#### Access to private repositories + +If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for +- security purposes +- to assist the repository owner with a support matter +- to maintain the integrity of the Service +- to comply with our legal obligations +- if we have reason to believe the contents are in violation of the law, or +- with your consent. + +However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories). -#### Repository contents +Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts). -GitHub personnel [do not access private repositories unless required to](/github/site-policy/github-terms-of-service#e-private-repositories) for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, or to comply with our legal obligations. However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, or other content known to violate our Terms, such as violent extremist or terrorist content or child exploitation imagery based on algorithmic fingerprinting techniques. Our Terms of Service provides [more details](/github/site-policy/github-terms-of-service#e-private-repositories). +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. -If your repository is public, anyone may view its contents. If you include private, confidential or [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. +#### Public repositories + +If your repository is public, anyone may view its contents. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. Please see more about [User Personal Information in public repositories](/github/site-policy/github-privacy-statement#public-information-on-github). +### Other important information + #### Public information on GitHub Many of GitHub services and features are public-facing. If your content is public-facing, third parties may access and use it in compliance with our Terms of Service, such as by viewing your profile or repositories or pulling data via our API. We do not sell that content; it is yours. However, we do allow third parties, such as research organizations or archives, to compile public-facing GitHub information. Other third parties, such as data brokers, have been known to scrape GitHub and compile data as well. Your User Personal Information associated with your content could be gathered by third parties in these compilations of GitHub data. If you do not want your User Personal Information to appear in third parties’ compilations of GitHub data, please do not make your User Personal Information publicly available and be sure to [configure your email address to be private in your user profile](https://github.com/settings/emails) and in your [git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). We currently set Users' email address to private by default, but legacy GitHub Users may need to update their settings. -If you would like to compile GitHub data, you must comply with our Terms of Service regarding [scraping](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users. +If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users. Similarly, projects on GitHub may include publicly available User Personal Information collected as part of the collaborative process. If you have a complaint about any User Personal Information on GitHub, please see our section on [resolving complaints](/github/site-policy/github-privacy-statement#resolving-complaints). @@ -219,7 +235,7 @@ That said, the email address you have supplied [via your Git commit settings](/g #### Cookies -GitHub uses cookies and similar technologies (collectively, “cookies”) to make interactions with our service easy and meaningful. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors. We use cookies to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. By using our Website, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use GitHub’s services. +GitHub uses cookies and similar technologies (e.g., HTML5 localStorage) to make interactions with our service easy and meaningful. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors. We use cookies and similar technologies (hereafter collectively "cookies") to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. By using our Website, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use GitHub’s services. We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies. It also lists our third-party analytics providers and how you can control your cookie preference settings for such cookies. @@ -300,7 +316,7 @@ In the unlikely event that a dispute arises between you and GitHub regarding our ### Changes to our Privacy Statement -Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For changes to this Privacy Statement that are not material changes or that do not affect your rights, we encourage Users to check our Site Policy repository frequently. +Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### 라이선스 diff --git a/translations/ko-KR/content/github/site-policy/github-terms-of-service.md b/translations/ko-KR/content/github/site-policy/github-terms-of-service.md index 4c7ddee2384b..598bdbaddef4 100644 --- a/translations/ko-KR/content/github/site-policy/github-terms-of-service.md +++ b/translations/ko-KR/content/github/site-policy/github-terms-of-service.md @@ -32,11 +32,11 @@ Thank you for using GitHub! We're happy you're here. Please read this Terms of S | [N. Disclaimer of Warranties](#n-disclaimer-of-warranties) | We provide our service as is, and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** | | [O. Limitation of Liability](#o-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** | | [P. Release and Indemnification](#p-release-and-indemnification) | You are fully responsible for your use of the service. | -| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of changes that affect your rights. | +| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. | | [R. Miscellaneous](#r-miscellaneous) | Please see this section for legal details including our choice of law. | ### The GitHub Terms of Service -Effective date: April 2, 2020 +Effective date: November 16, 2020 ### A. 정의 @@ -98,7 +98,7 @@ You agree that you will not under any circumstances violate our [Acceptable Use You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content. #### 2. GitHub May Remove Content -We do not pre-screen User-Generated Content, but we have the right (though not the obligation) to refuse or remove any User-Generated Content that, in our sole discretion, violates any [GitHub terms or policies](/github/site-policy). +We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub for mobile may be subject to mobile app stores' additional terms. #### 3. Ownership of Content, Right to Post, and License Grants You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post. @@ -106,9 +106,9 @@ You retain ownership of and responsibility for Your Content. If you're posting a Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it. #### 4. License Grant to Us -We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, parse, and display Your Content, and make incidental copies as necessary to render the Website and provide the Service. This includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. +We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. -This license does not grant GitHub the right to sell Your Content or otherwise distribute or use it outside of our provision of the Service. +This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/). #### 5. License Grant to Other Users Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). @@ -116,7 +116,7 @@ Any User-Generated Content you post publicly, including issues, comments, and co If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you [adopt a license](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users. #### 6. Contributions Under Repository License -Whenever you make a contribution to a repository containing notice of a license, you license your contribution under the same terms, and you agree that you have the right to license your contribution under those terms. If you have a separate agreement to license your contributions under different terms, such as a contributor license agreement, that agreement will supersede. +Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit. @@ -126,7 +126,7 @@ You retain all moral rights to Your Content that you upload, publish, or submit To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service. ### E. Private Repositories -**Short version:** *You may have access to private repositories. We treat the content of private repositories as confidential, and we only access it for support reasons, with your consent, or if required to for security reasons.* +**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.* #### 1. Control of Private Repositories Some Accounts may have private repositories, which allow the User to control access to Content. @@ -135,15 +135,14 @@ Some Accounts may have private repositories, which allow the User to control acc GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care. #### 3. 액세스 -GitHub personnel may only access the content of your private repositories in the following situations: -- With your consent and knowledge, for support reasons. If GitHub accesses a private repository for support reasons, we will only do so with the owner’s consent and knowledge. -- When access is required for security reasons, including when access is required to maintain ongoing confidentiality, integrity, availability and resilience of GitHub's systems and Service. +GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). You may choose to enable additional access to your private repositories. 예시: - You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights. -#### 4. Exclusions -If we have reason to believe the contents of a private repository are in violation of the law or of these Terms, we have the right to access, review, and remove them. Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. +Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. Copyright Infringement and DMCA Policy If you believe that content on our website violates your copyright, please contact us in accordance with our [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing copyright@github.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses. @@ -286,9 +285,9 @@ If you have a dispute with one or more Users, you agree to release GitHub from a You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense. ### Q. Changes to These Terms -**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any changes that affect your rights and give you time to adjust to them.* +**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.* -We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price changes, at least 30 days prior to the change taking effect by posting a notice on our Website. For non-material modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. +We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice. diff --git a/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md index a8c53d9f94da..819ac47d2fba 100644 --- a/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md +++ b/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md @@ -41,12 +41,12 @@ Within conversations on {% data variables.product.product_name %}, references to References to a commit's SHA hash are automatically converted into shortened links to the commit on {% data variables.product.product_name %}. -| Reference type | Raw reference | Short link | -| ----------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | -| Commit URL | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| Username/Repository@SHA | jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| Reference type | Raw reference | Short link | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | +| Commit URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| `Username/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | ### Custom autolinks to external resources diff --git a/translations/ko-KR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md b/translations/ko-KR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md index 26d95c251aee..063997c698f7 100644 --- a/translations/ko-KR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md +++ b/translations/ko-KR/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md @@ -8,19 +8,24 @@ versions: {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% endnote %} - {% data reusables.package_registry.container-registry-feature-highlights %} To share context about your package's use, you can link a repository to your container image on {% data variables.product.prodname_dotcom %}. For more information, see "[Connecting a repository to a container image](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)." ### Supported formats -The {% data variables.product.prodname_container_registry %} currently only supports Docker images. +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +#### Manifest Lists/Image Indexes +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. ### Visibility and access permissions for container images diff --git a/translations/ko-KR/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md b/translations/ko-KR/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md new file mode 100644 index 000000000000..3cb030c09baa --- /dev/null +++ b/translations/ko-KR/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md @@ -0,0 +1,37 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + + ![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/ko-KR/content/packages/getting-started-with-github-container-registry/index.md b/translations/ko-KR/content/packages/getting-started-with-github-container-registry/index.md index 46849f39a609..f07fd0941c04 100644 --- a/translations/ko-KR/content/packages/getting-started-with-github-container-registry/index.md +++ b/translations/ko-KR/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 %} For more information about configuring, deleting, pushing, or pulling container images, see "[Managing container images with {% data variables.product.prodname_github_container_registry %}](/packages/managing-container-images-with-github-container-registry)." diff --git a/translations/ko-KR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md b/translations/ko-KR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md index 8516292b8195..976e46a58930 100644 --- a/translations/ko-KR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md +++ b/translations/ko-KR/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md @@ -31,6 +31,8 @@ The domain for the {% data variables.product.prodname_container_registry %} is ` ### Authenticating with the container registry +{% data reusables.package_registry.feature-preview-for-container-registry %} + You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}. {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} @@ -72,6 +74,8 @@ To move Docker images that you host on {% data variables.product.prodname_regist ### Updating your {% data variables.product.prodname_actions %} workflow +{% data reusables.package_registry.feature-preview-for-container-registry %} + If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers. 1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)." diff --git a/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md b/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md index 05fc53b92d0a..81110a4ffcf7 100644 --- a/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md +++ b/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md @@ -24,7 +24,7 @@ If you have admin permissions to an organization-owned container image, you can If your package is owned by an organization and private, then you can only give access to other organization members or teams. -For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) @@ -54,7 +54,7 @@ When you first publish a package, the default visibility is private and only you A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. -For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 5. Under "Danger Zone", choose a visibility setting: diff --git a/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md b/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md index 0d4d0873d2d1..ddf6eae62764 100644 --- a/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md +++ b/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md @@ -16,8 +16,6 @@ To delete a container image, you must have admin permissions to the container im When deleting public packages, be aware that you may break projects that depend on your package. - - ### Reserved package versions and names {% data reusables.package_registry.package-immutability %} diff --git a/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md index e4e1db91970c..5dd0f067e25a 100644 --- a/translations/ko-KR/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ b/translations/ko-KR/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 %} -To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." ### Authenticating to {% data variables.product.prodname_github_container_registry %} 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 f86a9d046c3e..55a2bc4215e2 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 @@ -26,6 +26,8 @@ You can integrate {% data variables.product.prodname_registry %} with {% data va {% data reusables.package_registry.container-registry-beta %} +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + {% endif %} #### Viewing packages 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 3eff1a537717..26fe40cff451 100644 --- a/translations/ko-KR/content/rest/overview/other-authentication-methods.md +++ b/translations/ko-KR/content/rest/overview/other-authentication-methods.md @@ -37,12 +37,22 @@ $ curl -u username:token {% data variables.product.api_url_pre This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. -{% if enterpriseServerVersions contains currentVersion %} #### Via username and password -{% data reusables.apps.deprecating_password_auth %} +{% if currentVersion == "free-pro-team@latest" %} + +{% 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 %} -To use Basic Authentication with the {% data variables.product.product_name %} API, simply send the username and password associated with the account. +{% 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. For example, if you're accessing the API via [cURL][curl], the following command would authenticate you if you replace `` with your {% data variables.product.product_name %} username. (cURL will prompt you to enter the password.) @@ -88,14 +98,13 @@ The value `organizations` is a comma-separated list of organization IDs for orga {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ### Working with two-factor authentication -{% data reusables.apps.deprecating_password_auth %} - -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 or OAuth token instead of your username and password. - -You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}with [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %} or use the "[Create a new authorization][create-access]" endpoint in the OAuth Authorizations API to generate a new OAuth token. 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)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the GitHub API. 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. +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 %}. 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)". 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 %} #### Using the OAuth Authorizations API with two-factor authentication When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code: @@ -114,7 +123,6 @@ $ curl --request POST \ ``` {% endif %} -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization [curl]: http://curl.haxx.se/ [oauth-auth]: /v3/#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line 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 93455012cd2b..f1192cf231a6 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 @@ -135,9 +135,9 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar 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" @@ -165,19 +165,10 @@ $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product. 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 %} - -{% note %} - -**Note:** For {% data variables.product.prodname_ghe_server %}, [as with all other endpoints](/v3/enterprise-admin/#endpoint-urls), you'll need to pass your username and password. - -{% endnote %} - -{% endif %} - ### 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. diff --git a/translations/ko-KR/content/rest/overview/troubleshooting.md b/translations/ko-KR/content/rest/overview/troubleshooting.md index ff456f25af4b..a71f7348c090 100644 --- a/translations/ko-KR/content/rest/overview/troubleshooting.md +++ b/translations/ko-KR/content/rest/overview/troubleshooting.md @@ -13,16 +13,53 @@ versions: If you're encountering some oddities in the API, here's a list of resolutions to some of the problems you may be experiencing. -### Why am I getting a `404` error on a repository that exists? +### `404` error for an existing repository Typically, we send a `404` error when your client isn't properly authenticated. You might expect to see a `403 Forbidden` in these cases. However, since we don't want to provide _any_ information about private repositories, the API returns a `404` error instead. To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), and [third-party application restrictions][oap-guide] are not blocking access. -### Why am I not seeing all my results? +### Not all results returned 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. +{% 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. 예시: + +```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/ko-KR/content/rest/reference/interactions.md b/translations/ko-KR/content/rest/reference/interactions.md index 15c357b2503c..610d4666ed45 100644 --- a/translations/ko-KR/content/rest/reference/interactions.md +++ b/translations/ko-KR/content/rest/reference/interactions.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -Users interact with repositories by commenting, opening issues, and creating pull requests. The Interactions APIs allow people with owner or admin access to temporarily restrict certain users from interacting with public repositories. +Users interact with repositories by commenting, opening issues, and creating 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 @@ Users interact with repositories by commenting, opening issues, and creating pul ## 조직 -The Organization Interactions API allows organization owners to temporarily restrict which users can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users: +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 %} in the organization. * {% data reusables.interactions.contributor-user-limit-definition %} in the organization. * {% data reusables.interactions.collaborator-user-limit-definition %} in the organization. +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 %} ## 리포지토리 -The Repository Interactions API allows people with owner or admin access to temporarily restrict which users can comment, open issues, or create pull requests in a public repository. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users: +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 repository. * {% data reusables.interactions.contributor-user-limit-definition %} in the repository. * {% data reusables.interactions.collaborator-user-limit-definition %} in the repository. +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 %} + +## User + +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/ko-KR/content/rest/reference/oauth-authorizations.md b/translations/ko-KR/content/rest/reference/oauth-authorizations.md index 8bb3e8fa72cc..356309baff03 100644 --- a/translations/ko-KR/content/rest/reference/oauth-authorizations.md +++ b/translations/ko-KR/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 %} - You can use this API to manage the access OAuth applications have to your account. You can only access this API via [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) using your username and password, not tokens. If you or your users 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). diff --git a/translations/ko-KR/content/rest/reference/search.md b/translations/ko-KR/content/rest/reference/search.md index fe02f29a6735..9becc9da4785 100644 --- a/translations/ko-KR/content/rest/reference/search.md +++ b/translations/ko-KR/content/rest/reference/search.md @@ -31,13 +31,19 @@ Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is: ``` -q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N +SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N ``` For example, if you wanted to search for all _repositories_ owned by `defunkt` that contained the word `GitHub` and `Octocat` in the README file, you would use the following query with the _search repositories_ endpoint: ``` -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. 예시: +```javascript +// JavaScript +const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax/)." diff --git a/translations/ko-KR/data/graphql/ghae/graphql_previews.ghae.yml b/translations/ko-KR/data/graphql/ghae/graphql_previews.ghae.yml index 8540c1d976f7..f957e0b7bcff 100644 --- a/translations/ko-KR/data/graphql/ghae/graphql_previews.ghae.yml +++ b/translations/ko-KR/data/graphql/ghae/graphql_previews.ghae.yml @@ -85,7 +85,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Pinned Issues Preview description: This preview adds support for pinned issues. 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 7ad2acba5901..10f9989a1239 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 @@ -2,112 +2,112 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ko-KR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml b/translations/ko-KR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml index 4cb2fcaddf2d..cff46f0627fe 100644 --- a/translations/ko-KR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ko-KR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml @@ -2,63 +2,63 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ko-KR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/ko-KR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml index dcf3d7d79244..76ece32029eb 100644 --- a/translations/ko-KR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ko-KR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml @@ -2,560 +2,560 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` will be removed. Use the `Package` object instead." + description: '`color` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` will be removed. Use the `Package` object instead." + description: '`latestVersion` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` will be removed. Use the `Package` object instead." + description: '`name` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` will be removed. Use the `Package` object instead." + description: '`nameWithOwner` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` will be removed. Use the `Package` object." + description: '`packageFileByGuid` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` will be removed. Use the `Package` object." + description: '`packageFileBySha256` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` will be removed. Use the `Package` object instead." + description: '`packageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` will be removed. Use the `Package` object instead." + description: '`preReleaseVersions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` will be removed. Use the `Package` object instead." + description: '`registryPackageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` will be removed. Use the `Package` object instead." + description: '`repository` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` will be removed. Use the `Package` object instead." + description: '`statistics` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` will be removed. Use the `Package` object." + description: '`tags` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` will be removed. Use the `Package` object." + description: '`topics` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` will be removed. Use the `Package` object instead." + description: '`version` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` will be removed. Use the `Package` object instead." + description: '`versionByPlatform` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` will be removed. Use the `Package` object instead." + description: '`versionBySha256` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` will be removed. Use the `Package` object instead." + description: '`versions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` will be removed. Use the `Package` object instead." + description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` will be removed. Use the `PackageDependency` object instead." + description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` will be removed. Use the `PackageDependency` object instead." + description: '`name` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` will be removed. Use the `PackageDependency` object instead." + description: '`version` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` will be removed. Use the `PackageFile` object instead." + description: '`guid` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` will be removed. Use the `PackageFile` object instead." + description: '`md5` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` will be removed. Use the `PackageFile` object instead." + description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` will be removed. Use the `PackageFile` object instead." + description: '`name` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` will be removed. Use the `PackageFile` object instead." + description: '`packageVersion` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` will be removed. Use the `PackageFile` object instead." + description: '`sha1` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` will be removed. Use the `PackageFile` object instead." + description: '`sha256` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` will be removed. Use the `PackageFile` object instead." + description: '`size` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` will be removed. Use the `PackageFile` object instead." + description: '`url` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` will be removed. Use the `PackageTag` object instead." + description: '`name` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` will be removed. Use the `PackageTag` object instead." + description: '`version` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` will be removed. Use the `PackageVersion` object instead." + description: '`dependencies` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` will be removed. Use the `PackageVersion` object instead." + description: '`fileByName` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` will be removed. Use the `PackageVersion` object instead." + description: '`files` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` will be removed. Use the `PackageVersion` object instead." + description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` will be removed. Use the `PackageVersion` object instead." + description: '`manifest` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` will be removed. Use the `PackageVersion` object instead." + description: '`platform` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` will be removed. Use the `PackageVersion` object instead." + description: '`preRelease` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` will be removed. Use the `PackageVersion` object instead." + description: '`readme` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead." + description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` will be removed. Use the `PackageVersion` object instead." + description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` will be removed. Use the `PackageVersion` object instead." + description: '`release` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` will be removed. Use the `PackageVersion` object instead." + description: '`sha256` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` will be removed. Use the `PackageVersion` object instead." + description: '`size` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` will be removed. Use the `PackageVersion` object instead." + description: '`statistics` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` will be removed. Use the `PackageVersion` object instead." + description: '`summary` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` will be removed. Use the `PackageVersion` object instead." + description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` will be removed. Use the `PackageVersion` object instead." + description: '`version` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead." + description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ko-KR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/ko-KR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml index 4b56579d9316..5341a42e26e0 100644 --- a/translations/ko-KR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ko-KR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml @@ -2,568 +2,568 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` will be removed. Use the `Package` object instead." + description: '`color` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` will be removed. Use the `Package` object instead." + description: '`latestVersion` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` will be removed. Use the `Package` object instead." + description: '`name` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` will be removed. Use the `Package` object instead." + description: '`nameWithOwner` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` will be removed. Use the `Package` object." + description: '`packageFileByGuid` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` will be removed. Use the `Package` object." + description: '`packageFileBySha256` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` will be removed. Use the `Package` object instead." + description: '`packageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` will be removed. Use the `Package` object instead." + description: '`preReleaseVersions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` will be removed. Use the `Package` object instead." + description: '`registryPackageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` will be removed. Use the `Package` object instead." + description: '`repository` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` will be removed. Use the `Package` object instead." + description: '`statistics` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` will be removed. Use the `Package` object." + description: '`tags` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` will be removed. Use the `Package` object." + description: '`topics` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` will be removed. Use the `Package` object instead." + description: '`version` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` will be removed. Use the `Package` object instead." + description: '`versionByPlatform` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` will be removed. Use the `Package` object instead." + description: '`versionBySha256` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` will be removed. Use the `Package` object instead." + description: '`versions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` will be removed. Use the `Package` object instead." + description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` will be removed. Use the `PackageDependency` object instead." + description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` will be removed. Use the `PackageDependency` object instead." + description: '`name` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` will be removed. Use the `PackageDependency` object instead." + description: '`version` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` will be removed. Use the `PackageFile` object instead." + description: '`guid` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` will be removed. Use the `PackageFile` object instead." + description: '`md5` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` will be removed. Use the `PackageFile` object instead." + description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` will be removed. Use the `PackageFile` object instead." + description: '`name` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` will be removed. Use the `PackageFile` object instead." + description: '`packageVersion` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` will be removed. Use the `PackageFile` object instead." + description: '`sha1` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` will be removed. Use the `PackageFile` object instead." + description: '`sha256` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` will be removed. Use the `PackageFile` object instead." + description: '`size` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` will be removed. Use the `PackageFile` object instead." + description: '`url` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` will be removed. Use the `PackageTag` object instead." + description: '`name` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` will be removed. Use the `PackageTag` object instead." + description: '`version` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.deleted - description: "`deleted` will be removed. Use the `PackageVersion` object instead." + description: '`deleted` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` will be removed. Use the `PackageVersion` object instead." + description: '`dependencies` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` will be removed. Use the `PackageVersion` object instead." + description: '`fileByName` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` will be removed. Use the `PackageVersion` object instead." + description: '`files` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` will be removed. Use the `PackageVersion` object instead." + description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` will be removed. Use the `PackageVersion` object instead." + description: '`manifest` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` will be removed. Use the `PackageVersion` object instead." + description: '`platform` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` will be removed. Use the `PackageVersion` object instead." + description: '`preRelease` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` will be removed. Use the `PackageVersion` object instead." + description: '`readme` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead." + description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` will be removed. Use the `PackageVersion` object instead." + description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` will be removed. Use the `PackageVersion` object instead." + description: '`release` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` will be removed. Use the `PackageVersion` object instead." + description: '`sha256` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` will be removed. Use the `PackageVersion` object instead." + description: '`size` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` will be removed. Use the `PackageVersion` object instead." + description: '`statistics` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` will be removed. Use the `PackageVersion` object instead." + description: '`summary` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` will be removed. Use the `PackageVersion` object instead." + description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` will be removed. Use the `PackageVersion` object instead." + description: '`version` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead." + description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea diff --git a/translations/ko-KR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/ko-KR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml index f5fb1765b079..977c97a5785e 100644 --- a/translations/ko-KR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ko-KR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml @@ -2,71 +2,71 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea @@ -86,15 +86,15 @@ upcoming_changes: owner: oneill38 - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden @@ -107,21 +107,21 @@ upcoming_changes: owner: oneill38 - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ko-KR/data/graphql/graphql_previews.yml b/translations/ko-KR/data/graphql/graphql_previews.yml index e00c8f5704f1..ae939b5e57a6 100644 --- a/translations/ko-KR/data/graphql/graphql_previews.yml +++ b/translations/ko-KR/data/graphql/graphql_previews.yml @@ -102,7 +102,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Pinned Issues Preview description: This preview adds support for pinned issues. 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 c8040777f133..f12ecd03316b 100644 --- a/translations/ko-KR/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ko-KR/data/graphql/graphql_upcoming_changes.public.yml @@ -2,119 +2,119 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Query.sponsorsListing - description: "`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead." - reason: "`Query.sponsorsListing` will be removed." + description: '`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead.' + reason: '`Query.sponsorsListing` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ko-KR/data/reusables/feature-preview/feature-preview-setting.md b/translations/ko-KR/data/reusables/feature-preview/feature-preview-setting.md new file mode 100644 index 000000000000..8af532d9db24 --- /dev/null +++ b/translations/ko-KR/data/reusables/feature-preview/feature-preview-setting.md @@ -0,0 +1 @@ +1. In the upper-right corner of any page, click your profile photo, then click **Feature preview**. ![Feature preview button](/assets/images/help/settings/feature-preview-button.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/gated-features/secret-scanning.md b/translations/ko-KR/data/reusables/gated-features/secret-scanning.md new file mode 100644 index 000000000000..bd279034eee8 --- /dev/null +++ b/translations/ko-KR/data/reusables/gated-features/secret-scanning.md @@ -0,0 +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 %} diff --git a/translations/ko-KR/data/reusables/interactions/interactions-detail.md b/translations/ko-KR/data/reusables/interactions/interactions-detail.md index 9193cd04e704..187a3e73074d 100644 --- a/translations/ko-KR/data/reusables/interactions/interactions-detail.md +++ b/translations/ko-KR/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -When restrictions are enabled, only the specified group of {% data variables.product.product_name %} users will be able to participate in interactions. Restrictions expire 24 hours from the time they are set. +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. diff --git a/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md b/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md index a5e3b6f7f871..24313880baea 100644 --- a/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md +++ b/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. 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)." {% endnote %} diff --git a/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md new file mode 100644 index 000000000000..b0cddc8bcb84 --- /dev/null +++ b/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% endnote %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/secret-scanning/beta.md b/translations/ko-KR/data/reusables/secret-scanning/beta.md index 68ed06f9c93a..3625bb7a3e26 100644 --- a/translations/ko-KR/data/reusables/secret-scanning/beta.md +++ b/translations/ko-KR/data/reusables/secret-scanning/beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change. To request access to the beta, [join the waitlist](https://github.com/features/security/advanced-security/signup). +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change. {% endnote %} diff --git a/translations/ko-KR/data/ui.yml b/translations/ko-KR/data/ui.yml index 678ce9a66a45..0780738a45de 100644 --- a/translations/ko-KR/data/ui.yml +++ b/translations/ko-KR/data/ui.yml @@ -4,9 +4,10 @@ header: contact: 연락처 notices: ghae_silent_launch: GitHub AE is currently under limited release. Please contact our Sales Team to find out more. + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: 문서에 대한 업데이트가 자주 게시되며, 이 페이지의 번역이 아직 진행 중일 수 있습니다. 최신 정보는영어 설명서를 방문하십시오. 이 페이지에서 번역에 문제가 있는 경우 알려주십시오. localization_in_progress: 안녕하세요! 이 페이지는 현재 개발 중이거나 아직 번역 중입니다. 정확한 최신 정보를 확인하려면 영어 설명서를 방문하십시오. - product_in_progress: '👋 안녕하세요! 이 페이지는 현재 개발 중입니다. 정확한 최신 정보는 개발자 설명서를 방문하십시오.' + early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' search: need_help: 도움이 필요하십니까? placeholder: 검색 주제, 제품... @@ -19,7 +20,7 @@ toc: guides: 안내서 whats_new: What's new pages: - article_version: "문서 버전:" + article_version: '문서 버전:' miniToc: 기사 내용 errors: oops: 이런! diff --git a/translations/ko-KR/data/variables/action_code_examples.yml b/translations/ko-KR/data/variables/action_code_examples.yml new file mode 100644 index 000000000000..c35362989200 --- /dev/null +++ b/translations/ko-KR/data/variables/action_code_examples.yml @@ -0,0 +1,149 @@ +--- +- + title: Starter workflows + description: Workflow files for helping people get started with GitHub Actions + languages: TypeScript + href: actions/starter-workflows + tags: + - official + - workflows +- + title: Example services + description: Example workflows using service containers + languages: JavaScript + href: actions/example-services + tags: + - service containers +- + title: Declaratively setup GitHub Labels + description: GitHub Action to declaratively setup labels across repos + languages: JavaScript + href: lannonbr/issue-label-manager-action + tags: + - issues + - labels +- + title: Declaratively sync GitHub labels + description: GitHub Action to sync GitHub labels in the declarative way + languages: 'Go, Dockerfile' + href: micnncim/action-label-syncer + tags: + - issues + - labels +- + title: Add releases to GitHub + description: Publish Github releases in an action + languages: 'Dockerfile, Shell' + href: elgohr/Github-Release-Action + tags: + - 버전 출시 + - publishing +- + title: Publish a docker image to Dockerhub + description: A Github Action used to build and publish Docker images + languages: 'Dockerfile, Shell' + href: elgohr/Publish-Docker-Github-Action + tags: + - docker + - publishing + - build +- + title: Create an issue using content from a file + description: A GitHub action to create an issue using content from a file + languages: 'JavaScript, Python' + href: peter-evans/create-issue-from-file + tags: + - issues +- + title: Publish GitHub Releases with Assets + description: GitHub Action for creating GitHub Releases + languages: 'TypeScript, Shell, JavaScript' + href: softprops/action-gh-release + tags: + - 버전 출시 + - publishing +- + title: GitHub Project Automation+ + description: Automate GitHub Project cards with any webhook event. + languages: JavaScript + href: alex-page/github-project-automation-plus + tags: + - projects + - automation + - issues + - pull requests +- + title: Run GitHub Actions Locally with a web interface + description: Runs GitHub Actions workflows locally (local) + languages: 'JavaScript, HTML, Dockerfile, CSS' + href: phishy/wflow + tags: + - local-development + - devops + - docker +- + title: Run your GitHub Actions locally + description: Run GitHub Actions Locally in Terminal + languages: 'Go, Shell' + href: nektos/act + tags: + - local-development + - devops + - docker +- + title: Build and Publish Android debug APK + description: Build and release debug APK from your Android project + languages: 'Shell, Dockerfile' + href: ShaunLWM/action-release-debugapk + tags: + - android + - build +- + title: Generate sequential build numbers for GitHub Actions + description: GitHub action for generating sequential build numbers. + languages: JavaScript + href: einaregilsson/build-number + tags: + - build + - automation +- + title: GitHub actions to push back to repository + description: Push Git changes to GitHub repository without authentication difficulties + languages: 'JavaScript, Shell' + href: ad-m/github-push-action + tags: + - publishing +- + title: Generate release notes based on your events + description: Action to auto generate a release note based on your events + languages: 'Shell, Dockerfile' + href: Decathlon/release-notes-generator-action + tags: + - 버전 출시 + - publishing +- + title: Create a GitHub wiki page based on the provided markdown file + description: Create a GitHub wiki page based on the provided markdown file + languages: 'Shell, Dockerfile' + href: Decathlon/wiki-page-creator-action + tags: + - wiki + - publishing +- + title: 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: + - projects + - issues + - labels +- + title: Add Label to your Pull Requests based on the author team name + description: Github action to label your pull requests based on the author name + languages: 'TypeScript, JavaScript' + href: JulienKode/team-labeler-action + tags: + - 끌어오기 요청 + - labels diff --git a/translations/ko-KR/data/variables/contact.yml b/translations/ko-KR/data/variables/contact.yml index d230130d9418..890e996840ea 100644 --- a/translations/ko-KR/data/variables/contact.yml +++ b/translations/ko-KR/data/variables/contact.yml @@ -10,7 +10,7 @@ contact_dmca: >- {% if currentVersion == "free-pro-team@latest" %}[Copyright claims form](https://github.com/contact/dmca){% endif %} contact_privacy: >- {% if currentVersion == "free-pro-team@latest" %}[Privacy contact form](https://github.com/contact/privacy){% endif %} -contact_enterprise_sales: '[GitHub''s Sales team](https://enterprise.github.com/contact)' +contact_enterprise_sales: "[GitHub's Sales team](https://enterprise.github.com/contact)" contact_feedback_actions: '[Feedback form for GitHub Actions](https://support.github.com/contact/feedback?contact[category]=actions)' #The team that provides Standard Support enterprise_support: 'GitHub Enterprise Support' diff --git a/translations/ko-KR/data/variables/release_candidate.yml b/translations/ko-KR/data/variables/release_candidate.yml new file mode 100644 index 000000000000..ec65ef6f9445 --- /dev/null +++ b/translations/ko-KR/data/variables/release_candidate.yml @@ -0,0 +1,2 @@ +--- +version: '' 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 fac5e27b7209..53bf3338844b 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 7afadb442f5d..5c937ff7c60d 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,13 +79,13 @@ 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 %} @@ -95,20 +95,20 @@ Você pode armazenar as suas dependências para acelerar as execuções do seu f {% 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 549704f853a6..40900468ea40 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,13 +79,13 @@ 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 %} @@ -95,20 +95,20 @@ Você pode armazenar as suas dependências para acelerar as execuções do seu f {% 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 2c2dad9f3a91..1ff5743a66ad 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] ``` 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 f1edb036d50a..aa5095ca4372 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)". -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)". +Você pode armazenar em cache dependências do PowerShell usando uma chave única, o que lhe permite restaurar as dependências para futuros fluxos de trabalho com 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)". -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-ruby.md b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md new file mode 100644 index 000000000000..47bff7c4ae8b --- /dev/null +++ b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md @@ -0,0 +1,318 @@ +--- +title: Building and testing Ruby +intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### 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. + +### 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: + +- [Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions) +- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) + +### Starting with the Ruby workflow template + +{% 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). + +Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. + +{% raw %} +```yaml +name: Ruby + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: 2.6 + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Specifying the Ruby version + +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). + +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. + +The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 # Not needed with a .ruby-version file +- run: bundle install +- run: bundle exec rake +``` +{% 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. + +### Testing with multiple versions of 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. + +{% raw %} +```yaml +strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] +``` +{% 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." + +The full updated workflow with a matrix strategy could look like this: + +{% raw %} +```yaml +name: Ruby CI + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby ${{ matrix.ruby-version }} + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: ${{ matrix.ruby-version }} + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Installing dependencies with 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. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 +- run: bundle install +``` +{% endraw %} + +#### Memorizar dependências + +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 +steps: +- uses: ruby/setup-ruby@v1 + with: + bundler-cache: true +``` +{% 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. + +**Caching without 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)". + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + ${{ runner.os }}-gems- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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: + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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. + +{% raw %} +```yaml +name: Matrix Testing + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + runs-on: ${{ matrix.os }}-latest + strategy: + fail-fast: false + matrix: + os: [ubuntu, macos] + ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head] + continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }} + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: ${{ matrix.ruby }} + - run: bundle install + - run: bundle exec rake +``` +{% 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. + +{% raw %} +```yaml +name: Linting + +on: [push] + +jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + - name: Rubocop + run: rubocop +``` +{% endraw %} + +### Publishing 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 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`. + +{% raw %} +```yaml + +name: Ruby Gem + +on: + # Manually publish + workflow_dispatch: + # Alternatively, publish whenever changes are merged to the default branch. + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + build: + name: Build + Publish + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby 2.6 + uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + + - name: Publish to GPR + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem + env: + GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}" + OWNER: ${{ github.repository_owner }} + + - name: Publish to RubyGems + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push *.gem + env: + GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" +``` +{% endraw %} + diff --git a/translations/pt-BR/content/actions/guides/index.md b/translations/pt-BR/content/actions/guides/index.md index f7e40ce2e964..8774c1a09cf3 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 2883119128bf..055a0ebeec1a 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 631a3792dde6..f0cf61a99c67 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 2add474fe8d6..40ee31060ee5 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 @@ -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/index.md b/translations/pt-BR/content/actions/index.md index 573d92de1acf..7d23c9b917b7 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 - date: '2020-10-16' - href: https://github.blog/changelog/2020-10-16-github-actions-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: 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: 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: 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: 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: 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 + 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/ 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 -
- -
+ {% render 'code-example-card' for actionsCodeExamples as example %}
- Mostrar todos os guias {% octicon "arrow-right" %} + + +
+
{% 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 7c7d0bac96bf..27acef164a8f 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 e7ebf1d5c6c3..99b803b1ab79 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/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 3f2ec972ac8e..c553ce8e41e2 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,39 @@ git: -### Key features in {% data variables.product.prodname_actions %} +### Principais recursos em {% data variables.product.prodname_actions %} -When migrating from Travis CI, consider the following key features in {% 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 +206,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 +233,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 +281,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. @@ -320,11 +320,11 @@ Para obter mais informações, consulte "[Memorizar dependências para acelerar ### 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 +357,7 @@ env:
-#### Building with Node.js +#### Criar com Node.js @@ -405,4 +405,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 3f579e27c274..0dd84827a9be 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 e8626f46a9a5..75e45c99f448 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 75661c7e25f3..ebc6a5002c08 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 c68ead7ac9a1..8374c0bc65c0 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/quickstart.md b/translations/pt-BR/content/actions/quickstart.md index 1388f9bd7767..9da0b4a78c91 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/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md index 0cc799e2f7d6..5ee3379ef354 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 @@ -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,6 +350,7 @@ jobs: - run: | echo "Comment on issue #${{ github.event.issue.number }}" ``` +{% endraw %} #### `Problemas` @@ -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 %} 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 a91901658739..84ee8a1a717d 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/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md index 70980a1067d6..056b5a3f1a12 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 2d4d9a44dfb1..43713a75469c 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 @@ -446,7 +446,7 @@ 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`** @@ -492,7 +492,7 @@ 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 @@ -659,7 +659,7 @@ For built-in shell keywords, we provide the following defaults that are executed - `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. + - `cmd.exe` will exit with the error level of the last program it executed, and it will 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. #### **`jobs..steps.with`** @@ -718,7 +718,7 @@ 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. +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. #### **`jobs..steps.env`** 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 66b09f5d741a..adb7a3e762dd 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/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 bc52bd49c80f..2d0ae190531b 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 ef320ac2ce7e..d2461efe4ad4 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 eebe52d89f93..c95fb420dedf 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 d65730e2713a..cc57824de03b 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 %}. - - | 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 | +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. + + 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 5c95b614112e..a442518aa305 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 9b4b3f0a0aae..b037d6f7ea9a 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 c1c8230c9d9a..3304f0e0487c 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 a343b03be7f1..da4bcad0fd31 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/configuring-data-encryption-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index 595cb26b3e63..fa33e83cea71 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 a64ee9b62fbe..28a6f4a3e0e8 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 e7f23583451e..a7e0a468305b 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 86c9b6baae54..e3ac6f821455 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/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 5c3243a4cff3..4112082aae53 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 3024b7a519f3..1968eda320ac 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 aa6af7a30549..ca8b44834e79 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 d20a711bd06d..645f01789ec9 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 89d045d1e77e..c62ef5947295 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/monitoring-cluster-nodes.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md index 404349189204..7ab408f8ff66 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 13f5d92a6c8a..e3335854c4cf 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 3ac2a84849b1..18de3b059785 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 c687980e239c..b1d5b8a54612 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 c31d8df26e77..8bd24a4b4583 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 f986bff9469f..c6f1b8303478 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 500cc3cdccc6..2338266d9ac3 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 8757267bb273..3123ee09862d 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 83b767df1116..e2b743fadaf0 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 556efca9fb04..bf33586b9d3f 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/overview/about-the-github-enterprise-api.md b/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md index 155c8606d503..6a9a0ed3b816 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)." +- 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](/v4/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). \ No newline at end of file diff --git a/translations/pt-BR/content/admin/overview/index.md b/translations/pt-BR/content/admin/overview/index.md index 764e02bae544..5e243d5ad1fa 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 8e42153b82b4..0ef2520a9676 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 8dad72f6f528..902c96e5c38a 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 c23aba8618a0..841ef760e9cb 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. 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:** +- 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. 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 1b91d14bf71a..18c9849ca38f 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 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 6a536c064af1..f3f6369093a7 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)." +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. 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,7 +43,7 @@ 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 %} @@ -51,7 +51,7 @@ Se um administrador do site impedir que os membros criem certos tipos de reposit 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. -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)." +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. 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 %} @@ -86,7 +86,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 +106,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 +123,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 +151,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 +164,17 @@ 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) ### 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,7 +191,7 @@ 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 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 120209106b92..0c2d58fe3190 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 420adacf63c4..825e6d827a1b 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 7381c7b38b5f..a7eb538a5d12 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,53 +34,53 @@ 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. 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` | 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. 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)". | #### 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.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. | @@ -89,7 +89,7 @@ versions: | `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.unarchive` | Um repositório teve o arquivamento cancelado. 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.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)". | @@ -115,28 +115,28 @@ 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/ [aplicativo OAuth]: /guides/basics-of-authentication/#registering-your-app 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 092d928cd9ef..e86bf5098f2d 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 4065fb06c521..e8bc5340186e 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 6a12c83f4431..ae30d72ca373 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 02652de2e2f2..9b315050d4d9 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 4500fd7e5f9c..c298b992da8d 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 6feb06436cd5..4f71883b519a 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/index.md b/translations/pt-BR/content/admin/user-management/index.md index 598ef1452839..196578e022d4 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 b5ebba4ea936..1deccde9155a 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 108ac5bfa26a..499a075434a4 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 d54dcc96fecd..244a03011d03 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-repositories-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise.md index bf3d4ff9be69..04a6fbf4bd75 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 863fc30cdc9a..6311f01b8cf1 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/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 662db838e51c..9912307bd3b0 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 3452bbbb1e3f..e11d29c2d54c 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 64cdb229c69f..ac7ac875456e 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 882f6ad22d77..4ec3603287f1 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/viewing-push-logs.md b/translations/pt-BR/content/admin/user-management/viewing-push-logs.md index 6bdb33e07c43..8328b8c54589 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 9b4acc8e1e74..fbd513b31e6b 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. +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. 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 %} + +**Note:** Split diff displays are currently in beta and subject to change. + +{% endnote %} -![Linhas desmarcadas em um arquivo](/assets/images/help/desktop/partial-commit.png) +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. ![Linhas desmarcadas em um arquivo](/assets/images/help/desktop/partial-commit.png) -#### Descartar alterações +### 3. Descartar alterações +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. -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. +Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied. -{% mac %} +#### Discarding changes in one or more files {% 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 %} +#### Discarding changes in one or more lines +You can discard one or more changed lines that are uncommitted. -**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. - -{% endtip %} +{% note %} -{% endmac %} +**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. -{% windows %} +{% endnote %} -{% 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) +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**. -{% tip %} + ![Discard single line in the confirmation dialog](/assets/images/help/desktop/discard-single-line.png) -**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. +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**. -{% endtip %} + ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) -{% 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 c19cb3a47f6c..0ca4e8b3d789 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/ 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 f8c8325f68dd..7e245d2b0d7c 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 2f86c3061cc2..cb758383bc17 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 7fb85f4ed23b..6da87be3e586 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 @@ -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. 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 f277541f140b..aa0c0c07cbfc 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/rate-limits-for-github-apps.md b/translations/pt-BR/content/developers/apps/rate-limits-for-github-apps.md index 013c1d782b9d..421c0438e1c6 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/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md index da1c5b3d569f..a1f6ee5cf7df 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. - -### Available scopes - -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 %} +* `X-OAuth-Scopes` lista o escopo que seu token autorizou. +* `X-Accepted-OAuth-Scopes` lista os escopos verificados pela ação. + +### Escopos disponíveis + +| 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 %}](/v3/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](/v3/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 %}](/v3/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/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 e82a47ae292e..10badad00f0c 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/ 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 b3e018a6b5d0..a2ee8874cac0 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 e1db964b989d..12d0387cb430 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 f51e83ca2991..3985047aa75b 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 04f6e9d14e94..1017a9386bef 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 8e9ba94714d0..a0d1bdd15c9e 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/securing-your-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md index 3bac5716704f..ba8cd0bb522b 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 dee4a9679140..ee273ce0d1bb 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](/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. {% 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`](/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 %} -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](/v3/apps/installations/#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.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 %} -

-

+#### Webhook payload example -

{% data reusables.webhooks.repo_desc %}

+{{ webhookPayloadsForCurrentVersion.issue_comment.created }} -

-

+### issues -

{% data reusables.webhooks.org_desc %}

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

-

+#### Availability -

{% data reusables.webhooks.app_desc %}

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

-

+#### Webhook payload object -

{% data reusables.webhooks.sender_desc %}

+{% 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

+#### Webhook payload example when someone edits an issue -

{{ webhookPayloadsForCurrentVersion.issues.edited }}

+{{ webhookPayloadsForCurrentVersion.issues.edited }} -

etiqueta

+### label -

{% data reusables.webhooks.label_short_desc %}

+{% data reusables.webhooks.label_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 | -| ---------------------- | -------- | --------------------------------------------------------------------- | -| `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`. | +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 %} -#### Exemplo de carga de webhook +#### 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_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.member.added }}

- -

filiação

- -

{% data reusables.webhooks.membership_short_desc %}

- -

Disponibilidade

- -
    -
  • Webhooks da organização
    • -
  • Os {% data variables.product.prodname_github_app %}s com a permissão `membros`
    • -
+{% 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 %} -

Objeto da carga do webhook

+#### Webhook payload example -

{% data reusables.webhooks.membership_properties %}

+{{ webhookPayloadsForCurrentVersion.member.added }} -

-

+### membership -

{% data reusables.webhooks.org_desc %}

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

-

+#### Availability -

{% data reusables.webhooks.app_desc %}

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

-

+#### Webhook payload object -

{% data reusables.webhooks.sender_desc %}

+{% 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

+#### Webhook payload example -

{{ webhookPayloadsForCurrentVersion.membership.removed }}

+{{ webhookPayloadsForCurrentVersion.membership.removed }} -

meta

+### 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.

+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. -

Disponibilidade

+#### Availability -
    -
  • Webhooks do repositório
    • -
  • Webhooks da organização
    • -
+- Repository webhooks +- Organization webhooks -

Objeto da carga do webhook

+#### Webhook payload object -

- - - - - - - - - - - -
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` - - -

Objeto da carga do webhook

- -

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

+- 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 + +#### Webhook payload object + +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](/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 %}. -#### 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](/v3/repos/hooks/#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 - -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` - -#### Objeto da carga do webhook - -| 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. | +#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `contents` permission + +#### Webhook payload object + +Key | Type | Description +----|------|------------- +`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]`|`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](/v3/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](/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.
{% 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](/v3/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 - -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão membros` - - -

Objeto da carga do webhook

- -

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

+#### Availability + +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `members` permission + +#### Webhook payload object + +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 - -- Webhooks do repositório -- Webhooks da organização -- Os {% data variables.product.prodname_github_app %}s com a permissão membros` - - -

Objeto da carga do webhook

- -

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

+#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `members` permission + +#### Webhook payload object + +Key | Type | Description +----|------|------------- +`team`|`object` | The [team](/v3/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](/v3/users/) who starred a repository, and the event’s repository is the [repository](/v3/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,41 @@ 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" %} ### 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 %} ### 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 }} 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 8e23902c7ac2..3e16e2658040 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 58af138a95e2..942931397ccc 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 4bfcbe12c6c4..d4a28706c6a3 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 121135ce2025..a000158b1263 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,7 +37,7 @@ 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)". 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 f079e6206f8c..6bff42df2d5d 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 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 9e9615216763..0033ab237c7d 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/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index d8da8921c7c4..5a1f04a20410 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 956ff2b6ed18..25ff8c47122a 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 db204e574c1b..6e1a84bf45d4 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 405e97a07d3d..85b0144c0528 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/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 b21e6a0afb99..e7a08f76d448 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 2f4b8ed5c078..451a2bfdcc14 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 c306f5a9909a..ac4c3b6723c0 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 @@ -10,7 +10,7 @@ versions: 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 1b1588186ae4..625794839cbf 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 685c5215ebbc..d5176f462a82 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 941376e4982e..48918cac69db 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 b00d6e5b99ed..97346e253b31 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 b997f5b299ce..27f4effc0405 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-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 d9e76dbe843d..c7d6abc45189 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 4308f33dedf8..f56e42d2a4c8 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 @@ -20,11 +20,11 @@ Recomendamos revisar as seguintes advertências antes de alterar a visibilidade #### Tornar um repositório privado - * 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)" + * 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. 9" %}Se você alterar a visibilidade de um repositório interno para privada, {% data variables.product.prodname_dotcom %} removerá as bifurcações que pertencem a qualquer usuário sem acesso ao repositório privado recente.{% endif %} Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou tem sua visibilidade alterada?](/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 enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}* Acesso de leitura anônimo do Git não está mais disponível. 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 %} #### Tornar um repositório público 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 822fa6965c95..03a84d4d4ce5 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 50648ad2c845..051502db0739 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 833904e6676f..fd4100bc43c3 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-ssh.md b/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md index 76ba848f35be..8da751e4958e 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/authenticating-with-saml-single-sign-on.md b/translations/pt-BR/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md index 802cd946f41d..f74dfd75cb0e 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 939b19d59372..8c89752239ef 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/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 0abf639d7a93..f2fa7497c4b2 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 * 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 f225fe1a3878..89c37b5330c9 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 58ae2c06922b..d8a94860f8c7 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/managing-commit-signature-verification.md b/translations/pt-BR/content/github/authenticating-to-github/managing-commit-signature-verification.md index 326ea4c4764b..f5ca5f2c74d1 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 264a3a22b0a1..2e5c272ef278 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. +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/reviewing-your-security-log versions: @@ -33,218 +34,222 @@ The security log lists all actions performed within the last 90 days{% if curren #### Search based on the action performed {% else %} ### Understanding events in your security log - -Actions listed in your security log are grouped within the following categories: {% endif %} -| Category Name | Description +The events listed in your security log are triggered by your actions. Actions are grouped into the following categories: + +| 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. - -A description of the events within these categories is listed below. +| [`account_recovery_token`](#account_recovery_token-category-actions) | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods). +| [`billing`](#billing-category-actions) | Contains all activities related to your billing information. +| [`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 %} +| [`oauth_access`](#oauth_access-category-actions) | 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`](#payment_method-category-actions) | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your profile picture. +| [`project`](#project-category-actions) | Contains all activities related to project boards. +| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account). +| [`repo`](#repo-category-actions) | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | 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`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %} +| [`user`](#user-category-actions) | Contains all activities related to your account. + +{% if currentVersion == "free-pro-team@latest" %} + +### Exporting your security log + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} + +{% endif %} + +### Security log actions + +An overview of some of the most common actions that are recorded as events in the security log. {% if currentVersion == "free-pro-team@latest" %} -#### The `account_recovery_token` category +#### `account_recovery_token` category actions | 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. +| `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 +#### `billing` category actions | 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). +| `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 +#### `marketplace_agreement_signature` category actions | Action | Description |------------------|------------------- -| create | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. +| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. -#### The `marketplace_listing` category +#### `marketplace_listing` category actions | 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 %}. +| `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 +#### `oauth_access` category actions | 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). +| `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 +#### `payment_method` category actions | 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. +| `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 +#### `profile_picture` category actions | Action | Description |------------------|------------------- -| update | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/). +| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/). -#### The `project` category +#### `project` category actions | Action | Description |--------------------|--------------------- +| `access` | Triggered when a project board's visibility is changed. | `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 +#### `public_key` category actions | 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). +| `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 +#### `repo` category actions | 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. +| `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 +#### `sponsors` category actions | 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)") +| `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 +#### `successor_invitation` category actions | 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)") +| `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 +#### `team` category actions | 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. +| `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 +#### `two_factor_authentication` category actions | 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. +| `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 +#### `user` category actions | 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 +| `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.{% 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 %} +| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). +| `login` | Triggered when you log in to {% data variables.product.product_location %}. +| `failed_login` | Triggered when you failed to log in successfully. +| `remove_email` | Triggered when you remove an email address. +| `rename` | Triggered when you rename your account.{% 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 %} +| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% 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 %} + +#### `user_status` category actions | 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" %} +| `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. -### Exporting your security log -{% data reusables.audit_log.export-log %} -{% data reusables.audit_log.exported-log-keys-and-values %} - -{% endif %} 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 234002448a7e..cdddaf6e8b30 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 2970b800c22f..93aa14be43cd 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 7c167c514b4a..127c351deaf7 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 119a6b2cac16..8b434cb86806 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,7 @@ 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)." +É possível criar modelos padrão de problemas e pull requests para 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 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)." ### 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 53072cd01a84..eea10923a94f 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/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 6a27df12db07..96bf5f094138 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,7 @@ 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)." +Você pode criar recursos de suporte padrão para a 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 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)." {% 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 398985d286c4..81c18a34f2e6 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/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 bcae1fbbf171..ac3d1dfcfdfa 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 @@ -12,38 +12,38 @@ versions: ### 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 0bc1f8edfbb6..55d9b34334c0 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,7 @@ 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)." +É possível criar modelos padrão de pull requests para 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 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)." ### 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 02e1c3b8eeb1..32f75a3e3302 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 a5b193c11008..c682d4316acd 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 24e8f07689f7..e1b843b11b8a 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 382b02f7d6f7..9c5f179db4e0 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-on-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 16acb1360ccb..efdcd3664951 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/setting-guidelines-for-repository-contributors.md b/translations/pt-BR/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md index 09f420803983..c9899796e26b 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,7 @@ 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)." +Você pode criar diretrizes de contribuição padrão para a 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 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)." {% tip %} 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 f17a2643ef70..ff78c6b25b4f 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 @@ -25,7 +25,7 @@ Você deve ter acesso de gravação em um repositório para criar um branch, abr {% 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 %} -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,7 +74,7 @@ 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 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" %} - 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 %} ### 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 a6d5d3d1e089..026a64938e0b 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 d3898c112877..ee98e3cd533d 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/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 4135232bf843..0c5ebefda15c 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/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 81190022aa44..ab220e97be1c 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 fe9595fa3f86..4665ca5c1857 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 7fbcc480e5a2..6d3f11f19045 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/syncing-a-fork.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md index 1aca29abb9a8..2919a55ec45a 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/committing-changes-to-your-project/comparing-commits.md b/translations/pt-BR/content/github/committing-changes-to-your-project/comparing-commits.md index 1132eca9d9f0..256b11e73be3 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 e0e23bf5804f..0f1e8124bdd0 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 @@ -31,7 +31,7 @@ For more information, see "[Setting your commit email address](/articles/setting ### Creating co-authored commits using {% 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). +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#4-write-a-commit-message-and-push-your-changes)" and [{% 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) @@ -75,4 +75,4 @@ The new commit and message will appear on {% data variables.product.product_loca - "[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 +- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation 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 bfaea6e1b93f..970af981ef25 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 c6687d8c1e5f..0c1307f2a525 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 8af95a7a8930..838937fd4413 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,36 @@ 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. +Um arquivo README, 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. -Um LEIAME, muitas vezes, é o primeiro item que um visitante verá ao visitar seu repositório. Os arquivos LEIAME geralmente incluem informações sobre: +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 %} -![Arquivo LEIAME no nome de usuário/repositório do nome de usuário](/assets/images/help/repository/username-repo-with-readme.png) +![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 LEIAME e páginas blob +### 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 %} +Muitos projetos usam uma tabela de conteúdo no início de um README 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/creating-a-template-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md index 39778d159c4d..9533cf884f81 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 b84b840535ba..3b571dd4fc7b 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/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 a7db1b93425f..d1ba863b8fb8 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/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 ff27712b4928..231d1a2cb17e 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 obter mais informações, consulte "[Sobre o {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". -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 0cc08d5b3c84..48033fd7a79c 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,80 +12,76 @@ 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 +#### Fazer a varredura de forma pré-programada -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)." +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 %} -**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. +**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 %} -#### Example +#### Exemplo -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`. +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: - branches: [main, protected] pull_request: - branches: [main] 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 +90,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 +118,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 +166,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 +181,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 +196,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 +208,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. + +#### Especificar consultas adicionais -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. +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,17 +221,17 @@ 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. Você pode excluir os arquivos em diretórios específicos das varreduras, adicionando um array de `paths-ignore`. ``` yaml paths: @@ -247,37 +243,37 @@ paths-ignore: {% 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)." +Para C/C++, C#, e Java, se você desejar limitar {% data variables.product.prodname_code_scanning %} a diretórios específicos no seu projeto, você deverá especificar etapas de criação apropriadas no fluxo de trabalho. 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 +283,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 907b1cd3d961..ce18e7150f86 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 ef76c6ead1ad..62eccbbbb5ac 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 d44cd2e445b5..39c41a2402d0 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 876423b274e1..ba573e5bf493 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/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 b51fe36706e8..ab553d6878ad 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 3ddc1056facb..b99b3337b488 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. + For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. 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 02df04943055..76fba71719cf 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 4ba6040e8314..5ee639896586 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/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 25eff360eefa..9898486782ea 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 6b6b7b606222..ca95887da779 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/github-for-mobile.md b/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md index 4bd1e7e9de1b..f8e64d3dc58e 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 fd5d1481e549..b615238f2276 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 74264a493033..447f1f01a8da 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 fb2221f15e04..432693b58b4c 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 5f77beef3f86..96a9d424f94d 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](/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/managing-large-files/conditions-for-large-files.md b/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md index f803ba426f90..d0e00cc29774 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 2d663bba8899..f97112a8672d 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 c90bdd36df99..6c6aacf77b50 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 c0f46c36576b..e8ad172c2b76 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 de seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-dependabot-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 a645e9ae2124..45a9faeff077 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 73d18e4072ae..913431ac6347 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 235627fcba9b..2654037db9d9 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 860d7784a1d4..528e4bfc9a4c 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 846c79962828..b225e4c70a89 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 6c6165d70edd..bb789818c079 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 f1b3af4c35ff..5d56a0258520 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 878d09d6c1d4..7bfddce59ecf 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 a1e4114a7a73..1a8935eb50b3 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/configuring-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index a41f92ef021e..ccda8b7f877e 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 @@ -110,7 +110,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 +167,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" %} 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 253908d3c62e..1e87b53721ff 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-your-work-on-github/about-issues.md b/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md index 39b73088df0d..5e9c3695ce49 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-a-label.md b/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-label.md index a0d83432b653..d4c11f7ac28d 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-label.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-label.md @@ -30,6 +30,6 @@ versions: - "[Sobre etiquetas](/articles/about-labels)" - "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests)" - "[Editar uma etiqueta](/articles/editing-a-label)" -- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +- "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} - "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)" {% endif %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/deleting-a-label.md b/translations/pt-BR/content/github/managing-your-work-on-github/deleting-a-label.md index 5df91159e676..fc99fd715658 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/deleting-a-label.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/deleting-a-label.md @@ -19,6 +19,6 @@ A exclusão de uma etiqueta a removerá de qualquer problema ou pull request em ### Leia mais - "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests)" -- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +- "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} - "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)" {% endif %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/editing-a-label.md b/translations/pt-BR/content/github/managing-your-work-on-github/editing-a-label.md index 895bee3f7009..02dd89d5f04d 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/editing-a-label.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/editing-a-label.md @@ -24,6 +24,6 @@ versions: - "[Criar uma etiqueta](/articles/creating-a-label)" - "[Excluir uma etiqueta](/articles/deleting-a-label)" - "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests)" -- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +- "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} - "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)" {% endif %} 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 0b90cf40f6fd..756d98806e5a 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/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 72b27d861895..c260f5d27d2c 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 %} @@ -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/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 44850bd66582..d394bcb1bbcd 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 625f69695c2f..a862624e1d78 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 4994d250db8c..271dc1c307f8 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 @@ -63,9 +63,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-issues-and-pull-requests.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 74ec0b1461ff..0beb0d98b964 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. 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 58a10ab88fdb..cec29aa9ed49 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-your-organization-dashboard.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md index 068c6f3f7af4..03fc5a69b757 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. 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 95eaedc29630..43ab8f2afae0 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 b89b5fecce4a..5e6a4b2f6807 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 55a11392c520..01b0f1aacf1f 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 6f7319a61134..f753d6053539 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/keeping-your-organization-secure.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md index e173bbd03ace..28819a41c232 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 e49e67f95fb6..6e1d55436925 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 e5a98a15fe71..8e41a504aef8 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 02987a0fd4f2..684f92dbba59 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 511d676ff716..1a56221145b1 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 56be0018d7ca..df986ffaf5cc 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 8824fc5fafc8..b878a56111e7 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 3608669ae51d..7e7b23dfe83d 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 5addfe9716e4..dd89f15c649f 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,77 @@ 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** | +| 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 92ff459f4006..fe8b27ba6734 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/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 61497be9a9dd..12d028716278 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: - -{% 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) +#### Search based on time of action + +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 %} -##### The `account` category +**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" %} + +#### `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,7 +393,7 @@ 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 |------------------|------------------- @@ -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 +|------------------|------------------- +| `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-dependabot-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 |------------------|------------------- -| `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 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 ac62de20d3b2..e7e526062aa8 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 e70f55bc64b2..dcd4cbd05b7f 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/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 2b0bdf75424d..b2362a95c5a1 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 4855d718d639..2ba856a1911e 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 @@ -24,7 +24,7 @@ Uma conta corporativa permite que você gerencie múltiplas organizações {% da 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)". 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 2bd1d3b7665f..c2187fe3a952 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 dcb5400a3096..6ff1ec7816bb 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 3374f119cde0..6749343d5c4b 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 f6b634d619c4..72035f7b2ce0 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 b45da0bc2e83..249ecea3cbf2 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 2912c3987a80..f71e6b4e4bfd 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 2651dc1ee238..8672d1d92865 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 fab65dabc967..a1ab984a6e8d 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 ffbd4494817f..d0a6e2ea7b9c 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 3ff0ad16fd25..d93885da2f85 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/managing-your-profile-readme.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 5f0cf00facaf..a73e6555acc6 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 @@ -62,4 +62,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/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 6cdf3eb78065..5a63a82e264f 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,6 +1,6 @@ --- 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 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 35613400de7b..4c6a2863e9d9 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 @@ -15,7 +15,7 @@ O gráfico de contribuição mostra a atividade em repositórios públicos. Voc {% 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,7 +26,7 @@ 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 %} @@ -82,9 +82,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 d8a168542747..e74cd0bdf05c 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,7 +39,7 @@ 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 %} @@ -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 c3bdf530cdef..b8c4bad8c305 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 @@ -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 %}. 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 8140f491016e..b498d312f65b 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/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 22b6f45afc37..befe4bfdf593 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: 'Um repositório pertencente a uma conta de usuário tem dois níveis de permissão: *proprietário do repositório* e *colaboradores*.' redirect_from: - /articles/permission-levels-for-a-user-account-repository versions: @@ -11,64 +11,64 @@ versions: {% 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)." +**Dica:** Se você precisar de acesso de leitura e gravação mais granular em um repositório de propriedade de sua conta de usuário, considere transferir o repositório para uma organização. Para obter mais informações, consulte "[Transferir um repositório](/articles/transferring-a-repository)". {% endtip %} -#### Owner access on a repository owned by a user account +#### Acesso de proprietário em um repositório de propriedade de uma conta de usuário -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. Além de todas as permissões concedidas aos colaboradores de repositório, o proprietário do repositório pode: -- {% 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 %} +- {% if currentVersion == "free-pro-team@latest" %}[Convidar colaboradores](/articles/inviting-collaborators-to-a-personal-repository){% else %}[Adicionar colaboradores](/articles/inviting-collaborators-to-a-personal-repository){% endif %} +- Altere a visibilidade do repositório (de [público para privado](/articles/making-a-public-repository-private) ou de [privado para público](/articles/making-a-private-repository-public)){% if currentVersion == "free-pro-team@latest" %} +- [Restringir interações no repositório](/articles/limiting-interactions-with-your-repository){% endif %} +- Fazer merge de uma pull request em um branch protegido, mesmo sem revisões de aprovação +- [Excluir o repositório](/articles/deleting-a-repository) +- [Gerencie os tópicos de um repositório](/articles/classifying-your-repository-with-topics){% if currentVersion == "free-pro-team@latest" %} +- Gerenciar configurações de segurança e análise. Para obter mais informações, consulte "[Gerenciar 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)."{% endif %}{% 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) para um repositório privado{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- Excluir pacotes. Para obter mais informações, consulte "[Excluir um pacote](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} +- Criar e editar cartões sociais do repositório. Para obter mais informações, consulte "[Personalizar a exibição das redes sociais do repositório](/articles/customizing-your-repositorys-social-media-preview)". +- Transformar o repositório em um modelo. Para obter mais informações, consulte "[Criar um repositório de templates](/articles/creating-a-template-repository)."{% if currentVersion != "github-ae@latest" %} +- Receba [{% 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 %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) em um repositório.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- Ignorar {% data variables.product.prodname_dependabot_alerts %} no seu repositório. Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository). " +- [Gerenciar o uso de dados para o seu repositório privado](/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](/articles/about-code-owners) +- [Repositórios de arquivos](/articles/about-archiving-repositories){% if currentVersion == "free-pro-team@latest" %} +- Criar consultorias de segurança. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". +- Exibir um botão de patrocinador. 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 %} -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)." +Só existe um **único proprietário** de um repositório pertencente a uma conta de usuário. Essa permissão não pode ser compartilhada com outra conta de usuário. Para transferir a propriedade de um repositório a outro usuário, consulte "[Como transferir um repositório](/articles/how-to-transfer-a-repository)". -#### Collaborator access on a repository owned by a user account +#### Acesso de colaborador em um repositório de propriedade de uma conta de usuário {% 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: +Em um repositório pessoal, os colaboradores podem: -- 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)." +- Fazer push para (gravar), fazer pull de (ler) e bifurcar (copiar) o repositório +- Criar, aplicar e excluir etiquetas e marcos +- Abrir, fechar, reabrir e atribuir problemas +- Editar e excluir comentários em commits, pull request e problemas +- Marcar um problema ou pull request como duplicata. Para obter mais informações, consulte "[Sobre problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests)". +- Abrir, fazer merge e fechar pull requests +- Aplicar as alterações sugeridas em pull requests. Para obter mais informações, consulte "[Incluir feedback na pull request](/articles/incorporating-feedback-in-your-pull-request)". +- Envie pull requests das bifurcações do repositório{% if currentVersion == "free-pro-team@latest" %} +- Publicar, visualizar e instalar pacotes. Para obter mais informações, consulte "[Publicar e gerenciar pacotes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)".{% endif %} +- Criar e editar Wikis +- Criar e editar versões. Para obter mais informações, consulte "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository). +- Remover a si mesmos como colaboradores do repositório +- Enviar uma revisão de uma pull request que afetará a capacidade de merge dela +- Atuar como um proprietário do código designado do repositório. Para obter mais informações, consulte "[Sobre proprietários do código](/articles/about-code-owners)". +- Bloquear uma conversa. Para obter mais informações, consulte "[Bloquear conversas](/articles/locking-conversations)."{% if currentVersion == "free-pro-team@latest" %} +- Denunciar conteúdo abusivo para o {% data variables.contact.contact_support %}. Para obter mais informações, consulte "[Relatar abuso ou spam](/articles/reporting-abuse-or-spam)".{% endif %} +- Transferir um problema para um repositório diferente. Para obter mais informações, consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-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)" +- "[Convidar colaboradores para um repositório pessoal](/articles/inviting-collaborators-to-a-personal-repository)" +- "[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 d0f7e5e2ca49..d16cee6434ca 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 62d475e2aab3..8b82895678ec 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 7751adda5d11..8fccf722385a 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: + +- 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. -- 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. +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. -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. +You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling User Personal Information (as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement)), such as to recruiters, headhunters, and job boards. -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). +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 dda56088e1e8..48f0c215688e 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. -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 09a75802788d..a9f0840580a8 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,11 +10,11 @@ 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. +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**”). 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. @@ -53,9 +53,9 @@ Customer is a Controller only for the Customer Personal Data it transfers direct #### 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. @@ -68,13 +68,13 @@ 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. 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. #### 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 RGPD: a. *The subject matter and duration of the processing* of Customer Personal Data are set out in the Agreement and the DPA. 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 d77bb8a78b6c..a4787ea439dc 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,15 +8,15 @@ 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. 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 79945454280a..b4b7f5a8a302 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 %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/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 and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. 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 1c8491c84e35..625c90a1e019 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 @@ -9,7 +9,7 @@ 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 +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. +Customer grants to GitHub the right to store, archive, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service, including improving the Service over time. 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. It also does not grant GitHub the right to otherwise distribute or use Customer Content outside of our provision of the Service, except that as part of the right to archive Customer Content, GitHub may permit our partners to store and archive Customer Content in public repositories in connection with the GitHub Arctic Code Vault and 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. +Whenever Customer adds Content to a repository containing notice of a license, it licenses that Content under the same terms and agrees that it has the right to license that Content under those terms. If Customer has a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. #### 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. +GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/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. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. Avisos de Propriedade Intelectual @@ -203,7 +206,7 @@ O Cliente autoriza o GitHub a cobrar o cartão de crédito registrado, conta do ### K. Termo; Rescisão; Suspensão -#### 1. Vigência +#### 1. Term Este Contrato é válido a partir da Data do Início da Vigência e continuará em vigor até ser rescindido por uma das Partes, de acordo com esta Seção K. #### 2. Rescisão por Conveniência; Cancelamento de Conta @@ -212,7 +215,7 @@ Qualquer das Partes pode rescindir um Formulário de Pedido (se aplicável) ou e #### 3. Rescisão por violação de contrato Qualquer das Partes poderá rescindir este Contrato imediatamente, mediante notificação, se a outra Parte descumprir alguma clásula deste Contrato e não conseguir corrigir a violação no prazo de trinta (30) dias a partir da data em que receber a notificação. O GitHub pode rescindir este Contrato se a Conta do Cliente for suspensa por mais de 90 dias. -#### 4. Efeito da Rescisão +#### 4. Effect of Termination - _Formulários de Pedido._ Após a rescisão deste Contrato, o Cliente não poderá executar outros Formulários de Pedido (se aplicável). No entanto, este Contrato permanecerá em vigor durante o restante do período de qualquer Formulário de Pedido ativo. Quando um Formulário de Pedido é rescindido ou expira, em relação ao Formulário de Pedido: (i) o Termo finaliza imediatamente; (ii) qualquer Licença de Assinatura no Formulário de Pedido será automaticamente rescindida, e o Cliente perderá o direito de utilizar o Serviço; (iii) se alguma Taxa for devida antes da rescisão, o Cliente deverá pagá-la imediatamente; (iv) cada Parte devolverá prontamente (ou destruirá, se a outra Parte assim solicitar) todas as Informações Confidenciais pertencentes à outra Parte, na medida permitida pelo Serviço. Não obstante o acima exposto, o GitHub envidará esforços razoáveis para fornecer ao Cliente uma cópia do Conteúdo de sua conta que seja legal e não infrinja regulamentos mediante pedido; desde que o Cliente faça esse pedido no prazo de 90 dias após o encerramento, suspensão ou downgrade. - O GitHub vai reter e usar as informações do Cliente conforme necessário para cumprir obrigações legais, resolver conflitos e fazer valer os contratos do GitHub; salvo em casos de requisitos legais, o GitHub apagará o perfil do Cliente por completo e o Conteúdo de seus repositórios dentro de 90 dias do cancelamento ou encerramento (embora algumas informações possam permanecer em backups encriptados). Essas informações não podem ser recuperadas depois que a conta do Cliente for cancelada. @@ -270,12 +273,12 @@ 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. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. 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). ### S. Suporte -O GitHub fornecerá suporte técnico padrão para o Serviço sem cobrança adicional, vinte e quatro (24) horas por dia, cinco (5) dias por semana, excluindo fins de semana e feriados americanos. feriados. O Suporte padrão só é oferecido por meio de tíquetes na Web pelo Suporte do GitHub, e as solicitações de Suporte devem ser iniciadas a partir de um Usuário com o qual a equipe de Suporte do GitHub possa interagir. O GitHub pode oferecer Suporte premium (sujeito aos termos do [Suporte Premium para Enterprise Cloud](/articles/about-github-premium-support) ) ou Suporte técnico dedicado para o Serviço no nível de Suporte, Taxas e Termos de Assinatura especificados em um Formulário de Pedido ou SOW. +O GitHub fornecerá suporte técnico padrão para o Serviço sem cobrança adicional, vinte e quatro (24) horas por dia, cinco (5) dias por semana, excluindo fins de semana e feriados americanos. feriados. O Suporte padrão só é oferecido por meio de tíquetes na Web pelo Suporte do GitHub, e as solicitações de Suporte devem ser iniciadas a partir de um Usuário com o qual a equipe de Suporte do GitHub possa interagir. GitHub may provide premium Support (subject to the [GitHub Premium Support for Enterprise Cloud](/articles/about-github-premium-support) terms) or dedicated technical Support for the Service at the Support level, Fees, and Subscription Term specified in an Order Form or SOW. ### T. Disposições Gerais @@ -297,7 +300,7 @@ Se qualquer disposição deste Contrato for considerada ilegal, inválida ou ine #### 6. Alterações; Contrato Completo; Ordem da Precedência Este Contrato só pode ser modificado por uma alteração escrita assinada por um representante autorizado do GitHub, ou por meio de uma postagem do GitHub com uma versão revisada, conforme com a Seção T. Este Contrato representa o contrato completo e exclusivo entre as Partes. Este Contrato substitui qualquer proposta ou contrato prévio oral ou por escrito, e quaisquer outras comunicações entre as Partes relacionadas com o assunto destes termos, incluindo quaisquer acordos de confidencialidade ou não divulgação. 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. -#### 7. Comunicação +#### 7. Publicity Se o Cliente exibir publicamente o nome de sua empresa ou organização em sua conta ou exibir publicamente suas marcas registradas ou logotipos em sua página de perfil, o Cliente permite que o GitHub use o nome de sua empresa ou organização para identificar o Cliente como cliente GitHub em materiais promocionais. O Cliente pode revogar esta permissão ocultando o nome da sua empresa ou organização da exibição pública e notificando por escrito o GitHub para parar de usar o nome da sua organização em materiais promocionais. No entanto, o GitHub não tem nenhuma obrigação de remover ou recolher qualquer uso ou distribuição prévia dos materiais promocionais. #### 8. Força Maior @@ -307,4 +310,4 @@ O GitHub será dispensado da responsabilidade quando não for possível cumprir Cada Parte é um contratado independente no que diz respeito ao objeto deste Contrato. Nada do presente Contrato será considerado ou interpretado de forma a criar uma associação jurídica, parceria, joint venture, emprego, agência, relação fiduciária ou qualquer outra semelhante entre as Partes, e nenhuma Parte poderá vincular a outra contratualmente. #### 10. Perguntas -Perguntas sobre os Termos de Serviço? [Fale conosco](https://github.com/contact/). +Perguntas sobre os Termos de Serviço? [Contact us](https://github.com/contact/). 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 1a0e28548208..5bef77e45494 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 133d214dda34..5c515d90eabd 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. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. 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. +Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service. 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. +GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/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. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 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-privacy-statement.md b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md index fb1d5d2eb5e5..2e517fd3fd1f 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 + +#### Acesso a repositórios privados + +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. + +However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Nossos Termos de Serviço fornecem mais detalhes em [repositórios privados](/github/site-policy/github-terms-of-service#e-private-repositories). -#### Conteúdo do repositório +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). -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). +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. -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. +#### 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. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. 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. +If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. 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). @@ -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. +GitHub uses cookies and similar technologies (e.g., HTML5 localStorage) to make interactions with our service easy and meaningful. Cookies são pequenos arquivos de texto que os sites costumam armazenar nos discos rígidos de computadores ou dispositivos móveis de visitantes. We use cookies and similar technologies (hereafter collectively "cookies") to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of 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. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### 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 05b1c7f992a6..7b1e842e7da2 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. - -Since the number and names of cookies may change,the table below may be updated from time to time. - -| 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 | - -_*_ The **expiration** dates for the cookies listed below generally apply on a rolling basis. - -_**_ 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. - -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). - -(!) 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. +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. + +Como o número e os nomes dos cookies podem mudar, a tabela abaixo pode ser atualizada de vez em quando. + +| 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 | + +_*_ A data de **expiração** para os cookies listados abaixo geralmente se aplicam em uma base contínua. + +_**_ 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. + +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). + +(!) 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 6ee1de86ebb6..f46c443b3145 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 8c1f4a791f73..73555143c977 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) | We may modify this agreement, but we will give you 30 days' notice of material changes. | | [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). +We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub for mobile may be subject to mobile app stores' additional terms. #### 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. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. -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. +This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and 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. +Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. 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.* +**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.* #### 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. +GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/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. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 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. @@ -286,9 +285,9 @@ Se você tiver uma disputa com um ou mais Usuários, você concorda em liberar o Você concorda em nos indenizar, defender-nos e nos manter a parte de e contra quaisquer reivindicações, responsabilidades e despesas, incluindo honorários de advogados, resultantes do seu uso do Site e do Serviço, incluindo, mas não limitado, a sua violação deste Contrato, desde que o GitHub (1) forneça prontamente a você notificação por escrito com a reivindicação, demanda, fato ou procedimento; (2) dê a você o controle exclusivo da defesa e atendimento da reivindicação, demanda, fato ou procedimento (desde que você não possa resolver qualquer reivindicação, demanda, fato ou procedimento, a menos que a resolução libere incondicionalmente o GitHub de toda responsabilidade); e (3) forneça a você assistência razoável, às suas custas. ### 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.* +**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. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.* -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. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. 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/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 966c6b68b940..301577ca6b25 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/using-git/about-git-subtree-merges.md b/translations/pt-BR/content/github/using-git/about-git-subtree-merges.md index c81c4fda1aac..3c0d319be887 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 59d389793e0b..fa56e279dcfe 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 fabbb7bfc425..9478da8f4dea 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/updating-credentials-from-the-macos-keychain.md b/translations/pt-BR/content/github/using-git/updating-credentials-from-the-macos-keychain.md index fa12971044f5..ebc0d000f370 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 d3af5d4197e5..eeb808102c86 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 @@ -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 cb06bb75dee4..11dc1412fd0b 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/viewing-a-projects-contributors.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index 4642bc9b4b40..6bfbf896da15 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,7 +32,7 @@ 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 %} @@ -42,4 +42,4 @@ Se você não aparecer no gráfico de contribuidores de um repositório, pode se 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 5597ba968207..a5ad17ab3659 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 70bf122614e8..df4c0cf6a508 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 aed2ddd6d95c..13985dc1a3ad 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 @@ -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. +**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`. Se ambos os repositórios, `.github.com` e `.github.io` existirem, somente o repositório `.github.io` será publicado. {% endnote %} {% endif %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md index 827175069f34..5968c7e7c20d 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -14,7 +14,7 @@ versions: Pessoas com permissões de gravação para um repositório podem definir um processador markdown para um site do {% data variables.product.prodname_pages %}. -{% data variables.product.prodname_pages %} supports two Markdown processors: [kramdown](http://kramdown.gettalong.org/) and {% data variables.product.prodname_dotcom %}'s own extended [CommonMark](https://commonmark.org/) processor, which is used to render {% data variables.product.prodname_dotcom %} Flavored Markdown throughout {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)". +O {% data variables.product.prodname_pages %} é compatível com dois processadores markdown: [kramdown](http://kramdown.gettalong.org/) e o próprio processador [CommonMark](https://commonmark.org/) estendido do {% data variables.product.prodname_dotcom %}, que é usado para renderizar markdown em estilo {% data variables.product.prodname_dotcom %} em todo o {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)". Você pode usar o markdown em estilo {% data variables.product.prodname_dotcom %} com qualquer um dos processadores, mas apenas o processador CommonMark é que sempre corresponderá aos resultados que você vê no {% data variables.product.product_name %}. diff --git a/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md index c2d58b487df7..e7cab073db47 100644 --- a/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md +++ b/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md @@ -41,12 +41,12 @@ Nas conversas do {% data variables.product.product_name %}, as referências a pr As referências em um hash SHA de commit são convertidas automaticamente em links curtos para o commit no {% data variables.product.product_name %}. -| Tipo de referência | Referência bruta | Link curto | -| ----------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | -| URL do commit | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| Username/Repository@SHA | jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| Tipo de referência | Referência bruta | Link curto | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | +| URL do commit | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| `Username/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | ### Links automáticos personalizados para recursos externos diff --git a/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 511395f85cdd..d4604f6c2396 100644 --- a/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -171,7 +171,7 @@ Para obter mais informações, consulte "[Sobre listas de tarefas](/articles/abo ### Mencionar pessoas e equipes -Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando `@` mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. For more information about notifications, 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 %}." +Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando `@` mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. Para obter mais informações sobre notificaçõ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 %}." `@github/suporte O que você acha dessas atualizações?` diff --git a/translations/pt-BR/content/github/writing-on-github/creating-gists.md b/translations/pt-BR/content/github/writing-on-github/creating-gists.md index 394b29a86c23..6e8f0c638ef8 100644 --- a/translations/pt-BR/content/github/writing-on-github/creating-gists.md +++ b/translations/pt-BR/content/github/writing-on-github/creating-gists.md @@ -18,7 +18,7 @@ Cada gist é um repositório Git, o que significa que ele pode ser bifurcado e c Os gists podem ser públicos ou secretos. Os gists públicos são mostrados no {% data variables.gists.discover_url %}, onde as pessoas podem navegar por novos gists à medida que eles são criados. Eles também são pesquisáveis, de modo que é possível usá-los se desejar que outras pessoas encontrem e vejam seu trabalho. {% data reusables.gist.cannot-convert-public-gists-to-secret %} -Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. {% data reusables.gist.cannot-convert-public-gists-to-secret %} Os gists secretos não são privados. Se você enviar a URL de um gist secreto a uma amigo, ele poderá vê-la. No entanto, se alguém que você não conhece descobrir a URL, ele também poderá ver seu gist. Se precisar manter seu código longe de olhares curiosos, pode ser mais conveniente [criar um repositório privado](/articles/creating-a-new-repository). +Os gists secretos não aparecem em {% data variables.gists.discover_url %} e não são pesquisáveis. {% data reusables.gist.cannot-convert-public-gists-to-secret %} Os gists secretos não são privados. Se você enviar a URL de um gist secreto a uma amigo, ele poderá vê-la. No entanto, se alguém que você não conhece descobrir a URL, ele também poderá ver seu gist. Se precisar manter seu código longe de olhares curiosos, pode ser mais conveniente [criar um repositório privado](/articles/creating-a-new-repository). {% if enterpriseServerVersions contains currentVersion %} 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 bacc1c48ab15..ecd6c5988703 100644 --- a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md @@ -193,6 +193,6 @@ Para obter mais informações sobre como começar com GraphQL, consulte "[Introd 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](/v4/). 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). diff --git a/translations/pt-BR/content/graphql/reference/queries.md b/translations/pt-BR/content/graphql/reference/queries.md index 8ecf2ef0fe9b..5fc1fcaea36c 100644 --- a/translations/pt-BR/content/graphql/reference/queries.md +++ b/translations/pt-BR/content/graphql/reference/queries.md @@ -17,7 +17,7 @@ Para obter mais informações, consulte "[Sobre consultas](/v4/guides/forming-ca {% 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/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 5e7d5ec3b45b..8b2582a91346 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 d6859ecbcca3..226a607c70e4 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/enabling-improved-container-support.md b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md new file mode 100644 index 000000000000..e0793100aaa7 --- /dev/null +++ b/translations/pt-BR/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md @@ -0,0 +1,37 @@ +--- +title: Habilitar suporte ao contêiner aprimorado +intro: 'Para usar {% data variables.product.prodname_github_container_registry %}, você precisa habilitá-lo para a sua conta de usuário ou organização.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +{% 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. 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)." + +{% endnote %} + +### Habilitar {% data variables.product.prodname_github_container_registry %} para sua conta pessoal + +Uma vez que {% data variables.product.prodname_github_container_registry %} está habilitado para a sua conta pessoal de usuário, você pode publicar contêineres em {% data variables.product.prodname_github_container_registry %} que pertencem à sua conta de usuário. + +Para usar {% data variables.product.prodname_github_container_registry %} em uma organização, o dono da organização deve habilitar o recurso para os integrantes da organização. + +{% data reusables.feature-preview.feature-preview-setting %} +2. À esquerda, selecione "Suporte ao contêiner aprimorado" e, em seguida, clique em **Habilitar**. ![Suporte ao contêiner aprimorado](/assets/images/help/settings/improved-container-support.png) + +### Habilitar {% data variables.product.prodname_github_container_registry %} para a conta da sua organização + +Antes que os proprietários ou integrantes da organização possam publicar imagens do contêiner para {% data variables.product.prodname_github_container_registry %}, um proprietário da organização deve habilitar a pré-visualização do recurso para a organização. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. À esquerda, clique em **Pacotes**. +5. Em "Melhorar suporte ao container", selecione "Suporte ao contêiner aprimorado" e clique em **Salvar**. ![Opção de habilitar suporte de registro do contêiner e botão de salvar](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Em "Criação de contêiner", escolha se deseja habilitar a criação de imagens de recipientes públicas e/ou privadas. + - Para permitir que os integrantes da organização criem imagens de contêiner público, clique em **Público**. + - Para permitir que os integrantes da organização criem imagens privadas de contêiner visíveis apenas para outros integrantes da organização, clique em **Privado**. Você pode personalizar ainda mais a visibilidade de imagens de contêiner privado. 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)". + + ![Opções para habilitar pacotes públicos ou privados ](/assets/images/help/package-registry/package-creation-org-settings.png) 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 590004babf39..82c9d80a8a39 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 bf45b9e0e2cd..d0db4cbcb87d 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 51e488f358e1..5a888af734ac 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 219b1816244b..8c1ed3bc4982 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,8 +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 %} 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 50e25039f030..07cb027cbab9 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 d02bf8560b7f..eebeb30a21f9 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. 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 c1ae0b5aa209..545c84e3a160 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,7 +31,7 @@ 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 %} 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 70caf35ea7b1..6c1863a054b7 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 @@ -22,7 +22,7 @@ Você pode ajudar as pessoas a entender e usar seu pacote fornecendo uma descri {% 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-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 e0683ef90257..6d563a046e55 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 90b442cc99ba..92f6b395159e 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/rest/guides/basics-of-authentication.md b/translations/pt-BR/content/rest/guides/basics-of-authentication.md index ebbd031289a4..e241e7db96b6 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. 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 ffab348d3fa8..96592880f7c6 100644 --- a/translations/pt-BR/content/rest/overview/other-authentication-methods.md +++ b/translations/pt-BR/content/rest/overview/other-authentication-methods.md @@ -37,12 +37,22 @@ $ 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" %} + +{% 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 %} -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. +{% 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.) @@ -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,7 +123,6 @@ $ curl --request POST \ ``` {% endif %} -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization [curl]: http://curl.haxx.se/ [oauth-auth]: /v3/#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line 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 0f685dbf910e..dc52c2431d2b 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 @@ -135,9 +135,9 @@ $ 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`: ```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" @@ -165,19 +165,10 @@ $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product. 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: ```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 %} - -{% note %} - -**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. - -{% endnote %} - -{% endif %} - ### IDs de nós globais do GraphQL 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. diff --git a/translations/pt-BR/content/rest/overview/troubleshooting.md b/translations/pt-BR/content/rest/overview/troubleshooting.md index f0cfcfd6d2de..d571f3c44ffd 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. +{% 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/interactions.md b/translations/pt-BR/content/rest/reference/interactions.md index 38a825112d21..39199f965acb 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/oauth-authorizations.md b/translations/pt-BR/content/rest/reference/oauth-authorizations.md index 5c84f6084fe6..8a9ca5c0da48 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/search.md b/translations/pt-BR/content/rest/reference/search.md index d6abb35ef410..e70f5c19c3ef 100644 --- a/translations/pt-BR/content/rest/reference/search.md +++ b/translations/pt-BR/content/rest/reference/search.md @@ -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/data/graphql/ghae/graphql_previews.ghae.yml b/translations/pt-BR/data/graphql/ghae/graphql_previews.ghae.yml index 4c27ac9fe47f..849d74eb1d22 100644 --- a/translations/pt-BR/data/graphql/ghae/graphql_previews.ghae.yml +++ b/translations/pt-BR/data/graphql/ghae/graphql_previews.ghae.yml @@ -85,7 +85,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Visualização de Issues fixados description: Esta visualização adiciona suporte para os issues fixos. 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 5bfa10d0b25a..344e4d9d970f 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 @@ -2,112 +2,112 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso." - reason: "`availableSeats` serão substituídos por 'totalAvailableLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso.' + reason: '`availableSeats` serão substituídos por ''totalAvailableLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso." - reason: "`seats` serão substituídos por 'totalLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso.' + reason: '`seats` serão substituídos por ''totalLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso." - reason: "`Sponsorship.maintainer` será removido." + description: '`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso.' + reason: '`Sponsorship.maintainer` será removido.' date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os integrantes pendentes consomem uma licença date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso." + description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.' reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` será removido. Use Issue.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use Issue.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` será removido. Use PullRequest.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` será removido." - reason: "`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado." + description: '`INVITEE_LOGIN` será removido.' + reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso." - reason: "`Sponsorship.sponsor` será removido." + description: '`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso.' + reason: '`Sponsorship.sponsor` será removido.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os integrantes consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os colaboradores externos consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os colaboradores pendentes consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "O `DRAFT` será removido. Use PullRequest.isDraft." + description: 'O `DRAFT` será removido. Use PullRequest.isDraft.' reason: O status DRAFT será removido deste enum e o `isDraft` deverá ser usado date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/pt-BR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml b/translations/pt-BR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml index 09088eb68b48..619733e638b0 100644 --- a/translations/pt-BR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/pt-BR/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml @@ -2,63 +2,63 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "'field' será removido. Apenas um campo de pedido é suportado." - reason: "`field` será removido." + description: '''field'' será removido. Apenas um campo de pedido é suportado.' + reason: '`field` será removido.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` será removido. Use Issue.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use Issue.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` será removido. Use PullRequest.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: UnassignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/pt-BR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/pt-BR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml index 1fe25f35544a..b5c4b59c3c7c 100644 --- a/translations/pt-BR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/pt-BR/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml @@ -2,560 +2,560 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "'field' será removido. Apenas um campo de pedido é suportado." - reason: "`field` será removido." + description: '''field'' será removido. Apenas um campo de pedido é suportado.' + reason: '`field` será removido.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` será removido. Use Issue.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use Issue.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` será removido. Use PullRequest.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso." - reason: "`availableSeats` serão substituídos por 'totalAvailableLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso.' + reason: '`availableSeats` serão substituídos por ''totalAvailableLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso." - reason: "`seats` serão substituídos por 'totalLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso.' + reason: '`seats` serão substituídos por ''totalLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` será removido. Use o objeto `Package` em vez disso." + description: '`color` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` será removido. Use o objeto `Package` em vez disso." + description: '`latestVersion` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` será removido. Use o objeto `Package` em vez disso." + description: '`name` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` será removido. Use o objeto `Package` em vez disso." + description: '`nameWithOwner` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` será removido. Use o objeto `Package`." + description: '`packageFileByGuid` será removido. Use o objeto `Package`.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` será removido. Use o objeto `Package`." + description: '`packageFileBySha256` será removido. Use o objeto `Package`.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` será removido. Use o objeto `Package` em vez disso." + description: '`packageType` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` será removido. Use o objeto `Package` em vez disso." + description: '`preReleaseVersions` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` será removido. Use o objeto `Package` em vez disso." + description: '`registryPackageType` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` será removido. Use o objeto `Package` em vez disso." + description: '`repository` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` será removido. Use o objeto `Package` em vez disso." + description: '`statistics` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` serão removidas. Use o objeto `Package` em vez disso." + description: '`tags` serão removidas. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` serão removidos. Use o objeto `Package`." + description: '`topics` serão removidos. Use o objeto `Package`.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` será removido. Use o objeto `Package` em vez disso." + description: '`version` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` será removido. Use o objeto `Package` em vez disso." + description: '`versionByPlatform` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` será removido. Use o objeto `Package` em vez disso." + description: '`versionBySha256` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` serão removidas. Use o objeto `Package` em vez disso." + description: '`versions` serão removidas. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` será removido. Use o objeto `Package` em vez disso." + description: '`versionsByMetadatum` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` será removido. Use o objeto `PackageDependency` em vez disso." + description: '`dependencyType` será removido. Use o objeto `PackageDependency` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` será removido. Use o objeto `PackageDependency` em vez disso." + description: '`name` será removido. Use o objeto `PackageDependency` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` será removido. Use o objeto `PackageDependency` em vez disso." + description: '`version` será removido. Use o objeto `PackageDependency` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "'guid' será removido. Use o objeto 'PackageFile' em vez disso." + description: '''guid'' será removido. Use o objeto ''PackageFile'' em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` será removido. Use o objeto `PackageFile` em vez disso." + description: '`md5` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` será removido. Use o objeto `PackageFile` em vez disso." + description: '`metadataUrl` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` será removido. Use o objeto `PackageFile` em vez disso." + description: '`name` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` será removido. Use o objeto `PackageFile` em vez disso." + description: '`packageVersion` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` será removido. Use o objeto `PackageFile` em vez disso." + description: '`sha1` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` será removido. Use o objeto `PackageFile` em vez disso." + description: '`sha256` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` será removido. Use o objeto `PackageFile` em vez disso." + description: '`size` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` será removido. Use o objeto `PackageFile` em vez disso." + description: '`url` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` serão removidos. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsThisMonth` serão removidos. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` será removido. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsThisWeek` será removido. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` será removido. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsThisYear` será removido. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` serão removidos. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsToday` serão removidos. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` será removido. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsTotalCount` será removido. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` será removido. Use o objeto `PackageTag` em vez disso." + description: '`name` será removido. Use o objeto `PackageTag` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` será removido. Use o objeto `PackageTag` em vez disso." + description: '`version` será removido. Use o objeto `PackageTag` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`dependencies` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`fileByName` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`files` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`installationCommand` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`manifest` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`platform` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`preRelease` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`readme` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`readmeHtml` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`registryPackage` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`release` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`sha256` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`size` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`statistics` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`summary` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`updatedAt` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`version` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`viewerCanEdit` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` serão removidos. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsThisMonth` serão removidos. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsThisWeek` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsThisYear` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsToday` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsTotalCount` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso." - reason: "`Sponsorship.maintainer` será removido." + description: '`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso.' + reason: '`Sponsorship.maintainer` será removido.' date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking diff --git a/translations/pt-BR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/pt-BR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml index 69ac02366d06..1f91ef2f6b7a 100644 --- a/translations/pt-BR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/pt-BR/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml @@ -2,568 +2,568 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "'field' será removido. Apenas um campo de pedido é suportado." - reason: "`field` será removido." + description: '''field'' será removido. Apenas um campo de pedido é suportado.' + reason: '`field` será removido.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso." + description: '`pinnedRepositories` será removido. Use ProfileOwner.pinnedItems em vez disso.' reason: pinnedRepositories será removido date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso." - reason: "`availableSeats` serão substituídos por 'totalAvailableLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso.' + reason: '`availableSeats` serão substituídos por ''totalAvailableLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso." - reason: "`seats` serão substituídos por 'totalLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso.' + reason: '`seats` serão substituídos por ''totalLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` será removido. Use o objeto `Package` em vez disso." + description: '`color` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` será removido. Use o objeto `Package` em vez disso." + description: '`latestVersion` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` será removido. Use o objeto `Package` em vez disso." + description: '`name` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` será removido. Use o objeto `Package` em vez disso." + description: '`nameWithOwner` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` será removido. Use o objeto `Package`." + description: '`packageFileByGuid` será removido. Use o objeto `Package`.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` será removido. Use o objeto `Package`." + description: '`packageFileBySha256` será removido. Use o objeto `Package`.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` será removido. Use o objeto `Package` em vez disso." + description: '`packageType` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` será removido. Use o objeto `Package` em vez disso." + description: '`preReleaseVersions` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` será removido. Use o objeto `Package` em vez disso." + description: '`registryPackageType` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` será removido. Use o objeto `Package` em vez disso." + description: '`repository` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` será removido. Use o objeto `Package` em vez disso." + description: '`statistics` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` serão removidas. Use o objeto `Package` em vez disso." + description: '`tags` serão removidas. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` serão removidos. Use o objeto `Package`." + description: '`topics` serão removidos. Use o objeto `Package`.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` será removido. Use o objeto `Package` em vez disso." + description: '`version` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` será removido. Use o objeto `Package` em vez disso." + description: '`versionByPlatform` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` será removido. Use o objeto `Package` em vez disso." + description: '`versionBySha256` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` serão removidas. Use o objeto `Package` em vez disso." + description: '`versions` serão removidas. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` será removido. Use o objeto `Package` em vez disso." + description: '`versionsByMetadatum` será removido. Use o objeto `Package` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` será removido. Use o objeto `PackageDependency` em vez disso." + description: '`dependencyType` será removido. Use o objeto `PackageDependency` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` será removido. Use o objeto `PackageDependency` em vez disso." + description: '`name` será removido. Use o objeto `PackageDependency` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` será removido. Use o objeto `PackageDependency` em vez disso." + description: '`version` será removido. Use o objeto `PackageDependency` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "'guid' será removido. Use o objeto 'PackageFile' em vez disso." + description: '''guid'' será removido. Use o objeto ''PackageFile'' em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` será removido. Use o objeto `PackageFile` em vez disso." + description: '`md5` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` será removido. Use o objeto `PackageFile` em vez disso." + description: '`metadataUrl` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` será removido. Use o objeto `PackageFile` em vez disso." + description: '`name` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` será removido. Use o objeto `PackageFile` em vez disso." + description: '`packageVersion` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` será removido. Use o objeto `PackageFile` em vez disso." + description: '`sha1` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` será removido. Use o objeto `PackageFile` em vez disso." + description: '`sha256` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` será removido. Use o objeto `PackageFile` em vez disso." + description: '`size` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` será removido. Use o objeto `PackageFile` em vez disso." + description: '`url` será removido. Use o objeto `PackageFile` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` serão removidos. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsThisMonth` serão removidos. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` será removido. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsThisWeek` será removido. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` será removido. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsThisYear` será removido. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` serão removidos. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsToday` serão removidos. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` será removido. Use o objeto `PackageStatistics` em vez disso." + description: '`downloadsTotalCount` será removido. Use o objeto `PackageStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` será removido. Use o objeto `PackageTag` em vez disso." + description: '`name` será removido. Use o objeto `PackageTag` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` será removido. Use o objeto `PackageTag` em vez disso." + description: '`version` será removido. Use o objeto `PackageTag` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.deleted - description: "`deleted` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`deleted` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`dependencies` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`fileByName` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`files` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`installationCommand` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`manifest` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`platform` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`preRelease` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`readme` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`readmeHtml` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`registryPackage` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`release` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`sha256` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`size` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`statistics` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`summary` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`updatedAt` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`version` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` será removido. Use o objeto `PackageVersion` em vez disso." + description: '`viewerCanEdit` será removido. Use o objeto `PackageVersion` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` serão removidos. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsThisMonth` serão removidos. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsThisWeek` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsThisYear` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsToday` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` será removido. Use o objeto `PackageVersionStatistics` em vez disso." + description: '`downloadsTotalCount` será removido. Use o objeto `PackageVersionStatistics` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso." - reason: "`Sponsorship.maintainer` será removido." + description: '`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso.' + reason: '`Sponsorship.maintainer` será removido.' date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso." + description: '`registryPackages` será removido. Use o objeto `PackageOwner` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso." + description: '`registryPackagesForQuery` será removido. Use o objeto `PackageSearch` em vez disso.' reason: Renomeando campos e objetos de pacotes GitHub. date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` será removido. Use Issue.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use Issue.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` será removido. Use PullRequest.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea diff --git a/translations/pt-BR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/pt-BR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml index 91b11368a7aa..a4f5d93ca89b 100644 --- a/translations/pt-BR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/pt-BR/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml @@ -2,71 +2,71 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso." - reason: "`availableSeats` serão substituídos por 'totalAvailableLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso.' + reason: '`availableSeats` serão substituídos por ''totalAvailableLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso." - reason: "`seats` serão substituídos por 'totalLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso.' + reason: '`seats` serão substituídos por ''totalLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso." - reason: "`Sponsorship.maintainer` será removido." + description: '`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso.' + reason: '`Sponsorship.maintainer` será removido.' date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os integrantes pendentes consomem uma licença date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso." + description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.' reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` será removido. Use Issue.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use Issue.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` será removido. Use PullRequest.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea @@ -86,15 +86,15 @@ upcoming_changes: owner: oneill38 - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` será removido." - reason: "`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado." + description: '`INVITEE_LOGIN` será removido.' + reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso." - reason: "`Sponsorship.sponsor` será removido." + description: '`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso.' + reason: '`Sponsorship.sponsor` será removido.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden @@ -107,21 +107,21 @@ upcoming_changes: owner: oneill38 - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os integrantes consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os colaboradores externos consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os colaboradores pendentes consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/pt-BR/data/graphql/graphql_previews.yml b/translations/pt-BR/data/graphql/graphql_previews.yml index cfc098df73de..f6139b75aa8b 100644 --- a/translations/pt-BR/data/graphql/graphql_previews.yml +++ b/translations/pt-BR/data/graphql/graphql_previews.yml @@ -102,7 +102,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Visualização de Issues fixados description: Esta visualização adiciona suporte para os issues fixos. 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 28214733f095..3c2133cdcbaf 100644 --- a/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml @@ -2,119 +2,119 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso." - reason: "`availableSeats` serão substituídos por 'totalAvailableLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso.' + reason: '`availableSeats` serão substituídos por ''totalAvailableLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso." - reason: "`seats` serão substituídos por 'totalLicenses' para fornecer mais clareza sobre o valor que está sendo devolvido" + description: '`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso.' + reason: '`seats` serão substituídos por ''totalLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` será removido. Use o campo `assignee`." + description: '`user` será removido. Use o campo `assignee`.' reason: Os responsáveis podem agora ser mannequines. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Query.sponsorsListing - description: "`sponsorsListing` será removido. `Sponsorable.sponsorsListing`." - reason: "`Query.sponsorsListing` será removido." + description: '`sponsorsListing` será removido. `Sponsorable.sponsorsListing`.' + reason: '`Query.sponsorsListing` será removido.' date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: antn - location: Sponsorship.maintainer - description: "`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso." - reason: "`Sponsorship.maintainer` será removido." + description: '`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso.' + reason: '`Sponsorship.maintainer` será removido.' date: 'RegistryPackageDependency.dependencyType' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os integrantes pendentes consomem uma licença date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso." + description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.' reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` será removido. Use Issue.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use Issue.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` será removido. Use PullRequest.timelineItems em vez disso." - reason: "`timeline` será removido" + description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.' + reason: '`timeline` será removido' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` será removido." - reason: "`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado." + description: '`INVITEE_LOGIN` será removido.' + reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso." - reason: "`Sponsorship.sponsor` será removido." + description: '`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso.' + reason: '`Sponsorship.sponsor` será removido.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os integrantes consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os colaboradores externos consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` será removido." + description: '`isUnlicensed` será removido.' reason: Todos os colaboradores pendentes consomem uma licença date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "O `DRAFT` será removido. Use PullRequest.isDraft." + description: 'O `DRAFT` será removido. Use PullRequest.isDraft.' reason: O status DRAFT será removido deste enum e o `isDraft` deverá ser usado date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/pt-BR/data/reusables/feature-preview/feature-preview-setting.md b/translations/pt-BR/data/reusables/feature-preview/feature-preview-setting.md new file mode 100644 index 000000000000..e70e9012ebcb --- /dev/null +++ b/translations/pt-BR/data/reusables/feature-preview/feature-preview-setting.md @@ -0,0 +1 @@ +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) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md new file mode 100644 index 000000000000..bd279034eee8 --- /dev/null +++ b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md @@ -0,0 +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 %} diff --git a/translations/pt-BR/data/reusables/interactions/interactions-detail.md b/translations/pt-BR/data/reusables/interactions/interactions-detail.md index 06f68fdb071d..187a3e73074d 100644 --- a/translations/pt-BR/data/reusables/interactions/interactions-detail.md +++ b/translations/pt-BR/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -Quando as restrições são ativadas, apenas o grupo especificado de {% data variables.product.product_name %} os usuários serão capazes de participar de interações. As restrições expiram 24 horas a partir do momento que são estabelecidas. +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. 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 bcd2bc692f75..bbc99f348abf 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. 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. 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)." +**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)." {% endnote %} 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 new file mode 100644 index 000000000000..175131b3b694 --- /dev/null +++ b/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -0,0 +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)". + +{% endnote %} \ No newline at end of file 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 cadca78570ff..9b41c813bd12 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. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." +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)". diff --git a/translations/pt-BR/data/reusables/search/syntax_tips.md b/translations/pt-BR/data/reusables/search/syntax_tips.md index d38c9fc6b9db..38697327fd2c 100644 --- a/translations/pt-BR/data/reusables/search/syntax_tips.md +++ b/translations/pt-BR/data/reusables/search/syntax_tips.md @@ -1,6 +1,6 @@ {% 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. diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta.md b/translations/pt-BR/data/reusables/secret-scanning/beta.md index 2c7ead33b1a5..e4664002b63f 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/beta.md +++ b/translations/pt-BR/data/reusables/secret-scanning/beta.md @@ -1,5 +1,5 @@ {% note %} -**Observação:** {% data variables.product.prodname_secret_scanning_caps %} para repositórios privados está atualmente em beta e sujeitos a alterações. Para solicitar acesso ao beta, [join the waitlist](https://github.com/features/security/advanced-security/signup). +**Observação:** {% data variables.product.prodname_secret_scanning_caps %} para repositórios privados está atualmente em beta e sujeitos a alterações. {% endnote %} diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml index 620c5952e48d..a008706277db 100644 --- a/translations/pt-BR/data/ui.yml +++ b/translations/pt-BR/data/ui.yml @@ -4,9 +4,10 @@ header: contact: Contato notices: ghae_silent_launch: GitHub AE is currently under limited release. Please contact our Sales Team to find out more. + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco. localization_in_progress: Olá! No momento, esta página ainda está sendo desenvolvida ou traduzida. Para obter as informações mais recentes, acesse a documentação em inglês. - product_in_progress: '👋 Olá, explorador! Esta página está em desenvolvimento ativo. Para obter as informações mais atualizadas e precisas, visite nossa documentação do desenvolvedor.' + early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' search: need_help: Precisa de ajuda? placeholder: Pesquisar tópicos, produtos... @@ -19,7 +20,7 @@ toc: guides: Guias whats_new: O que há de novo pages: - article_version: "Versão do artigo:" + article_version: 'Versão do artigo:' miniToc: Neste artigo errors: oops: Ops! diff --git a/translations/pt-BR/data/variables/action_code_examples.yml b/translations/pt-BR/data/variables/action_code_examples.yml new file mode 100644 index 000000000000..6f6e4b4e71fe --- /dev/null +++ b/translations/pt-BR/data/variables/action_code_examples.yml @@ -0,0 +1,149 @@ +--- +- + title: Starter workflows + description: Workflow files for helping people get started with GitHub Actions + languages: TypeScript + href: actions/starter-workflows + tags: + - official + - fluxos de trabalho +- + title: Example services + description: Example workflows using service containers + languages: JavaScript + href: actions/example-services + tags: + - service containers +- + title: Declaratively setup GitHub Labels + description: GitHub Action to declaratively setup labels across repos + languages: JavaScript + href: lannonbr/issue-label-manager-action + tags: + - Problemas + - etiquetas +- + title: Declaratively sync GitHub labels + description: GitHub Action to sync GitHub labels in the declarative way + languages: 'Go, Dockerfile' + href: micnncim/action-label-syncer + tags: + - Problemas + - etiquetas +- + title: Add releases to GitHub + description: Publish Github releases in an action + languages: 'Dockerfile, Shell' + href: elgohr/Github-Release-Action + tags: + - releases + - publishing +- + title: Publish a docker image to Dockerhub + description: A Github Action used to build and publish Docker images + languages: 'Dockerfile, Shell' + href: elgohr/Publish-Docker-Github-Action + tags: + - docker + - publishing + - build +- + title: Create an issue using content from a file + description: A GitHub action to create an issue using content from a file + languages: 'JavaScript, Python' + href: peter-evans/create-issue-from-file + tags: + - Problemas +- + title: Publish GitHub Releases with Assets + description: GitHub Action for creating GitHub Releases + languages: 'TypeScript, Shell, JavaScript' + href: softprops/action-gh-release + tags: + - releases + - publishing +- + title: GitHub Project Automation+ + description: Automate GitHub Project cards with any webhook event. + languages: JavaScript + href: alex-page/github-project-automation-plus + tags: + - projetos + - automation + - Problemas + - Pull requests +- + title: Run GitHub Actions Locally with a web interface + description: Runs GitHub Actions workflows locally (local) + languages: 'JavaScript, HTML, Dockerfile, CSS' + href: phishy/wflow + tags: + - local-development + - devops + - docker +- + title: Run your GitHub Actions locally + description: Run GitHub Actions Locally in Terminal + languages: 'Go, Shell' + href: nektos/act + tags: + - local-development + - devops + - docker +- + title: Build and Publish Android debug APK + description: Build and release debug APK from your Android project + languages: 'Shell, Dockerfile' + href: ShaunLWM/action-release-debugapk + tags: + - android + - build +- + title: Generate sequential build numbers for GitHub Actions + description: GitHub action for generating sequential build numbers. + languages: JavaScript + href: einaregilsson/build-number + tags: + - build + - automation +- + title: GitHub actions to push back to repository + description: Push Git changes to GitHub repository without authentication difficulties + languages: 'JavaScript, Shell' + href: ad-m/github-push-action + tags: + - publishing +- + title: Generate release notes based on your events + description: Action to auto generate a release note based on your events + languages: 'Shell, Dockerfile' + href: Decathlon/release-notes-generator-action + tags: + - releases + - publishing +- + title: Create a GitHub wiki page based on the provided markdown file + description: Create a GitHub wiki page based on the provided markdown file + languages: 'Shell, Dockerfile' + href: Decathlon/wiki-page-creator-action + tags: + - wiki + - publishing +- + title: 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: + - projetos + - Problemas + - etiquetas +- + title: Add Label to your Pull Requests based on the author team name + description: Github action to label your pull requests based on the author name + languages: 'TypeScript, JavaScript' + href: JulienKode/team-labeler-action + tags: + - pull request + - etiquetas diff --git a/translations/pt-BR/data/variables/contact.yml b/translations/pt-BR/data/variables/contact.yml index acec5c159283..84bcada7bb03 100644 --- a/translations/pt-BR/data/variables/contact.yml +++ b/translations/pt-BR/data/variables/contact.yml @@ -10,7 +10,7 @@ contact_dmca: >- {% if currentVersion == "free-pro-team@latest" %}[Formulário de reivindicação de direitos autorais](https://github.com/contact/dmca){% endif %} contact_privacy: >- {% if currentVersion == "free-pro-team@latest" %}[Formulário de contato com a equipe de privacidade](https://github.com/contact/privacy){% endif %} -contact_enterprise_sales: '[Equipe de Vendas do GitHub](https://enterprise.github.com/contact)' +contact_enterprise_sales: "[Equipe de Vendas do GitHub](https://enterprise.github.com/contact)" contact_feedback_actions: '[Formulário de feedback do GitHub Actions](https://support.github.com/contact/feedback?contact[category]=actions)' #The team that provides Standard Support enterprise_support: 'Suporte do GitHub Enterprise' diff --git a/translations/pt-BR/data/variables/release_candidate.yml b/translations/pt-BR/data/variables/release_candidate.yml new file mode 100644 index 000000000000..ec65ef6f9445 --- /dev/null +++ b/translations/pt-BR/data/variables/release_candidate.yml @@ -0,0 +1,2 @@ +--- +version: '' 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 55fe27ec0f77..c8f14f7675e8 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 @@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - potatoqualitee --- {% data reusables.actions.enterprise-beta %} 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 new file mode 100644 index 000000000000..1a8c4f6d86cc --- /dev/null +++ b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md @@ -0,0 +1,318 @@ +--- +title: Building and testing Ruby +intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introduction + +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. + +### Требования + +We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. Дополнительные сведения см. в: + +- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions) +- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) + +### Starting with the Ruby workflow template + +{% 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). + +To get started quickly, add the template to the `.github/workflows` directory of your repository. + +{% raw %} +```yaml +name: Ruby + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: 2.6 + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Specifying the Ruby version + +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). + +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. + +The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 # Not needed with a .ruby-version file +- run: bundle install +- run: bundle exec rake +``` +{% 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. + +### Testing with multiple versions of 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. + +{% raw %} +```yaml +strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] +``` +{% 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." + +The full updated workflow with a matrix strategy could look like this: + +{% raw %} +```yaml +name: Ruby CI + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby ${{ matrix.ruby-version }} + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: ${{ matrix.ruby-version }} + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Installing dependencies with 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. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 +- run: bundle install +``` +{% endraw %} + +#### Caching dependencies + +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 +steps: +- uses: ruby/setup-ruby@v1 + with: + bundler-cache: true +``` +{% 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. + +**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)." + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + ${{ runner.os }}-gems- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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: + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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. + +{% raw %} +```yaml +name: Matrix Testing + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + runs-on: ${{ matrix.os }}-latest + strategy: + fail-fast: false + matrix: + os: [ubuntu, macos] + ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head] + continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }} + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: ${{ matrix.ruby }} + - run: bundle install + - run: bundle exec rake +``` +{% 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. + +{% raw %} +```yaml +name: Linting + +on: [push] + +jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + - name: Rubocop + run: rubocop +``` +{% endraw %} + +### Publishing Gems + +You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. + +You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. + +{% raw %} +```yaml + +name: Ruby Gem + +on: + # Manually publish + workflow_dispatch: + # Alternatively, publish whenever changes are merged to the default branch. + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + build: + name: Build + Publish + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby 2.6 + uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + + - name: Publish to GPR + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem + env: + GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}" + OWNER: ${{ github.repository_owner }} + + - name: Publish to RubyGems + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push *.gem + env: + GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" +``` +{% endraw %} + diff --git a/translations/ru-RU/content/actions/guides/index.md b/translations/ru-RU/content/actions/guides/index.md index 506ca7e9c55c..4a0e3a32c74b 100644 --- a/translations/ru-RU/content/actions/guides/index.md +++ b/translations/ru-RU/content/actions/guides/index.md @@ -31,6 +31,7 @@ You can use {% data variables.product.prodname_actions %} to create custom conti {% 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/ru-RU/content/actions/guides/publishing-nodejs-packages.md b/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md index 8069dc936c7d..6fcd92f8fc97 100644 --- a/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ru-RU/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/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index b04280b5701c..2e25b7201b80 100644 --- a/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ru-RU/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/ru-RU/content/actions/index.md b/translations/ru-RU/content/actions/index.md index 0f0516da0816..a52b17016f01 100644 --- a/translations/ru-RU/content/actions/index.md +++ b/translations/ru-RU/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 - date: '2020-10-16' - href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ + title: Removing set-env and add-path commands on November 16 + date: '2020-11-09' + href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - 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: Ubuntu-latest workflows will use 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: 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: MacOS Big Sur Preview + date: '2020-10-29' + href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview - - 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 + title: Self-Hosted Runner Group Access Changes + date: '2020-10-16' + href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ 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 %}
-

More guides

+

Code examples

+ +
+ +
-
- -
-

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 -
- -
+ {% render 'code-example-card' for actionsCodeExamples as example %}
- Show all guides {% octicon "arrow-right" %} + + +
+
{% octicon "search" width="24" %}
+

Sorry, there is no result for

+

It looks like we don't have an example that fits your filter.
Try another filter or add your code example

+ Learn how to add a code example {% octicon "arrow-right" %} +
+{% endif %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md index 3894421fc66c..345235b2522a 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -42,7 +42,7 @@ A job is a set of steps that execute on the same runner. By default, a workflow #### Steps -A step is an individual task that can run commands (known as _actions_). Each step in a job executes on the same runner, allowing the actions in that job to share data with each other. +A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. Each step in a job executes on the same runner, allowing the actions in that job to share data with each other. #### Actions @@ -50,7 +50,7 @@ _Actions_ are standalone commands that are combined into _steps_ to create a _jo #### Runners -A runner is a server that has the {% data variables.product.prodname_actions %} runner application installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment. +A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS. For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)." @@ -197,7 +197,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s #### Visualizing the workflow file -In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action. Steps 1 and 2 use prebuilt community actions. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." +In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell command. Steps 1 and 2 use prebuilt community actions. Steps 3 and 4 run shell commands directly on the runner. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." ![Workflow overview](/assets/images/help/images/overview-actions-event.png) diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md index 14b5d9226820..5c46ed4da575 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ru-RU/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/ru-RU/content/actions/quickstart.md b/translations/ru-RU/content/actions/quickstart.md index 6a5653008111..803a2f1f9ce6 100644 --- a/translations/ru-RU/content/actions/quickstart.md +++ b/translations/ru-RU/content/actions/quickstart.md @@ -73,3 +73,69 @@ The super-linter workflow you just added runs any time code is pushed to your re - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial - "[Guides](/actions/guides)" for specific uses cases and examples - [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action + + 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 90beda5904b6..61dd7738cba1 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 @@ -327,6 +327,7 @@ The `issue_comment` event occurs for comments on both issues and pull requests. 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 @@ -349,6 +350,7 @@ jobs: - run: | echo "Comment on issue #${{ github.event.issue.number }}" ``` +{% endraw %} #### `issues` diff --git a/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md index 0b08d1c3e64a..5adf188b42b5 100644 --- a/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md @@ -31,7 +31,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl {% data variables.product.prodname_dotcom %} hosts Linux and Windows runners on Standard_DS2_v2 virtual machines in Microsoft Azure with the {% data variables.product.prodname_actions %} runner application installed. The {% data variables.product.prodname_dotcom %}-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation. -{% data variables.product.prodname_dotcom %} uses [MacStadium](https://www.macstadium.com/) to host the macOS runners. +{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud. #### Administrative privileges of {% data variables.product.prodname_dotcom %}-hosted runners 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 8cdef8a5bc34..b68997495c83 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 @@ -446,7 +446,7 @@ 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`** @@ -492,7 +492,7 @@ 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 @@ -659,7 +659,7 @@ For built-in shell keywords, we provide the following defaults that are executed - `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. + - `cmd.exe` will exit with the error level of the last program it executed, and it will 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. #### **`jobs..steps.with`** @@ -718,7 +718,7 @@ 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. +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. #### **`jobs..steps.env`** diff --git a/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index d0208d6cd1d5..b3049bad1813 100644 --- a/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -28,16 +28,7 @@ To configure authentication and user provisioning for {% data variables.product. {% 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. - - | 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 Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. 1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. diff --git a/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md index 8a69a18c4af7..08c9c2058232 100644 --- a/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md @@ -38,6 +38,12 @@ After a user successfully authenticates on your IdP, the user's SAML session for {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} +The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | More information | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs | + 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. | Value | Other names | Description | Пример | diff --git a/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index af1a05ff4965..a1e4ad57aecc 100644 --- a/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -62,7 +62,15 @@ You must have administrative access on your IdP to configure the application for {% 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. Click **Save**. ![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. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. + + The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + + | IdP | More information | + |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs | + + The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}. | Value | Other names | Description | Пример | |:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- | diff --git a/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md b/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md index ad93892dc52c..908f264c813b 100644 --- a/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md +++ b/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md @@ -11,7 +11,7 @@ versions: ### Set up an external `collectd` server -If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.product.product_location %}. Your `collectd` server must by running `collectd` version 5.x or higher. +If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.product.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher. 1. Log into your `collectd` server. 2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf` diff --git a/translations/ru-RU/content/admin/packages/configuring-third-party-storage-for-packages.md b/translations/ru-RU/content/admin/packages/configuring-third-party-storage-for-packages.md index 523834c7e440..2a7e32e8c90d 100644 --- a/translations/ru-RU/content/admin/packages/configuring-third-party-storage-for-packages.md +++ b/translations/ru-RU/content/admin/packages/configuring-third-party-storage-for-packages.md @@ -21,7 +21,10 @@ For the best experience, we recommend using a dedicated bucket for {% data varia {% warning %} -**Warning:** Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. +**Warnings:** +- 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. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} diff --git a/translations/ru-RU/content/admin/packages/index.md b/translations/ru-RU/content/admin/packages/index.md index d677721898a2..2c1a7b4d0c1f 100644 --- a/translations/ru-RU/content/admin/packages/index.md +++ b/translations/ru-RU/content/admin/packages/index.md @@ -1,6 +1,5 @@ --- title: Managing GitHub Packages for your enterprise -shortTitle: GitHub Packages intro: 'You can enable {% data variables.product.prodname_registry %} for your enterprise and manage {% data variables.product.prodname_registry %} settings and allowed packaged types.' redirect_from: - /enterprise/admin/packages diff --git a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md index 5c4c09ad2789..5a1b29c18f25 100644 --- a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md +++ b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -36,17 +36,23 @@ As you make changes to files in your text editor and save them locally, you will #### Creating a partial commit -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. The rest of your changes will remain intact, so that you can make additional modifications and commits. This allows you to make separate, meaningful commits, such as keeping line break changes in a commit separate from code or prose changes. +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. The rest of your changes will remain intact, so that you can make additional modifications and commits. This allows you to make separate, meaningful commits, such as keeping line break changes in a commit separate from code or prose changes. -When you review the diff of the file, the lines that will be included in the commit are highlighted in blue. To exclude the change, click the changed line so the blue disappears. +{% note %} + +**Note:** Split diff displays are currently in beta and subject to change. + +{% endnote %} -![Unselected lines in a file](/assets/images/help/desktop/partial-commit.png) +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. ![Unselected lines in a file](/assets/images/help/desktop/partial-commit.png) -#### Discarding changes +### 3. Discarding changes +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. -You can discard all the uncommitted changes in one file, a range of files, or discard all changes in all files since the last commit. +Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied. -{% mac %} +#### Discarding changes in one or more files {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -54,30 +60,25 @@ You can discard all the uncommitted changes in one file, a range of files, or di {% data reusables.desktop.confirm-discard-files %} ![Discard Changes button in the confirmation dialog](/assets/images/help/desktop/discard-changes-confirm-mac.png) -{% tip %} +#### Discarding changes in one or more lines +You can discard one or more changed lines that are uncommitted. -**Tip:** The changes you discarded are saved in a dated file in the Trash and you can recover them until the Trash is emptied. - -{% endtip %} +{% note %} -{% endmac %} +**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. -{% windows %} +{% endnote %} -{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %} - ![Discard Changes option in context menu](/assets/images/help/desktop/discard-changes-win.png) -{% data reusables.desktop.confirm-discard-files %} - ![Discard Changes button in the confirmation dialog](/assets/images/help/desktop/discard-changes-confirm-win.png) +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**. -{% tip %} + ![Discard single line in the confirmation dialog](/assets/images/help/desktop/discard-single-line.png) -**Tip:** The changes you discarded are saved in a file in the Recycle Bin and you can recover them until it is emptied. +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**. -{% endtip %} + ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) -{% endwindows %} -### 3. Write a commit message and push your changes +### 4. Write a commit message and push your changes Once you're satisfied with the changes you've chosen to include in your commit, write your commit message and push your changes. If you've collaborated on a commit, you can also attribute a commit to more than one author. diff --git a/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md b/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md index e25d374ee18c..31607e2e14bb 100644 --- a/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md @@ -34,8 +34,6 @@ Different server-to-server request rate limits apply to {% data variables.produc ### User-to-server requests -{% data reusables.apps.deprecating_password_auth %} - {% 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. {% if currentVersion == "free-pro-team@latest" %} @@ -52,7 +50,7 @@ User-to-server requests are rate limited at 5,000 requests per hour and per auth #### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits -When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. +When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. {% endif %} diff --git a/translations/ru-RU/content/developers/overview/managing-deploy-keys.md b/translations/ru-RU/content/developers/overview/managing-deploy-keys.md index dad75176db2c..8fecf2688086 100644 --- a/translations/ru-RU/content/developers/overview/managing-deploy-keys.md +++ b/translations/ru-RU/content/developers/overview/managing-deploy-keys.md @@ -82,6 +82,32 @@ See [our guide on Git automation with tokens][git-automation]. 7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. 8. Click **Add key**. +##### Using multiple repositories on one server + +If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. + +In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. Например: + +```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 %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias. +* `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias. +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias. + +You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. Например: + +```bash +$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git +``` + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/ru-RU/content/developers/overview/secret-scanning.md b/translations/ru-RU/content/developers/overview/secret-scanning.md index b55c982bfcac..bf0a60000a02 100644 --- a/translations/ru-RU/content/developers/overview/secret-scanning.md +++ b/translations/ru-RU/content/developers/overview/secret-scanning.md @@ -79,7 +79,7 @@ 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. +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. * **Token**: The value of the secret match. * **Type**: The unique name you provided to identify your regular expression. diff --git a/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md b/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md index dfb2f9e1e53e..be6962f09392 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md @@ -1,6 +1,7 @@ --- title: About secret scanning intro: '{% data variables.product.product_name %} scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.' +product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /github/administering-a-repository/about-token-scanning - /articles/about-token-scanning diff --git a/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md b/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md index 5f2c3239295d..dcfae988ec4e 100644 --- a/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md +++ b/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md @@ -1,6 +1,7 @@ --- title: Configuring secret scanning for private repositories intro: 'You can configure how {% data variables.product.product_name %} scans your private repositories for secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'People with admin permissions to a private repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' versions: free-pro-team: '*' diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/ru-RU/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index 10f410a5d36e..9127ad2090f0 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -1,6 +1,7 @@ --- title: Managing alerts from secret scanning intro: You can view and close alerts for secrets checked in to your repository. +product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' --- diff --git a/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index e8f346af5235..921afd3c0eea 100644 --- a/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -31,7 +31,7 @@ For more information, see "[Setting your commit email address](/articles/setting ### Creating co-authored commits using {% 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). +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#4-write-a-commit-message-and-push-your-changes)" and [{% 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) @@ -74,4 +74,4 @@ The new commit and message will appear on {% data variables.product.product_loca - "[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 +- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md index 6aefe2c38758..32219c34daa7 100644 --- a/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- title: Using Codespaces in Visual Studio Code -intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_vs_codespaces %} extension with your account on {% data variables.product.product_name %}.' +intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% 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: ### Требования -Before you can develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must configure the {% data variables.product.prodname_vs_codespaces %} extension to connect to your {% data variables.product.product_name %} account. +To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. -1. Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. -2. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Extensions icon. ![The Extensions icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-extensions-icon-vscode.png) -3. Below {% data variables.product.prodname_vs_codespaces %}, click the Manage icon, then click **Extension Settings**. ![The Extension Settings option](/assets/images/help/codespaces/select-extension-settings.png) -4. Use the Codespaces: Account Provider drop-down menu, and click **{% data variables.product.prodname_dotcom %}**. ![Setting the Account Provider to {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/select-account-provider-vscode.png) +1. Use the + +{% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -6. If {% data variables.product.prodname_codespaces %} is not already selected in the header, click **{% data variables.product.prodname_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) -7. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -8. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -9. Sign in to {% data variables.product.product_name %} to approve the extension. +2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) +3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) +4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +5. Sign in to {% data variables.product.product_name %} to approve the extension. ### Creating a codespace in {% data variables.product.prodname_vscode %} @@ -31,8 +30,8 @@ After you connect your {% data variables.product.product_name %} account to the {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) 3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop in. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) - +4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) +5. Click the instance type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) ### Opening a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 9c5102f3fc38..e94a6b5c8a27 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -94,7 +94,7 @@ If the `autobuild` command can't build your code, you can run the build steps yo By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command. -Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-an-alert)." +Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your 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#viewing-the-alerts-for-a-repository)." ### {% data variables.product.prodname_codeql_runner %} command reference diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index 52c44246e32c..b62aafb4534d 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -58,7 +58,7 @@ After you enable {% data variables.product.prodname_code_scanning %}, you can mo 1. Review the logging output from the actions in this workflow as they run. -1. After a scan completes, you can view alerts from a completed scan. 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. After a scan completes, you can view alerts from a completed scan. 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-the-alerts-for-a-repository)." {% note %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index bbaf148dd67b..256db1838fba 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -1,7 +1,7 @@ --- title: Managing code scanning alerts for your repository shortTitle: Managing alerts -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: 'From the security view, 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.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: @@ -30,9 +30,11 @@ If you enable {% data variables.product.prodname_code_scanning %} using {% data When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. -### Viewing an alert +### Viewing the alerts for a repository -Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} alerts on pull requests. However, you need write permission to view a summary of alerts for repository on the **Security** tab. By default, alerts are shown for the default branch. +Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Managing a workflow run](/actions/configuring-and-managing-workflows/managing-a-workflow-run)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." + +You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -45,7 +47,7 @@ Anyone with read permission for a repository can see {% data variables.product.p Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[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)." -If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing an alert](#viewing-an-alert)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. +If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index 9b373b7a2102..721b4060208d 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -3,7 +3,7 @@ title: Triaging code scanning alerts in pull requests shortTitle: Triaging alerts in pull requests intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.' 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: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -31,9 +31,9 @@ When you look at the **Files changed** tab for a pull request, you see annotatio ![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png) -Some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." +If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." -For more information about an alert, click **Show more details** on the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. +To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code. @@ -41,11 +41,11 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_ ### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request -Anyone with write permission for a repository can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on a pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. +Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. {% if currentVersion == "enterprise-server@2.22" %} -If you don't think that an alert needs to be fixed, you can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. +If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. {% data reusables.code-scanning.false-positive-fix-codeql %} @@ -63,4 +63,4 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler For more information about dismissing alerts, 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#dismissing-or-deleting-alerts)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index 120f8640c163..43c891b98ffa 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -66,7 +66,7 @@ For more information, see the workflow extract in "[Automatic build for a compil * Building using a distributed build system external to GitHub Actions, using a daemon process. * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. - For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. + For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. For example, the following configuration for C# will pass the flag during the first build step. diff --git a/translations/ru-RU/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md b/translations/ru-RU/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md index 69ff5fb0e615..e9ab650944b6 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md +++ b/translations/ru-RU/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md @@ -21,5 +21,5 @@ versions: You can see a list of features that are available in beta and a brief description for each feature. Each feature includes a link to give feedback. -1. In the upper-right corner of any page, click your profile photo, then click **Feature preview**. ![Feature preview button](/assets/images/help/settings/feature-preview-button.png) +{% data reusables.feature-preview.feature-preview-setting %} 2. Optionally, to the right of a feature, click **Enable** or **Disable**. ![Enable button in feature preview](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md index 105edf9cf365..ae996656b559 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md @@ -1,6 +1,7 @@ --- title: Managing secret scanning for your organization intro: 'You can control which repositories in your organization {% data variables.product.product_name %} will scan for secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: 'Organization owners can manage {% data variables.product.prodname_secret_scanning %} for repositories in the organization.' versions: free-pro-team: '*' 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 b85fbeab2f71..1476faaf2072 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 @@ -43,74 +43,77 @@ In addition to managing organization-level settings, organization owners have ad ### Repository access for each permission level -| Repository action | Read | Приоритизация | Write | Maintain | Admin | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-----:|:--------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:| -| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | -| Open issues | **X** | **X** | **X** | **X** | **X** | -| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | -| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | -| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | -| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | -| View published releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| 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** | -| 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** | -| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | -| [Hide anyone's comments](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/articles/locking-conversations) | | | **X** | **X** | **X** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Mark a draft pull request as ready for review](/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" %} -| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| Create and edit releases | | | **X** | **X** | **X** | -| View draft releases | | | **X** | **X** | **X** | -| Edit a repository's description | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Limit [interactions in a repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | -| Add a repository to a team (see "[Managing team access to an organization repository](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | -| Change a repository's settings | | | | | **X** | -| Manage team and collaborator access to the repository | | | | | **X** | -| Edit the repository's default branch | | | | | **X** | -| Manage webhooks and deploy keys | | | | | **X** |{% 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 | | | | | **X** | -| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** | -| [Manage data use settings for your private repository](/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" %}| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} -| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | +| Repository action | Read | Приоритизация | Write | Maintain | Admin | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | +| Open issues | **X** | **X** | **X** | **X** | **X** | +| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | +| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | +| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | +| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | +| View published releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 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** | +| 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** | +| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | +| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | +| [Hide anyone's comments](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | +| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Mark a draft pull request as ready for review](/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" %} +| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | +| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | +| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| Create and edit releases | | | **X** | **X** | **X** | +| View draft releases | | | **X** | **X** | **X** | +| Edit a repository's description | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Enable wikis and restrict wiki editors | | | | **X** | **X** | +| Enable project boards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | +| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Limit [interactions in a repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} +| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | +| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | +| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | +| Add a repository to a team (see "[Managing team access to an organization repository](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | +| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | +| Change a repository's settings | | | | | **X** | +| Manage team and collaborator access to the repository | | | | | **X** | +| Edit the repository's default branch | | | | | **X** | +| Manage webhooks and deploy keys | | | | | **X** |{% 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 | | | | | **X** | +| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** | +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %} +| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** | ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index d889083de26e..77d43864e77a 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -3,6 +3,7 @@ title: Managing licenses for Visual Studio subscription with GitHub Enterprise intro: 'You can manage {% data variables.product.prodname_enterprise %} licensing for {% 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 diff --git a/translations/ru-RU/content/github/site-policy/github-acceptable-use-policies.md b/translations/ru-RU/content/github/site-policy/github-acceptable-use-policies.md index c9c20262dfe8..e51a13fda85b 100644 --- a/translations/ru-RU/content/github/site-policy/github-acceptable-use-policies.md +++ b/translations/ru-RU/content/github/site-policy/github-acceptable-use-policies.md @@ -37,6 +37,8 @@ While using the Service, under no circumstances will you: - harass, abuse, threaten, or incite violence towards any individual or group, including our employees, officers, and agents, or other users; +- post off-topic content, or interact with platform features, in a way that significantly or repeatedly disrupts the experience of other users; + - use our servers for any form of excessive automated bulk activity (for example, spamming or cryptocurrency mining), to place undue burden on our servers through automated means, or to relay any form of unsolicited advertising or solicitation through our servers, such as get-rich-quick schemes; - use our servers to disrupt or to attempt to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network (unless authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); @@ -48,15 +50,17 @@ While using the Service, under no circumstances will you: ### 4. Services Usage Limits You will not reproduce, duplicate, copy, sell, resell or exploit any portion of the Service, use of the Service, or access to the Service without our express written permission. -### 5. Scraping and API Usage Restrictions -Scraping refers to extracting data from our Service via an automated process, such as a bot or webcrawler. It does not refer to the collection of information through our API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. You may scrape the website for the following reasons: +### 5. Information Usage Restrictions +You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise: + +- Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are [open access](https://en.wikipedia.org/wiki/Open_access). +- Archivists may use public information from the Service for archival purposes. -- Researchers may scrape public, non-personal information from the Service for research purposes, only if any publications resulting from that research are open access. -- Archivists may scrape the Service for public data for archival purposes. +Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler. Scraping does not refer to the collection of information through our API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. -You may not scrape the Service for spamming purposes, including for the purposes of selling User Personal Information (as defined in the [GitHub Privacy Statement](/articles/github-privacy-statement)), such as to recruiters, headhunters, and job boards. +You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling User Personal Information (as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement)), such as to recruiters, headhunters, and job boards. -All use of data gathered through scraping must comply with the [GitHub Privacy Statement](/articles/github-privacy-statement). +Your use of information from the Service must comply with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). ### 6. Конфиденциальность Misuse of User Personal Information is prohibited. diff --git a/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md b/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md index 09594c862f80..e278733ac5a6 100644 --- a/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: November 1, 2020 +Version Effective Date: November 13, 2020 When you create an Account, you're given access to lots of different features and products that are all a part of the Service. Because many of these features and products offer different functionality, they may require additional terms and conditions specific to that feature or product. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -89,7 +89,7 @@ In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors ### 9. GitHub Advanced Security -GitHub Advanced Security enables you to identify security vulnerabilities through customizable and automated semantic code analysis. GitHub Advanced Security is licensed on a per User basis. If you are using GitHub Advanced Security as part of GitHub Enterprise Cloud, many features of GitHub Advanced Security, including automated code scanning of private repositories, also require the use of GitHub Actions. Billing for usage of GitHub Actions is usage-based and is subject to the [GitHub Actions terms](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages). +GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. If you are using GitHub Advanced Security as part of GitHub Enterprise Cloud, many features of GitHub Advanced Security, including automated code scanning of private repositories, also require the use of GitHub Actions. ### 10. Dependabot Preview @@ -108,4 +108,3 @@ We need the legal right to submit your contributions to the GitHub Advisory Data #### b. License to the GitHub Advisory Database The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by . - diff --git a/translations/ru-RU/content/github/site-policy/github-community-guidelines.md b/translations/ru-RU/content/github/site-policy/github-community-guidelines.md index 1ddfde17ac06..4e1af8927df0 100644 --- a/translations/ru-RU/content/github/site-policy/github-community-guidelines.md +++ b/translations/ru-RU/content/github/site-policy/github-community-guidelines.md @@ -11,7 +11,7 @@ Millions of developers host millions of projects on GitHub — both open and clo GitHub users worldwide bring wildly different perspectives, ideas, and experiences, and range from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub a welcoming environment for all the different voices and perspectives in our community, while maintaining a space where people are free to express themselves. -We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. We do not actively seek out content to moderate. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service. +We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service. ### Building a strong community @@ -47,23 +47,25 @@ Of course, you can always contact us to {% data variables.contact.report_abuse % We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. Such discussions, however, are unlikely to foster fruitful dialog when ideas are silenced because community members are being shouted down or are afraid to speak up. That means you should be respectful and civil at all times, and refrain from attacking others on the basis of who they are. We do not tolerate behavior that crosses the line into the following: -* **Threats of violence** - You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety. +- #### Threats of violence You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety. -* **Hate speech and discrimination** - While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics. +- #### Hate speech and discrimination While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics. -* **Bullying and harassment** - We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory. +- #### Bullying and harassment We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory. -* **Impersonation** - You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment. +- #### Disrupting the experience of other users Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on. Behaviors such as repeatedly posting off-topic comments, opening empty or meaningless issues or pull requests, or using any other platform feature in a way that continually disrupts the experience of other users are not allowed. While we encourage maintainers to moderate their own projects on an individual basis, GitHub staff may take further restrictive action against accounts that are engaging in these types of behaviors. -* **Doxxing and invasion of privacy** - Don't post other people's personal information, such as phone numbers, private email addresses, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject. +- #### Impersonation You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment. -* **Sexually obscene content** - Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors. +- #### Doxxing and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject. -* **Gratuitously violent content** - Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content. +- #### Sexually obscene content Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors. -* **Misinformation and disinformation** - You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) because such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information. +- #### Gratuitously violent content Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content. -* **Active malware or exploits** - Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Note, however, that we do not prohibit the posting of source code which could be used to develop malware or exploits, as the publication and distribution of such source code has educational value and provides a net benefit to the security community. +- #### Misinformation and disinformation You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information. + +- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Note, however, that we do not prohibit the posting of source code which could be used to develop malware or exploits, as the publication and distribution of such source code has educational value and provides a net benefit to the security community. ### What happens if someone breaks the rules? diff --git a/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md index 168691b986bd..009fbc608c31 100644 --- a/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md @@ -9,7 +9,7 @@ versions: THANK YOU FOR CHOOSING GITHUB FOR YOUR COMPANY’S BUSINESS NEEDS. PLEASE READ THIS AGREEMENT CAREFULLY AS IT GOVERNS USE OF THE PRODUCTS (AS DEFINED BELOW), UNLESS GITHUB HAS EXECUTED A SEPARATE WRITTEN AGREEMENT WITH CUSTOMER FOR THAT PURPOSE. BY CLICKING ON THE "I AGREE" OR SIMILAR BUTTON OR BY ACCESSING THE PRODUCTS, CUSTOMER ACCEPTS ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF CUSTOMER IS ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, CUSTOMER REPRESENTS THAT IT HAS THE LEGAL AUTHORITY TO BIND THE COMPANY OR OTHER LEGAL ENTITY TO THIS AGREEMENT. ### GitHub Corporate Terms of Service -Version Effective Date: July 20, 2020 +Version Effective Date: November 16, 2020 This Agreement applies to the following GitHub offerings, as further defined below (collectively, the **“Products”**): - The Service; @@ -133,13 +133,13 @@ Customer may create or upload User-Generated Content while using the Service. Cu Customer retains ownership of Customer Content that Customer creates or owns. Customer acknowledges that it: (a) is responsible for Customer Content, (b) will only submit Customer Content that Customer has the right to post (including third party or User-Generated Content), and (c) Customer will fully comply with any third-party licenses relating to Customer Content that Customer posts. Customer grants the rights set forth in Sections D.3 through D.6, free of charge and for the purposes identified in those sections until such time as Customer removes Customer Content from GitHub servers, except for Content Customer has posted publicly and that External Users have Forked, in which case the license is perpetual until such time as all Forks of Customer Content have been removed from GitHub servers. If Customer uploads Customer Content that already comes with a license granting GitHub the permissions it needs to run the Service, no additional license is required. #### 3. License Grant to Us -Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies only as necessary to provide the Service. This includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content or otherwise distribute or use it outside of the Service. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. +Customer grants to GitHub the right to store, archive, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service, including improving the Service over time. This license includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content. It also does not grant GitHub the right to otherwise distribute or use Customer Content outside of our provision of the Service, except that as part of the right to archive Customer Content, GitHub may permit our partners to store and archive Customer Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. #### 4. License Grant to External Users Any Content that Customer posts publicly, including issues, comments, and contributions to External Users' repositories, may be viewed by others. By setting its repositories to be viewed publicly, Customer agree to allow External Users to view and Fork Customer’s repositories. If Customer sets its pages and repositories to be viewed publicly, Customer grants to External Users a nonexclusive, worldwide license to use, display, and perform Customer Content through the Service and to reproduce Customer Content solely on the Service as permitted through functionality provided by GitHub (for example, through Forking). Customer may grant further rights to Customer Content if Customer adopts a license. If Customer is uploading Customer Content that it did not create or own, Customer is responsible for ensuring that the Customer Content it uploads is licensed under terms that grant these permissions to External Users #### 5. Contributions Under Repository License -Whenever Customer makes a contribution to a repository containing notice of a license, it licenses such contributions under the same terms and agrees that it has the right to license such contributions under those terms. If Customer has a separate agreement to license its contributions under different terms, such as a contributor license agreement, that agreement will supersede. +Whenever Customer adds Content to a repository containing notice of a license, it licenses that Content under the same terms and agrees that it has the right to license that Content under those terms. If Customer has a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. #### 6. Moral Rights Customer retains all moral rights to Customer Content that it uploads, publishes, or submits to any part of the Service, including the rights of integrity and attribution. However, Customer waives these rights and agrees not to assert them against GitHub, solely to enable GitHub to reasonably exercise the rights granted in Section D, but not otherwise. @@ -153,10 +153,13 @@ Customer is responsible for managing access to its Private Repositories, includi GitHub considers Customer Content in Customer’s Private Repositories to be Customer’s Confidential Information. GitHub will protect and keep strictly confidential the Customer Content of Private Repositories in accordance with Section P. #### 3. Access -GitHub personnel may only access Customer’s Private Repositories (i) with Customer’s consent and knowledge, for support reasons or (ii) when access is required for security reasons. Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. +GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 4. Exclusions -If GitHub has reason to believe the Content of a Private Repository is in violation of the law or of this Agreement, GitHub has the right to access, review, and remove that Content. Additionally, GitHub may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the Content of Customer’s Private Repositories. Unless otherwise bound by requirements under law or if in response to a security threat or other risk to security, GitHub will provide notice of such actions. +Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. + +Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. Intellectual Property Notice @@ -270,7 +273,7 @@ Neither Party will use the other Party's Confidential Information, except as per Upon Customer’s request for Professional Services, GitHub will provide an SOW detailing such Professional Services. GitHub will perform the Professional Services described in each SOW. GitHub will control the manner and means by which the Professional Services are performed and reserves the right to determine personnel assigned. GitHub may use third parties to perform the Professional Services, provided that GitHub remains responsible for their acts and omissions. Customer acknowledges and agrees that GitHub retains all right, title and interest in and to anything used or developed in connection with performing the Professional Services, including software, tools, specifications, ideas, concepts, inventions, processes, techniques, and know-how. To the extent GitHub delivers anything to Customer while performing the Professional Services, GitHub grants to Customer a non-exclusive, non-transferable, worldwide, royalty-free, limited-term license to use those deliverables during the term of this Agreement, solely in conjunction with Customer’s use of the Service. ### R. Changes to the Service or Terms -GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price changes, at least 30 days prior to the change taking effect by posting a notice on the Service. For non-material modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. +GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. GitHub changes the Service via Updates and addition of new features. Nothwithstanding the foregoing, GitHub reserves the right at any time to modify or discontinue, temporarily or permanently, the Service (or any part of it) with or without notice. diff --git a/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md index 25edfff43e19..efd1e9b9b4c8 100644 --- a/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -26,6 +26,6 @@ For definitions of each Service feature (“**Service Feature**”) and to revi Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption -If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption should be sent to [GitHub Support](https://support.github.com/contact). +If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). Service Credits may take the form of a refund or credit to Customer’s account, cannot be exchanged into a cash amount, are limited to a maximum of ninety (90) days of paid service per calendar quarter, require Customer to have paid any outstanding invoices, and expire upon termination of Customer’s agreement with GitHub. Service Credits are the sole and exclusive remedy for any failure by GitHub to meet any obligations in this SLA. diff --git a/translations/ru-RU/content/github/site-policy/github-enterprise-subscription-agreement.md b/translations/ru-RU/content/github/site-policy/github-enterprise-subscription-agreement.md index 50ad30b4a792..fcd2d9ec34ec 100644 --- a/translations/ru-RU/content/github/site-policy/github-enterprise-subscription-agreement.md +++ b/translations/ru-RU/content/github/site-policy/github-enterprise-subscription-agreement.md @@ -7,7 +7,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: July 20, 2020 +Version Effective Date: November 16, 2020 BY CLICKING THE "I AGREE" OR SIMILAR BUTTON OR BY USING ANY OF THE PRODUCTS (DEFINED BELOW), CUSTOMER ACCEPTS THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF CUSTOMER IS ENTERING INTO THIS AGREEMENT ON BEHALF OF A LEGAL ENTITY, CUSTOMER REPRESENTS THAT IT HAS THE LEGAL AUTHORITY TO BIND THE LEGAL ENTITY TO THIS AGREEMENT. @@ -197,7 +197,7 @@ This Agreement, together with the Exhibits and each Order Form and SOW, constitu #### 1.13.11 Amendments; Order of Precedence. -GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price changes, at least 30 days prior to the change taking effect by posting a notice on the Service. For non-material modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. In the event of any conflict between the terms of this Agreement and any Order Form or SOW, the terms of the Order Form or SOW will control with respect to that Order Form or SOW only. +GitHub reserves the right, at its sole discretion, to amend this Agreement at any time and will update this Agreement in the event of any such amendments. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Customer can view all changes to this Agreement in our [Site Policy](https://github.com/github/site-policy) repository. In the event of any conflict between the terms of this Agreement and any Order Form or SOW, the terms of the Order Form or SOW will control with respect to that Order Form or SOW only. #### 1.13.12 Severability. @@ -296,7 +296,7 @@ Customer may create or upload User-Generated Content while using the Service. Cu **(ii)** Customer grants the rights set forth in Sections 3.3.3 through 3.3.6, free of charge and for the purposes identified in those sections until such time as Customer removes Customer Content from GitHub servers, except for Content Customer has posted publicly and that External Users have Forked, in which case the license is perpetual until such time as all Forks of Customer Content have been removed from GitHub servers. If Customer uploads Customer Content that already comes with a license granting GitHub the permissions it needs to run the Service, no additional license is required. #### 3.3.3 License Grant to GitHub. -Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies only as necessary to provide the Service. This includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content or otherwise distribute or use it outside of the Service. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. +Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service. This includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. These rights apply to both public and Private Repositories. This license does not grant GitHub the right to sell Customer Content or otherwise distribute or use it outside of the Service. Customer grants to GitHub the rights it needs to use Customer Content without attribution and to make reasonable adaptations of Customer Content as necessary to provide the Service. #### 3.3.4 License Grant to External Users. **(i)** Any Content that Customer posts publicly, including issues, comments, and contributions to External Users' repositories, may be viewed by others. By setting its repositories to be viewed publicly, Customer agree to allow External Users to view and Fork Customer’s repositories. @@ -318,10 +318,13 @@ Customer is responsible for managing access to its Private Repositories, includi GitHub considers Customer Content in Customer’s Private Repositories to be Customer’s Confidential Information. GitHub will protect and keep strictly confidential the Customer Content of Private Repositories in accordance with Section 1.4. #### 3.4.3 Access. -GitHub may only access Customer’s Private Repositories (i) with Customer’s consent and knowledge, for support reasons, or (ii) when access is required for security reasons. Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. +GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 3.4.4 Exclusions. -If GitHub has reason to believe the Content of a Private Repository is in violation of the law or of this Agreement, GitHub has the right to access, review, and remove that Content. Additionally, GitHub may be compelled by law to disclose the Content of Customer’s Private Repositories. Unless otherwise bound by requirements under law or if in response to a security threat or other risk to security, GitHub will provide notice of such actions. +Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. + +Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 3.5. Intellectual Property Notices. 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 e434bcb669f2..6db712401f55 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 @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Effective date: July 22, 2020 +Effective date: November 16, 2020 Thanks for entrusting GitHub Inc. (“GitHub”, “we”) with your source code, your projects, and your personal information. Holding on to your private information is a serious responsibility, and we want you to know how we're handling it. @@ -150,23 +150,39 @@ We **do not** sell your User Personal Information for monetary or other consider Please note: The California Consumer Privacy Act of 2018 (“CCPA”) requires businesses to state in their privacy policy whether or not they disclose personal information in exchange for monetary or other valuable consideration. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. You can learn more about the CCPA and how we comply with it [here](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act). -### Other important information +### Repository contents + +#### Access to private repositories + +If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for +- security purposes +- to assist the repository owner with a support matter +- to maintain the integrity of the Service +- to comply with our legal obligations +- if we have reason to believe the contents are in violation of the law, or +- with your consent. + +However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories). -#### Repository contents +Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts). -GitHub personnel [do not access private repositories unless required to](/github/site-policy/github-terms-of-service#e-private-repositories) for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, or to comply with our legal obligations. However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, or other content known to violate our Terms, such as violent extremist or terrorist content or child exploitation imagery based on algorithmic fingerprinting techniques. Our Terms of Service provides [more details](/github/site-policy/github-terms-of-service#e-private-repositories). +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. -If your repository is public, anyone may view its contents. If you include private, confidential or [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. +#### Public repositories + +If your repository is public, anyone may view its contents. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. Please see more about [User Personal Information in public repositories](/github/site-policy/github-privacy-statement#public-information-on-github). +### Other important information + #### Public information on GitHub Many of GitHub services and features are public-facing. If your content is public-facing, third parties may access and use it in compliance with our Terms of Service, such as by viewing your profile or repositories or pulling data via our API. We do not sell that content; it is yours. However, we do allow third parties, such as research organizations or archives, to compile public-facing GitHub information. Other third parties, such as data brokers, have been known to scrape GitHub and compile data as well. Your User Personal Information associated with your content could be gathered by third parties in these compilations of GitHub data. If you do not want your User Personal Information to appear in third parties’ compilations of GitHub data, please do not make your User Personal Information publicly available and be sure to [configure your email address to be private in your user profile](https://github.com/settings/emails) and in your [git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). We currently set Users' email address to private by default, but legacy GitHub Users may need to update their settings. -If you would like to compile GitHub data, you must comply with our Terms of Service regarding [scraping](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users. +If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users. Similarly, projects on GitHub may include publicly available User Personal Information collected as part of the collaborative process. If you have a complaint about any User Personal Information on GitHub, please see our section on [resolving complaints](/github/site-policy/github-privacy-statement#resolving-complaints). @@ -219,7 +235,7 @@ That said, the email address you have supplied [via your Git commit settings](/g #### Cookies -GitHub uses cookies to make interactions with our service easy and meaningful. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors. We use cookies (and similar technologies, like HTML5 localStorage) to keep you logged in, remember your preferences, and provide information for future development of GitHub. For security purposes, we use cookies to identify a device. By using our Website, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use GitHub’s services. +GitHub uses cookies and similar technologies (e.g., HTML5 localStorage) to make interactions with our service easy and meaningful. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors. We use cookies and similar technologies (hereafter collectively "cookies") to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. By using our Website, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use GitHub’s services. We provide a web page on [cookies and tracking](/github/site-policy/github-subprocessors-and-cookies) that describes the cookies we set, the needs we have for those cookies, and the types of cookies they are (temporary or permanent). It also lists our third-party analytics providers and other service providers, and details exactly which parts of our Website we permit them to track. @@ -300,7 +316,7 @@ In the unlikely event that a dispute arises between you and GitHub regarding our ### Changes to our Privacy Statement -Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For changes to this Privacy Statement that are not material changes or that do not affect your rights, we encourage Users to check our Site Policy repository frequently. +Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### Лицензия diff --git a/translations/ru-RU/content/github/site-policy/github-terms-of-service.md b/translations/ru-RU/content/github/site-policy/github-terms-of-service.md index 4ee5348da0f5..fb1bbcc08aa2 100644 --- a/translations/ru-RU/content/github/site-policy/github-terms-of-service.md +++ b/translations/ru-RU/content/github/site-policy/github-terms-of-service.md @@ -32,11 +32,11 @@ Thank you for using GitHub! We're happy you're here. Please read this Terms of S | [N. Disclaimer of Warranties](#n-disclaimer-of-warranties) | We provide our service as is, and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** | | [O. Limitation of Liability](#o-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** | | [P. Release and Indemnification](#p-release-and-indemnification) | You are fully responsible for your use of the service. | -| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of changes that affect your rights. | +| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. | | [R. Miscellaneous](#r-miscellaneous) | Please see this section for legal details including our choice of law. | ### The GitHub Terms of Service -Effective date: April 2, 2020 +Effective date: November 16, 2020 ### A. Определения @@ -98,7 +98,7 @@ You agree that you will not under any circumstances violate our [Acceptable Use You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content. #### 2. GitHub May Remove Content -We do not pre-screen User-Generated Content, but we have the right (though not the obligation) to refuse or remove any User-Generated Content that, in our sole discretion, violates any [GitHub terms or policies](/github/site-policy). +We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub for mobile may be subject to mobile app stores' additional terms. #### 3. Ownership of Content, Right to Post, and License Grants You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post. @@ -106,9 +106,9 @@ You retain ownership of and responsibility for Your Content. If you're posting a Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it. #### 4. License Grant to Us -We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, parse, and display Your Content, and make incidental copies as necessary to render the Website and provide the Service. This includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. +We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. -This license does not grant GitHub the right to sell Your Content or otherwise distribute or use it outside of our provision of the Service. +This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/). #### 5. License Grant to Other Users Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). @@ -116,7 +116,7 @@ Any User-Generated Content you post publicly, including issues, comments, and co If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you [adopt a license](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users. #### 6. Contributions Under Repository License -Whenever you make a contribution to a repository containing notice of a license, you license your contribution under the same terms, and you agree that you have the right to license your contribution under those terms. If you have a separate agreement to license your contributions under different terms, such as a contributor license agreement, that agreement will supersede. +Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit. @@ -126,7 +126,7 @@ You retain all moral rights to Your Content that you upload, publish, or submit To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service. ### E. Private Repositories -**Short version:** *You may have access to private repositories. We treat the content of private repositories as confidential, and we only access it for support reasons, with your consent, or if required to for security reasons.* +**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.* #### 1. Control of Private Repositories Some Accounts may have private repositories, which allow the User to control access to Content. @@ -135,15 +135,14 @@ Some Accounts may have private repositories, which allow the User to control acc GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care. #### 3. Access -GitHub personnel may only access the content of your private repositories in the following situations: -- With your consent and knowledge, for support reasons. If GitHub accesses a private repository for support reasons, we will only do so with the owner’s consent and knowledge. -- When access is required for security reasons, including when access is required to maintain ongoing confidentiality, integrity, availability and resilience of GitHub's systems and Service. +GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). You may choose to enable additional access to your private repositories. Например: - You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights. -#### 4. Exclusions -If we have reason to believe the contents of a private repository are in violation of the law or of these Terms, we have the right to access, review, and remove them. Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. +Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. Copyright Infringement and DMCA Policy If you believe that content on our website violates your copyright, please contact us in accordance with our [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing copyright@github.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses. @@ -286,9 +285,9 @@ If you have a dispute with one or more Users, you agree to release GitHub from a You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense. ### Q. Changes to These Terms -**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any changes that affect your rights and give you time to adjust to them.* +**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.* -We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price changes, at least 30 days prior to the change taking effect by posting a notice on our Website. For non-material modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. +We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice. diff --git a/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md index 4c6b3952163b..b0679a98b847 100644 --- a/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md +++ b/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md @@ -41,12 +41,12 @@ Within conversations on {% data variables.product.product_name %}, references to References to a commit's SHA hash are automatically converted into shortened links to the commit on {% data variables.product.product_name %}. -| Reference type | Raw reference | Short link | -| ----------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | -| Commit URL | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| Username/Repository@SHA | jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| Reference type | Raw reference | Short link | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | +| Commit URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| `Username/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | ### Custom autolinks to external resources diff --git a/translations/ru-RU/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md b/translations/ru-RU/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md index 26d95c251aee..063997c698f7 100644 --- a/translations/ru-RU/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md +++ b/translations/ru-RU/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md @@ -8,19 +8,24 @@ versions: {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% endnote %} - {% data reusables.package_registry.container-registry-feature-highlights %} To share context about your package's use, you can link a repository to your container image on {% data variables.product.prodname_dotcom %}. For more information, see "[Connecting a repository to a container image](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)." ### Supported formats -The {% data variables.product.prodname_container_registry %} currently only supports Docker images. +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +#### Manifest Lists/Image Indexes +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. ### Visibility and access permissions for container images diff --git a/translations/ru-RU/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md b/translations/ru-RU/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md new file mode 100644 index 000000000000..3cb030c09baa --- /dev/null +++ b/translations/ru-RU/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md @@ -0,0 +1,37 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + + ![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/ru-RU/content/packages/getting-started-with-github-container-registry/index.md b/translations/ru-RU/content/packages/getting-started-with-github-container-registry/index.md index 46849f39a609..f07fd0941c04 100644 --- a/translations/ru-RU/content/packages/getting-started-with-github-container-registry/index.md +++ b/translations/ru-RU/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 %} For more information about configuring, deleting, pushing, or pulling container images, see "[Managing container images with {% data variables.product.prodname_github_container_registry %}](/packages/managing-container-images-with-github-container-registry)." diff --git a/translations/ru-RU/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md b/translations/ru-RU/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md index 8516292b8195..976e46a58930 100644 --- a/translations/ru-RU/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md +++ b/translations/ru-RU/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md @@ -31,6 +31,8 @@ The domain for the {% data variables.product.prodname_container_registry %} is ` ### Authenticating with the container registry +{% data reusables.package_registry.feature-preview-for-container-registry %} + You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}. {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} @@ -72,6 +74,8 @@ To move Docker images that you host on {% data variables.product.prodname_regist ### Updating your {% data variables.product.prodname_actions %} workflow +{% data reusables.package_registry.feature-preview-for-container-registry %} + If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers. 1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)." diff --git a/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md b/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md index 05fc53b92d0a..81110a4ffcf7 100644 --- a/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md +++ b/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md @@ -24,7 +24,7 @@ If you have admin permissions to an organization-owned container image, you can If your package is owned by an organization and private, then you can only give access to other organization members or teams. -For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) @@ -54,7 +54,7 @@ When you first publish a package, the default visibility is private and only you A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. -For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 5. Under "Danger Zone", choose a visibility setting: diff --git a/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md b/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md index 0d4d0873d2d1..ddf6eae62764 100644 --- a/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md +++ b/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md @@ -16,8 +16,6 @@ To delete a container image, you must have admin permissions to the container im When deleting public packages, be aware that you may break projects that depend on your package. - - ### Reserved package versions and names {% data reusables.package_registry.package-immutability %} diff --git a/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md index e4e1db91970c..5dd0f067e25a 100644 --- a/translations/ru-RU/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ b/translations/ru-RU/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 %} -To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." +To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." ### Authenticating to {% data variables.product.prodname_github_container_registry %} 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 3caa9d5fc40c..c3364bf00d35 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 @@ -26,6 +26,8 @@ You can integrate {% data variables.product.prodname_registry %} with {% data va {% data reusables.package_registry.container-registry-beta %} +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + {% endif %} #### Viewing packages 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 3eff1a537717..26fe40cff451 100644 --- a/translations/ru-RU/content/rest/overview/other-authentication-methods.md +++ b/translations/ru-RU/content/rest/overview/other-authentication-methods.md @@ -37,12 +37,22 @@ $ curl -u username:token {% data variables.product.api_url_pre This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. -{% if enterpriseServerVersions contains currentVersion %} #### Via username and password -{% data reusables.apps.deprecating_password_auth %} +{% if currentVersion == "free-pro-team@latest" %} + +{% 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 %} -To use Basic Authentication with the {% data variables.product.product_name %} API, simply send the username and password associated with the account. +{% 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. For example, if you're accessing the API via [cURL][curl], the following command would authenticate you if you replace `` with your {% data variables.product.product_name %} username. (cURL will prompt you to enter the password.) @@ -88,14 +98,13 @@ The value `organizations` is a comma-separated list of organization IDs for orga {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ### Working with two-factor authentication -{% data reusables.apps.deprecating_password_auth %} - -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 or OAuth token instead of your username and password. - -You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}with [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %} or use the "[Create a new authorization][create-access]" endpoint in the OAuth Authorizations API to generate a new OAuth token. 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)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the GitHub API. 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. +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 %}. 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)". 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 %} #### Using the OAuth Authorizations API with two-factor authentication When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code: @@ -114,7 +123,6 @@ $ curl --request POST \ ``` {% endif %} -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization [curl]: http://curl.haxx.se/ [oauth-auth]: /v3/#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line 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 be886723b8f2..65ca0ecb9479 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 @@ -135,9 +135,9 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar 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" @@ -165,19 +165,10 @@ $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product. 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 %} - -{% note %} - -**Note:** For {% data variables.product.prodname_ghe_server %}, [as with all other endpoints](/v3/enterprise-admin/#endpoint-urls), you'll need to pass your username and password. - -{% endnote %} - -{% endif %} - ### 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. diff --git a/translations/ru-RU/content/rest/overview/troubleshooting.md b/translations/ru-RU/content/rest/overview/troubleshooting.md index 0cd9a1b5fc14..dde7daba1b11 100644 --- a/translations/ru-RU/content/rest/overview/troubleshooting.md +++ b/translations/ru-RU/content/rest/overview/troubleshooting.md @@ -13,16 +13,53 @@ versions: If you're encountering some oddities in the API, here's a list of resolutions to some of the problems you may be experiencing. -### Why am I getting a `404` error on a repository that exists? +### `404` error for an existing repository Typically, we send a `404` error when your client isn't properly authenticated. You might expect to see a `403 Forbidden` in these cases. However, since we don't want to provide _any_ information about private repositories, the API returns a `404` error instead. To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), and [third-party application restrictions][oap-guide] are not blocking access. -### Why am I not seeing all my results? +### Not all results returned 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. +{% 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. Например: + +```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/ru-RU/content/rest/reference/interactions.md b/translations/ru-RU/content/rest/reference/interactions.md index c3c7606ce7fb..f57fa0785216 100644 --- a/translations/ru-RU/content/rest/reference/interactions.md +++ b/translations/ru-RU/content/rest/reference/interactions.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -Users interact with repositories by commenting, opening issues, and creating pull requests. The Interactions APIs allow people with owner or admin access to temporarily restrict certain users from interacting with public repositories. +Users interact with repositories by commenting, opening issues, and creating 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 @@ Users interact with repositories by commenting, opening issues, and creating pul ## Организация -The Organization Interactions API allows organization owners to temporarily restrict which users can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users: +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 %} in the organization. * {% data reusables.interactions.contributor-user-limit-definition %} in the organization. * {% data reusables.interactions.collaborator-user-limit-definition %} in the organization. +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 %} ## Репозиторий -The Repository Interactions API allows people with owner or admin access to temporarily restrict which users can comment, open issues, or create pull requests in a public repository. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users: +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 %} + +## User + +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/ru-RU/content/rest/reference/oauth-authorizations.md b/translations/ru-RU/content/rest/reference/oauth-authorizations.md index 8bb3e8fa72cc..356309baff03 100644 --- a/translations/ru-RU/content/rest/reference/oauth-authorizations.md +++ b/translations/ru-RU/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 %} - You can use this API to manage the access OAuth applications have to your account. You can only access this API via [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) using your username and password, not tokens. If you or your users 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). diff --git a/translations/ru-RU/content/rest/reference/search.md b/translations/ru-RU/content/rest/reference/search.md index 9715db99225f..ac5b70081c19 100644 --- a/translations/ru-RU/content/rest/reference/search.md +++ b/translations/ru-RU/content/rest/reference/search.md @@ -31,13 +31,19 @@ Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is: ``` -q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N +SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N ``` For example, if you wanted to search for all _repositories_ owned by `defunkt` that contained the word `GitHub` and `Octocat` in the README file, you would use the following query with the _search repositories_ endpoint: ``` -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. Например: +```javascript +// JavaScript +const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax/)." diff --git a/translations/ru-RU/data/graphql/ghae/graphql_previews.ghae.yml b/translations/ru-RU/data/graphql/ghae/graphql_previews.ghae.yml index 8540c1d976f7..f957e0b7bcff 100644 --- a/translations/ru-RU/data/graphql/ghae/graphql_previews.ghae.yml +++ b/translations/ru-RU/data/graphql/ghae/graphql_previews.ghae.yml @@ -85,7 +85,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Pinned Issues Preview description: This preview adds support for pinned issues. 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 7ad2acba5901..10f9989a1239 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 @@ -2,112 +2,112 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ru-RU/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml b/translations/ru-RU/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml index 4cb2fcaddf2d..cff46f0627fe 100644 --- a/translations/ru-RU/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ru-RU/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml @@ -2,63 +2,63 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ru-RU/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/ru-RU/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml index dcf3d7d79244..76ece32029eb 100644 --- a/translations/ru-RU/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ru-RU/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml @@ -2,560 +2,560 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` will be removed. Use the `Package` object instead." + description: '`color` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` will be removed. Use the `Package` object instead." + description: '`latestVersion` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` will be removed. Use the `Package` object instead." + description: '`name` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` will be removed. Use the `Package` object instead." + description: '`nameWithOwner` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` will be removed. Use the `Package` object." + description: '`packageFileByGuid` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` will be removed. Use the `Package` object." + description: '`packageFileBySha256` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` will be removed. Use the `Package` object instead." + description: '`packageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` will be removed. Use the `Package` object instead." + description: '`preReleaseVersions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` will be removed. Use the `Package` object instead." + description: '`registryPackageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` will be removed. Use the `Package` object instead." + description: '`repository` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` will be removed. Use the `Package` object instead." + description: '`statistics` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` will be removed. Use the `Package` object." + description: '`tags` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` will be removed. Use the `Package` object." + description: '`topics` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` will be removed. Use the `Package` object instead." + description: '`version` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` will be removed. Use the `Package` object instead." + description: '`versionByPlatform` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` will be removed. Use the `Package` object instead." + description: '`versionBySha256` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` will be removed. Use the `Package` object instead." + description: '`versions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` will be removed. Use the `Package` object instead." + description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` will be removed. Use the `PackageDependency` object instead." + description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` will be removed. Use the `PackageDependency` object instead." + description: '`name` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` will be removed. Use the `PackageDependency` object instead." + description: '`version` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` will be removed. Use the `PackageFile` object instead." + description: '`guid` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` will be removed. Use the `PackageFile` object instead." + description: '`md5` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` will be removed. Use the `PackageFile` object instead." + description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` will be removed. Use the `PackageFile` object instead." + description: '`name` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` will be removed. Use the `PackageFile` object instead." + description: '`packageVersion` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` will be removed. Use the `PackageFile` object instead." + description: '`sha1` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` will be removed. Use the `PackageFile` object instead." + description: '`sha256` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` will be removed. Use the `PackageFile` object instead." + description: '`size` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` will be removed. Use the `PackageFile` object instead." + description: '`url` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` will be removed. Use the `PackageTag` object instead." + description: '`name` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` will be removed. Use the `PackageTag` object instead." + description: '`version` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` will be removed. Use the `PackageVersion` object instead." + description: '`dependencies` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` will be removed. Use the `PackageVersion` object instead." + description: '`fileByName` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` will be removed. Use the `PackageVersion` object instead." + description: '`files` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` will be removed. Use the `PackageVersion` object instead." + description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` will be removed. Use the `PackageVersion` object instead." + description: '`manifest` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` will be removed. Use the `PackageVersion` object instead." + description: '`platform` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` will be removed. Use the `PackageVersion` object instead." + description: '`preRelease` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` will be removed. Use the `PackageVersion` object instead." + description: '`readme` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead." + description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` will be removed. Use the `PackageVersion` object instead." + description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` will be removed. Use the `PackageVersion` object instead." + description: '`release` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` will be removed. Use the `PackageVersion` object instead." + description: '`sha256` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` will be removed. Use the `PackageVersion` object instead." + description: '`size` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` will be removed. Use the `PackageVersion` object instead." + description: '`statistics` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` will be removed. Use the `PackageVersion` object instead." + description: '`summary` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` will be removed. Use the `PackageVersion` object instead." + description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` will be removed. Use the `PackageVersion` object instead." + description: '`version` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead." + description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ru-RU/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/ru-RU/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml index 4b56579d9316..5341a42e26e0 100644 --- a/translations/ru-RU/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ru-RU/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml @@ -2,568 +2,568 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: ContributionOrder.field - description: "`field` will be removed. Only one order field is supported." - reason: "`field` will be removed." + description: '`field` will be removed. Only one order field is supported.' + reason: '`field` will be removed.' date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead." + description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.' reason: pinnedRepositories will be removed date: '2019-10-01T00:00:00+00:00' criticality: breaking owner: cheshire137 - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Organization.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.color - description: "`color` will be removed. Use the `Package` object instead." + description: '`color` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` will be removed. Use the `Package` object instead." + description: '`latestVersion` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.name - description: "`name` will be removed. Use the `Package` object instead." + description: '`name` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` will be removed. Use the `Package` object instead." + description: '`nameWithOwner` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` will be removed. Use the `Package` object." + description: '`packageFileByGuid` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` will be removed. Use the `Package` object." + description: '`packageFileBySha256` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` will be removed. Use the `Package` object instead." + description: '`packageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` will be removed. Use the `Package` object instead." + description: '`preReleaseVersions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` will be removed. Use the `Package` object instead." + description: '`registryPackageType` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.repository - description: "`repository` will be removed. Use the `Package` object instead." + description: '`repository` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` will be removed. Use the `Package` object instead." + description: '`statistics` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.tags - description: "`tags` will be removed. Use the `Package` object." + description: '`tags` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.topics - description: "`topics` will be removed. Use the `Package` object." + description: '`topics` will be removed. Use the `Package` object.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.version - description: "`version` will be removed. Use the `Package` object instead." + description: '`version` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` will be removed. Use the `Package` object instead." + description: '`versionByPlatform` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` will be removed. Use the `Package` object instead." + description: '`versionBySha256` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versions - description: "`versions` will be removed. Use the `Package` object instead." + description: '`versions` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` will be removed. Use the `Package` object instead." + description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` will be removed. Use the `PackageDependency` object instead." + description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` will be removed. Use the `PackageDependency` object instead." + description: '`name` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` will be removed. Use the `PackageDependency` object instead." + description: '`version` will be removed. Use the `PackageDependency` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` will be removed. Use the `PackageFile` object instead." + description: '`guid` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` will be removed. Use the `PackageFile` object instead." + description: '`md5` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` will be removed. Use the `PackageFile` object instead." + description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.name - description: "`name` will be removed. Use the `PackageFile` object instead." + description: '`name` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` will be removed. Use the `PackageFile` object instead." + description: '`packageVersion` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` will be removed. Use the `PackageFile` object instead." + description: '`sha1` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` will be removed. Use the `PackageFile` object instead." + description: '`sha256` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.size - description: "`size` will be removed. Use the `PackageFile` object instead." + description: '`size` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageFile.url - description: "`url` will be removed. Use the `PackageFile` object instead." + description: '`url` will be removed. Use the `PackageFile` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.name - description: "`name` will be removed. Use the `PackageTag` object instead." + description: '`name` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageTag.version - description: "`version` will be removed. Use the `PackageTag` object instead." + description: '`version` will be removed. Use the `PackageTag` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.deleted - description: "`deleted` will be removed. Use the `PackageVersion` object instead." + description: '`deleted` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` will be removed. Use the `PackageVersion` object instead." + description: '`dependencies` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` will be removed. Use the `PackageVersion` object instead." + description: '`fileByName` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` will be removed. Use the `PackageVersion` object instead." + description: '`files` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` will be removed. Use the `PackageVersion` object instead." + description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` will be removed. Use the `PackageVersion` object instead." + description: '`manifest` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` will be removed. Use the `PackageVersion` object instead." + description: '`platform` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` will be removed. Use the `PackageVersion` object instead." + description: '`preRelease` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` will be removed. Use the `PackageVersion` object instead." + description: '`readme` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead." + description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` will be removed. Use the `PackageVersion` object instead." + description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` will be removed. Use the `PackageVersion` object instead." + description: '`release` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` will be removed. Use the `PackageVersion` object instead." + description: '`sha256` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` will be removed. Use the `PackageVersion` object instead." + description: '`size` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` will be removed. Use the `PackageVersion` object instead." + description: '`statistics` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` will be removed. Use the `PackageVersion` object instead." + description: '`summary` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` will be removed. Use the `PackageVersion` object instead." + description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` will be removed. Use the `PackageVersion` object instead." + description: '`version` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead." + description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead." + description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: User.registryPackages - description: "`registryPackages` will be removed. Use the `PackageOwner` object instead." + description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead." + description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.' reason: Renaming GitHub Packages fields and objects. date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: dinahshi - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea diff --git a/translations/ru-RU/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/ru-RU/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml index f5fb1765b079..977c97a5785e 100644 --- a/translations/ru-RU/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/ru-RU/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml @@ -2,71 +2,71 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea @@ -86,15 +86,15 @@ upcoming_changes: owner: oneill38 - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden @@ -107,21 +107,21 @@ upcoming_changes: owner: oneill38 - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ru-RU/data/graphql/graphql_previews.yml b/translations/ru-RU/data/graphql/graphql_previews.yml index e00c8f5704f1..ae939b5e57a6 100644 --- a/translations/ru-RU/data/graphql/graphql_previews.yml +++ b/translations/ru-RU/data/graphql/graphql_previews.yml @@ -102,7 +102,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: Pinned Issues Preview description: This preview adds support for pinned issues. 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 c8040777f133..f12ecd03316b 100644 --- a/translations/ru-RU/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ru-RU/data/graphql/graphql_upcoming_changes.public.yml @@ -2,119 +2,119 @@ upcoming_changes: - location: Migration.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." + 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' criticality: breaking owner: tambling - location: AssignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead." - reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned" + description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.' + reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead." - reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned" + description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.' + reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned' date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` will be removed. Use the `assignee` field instead." + description: '`user` will be removed. Use the `assignee` field instead.' reason: Assignees can now be mannequins. date: '2020-01-01T00:00:00+00:00' criticality: breaking owner: tambling - location: Query.sponsorsListing - description: "`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead." - reason: "`Query.sponsorsListing` will be removed." + description: '`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead.' + reason: '`Query.sponsorsListing` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: Sponsorship.maintainer - description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead." - reason: "`Sponsorship.maintainer` will be removed." + description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.' + reason: '`Sponsorship.maintainer` will be removed.' date: '2020-04-01T00:00:00+00:00' criticality: breaking owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending members consume a license date: '2020-07-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead." + description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.' reason: Repository invitations can now be associated with an email, not only an invitee. date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Issue.timeline - description: "`timeline` will be removed. Use Issue.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use Issue.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: PullRequest.timeline - description: "`timeline` will be removed. Use PullRequest.timelineItems instead." - reason: "`timeline` will be removed" + description: '`timeline` will be removed. Use PullRequest.timelineItems instead.' + reason: '`timeline` will be removed' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` will be removed." - reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee." + description: '`INVITEE_LOGIN` will be removed.' + reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead." - reason: "`Sponsorship.sponsor` will be removed." + description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.' + reason: '`Sponsorship.sponsor` will be removed.' date: '2020-10-01T00:00:00+00:00' criticality: breaking owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All members consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All outside collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` will be removed." + description: '`isUnlicensed` will be removed.' reason: All pending collaborators consume a license date: '2021-01-01T00:00:00+00:00' criticality: breaking owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." + description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.' reason: DRAFT state will be removed from this enum and `isDraft` should be used instead date: '2021-01-01T00:00:00+00:00' criticality: breaking diff --git a/translations/ru-RU/data/reusables/feature-preview/feature-preview-setting.md b/translations/ru-RU/data/reusables/feature-preview/feature-preview-setting.md new file mode 100644 index 000000000000..8af532d9db24 --- /dev/null +++ b/translations/ru-RU/data/reusables/feature-preview/feature-preview-setting.md @@ -0,0 +1 @@ +1. In the upper-right corner of any page, click your profile photo, then click **Feature preview**. ![Feature preview button](/assets/images/help/settings/feature-preview-button.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/gated-features/secret-scanning.md b/translations/ru-RU/data/reusables/gated-features/secret-scanning.md new file mode 100644 index 000000000000..bd279034eee8 --- /dev/null +++ b/translations/ru-RU/data/reusables/gated-features/secret-scanning.md @@ -0,0 +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 %} diff --git a/translations/ru-RU/data/reusables/interactions/interactions-detail.md b/translations/ru-RU/data/reusables/interactions/interactions-detail.md index 9193cd04e704..187a3e73074d 100644 --- a/translations/ru-RU/data/reusables/interactions/interactions-detail.md +++ b/translations/ru-RU/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -When restrictions are enabled, only the specified group of {% data variables.product.product_name %} users will be able to participate in interactions. Restrictions expire 24 hours from the time they are set. +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. diff --git a/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md b/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md index a5e3b6f7f871..24313880baea 100644 --- a/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md +++ b/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. 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)." {% endnote %} diff --git a/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md new file mode 100644 index 000000000000..b0cddc8bcb84 --- /dev/null +++ b/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% endnote %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/secret-scanning/beta.md b/translations/ru-RU/data/reusables/secret-scanning/beta.md index 68ed06f9c93a..3625bb7a3e26 100644 --- a/translations/ru-RU/data/reusables/secret-scanning/beta.md +++ b/translations/ru-RU/data/reusables/secret-scanning/beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change. To request access to the beta, [join the waitlist](https://github.com/features/security/advanced-security/signup). +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change. {% endnote %} diff --git a/translations/ru-RU/data/ui.yml b/translations/ru-RU/data/ui.yml index b26870cdbb0c..dbb583d01aa4 100644 --- a/translations/ru-RU/data/ui.yml +++ b/translations/ru-RU/data/ui.yml @@ -4,9 +4,10 @@ header: contact: Контакт notices: ghae_silent_launch: GitHub AE is currently under limited release. Please contact our Sales Team to find out more. + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation. If there's a problem with translations on this page, please let us know. localization_in_progress: Hello, explorer! This page is under active development or still in translation. For the most up-to-date and accurate information, please visit our English documentation. - product_in_progress: '👋 Hello, explorer! This page is under active development. For the most up-to-date and accurate information, please visit our developer documentation.' + early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' search: need_help: Need help? placeholder: Search topics, products... @@ -19,7 +20,7 @@ toc: guides: Руководства whats_new: What's new pages: - article_version: "Article version:" + article_version: 'Article version:' miniToc: В этой статье errors: oops: Ooops! diff --git a/translations/ru-RU/data/variables/action_code_examples.yml b/translations/ru-RU/data/variables/action_code_examples.yml new file mode 100644 index 000000000000..9cc8394aff49 --- /dev/null +++ b/translations/ru-RU/data/variables/action_code_examples.yml @@ -0,0 +1,149 @@ +--- +- + title: Starter workflows + description: Workflow files for helping people get started with GitHub Actions + languages: TypeScript + href: actions/starter-workflows + tags: + - official + - workflows +- + title: Example services + description: Example workflows using service containers + languages: JavaScript + href: actions/example-services + tags: + - service containers +- + title: Declaratively setup GitHub Labels + description: GitHub Action to declaratively setup labels across repos + languages: JavaScript + href: lannonbr/issue-label-manager-action + tags: + - issues + - labels +- + title: Declaratively sync GitHub labels + description: GitHub Action to sync GitHub labels in the declarative way + languages: 'Go, Dockerfile' + href: micnncim/action-label-syncer + tags: + - issues + - labels +- + title: Add releases to GitHub + description: Publish Github releases in an action + languages: 'Dockerfile, Shell' + href: elgohr/Github-Release-Action + tags: + - релизы + - publishing +- + title: Publish a docker image to Dockerhub + description: A Github Action used to build and publish Docker images + languages: 'Dockerfile, Shell' + href: elgohr/Publish-Docker-Github-Action + tags: + - докер + - publishing + - build +- + title: Create an issue using content from a file + description: A GitHub action to create an issue using content from a file + languages: 'JavaScript, Python' + href: peter-evans/create-issue-from-file + tags: + - issues +- + title: Publish GitHub Releases with Assets + description: GitHub Action for creating GitHub Releases + languages: 'TypeScript, Shell, JavaScript' + href: softprops/action-gh-release + tags: + - релизы + - publishing +- + title: GitHub Project Automation+ + description: Automate GitHub Project cards with any webhook event. + languages: JavaScript + href: alex-page/github-project-automation-plus + tags: + - projects + - automation + - issues + - pull requests +- + title: Run GitHub Actions Locally with a web interface + description: Runs GitHub Actions workflows locally (local) + languages: 'JavaScript, HTML, Dockerfile, CSS' + href: phishy/wflow + tags: + - local-development + - devops + - докер +- + title: Run your GitHub Actions locally + description: Run GitHub Actions Locally in Terminal + languages: 'Go, Shell' + href: nektos/act + tags: + - local-development + - devops + - докер +- + title: Build and Publish Android debug APK + description: Build and release debug APK from your Android project + languages: 'Shell, Dockerfile' + href: ShaunLWM/action-release-debugapk + tags: + - android + - build +- + title: Generate sequential build numbers for GitHub Actions + description: GitHub action for generating sequential build numbers. + languages: JavaScript + href: einaregilsson/build-number + tags: + - build + - automation +- + title: GitHub actions to push back to repository + description: Push Git changes to GitHub repository without authentication difficulties + languages: 'JavaScript, Shell' + href: ad-m/github-push-action + tags: + - publishing +- + title: Generate release notes based on your events + description: Action to auto generate a release note based on your events + languages: 'Shell, Dockerfile' + href: Decathlon/release-notes-generator-action + tags: + - релизы + - publishing +- + title: Create a GitHub wiki page based on the provided markdown file + description: Create a GitHub wiki page based on the provided markdown file + languages: 'Shell, Dockerfile' + href: Decathlon/wiki-page-creator-action + tags: + - wiki + - publishing +- + title: 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: + - projects + - issues + - labels +- + title: Add Label to your Pull Requests based on the author team name + description: Github action to label your pull requests based on the author name + languages: 'TypeScript, JavaScript' + href: JulienKode/team-labeler-action + tags: + - запрос на включение внесенных изменений + - labels diff --git a/translations/ru-RU/data/variables/contact.yml b/translations/ru-RU/data/variables/contact.yml index d230130d9418..890e996840ea 100644 --- a/translations/ru-RU/data/variables/contact.yml +++ b/translations/ru-RU/data/variables/contact.yml @@ -10,7 +10,7 @@ contact_dmca: >- {% if currentVersion == "free-pro-team@latest" %}[Copyright claims form](https://github.com/contact/dmca){% endif %} contact_privacy: >- {% if currentVersion == "free-pro-team@latest" %}[Privacy contact form](https://github.com/contact/privacy){% endif %} -contact_enterprise_sales: '[GitHub''s Sales team](https://enterprise.github.com/contact)' +contact_enterprise_sales: "[GitHub's Sales team](https://enterprise.github.com/contact)" contact_feedback_actions: '[Feedback form for GitHub Actions](https://support.github.com/contact/feedback?contact[category]=actions)' #The team that provides Standard Support enterprise_support: 'GitHub Enterprise Support' diff --git a/translations/ru-RU/data/variables/release_candidate.yml b/translations/ru-RU/data/variables/release_candidate.yml new file mode 100644 index 000000000000..ec65ef6f9445 --- /dev/null +++ b/translations/ru-RU/data/variables/release_candidate.yml @@ -0,0 +1,2 @@ +--- +version: '' 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 22cab259846e..5a02b9e89ed8 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 @@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +authors: + - potatoqualitee --- {% data reusables.actions.enterprise-beta %} @@ -28,7 +30,7 @@ versions: ### 为 Pester 添加工作流程 -要使用 PowerShell 和 Pester 自动执行测试，可以添加一个在每次有更改推送到存储库时运行的工作流程。 在以下示例中，`Test-Path` 用于检查文件 `resultsfile.log` 是否存在。 +要使用 PowerShell 和 Pester 自动执行测试，您可以添加在每次将更改推送到仓库时运行的工作流程。 在以下示例中，`Test-Path` 用于检查文件 `resultsfile.log` 是否存在。 此示例工作流程文件必须添加到您仓库的 `.github/workflows/` 目录： 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 new file mode 100644 index 000000000000..729b1d13410a --- /dev/null +++ b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md @@ -0,0 +1,318 @@ +--- +title: Building and testing Ruby +intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### 简介 + +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. + +### 基本要求 + +We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. 更多信息请参阅： + +- [了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions) +- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) + +### Starting with the Ruby workflow template + +{% 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). + +要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。 + +{% raw %} +```yaml +name: Ruby + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: 2.6 + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Specifying the Ruby version + +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). + +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. + +The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 # Not needed with a .ruby-version file +- run: bundle install +- run: bundle exec rake +``` +{% 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. + +### Testing with multiple versions of 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. + +{% raw %} +```yaml +strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] +``` +{% 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." + +The full updated workflow with a matrix strategy could look like this: + +{% raw %} +```yaml +name: Ruby CI + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + + runs-on: ubuntu-latest + + strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby ${{ matrix.ruby-version }} + # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, + # change this to (see https://github.com/ruby/setup-ruby#versioning): + # uses: ruby/setup-ruby@v1 + uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + with: + ruby-version: ${{ matrix.ruby-version }} + - name: Install dependencies + run: bundle install + - name: Run tests + run: bundle exec rake +``` +{% endraw %} + +### Installing dependencies with 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. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 +- run: bundle install +``` +{% endraw %} + +#### 缓存依赖项 + +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 +steps: +- uses: ruby/setup-ruby@v1 + with: + bundler-cache: true +``` +{% 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. + +**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)”。 + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + ${{ runner.os }}-gems- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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: + +{% raw %} +```yaml +steps: +- uses: actions/cache@v2 + with: + path: vendor/bundle + key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}- +- name: Bundle install + run: | + bundle config path vendor/bundle + bundle install --jobs 4 --retry 3 +``` +{% 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. + +{% raw %} +```yaml +name: Matrix Testing + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + test: + runs-on: ${{ matrix.os }}-latest + strategy: + fail-fast: false + matrix: + os: [ubuntu, macos] + ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head] + continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }} + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: ${{ matrix.ruby }} + - run: bundle install + - run: bundle exec rake +``` +{% 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. + +{% raw %} +```yaml +name: Linting + +on: [push] + +jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + - name: Rubocop + run: rubocop +``` +{% endraw %} + +### Publishing Gems + +You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. + +您可以使用仓库密码存储发布软件包所需的访问令牌或凭据。 The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. + +{% raw %} +```yaml + +name: Ruby Gem + +on: + # Manually publish + workflow_dispatch: + # Alternatively, publish whenever changes are merged to the default branch. + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + build: + name: Build + Publish + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Ruby 2.6 + uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 + - run: bundle install + + - name: Publish to GPR + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem + env: + GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}" + OWNER: ${{ github.repository_owner }} + + - name: Publish to RubyGems + run: | + mkdir -p $HOME/.gem + touch $HOME/.gem/credentials + chmod 0600 $HOME/.gem/credentials + printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials + gem build *.gemspec + gem push *.gem + env: + GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" +``` +{% endraw %} + diff --git a/translations/zh-CN/content/actions/guides/index.md b/translations/zh-CN/content/actions/guides/index.md index 5056026c50df..f3da642ef2f2 100644 --- a/translations/zh-CN/content/actions/guides/index.md +++ b/translations/zh-CN/content/actions/guides/index.md @@ -31,6 +31,7 @@ versions: {% 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/zh-CN/content/actions/guides/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md index 2909e18a9ec2..bb65fffb6e1d 100644 --- a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/zh-CN/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/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index e6e6040685fc..7e5a0986dcf5 100644 --- a/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/zh-CN/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/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md index 6a9f1499ed9a..af2d6dd6445e 100644 --- a/translations/zh-CN/content/actions/index.md +++ b/translations/zh-CN/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: 自托管运行器组访问权限更改 - date: '2020-10-16' - href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ + title: 11 月 16 日删除 set-env 和 add-path 命令 + date: '2020-11-09' + href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - title: 更改构件和日志保留天数的功能 - date: '2020-10-08' - href: https://github.blog/changelog/2020-10-08-github-actions-ability-to-change-retention-days-for-artifacts-and-logs + title: Ubuntu-latest 工作流程将使用 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: 弃用 set-env 和 add-path 命令 - date: '2020-10-01' - href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands + title: MacOS Big Sur 预览 + date: '2020-10-29' + href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview - - title: 微调对外部操作的访问 - date: '2020-10-01' - href: https://github.blog/changelog/2020-10-01-github-actions-fine-tune-access-to-external-actions + title: 自托管运行器组访问权限更改 + date: '2020-10-16' + href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ 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 %}
-

更多指南

+

代码示例

+ +
+ +
-
- -
-

构建和测试 Node.js

-

使用 GitHub Actions 在 Node.js 应用程序中支持 CI。

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

构建和测试 Python

-

使用 GitHub Actions 在 Python 应用程序中支持 CI。

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

使用 Maven 构建和测试 Java

-

使用 GitHub Actions 在包含 Maven 的 Java 项目中支持 CI。

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

使用 Gradle 构建和测试 Java

-

使用 GitHub Actions 在包含 Gradle 的 Java 项目中支持 CI。

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

使用 Ant 构建和测试 Java

-

使用 GitHub Actions 在包含 Ant 的 Java 项目中支持 CI。

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

发布 Node.js 包

-

使用 GitHub Actions 将 Node.js 包发布到 GitHub Packages 或 npm。

-
- JavaScript/TypeScript - CI -
-
-
- {% octicon "workflow" class="flex-shrink-0" %} - /guides/publishing-nodejs-packages -
- -
+ {% render 'code-example-card' for actionsCodeExamples as example %}
- 显示所有指南 {% octicon "arrow-right" %} + + +
+
{% octicon "search" width="24" %}
+

抱歉，找不到结果

+

似乎没有适合您的过滤条件的示例。
请尝试其他过滤条件或添加代码示例

+ 了解如何添加代码示例 {% octicon "arrow-right" %} +
+{% endif %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md index bc578e502fce..f25fdcce50d1 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -87,7 +87,7 @@ steps: ### 对操作使用输入和输出 -操作通常接受或需要输入并生成可以使用的输出。 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. +操作通常接受或需要输入并生成可以使用的输出。 例如，操作可能要求您指定文件的路径、标签的名称或它将用作操作处理一部分的其他数据。 要查看操作的输入和输出，请检查仓库根目录中的 `action.yml` 或 `action.yaml`。 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 ae55800e5a95..8df2adc6c219 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. 作业中的每个步骤在同一运行器上执行，可让该作业中的操作互相共享数据。 #### 操作 @@ -50,7 +50,7 @@ _操作_ 是独立命令，它们组合到_步骤_以创建_作业_。 操作是 #### 运行器 -运行器是安装了 {% data variables.product.prodname_actions %} 运行器应用程序的服务器。 您可以使用 {% data variables.product.prodname_dotcom %} 托管的运行器或托管您自己的运行器。 运行器将侦听可用的作业，每次运行一个作业，并将进度、日志和结果报告回 {% data variables.product.prodname_dotcom %}。 对于 {% data variables.product.prodname_dotcom %} 托管的运行器，工作流程中的每项作业都会在一个新的虚拟环境中运行。 +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_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 @@ _操作_ 是独立命令，它们组合到_步骤_以创建_作业_。 操作是 #### 可视化工作流程文件 -在此关系图中，您可以看到刚刚创建的工作流程文件，以及 {% data variables.product.prodname_actions %} 组件在层次结构中的组织方式。 每个步骤执行单个操作。 步骤 1 和 2 使用预构建的社区操作。 要查找更多为工作流预构建的操作，请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-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)”。 ![工作流程概述](/assets/images/help/images/overview-actions-event.png) diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 65e03f4f3162..75d37ca3bbc4 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/zh-CN/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 +### 配置工作流程手动运行 -要手动运行工作流程，工作流程必须配置为在发生 `workflow_dispatch` 事件时运行。 For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". +要手动运行工作流程，工作流程必须配置为在发生 `workflow_dispatch` 事件时运行。 有关配置 `workflow_paid` 事件的更多信息，请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#workflow_dispatch)”。 ### 在 {% data variables.product.prodname_dotcom %} 上运行工作流程 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md index 4adc5f2ffa96..58e6c9ea7fbb 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/zh-CN/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/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index 1e80cf9fcac6..adcc9aa67de2 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -73,3 +73,69 @@ versions: - “[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”，以获取深入教程 - “[指南](/actions/guides)”，以获取特定用例和示例 - [github/super-linter](https://github.com/github/super-linter)，以获取有关配置 Super-Linter 操作的详细信息 + + 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 148a01f7ae90..826301cad378 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 @@ -100,7 +100,7 @@ versions: ##### 示例 -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: +要使用 `Workflow_paid` 事件，您需要将其作为触发器包含在您的 GitHub Actions 工作流程文件中。 下面的示例仅在手动触发时运行工作流程： ```yaml on: workflow_dispatch @@ -327,6 +327,7 @@ on: 例如，您可以选择在拉取请求中发生评论事件时运行 `pr_commented` 作业，在议题中发生评论事件时运行 `issue_commented` 作业。 +{% raw %} ```yaml on: issue_comment @@ -349,6 +350,7 @@ jobs: - run: | echo "Comment on issue #${{ github.event.issue.number }}" ``` +{% endraw %} #### `issues` diff --git a/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md index 6d38800f155e..03a010a325f4 100644 --- a/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md @@ -31,7 +31,7 @@ versions: {% data variables.product.prodname_dotcom %} 在 Microsoft Azure 中安装了 {% data variables.product.prodname_actions %} 运行器应用程序的 Standard_DS2_v2 虚拟机上托管 Linux 和 Windows 运行器。 {% data variables.product.prodname_dotcom %} 托管的运行器应用程序是 Azure Pipelines Agent 的复刻。 入站 ICMP 数据包被阻止用于所有 Azure 虚拟机，因此 ping 或 traceroute 命令可能无效。 有关 Standard_DS2_v2 机器资源的更多信息，请参阅 Microsoft Azure 文档中的“[Dv2 和 DSv2 系列](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)”。 -{% data variables.product.prodname_dotcom %} 使用 [MacStadium](https://www.macstadium.com/) 托管 macOS 运行器。 +{% data variables.product.prodname_dotcom %} 在 {% data variables.product.prodname_dotcom %} 自己的 macOS Cloud 中托管 macOS 运行器。 #### {% data variables.product.prodname_dotcom %} 托管的运行器的管理权限 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 45e50ee3e29e..46a9883e0750 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 @@ -446,7 +446,7 @@ 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`** @@ -492,7 +492,7 @@ 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 @@ -659,7 +659,7 @@ steps: - `cmd` - 除了编写脚本来检查每个错误代码并相应地响应之外，似乎没有办法完全选择快速失败行为。 由于我们默认不能实际提供该行为，因此您需要将此行为写入脚本。 - - `cmd.exe` 在退出时带有其执行的最后一个程序的错误等级，并且会将错误代码返回到运行程序。 此行为在内部与上一个 `sh` 和 `pwsh` 默认行为一致，是 `cmd.exe` 的默认值，所以此行为保持不变。 + - `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` 的默认值，所以此行为保持不变。 #### **`jobs..steps.with`** @@ -718,7 +718,7 @@ steps: entrypoint: /a/different/executable ``` -`entrypoint` 关键词旨在用于 Docker 容器操作，但您也可以将其用于未定义任何输入的 JavaScript 操作。 +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. #### **`jobs..steps.env`** diff --git a/translations/zh-CN/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md index 9661a97ffca7..5111548a0f4a 100644 --- a/translations/zh-CN/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md +++ b/translations/zh-CN/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: 关于企业的身份和访问管理 +shortTitle: 关于身份和访问管理 +intro: '您可以使用 {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} 的内置身份验证，或者选择 CAS、LDAP 或 SAML{% else %}SAML 单点登录 (SSO) 和跨域身份管理系统 (SCIM){% endif %} 来集中管理对 {% data variables.product.prodname_dotcom_the_website %} 上{% if currentVersion == "free-pro-team@latest" %}企业拥有的组织{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} {% data variables.product.product_location %}{% endif %}的访问。' product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About identity and access management for your enterprise +### 关于企业的身份和访问管理 {% 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)." +在 IdP 上为 {% data variables.product.product_name %} 配置应用程序后，可以通过将应用程序分配到 IdP 上的用户来授予其访问 {% data variables.product.product_location %} 的权限。 有关用于 {% data variables.product.product_name %} 的 SAML SSO 的详细信息，请参阅“[为企业配置 SAML 单点登录](/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 %} 更多信息请参阅“[配置企业的用户预配](/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)." +要了解如何合适特定 IdP 为 {% data variables.product.product_location %} 配置身份验证和用户预配，请参阅“[使用身份提供程序配置身份验证和预配](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)”。 {% endif %} ### 延伸阅读 -- [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 +- OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security) +- IETF 网站上的[跨域身份管理系统：协议 (RFC 7644)](https://tools.ietf.org/html/rfc7644) diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 6b84c58a5794..3ae556023db1 100644 --- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/zh-CN/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: 使用 Azure AD 为企业配置身份验证和预配 +shortTitle: 使用 Azure AD 配置 +intro: 您可以使用 Azure Active Directory (Azure AD) 中的租户作为身份提供程序 (IDP) 来集中管理 {% data variables.product.product_location %} 的身份验证和用户预配。 +permissions: 企业所有者可在 {% data variables.product.product_name %} 上为企业配置身份验证和预配。 product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About authentication and user provisioning with Azure AD +### 关于使用 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. +Azure Active Directory (Azure AD) 是一项来自 Microsoft 的服务，它允许您集中管理用户帐户和 web 应用程序访问。 更多信息请参阅 Microsoft 文档中的[什么是 Azure Active Directory？](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)。 -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 %}. +要管理身份以及对 {% data variables.product.product_name %} 的访问，您可以使用 Azure AD 租户作为 SAML IdP 进行身份验证。 您还可以配置 Azure AD 以使用 SCIM自动预配帐户和访问权限。 此配置允许您为 Azure AD 租户中的用户帐户分配或取消分配 {% data variables.product.prodname_ghe_managed %} 应用程序，以在 {% 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)." +有关在 {% data variables.product.product_location %} 上管理企业的身份和访问权限的详细信息，请参阅“[管理企业的身份和访问权限](/admin/authentication/managing-identity-and-access-for-your-enterprise)”。 ### 基本要求 -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. +要使用 Azure AD 配置 {% data variables.product.product_name %} 的身份验证和用户预配，您必须有 Azure AD 帐户和租户。 更多信息请参阅 [Azure AD 网站](https://azure.microsoft.com/free/active-directory)和 Microsoft 文档中的[快速入门：创建 Azure Active Directory 租户](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)。 -{% 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 %} 有关在来自 Azure AD 的 SAML 声明中包含 `administrator` 属性的详细信息， 请参阅 Microsoft 文档中的[如何：为企业应用程序自定义 SAML 令牌中发行的声明](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization)。 {% data reusables.saml.create-a-machine-user %} -### Configuring authentication and user provisioning with Azure AD +### 使用 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. 在 Azure AD 中，将 {% data variables.product.ae_azure_ad_app_link %} 添加到您的租户并配置单点登录。 更多信息请参阅 Microsoft 文档中的[教程：与 {% data variables.product.prodname_ghe_managed %} 的 Azure Active Directory 单点登录 (SSO) 集成](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial)。 - | 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. 在 {% data variables.product.prodname_ghe_managed %} 中，输入 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)." + - 如果已为使用其他 IdP 的 {% data variables.product.product_location %} 配置 SAML SSO，并且希望改为使用 Azure AD，您可以编辑配置。 更多信息请参阅“[配置企业的 SAML 单点登录](/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. 在 {% data variables.product.product_name %} 中启用用户预配，并在 Azure AD 中配置用户预配。 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)”。 {% endif %} diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md index ef320ac2ce7e..fe51bf132399 100644 --- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md +++ b/translations/zh-CN/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: 使用身份提供程序配置身份验证和预配 +intro: 您可以使用同时支持 SAML 单点登录 (SSO) 和跨域身份管理系统 (SCIM) 的标识提供程序 (IdP) 来配置 {% data variables.product.product_location %} 的身份验证和用户预配。 mapTopic: true versions: github-ae: '*' diff --git a/translations/zh-CN/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md index ebb4f6210753..a2729cab26f4 100644 --- a/translations/zh-CN/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/zh-CN/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: 为企业配置 SAML 单点登录 +shortTitle: 配置 SAML SSO +intro: 您可以为企业配置 SAML 单点登录 (SSO)，这允许您使用身份提供程序 (IdP) 集中控制 {% data variables.product.product_location %} 的身份验证。 product: '{% data reusables.gated-features.saml-sso %}' -permissions: Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}. +permissions: 企业所有者可在 {% data variables.product.product_name %} 上为企业配置 SAML SSO。 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. +SAML SSO 允许您从 SAML IDP 集中控制和安全访问 {% data variables.product.product_location %}。 当未经身份验证的用户在浏览器中访问 {% data variables.product.product_location %} 时，{% data variables.product.product_name %} 会将用户重定向到您的 SAML IDP 进行身份验证。 在用户使用 IdP 上的帐户成功进行身份验证后，IdP 会将用户重定向回 {% data variables.product.product_location %}。 {% data variables.product.product_name %} 将验证 IdP 的响应，然后授予用户访问权限。 -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. +当用户在 IdP 上成功进行身份验证后，用户对 {% data variables.product.product_location %} 的 SAML 会话将在浏览器中激活 24 小时。 24 小时后，用户必须再次使用您的 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 %} 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 {% endif %} -### Supported identity providers +### 支持的身份提供程序 -{% 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 %} 支持 SAML SSO 与采用 SAML 2.0 标准的 IdP 一起使用。 更多信息请参阅 OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)。 -{% data variables.product.company_short %} has tested SAML SSO for {% data variables.product.product_name %} with the following IdPs. +{% data variables.product.company_short %} 已使用以下 IdP 测试 {% data variables.product.product_name %} 的 SAML SSO。 {% if currentVersion == "github-ae@latest" %} - Azure AD {% endif %} -### Enabling SAML SSO +### 启用 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. +以下 IdP 提供有关为 {% data variables.product.product_name %} 配置 SAML SSO 的文档。 如果您的 IdP 未列出，请与您的 IdP 联系，以请求 {% data variables.product.product_name %}。 -| 值 | Other names | 描述 | 示例 | -|:--------------------------------------- |:----------- |:-------------------------------------------------------------------------- |:------------------------- | -| 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 | 更多信息 | + |:-------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [教程： Microsoft 文档中的“与 {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) 的 Azure Active Directory 单点登录 (SSO) 集成” | + +在 {% data variables.product.product_name %} 的初始化期间，您必须在 IdP 上将 {% data variables.product.product_name %} 配置为 SAML 服务提供程序 (SP)。 您必须在 IdP 上输入多个唯一值以将 {% data variables.product.product_name %} 配置为有效的 SP。 + +| 值 | 其他名称 | 描述 | 示例 | +|:-------------------- |:------ |:---------------------------------------------------------- |:------------------------- | +| SP 实体 ID | SP URL | {% data variables.product.prodname_ghe_managed %} 顶级 URL | https://YOUR-GITHUB-AE-HOSTNAME | +| SP 断言使用者服务 (ACS) URL | 回复 URL | IdP 发送 SAML 响应的 URL | https://YOUR-GITHUB-AE-HOSTNAME/saml/consume | +| SP 单点登录 (SSO) URL | | IdP 开始 SSO 的 URL | https://YOUR-GITHUB-AE-HOSTNAME/sso | {% endif %} -### Editing the SAML SSO configuration +### 编辑 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. +如果 IdP 的详细信息发生更改，则需要编辑 {% data variables.product.product_location %} 的 SAML SSO 配置。 例如，如果 IdP 的证书过期，您可以编辑公共证书的值。 {% 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. 在“SAML single sign-on（SAML 单点登录）”下，键入 IdP 的新详细信息。 ![包含企业 SAML SSO 配置 IdP 详细信息的文本输入字段](/assets/images/help/saml/ae-edit-idp-details.png) +1. （可选）单击 {% octicon "pencil" aria-label="The edit icon" %} 以配置新的签名或摘要方法。 ![用于更改签名和摘要方法的编辑图标](/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. 单击 **Save（保存）**。 !["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)." + - 使用下拉菜单并选择新的签名或摘要方法。 ![用于选择新签名或摘要方法的下拉菜单](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. 为确保输入的信息正确，请单击 **Test SAML configuration（测试 SAML 配置）**。 !["Test SAML configuration（测试 SAML 配置）"按钮](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. 单击 **Save（保存）**。 ![用于 SAML SSO 配置的"Save（保存）"按钮](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. （可选）要自动预配和取消预配 {% data variables.product.product_location %} 的用户帐户，请使用 SCIM 重新配置用户预配。 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 {% endif %} -### Disabling SAML SSO +### 禁用 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. +**警告**：如果您对 {% data variables.product.product_location %} 禁用 SAML SSO，则没有现有 SAML SSO 会话的用户无法登录 {% data variables.product.product_location %}。 {% data variables.product.product_location %} 上的 SAML SSO 会话在 24 小时后结束。 {% 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. 在“SAML single sign-on”（SAML 单点登录）下，取消选择 **Enable SAML authentication（启用 SAML 身份验证）**。 !["Enable SAML authentication（启用 SAML 身份验证）"的复选框](/assets/images/help/saml/ae-saml-disabled.png) +1. 要禁用 SAML SSO 并要求使用在初始化期间创建的内置用户帐户登录，请单击“**Save（保存）**”。 ![用于 SAML SSO 配置的"Save（保存）"按钮](/assets/images/help/saml/ae-saml-disabled-save.png) {% endif %} diff --git a/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index 77a462b67f3f..743a4ee79fc2 100644 --- a/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/zh-CN/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: 为企业配置用户预配 +shortTitle: 配置用户预配 +intro: 您可以为企业配置跨域身份管理 (SCIM)，以在将 {% data variables.product.product_location %} 的应用程序分配给身份提供商 (IdP) 上的用户时，就自动在 {% data variables.product.product_location %} 上预配用户帐户。 +permissions: 企业所有者可在 {% data variables.product.product_name %} 上为企业配置用户预配。 product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About user provisioning for your enterprise +### 关于企业的用户预配 -{% 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 %} 更多信息请参阅“[配置企业的 SAML 单点登录](/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 %} 有关 SCIM 的更多信息，请参阅 IETF 网站上的[跨域身份管理系统：协议 (RFC 7644)](https://tools.ietf.org/html/rfc7644)。 {% 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. +配置预配允许 IdP 在您将 {% data variables.product.product_name %} 的应用程序分配或取消分配给 IdP 上的用户时与 {% data variables.product.product_location %} 通信。 当您分配应用程序时，IdP 将提示 {% data variables.product.product_location %} 创建帐户并向用户发送一封登录电子邮件。 取消分配应用程序时，IdP 将与 {% data variables.product.product_name %} 通信以取消任何 SAML 会话并禁用成员的帐户。 -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. +要为企业配置预配，必须在 {% data variables.product.product_name %} 上启用预配，然后在 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. +IdP 上的预配应用程序通过企业的 SCIM API 与 {% data variables.product.product_name %} 通信。 更多信息请参阅 {% data variables.product.prodname_dotcom %} REST API 文档中的“[GitHub Enterprise 管理](/rest/reference/enterprise-admin#scim)”。 {% endif %} -### Supported identity providers +### 支持的身份提供程序 {% 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)." +要自动预配和解除预配从 IdP 访问 {% data variables.product.product_location %}，必须先在初始化 {% data variables.product.product_name %} 时配置 SAML SSO。 更多信息请参阅“[初始化 {% 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 %}. +您必须对 IdP 具有管理访问权限，才能配置应用程序进行 {% data variables.product.product_name %} 的用户预配。 {% endif %} -### Enabling user provisioning for your enterprise +### 为企业启用用户预配 {% if currentVersion == "github-ae@latest" %} -1. While signed into +1. 作为企业所有者登录到 -{% data variables.product.product_location %} as an enterprise owner, create a personal access token with **admin:enterprise** scope. 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +{% data variables.product.product_location %} 时，创建作用域为 **admin:enterprise** 的个人访问令牌。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 {% note %} **注意**： - - 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. + - 要创建个人访问令牌，我们建议使用初始化期间创建的第一个企业所有者的帐户。 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)。” + - 您需要此个人访问令牌在 IdP 上为 SCIM 配置应用程序。 将令牌安全地存储在密码管理器中，直到您稍后在这些说明中再次需要该令牌。 {% 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. + **警告**：如果创建个人访问令牌的企业所有者的用户帐户已停用或取消预配，则您的 IdP 将不再自动预配和取消预配企业用户帐户。 另一个企业所有者必须创建新的个人访问令牌，并在 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. 单击 **Save（保存）**。 ![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 %}. - - | 值 | Other names | 描述 | 示例 | - |:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- | - | 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 | +1. 在“SAML User Provisioning（SAML 用户预配）”下，选择 **Require SCIM user provisioning（需要 SAML 用户预配）**。 ![企业安全性设置内的"Require SCIM user provisioning（需要 SCIM 用户预配）"复选框](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) +1. 单击 **Save（保存）**。 ![企业安全性设置中"Require SCIM user provisioning（需要 SCIM 用户预配）"下的 Save（保存）按钮](/assets/images/help/enterprises/settings-scim-save.png) +1. 在 IdP 上 {% data variables.product.product_name %} 的应用程序中配置用户预配。 + + 以下 IdP 提供有关为 {% data variables.product.product_name %} 配置预配的文档。 如果您的 IdP 未列出，请与您的 IdP 联系，以请求 {% data variables.product.product_name %}。 + + | IdP | 更多信息 | + |:-------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [教程：Microsoft 文档中的“配置 {% data variables.product.prodname_ghe_managed %} 进行自动用户预配](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial)” | + + IdP 上的应用程序需要两个值来预配或取消预配 {% data variables.product.product_location %} 上的用户帐户。 + + | 值 | 其他名称 | 描述 | 示例 | + |:---- |:----------- |:-------------------------------------------------------------------------- |:------------------------- | + | URL | 租户 URL | {% data variables.product.prodname_ghe_managed %} 上企业的 SCIM 预配 API 的 URL | https://YOUR-GITHUB-AE-HOSTNAME/scim/v2 | + | 共享机密 | 个人访问令牌、机密令牌 | IdP 上的应用程序用于代表企业所有者执行预配任务的令牌 | 您在步骤 1 中创建的个人访问令牌 | {% endif %} diff --git a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md index 9b4b3f0a0aae..75a70325baf3 100644 --- a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md +++ b/translations/zh-CN/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: 管理企业的身份和访问权限 +shortTitle: 管理身份和访问权限 +intro: 您可以集中管理帐户以及对 {% data variables.product.product_location %} 的访问权限。 mapTopic: true versions: github-ae: '*' diff --git a/translations/zh-CN/content/admin/configuration/about-enterprise-configuration.md b/translations/zh-CN/content/admin/configuration/about-enterprise-configuration.md index 4cdef7c8d891..b17728f3f446 100644 --- a/translations/zh-CN/content/admin/configuration/about-enterprise-configuration.md +++ b/translations/zh-CN/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: 关于企业配置 +intro: '您可以使用站点管理员仪表板{% if enterpriseServerVersions contains currentVersion %}、{% data variables.enterprise.management_console %}和管理 shell (SSH){% elsif currentVersion == "github-ae@latest" %} 以及企业设置或联系支持{% endif %}来管理您的企业。' 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 %} 更多信息请参阅“[站点管理员仪表板](/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 %} 更多信息请参阅“[访问管理控制台](/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 %} 更多信息请参阅“[访问管理 shell (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)." +第一次访问您的企业时，您将完成初始配置以获取 +可供使用的 {% data variables.product.product_name %}。 初始配置包括连接您的企业与 idP 连接、通过 SAML SSO 进行身份验证，以及配置企业中仓库和组织的策略。 更多信息请参阅“[初始化 {% 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)." +为使用户在初始配置后收到来自 {% data variables.product.product_name %} 的任何电子邮件，您必须要求 {% data variables.contact.github_support %} 配置支持 SMTP 服务器的出站电子邮件。 更多信息请参阅“[配置电子邮件通知](/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. +稍后，您可以使用站点管理员仪表板和企业设置进一步配置企业、管理用户、组织和仓库，并设置可降低风险和提高质量的策略。 -All enterprises are configured with subdomain isolation and support for TLS 1.2 and higher for encrypted traffic only. +所有企业都配置了子域隔离，仅对加密流量支持 TLS 1.2 及更高版本。 {% endif %} ### 延伸阅读 -- "[Managing users, organizations, and repositories](/admin/user-management)" -- "[Setting policies for your enterprise](/admin/policies)" +- "[管理用户、组织和仓库](/admin/user-management)" +- "[为企业设置策略](/admin/policies)" diff --git a/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index 6e54356aa831..fe85162e3e26 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/zh-CN/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: 为企业配置数据加密 +shortTitle: 配置数据加密 +intro: '对于休息时加密，您可以提供自己的加密密钥，以在加密策略下加密数据。' versions: github-ae: '*' --- {% note %} -**Note:** Configuring encryption at rest with a customer-managed key is currently in beta and subject to change. +**注：**在休息时使用客户管理的密钥配置加密当前处于测试阶段，可能会更改。 {% endnote %} -### About data encryption +### 关于数据加密 -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. +为了提供高级别的安全性，{% data variables.product.product_name %} 在休息时对数据中心中的数据加密，以及在用户计算机与数据中心之间传输数据时对数据加密。 -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. +对于传输中的加密，{% data variables.product.product_name %} 使用传输层安全性 (TLS)。 对于休息时的加密， {% data variables.product.product_name %} 提供默认的 RSA 密钥。 在初始化企业后，您可以选择提供自己的密钥。 密钥应该是采用 PEM 格式的 2048 位 RSA 私钥。 -The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages. +您提供的钥匙存储在 {% data variables.product.company_short %} 管理的密钥保管库的硬件安全模块 (HSM) 中。 -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. +要配置加密密钥，请使用 REST API。 有许多 API 端点，例如检查加密状态、更新加密密钥以及删除加密密钥的端点。 请注意，删除密钥将冻结企业。 有关 API 端点的详细信息，请参阅 REST API 文档中的“[休息时加密](/rest/reference/enterprise-admin#encryption-at-rest)”。 -### Adding or updating an encryption key +### 添加或更新加密密钥 -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. +您可以随时随地添加新的加密密钥。 添加新密钥时，旧密钥将被丢弃。 更新密钥时，您的企业不会遇到停机。 -Your 2048 bit RSA private key should be in PEM format, for example in a file called _private-key.pem_. +您的 2048 位 RSA 私钥应采用 PEM 格式，例如在名为 _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. 要添加密钥，请使用 `PATCH /enterprise/encryption` 端点，将 *~/private-key.pem* 替换为私钥的路径。 ```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. （可选）检查更新操作的状态。 ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Deleting your encryption key +### 删除加密密钥 -To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key. +要冻结企业（例如在发生违规的情况下），可以通过删除加密密钥来禁用休息时加密。 -To unfreeze your enterprise after you've deleted your encryption key, contact support. 更多信息请参阅“[关于 {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)”。 +要在删除加密密钥后解冻企业，请联系支持人员。 更多信息请参阅“[关于 {% 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. 要删除密钥并禁用休息时加密，请使用 `DELETE /enterprise/encryption` 端点。 ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Optionally, check the status of the delete operation. +2. （可选）检查删除操作的状态。 ```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 ### 延伸阅读 -- "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation +- REST API 文档中的“[休息时加密](/rest/reference/enterprise-admin#encryption-at-rest)” diff --git a/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md b/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md index ae4c25b04dd9..a05f1d19331d 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/zh-CN/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: '为了让用户轻松地快速响应 {% data variables.product.product_name %} 上的活动，您可以企业在对议题、拉取请求和提交评论发送电子邮件通知{% if enterpriseServerVersions contains currentVersion %}，以及进行其他设置以允许入站电子邮件回复。{% endif %}' versions: enterprise-server: '*' github-ae: '*' @@ -15,16 +15,16 @@ versions: 如果用户关注的仓库或他们参与的拉取请求或问题有活动，或者用户或他们所在的团队在评论中被 @提及，系统将发送通知电子邮件。 {% 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. +您在 +{% data variables.contact.github_support %} 中的技术客户经理可以配置通过 SMTP 服务器发送电子邮件通知。 确保在支持请求中包含以下详细信息。 -- 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 +- 您的 SMTP服务器地址 +- SMTP 服务器用于发送电子邮件的端口 +- SMTP 服务器将随 HELO 响应发送的域名（如果有） +- SMTP 服务器使用的加密类型 +- 要在所有通知的 `From` 和 `To` 字段中使用的无需回复电子邮件地址 -For more information about contacting support, see "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)." +有关联系支持的更多信息，请参阅“[关于 {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)”。 {% else %} ### 配置 SMTP @@ -161,7 +161,7 @@ Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asm 如果 {% data variables.product.product_location %} 位于防火墙后或者正在通过 AWS 安全组提供，请确保端口 25 对将电子邮件发送到 `reply@reply.[hostname]` 的所有邮件服务器开放。 #### 联系支持 -If you're still unable to resolve the problem, contact +如果仍然无法解决问题，请联系 {% data variables.contact.contact_ent_support %}. 请在您的电子邮件中附上 `http(s)://[hostname]/setup/diagnostics` 的输出文件，以便帮助我们排查您的问题。 {% endif %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-pages-for-your-enterprise.md index 16ff255a24a8..825402588ede 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-pages-for-your-enterprise.md +++ b/translations/zh-CN/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: 为企业配置 GitHub Pages +intro: '您可以为企业启用或禁用 {% data variables.product.prodname_pages %}，并选择是否让站点被公开访问。' 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 %} +### 为 {% 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 %}如果您的企业启用了私有模式，则除非您启用公共站点，否则{% else %}{% endif %}公众无法访问您的企业托管的 {% data variables.product.prodname_pages %} 站点。 {% 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. +**警告**：如果为 {% data variables.product.prodname_pages %} 启用公共站点，则企业上每个仓库中的每个站点均可由公众访问。 {% 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. 在“Pages policies（页面策略）”下，选择 **Public {% data variables.product.prodname_pages %}（公共 Github）**。 ![用于启用公共 {% data variables.product.prodname_pages %} 的复选框](/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 +### 为企业禁用 {% data variables.product.prodname_pages %} {% 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. 更多信息请参阅“[启用子域隔离](/admin/configuration/enabling-subdomain-isolation)”。 +如果为企业禁用了子域隔离，则还应禁用 +{% data variables.product.prodname_pages %} 以保护自己免受潜在安全漏洞的威胁。 更多信息请参阅“[启用子域隔离](/admin/configuration/enabling-subdomain-isolation)”。 {% endif %} {% if enterpriseServerVersions contains currentVersion %} @@ -54,7 +54,7 @@ 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 %}**. ![禁用 {% data variables.product.prodname_pages %} 复选框](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) +5. 在“Pages policies（页面策略）”下，取消选择 **Enable {% data variables.product.prodname_pages %}（启用 Github）**。 ![禁用 {% data variables.product.prodname_pages %} 复选框](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) {% data reusables.enterprise-accounts.pages-policies-save %} {% endif %} diff --git a/translations/zh-CN/content/admin/configuration/initializing-github-ae.md b/translations/zh-CN/content/admin/configuration/initializing-github-ae.md index e3c02c3c23e3..65c945363fd9 100644 --- a/translations/zh-CN/content/admin/configuration/initializing-github-ae.md +++ b/translations/zh-CN/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: 初始化 GitHub AE +intro: '要让您的企业准备好使用，您可以完成 {% data variables.product.product_name %} 的初始配置。' versions: github-ae: '*' --- -### About initialization +### 关于初始化 -Before you can initialize your enterprise, you must purchase {% data variables.product.product_name %}. For more information, contact {% data variables.contact.contact_enterprise_sales %}. +在初始化企业之前，必须购买 {% data variables.product.product_name %}。 更多信息请联系 {% 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)." +在购买 {% data variables.product.product_name %} 后，我们会要求您提供想要初始化企业的个人的电子邮件地址和用户名。 您在 {% data variables.contact.enterprise_support %} 中的专用技术客户经理将为企业所有者创建一个帐户，并向企业所有者发送一封电子邮件以登录 {% data variables.product.product_name %} 并完成初始化。 确保您提供的信息与 IdP 中的预期企业所有者信息相匹配。 有关企业所有者的更多信息，请参阅“[企业中的角色](/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. +在初始化期间，企业所有者将命名企业、配置 SAML SSO、为企业中的所有组织创建策略以及为用户配置支持联系人。 ### 基本要求 {% 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 %} +**注**：在开始初始化之前，请将 {% data variables.product.prodname_ghe_managed %} 的初始用户名和密码安全地存储在密码管理器中。 {% 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. 要初始化 {% data variables.product.product_location %}，您必须具有 SAML 身份提供程序 (Idp)。 {% data reusables.saml.ae-uses-saml-sso %} 在初始化过程中将您的 IdP 连接到企业，您应该具有您的 IdP 实体 ID (SSO) URL、发行者 ID URL 和公共签名证书（Base64 编码）。 更多信息请参阅“[关于企业的身份和访问权限管理](/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 +### 登录并命名企业 -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. 按照欢迎电子邮件中的说明联系您的企业。 +2. 在“Change password（更改密码）”下键入您的凭据，然后单击 **Change password（更改密码）**。 +3. 在“What would you like your enterprise account to be named?（您要将企业帐户命名为什么？）”下，键入企业的名称，然后单击 **Save and continue（保存并继续）**。 ![用于命名企业的"Save and continue（保存并继续）"按钮](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) -### Connecting your IdP to your enterprise +### 将 IdP 连接到企业 -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)." +要配置 {% data variables.product.product_name %} 的身份验证，您必须提供包含 SAML IdP 详细信息的 {% data variables.product.product_name %}。 {% data variables.product.company_short %} 建议使用 Azure AD 作为您的 IdP。 更多信息请参阅“[使用身份提供程序配置身份验证和预配](/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. 单击 **Save（保存）**。 !["Save" button for IdP configuration](/assets/images/enterprise/configuration/ae-save.png) +1. 在“Set up your identity provider（设置身份提供程序）”右侧，单击 **Configure（配置）**。 ![用于 IdP 配置的"Configure（配置）"按钮](/assets/images/enterprise/configuration/ae-idp-configure.png) +1. 在“Sign on URL（登录 URL）”下，复制并粘贴 SAML IdP 的 URL。 ![SAML IDP 登录 URL 的文本字段](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) +1. 在“Issuer（发行机构）”下，复制并粘贴 SAML IdP 的发行机构 URL。 ![SAML IdP 发行机构 URL 的文本字段](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) +1. 在“Public certificate（公共证书）”下，复制并粘贴 SAML IdP 的公共证书。 ![SAML IdP 公共证书的文本字段](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) +1. 单击 **Test SAML configuration（测试 SAML 配置）** 以确保您输入的信息是正确的。 !["Test SAML configuration（测试 SAML 配置）"按钮](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) +1. 单击 **Save（保存）**。 ![用于 IdP 配置的"Save（保存）"按钮](/assets/images/enterprise/configuration/ae-save.png) -### Setting your enterprise policies +### 设置企业策略 -Configuring policies will set limitations for repository and organization management for your enterprise. These can be reconfigured after the initialization process. +配置策略将为企业的仓库和组织管理设置限制。 这些可以在初始化过程后重新配置。 -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. Click **Save** !["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. 在“Set your enterprise policies（设置企业策略）”右侧，单击 **Configure（配置）**。 ![用于策略配置的"Configure（配置）"按钮](/assets/images/enterprise/configuration/ae-policies-configure.png) +2. 在“Default Repository Permissions（默认仓库权限）”下，使用下拉菜单，并单击企业中仓库的默认权限级别。 如果某人可通过多种途径访问组织（个人访问、通过团队访问或作为组织成员访问），则最高的项目板权限级别将覆盖任何较低的权限级别。 （可选）要允许企业内的组织设置其默认仓库权限，请单击 **No policy（无策略）** ![默认仓库权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) +3. 在“Repository creation（仓库创建）”下，选择是否允许会员创建仓库. （可选）要允许企业内的组织设置权限，请单击 **No policy（无策略）** ![用于企业策略配置的"Members can create repositories（成员可以创建仓库）"按钮](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) +4. 在“Repository forking（仓库复刻）”下，选择是否允许私有和内部仓库复刻。 （可选）要允许企业内的组织设置权限，请单击 **No policy（无策略）** ![仓库复刻权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) +5. 在“Repository invitations（仓库邀请）”下，选择成员或组织所有者是否可以邀请合作者进入仓库。 （可选）要允许企业内的组织设置权限，请单击 **No policy（无策略）** ![仓库邀请权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) +6. 在“Default repository visibility（默认仓库可见性）”下，使用下拉菜单并单击新仓库的默认可见性设置。 ![默认仓库可见性选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) +7. 在“Users can create organizations（用户可以创建组织）”下，使用下拉菜单来启用或禁用企业成员创建组织。 ![组织创建权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) +8. 在“Force pushes（强制推送）”下，使用下拉菜单选择是允许还是阻止强制推送。 ![强制推送配置选项的下拉菜单](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) +9. 在“Git SSH access（Git SSH 访问）”下，使用下拉菜单并选择是否为企业中所有仓库启用 Git SSH 访问。 ![Git SSH 访问选项的下拉菜单](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) +10. 单击 **Save（保存）** ![用于企业策略配置的"Save（保存）"按钮](/assets/images/enterprise/configuration/ae-save.png) +11. （可选）要重置所有选项，请单击“Reset to default policies（重置为默认策略）”。 ![重置所有默认策略的链接](/assets/images/enterprise/configuration/ae-reset-default-options.png) -### Setting your internal support contact +### 设置内部支持联系人 -You can configure the method your users will use to contact your internal support team. This can be reconfigured after the initialization process. +您可以配置用户联系内部支持团队的方法。 这可以在初始化过程后重新配置。 -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. 单击 **Save（保存）**。 !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png) +1. 在“Internal support contact（内部支持联系人）”右侧，单击 **Configure（配置）**。 ![用于内部支持联系人配置的"Configure（配置）"按钮](/assets/images/enterprise/configuration/ae-support-configure.png) +2. 在“Internal support contact（内部支持联系人）”下，选择您企业的用户通过网址或电子邮件地址联系支持的方法。 然后，键入支持联系信息。 ![内部支持联系人 URL 的文本字段](/assets/images/enterprise/configuration/ae-support-link-url.png) +3. 单击 **Save（保存）**。 ![用于企业支持联系人配置的"Save（保存）"按钮](/assets/images/enterprise/configuration/ae-save.png) diff --git a/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index d20a711bd06d..8a36e1677fdf 100644 --- a/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/zh-CN/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: 限制到企业的网络流量 +shortTitle: 限制网络流量 +intro: '您可以将企业访问权限限制为来自指定 IP 地址的连接。' 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. +默认情况下，授权用户可以从任何 IP 地址访问您的企业。 您可以通过联系支持来限制对特定 IP 地址的访问，如您的办公地点。 -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)." +通过应该可以访问企业的 IP 地址联系 {% data variables.contact.github_support %}。 使用标准 CIDR（无类域间路由）格式指定地址范围。 {% data variables.contact.github_support %} 将为您的企业配置合适的防火墙规则，以限制 HTTP、SSH、HTTPS 和 SMTP 网络访问。 更多信息请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/enterprise/admin/guides/enterprise-support/receiving-help-from-github-support)”。 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 76a9f6ccda77..b8109797def6 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` 转发。 您的 `collectd` 服务器运行的 `collectd` 版本不得低于 5.x。 +如果您尚未设置外部 `collectd` 服务器，则需要首先进行设置，然后才能在 {% data variables.product.product_location %} 上启用 `collectd` 转发。 Your `collectd` server must be running `collectd` version 5.x or higher. 1. 登录 `collectd` 服务器。 2. 创建或编辑 `collectd` 配置文件，以加载网络插件并为服务器和端口指令填入适当的值。 在大多数分发中，此文件位于 `/etc/collectd/collectd.conf` 中 diff --git a/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md index 28a5d21a1dac..b953de819526 100644 --- a/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md @@ -50,7 +50,7 @@ versions: ### 联系 {% 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)." +您可以通过 {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} {% data variables.contact.ae_azure_portal %}{% endif %} 联系 {% data variables.contact.enterprise_support %}，以书面报告问题。 更多信息请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。 ### 运行时间 @@ -61,7 +61,7 @@ You can contact {% data variables.contact.enterprise_support %} through {% if en {% if enterpriseServerVersions contains currentVersion %} 对于标准的非紧急问题，我们提供每天 24 小时、每周 5 天的英语支持，不包括周末和美国国家法定节假日。 GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对软件提供标准技术支持，不收取额外费用。 标准响应时间为 24 小时。 -For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 days per week, even during national U.S. GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对软件提供标准技术支持，不收取额外费用。 +对于紧急问题，{% else %}我们{% endif %}每周 7 天、每天 24 小时提供服务，即使在美国法定节假日也不例外。 GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对软件提供标准技术支持，不收取额外费用。 {% 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 对于非紧急问题，日语支持的服务时间为周一至周五上午 9:00 至下午 5:00（日本标准时间），不包括日本的法定节假日。 对于紧急问题，我们每周 7 天、每天 24 小时提供英语支持，即使在美国法定节假日也不例外。 GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对软件提供标准技术支持，不收取额外费用。 -有关 and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."{% endif %} +有关 有关 {% data variables.contact.enterprise_support %} 遵守的美国和日本法定节假日的完整列表，请参阅“[节假日安排](#holiday-schedules)”。{% endif %} {% if enterpriseServerVersions contains currentVersion %} ### 节假日安排 -对于紧急问题，我们全天候为您提供英语帮助，包括美国 {% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %} holidays. +对于紧急问题，我们全天候为您提供英语帮助，包括美国 {% if enterpriseServerVersions contains currentVersion %}和日本{% endif %}假期。 #### 美国的节假日 -{% data variables.contact.enterprise_support %} observes these U.S. holidays. holidays{% if enterpriseServerVersions contains currentVersion %}, although our global support team is available to answer urgent tickets{% endif %}. +{% data variables.contact.enterprise_support %} observes these U.S. holidays. 节假日{% if enterpriseServerVersions contains currentVersion %} ，但我们的全球支持团队可以回答紧急事件单{% endif %}。 | 美国 美国节假日 | 观察日期 | | ----------- | ----------- | @@ -124,7 +124,7 @@ For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 {% if enterpriseServerVersions contains currentVersion %} - [关于 {% 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 %} +- 关于“[{% data variables.product.prodname_ghe_server %} 许可协议](https://enterprise.github.com/license)”中支持的第 10 节{% endif %} +- "[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)"{% if enterpriseServerVersions contains currentVersion %} +- “[准备提交事件单](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)”{% endif %} - “[提交事件单](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)” diff --git a/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md index 4f44c5deadd2..a72980b81e8b 100644 --- a/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md +++ b/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md @@ -1,6 +1,6 @@ --- title: 准备提交事件单 -intro: 'You can expedite your issue with {% data variables.contact.enterprise_support %} by following these suggestions before you open a support ticket.' +intro: '在打开支持单之前，您可以按照以下建议通过 {% data variables.contact.enterprise_support %} 加快问题的解决。' redirect_from: - /enterprise/admin/enterprise-support/preparing-to-submit-a-ticket versions: diff --git a/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md index 37708f2d374a..c86d05845b22 100644 --- a/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md @@ -85,7 +85,7 @@ $ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt #### 使用 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. +如果您可以通过 SSH 访问 {% data variables.product.product_location %} 并且拥有出站互联网访问权限，则可以使用下列步骤来创建和共享支持包。 {% 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 #### 使用 SSH 直接上传支持包 在以下情况下您可以直接将支持包上传到我们的服务器： -- 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 %}. +- 您可以通过 SSH 访问 {% data variables.product.product_location %}。 +- 允许从 {% data variables.product.product_location %} 通过 TCP 端口 443 建立出站 HTTPS 连接。 1. 将包上传到我们的支持包服务器： ```shell @@ -126,7 +126,7 @@ You can use these steps to create and share a support bundle if you have SSH acc #### 使用 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. +如果您可以通过 SSH 访问 {% data variables.product.product_location %} 并有拥有出站互联网访问权限，则可以使用下列步骤来创建和共享扩展支持包。 1. 要通过 SSH 下载扩展支持包，可将 `-x` 标记添加到 `ghe-support-bundle` 命令中： ```shell @@ -138,8 +138,8 @@ You can use these steps to create and share an extended support bundle if you ha #### 使用 SSH 直接上传扩展支持包 在以下情况下您可以直接将支持包上传到我们的服务器： -- 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 %}. +- 您可以通过 SSH 访问 {% data variables.product.product_location %}。 +- 允许从 {% data variables.product.product_location %} 通过 TCP 端口 443 建立出站 HTTPS 连接。 1. 将包上传到我们的支持包服务器： ```shell diff --git a/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md b/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md index 56d0730bb45b..60c8de42d0c2 100644 --- a/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md +++ b/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md @@ -1,6 +1,6 @@ --- title: 联系 GitHub Support -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: '使用 {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} 或{% endif %}支持门户联系 {% data variables.contact.enterprise_support %}。' redirect_from: - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support/ - /enterprise/admin/enterprise-support/reaching-github-support @@ -14,7 +14,7 @@ versions: ### 联系 {% 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 %}. 将事件单的优先级标为 {% data variables.product.support_ticket_priority_urgent %}、{% data variables.product.support_ticket_priority_high %}、{% data variables.product.support_ticket_priority_normal %} 或 {% data variables.product.support_ticket_priority_low %}。 更多信息请参阅“[为支持事件单分配优先级](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)”和“[提交事件单](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)”。 +{% data variables.contact.enterprise_support %} 客户可以使用 {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} 或 {% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} {% data variables.contact.contact_ae_portal %}{% endif %} 打开支持单。 将事件单的优先级标为 {% data variables.product.support_ticket_priority_urgent %}、{% data variables.product.support_ticket_priority_high %}、{% data variables.product.support_ticket_priority_normal %} 或 {% data variables.product.support_ticket_priority_low %}。 更多信息请参阅“[为支持事件单分配优先级](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)”和“[提交事件单](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)”。 ### 联系 {% data variables.contact.enterprise_support %} diff --git a/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support.md b/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support.md index bb400e412fdb..ef16a616f3b2 100644 --- a/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support.md +++ b/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support.md @@ -1,6 +1,6 @@ --- title: 从 GitHub Support 获得帮助 -intro: 'You can contact {% data variables.contact.enterprise_support %} to report a range of issues for your enterprise.' +intro: '您可以联系 {% data variables.contact.enterprise_support %} 报告企业的一系列问题。' 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/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md b/translations/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md index ca385851b9bd..091c2cd5e78d 100644 --- a/translations/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md +++ b/translations/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md @@ -1,6 +1,6 @@ --- title: 提交事件单 -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: '您可以使用 {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} 或{% endif %}支持门户提交支持单。' redirect_from: - /enterprise/admin/enterprise-support/submitting-a-ticket versions: @@ -13,8 +13,8 @@ versions: 在提交事件单之前，您应当收集 {% data variables.contact.github_support %} 的有用信息并选择联系人。 更多信息请参阅“[准备提交事件单](/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. 更多信息请参阅“[将数据提供给 {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)”。 +在提交支持请求和可选诊断信息后， +{% data variables.contact.github_support %} 可能要求您下载并与我们分享支持包。 更多信息请参阅“[将数据提供给 {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)”。 ### 使用 {% data variables.contact.enterprise_portal %} 提交事件单 @@ -51,13 +51,13 @@ After submitting your support request and optional diagnostic information, {% if currentVersion == "github-ae@latest" %} ### 使用 {% 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. +商业客户可以在 {% data variables.contact.contact_ae_portal %} 中提交支持请求。 政府客户应该使用[政府客户的 Azure 门户网站](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)。 更多信息请参阅 Microsoft 文档中的 "[创建 Azure 支持请求](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request)"。 -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. +对于紧急问题，为了确保快速反应，在提交支持单后，请立即呼叫支持热线。 技术支持客户经理 (TSAM) 将为您提供一个编号供在登录会话中使用。 {% endif %} ### 延伸阅读 -- "[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 %} +- "[关于 {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% if enterpriseServerVersions contains currentVersion %} +- "[关于 {% 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 %} diff --git a/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index 24154eecb6ee..542018e04634 100644 --- a/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -12,7 +12,7 @@ versions: ### 关于企业的 {% data variables.product.prodname_actions %} 权限 -在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %} 时，它会对您企业中的所有组织启用。 您可以选择对企业中的所有组织禁用 {% data variables.product.prodname_actions %}，或只允许特定的组织。 You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. +在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %} 时，它会对您企业中的所有组织启用。 您可以选择对企业中的所有组织禁用 {% data variables.product.prodname_actions %}，或只允许特定的组织。 您还可以限制公共操作的使用，以使人们只能使用您的企业中存在的本地操作。 ### 管理企业的 {% data variables.product.prodname_actions %} 权限 diff --git a/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index cce4dc0ca6c6..758369d4a529 100644 --- a/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -24,7 +24,7 @@ versions: ### 基本要求 -* 在使用 `actions-sync` 工具之前，您必须确保所有目标组织已经存在于您的企业实例中。 以下示例演示如何将操作同步到企业实例上名为 `synced-actions` 的组织。 For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +* 在使用 `actions-sync` 工具之前，您必须确保所有目标组织已经存在于您的企业实例中。 以下示例演示如何将操作同步到企业实例上名为 `synced-actions` 的组织。 更多信息请参阅“[从头开始创建新组织](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)”。 * 您必须在企业实例上创建可以创建并写入目标组织中的仓库的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 ### 示例：使用 `actions-sync` 工具 diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md index 0fd51d9ae12e..d8f150d6b8d6 100644 --- a/translations/zh-CN/content/admin/index.md +++ b/translations/zh-CN/content/admin/index.md @@ -3,7 +3,7 @@ title: 企业管理员 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: 适用于{% if enterpriseServerVersions contains currentVersion %}部署、{% endif %}配置{% if enterpriseServerVersions contains currentVersion %}、{% endif %}和管理 {% data variables.product.product_name %} 的企业管理员、系统管理员及安全专家的文档和指南。 versions: enterprise-server: '*' github-ae: '*' 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 e685e50d5713..597a20c8fe83 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 @@ -1,6 +1,6 @@ --- -title: About the GitHub Enterprise API -intro: '{% data variables.product.product_name %} supports REST and GraphQL APIs.' +title: 关于 GitHub Enterprise API +intro: '{% data variables.product.product_name %} 支持 REST 和 GraphQL API。' 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. 包含以下例子： +利用 API，您可以自动处理多种管理任务。 包含以下例子： {% if enterpriseServerVersions contains currentVersion %} - 对 {% 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)." +- 收集关于企业的统计信息。 更多信息请参阅“[管理统计](/rest/reference/enterprise-admin#admin-stats)”。 - 管理企业帐户。 更多信息请参阅“[企业帐户](/v4/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 +有关 {% 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 diff --git a/translations/zh-CN/content/admin/overview/index.md b/translations/zh-CN/content/admin/overview/index.md index 8ff942eb7413..4d29f3b3c310 100644 --- a/translations/zh-CN/content/admin/overview/index.md +++ b/translations/zh-CN/content/admin/overview/index.md @@ -1,6 +1,6 @@ --- title: 概览 -intro: 'You can learn about {% data variables.product.product_name %} and manage{% if enterpriseServerVersions contains currentVersion %} accounts and access, licenses, and{% endif %} billing.' +intro: '您可以了解{% data variables.product.product_name %}和管理{% if enterpriseServerVersions contains currentVersion %}帐户以及访问、许可和{% endif %}计费。' redirect_from: - /enterprise/admin/overview versions: diff --git a/translations/zh-CN/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/zh-CN/content/admin/overview/managing-billing-for-your-enterprise.md index 9356a7f5255f..4a45367cdf34 100644 --- a/translations/zh-CN/content/admin/overview/managing-billing-for-your-enterprise.md +++ b/translations/zh-CN/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: 管理企业的帐单 +intro: '您可以查看企业的帐单信息。' 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 %} 每天一次，{% data variables.product.prodname_dotcom %} 将计算拥有企业许可证的用户数目。 {% data variables.product.company_short %} 对每个许可的用户计费，而不论用户当天是否登录 {% data variables.product.prodname_ghe_managed %}。 -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. +对于商业区，每个用户每天的价格是 1.2580645161 美元。 在 31 天的月份中，每个用户的每月费用为 39 美元。 对于天数较少的月份，每月费用较低。 每个计费月份在日历月第一天的固定时间开始。 -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. +如果月中添加许可用户，则该用户将仅包含在其拥有许可证的天数的计数中。 当您移除授权用户时，该用户将在计数中保留到该月底。 因此，如果在一个月中添加用户然后在该月移除该用户，则用户将从添加之日到月底包含在计数中。 如果您在用户被移除的同一个月内重新添加该用户，不会有额外的费用。 -For example, here are the costs for users with licenses on different dates. +例如，以下是在不同日期具有许可证的用户的费用。 -| 用户 | 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 | +| 用户 | 许可日期 | 计入的天数 | 费用 | +| --------- | --------------------------------------------- | ----- | ------ | +| @octocat | 1 月 1 日至 1 月 31 日 | 31 | $39 | +| @robocat | 2 月 1 日至 2 月 28 日 | 29 | $35.23 | +| @devtocat | 1 月 15 日至 1 月 31 日 | 17 | $21.39 | +| @doctocat | 1 月 1 日至 1 月 15 日 | 31 | $39 | +| @prodocat | 1 月 7 日至 1 月 15 日 | 25 | $31.45 | +| @monalisa | 1 月 1 日至 1 月 7 日，
1 月 15 日至 1 月 31 日 | 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. +企业可以包括一个或多个实例。 {% data variables.product.prodname_ghe_managed %} 的每个实例至少 500 个用户。 {% data variables.product.company_short %} 按每个实例至少 500 个用户计费，即使当天拥有许可证的用户少于 500 个也一样。 -You can see your current usage in your [Azure account portal](https://portal.azure.com). +您可以在[Azure 帐户门户](https://portal.azure.com)中看到您当前的使用情况。 {% else %} @@ -40,7 +40,7 @@ You can see your current usage in your [Azure account portal](https://portal.azu 企业帐户目前适用于通过发票付费的 {% data variables.product.prodname_enterprise %} 客户。 对于所有付费 {% data variables.product.prodname_dotcom_the_website %} 服务（包括组织中的付费许可、{% data variables.large_files.product_name_long %} 数据包和 {% data variables.product.prodname_marketplace %} 应用程序订阅），连接至企业帐户的所有组织和 {% data variables.product.prodname_ghe_server %} 实例的帐单都将汇总为一个计费帐单。 -企业所有者和帐单管理员均可访问和管理企业帐户的所有帐单设置。 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)." +企业所有者和帐单管理员均可访问和管理企业帐户的所有帐单设置。 有关企业帐户的更多信息，请参阅{% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}“[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)”和{% endif %}“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)”。有关管理帐单管理员的更多信息，请参阅“[邀请人员管理企业](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)”。 ### 查看当前发票 diff --git a/translations/zh-CN/content/admin/overview/system-overview.md b/translations/zh-CN/content/admin/overview/system-overview.md index 4ec3b298ded6..34267025db20 100644 --- a/translations/zh-CN/content/admin/overview/system-overview.md +++ b/translations/zh-CN/content/admin/overview/system-overview.md @@ -77,7 +77,7 @@ versions: #### 外部服务和支持 -{% data variables.product.prodname_ghe_server %} 无需从网络访问外部服务也可以正常运行。 您可以选择集成外部服务，以提供电子邮件传送、外部监控和日志转发等功能。 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)." +{% data variables.product.prodname_ghe_server %} 无需从网络访问外部服务也可以正常运行。 您可以选择集成外部服务，以提供电子邮件传送、外部监控和日志转发等功能。 更多信息请参阅“[配置电子邮件通知](/admin/configuration/configuring-email-for-notifications)”、“[设置外部监控](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)”和“[日志转发](/admin/user-management/log-forwarding)”。 您可以手动收集故障排除数据并发送至 {% data variables.contact.github_support %}。 更多信息请参阅“[向 {% data variables.contact.github_support %} 提供数据](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)”。 @@ -108,7 +108,7 @@ versions: #### 审核和访问日志记录 -{% data variables.product.prodname_ghe_server %} 存储传统的操作系统日志和应用程序日志。 应用程序还会编写详细的审核和安全日志，永久存储在 {% data variables.product.prodname_ghe_server %} 上。 您可以通过 `syslog-ng` 协议将两种类型的日志实时转发到多个目标。 For more information, see "[Log forwarding](/admin/user-management/log-forwarding)." +{% data variables.product.prodname_ghe_server %} 存储传统的操作系统日志和应用程序日志。 应用程序还会编写详细的审核和安全日志，永久存储在 {% data variables.product.prodname_ghe_server %} 上。 您可以通过 `syslog-ng` 协议将两种类型的日志实时转发到多个目标。 更多信息请参阅“[日志转发](/admin/user-management/log-forwarding)。” 访问和审核日志包括如下信息。 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 b91210f90ad3..381702d2bacb 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 %} 界面中实现。 You can use MinIO for storage by following the instructions for AWS S3, entering the analogous information for your MinIO configuration. +目前，{% 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_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 @@ -21,7 +21,10 @@ versions: {% warning %} -**警告**：确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。 +**警告：** +- 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 %} 后，我们不建议更改存储系统。 {% endwarning %} diff --git a/translations/zh-CN/content/admin/packages/index.md b/translations/zh-CN/content/admin/packages/index.md index 8e36ad1cf8a1..30331937754b 100644 --- a/translations/zh-CN/content/admin/packages/index.md +++ b/translations/zh-CN/content/admin/packages/index.md @@ -1,6 +1,5 @@ --- title: 管理企业的 GitHub Packages -shortTitle: GitHub Packages intro: '您可以为企业启用 {% data variables.product.prodname_registry %}，并管理 {% data variables.product.prodname_registry %} 设置和允许的包类型。' redirect_from: - /enterprise/admin/packages 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 073735be7868..f92a91da7225 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 @@ -30,11 +30,11 @@ versions: github-ae: '*' --- -### Configuring the default visibility of new repositories in your enterprise +### 配置企业中新仓库的默认可见性 -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. 有关仓库可见性的更多信息，请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)。” +每次有人在您的企业上创建新仓库时，此人必须选择仓库的可见性。 当您配置企业的默认可见性设置时，需要选择默认可见性。 有关仓库可见性的更多信息，请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)。” -如果站点管理员不允许成员创建某种类型的仓库，成员将无法创建此类仓库，即使可见性设置默认为此类型。 For more information, see "[Setting a policy for repository creation](#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" %} @@ -43,7 +43,7 @@ Each time someone creates a new repository on your enterprise, that person must {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %} -1. 在“默认仓库可见性”下，使用下拉菜单并选择默认可见性。 ![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) +1. 在“默认仓库可见性”下，使用下拉菜单并选择默认可见性。 ![用于选择企业的默认仓库可见性的下拉菜单](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) {% data reusables.enterprise_installation.image-urls-viewable-warning %} @@ -51,7 +51,7 @@ Each time someone creates a new repository on your enterprise, that person must 当您阻止成员更改仓库可见性时，只有站点管理员可以将公共仓库设置为私有或者将私有仓库设置为公共。 -如果站点管理员仅允许组织所有者创建仓库，成员将无法更改仓库可见性。 如果站点管理员只允许成员创建私有仓库，则成员只能将仓库从公共更改为私有。 For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)." +如果站点管理员仅允许组织所有者创建仓库，成员将无法更改仓库可见性。 如果站点管理员只允许成员创建私有仓库，则成员只能将仓库从公共更改为私有。 更多信息请参阅“[设置仓库创建策略](#setting-a-policy-for-repository-creation)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -86,7 +86,7 @@ Each time someone creates a new repository on your enterprise, that person must ### 设置 Git 推送限制策略 -To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise. +要使仓库大小保持可管理并防止发生性能问题，可以为企业中的仓库配置文件大小限制。 默认情况下，强制执行仓库上传限制时，无法添加或上传超过 100 MB 的文件。 @@ -106,7 +106,7 @@ To keep your repository size manageable and prevent performance issues, you can {% endif %} {% data reusables.enterprise-accounts.options-tab %} 4. 在“Repository upload limit”下，使用下拉菜单，然后单击最大对象大小。 ![包含最大对象大小选项的下拉菜单](/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** ![对所有仓库选项强制执行最大对象限制](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) +5. （可选）要对企业中的所有仓库实施最大上传限制，请选择 **Enforce on all repositories（对所有仓库强制执行）** ![对所有仓库选项强制执行最大对象限制](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) ### 为仓库之间的拉取请求配置合并冲突编辑器 @@ -123,7 +123,7 @@ To keep your repository size manageable and prevent performance issues, you can ### 配置强制推送 -每个仓库都从其所属的用户帐户或组织的设置继承了默认强制推送设置。 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. +每个仓库都从其所属的用户帐户或组织的设置继承了默认强制推送设置。 同样，每个组织和用户帐户都会从企业的强制推送设置继承默认强制推送设置。 如果更改企业的强制推送设置，则会更改任何用户或组织拥有的所有仓库。 #### 阻止设备上的所有强制推送 @@ -151,7 +151,7 @@ To keep your repository size manageable and prevent performance issues, you can #### 阻止对用户帐户或组织拥有的仓库进行强制推送 -仓库从它们所属的用户帐户或组织继承强制推送设置。 User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise. +仓库从它们所属的用户帐户或组织继承强制推送设置。 反过来，用户帐户和组织从企业的强制推送设置继承其强制推送设置。 您可以通过配置用户帐户或组织的设置来覆盖默认的继承设置。 @@ -164,17 +164,17 @@ To keep your repository size manageable and prevent performance issues, you can 5. 在“Force pushes”部分的“Repository default settings”下，选择 - **Block** 来阻止对所有分支进行强制推送。 - **Block to the default branch** 来仅阻止对默认分支进行强制推送。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png) -6. 可以视情况选择 **Enforce on all repositories** 来覆盖仓库特定的设置。 Note that this will **not** override an enterprise-wide policy. ![阻止强制推送](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) +6. 可以视情况选择 **Enforce on all repositories** 来覆盖仓库特定的设置。 注意，这**不**会覆盖企业范围的策略。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) ### 配置匿名 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 %}如果您已经在企业上[启用私密模式](/enterprise/admin/configuration/enabling-private-mode)，{% else %}您{% endif %}可以允许仓库管理员启用对公共仓库的匿名 Git 读取访问。 -Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. 当您或仓库管理员为仓库启用此权限设置时，未经过身份验证的 Git 操作（和具有 {% data variables.product.product_name %} 的网络访问权限的任何人）将获得仓库的读取权限（无需身份验证）。 +启用匿名 Git 读取允许用户在企业上为自定义工具绕过身份验证。 当您或仓库管理员为仓库启用此权限设置时，未经过身份验证的 Git 操作（和具有 {% data variables.product.product_name %} 的网络访问权限的任何人）将获得仓库的读取权限（无需身份验证）。 -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. 在您锁定仓库的 Git 读取权限设置后，只有站点管理员可以更改设置。 +如有必要，您可以通过锁定仓库的访问设置，阻止仓库管理员更改企业上仓库的匿名 Git 访问设置。 在您锁定仓库的 Git 读取权限设置后，只有站点管理员可以更改设置。 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %} @@ -190,7 +190,7 @@ If necessary, you can prevent repository administrators from changing anonymous {% endif %} {% data reusables.enterprise-accounts.options-tab %} 4. 在“Anonymous Git read access”下，使用下列菜单并单击 **Enabled**。 ![匿名 Git 读取权限下拉菜单显示菜单选项"Enabled（已启用）"和"Disabled（已禁用）"](/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. 或者，如果要阻止仓库管理员为企业上的所有仓库更改匿名 Git 读取权限设置，请选择 **Prevent repository admins from changing anonymous Git read access**。 ![选中复选框可阻止仓库管理员更改企业上所有仓库的匿名 Git 读取权限设置。](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png) {% if enterpriseServerVersions contains currentVersion %} #### 设置特定仓库的匿名 Git 读取访问 diff --git a/translations/zh-CN/content/admin/user-management/activity-dashboard.md b/translations/zh-CN/content/admin/user-management/activity-dashboard.md index d3ac8cb35728..79d4055c5bac 100644 --- a/translations/zh-CN/content/admin/user-management/activity-dashboard.md +++ b/translations/zh-CN/content/admin/user-management/activity-dashboard.md @@ -1,6 +1,6 @@ --- title: 活动仪表板 -intro: 'The Activity dashboard gives you an overview of all the activity in your enterprise.' +intro: '活动仪表板提供企业中所有活动的概览。' redirect_from: - /enterprise/admin/articles/activity-dashboard/ - /enterprise/admin/installation/activity-dashboard @@ -24,8 +24,8 @@ versions: ![活动仪表板](/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 %}. 更多信息请参阅“[关于 {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/about-github-insights)”。 +有关基于 +{% data variables.product.product_name %} 中数据的更多分析，您可以购买 {% data variables.product.prodname_insights %}。 更多信息请参阅“[关于 {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/about-github-insights)”。 {% endif %} ### 访问活动仪表板 diff --git a/translations/zh-CN/content/admin/user-management/audit-logging.md b/translations/zh-CN/content/admin/user-management/audit-logging.md index 165a73a8ec57..6c69560ecf82 100644 --- a/translations/zh-CN/content/admin/user-management/audit-logging.md +++ b/translations/zh-CN/content/admin/user-management/audit-logging.md @@ -1,6 +1,6 @@ --- title: 审核日志 -intro: '{% data variables.product.product_name %} keeps logs of audited{% if enterpriseServerVersions contains currentVersion %} system,{% endif %} user, organization, and repository events. 日志可用于调试以及内部和外部合规。' +intro: '{% data variables.product.product_name %} 会保留已审计 {% if enterpriseServerVersions contains currentVersion %} 系统、{% endif %}用户、组织和仓库事件的日志。 日志可用于调试以及内部和外部合规。' 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)." +有关完整列表，请参阅“[审核的操作](/admin/user-management/audited-actions)”。 有关查找特定操作的详细信息，请参阅“[搜索审核日志](/admin/user-management/searching-the-audit-log)”。 ### 推送日志 -会记录每个 Git 推送操作。 For more information, see "[Viewing push logs](/admin/user-management/viewing-push-logs)." +会记录每个 Git 推送操作。 更多信息请参阅“[查看推送日志](/admin/user-management/viewing-push-logs)”。 {% if enterpriseServerVersions contains currentVersion %} ### 系统事件 所有经过审核的系统事件（包括所有推送和拉取）都会记录到 `/var/log/github/audit.log` 中。 日志每 24 小时自动轮换一次，并会保留七天。 -支持包中包含系统日志。 For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/admin/enterprise-support/providing-data-to-github-support)." +支持包中包含系统日志。 更多信息请参阅“[向 {% data variables.product.prodname_dotcom %} Support 提供数据](/admin/enterprise-support/providing-data-to-github-support)”。 ### 支持包 -所有审核信息均会记录到任何支持包 `github-logs` 目录的 `audit.log` 文件中。 如果已启用日志转发，您可以将此数据传输到外部 syslog 流使用者，例如 [Splunk](http://www.splunk.com/) 或 [Logstash](http://logstash.net/)。 此日志中的所有条目均使用 `github_audit` 关键词，并且可以通过该关键词进行筛选。 For more information see "[Log forwarding](/admin/user-management/log-forwarding)." +所有审核信息均会记录到任何支持包 `github-logs` 目录的 `audit.log` 文件中。 如果已启用日志转发，您可以将此数据传输到外部 syslog 流使用者，例如 [Splunk](http://www.splunk.com/) 或 [Logstash](http://logstash.net/)。 此日志中的所有条目均使用 `github_audit` 关键词，并且可以通过该关键词进行筛选。 更多信息请参阅“[日志转发](/admin/user-management/log-forwarding)。” 例如，此条目显示已创建的新仓库。 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 bac542b54b4b..79f99394740b 100644 --- a/translations/zh-CN/content/admin/user-management/audited-actions.md +++ b/translations/zh-CN/content/admin/user-management/audited-actions.md @@ -12,18 +12,18 @@ versions: #### 身份验证 -| 名称 | 描述 | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------- | -| `oauth_access.create` | 已为用户帐户[生成>][generate token] [OAuth 访问令牌][]。 | -| `oauth_access.destroy` | 已从用户帐户中删除 [OAuth 访问令牌][]。 | -| `oauth_application.destroy` | 已从用户或组织帐户中删除 [OAuth 应用程序][]。 | -| `oauth_application.reset_secret` | 已重置 [OAuth 应用程序][]的密钥。 | -| `oauth_application.transfer` | 已将 [OAuth 应用程序][]从一个用户或组织帐户传送到另一个用户或组织帐户。 | -| `public_key.create` | 已将 SSH 密钥[添加][add key]到用户帐户中，或者已将[部署密钥][]添加到仓库中。 | -| `public_key.delete` | 已从用户帐户中移除 SSH 密钥，或已从仓库中移除[部署密钥][]。 | -| `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` | 已为用户帐户启用[双重身份验证][2fa]。 | -| `two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.{% endif %} +| 名称 | 描述 | +| ------------------------------------:| ------------------------------------------------------------------------------------- | +| `oauth_access.create` | 已为用户帐户[生成>][generate token] [OAuth 访问令牌][]。 | +| `oauth_access.destroy` | 已从用户帐户中删除 [OAuth 访问令牌][]。 | +| `oauth_application.destroy` | 已从用户或组织帐户中删除 [OAuth 应用程序][]。 | +| `oauth_application.reset_secret` | 已重置 [OAuth 应用程序][]的密钥。 | +| `oauth_application.transfer` | 已将 [OAuth 应用程序][]从一个用户或组织帐户传送到另一个用户或组织帐户。 | +| `public_key.create` | 已将 SSH 密钥[添加][add key]到用户帐户中，或者已将[部署密钥][]添加到仓库中。 | +| `public_key.delete` | 已从用户帐户中移除 SSH 密钥，或已从仓库中移除[部署密钥][]。 | +| `public_key.update` | 已更新用户帐户的 SSH 密钥或仓库的[部署密钥][]。{% if enterpriseServerVersions contains currentVersion %} +| `two_factor_authentication.enabled` | 已为用户帐户启用[双重身份验证][2fa]。 | +| `two_factor_authentication.disabled` | 已为用户帐户禁用[双重身份验证][2fa]。{% endif %} #### 挂钩 @@ -34,53 +34,53 @@ versions: | `hook.destroy` | 已删除挂钩。 | | `hook.events_changed` | 已更改挂钩的配置事件。 | -#### Enterprise configuration settings +#### 企业配置设置 -| 名称 | 描述 | -| -------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `business.update_member_repository_creation_permission` | A site admin restricts repository creation in organizations in the enterprise. 更多信息请参阅“[在企业中实施仓库管理策略](/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. 更多信息请参阅“[在企业中实施仓库管理策略](/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. 更多信息请参阅“[在企业中实施仓库管理策略](/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. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。 | +| 名称 | 描述 | +| -------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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)”。 | +| `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)”。 | #### 议题和拉取请求 -| 名称 | 描述 | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------- | -| `issue.update` | 问题的正文文本（初始注释）已更改。 | -| `issue_comment.update` | 已更改问题的正文文本（初始注释）。 | -| `pull_request_review_comment.delete` | 已删除对拉取请求的评论。 | -| `issue.destroy` | 已从仓库中删除问题。 For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)." | +| 名称 | 描述 | +| ------------------------------------:| ----------------------------------------------------------------------------------- | +| `issue.update` | 问题的正文文本（初始注释）已更改。 | +| `issue_comment.update` | 已更改问题的正文文本（初始注释）。 | +| `pull_request_review_comment.delete` | 已删除对拉取请求的评论。 | +| `issue.destroy` | 已从仓库中删除问题。 更多信息请参阅“[删除议题](/github/managing-your-work-on-github/deleting-an-issue)”。 | #### 组织 -| 名称 | 描述 | -| ------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org.async_delete` | 用户发起了删除组织的后台作业。 | -| `org.delete` | An organization was deleted by a user-initiated background job.{% if currentVersion != "github-ae@latest" %} -| `org.transform` | 已将用户帐户转换为组织。 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 %} +| 名称 | 描述 | +| ------------------:| -------------------------------------------------------------------------------------------------------------------------------------------- | +| `org.async_delete` | 用户发起了删除组织的后台作业。 | +| `org.delete` | 用户发起的背景作业删除了组织。{% if currentVersion != "github-ae@latest" %} +| `org.transform` | 已将用户帐户转换为组织。 更多信息请参阅“[将用户转换为组织](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)”{% endif %} #### 受保护分支 -| 名称 | 描述 | -| ------------------------------------------------------------------:| ----------------------------------------------------------------- | -| `protected_branch.create` | 已在分支上启用分支保护。 | -| `protected_branch.destroy` | 已在分支上禁用分支保护。 | -| `protected_branch.update_admin_enforced` | 已为仓库管理员强制执行分支保护。 | -| `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review is updated on a branch. | -| `protected_branch.dismiss_stale_reviews` | 已在分支上更新忽略旧拉取请求的强制执行。 | -| `protected_branch.update_signature_requirement_enforcement_level` | 已在分支上更新必需提交签名的强制执行。 | -| `protected_branch.update_pull_request_reviews_enforcement_level` | 已在分支上更新必需拉取请求审查的强制执行。 | -| `protected_branch.update_required_status_checks_enforcement_level` | 已在分支上更新必需状态检查的强制执行。 | -| `protected_branch.rejected_ref_update` | 分支更新尝试被拒。 | -| `protected_branch.policy_override` | 分支保护要求被仓库管理员覆盖。 | +| 名称 | 描述 | +| ------------------------------------------------------------------:| ---------------------- | +| `protected_branch.create` | 已在分支上启用分支保护。 | +| `protected_branch.destroy` | 已在分支上禁用分支保护。 | +| `protected_branch.update_admin_enforced` | 已为仓库管理员强制执行分支保护。 | +| `protected_branch.update_require_code_owner_review` | 已在分支上更新必需代码所有者审查的强制执行。 | +| `protected_branch.dismiss_stale_reviews` | 已在分支上更新忽略旧拉取请求的强制执行。 | +| `protected_branch.update_signature_requirement_enforcement_level` | 已在分支上更新必需提交签名的强制执行。 | +| `protected_branch.update_pull_request_reviews_enforcement_level` | 已在分支上更新必需拉取请求审查的强制执行。 | +| `protected_branch.update_required_status_checks_enforcement_level` | 已在分支上更新必需状态检查的强制执行。 | +| `protected_branch.rejected_ref_update` | 分支更新尝试被拒。 | +| `protected_branch.policy_override` | 分支保护要求被仓库管理员覆盖。 | #### 仓库 | 名称 | 描述 | | ------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `repo.access` | 已将私有仓库设为公共，或者已将公共仓库设为私有。 | -| `repo.archive` | 已存档仓库。 For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)." | +| `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` | 已创建仓库。 | @@ -89,7 +89,7 @@ versions: | `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)." | +| `repo.unarchive` | 已取消存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。 | | `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)”。 | @@ -115,30 +115,28 @@ versions: #### 用户 -| 名称 | 描述 | -| ---------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | 已向用户帐户添加电子邮件地址。 | -| `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` | 已创建新的用户帐户。 | -| `user.delete` | 已通过异步作业销毁用户帐户。 | -| `user.demote` | 已将站点管理员降级为普通用户帐户。 | -| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.failed_login` | 用户尝试登录时使用的用户名、密码或双重身份验证码不正确。 | -| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} -| `user.login` | 用户已登录。 | -| `user.promote` | 已将普通用户帐户升级为站点管理员。 | -| `user.remove_email` | 已从用户帐户中移除电子邮件地址。 | -| `user.rename` | 已更改用户名。 | -| `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` | 站点管理员已取消挂起用户帐户。 | +| 名称 | 描述 | +| ---------------------------:| ------------------------------------------------------------------------------------------ | +| `user.add_email` | 已向用户帐户添加电子邮件地址。 | +| `user.async_delete` | 异步作业已开始破坏用户帐户，最终触发 `user.delete`。{% if enterpriseServerVersions contains currentVersion %} +| `user.change_password` | 用户已更改其密码。{% endif %} +| `user.create` | 已创建新的用户帐户。 | +| `user.delete` | 已通过异步作业销毁用户帐户。 | +| `user.demote` | 已将站点管理员降级为普通用户帐户。 | +| `user.destroy` | 用户已删除其帐户，触发 `user.async_delete`。{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | 用户尝试登录时使用的用户名、密码或双重身份验证码不正确。 | +| `user.forgot_password` | 用户通过登录页面请求了密码重置。{% endif %} +| `user.login` | 用户已登录。 | +| `user.promote` | 已将普通用户帐户升级为站点管理员。 | +| `user.remove_email` | 已从用户帐户中移除电子邮件地址。 | +| `user.rename` | 已更改用户名。 | +| `user.suspend` | 用户帐户被站点管理员暂停。{% if enterpriseServerVersions contains currentVersion %} +| `user.two_factor_requested` | 已提示用户输入双重身份验证码。{% endif %} +| `user.unsuspend` | 站点管理员已取消挂起用户帐户。 | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [部署密钥]: /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 应用程序]: /guides/basics-of-authentication/#registering-your-app [2fa]: /articles/about-two-factor-authentication - [2fa]: /articles/about-two-factor-authentication diff --git a/translations/zh-CN/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/zh-CN/content/admin/user-management/auditing-users-across-your-enterprise.md index b12126903509..da0c13696ab8 100644 --- a/translations/zh-CN/content/admin/user-management/auditing-users-across-your-enterprise.md +++ b/translations/zh-CN/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: 审核整个企业的用户 +intro: '审核日志仪表板向站点管理员显示过去 90 天内企业中所有用户和组织执行的操作，包括操作执行者、操作内容以及操作执行时间等详细信息。' 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: ### 访问审核日志 -The audit log dashboard gives you a visual display of audit data across your enterprise. +审核日志仪表板让您能够直观地看到企业中的审计数据。 ![实例级审核日志仪表板](/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 在地图中，您可以平移和缩放来查看世界范围内的事件。 将鼠标悬停在国家/地区上，可以看到该国家/地区内事件的快速盘点。 -### Searching for events across your enterprise +### 在企业中搜索事件 -The audit log lists the following information about actions made within your enterprise: +审核日志列出了有关企业内所执行操作的以下信息： * 操作发生的[仓库](#search-based-on-the-repository) * 执行操作的[用户](#search-based-on-the-user) @@ -37,7 +37,7 @@ The audit log lists the following information about actions made within your ent **注意：** -- 您无法使用文本搜索审核条目，但您可以使用多个筛选器构建搜索查询。 {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。 +- 您无法使用文本搜索审核条目，但您可以使用多个筛选器构建搜索查询。 {% data variables.product.product_name %} 支持在 {% data variables.product.product_name %} 中使用多种运算符进行搜索。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。 - 要搜索 90 天之前的事件，请使用 `created` 限定符。 {% endwarning %} @@ -66,13 +66,13 @@ The audit log lists the following information about actions made within your ent `org` 限定符可将操作限定为特定组织。 例如： -* `org:my-org` finds all events that occurred for the `my-org` organization. +* `org:my-org` 会找到 `my-org` 组织发生的所有事件。 * `org:my-org action:team` 会找到在 `my-org` 组织中执行的所有团队事件。 -* `-org:my-org` excludes all events that occurred for the `my-org` organization. +* `-org:my-org` 会排除 `my-org` 组织发生的所有事件。 #### 基于执行的操作搜索 -`action` 限定符可搜索特定事件（按类别组织）。 For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)". +`action` 限定符可搜索特定事件（按类别组织）。 有关与这些类别相关的事件的信息，请参阅“[审核的操作](/admin/user-management/audited-actions)”。 | 类别名称 | 描述 | | ------ | -------------------- | diff --git a/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md b/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md index 520848e3494f..453b600ec86a 100644 --- a/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md +++ b/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md @@ -1,6 +1,6 @@ --- title: 用户安全的最佳实践 -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 %}除了站点管理员可以实现的实例级别安全措施（SSL、子域隔离、配置防火墙）外，{% else %}{% endif %}您的用户还可以按照一些步骤操作来帮助保护。' redirect_from: - /enterprise/admin/user-management/best-practices-for-user-security versions: @@ -18,7 +18,7 @@ versions: ### 需要密码管理器 -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. 这样可以确保密码更强，大大降低被入侵或被盗的可能性。 +我们强烈建议要求您的用户在他们用于连接到企业的任何计算机上安装和使用密码管理器，例如 [LastPass](https://lastpass.com/)、[1Password](https://1password.com/) 或 [Keeper](https://keepersecurity.com/)。 这样可以确保密码更强，大大降低被入侵或被盗的可能性。 ### 限制对团队和仓库的访问 diff --git a/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md index 4390ab7c7587..ce53da42a7e7 100644 --- a/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md @@ -19,7 +19,7 @@ versions: ### 关于 {% 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 %} 您可以将 {% data variables.large_files.product_name_long %} 与单一仓库、所有个人或组织仓库或企业中的每一个仓库结合使用。 您需要先为企业启用 {% data variables.large_files.product_name_short %}，然后才能为特定仓库或组织启用 {% data variables.large_files.product_name_short %}。 {% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} @@ -28,7 +28,7 @@ versions: {% data reusables.large_files.can-include-lfs-objects-archives %} -### Configuring {% data variables.large_files.product_name_long %} for your enterprise +### 为企业配置 {% data variables.large_files.product_name_long %} {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} @@ -65,7 +65,7 @@ versions: {% 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. 在 {% data variables.product.product_location %} 上禁用 {% data variables.large_files.product_name_short %}。 更多信息请参阅“[为企业配置 {% data variables.large_files.product_name_long %}](#configuring-git-large-file-storage-for-your-enterprise)”。 2. 创建指向第三方服务器的 {% data variables.large_files.product_name_short %} 配置文件。 ```shell @@ -99,7 +99,7 @@ versions: ### 迁移到其他 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)." +迁移到其他 {% data variables.large_files.product_name_long %} 服务器之前，您必须将 {% data variables.large_files.product_name_short %} 配置为使用第三方服务器。 解更多信息请参阅“[配置 {% data variables.large_files.product_name_long %} 使用第三方服务器](#configuring-git-large-file-storage-to-use-a-third-party-server)”。 1. 使用第二个远端配置仓库。 ```shell diff --git a/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md index afee3ad5dc10..115944d977dd 100644 --- a/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md +++ b/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md @@ -1,6 +1,6 @@ --- title: 配置组织成员关系的可见性 -intro: You can set visibility for new organization members across your enterprise to public or private. 您还可以阻止成员将其可见性改为非默认值。 +intro: 您可以将企业中新组织成员的可见性设置为公开或私密。 您还可以阻止成员将其可见性改为非默认值。 redirect_from: - /enterprise/admin/user-management/configuring-visibility-for-organization-membership versions: @@ -21,4 +21,4 @@ versions: {% data reusables.enterprise-accounts.options-tab %} 3. 在“Default organization membership visibility（默认组织成员可见性）”下，使用下拉菜单，然后单击 **Private（私密）**或 **Public（公开）**。 ![包含用于将默认组织成员关系可见性配置为公开或私密的选项的下拉菜单](/assets/images/enterprise/site-admin-settings/default-organization-membership-visibility-drop-down-menu.png) 4. 或者，为了阻止成员将他们的成员关系可见性改为非默认值，也可以选择 **Enforce on organization members**。 ![Checkbox to enforce the default setting on all members](/assets/images/enterprise/site-admin-settings/enforce-default-org-membership-visibility-setting.png){% if enterpriseServerVersions contains currentVersion %} -5. 如果您想在所有现有成员中强制使用新的可见性设置，请使用 `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. 如果您想在所有现有成员中强制使用新的可见性设置，请使用 `ghe-org-membership-update` 命令行实用程序。 更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)”。{% endif %} diff --git a/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index 84991409c23b..47be845fbd49 100644 --- a/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -1,10 +1,10 @@ --- -title: Customizing user messages for your enterprise +title: 自定义企业的用户消息 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: '您可以创建用户将在{% if enterpriseServerVersions contains currentVersion %} 登录和注销页面{% else %} 注销页面{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} 或每个页面顶部的公告横幅中{% endif %} 看到的自定义消息。' versions: enterprise-server: '*' github-ae: '*' @@ -51,7 +51,7 @@ versions: {% 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)." +您也可以{% if enterpriseServerVersions contains currentVersion %} 使用命令行实用工具或{% endif %} 使用 API 在管理 shell 中设置公告横幅。 更多信息请参阅 {% if enterpriseServerVersions contains currentVersion %}“[命令行实用工具](/enterprise/admin/configuration/command-line-utilities#ghe-announce)”和 {% endif %}“[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)”。 {% else %} diff --git a/translations/zh-CN/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/zh-CN/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md index e73ff4c34921..48ade184f05e 100644 --- a/translations/zh-CN/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md +++ b/translations/zh-CN/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: 在企业上禁用 Git SSH 访问 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: '您可以阻止用户为企业上的某些仓库或所有仓库使用 Git over SSH。' versions: enterprise-server: '*' github-ae: '*' @@ -41,7 +41,7 @@ versions: {% data reusables.enterprise_site_admin_settings.admin-tab %} 7. 在“Git SSH access”下，使用下拉菜单，然后单击 **Disabled**。 然后选择 **Enforce on all repositories**。 ![选择了禁用选项的 Git SSH access 下拉菜单](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png) -### Disabling Git SSH access to all repositories in your enterprise +### 禁止对企业中的所有仓库进行 Git SSH 访问 {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} diff --git a/translations/zh-CN/content/admin/user-management/index.md b/translations/zh-CN/content/admin/user-management/index.md index 7679aa6f61a2..76a491288450 100644 --- a/translations/zh-CN/content/admin/user-management/index.md +++ b/translations/zh-CN/content/admin/user-management/index.md @@ -1,7 +1,7 @@ --- title: '管理用户、组织和仓库' shortTitle: '管理用户、组织和仓库' -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: '本指南介绍了可让用户登录您的企业的身份验证方法、如何创建组织和团队以进行仓库访问和协作，并针对用户安全提供了最佳实践建议。' redirect_from: - /enterprise/admin/categories/user-management/ - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration diff --git a/translations/zh-CN/content/admin/user-management/log-forwarding.md b/translations/zh-CN/content/admin/user-management/log-forwarding.md index d1f3223e53a5..c499e8c1f24d 100644 --- a/translations/zh-CN/content/admin/user-management/log-forwarding.md +++ b/translations/zh-CN/content/admin/user-management/log-forwarding.md @@ -1,6 +1,6 @@ --- title: 日志转发 -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 %} 使用 `syslog-ng` 将 {% if enterpriseServerVersions contains currentVersion %}系统{% elsif currentVersion == "github-ae@latest" %}Git{% endif %} 和应用程序日志转发到您指定的服务器。' redirect_from: - /enterprise/admin/articles/log-forwarding/ - /enterprise/admin/installation/log-forwarding @@ -25,18 +25,18 @@ versions: {% 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. 单击 **Save（保存）**。 ![Save button for log forwarding](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) +1. 在 {% octicon "gear" aria-label="The Settings gear" %} **Settings（设置）**下，单击 **Log forwarding（日志转发）**。 ![日志转发选项卡](/assets/images/enterprise/business-accounts/log-forwarding-tab.png) +1. 在“Log forwarding（日志转发）”下，选择 **Enable log forwarding（启用日志转发）**。 ![启用日志转发的复选框](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png) +1. 在“Server address（服务器地址）”下，输入您想要日志转发到的服务器地址。 ![服务器地址字段](/assets/images/enterprise/business-accounts/server-address-field.png) +1. 使用“Protocol（协议）”下拉菜单选择一个协议。 ![协议下拉菜单](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png) +1. （可选）要在系统日志端点之间的训用 TLS 加密通信，请选择 **Enable TLS（启用 TLS）**。 ![启用 TLS 的复选框](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png) +1. 在“Public certificate（公共证书）”下，粘贴您的 x509 证书。 ![公共证书文本框](/assets/images/enterprise/business-accounts/public-certificate-text-box.png) +1. 单击 **Save（保存）**。 ![用于日志转发的 Save（保存）按钮](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) {% endif %} {% if enterpriseServerVersions contains currentVersion %} ### 疑难解答 -If you run into issues with log forwarding, contact +如果遇到日志转发问题，请联系 -{% 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 %} 并在您的电子邮件中附上 `http(s)://[hostname]/setup/diagnostics` 的输出文件。 {% endif %} diff --git a/translations/zh-CN/content/admin/user-management/managing-dormant-users.md b/translations/zh-CN/content/admin/user-management/managing-dormant-users.md index a07b9b947093..0b0f20ec0d8e 100644 --- a/translations/zh-CN/content/admin/user-management/managing-dormant-users.md +++ b/translations/zh-CN/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: 如果用户帐户至少在一个月内未激活，则被视为休眠状态。{% if enterpriseServerVersions contains currentVersion %} 您可以选择暂停休眠用户以释放用户许可。{% endif %} versions: enterprise-server: '*' github-ae: '*' @@ -15,7 +15,7 @@ versions: - 登录 {% data variables.product.product_name %}。 - 评论问题和拉取请求。 - 创建、删除、关注仓库和加星标。 -- Pushing commits.{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- 推送提交。{% if currentversion ver_gt "enterprise-server@2.21" or currentversion == "github-ae@latest" %} - 使用个人访问令牌或 SSH 密钥访问资源。{% endif %} ### 查看休眠用户 diff --git a/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md b/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md index 6b62a7856e44..7bf0205456b0 100644 --- a/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md +++ b/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md @@ -1,6 +1,6 @@ --- title: 管理全局 web 挂钩 -intro: 'Site administrators can view, add, edit, and delete global webhooks to track events for the enterprise.' +intro: '站点管理员可以查看、添加、编辑和删除全局 web 挂钩，以跟踪企业的事件。' redirect_from: - /enterprise/admin/user-management/about-global-webhooks - /enterprise/admin/user-management/managing-global-webhooks @@ -11,7 +11,7 @@ versions: ### 关于全局 web 挂钩 -You can use global webhooks to automatically monitor, respond to, or enforce rules for user and organization management for your enterprise. 例如，您可以将 web 挂钩配置为在以下情况下执行： +您可以使用全局 web 挂钩自动监视、响应或者为企业的用户和组织管理强制执行规则。 例如，您可以将 web 挂钩配置为在以下情况下执行： - 创建或删除用户帐户 - 创建或删除组织 - 向仓库添加协作者或从仓库中移除协作者 diff --git a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise.md index c1ae1ba7a1db..a496491d45a3 100644 --- a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: 管理企业中的仓库 -intro: 'You can manage the settings available to repository administrators in your enterprise.' +intro: '您可以管理企业中仓库管理员可用的设置。' redirect_from: - /enterprise/admin/user-management/repositories - /enterprise/admin/user-management/managing-repositories-in-your-enterprise diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise.md index 3c37df887bed..4ea7a21a0594 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: 管理企业中的用户 -intro: 'You can audit user activity and manage user settings.' +intro: '您可以审核用户活动并管理用户设置。' redirect_from: - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ - /enterprise/admin/user-management/basic-account-settings diff --git a/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md index 499609660ef8..e8b0bcaaa58d 100644 --- a/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md +++ b/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md @@ -1,6 +1,6 @@ --- title: 合法保留用户或组织 -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: '您可以合法保留用户或组织，以便确保他们拥有的仓库不会从企业中永久移除。' redirect_from: - /enterprise/admin/user-management/placing-a-legal-hold-on-a-user-or-organization versions: diff --git a/translations/zh-CN/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/zh-CN/content/admin/user-management/preventing-users-from-creating-organizations.md index 029d77d1d3ec..01cd803f51ca 100644 --- a/translations/zh-CN/content/admin/user-management/preventing-users-from-creating-organizations.md +++ b/translations/zh-CN/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: '您可以防止用户在您的企业中创建组织。' versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/zh-CN/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/zh-CN/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md index a63e219da750..24ea4651893d 100644 --- a/translations/zh-CN/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md +++ b/translations/zh-CN/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 %}. 组织管理员可以要求成员启用双重身份验证。 +使用 LDAP 或内置身份验证时，{% data variables.product.product_location %} 将支持双重身份验证。 组织管理员可以要求成员启用双重身份验证。 {% data reusables.enterprise_user_management.external_auth_disables_2fa %} diff --git a/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md b/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md index 5765732f377b..47fd58021069 100644 --- a/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md +++ b/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md @@ -1,6 +1,6 @@ --- title: 搜索审核日志 -intro: 'Site administrators can search an extensive list of audited actions on the enterprise.' +intro: '站点管理员可以在企业上搜索已审核操作的广泛列表。' redirect_from: - /enterprise/admin/articles/searching-the-audit-log/ - /enterprise/admin/installation/searching-the-audit-log @@ -14,28 +14,28 @@ versions: 由一个或多个键值对（以 AND/OR 逻辑运算符分隔）构成一个搜索查询。 -| 键 | 值 | -| --------------:| -------------------------- | -| `actor_id` | 发起操作的用户帐户的 ID | -| `actor` | 发起操作的用户帐户的名称 | -| `oauth_app_id` | 与操作相关联的 OAuth 应用程序的 ID | -| `action` | Name of the audited action | -| `user_id` | 受操作影响的用户的 ID | -| `用户` | 受操作影响的用户的名称 | -| `repo_id` | 受操作影响的仓库的 ID（若适用） | -| `repo` | 受操作影响的仓库的名称（若适用） | -| `actor_ip` | 发起操作的 IP 地址 | -| `created_at` | 操作发生的时间 | -| `from` | 发起操作的视图 | -| `note` | 事件特定的其他信息（采用纯文本或 JSON 格式） | -| `org` | 受操作影响的组织的名称（若适用） | -| `org_id` | 受操作影响的组织的 ID（若适用） | +| 键 | 值 | +| --------------:| ------------------------- | +| `actor_id` | 发起操作的用户帐户的 ID | +| `actor` | 发起操作的用户帐户的名称 | +| `oauth_app_id` | 与操作相关联的 OAuth 应用程序的 ID | +| `action` | 已审核操作的名称 | +| `user_id` | 受操作影响的用户的 ID | +| `用户` | 受操作影响的用户的名称 | +| `repo_id` | 受操作影响的仓库的 ID（若适用） | +| `repo` | 受操作影响的仓库的名称（若适用） | +| `actor_ip` | 发起操作的 IP 地址 | +| `created_at` | 操作发生的时间 | +| `from` | 发起操作的视图 | +| `note` | 事件特定的其他信息（采用纯文本或 JSON 格式） | +| `org` | 受操作影响的组织的名称（若适用） | +| `org_id` | 受操作影响的组织的 ID（若适用） | 例如，要查看自 2017 年初开始影响仓库 `octocat/Spoon-Knife` 的所有操作： `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)." +有关操作的完整列表，请参阅“[审核的操作](/admin/user-management/audited-actions)”。 ### 搜索审核日志 diff --git a/translations/zh-CN/content/admin/user-management/viewing-push-logs.md b/translations/zh-CN/content/admin/user-management/viewing-push-logs.md index a5fa190b3807..ea8f61c04a5b 100644 --- a/translations/zh-CN/content/admin/user-management/viewing-push-logs.md +++ b/translations/zh-CN/content/admin/user-management/viewing-push-logs.md @@ -1,6 +1,6 @@ --- title: 查看推送日志 -intro: 'Site administrators can view a list of Git push operations for any repository on the enterprise.' +intro: '站点管理员可以查看企业上任何仓库的 Git 推送操作列表。' redirect_from: - /enterprise/admin/articles/viewing-push-logs/ - /enterprise/admin/installation/viewing-push-logs diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md index d39ec7603241..756a72c2fdd2 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -36,17 +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. 其余更改会保持不动，以便您进行其他修改和提交。 这允许您进行单独、有意义的提交，例如使提交中的换行符更改区别于代码或文字更改。 -在审查文件的差异时，包含在提交中的行将以蓝色高亮显示。 要排除更改，请单击更改的行让蓝色消失。 +{% note %} + +**Note:** Split diff displays are currently in beta and subject to change. + +{% endnote %} -![文件中取消选择的行](/assets/images/help/desktop/partial-commit.png) +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) -#### 放弃更改 +### 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. -{% mac %} +#### Discarding changes in one or more files {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -54,30 +60,25 @@ versions: {% data reusables.desktop.confirm-discard-files %} ![确认对话框中的放弃更改按钮](/assets/images/help/desktop/discard-changes-confirm-mac.png) -{% tip %} +#### Discarding changes in one or more lines +You can discard one or more changed lines that are uncommitted. -**提示：**您放弃的更改保存在垃圾桶的日期文件中，在垃圾桶清空之前可以恢复。 - -{% endtip %} +{% note %} -{% endmac %} +**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. -{% windows %} +{% endnote %} -{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %} - ![上下文菜单中的 Discard Changes（放弃更改）选项](/assets/images/help/desktop/discard-changes-win.png) -{% data reusables.desktop.confirm-discard-files %} - ![确认对话框中的放弃更改按钮](/assets/images/help/desktop/discard-changes-confirm-win.png) +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**. -{% tip %} + ![Discard single line in the confirmation dialog](/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**. -{% endtip %} + ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) -{% endwindows %} -### 3. 编写提交消息并推送更改 +### 4. 编写提交消息并推送更改 对选择要包含在提交中的更改感到满意后，编写提交消息并推送更改。 如果协作处理了某个提交，也可以将提交归于多个作者。 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 e25d374ee18c..31607e2e14bb 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 @@ -34,8 +34,6 @@ Different server-to-server request rate limits apply to {% data variables.produc ### User-to-server requests -{% data reusables.apps.deprecating_password_auth %} - {% 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. {% if currentVersion == "free-pro-team@latest" %} @@ -52,7 +50,7 @@ User-to-server requests are rate limited at 5,000 requests per hour and per auth #### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits -When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. +When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. {% endif %} diff --git a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md index d163986b7413..750d6a3f0581 100644 --- a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md +++ b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md @@ -82,6 +82,32 @@ See [our guide on Git automation with tokens][git-automation]. 7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. 8. Click **Add key**. +##### Using multiple repositories on one server + +If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. + +In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. 例如： + +```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 %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias. +* `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias. +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias. + +You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. 例如： + +```bash +$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git +``` + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/zh-CN/content/developers/overview/secret-scanning.md b/translations/zh-CN/content/developers/overview/secret-scanning.md index 7fc4c8800cb7..3b4eeaec1ce8 100644 --- a/translations/zh-CN/content/developers/overview/secret-scanning.md +++ b/translations/zh-CN/content/developers/overview/secret-scanning.md @@ -79,7 +79,7 @@ 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. +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. * **Token**: The value of the secret match. * **Type**: The unique name you provided to identify your regular expression. diff --git a/translations/zh-CN/content/github/administering-a-repository/about-branch-restrictions.md b/translations/zh-CN/content/github/administering-a-repository/about-branch-restrictions.md index cec3dc94ed79..0a00bdb53303 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-branch-restrictions.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-branch-restrictions.md @@ -1,6 +1,6 @@ --- title: 关于分支限制 -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: '属于组织的仓库中的分支可配置为仅特定用户、团队或应用程序可推送到分支。' product: '{% data reusables.gated-features.branch-restrictions %}' redirect_from: - /articles/about-branch-restrictions diff --git a/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index 8ee201eb3059..cc15409f9f9e 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -25,7 +25,7 @@ versions: - 作为提交一部分所更改的文件 - 提交消息 -您可以过滤因推送到仓库而收到的电子邮件通知。 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)." 您还可以对推送关闭电子邮件通知。 更多信息请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}”。 +您可以过滤因推送到仓库而收到的电子邮件通知。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}”[关于通知电子邮件](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”。 您还可以对推送关闭电子邮件通知。 更多信息请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}”。 ### 对推送到仓库启用电子邮件通知 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 d1270ff0ab62..48a5e64b8563 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 @@ -21,7 +21,7 @@ versions: 发行版基于 [Git 标记](https://git-scm.com/book/en/Git-Basics-Tagging)，这些标记会标记仓库历史记录中的特定点。 标记日期可能与发行日期不同，因为它们可在不同的时间创建。 有关查看现有标记的更多信息，请参阅“[查看仓库的发行版和标记](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)”。 -当仓库中发布新发行版时您可以接收通知，但不会接受有关仓库其他更新的通知。 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 %}." +当仓库中发布新发行版时您可以接收通知，但不会接受有关仓库其他更新的通知。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}”[关注和取消关注仓库的发行版](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}”。 对仓库具有读取访问权限的任何人都可以查看和比较发行版，但只有对仓库具有写入权限的人员才能管理发行版。 更多信息请参阅“[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)”。 @@ -32,7 +32,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} 如果发行版修复了安全漏洞，您应该在仓库中发布安全通告。 -{% 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. 更多信息请参阅“[关于 GitHub 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 +{% data variables.product.prodname_dotcom %} 审查每个发布的安全通告，并且可能使用它向受影响的仓库发送 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 GitHub 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 您可以查看依赖项图的 **Dependents（依赖项）**选项卡，了解哪些仓库和包依赖于您仓库中的代码，并因此可能受到新发行版的影响。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 {% endif %} diff --git a/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md b/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md index 62a348d61049..091d87fdc51e 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md @@ -1,6 +1,7 @@ --- title: 关于密码扫描 intro: '{% data variables.product.product_name %} 扫描仓库查找已知的密码类型，以防止欺诈性使用意外提交的密码。' +product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /github/administering-a-repository/about-token-scanning - /articles/about-token-scanning diff --git a/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md index 3d1df7c88d4f..6f8776974a1b 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md @@ -21,7 +21,7 @@ versions: 私下讨论并修复仓库代码中的安全漏洞。 然后，您可以发布安全通告，提醒您的社区注意漏洞并鼓励他们升级。 更多信息请参阅“[关于 {% 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 %} 和安全更新** 查看有关已知包含安全漏洞的依赖项的警报，并选择是否自动生成拉取请求以更新这些依赖项。 更多信息请参阅“[关于漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”和“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 @@ -43,6 +43,6 @@ versions: * 您的仓库依赖的生态系统和包 * 依赖于您的仓库的仓库和包 -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. +必须先启用依赖项图，然后 {% data variables.product.prodname_dotcom %} 才能针对有安全漏洞的依赖项生成 {% data variables.product.prodname_dependabot_alerts %}。 您可以在仓库的 **Insights（洞察）**选项卡上找到依赖项图。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index 4561a090e2a3..3766bf752fc9 100644 --- a/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -12,7 +12,7 @@ versions: {% data variables.product.prodname_dependabot %} 配置文件 *dependabot.yml* 使用 YAML 语法。 如果您是 YAML 的新用户并想要了解更多信息，请参阅“[五分钟了解 YAML](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)”。 -必须将此文件存储在仓库的 `.github` 目录中。 添加或更新 *dependabot.yml* 文件时，这将触发对版本更新的立即检查。 Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”和“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)”。 +必须将此文件存储在仓库的 `.github` 目录中。 添加或更新 *dependabot.yml* 文件时，这将触发对版本更新的立即检查。 下次安全警报触发安全更新的拉取请求时将使用所有同时影响安全更新的选项。 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”和“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)”。 ### *dependabot.yml* 的配置选项 diff --git a/translations/zh-CN/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md b/translations/zh-CN/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md index be3125901a04..49f6950805b6 100644 --- a/translations/zh-CN/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md +++ b/translations/zh-CN/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. +任何对仓库具有管理员权限的人都可以配置自动链接引用，以将议题、拉取请求、{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} 提交消息和发行版说明{% else %} 和提交消息{% endif %} 链接到外部第三方服务。 如果您使用 Zendesk 跟踪用户报告的事件单，例如，您可以引用所打开拉取请求中的事件单号来解决问题。 diff --git a/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md b/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md index ef2828811fb6..1e68e8d5bdc1 100644 --- a/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md +++ b/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md @@ -1,6 +1,7 @@ --- title: 配置私有仓库的密码扫描 intro: '您可以配置 {% data variables.product.product_name %} 如何扫描您私有仓库中的密码。' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: '对私有仓库具有管理员权限的人员可为 {% data variables.product.prodname_secret_scanning %} 启用仓库。' versions: free-pro-team: '*' diff --git a/translations/zh-CN/content/github/administering-a-repository/customizing-dependency-updates.md b/translations/zh-CN/content/github/administering-a-repository/customizing-dependency-updates.md index fc40179174d9..15868b889635 100644 --- a/translations/zh-CN/content/github/administering-a-repository/customizing-dependency-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/customizing-dependency-updates.md @@ -20,7 +20,7 @@ versions: 有关配置选项的详细信息，请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates)”。 -更新仓库中的 *dependabot.yml* 文件时，{% data variables.product.prodname_dependabot %} 使用新配置即刻进行检查。 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. 您可能还会看到针对版本更新的新拉取请求。 更多信息请参阅“[列出为版本更新配置的依赖项](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)”。 +更新仓库中的 *dependabot.yml* 文件时，{% data variables.product.prodname_dependabot %} 使用新配置即刻进行检查。 几分钟内，您将在 **{% data variables.product.prodname_dependabot %}** 选项卡上看到更新的依赖项列表，如果仓库有很多依赖项，可能需要更长时间。 您可能还会看到针对版本更新的新拉取请求。 更多信息请参阅“[列出为版本更新配置的依赖项](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)”。 ### 配置更改对安全更新的影响 diff --git a/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index 44f5279e7a54..cef180df2e02 100644 --- a/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -23,7 +23,7 @@ versions: {% note %} -**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 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 %} +**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 更多信息请参阅“[禁用或限制组织的 {% 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_actions %} 策略](/github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account)”。{% else if currentVersion ver_gt "enterprise-server@2.21"%}"[实施企业的 {% data variables.product.prodname_actions %} 策略](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)“。{% endif %} {% endnote %} @@ -44,7 +44,7 @@ versions: {% note %} -**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 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)." +**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 更多信息请参阅“[禁用或限制组织的 {% 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_actions %} 策略](/github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account)”。{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[实施企业的 {% data variables.product.prodname_actions %} 策略](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)“。 {% endif %} @@ -63,7 +63,7 @@ versions: {% 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. ![添加操作到允许列表](/assets/images/help/repository/actions-policy-allow-list.png) +1. 在 **Actions permissions（操作权限）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 ![添加操作到允许列表](/assets/images/help/repository/actions-policy-allow-list.png) 2. 单击 **Save（保存）**。 {% endif %} diff --git a/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index 94b7f5a110c8..7a66ca0747f2 100644 --- a/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -10,7 +10,7 @@ versions: ### 关于依赖项的版本更新 -通过将 *dependabot.yml* 配置文件检入仓库的 `.github` 目录，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. 对于您想更新的每个包管理器的依赖项，必须指定包清单文件的位置及为文件所列的依赖项检查更新的频率。 For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +通过将 *dependabot.yml* 配置文件检入仓库的 `.github` 目录，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 {% data variables.product.prodname_dependabot %} 然后提出拉取请求，使您配置的依赖项保持最新。 对于您想更新的每个包管理器的依赖项，必须指定包清单文件的位置及为文件所列的依赖项检查更新的频率。 有关启用安全更新的信息，请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)。” {% data reusables.dependabot.initial-updates %} 更多信息请参阅“[自定义依赖项更新](/github/administering-a-repository/customizing-dependency-updates)。” @@ -72,7 +72,7 @@ updates: ### 检查版本更新的状态 -启用版本更新后，将在仓库的依赖关系图中发现新的 **Dependabot** 选项卡。 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. +启用版本更新后，将在仓库的依赖关系图中发现新的 **Dependabot** 选项卡。 此选项卡显示配置了哪些要监视的包管理器 {% data variables.product.prodname_dependabot %} 以及 {% data variables.product.prodname_dependabot %} 上次检查新版本的时间。 ![仓库洞察选项卡，依赖关系图，Dependabot 选项卡](/assets/images/help/dependabot/dependabot-tab-view-beta.png) diff --git a/translations/zh-CN/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md index b55c7a1f48d7..3b2b97f9f4b1 100644 --- a/translations/zh-CN/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md @@ -10,7 +10,7 @@ versions: 在以下情况下，仓库管理员可以更改特定仓库的匿名 Git 读取权限设置： - 站点管理员已启用私有模式和匿名 Git 读取权限。 -- The repository is public on the enterprise and is not a fork. +- 仓库在企业上是公共的，并且不是复刻。 - 站点管理员尚未禁用仓库的匿名 Git 读取权限。 {% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %} diff --git a/translations/zh-CN/content/github/administering-a-repository/enabling-branch-restrictions.md b/translations/zh-CN/content/github/administering-a-repository/enabling-branch-restrictions.md index 1aaaa50bd544..a9466b159c5e 100644 --- a/translations/zh-CN/content/github/administering-a-repository/enabling-branch-restrictions.md +++ b/translations/zh-CN/content/github/administering-a-repository/enabling-branch-restrictions.md @@ -1,6 +1,6 @@ --- title: 启用分支限制 -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: '您可以强制实施分支限制，以便只有某些用户、团队或应用程序可以推送到组织拥有的仓库中的受保护分支。' product: '{% data reusables.gated-features.branch-restrictions %}' redirect_from: - /articles/enabling-branch-restrictions diff --git a/translations/zh-CN/content/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch.md b/translations/zh-CN/content/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch.md index 0bac7a84e714..433c857a3245 100644 --- a/translations/zh-CN/content/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch.md +++ b/translations/zh-CN/content/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch.md @@ -16,7 +16,7 @@ versions: 启用强制推送不会覆盖任何其他分支保护规则。 例如，如果分支需要线性提交历史记录，则无法强制推送合并提交到该分支。 -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. 更多信息请参阅“[阻止强制推送到用户帐户或组织拥有的仓库](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)”。 +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}如果站点管理员阻止强制推送到仓库中的所有分支，您不能启用强制推送到受保护分支。 更多信息请参阅“[阻止强制推送到用户帐户或组织拥有的仓库](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)”。 如果站点管理员只阻止强制推送到默认分支，您仍然可以为任何其他受保护分支启用强制推送。{% endif %} diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/zh-CN/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index bb98b6ca6345..5b376eac0858 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -1,6 +1,7 @@ --- title: 管理来自密码扫描的警报 intro: 您可以查看并关闭已检入仓库的密码的警报。 +product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' --- diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md index d9e16f2d7aa2..355af0816406 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -14,8 +14,8 @@ versions: {% data variables.product.product_name %} 以 ZIP 文件和 tarball 的形式创建仓库的源代码存档。 用户可以在您仓库的主页上下载这些存档或者将其作为发行版资产。 默认情况下，{% data variables.large_files.product_name_short %} 对象不会包含在这些存档中，只有这些对象的指针文件包含在其中。 为了提高仓库存档的可用性，您可以选择包含 {% 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. 每个帐户每月免费获得 {% data variables.large_files.initial_bandwidth_quota %} 的带宽，您可以付费获得额外用量。 更多信息请参阅“[关于存储和带宽使用](/github/managing-large-files/about-storage-and-bandwidth-usage)”和“[管理 {% data variables.large_files.product_name_long %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage)”。 +如果您选择在仓库存档中包含 +{% data variables.large_files.product_name_short %} 对象，则每次下载这些存档都会计入您帐户的带宽使用量。 每个帐户每月免费获得 {% data variables.large_files.initial_bandwidth_quota %} 的带宽，您可以付费获得额外用量。 更多信息请参阅“[关于存储和带宽使用](/github/managing-large-files/about-storage-and-bandwidth-usage)”和“[管理 {% 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 %} ### 管理存档中的 {% data variables.large_files.product_name_short %} 对象 diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index 8f35ca754044..2eb7ac76469b 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -1,6 +1,6 @@ --- title: 管理仓库的复刻政策 -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: '您可以允许或阻止对组织拥有的特定私有{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或内部{% endif %} 仓库进行复刻。' 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. 更多信息请参阅“[管理组织的复刻政策](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)”。 +组织所有者必须在组织级别上允许复刻私有{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 和内部{% endif %} 仓库，然后才能允许或禁止对特定仓库进行复刻。 更多信息请参阅“[管理组织的复刻政策](/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/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md index da3948ddda1f..0948548fd032 100644 --- a/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md @@ -20,11 +20,11 @@ versions: #### 将仓库设为私有 - * {% data variables.product.prodname_dotcom %} 将会分离公共仓库的公共复刻并将其放入新的网络中。 公共复刻无法设为私有。 {% 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)" + * {% data variables.product.prodname_dotcom %} 将会分离公共仓库的公共复刻并将其放入新的网络中。 公共复刻无法设为私有。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}如果将仓库的可见性从内部更改为私有，{% data variables.product.prodname_dotcom %} 将删除属于无法访问新私有仓库的任何用户的复刻。{% endif %}更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/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" %}* 如果对用户帐户或组织使用 {% data variables.product.prodname_free_user %}，有些功能在您将可见性更改为私有后不可用于仓库。 {% data reusables.gated-features.more-info %} * 任何已发布的 {% data variables.product.prodname_pages %} 站点都将自动取消发布。 如果您将自定义域添加到 {% data variables.product.prodname_pages %} 站点，应在将仓库设为私有之前删除或更新 DNS 记录，以避免域接管的风险。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。 * {% data variables.product.prodname_dotcom %} 不再在 {% data variables.product.prodname_archive %} 中包含该仓库。 更多信息请参阅“[关于在 {% 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. 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。{% endif %} + {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}* 匿名 Git 读取权限不再可用。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。{% endif %} #### 将仓库设为公共 diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md index 58e574ac238c..8d50c74612ee 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md @@ -9,17 +9,17 @@ versions: ### 关于 {% 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 %}. 向 {% data variables.product.product_name %} 验证时，您提供或确认您唯一的凭据，以证明您就是声明者。 +为确保帐户安全，必须先进行身份验证，然后才能访问 {% data variables.product.product_name %} 上的{% if currentVersion != "github-ae@latest" %}某些{% endif %}资源。 向 {% data variables.product.product_name %} 验证时，您提供或确认您唯一的凭据，以证明您就是声明者。 您可以通过多种方式访问 {% data variables.product.product_name %} 中的资源：浏览器中、通过 {% data variables.product.prodname_desktop %} 或其他桌面应用程序、使用 API 或通过命令行。 每种访问 {% data variables.product.product_name %} 的方式都支持不同的身份验证模式。 -- {% if currentVersion == "github-ae@latest" %}Your identity provider (IdP){% else %}Username and password with two-factor authentication{% endif %} +- {% if currentversion == "github-ae@latest" %}您的身份提供程序 (IdP){% else %}使用双重身份验证的用户名和密码{% endif %} - 个人访问令牌 - SSH 密钥 ### 在浏览器中进行身份验证 -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. +您可以 {% if currentVersion == "github-ae@latest" %}使用 IdP 在浏览器中向 {% data variables.product.product_name %} 验证。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”{% else %}。 - **仅用户名和密码** - 在 {% data variables.product.product_name %} 上创建用户帐户时，您将创建一个密码。 我们建议您使用密码管理器生成随机且唯一的密码。 更多信息请参阅“[创建强式密码](/github/authenticating-to-github/creating-a-strong-password)”。 @@ -34,7 +34,7 @@ You can authenticate to {% data variables.product.product_name %} in your browse ### 使用 API 验证身份 -You can authenticate with the API in different ways. +您可以通过不同方式使用 API 进行身份验证。 - **个人访问令牌** - 在有限的情况（如测试）下可以使用个人访问令牌访问 API。 使用个人访问令牌可让您随时撤销访问。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index fb53fc9de9bb..fd16a10fdedc 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,5 +1,5 @@ --- -title: 关于使用 SAML 单点登录进行身份验证 +title: About authentication with SAML single sign-on 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 %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: @@ -15,33 +15,33 @@ SAML SSO allows an enterprise owner to centrally control and secure access to {% {% 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. +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. {% endif %} {% if currentVersion == "free-pro-team@latest" %} -{% data reusables.saml.dotcom-saml-explanation %} 组织所有者可以邀请您在 {% data variables.product.prodname_dotcom %} 上的用户帐户加入其使用 SAML SSO 的组织，这样您可以对该组织做出贡献，并且保留您在 {% data variables.product.prodname_dotcom %} 上的现有身份和贡献。 +{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. -在访问使用 SAML SSO 的组织中的资源时，{% data variables.product.prodname_dotcom %} 会将您重定向到组织的 SAML IdP 进行身份验证。 在 IdP 上成功验证您的帐户后，IdP 会将您重定向回到 {% data variables.product.prodname_dotcom %}，您可以在那里访问组织的资源。 +When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} -如果您最近在浏览器中使用组织的 SAML IdP 进行过身份验证，则在访问使用 SAML SSO 的 {% data variables.product.prodname_dotcom %} 组织时会自动获得授权。 如果您最近没有在浏览器中使用组织的 SAML IdP 进行身份验证，则必须在 SAML IdP 进行身份验证后才可访问组织。 +If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. {% data reusables.saml.you-must-periodically-authenticate %} -要在命令行上使用 API 或 Git 访问使用 SAML SSO 的组织中受保护的内容，需要使用授权的 HTTPS 个人访问令牌或授权的 SSH 密钥。 默认授权 {% data variables.product.prodname_oauth_app %} 访问令牌。 +To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. {% data variables.product.prodname_oauth_app %} access tokens are authorized by default. -如果没有个人访问令牌或 SSH 密钥，可以创建用于命令行的个人访问令牌或生成新的 SSH 密钥。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”或“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 +If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -要对实施 SAML SSO 的组织使用新的或现有的个人访问令牌或 SSH 密钥，需要授权该令牌或授权 SSH 密钥用于 SAML SSO 组织。 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”或“[授权 SSH 密钥用于 SAML 单点登录](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。 +To use a new or existing personal access token or SSH key with an organization that enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[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)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -每次授权 {% data variables.product.prodname_oauth_app %} 时必须有活动的 SAML 会话。 +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %}. {% endif %} -### 延伸阅读 +### Further reading {% 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 %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md index aa03736a293a..8c4705f29fae 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -1,6 +1,6 @@ --- title: 关于提交签名验证 -intro: 'Using GPG or S/MIME, you can sign tags and commits locally. 这些标记或提交在 {% data variables.product.product_name %} 上标示为已验证，便于其他人信任更改来自可信的来源。' +intro: '使用 GPG 或 S/MIME，您可以在本地对标记和提交进行签名。 这些标记或提交在 {% data variables.product.product_name %} 上标示为已验证，便于其他人信任更改来自可信的来源。' redirect_from: - /articles/about-gpg-commit-and-tag-signatures/ - /articles/about-gpg/ diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md b/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md index 532fa18c4071..ab12730191f7 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md @@ -1,6 +1,6 @@ --- title: 关于 SSH -intro: '使用 SSH 协议可以连接远程服务器和服务并向它们验证。 With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.' +intro: '使用 SSH 协议可以连接远程服务器和服务并向它们验证。 利用 SSH 密钥可以连接 {% data variables.product.product_name %}，而无需在每次访问时都提供用户名和个人访问令牌。' redirect_from: - /articles/about-ssh versions: diff --git a/translations/zh-CN/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md b/translations/zh-CN/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md index e96c898150e9..50d4f29d4bec 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: 使用 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: '您可以使用 SAML 单点登录 (SSO)向 {% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} 组织验证 {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %}{% if currentVersion == "free-pro-team@latest" %}并查看您活动的会话{% endif %}。' mapTopic: true product: '{% data reusables.gated-features.saml-sso %}' redirect_from: diff --git a/translations/zh-CN/content/github/authenticating-to-github/connecting-with-third-party-applications.md b/translations/zh-CN/content/github/authenticating-to-github/connecting-with-third-party-applications.md index eee156562cca..a6d0f4b3f1c5 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/connecting-with-third-party-applications.md +++ b/translations/zh-CN/content/github/authenticating-to-github/connecting-with-third-party-applications.md @@ -52,17 +52,17 @@ versions: {% endtip %} -| 数据类型 | 描述 | -| ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 提交状态 | 您可以授权第三方应用程序报告您的提交状态。 提交状态访问权限允许应用程序确定对特定提交的构建是否成功。 应用程序无法访问您的代码，但能够读取和写入特定提交的状态信息。 | -| 部署 | 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. | -| Gist | [Gist](https://gist.github.com) 访问权限允许应用程序读取或写入公共和机密 Gist。 | -| 挂钩 | [Web 挂钩](/webhooks)访问权限允许应用程序读取或写入您管理的仓库中的挂钩配置。 | -| 通知 | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. 但应用程序仍然无法访问仓库中的任何内容。 | -| 组织和团队 | 组织和团队访问权限允许应用程序访问并管理组织和团队成员资格。 | -| 个人用户数据 | 用户数据包括您的用户个人资料中的信息，例如您的姓名、电子邮件地址和地点。 | -| 仓库 | 仓库信息包括贡献者的姓名、您创建的分支以及仓库中的实际文件。 应用程序可以申请访问用户级别的公共或私有仓库。 | -| 仓库删除 | 应用程序可以申请删除您管理的仓库，但无法访问您的代码。 | +| 数据类型 | 描述 | +| ------ | ---------------------------------------------------------------------------------------------------------- | +| 提交状态 | 您可以授权第三方应用程序报告您的提交状态。 提交状态访问权限允许应用程序确定对特定提交的构建是否成功。 应用程序无法访问您的代码，但能够读取和写入特定提交的状态信息。 | +| 部署 | 部署状态访问权限允许应用程序根据公共和私有仓库的特定提交确定部署是否成功。 应用程序无法访问您的代码。 | +| Gist | [Gist](https://gist.github.com) 访问权限允许应用程序读取或写入公共和机密 Gist。 | +| 挂钩 | [Web 挂钩](/webhooks)访问权限允许应用程序读取或写入您管理的仓库中的挂钩配置。 | +| 通知 | 通知访问权限允许应用程序读取您的 {% data variables.product.product_name %} 通知，如议题和拉取请求的评论。 但应用程序仍然无法访问仓库中的任何内容。 | +| 组织和团队 | 组织和团队访问权限允许应用程序访问并管理组织和团队成员资格。 | +| 个人用户数据 | 用户数据包括您的用户个人资料中的信息，例如您的姓名、电子邮件地址和地点。 | +| 仓库 | 仓库信息包括贡献者的姓名、您创建的分支以及仓库中的实际文件。 应用程序可以申请访问用户级别的公共或私有仓库。 | +| 仓库删除 | 应用程序可以申请删除您管理的仓库，但无法访问您的代码。 | ### 申请更新的权限 diff --git a/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index ad102847921e..279fb5db448c 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -24,7 +24,7 @@ versions: ``` {% note %} - **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use: + **注：**如果您使用的是不支持 Ed25519 算法的旧系统，请使用以下命令： ```shell $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` @@ -89,7 +89,7 @@ versions: $ 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. + * 打开 `~/.ssh/config` 文件，然后修改该文件，如果未使用 `id_ed25519` 键的默认位置和名称，则替换 `~/.ssh/id_ed25519`。 ``` Host * diff --git a/translations/zh-CN/content/github/authenticating-to-github/index.md b/translations/zh-CN/content/github/authenticating-to-github/index.md index 730700954db8..6cceee5010f0 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/index.md +++ b/translations/zh-CN/content/github/authenticating-to-github/index.md @@ -1,7 +1,7 @@ --- title: 向 GitHub 验证 shortTitle: 身份验证 -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: '通过{% if currentVersion != "github-ae@latest" %}双重身份验证、{% endif %}SSH{% if currentVersion != "github-ae@latest" %}、{% endif %}和提交签名验证等功能保持帐户和数据的安全。' redirect_from: - /categories/56/articles/ - /categories/ssh/ diff --git a/translations/zh-CN/content/github/authenticating-to-github/managing-commit-signature-verification.md b/translations/zh-CN/content/github/authenticating-to-github/managing-commit-signature-verification.md index a5ddca47099c..f0713fed1185 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/managing-commit-signature-verification.md +++ b/translations/zh-CN/content/github/authenticating-to-github/managing-commit-signature-verification.md @@ -1,6 +1,6 @@ --- title: 管理提交签名验证 -intro: 'You can sign your work locally using GPG or S/MIME. {% data variables.product.product_name %} 将会验证这些签名，以便其他人知道提交来自可信的来源。{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} 将自动使用 {% data variables.product.product_name %} web 界面{% endif %}对您的提交签名。' +intro: '您可以使用 GPG 或 S/MIME 在本地对工作进行签名。 {% data variables.product.product_name %} 将会验证这些签名，以便其他人知道提交来自可信的来源。{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} 将自动使用 {% data variables.product.product_name %} web 界面{% endif %}对您的提交签名。' redirect_from: - /articles/generating-a-gpg-key/ - /articles/signing-commits-with-gpg/ diff --git a/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md index 1c5949f77aed..e178adaafdbe 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -32,22 +32,22 @@ versions: ### 了解安全日志中的事件 安全日志中列出的操作分为以下类别： |{% endif %} -| 类别名称 | 描述 | -| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} -| `account_recovery_token` | 包含与[添加恢复令牌](/articles/configuring-two-factor-authentication-recovery-methods)相关的所有活动。 | -| `计费，帐单` | 包含与帐单信息相关的所有活动。 | -| `marketplace_agreement_signature` | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的所有活动。 | +| 类别名称 | 描述 | +| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} +| `account_recovery_token` | 包含与[添加恢复令牌](/articles/configuring-two-factor-authentication-recovery-methods)相关的所有活动。 | +| `计费，帐单` | 包含与帐单信息相关的所有活动。 | +| `marketplace_agreement_signature` | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的所有活动。 | | `marketplace_listing` | 包含与 {% data variables.product.prodname_marketplace %} 中列出的应用程序相关的所有活动。{% endif %} | `oauth_access` | 包含与您已连接的 [{% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps) 相关的所有活动。{% if currentVersion == "free-pro-team@latest" %} | `payment_method` | 包含与 {% data variables.product.prodname_dotcom %} 订阅支付相关的所有活动。{% endif %} -| `profile_picture` | 包含与头像相关的所有活动。 | -| `project` | 包含与项目板相关的所有活动。 | -| `public_key` | 包含与[公共 SSH 密钥](/articles/adding-a-new-ssh-key-to-your-github-account)相关的所有活动。 | +| `profile_picture` | 包含与头像相关的所有活动。 | +| `project` | 包含与项目板相关的所有活动。 | +| `public_key` | 包含与[公共 SSH 密钥](/articles/adding-a-new-ssh-key-to-your-github-account)相关的所有活动。 | | `repo` | 包含与您拥有的仓库相关的所有活动。{% 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" %} -| `团队` | 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 %} -| `用户` | 包含与您的帐户相关的所有活动。 | +| `sponsors` | 包含与 {% data variables.product.prodname_sponsors %}和赞助者按钮相关的所有事件（请参阅“[关于 {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)”和“[在仓库中显示赞助者按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| `团队` | 包含与您所在团队相关的所有活动。{% endif %}{% if currentVersion != "github-ae@latest" %} +| `two_factor_authentication` | 包含与[双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)相关的所有活动。{% endif %} +| `用户` | 包含与您的帐户相关的所有活动。 | 下面列出了这些类别中各事件的说明。 @@ -138,7 +138,7 @@ versions: | access | 当您拥有的仓库[从“私有”切换到“公共”](/articles/making-a-private-repository-public)（反之亦然）时触发。 | | add_member | 当 {% data variables.product.product_name %} 用户 {% if currentVersion == "free-pro-team@latest" %}[被邀请协作使用](/articles/inviting-collaborators-to-a-personal-repository){% else %}[被授权协作使用](/articles/inviting-collaborators-to-a-personal-repository){% endif %}仓库时触发。 | | add_topic | 当仓库所有者向仓库[添加主题](/articles/classifying-your-repository-with-topics)时触发。 | -| archived | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| archived | 在仓库所有者[存档仓库](/articles/about-archiving-repositories)时触发。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | config.disable_anonymous_git_access | 当公共仓库中[禁用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)时触发。 | | config.enable_anonymous_git_access | 当公共仓库中[启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)时触发。 | | config.lock_anonymous_git_access | 当仓库的[匿名 Git 读取权限设置被锁定](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)时触发。 | @@ -213,18 +213,18 @@ versions: #### `user` 类别 -| 操作 | 描述 | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 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 | 当您创建新用户帐户时触发。 | -| remove_email | 当您删除电子邮件地址时触发。 | -| rename | Triggered when you rename your account.{% if currentVersion != "github-ae@latest" %} -| change_password | 当您更改密码时触发。 | -| forgot_password | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} -| login | 当您登录 {% 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 | 当您[在个人资料中公开私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。 | +| 操作 | 描述 | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| add_email | 在您{% if currentVersion != "github-ae@latest" %}[新增电子邮件地址](/articles/changing-your-primary-email-address){% else %}新增电子邮件地址{% endif %}时触发。 | +| create | 当您创建新用户帐户时触发。 | +| remove_email | 当您删除电子邮件地址时触发。 | +| rename | 在重命名帐户时触发。{% if currentVersion != "github-ae@latest" %} +| change_password | 当您更改密码时触发。 | +| forgot_password | 在您要求[重置密码](/articles/how-can-i-reset-my-password)时触发。{% endif %} +| login | 当您登录 {% data variables.product.product_location %} 时触发。 | +| failed_login | 在无法成功登录时触发。{% if currentVersion != "github-ae@latest" %} +| two_factor_requested | 当 {% data variables.product.product_name %} 要求您提供[双重身份验证代码](/articles/accessing-github-using-two-factor-authentication)时触发。{% endif %} +| show_private_contributions_count | 当您[在个人资料中公开私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。 | | hide_private_contributions_count | 当您[在个人资料中隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。{% if currentVersion == "free-pro-team@latest" %} | report_content | 当您[举报议题或拉取请求，或者举报对议题、拉取请求或提交的评论](/articles/reporting-abuse-or-spam)时触发。{% endif %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/signing-commits.md b/translations/zh-CN/content/github/authenticating-to-github/signing-commits.md index 75001f1f673d..b088b3bb9f9f 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/signing-commits.md +++ b/translations/zh-CN/content/github/authenticating-to-github/signing-commits.md @@ -1,6 +1,6 @@ --- title: 对提交签名 -intro: You can sign commits locally using GPG or S/MIME. +intro: 您可以使用 GPG 或 S/MIME 在本地对提交进行签名。 redirect_from: - /articles/signing-commits-and-tags-using-gpg/ - /articles/signing-commits-using-gpg/ diff --git a/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md index f4ef3c762f77..6c533030fe2a 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md +++ b/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md @@ -1,6 +1,6 @@ --- title: 将您的签名密钥告知 Git -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: "要在本地对提交签名，您需要通知 Git 您想要使用的 GPG 或 X.509 密钥。" redirect_from: - /articles/telling-git-about-your-gpg-key/ - /articles/telling-git-about-your-signing-key diff --git a/translations/zh-CN/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/zh-CN/content/github/authenticating-to-github/updating-your-github-access-credentials.md index 6f059fb3a844..8ccdf4919818 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/updating-your-github-access-credentials.md +++ b/translations/zh-CN/content/github/authenticating-to-github/updating-your-github-access-credentials.md @@ -1,6 +1,6 @@ --- title: 更新 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 %}. 如果您有需要，可以自行重置所有这些访问凭据。' +intro: '{% data variables.product.product_name %} 凭据不仅{% if currentVersion != "github-ae@latest" %}包括密码，还{% endif %}包括您用于与 {% data variables.product.product_name %} 通信的访问令牌、SSH 密钥和应用程序 API 令牌。 如果您有需要，可以自行重置所有这些访问凭据。' redirect_from: - /articles/rolling-your-credentials/ - /articles/how-can-i-reset-my-password/ diff --git a/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md b/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md index e750d090605b..296183e382b2 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md +++ b/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md @@ -11,7 +11,7 @@ versions: 在仓库中创建议题和拉取请求后，贡献者可以根据仓库的参与指南使用模板打开议题或描述其拉取请求中提议的更改。 有关向仓库添加参与指南的更多信息，请参阅“[设置仓库贡献者指南](/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 %}. 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 +您可以为组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %} 创建默认的议题和拉取请求模板。 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 ### 议题模板 diff --git a/translations/zh-CN/content/github/building-a-strong-community/about-team-discussions.md b/translations/zh-CN/content/github/building-a-strong-community/about-team-discussions.md index b2d9a9e01cbf..5095d1043198 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/about-team-discussions.md +++ b/translations/zh-CN/content/github/building-a-strong-community/about-team-discussions.md @@ -27,7 +27,7 @@ versions: {% tip %} -**提示：**根据通知设置，您将通过电子邮件和/或 {% data variables.product.product_name %} 上的 web 通知页面收到更新。 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 %}." +**提示：**根据通知设置，您将通过电子邮件和/或 {% data variables.product.product_name %} 上的 web 通知页面收到更新。 更多信息请参阅 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”和“[关于 web 通知](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}”。 {% endtip %} @@ -35,7 +35,7 @@ versions: 要关闭团队讨论的通知，您可以取消订阅特定的讨论帖子，或者更改通知设置，以取消关注或完全忽略特定团队的讨论。 即使您取消关注团队的讨论，也可订阅特定讨论帖子的通知。 -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)." +更多信息请参阅 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}“[订阅和退订通知](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}”和“[嵌套的团队](/articles/about-teams/#nested-teams)”。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md b/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md index 8962aa5e6763..5aff7dc3d223 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md +++ b/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md @@ -13,7 +13,7 @@ versions: ![支持指南](/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 %}. 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 +您可以为组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %} 创建默认的支持资源。 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 {% tip %} diff --git a/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 028e99d7c13e..b1d70722b352 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -20,7 +20,7 @@ versions: 您阻止用户后： - 该用户停止关注您 - 该用户停止关注并取消固定您的仓库 -- The user is not able to join any organizations you are an owner of +- 用户无法加入您是所有者的任何组织 - 该用户的星标和议题分配从您的仓库中删除 - 该用户对您的仓库的复刻被删除 - 您删除用户仓库的任何复刻 diff --git a/translations/zh-CN/content/github/building-a-strong-community/creating-a-default-community-health-file.md b/translations/zh-CN/content/github/building-a-strong-community/creating-a-default-community-health-file.md index 5575afd0bb52..ffee368355c9 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/creating-a-default-community-health-file.md +++ b/translations/zh-CN/content/github/building-a-strong-community/creating-a-default-community-health-file.md @@ -12,38 +12,38 @@ versions: ### 关于默认社区健康文件 -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 %}. +您可以将默认社区健康文件添加到组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %}拥有的公共仓库 `.github` 的根目录。 对于在以下任何位置不含该类型自有文件的帐户所拥有的任何公共仓库，{% data variables.product.product_name %} 将使用并显示默认文件： - 仓库的根目录 - `.github` 文件夹 - `docs` 文件夹 -例如，在不含自有 CONTRIBUTING 文件的公共仓库中创建议题或拉取请求的人将会看到指向默认 CONTRIBUTING 文件的链接。 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. +例如，在不含自有 CONTRIBUTING 文件的公共仓库中创建议题或拉取请求的人将会看到指向默认 CONTRIBUTING 文件的链接。 如果仓库在其自己的 `.github/ISSUE_TEMPLATE` 文件夹{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}中含有任何文件，包括议题模板或*config.yml*文件{% endif %}，则不会使用默认 `.github/ISSUE_TEMPLATE` 文件夹的内容。 默认文件不包含在各个仓库的克隆、包或下载中，因为它们只存储在 `.github` 仓库中。 ### 支持的文件类型 -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: +您可以在组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %} 中为以下社区健康文件创建默认内容： -| 社区健康文件 | 描述 | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| *CODE_OF_CONDUCT.md* | CODE_OF_CONDUCT 文件定义如何参与社区的标准。 更多信息请参阅“[为项目添加行为准则](/articles/adding-a-code-of-conduct-to-your-project/)”。{% endif %} -| *CONTRIBUTING.md* | CONTRIBUTING 文件说明人们应如何参与您的项目。 更多信息请参阅“[设置仓库参与者指南](/articles/setting-guidelines-for-repository-contributors/)”。{% if currentVersion == "free-pro-team@latest" %} -| *FUNDING.yml* | FUNDING 文件在仓库中显示赞助者按钮，以提高开源项目资助选项的可见性。 更多信息请参阅“[在仓库中显示赞助按钮](/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 %} | 议题和拉取请求模板可自定义和标准化您希望贡献者在您的仓库中打开议题和拉取请求时加入的信息。 更多信息请参阅“[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates/)”。{% if currentVersion == "free-pro-team@latest" %} -| *SECURITY.md* | SECURITY 文件说明如何负责任地报告项目中的安全漏洞。 更多信息请参阅“[添加安全政策到仓库](/articles/adding-a-security-policy-to-your-repository)”。{% endif %} -| *SUPPORT.md* | SUPPORT 文件告知获取项目相关帮助的方式。 更多信息请参阅“[为项目添加支持资源](/articles/adding-support-resources-to-your-project/)”。 | +| 社区健康文件 | 描述 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| *CODE_OF_CONDUCT.md* | CODE_OF_CONDUCT 文件定义如何参与社区的标准。 更多信息请参阅“[为项目添加行为准则](/articles/adding-a-code-of-conduct-to-your-project/)”。{% endif %} +| *CONTRIBUTING.md* | CONTRIBUTING 文件说明人们应如何参与您的项目。 更多信息请参阅“[设置仓库参与者指南](/articles/setting-guidelines-for-repository-contributors/)”。{% if currentVersion == "free-pro-team@latest" %} +| *FUNDING.yml* | FUNDING 文件在仓库中显示赞助者按钮，以提高开源项目资助选项的可见性。 更多信息请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”。{% endif %} +| 议题和拉取请求模板{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 和 *config.yml*{% endif %} | 议题和拉取请求模板可自定义和标准化您希望贡献者在您的仓库中打开议题和拉取请求时加入的信息。 更多信息请参阅“[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates/)”。{% if currentVersion == "free-pro-team@latest" %} +| *SECURITY.md* | SECURITY 文件说明如何负责任地报告项目中的安全漏洞。 更多信息请参阅“[添加安全政策到仓库](/articles/adding-a-security-policy-to-your-repository)”。{% endif %} +| *SUPPORT.md* | SUPPORT 文件告知获取项目相关帮助的方式。 更多信息请参阅“[为项目添加支持资源](/articles/adding-support-resources-to-your-project/)”。 | 您不能创建默认许可文件。 必须将许可文件添加到各个仓库中，以便在克隆、打包或下载项目时包含该文件。 ### 创建用于默认文件的仓库 {% 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. ![所有者下拉菜单](/assets/images/help/repository/create-repository-owner.png) +2. 使用 **Owner（所有者）** 下拉菜单选择要为其创建默认文件的组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %}。 ![所有者下拉菜单](/assets/images/help/repository/create-repository-owner.png) 3. 键入 **.github** 作为仓库的名称，可选择键入说明。 ![创建仓库字段](/assets/images/help/repository/default-file-repository-name.png) 4. 确保存储库状态设置为**公共**（默认文件的仓库不能是私有的）。 ![用于选择机密或公开状态的单选按钮](/assets/images/help/repository/create-repository-public-private.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -7. 在仓库中，创建一个受支持的社区健康文件。 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`. 所有其他支持的文件必须在仓库的根目录中。 更多信息请参阅“[创建新文件](/articles/creating-new-files/)”。 +7. 在仓库中，创建一个受支持的社区健康文件。 议题模板{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 及其配置文件{% endif %} 必须在一个名为 `.github/ISSUE_TEMPLATE` 的文件夹中。 所有其他支持的文件必须在仓库的根目录中。 更多信息请参阅“[创建新文件](/articles/creating-new-files/)”。 diff --git a/translations/zh-CN/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md b/translations/zh-CN/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md index 9279fdaf407d..a02aace2b136 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md +++ b/translations/zh-CN/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md @@ -13,7 +13,7 @@ versions: 您可以在任何支持的文件夹中创建 *PULL_REQUEST_TEMPLATE/* 子目录，以包含多个拉取请求模板，并使用 `template` 查询参数指定填充拉取请求正文的模板。 更多信息请参阅“[关于使用查询参数自动化议题和拉取请求](/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 %}. 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 +您可以为组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %} 创建默认的拉取请求模板。 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 ### 添加拉取请求模板 diff --git a/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md b/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md index 1db1fe80fc6b..c6776434fbe2 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md +++ b/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md @@ -1,35 +1,35 @@ --- title: 限制组织中的交互 -intro: 'You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.' +intro: '您可以临时为组织拥有的所有公共仓库中的某些用户执行一段时间有限的活动。' 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: 组织所有者可限制组织中的交互。 --- ### About temporary interaction limits -Limiting interactions in your organization enables temporary interaction limits for all public repositories owned by the organization. {% data reusables.community.interaction-limits-restrictions %} +限制组织中的交互可对组织拥有的所有公共仓库启用临时交互限制。 {% 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 %} 限制期过后，用户可以在组织的公共仓库中恢复正常活动。 {% data reusables.community.types-of-interaction-limits %} -Members of the organization are not affected by any of the limit types. +组织成员不受任何限制类型的影响。 在整个组织范围内启用活动限制时，无法对个别仓库启用或禁用交互限制。 For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/articles/limiting-interactions-in-your-repository)." -Organization owners can also block users for a specific amount of time. 在阻止到期后，该用户会自动解除阻止。 更多信息请参阅“[阻止用户访问组织](/articles/blocking-a-user-from-your-organization)”。 +组织所有者也可在特定的时间段内阻止用户。 在阻止到期后，该用户会自动解除阻止。 更多信息请参阅“[阻止用户访问组织](/articles/blocking-a-user-from-your-organization)”。 ### 限制组织中的交互 {% 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. 在组织设置侧边栏中，单击 **Moderation settings（仲裁设置）**。 ![组织设置侧边栏中的"Moderation settings（仲裁设置）"](/assets/images/help/organizations/org-settings-moderation-settings.png) +1. 在“Moderation settings（仲裁设置）”下，单击 **Interaction limits（交互限制）**。 ![组织设置侧边栏中的"Interaction limits（交互限制）"](/assets/images/help/organizations/org-settings-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![临时交互限制选项](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) diff --git a/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md b/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md index ad36cbd0561a..d6dc06d38f0a 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md +++ b/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md @@ -1,30 +1,30 @@ --- title: 限制仓库中的交互 -intro: 'You can temporarily enforce a period of limited activity for certain users on a public repository.' +intro: '您可以临时对公共仓库中的某些用户限制活动一段时间。' 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: 对仓库具有管理员权限的人可以临时限制该仓库中的交互。 --- ### About temporary interaction limits {% 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 %} 在限制期过后，用户可以在您的仓库中恢复正常活动。 {% 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)." +您也可以为用户帐户或组织拥有的所有仓库启用或活动限制。 如果启用了用户范围或组织范围的限制，则不能限制帐户拥有的单个仓库的活动。 更多信息请参阅“[限制用户帐户的交互](/github/building-a-strong-community/limiting-interactions-for-your-user-account)”和“[限制组织中的交互](/github/building-a-strong-community/limiting-interactions-in-your-organization)”。 ### 限制仓库中的交互 {% 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**. ![仓库设置中的交互限制 ](/assets/images/help/repository/repo-settings-interaction-limits.png) +1. 在左侧边栏中，单击 **Moderation settings（仲裁设置）**。 ![仓库设置侧边栏中的"Moderation settings（仲裁设置）"](/assets/images/help/repository/repo-settings-moderation-settings.png) +1. 在“Moderation settings（仲裁设置）”下，单击 **Interaction limits（交互限制）**。 ![仓库设置中的交互限制 ](/assets/images/help/repository/repo-settings-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![临时交互限制选项](/assets/images/help/repository/temporary-interaction-limits-options.png) diff --git a/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md b/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md index e365d359f14f..8d9264108f1d 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md +++ b/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md @@ -20,7 +20,7 @@ versions: 对于所有者和参与者来说，参与指南节省了由于不正确创建必须拒绝和重新提交的拉取请求或议题而导致的时间和麻烦。 -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 %}. 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 +您可以为组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %} 创建默认的参与指南。 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 {% tip %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index 963d01f373bb..92a6dba43e77 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -25,7 +25,7 @@ versions: {% data reusables.branches.new-repo-default-branch %} 默认分支是任何人访问您的仓库时 {% data variables.product.prodname_dotcom %} 显示的分支。 默认分支也是初始分支，当有人克隆存储库时，Git 会在本地检出该分支。 {% 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. +默认情况下，{% data variables.product.product_name %} 将任何新仓库中的默认分支命名为{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}。 {% data reusables.branches.set-default-branch %} @@ -74,7 +74,7 @@ By default, {% data variables.product.product_name %} names the default branch { - 如果对分支启用了必需状态检查，则在所有必需 CI 测试通过之前，无法将更改合并到分支。 更多信息请参阅“[关于状态检查](/articles/about-status-checks)”。 - 如果对分支启用了必需拉取请求审查，则在满足拉取请求审查策略中的所有要求之前，无法将更改合并到分支。 更多信息请参阅“[合并拉取请求](/articles/merging-a-pull-request)”。 - 如果对分支启用了代码所有者的必需审查，并且拉取请求修改具有所有者的代码，则代码所有者必须批准拉取请求后才可合并。 更多信息请参阅“[关于代码所有者](/articles/about-code-owners)”。 -- 如果对分支启用了必需提交签名，则无法将任何提交推送到未签名和验证的分支。 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" %} +- 如果对分支启用了必需提交签名，则无法将任何提交推送到未签名和验证的分支。 更多信息请参阅“[关于提交签名验证](/articles/about-commit-signature-verification)”和“[关于必需提交签名](/articles/about-required-commit-signing)”。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - 如果您使用 {% data variables.product.prodname_dotcom %} 的冲突编辑器来解决从受保护分支创建拉取请求的冲突，{% data variables.product.prodname_dotcom %} 可帮助您为拉取请求创建一个备用分支，以解决合并冲突。 更多信息请参阅“[解决 {% data variables.product.prodname_dotcom %} 上的合并冲突](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)”。{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index 780ecd5aa8fb..897a71826544 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -20,7 +20,7 @@ versions: ### 反应评论意见 -您可以在对话中对某种想法表示支持或反对。 在对评论或者团队讨论、议题或拉取请求添加反应时，订阅对话的人不会收到通知。 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 %}." +您可以在对话中对某种想法表示支持或反对。 在对评论或者团队讨论、议题或拉取请求添加反应时，订阅对话的人不会收到通知。 有关订阅的更多信息，请参阅 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[订阅和退订通知](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}”。 ![包含反应的议题示例](/assets/images/help/repository/issue-reactions.png) diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index 7efa3cfed14e..e42f3a7fa2c2 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -13,7 +13,7 @@ versions: 打开拉取请求后，具有*读取*权限的任何人都可以查看该拉取请求提议的更改并进行评论。 您也可以建议对代码行的具体更改，作者可直接从拉取请求应用这些更改。 更多信息请参阅“[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-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. 更多信息请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”。{% endif %} +仓库所有者和协作者可向具体的个人申请拉取请求审查。 组织成员也可向具有仓库读取权限的团队申请拉取请求审查。 更多信息请参阅“[申请拉取请求审查](/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" %}您可以指定自动分配一部分团队成员，而不是分配整个团队。 更多信息请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”。{% endif %} 审查允许讨论提议的更改，帮助确保更改符合仓库的参与指南及其他质量标准。 您可以在 CODEOWNERS 文件中定义哪些个人或团队拥有代码的特定类型或区域。 当拉取请求修改定义了所有者的代码时，该个人或团队将自动被申请为审查者。 更多信息请参阅“[关于代码所有者](/articles/about-code-owners/)”。 @@ -38,7 +38,7 @@ versions: {% data reusables.pull_requests.resolving-conversations %} -### Re-requesting a review +### 重新请求审核 {% data reusables.pull_requests.re-request-review %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md index 72d1128caf5d..2fc0c19a5531 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md @@ -59,7 +59,7 @@ versions: 比较页和拉取请求页使用不同的方法来计算已更改文件的差异： - 比较页显示头部引用的提示与头部及基础引用当前的共同上层节点（即合并基础）之间的差异。 -- Pull request pages show the diff between the tip of the head ref and the common ancestor of the head and base ref at the time when the pull request was created. Consequently, the merge base used for the comparison might be different. +- 拉请求页面显示在创建拉取请求时头部引用头与头部和基础的共同上层节点之间的差异。 因此，用于比较的合并基础可能不同。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md index e6cc7e33a10f..86b3bba2f8f3 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md @@ -23,7 +23,7 @@ versions: {% tip %} -**Tip:** When you open a pull request, {% data variables.product.product_name %} will set the base to the commit that branch references. If the branch is updated in the future, {% data variables.product.product_name %} will not update the base branch's commit. +**提示：**当您打开拉取请求时，{% data variables.product.product_name %} 将设置分支引用的提交的基础。 如果将来更新该分支，{% data variables.product.product_name %} 不会更新基础分支的提交。 {% endtip %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md index 27961337a628..d2c94f75cbb0 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: 更改拉取请求的阶段 -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: '您可以将拉取请求草稿标记为可供审查{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} 或将拉取请求转换为草稿{% endif %}。' permissions: 具有仓库写入权限的人员和拉取请求作者可以更改拉取请求的阶段。 product: '{% data reusables.gated-features.draft-prs %}' redirect_from: diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md index 851ca1964d89..db629bdb65a1 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md @@ -25,7 +25,7 @@ versions: 4. 在提交消息字段中，输入简短、有意义的提交消息，以描述对文件的更改。 ![提交消息字段](/assets/images/help/pull_requests/suggested-change-commit-message-field.png) 5. 单击 **Commit changes（提交更改）**。 ![提交更改按钮](/assets/images/help/pull_requests/commit-changes-button.png) -### Re-requesting a review +### 重新请求审核 {% data reusables.pull_requests.re-request-review %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index f5e446173596..8fd56fd6ca0d 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -45,7 +45,7 @@ versions: {% 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. + **注意：** 电子邮件选择器不可用于变基合并（无法创建合并提交） 或压缩合并（将创建拉取请求的用户计为压缩提交的作者）。 {% endnote %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index a976b5404e22..8070881fa28b 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -11,7 +11,7 @@ versions: 用户帐户拥有的仓库的所有者和协作者可以分配拉取请求审查。 拥有仓库查验漏洞权限的组织成员可以分配拉取请求审查。 -所有者或协作者可以将拉取请求审核分配给被明确授予用户拥有仓库[读取权限](/articles/access-permissions-on-github)的任何人。 组织成员也可将拉取请求审查分配给拥有仓库读取权限的任何个人或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% 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. 更多信息请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”。{% endif %} +所有者或协作者可以将拉取请求审核分配给被明确授予用户拥有仓库[读取权限](/articles/access-permissions-on-github)的任何人。 组织成员也可将拉取请求审查分配给拥有仓库读取权限的任何个人或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 更多信息请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”。{% endif %} {% note %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md index 639f20575cd8..de59e89ab492 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md @@ -34,7 +34,7 @@ versions: {% 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 %}. 必须使用备用 Git 客户端或在命令行上使用 Git 解决合并冲突。 更多信息请参阅“[使用命令行解决合并冲突](/articles/resolving-a-merge-conflict-using-the-command-line)”。 + **提示：**如果停用 **Resolve conflicts（解决冲突）**按钮，则拉取请求的合并冲突过于复杂而无法在 {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 上解决，或站点管理员已禁用仓库之间拉取请求的冲突编辑器{% endif %}。 必须使用备用 Git 客户端或在命令行上使用 Git 解决合并冲突。 更多信息请参阅“[使用命令行解决合并冲突](/articles/resolving-a-merge-conflict-using-the-command-line)”。 {% endtip %} {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index b50123e97848..0d0b0aee3eaa 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -11,7 +11,7 @@ versions: ### 关于审查拉取请求 -您可以在拉取请求中每次审查一个文件的更改。 While reviewing the files in a pull request, you can leave individual comments on specific changes. After you finish reviewing each file, you can mark the file as viewed. 这会折叠文件，帮助您识别还需要审查的文件。 A progress bar in the pull request header shows the number of files you've viewed. After reviewing as many files as you want, you can approve the pull request or request additional changes by submitting your review with a summary comment. +您可以在拉取请求中每次审查一个文件的更改。 在拉取请求中审查文件时，可以对特定更改留下单个注释。 在完成审查每个文件后，您可以将该文件标记为已查看。 这会折叠文件，帮助您识别还需要审查的文件。 拉取请求标题中的进度条显示您查看过的文件数。 在按需要审查文件后， 您可以提交包含摘要评论的审查来批准拉取请求或请求额外更改。 {% data reusables.search.requested_reviews_search_tip %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md index acf885c1c1cc..598287985064 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md @@ -13,7 +13,7 @@ versions: {% data reusables.command_line.open_the_multi_os_terminal %} 2. 将当前工作目录更改为您的本地仓库。 -3. 从上游仓库获取分支及其各自的提交。 Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +3. 从上游仓库获取分支及其各自的提交。 对 `BRANCHNAME` 的提交将存储在本地分支 `upstream/BRANCHNAME` 中。 ```shell $ git fetch upstream > remote: Counting objects: 75, done. @@ -23,12 +23,12 @@ versions: > 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. 检出复刻的本地默认分支 - 在本例中，我们使用 `main`。 ```shell $ git checkout main > Switched to branch 'main' ``` -5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. +5. 将上游默认分支 - 本例中为 `upstream/main` - 的更改合并到本地默认分支。 这会使复刻的默认分支与上游仓库同步，而不会丢失本地更改。 ```shell $ git merge upstream/main > Updating a422352..5fdff0f diff --git a/translations/zh-CN/content/github/committing-changes-to-your-project/comparing-commits.md b/translations/zh-CN/content/github/committing-changes-to-your-project/comparing-commits.md index 4335b27ab466..5a4fceac5757 100644 --- a/translations/zh-CN/content/github/committing-changes-to-your-project/comparing-commits.md +++ b/translations/zh-CN/content/github/committing-changes-to-your-project/comparing-commits.md @@ -27,9 +27,9 @@ versions: ### 比较标记 -比较发行版标记将显示自上次发布以来您对仓库的更改。 {% 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 %} +比较发行版标记将显示自上次发布以来您对仓库的更改。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} 更多信息请参阅“[比较发行版](/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.20" %}要比较标记，可以从页面顶部的 `compare` 下拉菜单选择标记名称。{% else %} 不是键入分支名称，而是键入 `compare` 下拉菜单中的标记名称。{% endif %} 此处是[在两个标记之间进行比较](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3)的示例。 diff --git a/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index 41e50390c01a..3ef52bd5cf98 100644 --- a/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -1,6 +1,6 @@ --- title: 创建有多个作者的提交 -intro: '通过在提交消息中添加一个或多个 `Co-authored-by` 尾行，可将提交归属于多个作者。 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 %}.' +intro: '通过在提交消息中添加一个或多个 `Co-authored-by` 尾行，可将提交归属于多个作者。 合作提交在 {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 上可见，并且可包含在个人资料贡献图和仓库统计信息中{% endif %}。' redirect_from: - /articles/creating-a-commit-with-multiple-authors versions: @@ -31,7 +31,7 @@ versions: ### 使用 {% data variables.product.prodname_desktop %} 创建合作提交 -可以使用 {% data variables.product.prodname_desktop %} 创建合作提交。 更多信息请参阅“[编写提交消息并推送更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)”和 [{% data variables.product.prodname_desktop %}](https://desktop.github.com)。 +可以使用 {% data variables.product.prodname_desktop %} 创建合作提交。 更多信息请参阅“[编写提交消息并推送更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)”和 [{% data variables.product.prodname_desktop %}](https://desktop.github.com)。 ![添加合作作者到提交消息](/assets/images/help/desktop/co-authors-demo-hq.gif) @@ -74,4 +74,4 @@ versions: - “[查看仓库活动的摘要](/articles/viewing-a-summary-of-repository-activity)” - “[查看项目的贡献者](/articles/viewing-a-projects-contributors)” - “[更改提交消息](/articles/changing-a-commit-message)” -- {% data variables.product.prodname_desktop %} 文档中的“[提交和审查对项目的更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)” +- {% data variables.product.prodname_desktop %} 文档中的“[提交和审查对项目的更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)” diff --git a/translations/zh-CN/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md b/translations/zh-CN/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md index 0940bd94bbd4..33e764eadf7b 100644 --- a/translations/zh-CN/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/zh-CN/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md @@ -3,7 +3,7 @@ title: 我的提交为什么链接到错误的用户？ 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: '{% data variables.product.product_name %} 使用提交标题中的电子邮件地址将提交链接到 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: '{% data variables.product.product_name %} 使用提交标题中的电子邮件地址将提交链接到 GitHub 用户。 如果将您的提交链接到其他用户，或者根本没有链接到任何用户，您可能需要更改本地 Git 配置设置{% if currentVersion != "github-ae@latest" %}，将电子邮件地址添加到您的帐户电子邮件设置，或同时执行这两项操作{% endif %}。' versions: free-pro-team: '*' enterprise-server: '*' @@ -19,10 +19,10 @@ versions: ### 提交链接到其他用户 -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. 原来的提交不会进行链接。 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. +如果您的提交链接到其他用户，则意味着本地 Git 配置设置中的电子邮件地址已连接到该用户在 {% data variables.product.product_name %}上的帐户。 在这种情况下，您可以将本地 Git 配置设置中的电子邮件{% if currentVersion == "github-ae@latest" %} 更改为 {% data variables.product.product_name %} 上与您的帐户关联的地址，以链接您未来的提交。 原来的提交不会进行链接。 更多信息请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”。{% else %}并且将新的电子邮件地址添加到 {% data variables.product.product_name %} 帐户以将未来的提交链接到您的帐户。 -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)". 如果您在多台计算机上工作，则需要在每台计算机上更改此设置。 -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. 要更改本地 Git 配置中的电子邮件地址，请按照“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”中的步骤操作。 如果您在多台计算机上工作，则需要在每台计算机上更改此设置。 +2. 按照“[添加电子邮件地址到 GitHub 帐户](/articles/adding-an-email-address-to-your-github-account)”中的步骤操作，将步骤 2 中的电子邮件地址添加到您的帐户设置。{% endif %} 从这时开始，您提交的内容将链接到您的帐户。 @@ -35,12 +35,12 @@ If your commits are linked to another user, that means the email address in your 1. 通过单击提交消息链接导航到提交。 ![提交消息链接](/assets/images/help/commits/commit-msg-link.png) 2. 要阅读有关提交未链接原因的消息，请将鼠标悬停在用户名右侧的蓝色 {% octicon "question" aria-label="Question mark" %} 上。 ![提交悬停消息](/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 %} + - **无法识别的作者（含电子邮件地址）**如果您看到此消息包含电子邮件地址，则表示用于创作提交的地址未连接到您在 {% data variables.product.product_name %} 上的帐户。 {% if currentVersion != "github-ae@latest" %}要链接提交，请[将电子邮件地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)。{% endif %}如果电子邮件地址关联了 Gravatar，提交旁边将显示该 Gravatar，而不是默认的灰色 Octocat。 + - **无法识别的作者（无电子邮件地址）**如果您看到此消息没有电子邮件地址，则表示您使用了无法连接到您在 {% data variables.product.product_name %} 上的帐户的通用电子邮件地址。{% if currentVersion != "github-ae@latest" %} 您需要[在 Git 中设置提交电子邮件地址](/articles/setting-your-commit-email-address)，然后[将新地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)以链接您未来的提交。 旧提交不会链接。{% endif %} + - **无效的电子邮件地址**本地 Git 配置设置中的电子邮件地址为空白或未格式化为电子邮件地址。{% if currentVersion != "github-ae@latest" %} 您需要[在 Git 中设置提交电子邮件地址](/articles/setting-your-commit-email-address)，然后[将新地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)以链接您未来的提交。 旧提交不会链接。{% 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. 原来的提交不会进行链接。 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)." +您可以将本地 Git 配置设置中的电子邮件地址更改为与您的帐户关联的地址，以链接您未来的提交。 原来的提交不会进行链接。 更多信息请参阅“[设置提交电子邮件地址](/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/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 359115677392..a7ae9d0d054a 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -21,7 +21,7 @@ versions: 当具有管理员或所有者权限的人员启用必需审查时，他们也可选择性要求代码所有者批准后，作者才可合并仓库中的拉取请求。 更多信息请参阅“[启用拉取请求的必需审查](/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. 更多信息请参阅“[管理团队的代码审查分配](/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.19" %}如果团队启用了代码审查分配，则个别审批无法满足受保护分支中代码所有者审批的要求。 更多信息请参阅“[管理团队的代码审查分配](/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" %} 如果文件具有代码所有者，则在打开拉取请求之前可以看到代码所有者是谁。 在仓库中，您可以浏览文件并将鼠标悬停在上方 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md index f14d91ce5194..24d6b95a4f9e 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -14,8 +14,8 @@ versions: github-ae: '*' --- -{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to -determine file languages for syntax highlighting and repository statistics. 语言统计数据在您推送更改到默认分支后将会更新。 +{% data variables.product.product_name %} 使用开源 [Linguist 库](https://github.com/github/linguist)来 +确定用于语法突出显示和仓库统计信息的文件语言。 语言统计数据在您推送更改到默认分支后将会更新。 有些文件难以识别，有时项目包含的库和供应商文件多于其主要代码。 如果您收到错误结果，请查阅 Linguist [故障排除指南](https://github.com/github/linguist#troubleshooting)寻求帮助。 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index 251aa7d4763e..f467ee2463aa 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -1,6 +1,6 @@ --- title: 关于仓库可见性 -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 %}.' +intro: '您可以通过选择仓库的可见性来限制谁有权访问仓库：{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}公共、内部或私有{% elsif currentVersion == "github-ae@latest" %}私有或内部{% else %} 公共或私有{% endif %}。' versions: free-pro-team: '*' enterprise-server: '*' @@ -9,15 +9,15 @@ versions: ### 关于仓库可见性 -{% 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" %}当您创建由您的用户帐户拥有的仓库时，仓库始终是私有的。 创建组织拥有的仓库时，可以选择将仓库设为私有或内部。{% else %}创建仓库时，可以选择使仓库成为公共或私有。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 如果要在组织中创建{% if currentVersion == "free-pro-team@latest" %} 由企业帐户拥有的仓库{% endif %}，也可以选择将仓库设为内部。{% 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. 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。{% endif %} +{% data variables.product.product_location %} 不是私人模式或在防火墙后面，所有人都可以在互联网上访问公共仓库。 或者，使用 {% data variables.product.product_location %} 的每个人都可以使用公共仓库，包括外部协作者。 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 {% if currentversion ver_gt "enterprise-server@2.19" %} 内部仓库可供企业成员访问。 更多信息请参阅“[关于内部仓库](#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)." +私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 所有企业成员均可访问内部仓库。 更多信息请参阅“[关于内部仓库](#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)." +互联网上的所有人都可以访问公共仓库。 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 企业成员可以访问内部仓库。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。 {% endif %} 组织所有者始终有权访问其组织中创建的每个仓库。 更多信息请参阅“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)”。 @@ -35,9 +35,9 @@ Public repositories are accessible to everyone on the internet. Private reposito {% data reusables.repositories.about-internal-repos %} 有关内部资源的更多信息，请参阅 {% data variables.product.prodname_dotcom %} 的白皮书“[内部资源简介](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)." +所有企业成员对内部仓库具有读取权限，但内部仓库对{% if currentVersion == "free-pro-team@latest" %}企业外部{% else %}非组织成员{% endif %}的人员不可见，包括组织仓库的外部协作者。 更多信息请参阅 {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}“[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)”和{% endif %}“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)”。 {% 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. +如果用户从企业拥有的所有组织中删除，该用户的内部仓库复刻也会自动删除。 {% endif %} 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 f252dbd72818..d7ac5179bc46 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 @@ -1,6 +1,6 @@ --- title: 备份仓库 -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.' +intro: '您可以使用{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Git 和{% endif %} API {% if currentVersion == "free-pro-team@latest" %}或第三方工具{% endif %}备份仓库。' redirect_from: - /articles/backing-up-a-repository versions: @@ -32,7 +32,7 @@ versions: - [项目](/v3/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/). +一旦您拥有 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}所有要备份内容的本地版本，您就可以创建一个 zip 存档并{% else %}下载您的存档。您可以{% endif %}将其复制到外部硬盘和/或将其上传到基于云的备份服务，例如 [Google Drive](https://www.google.com/drive/) 或 [Dropbox](https://www.dropbox.com/)。 {% if currentVersion == "free-pro-team@latest" %} ### 第三方备份工具 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md index 563731cb2e0a..8b1c278b6864 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md @@ -47,7 +47,7 @@ versions: 空仓库不含任何文件。 如果创建仓库时不使用 README 初始化仓库，通常会出现空仓库。 {% data reusables.repositories.navigate-to-repo %} -2. 要使用 HTTPS 以命令行克隆仓库，请在“Quick setup（快速设置）”下单击 {% 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 **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. ![空仓库克隆 URL 按钮](/assets/images/help/repository/empty-https-url-clone-button.png) +2. 要使用 HTTPS 以命令行克隆仓库，请在“Quick setup（快速设置）”下单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 要使用 SSH 密钥克隆仓库，包括组织的 SSH 认证中心颁发的证书，单击 **SSH**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 ![空仓库克隆 URL 按钮](/assets/images/help/repository/empty-https-url-clone-button.png) 或者，要在 Desktop 中克隆仓库，请单击 {% octicon "desktop-download" aria-label="The desktop download button" %} **Set up in Desktop（在 Desktop 中设置）**并按照提示完成克隆。 ![空仓库克隆桌面按钮](/assets/images/help/repository/empty-desktop-clone-button.png) diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md index be77a2aa0b0c..62ba4f138a8f 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: 创建模板仓库 -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.' +intro: '您可以将现有仓库设置为模板，以便您与其他人能够生成目录结构相同的新仓库{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}、分支{% endif %} 和文件。' permissions: 任何对仓库有管理员权限的人都可以将该仓库设置为模板。 redirect_from: - /articles/creating-a-template-repository @@ -12,13 +12,13 @@ versions: {% note %} -**Note**: Your template repository cannot include files stored using {% data variables.large_files.product_name_short %}. +**注意**：您的模板仓库不能包含使用 {% data variables.large_files.product_name_short %} 存储的文件。 {% endnote %} 要创建模板仓库，必须先创建一个仓库，然后将该仓库设置为模板。 关于创建仓库的更多信息，请参阅“[创建新仓库](/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)." +将仓库设置为模板后，有权访问仓库的任何人都可以生成与默认分支具有相同目录结构和文件的新仓库。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} 他们还可以选择包含您的仓库中的所有其他分支。{% endif %} 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index 66c0e9e568c8..d58ecebf9ef1 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -1,6 +1,6 @@ --- title: '错误：未找到仓库' -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-proteam@latest" or currentversion == "github-ae@latest" %}如果您在克隆仓库时看到这个错误，意味着仓库不存在或您没有权限访问它。{% else %}如果您在克隆仓库时看到此错误，意味着仓库不存在、您没有访问权限，或者 {% data variables.product.product_location %} 处于隐私模式。{% endif %} 对此错误有一些解决办法，具体取决于错误原因。' redirect_from: - /articles/error-repository-not-found versions: diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md index da74583659b2..452b673e219f 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -71,7 +71,7 @@ $ git remote -v {% tip %} -**提示**：如果不想在每次与远程仓库交互时都输入用户名和密码，您可以打开[凭据缓存](/github/using-git/caching-your-github-credentials-in-git)。 If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail. +**提示**：如果不想在每次与远程仓库交互时都输入用户名和密码，您可以打开[凭据缓存](/github/using-git/caching-your-github-credentials-in-git)。 如果已在使用凭据缓存，请确保您的计算机缓存了正确的凭据。 不正确或过期的凭据将导致身份验证失败。 {% endtip %} 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 1f69fcf9b564..f75d642ac574 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 @@ -18,7 +18,7 @@ versions: {% note %} -**Note:** If you publish your source code in a public repository on GitHub, {% if currentVersion == "free-pro-team@latest" %}according to the [Terms of Service](/articles/github-terms-of-service), {% endif %}other GitHub users have the right to view and fork your repository within the GitHub site. 如果您已创建公共仓库，并且不再希望用户访问它，便可将仓库设为私有。 在将公共仓库转换为私有仓库时，其他用户创建的现有复刻或本地副本仍将存在。 更多信息请参阅“[将公共仓库设为私有](/articles/making-a-public-repository-private)”。 +**注：**如果您在 GitHub 的公共仓库中发布源代码，{% if currentVersion == "free-pro-team@latest" %}根据[服务条款](/articles/github-terms-of-service)，{% endif %}其他 GitHub 用户有权利在 GitHub 站点中查看您的仓库并对其复刻。 如果您已创建公共仓库，并且不再希望用户访问它，便可将仓库设为私有。 在将公共仓库转换为私有仓库时，其他用户创建的现有复刻或本地副本仍将存在。 更多信息请参阅“[将公共仓库设为私有](/articles/making-a-public-repository-private)”。 {% endnote %} @@ -91,5 +91,5 @@ GitHub 开源许可的目标是提供一个起点，帮助您做出明智的决 ### 延伸阅读 -- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% if currentVersion == "free-pro-team@latest" %} +- 开源指南的“[开源的法律 方面](https://opensource.guide/legal/)”部分{% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/zh-CN/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md b/translations/zh-CN/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md index 915d9e98a3c7..793746ac599c 100644 --- a/translations/zh-CN/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md +++ b/translations/zh-CN/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md @@ -10,7 +10,7 @@ versions: ### 编辑器工具 -You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio. +您可以在第三方编辑器工具中连接到 {% data variables.product.product_name %} 仓库，例如 Atom、Unity 和 Visual Studio 等工具。 #### {% data variables.product.product_name %} for Atom @@ -34,8 +34,8 @@ You can connect to {% data variables.product.product_name %} repositories within #### Jira Cloud 与 {% data variables.product.product_name %}.com 集成 -您可以将 Jira Cloud 与个人或组织帐户集成，以扫描提交和拉取请求，在任何提及的 Jira 议题中创建相关的元数据和超链接。 For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace. +您可以将 Jira Cloud 与个人或组织帐户集成，以扫描提交和拉取请求，在任何提及的 Jira 议题中创建相关的元数据和超链接。 更多信息请访问 Marketplace 中的 [Jira 集成应用程序](https://github.com/marketplace/jira-software-github)。 -#### Slack and {% data variables.product.product_name %} integration +#### Slack 与 {% data variables.product.product_name %} 集成 -You can integrate Slack with your personal or organization account to subscribe for notifications, close or open issues, and provide rich references to issues and pull requests without leaving Slack. For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace. +您可以将 Slack 与您的个人或组织帐户集成，以订阅通知、关闭或打开的议题，并提供对议题和拉取请求的丰富引用，而无需离开 Slack。 更多信息请访问 Marketplace 中的 [Slack 集成应用程序](https://github.com/marketplace/slack-github)。 diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index b1903c24294a..c6b82da3430e 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -21,9 +21,9 @@ versions: 您可以使用项目类型的预建容器配置创建默认代码空间配置，也可以根据项目需要创建自定义配置。 -{% data variables.product.prodname_codespaces %} uses settings contained in a configuration file named `devcontainer.json`. {% data reusables.codespaces.devcontainer-location %} +{% data variables.product.prodname_codespaces %} 使用配置文件 `devcontainer.json` 中包含的设置。 {% data reusables.codespaces.devcontainer-location %} -You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the {% data variables.product.prodname_vscode %} editor, but you can also set editor-specific settings in a file named `.vscode/settings.json`. +您可以使用 `devcontainer.json` 为整个代码空间环境设置默认设置，包括 {% data variables.product.prodname_vscode %} 编辑器，但您也可以在 `.vscode/set.json` 文件中设置编辑器特定的设置。 对仓库代码空间配置的更改只会应用到每个新的代码空间，而不影响任何现有的代码空间。 @@ -40,7 +40,7 @@ You can use your `devcontainer.json` to set default settings for the entire code ### 创建自定义代码空间配置 -If none of the pre-built configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %} +如果任何预构建的配置都不能满足您的需要，您可以通过添加 `devcontainer.json` 文件来创建自定义配置。 {% data reusables.codespaces.devcontainer-location %} 在该文件中，您可以使用支持的配置键来指定代码库环境的各个方面，例如要安装哪些 {% data variables.product.prodname_vscode %} 扩展。 diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md index 49a0d649aa10..3da60d2a8cda 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- title: 在 Visual Studio Code 中使用代码空间 -intro: '您可以将 {% data variables.product.prodname_vs_codespaces %} 扩展连接到您在 {% data variables.product.product_name %} 上的帐户，直接在 {% data variables.product.prodname_vscode %} 代码空间中开发。' +intro: '您可以将 {% data variables.product.prodname_github_codespaces %} 扩展连接到您在 {% data variables.product.product_name %} 上的帐户，直接在 {% data variables.product.prodname_vscode %} 代码空间中开发。' product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code @@ -12,34 +12,33 @@ versions: ### 基本要求 -直接在 {% data variables.product.prodname_vscode %} 的代码空间中开发之前，您必须配置 {% data variables.product.prodname_vs_codespaces %} 扩展连接到您的 {% data variables.product.product_name %} 帐户。 +要直接在 {% data variables.product.prodname_vscode %} 中开发代码空间，必须登录到 {% data variables.product.prodname_github_codespaces %} 扩展。 {% data variables.product.prodname_github_codespaces %} 扩展需要 {% data variables.product.prodname_vscode %} 2020 年 10 月 1 日版本 1.51 或更高版本。 -1. 使用 {% data variables.product.prodname_vs %} Marketplace 安装 [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline) 扩展。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档中的[扩展 Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)。 -2. 在 {% data variables.product.prodname_vscode %} 中，从左侧边栏单击 Extensions（扩展）图标。 ![{% data variables.product.prodname_vscode %} 中的 Extensions（扩展）图标](/assets/images/help/codespaces/click-extensions-icon-vscode.png) -3. 在 {% data variables.product.prodname_vs_codespaces %} 下面，单击 Manage（管理）图标，然后单击 **Extension Settings（扩展设置）**。 ![Extension Settings（扩展设置）选项](/assets/images/help/codespaces/select-extension-settings.png) -4. 使用“Vsonline: Account Provider（Vsonline：帐户提供商）”下拉菜单，选择 {% data variables.product.prodname_dotcom %}。 ![设置帐户提供者为 {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/select-account-provider-vscode.png) +1. 使用 + +{% data variables.product.prodname_vs %} Marketplace 安装 [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 扩展。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档中的[扩展 Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)。 {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -6. 如果尚未在标题中选择 {% data variables.product.prodname_codespaces %}，请单击 **{% data variables.product.prodname_codespaces %}**。 ![{% data variables.product.prodname_codespaces %} 标头](/assets/images/help/codespaces/codespaces-header-vscode.png) -7. 单击 **Sign in to view {% data variables.product.prodname_codespaces %}...（登录以查看 Codespaces...）**。 ![登录以查看 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -8. 要授权 {% data variables.product.prodname_vscode %} 访问您在 {% data variables.product.product_name %} 上的帐户，请单击 **Allow（允许）**。 -9. 登录 {% data variables.product.product_name %} 以审批扩展。 +2. 使用“REMOTE EXPLORER（远程资源管理器）”下拉列表，然后单击 **{% data variables.product.prodname_github_codespaces %}**。 ![{% data variables.product.prodname_codespaces %} 标头](/assets/images/help/codespaces/codespaces-header-vscode.png) +3. 单击 **Sign in to view {% data variables.product.prodname_codespaces %}...（登录以查看 Codespaces...）**。 ![登录以查看 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) +4. 要授权 {% data variables.product.prodname_vscode %} 访问您在 {% data variables.product.product_name %} 上的帐户，请单击 **Allow（允许）**。 +5. 登录 {% data variables.product.product_name %} 以审批扩展。 ### 在 {% data variables.product.prodname_vscode %} 中创建代码空间 -After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_vs_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}. +将 {% data variables.product.product_name %} 帐户连接到 {% data variables.product.prodname_vs_codespaces %} 扩展后，您可以在 {% data variables.product.prodname_vscode %} 或 {% data variables.product.product_name %} 上创建的代码空间中进行开发。 {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) -3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop in. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) - +2. 单击 Add（添加）图标，然后单击 **Create New Codespace（创建新代码空间）**。 ![{% data variables.product.prodname_codespaces %} 中的 Create new Codespace（创建新代码空间）选项](/assets/images/help/codespaces/create-codespace-vscode.png) +3. 键入，然后单击要在其中开发仓库的名称。 ![搜索仓库以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) +4. 单击要在其中开发的分支。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) +5. 单击要在其中开发的实例类型。 ![新 {% data variables.product.prodname_codespaces %} 的实例类型](/assets/images/help/codespaces/choose-sku-vscode.png) ### 在 {% data variables.product.prodname_vscode %} 中打开代码空间 {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. 在 Codespaces（代码空间）下，单击您要在其中开发的代码空间。 3. 单击 Connect to Codespace（连接到代码空间）图标。 ![{% data variables.product.prodname_vscode %} 中的连接到代码空间图标](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -### Deleting a codespace in {% data variables.product.prodname_vscode %} +### 在 {% data variables.product.prodname_vscode %} 中删除代码空间 -1. Under Codespaces, right-click the codespace you want to delete. -2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) +1. 在 Codespaces（代码空间）下，右键点击您要删除的代码空间。 +2. 在下拉菜单中，单击 **Delete Codespace（删除代码空间）**。 ![在 {% data variables.product.prodname_dotcom %} 中删除代码空间](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/zh-CN/content/github/extending-github/getting-started-with-the-api.md b/translations/zh-CN/content/github/extending-github/getting-started-with-the-api.md index 90fb305b81b0..0007af38f18d 100644 --- a/translations/zh-CN/content/github/extending-github/getting-started-with-the-api.md +++ b/translations/zh-CN/content/github/extending-github/getting-started-with-the-api.md @@ -14,5 +14,5 @@ versions: ### 延伸阅读 -- "[Backing up a repository](/articles/backing-up-a-repository)"{% if currentVersion == "free-pro-team@latest" %} +- "[备份仓库](/articles/backing-up-a-repository)"{% if currentVersion == "free-pro-team@latest" %} - “[关于集成](/articles/about-integrations)”{% endif %} 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 ff27712b4928..572ca132ebc9 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 @@ -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: 关于代码扫描 +intro: '您可以使用 {% data variables.product.prodname_code_scanning %} 在 {% 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 %} +### 关于 {% 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. +您可以使用 {% data variables.product.prodname_code_scanning %} 来查找代码中现有的问题，并且对其进行分类和确定修复的优先级。 {% data variables.product.prodname_code_scanning_capc %} 还可防止开发者引入新问题。 您可以计划在特定的日期和时间进行扫描，或在仓库中发生特定事件（如推送）时触发扫描。 -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)." +如果 {% 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)”。 -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 %} 使用 {% data variables.product.prodname_actions %}。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。 -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)." +要开始 {% data variables.product.prodname_code_scanning %}，请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 -### About {% data variables.product.prodname_codeql %} +### 关于 {% 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. +您可以在 [`github/codeql`](https://github.com/github/codeql) 仓库中查看并参与 {% data variables.product.prodname_code_scanning %} 的查询。 {% data variables.product.prodname_codeql %} 将代码视为数据，允许您在代码中查找潜在漏洞，比传统的静态分析工具更可靠。 -{% 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 %} 是授权 {% data variables.product.prodname_codeql %} 的查询语言。 {% data variables.product.prodname_ql %} 是一种面向对象的逻辑编程语言。 {% data variables.product.company_short %}、语言专家和安全研究人员创建用于 {% data variables.product.prodname_code_scanning %} 的查询，查询是开源的。 社区维护和更新查询，以改善分析和减少误报。 更多信息请参阅 GitHub Security Lab 网站上的 [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)。 -{% 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. +有关 {% data variables.product.prodname_code_scanning %} 的 API 端点的更多信息，请参阅“[{% 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. +您可以在 [`github/codeql`](https://github.com/github/codeql) 仓库中查看并参与 {% data variables.product.prodname_code_scanning %} 的查询。 更多信息请参阅 {% data variables.product.prodname_codeql %} 文档中的 [{% data variables.product.prodname_codeql %} 查询](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html)。 {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### 关于 {% 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 %} 使用 {% data variables.product.prodname_actions %}，{% data variables.product.prodname_code_scanning %} 工作流程的每次运行将耗用 {% data variables.product.prodname_actions %} 的分钟数。 更多信息请参阅“[关于 {% 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 +### 关于第三方代码扫描工具 {% 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 +### 延伸阅读 {% 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 +- OASIS Committee 网站上的 [OASIS 静态分析结果交换格式 (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md index b3e1b3bf9b2b..9102e3de3645 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md @@ -1,7 +1,7 @@ --- title: 关于与代码扫描的集成 shortTitle: 关于集成 -intro: 'You can perform {% data variables.product.prodname_code_scanning %} externally and then display the results in {% data variables.product.prodname_dotcom %}, or set up webhooks that listen to {% data variables.product.prodname_code_scanning %} activity in your repository.' +intro: '您可以在外部执行 {% data variables.product.prodname_code_scanning %}，然后在 {% data variables.product.prodname_dotcom %} 中显示结果，或者设置侦听仓库中 {% data variables.product.prodname_code_scanning %} 活动的 web 挂钩。' product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' @@ -11,16 +11,16 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -作为在 {% data variables.product.prodname_dotcom %} 中运行 {% data variables.product.prodname_code_scanning %} 的替代方法，您可以在其他地方执行分析，然后上传结果。 在外部运行的 {% data variables.product.prodname_code_scanning %} 的警报显示方式与在 {% data variables.product.prodname_dotcom %} 内运行的 {% data variables.product.prodname_code_scanning %} 的警报显示方式相同。 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_dotcom %} 中运行 {% data variables.product.prodname_code_scanning %} 的替代方法，您可以在其他地方执行分析，然后上传结果。 在外部运行的 {% data variables.product.prodname_code_scanning %} 的警报显示方式与在 {% data variables.product.prodname_dotcom %} 内运行的 {% data variables.product.prodname_code_scanning %} 的警报显示方式相同。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 如果使用可生成结果为静态分析结果交换格式 (SARIF) 2.1.0 数据的第三方静态分析工具，您可以将其上传到 {% data variables.product.prodname_dotcom %}。 更多信息请参阅“[将 SARIF 文件上传到 GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)”。 -### Integrations with webhooks +### 与 web 挂钩集成 -You can use {% data variables.product.prodname_code_scanning %} webhooks 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/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. For example, you could build an integration that creates an issue on {% data variables.product.product_location %} or sends you a Slack notification when a new {% data variables.product.prodname_code_scanning %} alert is added in your repository. For more information, see "[Creating webhooks](/developers/webhooks-and-events/creating-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." +您可以使用 {% data variables.product.prodname_code_scanning %} web 挂钩构建或设置集成，例如 [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) 或 [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/)，以订阅仓库中的 {% data variables.product.prodname_code_scanning %} 事件。 例如，您可以构建在 {% data variables.product.product_location %} 上创建议题，或者在仓库中新增 {% data variables.product.prodname_code_scanning %} 警报时向您发送 Slack 通知的集成。 更多信息请参阅“[创建 web 挂钩](/developers/webhooks-and-events/creating-webhooks)”和“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)”。 ### 延伸阅读 -* "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" -* "[Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system)" -* "[SARIF support for {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)" +* "[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" +* "[将 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 与现有的 CI 系统一起使用](/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system)" +* "[{% data variables.product.prodname_code_scanning %} 的 SARIF 支持](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)" diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index c5c73938eda8..02103784f37c 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -95,7 +95,7 @@ $ /path/to-runner/codeql-runner-linux autobuild --language csharp 默认情况下，当您运行 `analyze` 命令时，{% data variables.product.prodname_codeql_runner %} 上传来自 {% data variables.product.prodname_code_scanning %} 的结果。 您也可以使用 `upload` 命令单独上传 SARIF 文件。 -上传数据后，{% 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#viewing-an-alert)." +上传数据后，{% 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#viewing-the-alerts-for-a-repository)." ### {% data variables.product.prodname_codeql_runner %} 命令引用 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index d44cd2e445b5..85a1cce98e4f 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -1,7 +1,7 @@ --- -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: 为仓库启用代码扫描 +shortTitle: 启用代码扫描 +intro: '您可以对项目的仓库启用 {% data variables.product.prodname_code_scanning %}。' 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.' redirect_from: @@ -15,44 +15,40 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### Options for enabling {% data variables.product.prodname_code_scanning %} +### 启用 {% 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)." +在仓库级别决定如何生成 {% data variables.product.prodname_code_scanning %} 警报，以及使用哪些工具。 {% data variables.product.product_name %} 对 {% data variables.product.prodname_codeql %} 分析提供完全集成的支持，还支持使用第三方工具进行分析。 更多信息请参阅“[关于 {% 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 +### 使用操作启用 {% data variables.product.prodname_code_scanning %} -{% 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" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. 更多信息请参阅“[关于 {% 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. To the right of "Code scanning", click **Set up code scanning**. !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Under "Get started with 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 code scanning" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) +5. Optionally, to customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." 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. - 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**. + 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。” +6. 使用 **Start commit（开始提交）**下拉菜单，并键入提交消息。 ![开始提交](/assets/images/help/repository/start-commit-commit-new-file.png) +7. 选择您是想直接提交到默认分支，还是创建新分支并启动拉取请求。 ![选择提交位置](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. 单击 **Commit new file（提交新文件）**或 **Propose new file（提议新文件）**。 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. -### Viewing the logging output from {% 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)." -After enabling {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. +After you enable {% data variables.product.prodname_code_scanning %}, you can monitor analysis, view results, and further customize how you scan your code. {% data reusables.repositories.actions-tab %} - You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. + You can view the run status of {% data variables.product.prodname_code_scanning %} and get notifications for completed runs. For more information, see "[Managing a workflow run](/actions/configuring-and-managing-workflows/managing-a-workflow-run)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." - ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) + ![After you commit the workflow file or create a pull request, {% data variables.product.prodname_code_scanning %} will analyze your code according to the frequency you specified in your workflow file. If you created a pull request, {% data variables.product.prodname_code_scanning %} will only analyze the code on the pull request's topic branch until you merge the pull request into the default branch of the repository.](/assets/images/help/repository/code-scanning-actions-list.png) 1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. @@ -62,7 +58,7 @@ After enabling {% data variables.product.prodname_code_scanning %} for your repo 1. Review the logging output from the actions in this workflow as they run. -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. 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-the-alerts-for-a-repository)." {% note %} @@ -78,7 +74,7 @@ Each {% data variables.product.prodname_code_scanning %} workflow you enable to 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. - ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) + ![After a scan completes, you can view alerts from a completed scan. For more information, see "Managing alerts from {% 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. @@ -96,7 +92,7 @@ There are other situations where there may be no analysis for the latest commit ![Choose a branch from the Branch drop-down menu](/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. + {% 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 %} * The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available. @@ -106,12 +102,12 @@ There are other situations where there may be no analysis for the latest commit 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 %}. -### Next steps +### 后续步骤 After enabling {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: -- 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 all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/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)." +- Set up notifications for completed runs. 更多信息请参阅“[配置通知](/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)." +- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。” diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 82a776fac7e1..d5464a406757 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -1,7 +1,7 @@ --- title: Managing code scanning alerts for your repository shortTitle: 管理警报 -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: 'From the security view, 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.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: @@ -30,9 +30,11 @@ By default, {% data variables.product.prodname_code_scanning %} analyzes your co 当 {% data variables.product.prodname_code_scanning %} 报告数据流警报时，{% data variables.product.prodname_dotcom %} 将显示数据在代码中如何移动。 {% data variables.product.prodname_code_scanning_capc %} 可用于识别泄露敏感信息的代码区域，以及可能成为恶意用户攻击切入点的代码区域。 -### 查看警报 +### Viewing the alerts for a repository -Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} alerts on pull requests. However, you need write permission to view a summary of alerts for repository on the **Security** tab. By default, alerts are shown for the default branch. +Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. 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)." + +You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -45,7 +47,7 @@ Anyone with read permission for a repository can see {% data variables.product.p Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[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)." -If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing an alert](#viewing-an-alert)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. +If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 610ead543388..72a38a8e45d7 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -118,7 +118,7 @@ $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 > Successfully uploaded results ``` -服务器有权直接从 {% data variables.product.prodname_dotcom_the_website %} 上{% if enterpriseServerVersions contains currentVersion %}或在 {% data variables.product.product_location %} 上镜像{% endif %}的 `github/codeql-action` 仓库下载 {% data variables.product.prodname_codeql %} 包，因此无需使用 `--codeql-path` 标志。 分析完成后， {% data variables.product.prodname_codeql_runner %} 会将结果上传到 {% data variables.product.prodname_code_scanning %} 视图。 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_dotcom_the_website %} 上{% if enterpriseServerVersions contains currentVersion %}或在 {% data variables.product.product_location %} 上镜像{% endif %}的 `github/codeql-action` 仓库下载 {% data variables.product.prodname_codeql %} 包，因此无需使用 `--codeql-path` 标志。 分析完成后， {% data variables.product.prodname_codeql_runner %} 会将结果上传到 {% data variables.product.prodname_code_scanning %} 视图。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 #### 编译语言示例 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 546a05176bc4..4b45193c672f 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -20,7 +20,7 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 如果您结合使用 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_codeql_workflow %}，或者使用 {% data variables.product.prodname_codeql_runner %}，则 {% data variables.product.prodname_code_scanning %} 结果将自动使用受支持的 SARIF 2.1.0 子集。 For more information, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)" or "[Running {% data variables.product.prodname_codeql %} {% 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)." -{% data variables.product.prodname_dotcom %} 使用 SARIF 文件中的属性来显示警报。 例如，`shortDescription` 和 `fullDescription` 出现在 {% data variables.product.prodname_code_scanning %} 警报的顶部。 `location` 允许 {% 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_dotcom %} 使用 SARIF 文件中的属性来显示警报。 例如，`shortDescription` 和 `fullDescription` 出现在 {% data variables.product.prodname_code_scanning %} 警报的顶部。 `location` 允许 {% 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)”。 如果您是 SARIF 的新用户，想了解更多信息，请参阅 Microsoft 的[`SARIF 教程`](https://github.com/microsoft/sarif-tutorials)库。 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index 33db7c6036ba..71400c1fe226 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -3,7 +3,7 @@ title: Triaging code scanning alerts in pull requests shortTitle: Triaging alerts in pull requests intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.' 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: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -31,9 +31,9 @@ When you look at the **Files changed** tab for a pull request, you see annotatio ![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png) -Some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." +If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)." -For more information about an alert, click **Show more details** on the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. +To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code. @@ -41,11 +41,11 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_ ### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request -Anyone with write permission for a repository can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on a pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. +Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. {% if currentVersion == "enterprise-server@2.22" %} -If you don't think that an alert needs to be fixed, you can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. +If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository. {% data reusables.code-scanning.false-positive-fix-codeql %} @@ -63,4 +63,4 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler For more information about dismissing alerts, 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#dismissing-or-deleting-alerts)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index 9dd5a07a9074..e3c8e6452344 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -66,7 +66,7 @@ For more information, see the workflow extract in "[Automatic build for a compil * Building using a distributed build system external to GitHub Actions, using a daemon process. * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. - For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. + For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. For example, the following configuration for C# will pass the flag during the first build step. diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 329c7194e482..3a0587753c1f 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -16,7 +16,7 @@ versions: ### 关于 {% data variables.product.prodname_code_scanning %} 的 SARIF 文件上传 -{% data variables.product.prodname_dotcom %} 使用静态分析结果交换格式 (SARIF) 文件中的信息创建 {% data variables.product.prodname_code_scanning %} 警报。 SARIF 文件可通过在用于上传文件的 {% data variables.product.prodname_actions %} 工作流程中运行的 SARIF 兼容分析工具生成。 或者，当文件生成为仓库外部的构件时， 您可以直接将 SARIF 文件推送到仓库，并使用工作流程上传 SARIF 文件。 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_dotcom %} 使用静态分析结果交换格式 (SARIF) 文件中的信息创建 {% data variables.product.prodname_code_scanning %} 警报。 SARIF 文件可通过在用于上传文件的 {% data variables.product.prodname_actions %} 工作流程中运行的 SARIF 兼容分析工具生成。 或者，当文件生成为仓库外部的构件时， 您可以直接将 SARIF 文件推送到仓库，并使用工作流程上传 SARIF 文件。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 您可以使用许多静态分析安全测试工具来生成 SARIF 文件，包括 {% data variables.product.prodname_codeql %}。 结果必须使用 SARIF 版本 2.1.0。 更多信息请参阅“[关于代码扫描的 SARIF 支持](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning)”。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md b/translations/zh-CN/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md index 7c751c4c8be5..acf9c1dff566 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md +++ b/translations/zh-CN/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md @@ -21,5 +21,5 @@ versions: 您可以查看测试版中可用的功能列表以及各功能的简短说明。 每项功能都包含一个链接，用于提供反馈。 -1. 在任何页面的右上角，单击您的个人资料照片，然后单击 **Feature preview（功能预览）**。 ![功能预览按钮](/assets/images/help/settings/feature-preview-button.png) +{% data reusables.feature-preview.feature-preview-setting %} 2. （可选）在功能右侧，单击 **Enable（启用）**或 **Disable（禁用）**。 ![在功能预览中启用按钮](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md index edaf8d7dc98f..cc48901fd2cf 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md @@ -1,6 +1,7 @@ --- title: 管理组织的密码扫描 intro: '您可以控制 {% data variables.product.product_name %} 要扫描组织中哪些仓库的密码。' +product: '{% data reusables.gated-features.secret-scanning %}' permissions: '组织所有者可以管理组织中仓库的 {% data variables.product.prodname_secret_scanning %}。' versions: free-pro-team: '*' 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 88ecf2aba74f..68114d16da1e 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 @@ -43,74 +43,77 @@ versions: ### 每个权限级别的仓库权限 -| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:| -| 从人员或团队的已分配仓库拉取 | **X** | **X** | **X** | **X** | **X** | -| 复刻人员或团队的已分配仓库 | **X** | **X** | **X** | **X** | **X** | -| 编辑和删除自己的评论 | **X** | **X** | **X** | **X** | **X** | -| 打开议题 | **X** | **X** | **X** | **X** | **X** | -| 关闭自己打开的议题 | **X** | **X** | **X** | **X** | **X** | -| 重新打开自己关闭的议题 | **X** | **X** | **X** | **X** | **X** | -| 受理议题 | **X** | **X** | **X** | **X** | **X** | -| 从团队已分配仓库的复刻发送拉取请求 | **X** | **X** | **X** | **X** | **X** | -| 提交拉取请求审查 | **X** | **X** | **X** | **X** | **X** | -| 查看已发布的版本 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 查看 [GitHub 操作工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| 编辑 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** | -| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** | -| 应用里程碑 | | **X** | **X** | **X** | **X** | -| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| 申请[拉取请求审查](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| 推送到（写入）人员或团队的已分配仓库 | | | **X** | **X** | **X** | -| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **X** | **X** | **X** | -| [隐藏任何人的评论](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [锁定对话](/articles/locking-conversations) | | | **X** | **X** | **X** | -| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **X** | **X** | **X** | -| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [将拉取请求草稿标记为可供审查](/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" %} -| [将拉取请求转换为草稿](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| 提交影响拉取请求可合并性的审查 | | | **X** | **X** | **X** | -| 对拉取请求[应用建议的更改](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| 创建[状态检查](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 创建、编辑、运行、重新运行和取消 [GitHub 操作工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| 创建和编辑发行版 | | | **X** | **X** | **X** | -| 查看发行版草稿 | | | **X** | **X** | **X** | -| 编辑仓库的说明 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [删除包](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| 启用 wiki 和限制 wiki 编辑器 | | | | **X** | **X** | -| 启用项目板 | | | | **X** | **X** | -| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [推送到受保护分支](/articles/about-protected-branches) | | | | **X** | **X** | -| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 限制[仓库中的交互](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} -| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | -| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** | -| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | -| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **X** | -| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **X** | -| 更改仓库设置 | | | | | **X** | -| 管理团队和协作者对仓库的权限 | | | | | **X** | -| 编辑仓库的默认分支 | | | | | **X** | -| 管理 web 挂钩和部署密钥 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 为私有仓库[启用依赖关系图](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | -| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | | | | | **X** | -| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [指定其他人员或团队接收易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) | | | | | **X** | -| [管理私有仓库的数据使用设置](/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" %}| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %} -| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [存档仓库](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **X** |{% endif %} -| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** | +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-----:|:-----:|:-----:|:-----:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 从人员或团队的已分配仓库拉取 | **X** | **X** | **X** | **X** | **X** | +| 复刻人员或团队的已分配仓库 | **X** | **X** | **X** | **X** | **X** | +| 编辑和删除自己的评论 | **X** | **X** | **X** | **X** | **X** | +| 打开议题 | **X** | **X** | **X** | **X** | **X** | +| 关闭自己打开的议题 | **X** | **X** | **X** | **X** | **X** | +| 重新打开自己关闭的议题 | **X** | **X** | **X** | **X** | **X** | +| 受理议题 | **X** | **X** | **X** | **X** | **X** | +| 从团队已分配仓库的复刻发送拉取请求 | **X** | **X** | **X** | **X** | **X** | +| 提交拉取请求审查 | **X** | **X** | **X** | **X** | **X** | +| 查看已发布的版本 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 查看 [GitHub 操作工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 编辑 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** | +| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** | +| 应用里程碑 | | **X** | **X** | **X** | **X** | +| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| 申请[拉取请求审查](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| 推送到（写入）人员或团队的已分配仓库 | | | **X** | **X** | **X** | +| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **X** | **X** | **X** | +| [隐藏任何人的评论](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [锁定对话](/articles/locking-conversations) | | | **X** | **X** | **X** | +| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **X** | **X** | **X** | +| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [将拉取请求草稿标记为可供审查](/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" %} +| [将拉取请求转换为草稿](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| 提交影响拉取请求可合并性的审查 | | | **X** | **X** | **X** | +| 对拉取请求[应用建议的更改](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | +| 创建[状态检查](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 创建、编辑、运行、重新运行和取消 [GitHub 操作工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| 创建和编辑发行版 | | | **X** | **X** | **X** | +| 查看发行版草稿 | | | **X** | **X** | **X** | +| 编辑仓库的说明 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [删除包](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| 启用 wiki 和限制 wiki 编辑器 | | | | **X** | **X** | +| 启用项目板 | | | | **X** | **X** | +| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [推送到受保护分支](/articles/about-protected-branches) | | | | **X** | **X** | +| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 限制[仓库中的交互](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} +| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | +| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** | +| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | +| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **X** | +| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **X** | +| 更改仓库设置 | | | | | **X** | +| 管理团队和协作者对仓库的权限 | | | | | **X** | +| 编辑仓库的默认分支 | | | | | **X** | +| 管理 web 挂钩和部署密钥 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 为私有仓库[启用依赖关系图](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | +| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | | | | | **X** | +| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [指定其他人员或团队接收易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) | | | | | **X** | +| [管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | +| 创建[安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %} +| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [存档仓库](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **X** |{% endif %} +| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** | ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 61497be9a9dd..12d028716278 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/zh-CN/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: - -{% 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) +#### Search based on time of action + +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 %} -##### The `account` category +**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" %} + +#### `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,7 +393,7 @@ 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 |------------------|------------------- @@ -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 +|------------------|------------------- +| `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-dependabot-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 |------------------|------------------- -| `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 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/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index ba1220c24a5e..c6f135ef0a87 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -3,6 +3,7 @@ title: Managing licenses for Visual Studio subscription with GitHub Enterprise intro: 'You can manage {% data variables.product.prodname_enterprise %} licensing for {% 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 diff --git a/translations/zh-CN/content/github/site-policy/github-acceptable-use-policies.md b/translations/zh-CN/content/github/site-policy/github-acceptable-use-policies.md index d27bc7ff6591..f7fb9cf454c1 100644 --- a/translations/zh-CN/content/github/site-policy/github-acceptable-use-policies.md +++ b/translations/zh-CN/content/github/site-policy/github-acceptable-use-policies.md @@ -37,6 +37,8 @@ versions: - 骚扰、辱骂、威胁或煽动暴力对待任何个人或团体，包括我们的员工、高管和代理或其他用户； +- post off-topic content, or interact with platform features, in a way that significantly or repeatedly disrupts the experience of other users; + - 将我们的服务器用于任何形式的过度自动化批量活动（如发送垃圾邮件或加密货币挖矿），通过自动化方式对我们的服务器施加不当的负担，或者通过我们的服务器转发任何其他形式的主动广告或招揽，如快速致富方案； - 使用我们的服务器破坏或试图破坏、非授权访问或试图非授权访问任何服务、设备、数据、帐户或网络（[GitHub 漏洞赏金计划](https://bounty.github.com)授权的活动除外）； @@ -48,15 +50,17 @@ versions: ### 4. 服务使用限制 未获明确的书面同意，不得重制、重复、复制、销售、转售或利用服务的任何部分、使用服务或访问服务。 -### 5. 擦除和 API 使用限制 -擦除是指通过自动化过程（如自动程序或网络爬虫 ）从我们的服务中提取数据。 它不是指通过我们的 API 收集信息。 有关我们的 API 条款，请参阅我们[服务条款](/articles/github-terms-of-service#h-api-terms)的 H 部分。 您可能因以下原因而擦除网站： +### 5. Information Usage Restrictions +You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise: + +- Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are [open access](https://en.wikipedia.org/wiki/Open_access). +- Archivists may use public information from the Service for archival purposes. -- 研究人员可能出于研究目的而从服务中擦除公共的非个人信息，但仅当来自该研究的出版物开放访问时才可擦除。 -- 档案管理人员可能出于存档目的而擦除服务中的公共数据。 +Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler. Scraping does not refer to the collection of information through our API. 有关我们的 API 条款，请参阅我们[服务条款](/articles/github-terms-of-service#h-api-terms)的 H 部分。 -不得出于发送垃圾邮件的目的而擦除服务，包括出于销售用户个人信息的目的（根据 [GitHub 隐私声明](/articles/github-privacy-statement)中的定义），例如招聘人员、猎头和工作板。 +You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling User Personal Information (as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement)), such as to recruiters, headhunters, and job boards. -通过擦除收集的数据的所有使用必须遵守 [GitHub 隐私声明](/articles/github-privacy-statement)。 +Your use of information from the Service must comply with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). ### 6. 隐私 禁止滥用用户个人信息。 diff --git a/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md b/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md index 4a800ce47ab5..316e412caef5 100644 --- a/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md +++ b/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -版本生效日期：2020 年 11 月 1 日 +版本生效日期：2020 年 11 月 13 日 创建帐户后，您有权访问许多不同的功能和产品，它们都是服务的一部分。 由于其中许多功能和产品具有不同的功能，因此可能需要特定于该功能或产品的附加条款和条件。 Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -89,7 +89,7 @@ In order to access GitHub Connect, Customer must have at least one (1) Account o ### 9. GitHub Advanced Security -GitHub Advanced Security 帮助您通过可自定义的自动化语义学代码分析来识别安全漏洞。 GitHub Advanced Security 逐用户许可。 如果您将 GitHub Advanced Security 用作 GitHub Enterprise Cloud 的一部分，GitHub Advanced Security 的许多功能（包括对私有仓库的自动化代码扫描）还需要使用 GitHub 操作。 对 GitHub 操作使用情况的计费以使用为基础，必须遵守 [GitHub 操作条款](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages)。 +GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. 如果您将 GitHub Advanced Security 用作 GitHub Enterprise Cloud 的一部分，GitHub Advanced Security 的许多功能（包括对私有仓库的自动化代码扫描）还需要使用 GitHub 操作。 ### 10. Dependabot Preview @@ -108,4 +108,3 @@ GitHub Advanced Security 帮助您通过可自定义的自动化语义学代码 #### b. GitHub Advisory Database 的许可 GitHub Advisory Database 的许可采用[知识共享署名 4.0 许可](https://creativecommons.org/licenses/by/4.0/)原则。 有关署名条款，请参阅 上的 GitHub Advisory Database，或者所使用的单独 GitHub Advisory Database 记录（以 为前缀）。 - diff --git a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md index fa42615684ae..0627e1c1ceb6 100644 --- a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md +++ b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md @@ -11,7 +11,7 @@ versions: GitHub 的用户来自世界各地，有上周才创建其第一个 "Hello World" 项目的新人，也有享誉全球的软件开发高手，他们带来了各种不同的观点、想法和经验。 我们致力于让 GitHub 成为一个海纳百川的环境，接纳各种不同的声音和观点，打造一个所有人都能畅所欲言的空间。 -我们依靠社区成员传达期望、[仲裁](#what-if-something-or-someone-offends-you)他们的项目以及{% data variables.contact.report_abuse %}或{% data variables.contact.report_content %}。 我们不主动寻求仲裁内容。 通过概述我们期望社区内出现的情况，我们希望帮助您理解如何在 GitHub 上进行最佳的协作，以及哪种操作或内容可能违反我们的[服务条款](#legal-notices)。 我们将调查任何滥用举报，并且可能在我们的网站上仲裁我们确定违反了 GitHub 服务条款的公共内容。 +我们依靠社区成员传达期望、[仲裁](#what-if-something-or-someone-offends-you)他们的项目以及{% data variables.contact.report_abuse %}或{% data variables.contact.report_content %}。 By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). 我们将调查任何滥用举报，并且可能在我们的网站上仲裁我们确定违反了 GitHub 服务条款的公共内容。 ### 建立强大的社区 @@ -47,23 +47,25 @@ GitHub 社区的主要目的是协作处理软件项目。 我们希望人们能 我们致力于维持一个用户能够自由表达意见并对彼此想法（包括技术和其他方面）提出挑战的社区。 但当思想被压制时，这种讨论不可能促进富有成果的对话，因为因为社区成员被禁声或害怕说出来。 因此，您应该始终尊重他人，言行文明，不要对他人有任何人身攻击以谁为由攻击他人。 我们不容忍以下越界行为： -* **暴力威胁** - 不得暴力威胁他人，也不得利用网站组织、宣传或煽动现实世界中的暴力或恐怖主义行为。 仔细考虑您使用的文字、发布的图像、编写的软件以及其他人会如何解读它们。 即使您只是开个玩笑，但别人不见得这样理解。 如果您认为别人*可能*会将您发布的内容解读为威胁或者煽动暴力或恐怖主义， 不要在 GitHub 上发布。 在非常情况下， 如果我们认为可能存在真正的人身伤害风险或公共安全威胁，我们可能会向执法机构报告暴力威胁。 +- #### Threats of violence You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. 仔细考虑您使用的文字、发布的图像、编写的软件以及其他人会如何解读它们。 即使您只是开个玩笑，但别人不见得这样理解。 如果您认为别人*可能*会将您发布的内容解读为威胁或者煽动暴力或恐怖主义， 不要在 GitHub 上发布。 在非常情况下， 如果我们认为可能存在真正的人身伤害风险或公共安全威胁，我们可能会向执法机构报告暴力威胁。 -* **仇恨言论和歧视** - 虽然不禁止谈论年龄、身材、能力、种族、性别认同和表达、经验水平、国籍、外貌、民族、宗教或性认同和性取向等话题，但我们不允许基于身份特征攻击任何个人或群体。 只要认识到以一种侵略性或侮辱性的方式处理这些（及其他）敏感的专题，就可能使其他人感到不受欢迎甚至不安全。 虽然总是存在误解的可能性，但我们期望社区成员在讨论敏感问题时保持尊重和平静。 +- #### Hate speech and discrimination While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. 只要认识到以一种侵略性或侮辱性的方式处理这些（及其他）敏感的专题，就可能使其他人感到不受欢迎甚至不安全。 虽然总是存在误解的可能性，但我们期望社区成员在讨论敏感问题时保持尊重和平静。 -* **欺凌和骚扰** - 我们不容忍欺凌或骚扰。 这意味着我们不允许针对任何特定个人或群体的典型骚扰或恐吓行为。 一般来说，如果您屡次三番采取多余的行动，就很可能走进了欺凌或骚扰的歧途。 +- #### Bullying and harassment We do not tolerate bullying or harassment. 这意味着我们不允许针对任何特定个人或群体的典型骚扰或恐吓行为。 一般来说，如果您屡次三番采取多余的行动，就很可能走进了欺凌或骚扰的歧途。 -* **冒充** - 不得通过复制他人头像、在他人的电子邮件地址下发布内容、使用类似的用户名或以他人身份发帖等方式来误传您的身份。 冒充是骚扰的一种形式。 +- #### Disrupting the experience of other users Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on. Behaviors such as repeatedly posting off-topic comments, opening empty or meaningless issues or pull requests, or using any other platform feature in a way that continually disrupts the experience of other users are not allowed. While we encourage maintainers to moderate their own projects on an individual basis, GitHub staff may take further restrictive action against accounts that are engaging in these types of behaviors. -* **人肉和侵犯隐私** - 不得发布他人的个人信息，例如电话号码、私人电子邮件地址、实际地址、信用卡号码、社会保障/国民身份号码或密码。 根据具体情况，例如在恐吓或骚扰的情况下，我们可能会认为发布他人信息（例如未经当事人同意而拍摄或散发的照片或视频）是侵犯隐私的行为，特别是当此类材料会给当事人带来安全风险时。 +- #### Impersonation You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. 冒充是骚扰的一种形式。 -* **性淫秽内容** - 不得发布色情内容。 但这并不意味着禁止一切裸体或与性有关的所有代码和内容。 我们认识到，性行为是生活的一部分，非色情的性内容可能是您项目的一部分，或者出于教育或艺术目的而呈现。 我们不允许淫秽性内容或可能涉及利用或性化未成年人的内容。 +- #### Doxxing and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. 根据具体情况，例如在恐吓或骚扰的情况下，我们可能会认为发布他人信息（例如未经当事人同意而拍摄或散发的照片或视频）是侵犯隐私的行为，特别是当此类材料会给当事人带来安全风险时。 -* **过激的暴力内容** - 不得在没有合理的上下文或警告的情况下发布暴力图像、文本或其他内容。 在视频游戏、新闻报道以及对历史事件的描述中通常可以包含暴力内容，但我们不允许不加选择地发布暴力内容，或者以其他用户很难避开的方式发布（例如头像或议题评论）。 在其他情况下发布明确警告或免责声明有助于用户就他们是否想要参与这类内容作出明智的决定。 +- #### Sexually obscene content Don’t post content that is pornographic. 但这并不意味着禁止一切裸体或与性有关的所有代码和内容。 我们认识到，性行为是生活的一部分，非色情的性内容可能是您项目的一部分，或者出于教育或艺术目的而呈现。 我们不允许淫秽性内容或可能涉及利用或性化未成年人的内容。 -* **错误信息和虚假信息** - 不得发布歪曲现实的内容，包括不准确或虚假的信息（错误信息），或者故意欺骗的信息（假信息），因为这种内容可能伤害公众，或者干扰所有人公平和平等参与公共生活的机会。 例如，我们不允许可能危及群体福祉或限制他们参与自由和开放社会的内容。 鼓励积极参与表达想法、观点和经验，不得质疑个人帐户或言论。 我们通常允许模仿和讽刺，但要符合我们的“可接受使用政策”，而且我们认为上下文对于如何接收和理解信息很重要；因此，通过免责声明或其他方式澄清您的意图以及您的信息的来源，可能是适当的做法。 +- #### Gratuitously violent content Don’t post violent images, text, or other content without reasonable context or warnings. 在视频游戏、新闻报道以及对历史事件的描述中通常可以包含暴力内容，但我们不允许不加选择地发布暴力内容，或者以其他用户很难避开的方式发布（例如头像或议题评论）。 在其他情况下发布明确警告或免责声明有助于用户就他们是否想要参与这类内容作出明智的决定。 -* **主动恶意软件或漏洞利用程序** - 本社区不允许恶意利用社区的其他成员。 我们不允许任何人利用我们的平台传递漏洞利用程序（例如，利用 GitHub 传递恶意的可执行文件）或攻击基础设施（例如，组织拒绝服务攻击或支配命令和控制服务器）。 但请注意，我们不禁止发布可用于开发恶意软件或漏洞利用程序的源代码，因为此类源代码的发布和分发具有教育价值，并且能够为安全社区带来净收益。 +- #### Misinformation and disinformation You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. 例如，我们不允许可能危及群体福祉或限制他们参与自由和开放社会的内容。 鼓励积极参与表达想法、观点和经验，不得质疑个人帐户或言论。 我们通常允许模仿和讽刺，但要符合我们的“可接受使用政策”，而且我们认为上下文对于如何接收和理解信息很重要；因此，通过免责声明或其他方式澄清您的意图以及您的信息的来源，可能是适当的做法。 + +- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. 我们不允许任何人利用我们的平台传递漏洞利用程序（例如，利用 GitHub 传递恶意的可执行文件）或攻击基础设施（例如，组织拒绝服务攻击或支配命令和控制服务器）。 但请注意，我们不禁止发布可用于开发恶意软件或漏洞利用程序的源代码，因为此类源代码的发布和分发具有教育价值，并且能够为安全社区带来净收益。 ### 如果有人违反规则会怎么样？ diff --git a/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md b/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md index c4d6f270ced9..a616081ce70b 100644 --- a/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md @@ -9,7 +9,7 @@ versions: 感谢您选择 GitHub 满足贵公司的业务需求。 请仔细阅读本协议，因为它管辖对产品（定义如下）的使用，除非 GITHUB 在这方面与客户签订了单独的书面协议。 单击“I AGREE（我同意）”或类似按钮或者使用产品，即表示客户接受本协议的所有条款和条件。 如果客户代表公司或其他法律实体签订本协议，则表示其拥有让该公司或其他法律实体受本协议约束的法律权限。 ### GitHub 公司服务条款 -版本生效日期：2020 年 7 月 20 日 +Version Effective Date: November 16, 2020 本协议适用于以下 GitHub 产品（详细定义见下文，统称为**“产品”**）： - 服务； @@ -133,13 +133,13 @@ GitHub 在[企业服务等级协议](/github/site-policy/github-enterprise-servi 客户保留客户创建或拥有的客户内容的所有权。 客户承认：(a) 对客户内容负责，(b) 只会提供客户有权利发布的客户内容（包括第三方或用户生成的内容），以及 (c) 客户将完全遵守与客户发布的客户内容相关的任何第三方许可。 客户免费授予第 D.3 至 D.6 条所述的权利，用于这两条所述的目的，直到客户从 GitHub 服务器中删除客户内容，但公开发布以及外部用户已经复刻的内容除外，这些内容的有效期直到所有客户内容复刻从 GitHub 服务器中删除。 如果客户上传的客户内容具有已经向 GitHub 授予运行服务所需的许可，则无需其他许可。 #### 3. 向我们授予许可 -客户向 GitHub 授予存储、剖析和显示客户内容的权利，并仅在提供服务需要时才创建偶尔的副本。 这些权利包括将客户内容复制到 GitHub 数据库和制作备份；向客户以及客户选择要向其显示内容的人员显示客户内容；将客户内容剖析为搜索索引或在 GitHub 的服务器上分析；与客户选择要共享的外部用户共享客户内容；以及执行客户内容，有点像音乐或视频一样。 这些权利适用于公共和私有仓库。 此许可并未向 GitHub 授予销售客户内容或者在服务外部分发或使用内容的权利。 客户向 GitHub 授予以无归属方式使用客户内容所需的权利，以及根据提供服务的需要对客户内容进行合理改编的权利。 +Customer grants to GitHub the right to store, archive, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service, including improving the Service over time. This license includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. 这些权利适用于公共和私有仓库。 This license does not grant GitHub the right to sell Customer Content. It also does not grant GitHub the right to otherwise distribute or use Customer Content outside of our provision of the Service, except that as part of the right to archive Customer Content, GitHub may permit our partners to store and archive Customer Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. 客户向 GitHub 授予以无归属方式使用客户内容所需的权利，以及根据提供服务的需要对客户内容进行合理改编的权利。 #### 4. 向外部用户授予的许可 客户快速发布的任何内容，包括议题、评论以及对外部用户仓库的贡献，都可供其他人查看。 只要将其仓库设置为公开显示，即表示客户同意允许外部用户查看客户的仓库以及对其复刻。 如果客户将其页面和仓库设为公开显示，客户向外部用户授予非独占、全球许可，允许他们通过服务使用、显示和执行客户内容，以及通过 GitHub 提供的功能（例如通过复刻）只在服务上重制允许的客户内容。 如果客户采用许可，客户可授予客户内容更多的权利。 如果客户上传其未创建或拥有的客户内容，则客户负责确保其上传的客户内容根据向外部用户授予这些许可的条款进行许可。 #### 5. 仓库许可下的参与。 -只要客户参与包含许可通告的仓库，则表示客户在相同的条款下许可该等参与，并且同意其有权利在这些条款下许可该等参与。 如果客户使用单独的协议在不同的条款下许可其参与，如参与者许可协议，则该协议优先。 +Whenever Customer adds Content to a repository containing notice of a license, it licenses that Content under the same terms and agrees that it has the right to license that Content under those terms. If Customer has a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. #### 6. 精神权利 客户对其上传、发布或提交到服务任何部分的客户内容保留所有精神权利，包括完整性和归属的权利。 但客户对 GitHub 放弃这些权利并且同意不宣称这些权利，唯一目的是让 GitHub 合理行使第 D 条中宣称的权利，而没有任何其他目的。 @@ -153,10 +153,13 @@ GitHub 在[企业服务等级协议](/github/site-policy/github-enterprise-servi GitHub 将客户私有仓库中的客户内容视为客户的机密信息。 GitHub 将根据本第 P 条对私有仓库的客户内容实施保护和严格保密。 #### 3. 访问 -GitHub 人员只能在以下情况下访问客户的私有仓库 (i) 出于支持原因，经客户同意并确认，或者 (ii) 出于安全原因而需要访问时。 客户可选择对其私有仓库启用其他访问权限。 例如，客户可向不同的 GitHub 服务或功能授予对私有仓库中客户内容的额外访问权限。 这些权利可能根据服务或功能而不同，但 GitHub 仍会将客户私有仓库中的客户内容视为客户的机密信息。 如果这些服务或功能除了提供服务所需的权限之前，还需要其他权限，GitHub 将会说明这些权限。 +GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 4. 排除 -如果 GitHub 有理由相信私有仓库的内容违反法律或本协议，则 GitHub 有权利访问、检查和删除该内容。 此外，GitHub 可能[按法律要求](/github/site-policy/github-privacy-statement#for-legal-disclosure)披露客户私有仓库的内容。 除非法律要求另有约束或者是回应安全威胁或其他安全风险，否则 GitHub 对此类操作需发出通知。 +客户可选择对其私有仓库启用其他访问权限。 例如，客户可向不同的 GitHub 服务或功能授予对私有仓库中客户内容的额外访问权限。 这些权利可能根据服务或功能而不同，但 GitHub 仍会将客户私有仓库中的客户内容视为客户的机密信息。 如果这些服务或功能除了提供服务所需的权限之前，还需要其他权限，GitHub 将会说明这些权限。 + +此外，我们可能[按法律要求](/github/site-policy/github-privacy-statement#for-legal-disclosure)披露您的私有仓库的内容。 + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. 知识产权通告 @@ -270,12 +273,12 @@ _测试版预览。_客户可自行决定选择使用测试版预览。 测试 在客户申请专业服务后，GitHub 将提供详述该等专业服务的 SOW。 GitHub 将执行每个 SOW 中描述的专业服务。 GitHub 将控制专业服务执行的方式和途径，并保留确定分配人员的权利。 GitHub 可能使用第三方执行专业服务，但 GitHub 对他们的行为和疏漏负责。 客户承认并同意，GitHub 保留在执行专业服务时使用或开发的任何内容的权利、资格和利益，包括软件、工具、规格、想法、概念、发明、流程、技术和知识。 对于 GitHub 在履行专业服务时向客户提供的任何交付项，GitHub 授予客户非独占、不可转让、全球、免版税、有限期的许可，允许他们在本协议有效期内使用这些交付项，但只能用于与客户使用服务相关的用途。 ### R. 服务或条款的更改 -GitHub 有权利独自裁量随时修订本协议，并在发生任何此类修正时更新本协议。 本协议如有重大更改，如价格变动，GitHub 将至少在更改生效前 30 天在服务上发布通知，向客户通知本协议的重大变更。 对于非重大修改，客户继续使用服务即表示同意我们对本协议的修订。 客户在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看本协议的所有更改。 +GitHub 有权利独自裁量随时修订本协议，并在发生任何此类修正时更新本协议。 GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. 客户在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看本协议的所有更改。 GitHub 通过更新和添加新功能来更改服务。 对于 GitHub 在履行专业服务时向客户提供的任何交付项，GitHub 授予客户非独占、不可转让、全球、免版税、有限期的许可，允许他们在本协议有效期内使用这些交付项，但只能用于与客户使用服务相关的用途。 ### S. 支持 -GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对服务提供标准技术支持，不收取额外费用。 GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对软件提供标准技术支持，不收取额外费用。 标准支持只通过 GitHub 以基于 web 的支持单提供，支持请求必须从 GitHub 支持团队可与之交互的用户发起。 GitHub 按订单或 SOW 规定的支持级别、费用和订阅期为服务提供高级支持（根据 [GitHub 对 Enterprise Cloud 的高级支持](/articles/about-github-premium-support)条款）或专门的技术支持。 +GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对服务提供标准技术支持，不收取额外费用。 GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对软件提供标准技术支持，不收取额外费用。 标准支持只通过 GitHub 以基于 web 的支持单提供，支持请求必须从 GitHub 支持团队可与之交互的用户发起。 GitHub may provide premium Support (subject to the [GitHub Premium Support for Enterprise Cloud](/articles/about-github-premium-support) terms) or dedicated technical Support for the Service at the Support level, Fees, and Subscription Term specified in an Order Form or SOW. ### T. 其他 @@ -307,4 +310,4 @@ GitHub 如果因其合理控制力之外的特殊原因（包括天灾、自然 每一方都是关于本协议主题的独立缔约方。 本协议中的任何内容都不得视为或以任何方式构成在双方之间建立法律关联、伙伴关系、合资企业、雇用、代理、信托或其他类似关系，任一方不得以合同来约束另一方。 #### 10. 问题 -对服务条款有疑问吗？ [请联系我们](https://github.com/contact/)。 +对服务条款有疑问吗？ [Contact us](https://github.com/contact/). diff --git a/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md index 9a5b8b10baca..1a7b518dddb7 100644 --- a/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -26,6 +26,6 @@ versions: 正常运行时间计算不包括因以下原因导致的服务功能故障：(i) 客户的行为、疏忽或滥用服务，包括违反协议；(ii) 客户的网络连接故障；(iii) 超出 GitHub 合理控制范围的因素，包括不可抗力事件；或 (iv) 客户的设备、服务或其他技术。 ## 服务积分兑换 -如果 GitHub 不符合此 SLA，则客户必须在该日历季度结束后的三十 (30) 天内向 GitHub 提出书面申请才能兑换服务积分。 服务积分兑换的书面申请应发送到 [GitHub 支持部门](https://support.github.com/contact)。 +如果 GitHub 不符合此 SLA，则客户必须在该日历季度结束后的三十 (30) 天内向 GitHub 提出书面申请才能兑换服务积分。 Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). 服务积分可以采取退款或贷记给客户帐户的形式，不能兑换为现金，每个日历季度的上限为九十 (90) 天的付费服务，要求客户已支付任何未结发票， 并在客户与 GitHub 的协议终止后过期。 服务积分是针对 GitHub 未能履行此 SLA 中任何义务的唯一和排他性补救措施。 diff --git a/translations/zh-CN/content/github/site-policy/github-enterprise-subscription-agreement.md b/translations/zh-CN/content/github/site-policy/github-enterprise-subscription-agreement.md index 8b3757cc8ed6..8fe8c2283a09 100644 --- a/translations/zh-CN/content/github/site-policy/github-enterprise-subscription-agreement.md +++ b/translations/zh-CN/content/github/site-policy/github-enterprise-subscription-agreement.md @@ -7,7 +7,7 @@ versions: free-pro-team: '*' --- -版本生效日期：2020 年 7 月 20 日 +Version Effective Date: November 16, 2020 只要单击“我同意”或类似按钮或者使用任何产品（定义如下），即表示客户接受本协议的条款和条件。 如果客户代表法人实体签订本协议，则客户表示其拥有确保该法人实体受本协议约束的法律权限。 @@ -197,7 +197,7 @@ GitHub 如果因其合理控制力之外的特殊原因（包括天灾、自然 #### 1.13.11 修正；偏好顺序。 -GitHub 有权利独自裁量随时修订本协议，并在发生任何此类修正时更新本协议。 本协议如有重大更改，如价格变动，GitHub 将至少在更改生效前 30 天在服务上发布通知，向客户通知本协议的重大变更。 对于非重大修改，客户继续使用服务即表示同意我们对本协议的修订。 客户在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看本协议的所有更改。 如果本协议条款与任何订单或 SOW 有任何冲突，则订单或 SOW 的条款只管制该订单或 SOW。 +GitHub 有权利独自裁量随时修订本协议，并在发生任何此类修正时更新本协议。 GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. 客户在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看本协议的所有更改。 如果本协议条款与任何订单或 SOW 有任何冲突，则订单或 SOW 的条款只管制该订单或 SOW。 #### 1.13.12 可分割性。 @@ -296,7 +296,7 @@ GitHub 将在客户下载软件和许可密钥的安全网站上提供软件的 **(ii)** 客户免费授予第 3.3.3 至 3.3.6 条所述的权利，用于这两条所述的目的，直到客户从 GitHub 服务器中删除客户内容，但公开发布以及外部用户已经复刻的内容除外，这些内容的有效期直到所有客户内容复刻从 GitHub 服务器中删除。 如果客户上传的客户内容具有已经向 GitHub 授予运行服务所需的许可，则无需其他许可。 #### 3.3.3 向 GitHub 授予的许可。 -客户向 GitHub 授予存储、剖析和显示客户内容的权利，并仅在提供服务需要时才创建偶尔的副本。 这些权利包括将客户内容复制到 GitHub 数据库和制作备份；向客户以及客户选择要向其显示内容的人员显示客户内容；将客户内容剖析为搜索索引或在 GitHub 的服务器上分析；与客户选择要共享的外部用户共享客户内容；以及执行客户内容，有点像音乐或视频一样。 这些权利适用于公共和私有仓库。 此许可并未向 GitHub 授予销售客户内容或者在服务外部分发或使用内容的权利。 客户向 GitHub 授予以无归属方式使用客户内容所需的权利，以及根据提供服务的需要对客户内容进行合理改编的权利。 +Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service. 这些权利包括将客户内容复制到 GitHub 数据库和制作备份；向客户以及客户选择要向其显示内容的人员显示客户内容；将客户内容剖析为搜索索引或在 GitHub 的服务器上分析；与客户选择要共享的外部用户共享客户内容；以及执行客户内容，有点像音乐或视频一样。 这些权利适用于公共和私有仓库。 此许可并未向 GitHub 授予销售客户内容或者在服务外部分发或使用内容的权利。 客户向 GitHub 授予以无归属方式使用客户内容所需的权利，以及根据提供服务的需要对客户内容进行合理改编的权利。 #### 3.3.4 向外部用户授予的许可。 **(i)** 客户快速发布的任何内容，包括议题、评论以及对外部用户仓库的贡献，都可供其他人查看。 只要将其仓库设置为公开显示，即表示客户同意允许外部用户查看客户的仓库以及对其复刻。 @@ -318,10 +318,13 @@ GitHub 将在客户下载软件和许可密钥的安全网站上提供软件的 GitHub 将客户私有仓库中的客户内容视为客户的机密信息。 GitHub 将根据本第 1.4 条对私有仓库的客户内容实施保护和严格保密。 #### 3.4.3 访问。 -GitHub 只能在以下情况下访问客户的私有仓库 (i) 经客户同意并确认，出于支持原因，或者 (ii) 出于安全原因而需要访问时。 客户可选择对其私有仓库启用其他访问权限。 例如，客户可向不同的 GitHub 服务或功能授予对私有仓库中客户内容的额外访问权限。 这些权利可能根据服务或功能而不同，但 GitHub 仍会将客户私有仓库中的客户内容视为客户的机密信息。 如果这些服务或功能除了提供服务所需的权限之前，还需要其他权限，GitHub 将会说明这些权限。 +GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -#### 3.4.4 除外条款。 -如果 GitHub 有理由相信私有仓库的内容违反法律或本协议，则 GitHub 有权利访问、检查和删除该内容。 此外，法律可能要求 GitHub 披露客户私有仓库中的内容。 除非法律要求另有约束或者是回应安全威胁或其他安全风险，否则 GitHub 对此类操作需发出通知。 +客户可选择对其私有仓库启用其他访问权限。 例如，客户可向不同的 GitHub 服务或功能授予对私有仓库中客户内容的额外访问权限。 这些权利可能根据服务或功能而不同，但 GitHub 仍会将客户私有仓库中的客户内容视为客户的机密信息。 如果这些服务或功能除了提供服务所需的权限之前，还需要其他权限，GitHub 将会说明这些权限。 + +此外，我们可能[按法律要求](/github/site-policy/github-privacy-statement#for-legal-disclosure)披露您的私有仓库的内容。 + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 3.5. 知识产权通告。 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 8bfaddc2248f..2546db1601e0 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 @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Effective date: July 22, 2020 +生效日期：2020 年 11 月 16 日 感谢您将自己的源代码、项目和个人信息交托给 GitHub Inc. （“GitHub”、“我们”）。 保管您的私人信息是一项重大责任，我们希望您了解我们的处理方式。 @@ -150,23 +150,39 @@ GitHub 可能会从第三方收集用户个人信息。 例如，如果您报名 请注意：《2018 年加州消费者隐私法案》(“CCPA”) 要求企业在其隐私政策中声明，他们是否会披露个人信息以换取金钱或其他有价值的报酬。 虽然 CCPA 只涵盖加州居民，但我们自愿将人们控制自己的数据之核心权利扩展到我们的_所有_用户，而不仅仅是居住在加州的用户。 您可以在[此处](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act)了解有关 CCPA 以及我们如何遵守它的更多信息。 -### 其他重要信息 +### 仓库内容 + +#### Access to private repositories + +If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for +- security purposes +- to assist the repository owner with a support matter +- to maintain the integrity of the Service +- to comply with our legal obligations +- if we have reason to believe the contents are in violation of the law, or +- 经您同意. + +However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories). -#### 仓库内容 +Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts). -GitHub 人员[不会访问私有仓库，除非](/github/site-policy/github-terms-of-service#e-private-repositories)出于安全原因，或者为了协助仓库所有者解决支持问题、保持服务的完整性或履行我们的法律义务而需要这样做。 不过，虽然我们一般不搜索您的仓库中的内容，但可能扫描我们的服务器和内容，以根据算法指纹技术检测某些令牌或安全签名、已知活动的恶意软件或其他已知违反我们条款的内容，例如暴力极端主义或恐怖主义内容或儿童剥削图片。 我们的服务条款提供了[更多详细信息](/github/site-policy/github-terms-of-service#e-private-repositories)。 +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. -如果您的仓库是公共仓库，则任何人都可以查看其内容。 如果您的公共仓库中含有私人、机密或[敏感个人信息](https://gdpr-info.eu/art-9-gdpr/)，例如电子邮件地址或密码，则该信息可能会被搜索引擎索引或被第三方使用。 +#### Public repositories + +如果您的仓库是公共仓库，则任何人都可以查看其内容。 If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties. 更多信息请参阅[公共仓库中的用户个人信息](/github/site-policy/github-privacy-statement#public-information-on-github)。 +### 其他重要信息 + #### GitHub 上的公共信息 GitHub 的许多服务和功能都是面向公众的。 如果您的内容是面向公众的，则第三方可能会按照我们的服务条款访问和使用它，例如查看您的个人资料或仓库，或者通过我们的 API 拉取数据。 我们不会出售您的内容；它是您的财产。 但是，我们会允许第三方（例如研究或存档组织）汇编面向公众的 GitHub 信息。 据悉，数据中间商等其他第三方也会搜刮 GitHub 和汇编数据。 与您的内容相关的用户个人信息可能被第三方收集在这些 GitHub 数据汇编中。 如果您不希望自己的用户个人信息出现在第三方的 GitHub 数据汇编中，请不要公开自己的用户个人信息，并确保在您的用户个人资料和 [Git 提交设置](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)中[将您的电子邮件地址配置为私密](https://github.com/settings/emails)。 在当前版本中，用户的电子邮件地址默认设置为私密，但旧版 GitHub 的用户可能需要更新其设置。 -如果您要汇编 GitHub 数据，则必须遵守我们有关[搜刮](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions)和[隐私](/github/site-policy/github-acceptable-use-policies#6-privacy)的服务条款，并且只能出于我们用户授权的目的使用所收集的任何面向公众的用户个人信息。 例如，如果 GitHub 用户出于身份识别和归因的目的而将电子邮件地址设为公开，则您不得将该电子邮件地址用于商业广告。 我们希望您合理地保护从 GitHub 收集的任何用户个人信息，并且必须及时回应 GitHub 或 GitHub 用户的投诉以及删除和“别碰”要求。 +If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. 我们希望您合理地保护从 GitHub 收集的任何用户个人信息，并且必须及时回应 GitHub 或 GitHub 用户的投诉以及删除和“别碰”要求。 同样，GitHub 上项目包含的公开用户个人信息可能在协作过程中被收集。 如果您要针对 GitHub 上的任何用户个人信息问题提出投诉，请参阅我们的[解决投诉](/github/site-policy/github-privacy-statement#resolving-complaints)部分。 @@ -219,7 +235,7 @@ GitHub 的许多服务和功能都是面向公众的。 如果您的内容是面 #### Cookie -GitHub 使用 cookie 让服务交互变得简单而有意义。 Cookie 是网站通常存储在访客的计算机硬盘或移动设备上的小型文本文件。 我们使用 cookie（以及类似技术，例如 HTML5 localStorage）保持登录状态、记住您的首选项，并为 GitHub 的未来开发提供信息。 出于安全目的，我们使用 cookie 来识别设备。 使用我们的网站，即表示您同意我们将这些类型的 cookie 放在您的计算机或设备上。 如果您禁止浏览器或设备接受这些 cookie，则将无法登录或使用 GitHub 的服务。 +GitHub uses cookies and similar technologies (e.g., HTML5 localStorage) to make interactions with our service easy and meaningful. Cookie 是网站通常存储在访客的计算机硬盘或移动设备上的小型文本文件。 We use cookies and similar technologies (hereafter collectively "cookies") to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. 使用我们的网站，即表示您同意我们将这些类型的 cookie 放在您的计算机或设备上。 如果您禁止浏览器或设备接受这些 cookie，则将无法登录或使用 GitHub 的服务。 我们提供了一个有关 [cookie 和跟踪技术](/github/site-policy/github-subprocessors-and-cookies)的网页，介绍我们设置的 cookie、对这些 cookie 的需求以及它们的类型（临时或永久）。 它还列出了我们的第三方分析提供商和其他服务提供商，并明确说明了允许他们跟踪我们网站的哪些部分。 @@ -300,7 +316,7 @@ GitHub 处理美国境内外的个人信息，并依靠标准合同条款作为 ### 隐私声明的变更 -GitHub 可能会不时更改我们的隐私声明，不过大多数情况都是小变动。 如果本隐私声明发生重大变更，我们会在变更生效之前至少 30 天通知用户 - 在我们网站的主页上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 我们还会更新我们的[站点政策仓库](https://github.com/github/site-policy/)，通过它可跟踪本政策的所有变更。 对于本隐私声明的非重大变更或不影响您权利的变更，我们建议用户经常查看我们的站点政策仓库。 +GitHub 可能会不时更改我们的隐私声明，不过大多数情况都是小变动。 如果本隐私声明发生重大变更，我们会在变更生效之前至少 30 天通知用户 - 在我们网站的主页上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 我们还会更新我们的[站点政策仓库](https://github.com/github/site-policy/)，通过它可跟踪本政策的所有变更。 For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### 许可 diff --git a/translations/zh-CN/content/github/site-policy/github-terms-of-service.md b/translations/zh-CN/content/github/site-policy/github-terms-of-service.md index 62152dc82b45..26f4f2aed8b2 100644 --- a/translations/zh-CN/content/github/site-policy/github-terms-of-service.md +++ b/translations/zh-CN/content/github/site-policy/github-terms-of-service.md @@ -14,29 +14,29 @@ versions: ### 摘要 -| 节 | 说明 | -| ----------------------------------------------------------- | ------------------------------------------------------------- | -| [A. 定义](#a-definitions) | 一些基本术语，其定义方式将有助于您理解此协议。 不明确时请回头参阅本节内容。 | -| [B. 帐户条款](#b-account-terms) | 这些是在GitHub 上开设帐户的基本要求。 | -| [C. 可接受的使用](#c-acceptable-use) | 这些是您使用 GitHub 帐户时必须遵循的基本规则。 | -| [D. 用户生成内容](#d-user-generated-content) | 您在 GitHub 上发布的内容归您所有。 但您对此负有一些责任，我们请您向我们授予一些权利，以便我们能够为您提供服务。 | -| [E. 私有仓库](#e-private-repositories) | 本节讨论 GitHub 如何处理您在私有仓库中发布的内容。 | -| [F. 版权和 DMCA 政策](#f-copyright-infringement-and-dmca-policy) | 本节介绍当您认为有人正在侵犯您在 GitHub 上的版权时，GitHub 将如何应对。 | -| [G. 知识产权通告](#g-intellectual-property-notice) | 说明 GitHub 在网站和服务中的权利。 | -| [H. API 条款](#h-api-terms) | 这些是使用 GitHub 的 API 时需遵守的规则，无论您是使用 API 来开发还是数据收集。 | -| [I. 附加产品条款](#i-github-additional-product-terms) | 我们对 GitHub 的功能和产品有一些具体的规则。 | -| [J. 测试版预览](#j-beta-previews) | 这些是适用于 GitHub 仍在开发中的功能的一些附加条款。 | -| [K. 付款](#k-payment) | 您负责付款。 我们负责对您准确计费。 | -| [L. 取消和终止](#l-cancellation-and-termination) | 您可以随时取消此协议并关闭您的帐户。 | -| [M. 与 GitHub 的通信](#m-communications-with-github) | 我们只使用电子邮件和其他电子方式与用户保持联系。 我们不提供电话支持。 | -| [N. 免责声明](#n-disclaimer-of-warranties) | 我们按原样提供服务，我们对此服务不作任何承诺或保证。 **请仔细阅读本节内容；您应该理解要求。** | -| [O. 责任限制](#o-limitation-of-liability) | 对因您使用或不能使用服务或本协议下产生的损害或损失，我们不承担责任。 **请仔细阅读本节内容；它限制了我们对您的义务。** | -| [P. 免除和赔偿](#p-release-and-indemnification) | 您对自己使用服务负全部责任。 | -| [Q. 这些服务条款的更改](#q-changes-to-these-terms) | 我们可能修改本协议，但我们会提前 30 天向您通知会影响您权利的更改。 | -| [R. 其他](#r-miscellaneous) | 关于法律详情，包括我们对法律的选择，请参阅本节内容。 | +| 节 | 说明 | +| ----------------------------------------------------------- | --------------------------------------------------------------------------------------- | +| [A. 定义](#a-definitions) | 一些基本术语，其定义方式将有助于您理解此协议。 不明确时请回头参阅本节内容。 | +| [B. 帐户条款](#b-account-terms) | 这些是在GitHub 上开设帐户的基本要求。 | +| [C. 可接受的使用](#c-acceptable-use) | 这些是您使用 GitHub 帐户时必须遵循的基本规则。 | +| [D. 用户生成内容](#d-user-generated-content) | 您在 GitHub 上发布的内容归您所有。 但您对此负有一些责任，我们请您向我们授予一些权利，以便我们能够为您提供服务。 | +| [E. 私有仓库](#e-private-repositories) | 本节讨论 GitHub 如何处理您在私有仓库中发布的内容。 | +| [F. 版权和 DMCA 政策](#f-copyright-infringement-and-dmca-policy) | 本节介绍当您认为有人正在侵犯您在 GitHub 上的版权时，GitHub 将如何应对。 | +| [G. 知识产权通告](#g-intellectual-property-notice) | 说明 GitHub 在网站和服务中的权利。 | +| [H. API 条款](#h-api-terms) | 这些是使用 GitHub 的 API 时需遵守的规则，无论您是使用 API 来开发还是数据收集。 | +| [I. 附加产品条款](#i-github-additional-product-terms) | 我们对 GitHub 的功能和产品有一些具体的规则。 | +| [J. 测试版预览](#j-beta-previews) | 这些是适用于 GitHub 仍在开发中的功能的一些附加条款。 | +| [K. 付款](#k-payment) | 您负责付款。 我们负责对您准确计费。 | +| [L. 取消和终止](#l-cancellation-and-termination) | 您可以随时取消此协议并关闭您的帐户。 | +| [M. 与 GitHub 的通信](#m-communications-with-github) | 我们只使用电子邮件和其他电子方式与用户保持联系。 我们不提供电话支持。 | +| [N. 免责声明](#n-disclaimer-of-warranties) | 我们按原样提供服务，我们对此服务不作任何承诺或保证。 **请仔细阅读本节内容；您应该理解要求。** | +| [O. 责任限制](#o-limitation-of-liability) | 对因您使用或不能使用服务或本协议下产生的损害或损失，我们不承担责任。 **请仔细阅读本节内容；它限制了我们对您的义务。** | +| [P. 免除和赔偿](#p-release-and-indemnification) | 您对自己使用服务负全部责任。 | +| [Q. 这些服务条款的更改](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. | +| [R. 其他](#r-miscellaneous) | 关于法律详情，包括我们对法律的选择，请参阅本节内容。 | ### GitHub 服务条款 -生效日期：2020 年 4 月 2 日 +生效日期：2020 年 11 月 16 日 ### A. 定义 @@ -98,7 +98,7 @@ versions: 您在使用服务时可能创建或上传用户生成的内容。 对于您发布、上传、链接或通过服务提供的任何用户生成内容，无论内容的形式如何，您对其内容以及由此造成的任何伤害负有全部责任。 我们对用户生成内容的任何公开显示或滥用概不负责。 #### 2. GitHub 可删除内容 -我们不预先筛选用户生成的内容，但我们有权利（但没有义务）拒绝或删除单方面认为违反了任何 [GitHub 条款或政策](/github/site-policy)的任何用户生成内容。 +We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub for mobile may be subject to mobile app stores' additional terms. #### 3. 内容所有权、发布权利和许可授予 您对您的内容保有所有权和责任。 如果您发布不是您自己创建或者您没有所有权的内容，则您同意对您发布的任何内容负责；您只会提交您有权发布的内容；并且您将完全遵守与您发布的内容有关的任何第三方许可。 @@ -106,9 +106,9 @@ versions: 因为您对您的内容保有所有权和责任，所以我们需要授予我们——及其他 GitHub 用户——第 D.4 — D.7 部分所列的某些法律权限。 这些许可授予适用于您的内容。 如果您上传的内容具有已经向 GitHub 授予运行服务所需权限的许可，则无需其他许可。 您了解，您对第 D.4-D.7 部分授予的任何权利不会收取任何费用。 您授予我们的许可将在您从我们的服务器删除您的内容后结束，除非其他用户已经复刻它。 #### 4. 向我们授予许可 -我们需要合法的权利来为您服务，例如托管、发布以及分享您的内容。 您授权我们和我们的合法继承者存储、解析和显示您的内容，以及视需要偶尔制作副本来渲染网站和提供服务。 这包括如下权利：将您的内容复制到我们的数据库并制作备份；向您及其他用户显示；将其解析为搜索索引或在我们的服务器上分析；与其他用户分享；执行（如果您的内容是音乐或视频之类的内容）。 +我们需要合法的权利来为您服务，例如托管、发布以及分享您的内容。 You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. -此许可并未授权 GitHub 销售您的内容或者在服务条款之外使用。 +This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/). #### 5. 向其他用户授予许可 您公开发布的任何用户生成内容，包括议题、评论以及对其他用户仓库的贡献，都可供其他人查看。 设置公开显示您的仓库，即表示您同意允许他人查看和“复刻”您的仓库（这意味着他人可以从他们控制的仓库自行复制您仓库中的内容）。 @@ -116,7 +116,7 @@ versions: 如果您将页面和仓库设为公开显示，则表示您向每个用户授予非独占、全球许可，允许他们通过 GitHub 服务使用、显示和执行您的内容，以及通过 GitHub 的功能（例如通过复刻）只在 GitHub 上重制您的内容。 如果您[采用许可](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository)，您得授予进一步的权利。 如果您上传不是您创建或拥有的内容，则您负责确保上传的内容根据向其他 GitHub 用户授予这些许可的条款进行许可。 #### 6. 仓库许可下的参与。 -只要您参与包含许可通告的仓库，则表示您在相同条款下许可您的参与，并且同意您有权利在这些条款下许可您的参与。 如果您使用单独的协议在不同条款下许可您的参与，如参与者许可协议，则该协议优先。 +Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. 不只是它如此运作吧？ 对。 这在开源社区中广泛接受的行为规范；通常被简称为“入站=出站”。 我们只是将它明确化了。 @@ -126,7 +126,7 @@ versions: 在适用法律不能强制执行本协议的范围内，您授权 GitHub 无归属使用您的内容，并在必要时对您的内容进行合理的修改，以便呈现网站和提供服务。 ### E. 私有仓库 -**短版本：** *您可以访问私有仓库。 我们将私有仓库的内容视为机密， 而且我们仅出于支持的原因、经您同意或出于安全的需要而访问它们。* +**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.* #### 1. 私有仓库的控制 某些帐户可能有私有仓库，允许用户控制对内容的访问。 @@ -135,15 +135,14 @@ versions: GitHub 将私有仓库的内容视为您的机密。 GitHub 将保护私有仓库的内容，防止受未授权的使用和访问，在披露时就像处理我们自己性质类似的机密信息一样，在任何情况下都不低于合理的谨慎程度。 #### 3. 访问 -GitHub 人员仅在以下情况下才可访问您私有仓库的内容： -- 出于支持原因，并征得您的同意和确认。 如果 GitHub 基于支持原因而访问私有仓库，仅在所有者同意并确认后才访问。 -- 当出于安全原因而需要访问时，包括为保持 GitHub 系统和服务的持续保密性、完整性、可用性和弹性而需要访问时。 +GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). 您可选择对您私有仓库启用其他访问权限。 例如： - 例如，您可向不同的 GitHub 服务或功能授予对私有仓库中您的内容的额外访问权限。 这些权限可能因服务或功能而异，但 GitHub 将继续将您的私有仓库内容视为机密。 如果这些服务或功能除了提供 GitHub 服务所需的权限之前，还需要其他权限，我们将会说明这些权限。 -#### 4. 排除 -如果我们有理由相信私有仓库的内容违反法律或本协议的条款，则我们有权利访问、检查和删除该内容。 此外，我们可能[按法律要求](/github/site-policy/github-privacy-statement#for-legal-disclosure)披露您的私有仓库的内容。 +此外，我们可能[按法律要求](/github/site-policy/github-privacy-statement#for-legal-disclosure)披露您的私有仓库的内容。 + +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### F. 版权侵权和 DMCA 政策 如果您认为我们网站上的内容侵犯了您的版权， 请按照我们的[数字千禧年版权法政策](/articles/dmca-takedown-policy/)联系我们。 如果您是版权所有者并且您认为 GitHub 上的内容侵犯了您的权利，请通过[我们便利的 DMCA 表](https://github.com/contact/dmca)联系我们，或发送电子邮件到 copyright@github.com。 发出虚假或无聊的撤销通知可能会产生法律后果。 在发送撤销请求之前，您必须考虑合法用途，如公平使用和许可使用。 @@ -286,9 +285,9 @@ GitHub 不保证服务将满足您的要求；服务不中断、及时、安全 您同意，对于因您使用网站和服务，包括但不限于您违反本协议，而引起的任何和所有索赔、责任和费用，您负责赔偿我们、为我们抗辩并保护我们免受任何损害，但 GitHub 应 (1) 及时向您提供有关索赔、要求、诉讼或程序的书面通知；(2) 赋予您对索赔、要求、诉讼或程序进行抗辩和解决的唯一控制权（但您对任何索赔、要求、诉讼或程序的解决方案必须无条件免除 GitHub 的所有责任）；以及 (3) 向您提供所有合理的协助，但费用由您承担。 ### Q. 这些条款的变更 -**短版本：** *我们希望用户了解我们条款的重要变化，但有些更改并不是那么重要——我们不想每次修复错误时都打扰您。 因此，虽然我们可以随时修改本协议，但我们会向用户通知任何影响您权利的更改，并给您时间进行调整。* +**短版本：** *我们希望用户了解我们条款的重要变化，但有些更改并不是那么重要——我们不想每次修复错误时都打扰您。 So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.* -我们有权利独自裁量随时修订这些服务条款，并在发生任何此类修正时更新这些服务条款。 本协议如有重大更改，如价格变动，我们将至少在更改生效前 30 天在网站上发布通知来告知用户。 对于非重大修改，您继续使用网站即表示同意我们对这些服务条款的修订。 在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看这些条款的所有变更。 +我们有权利独自裁量随时修订这些服务条款，并在发生任何此类修正时更新这些服务条款。 We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. 在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看这些条款的所有变更。 我们保留随时和不时修改或停用（临时或永久）网站或其任何部分的权利，可能通知，也可能不通知。 diff --git a/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md index 5fb00a7500c0..ab710d309949 100644 --- a/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md +++ b/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md @@ -41,12 +41,12 @@ versions: 对提交 SHA 哈希的引用会自动转换为指向 {% data variables.product.product_name %} 上提交的短链接。 -| 引用类型 | 源引用 | 短链接 | -| ----------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | -| 提交 URL | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| Username/Repository@SHA | jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| 引用类型 | 源引用 | 短链接 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | +| 提交 URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | +| `Username/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | ### 自定义外部资源的自动链接 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 be486d8c100b..ac282cebc877 100644 --- a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md @@ -203,6 +203,6 @@ fragment repositories on Organization { 下面是关于可与企业账户 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/). +有关可与企业账户 API 结合使用的新查询、突变和架构定义类型的详细信息，请参阅任何 [GraphQL 参考页面](/v4/)含有详细 GraphQL 定义的边栏。 您可以从 GitHub 的 GraphQL explorer 访问参考文档。 更多信息请参阅“[使用 explorer](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)。” 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/v4/guides)。 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/v4/guides)。 diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md index db3b76549d1c..733196f5bb46 100644 --- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md +++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md @@ -90,7 +90,7 @@ versions: {% data reusables.github-insights.settings-tab %} {% data reusables.github-insights.teams-tab %} {% data reusables.github-insights.edit-team %} -3. 在“Contributors（贡献者）”下，使用下拉菜单并选择贡献者。 ![Contributors drop-down](/assets/images/help/insights/contributors-drop-down.png) +3. 在“Contributors（贡献者）”下，使用下拉菜单并选择贡献者。 ![贡献者下拉菜单](/assets/images/help/insights/contributors-drop-down.png) 4. 单击 **Done（完成）**。 #### 从自定义团队中删除贡献者 diff --git a/translations/zh-CN/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md b/translations/zh-CN/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md index 92d4b3326d4b..b9f817a52bc6 100644 --- a/translations/zh-CN/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md +++ b/translations/zh-CN/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md @@ -8,19 +8,24 @@ versions: {% note %} -**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 目前，{% data variables.product.prodname_github_container_registry %} 只支持 Docker 映像格式。 在测试阶段，存储和带宽是免费的。 +**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% endnote %} - {% data reusables.package_registry.container-registry-feature-highlights %} 要共享有关包使用的上下文，可以将仓库链接到 {% data variables.product.prodname_dotcom %} 上的容器映像。 更多信息请参阅“[将仓库连接到容器映像](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)”。 ### 支持的格式 -{% data variables.product.prodname_container_registry %} 目前只支持 Docker 映像。 +{% data variables.product.prodname_container_registry %} 目前支持以下容器映像格式： + +* [Docker 映像清单 V2，架构 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) 规格](https://github.com/opencontainers/image-spec) + +#### 清单列表/映像索引 +{% data variables.product.prodname_github_container_registry %} 也支持 Docker V2、Schema 2 和 OCI 映像规格中定义的 [Docker 清单列表](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI 映像索引](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md)格式。 ### 容器映像的可见性和访问权限 diff --git a/translations/zh-CN/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md b/translations/zh-CN/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md new file mode 100644 index 000000000000..381be1f0cf3d --- /dev/null +++ b/translations/zh-CN/content/packages/getting-started-with-github-container-registry/enabling-improved-container-support.md @@ -0,0 +1,37 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)”。 + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. 更多信息请参阅“[配置容器映像的访问控制和可见性](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)”。 + + ![用于启用公共或私有包的选项 ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/zh-CN/content/packages/getting-started-with-github-container-registry/index.md b/translations/zh-CN/content/packages/getting-started-with-github-container-registry/index.md index 6cf2b59cd6f4..e59088076993 100644 --- a/translations/zh-CN/content/packages/getting-started-with-github-container-registry/index.md +++ b/translations/zh-CN/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 %} 有关配置、删除、推送或拉取容器映像的信息，请参阅“[使用 {% data variables.product.prodname_github_container_registry %} 管理容器映像](/packages/managing-container-images-with-github-container-registry)”。 diff --git a/translations/zh-CN/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md b/translations/zh-CN/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md index 13e923ddbcae..7d5f27891f04 100644 --- a/translations/zh-CN/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md +++ b/translations/zh-CN/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md @@ -31,6 +31,8 @@ versions: ### 使用容器注册表进行身份验证 +{% data reusables.package_registry.feature-preview-for-container-registry %} + 您需要使用基本 URL `ghcr.io` 向 {% data variables.product.prodname_container_registry %} 验证。 我们建议创建新的访问令牌以使用 {% data variables.product.prodname_container_registry %}。 {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} @@ -72,6 +74,8 @@ versions: ### 更新 {% data variables.product.prodname_actions %} 工作流程 +{% data reusables.package_registry.feature-preview-for-container-registry %} + 如果您有 {% data variables.product.prodname_actions %} 工作流程使用来自 {% data variables.product.prodname_registry %} Docker 注册表的 Docker 映像，则可能需要将工作流程更新到 {% data variables.product.prodname_container_registry %}，以允许匿名访问公共容器映像、更细致的访问权限以及更好的容器存储和带宽兼容性。 1. 将 Docker 映像迁移到 `ghcr.io` 上的新 {% data variables.product.prodname_container_registry %}。 例如，请参阅“[使用 Docker CLI 迁移 Docker 映像](#migrating-a-docker-image-using-the-docker-cli)”。 diff --git a/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md b/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md index 4ffede1b3d86..38df231fc685 100644 --- a/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md +++ b/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md @@ -24,7 +24,7 @@ versions: 如果您的软件包由组织和私人拥有，则您只能向其他组织成员或团队授予访问。 -对于组织映像容器，组织管理员必须先启用包，然后才能将可见性设置为公共。 更多信息请参阅“[为组织启用 GitHub Container Registry](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)”。 +对于组织映像容器，组织管理员必须先启用包，然后才能将可见性设置为公共。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 1. 在软件包设置页面上，单击 **Invite teams or people（邀请团队或人员）**，然后输入名称、用户名或您想要授予访问权限的人员的电子邮件地址。 您还可以从组织输入团队名称，以允许所有团队成员访问。 ![容器访问邀请按钮](/assets/images/help/package-registry/container-access-invite.png) @@ -54,7 +54,7 @@ versions: 公共包可以匿名访问，无需身份验证。 包一旦被设为公共，便无法再次将其设为私有。 -对于组织映像容器，组织管理员必须先启用公共包，然后才能将可见性设置为公共。 更多信息请参阅“[为组织启用 GitHub Container Registry](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)”。 +对于组织映像容器，组织管理员必须先启用公共包，然后才能将可见性设置为公共。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." {% data reusables.package_registry.package-settings-from-org-level %} 5. 在“Danger Zone（危险区域）”下，选择可见性设置： diff --git a/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md b/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md index de84b26f7792..ebf4ca347e4a 100644 --- a/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md +++ b/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md @@ -16,8 +16,6 @@ versions: 删除公共包时，请注意，您可能会破坏依赖于包的项目。 - - ### 保留的包版本和名称 {% data reusables.package_registry.package-immutability %} diff --git a/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md index 228c5437b0a9..0db1573a0ab9 100644 --- a/translations/zh-CN/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ b/translations/zh-CN/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 %} -要推送和拉取组织拥有的容器映像，组织管理员必须为组织启用 {% data variables.product.prodname_github_container_registry %}。 更多信息请参阅“[为组织启用 GitHub Container Registry](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)”。 +要推送和拉取组织拥有的容器映像，组织管理员必须为组织启用 {% data variables.product.prodname_github_container_registry %}。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." ### 向 {% data variables.product.prodname_github_container_registry %} 验证 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 2a1157938f52..ce9044313cca 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 @@ -26,6 +26,8 @@ versions: {% data reusables.package_registry.container-registry-beta %} +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + {% endif %} #### 查看包 @@ -34,17 +36,17 @@ versions: #### 关于包权限和可见性 {% if currentVersion == "free-pro-team@latest" %} -| | 包注册表 | {% data variables.product.prodname_github_container_registry %} -| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | -| 托管位置 | 您可以在一个仓库中托管多个包。 | 您可以在一个组织或用户帐户中托管多个容器映像。 | -| 权限 | {{ site.data.reusables.package_registry.public-or-private-packages }} 您可以使用 {{ site.data.variables.product.prodname_dotcom }} 角色和团队来限制谁可以安装或发布每个包，因为包会继承仓库的权限。 对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | 对于每个容器映像，您可以选择其他人具有的访问权限级别。 容器映像访问的权限与组织和仓库权限不同。 | +| | 包注册表 | {% data variables.product.prodname_github_container_registry %} +| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | +| 托管位置 | 您可以在一个仓库中托管多个包。 | 您可以在一个组织或用户帐户中托管多个容器映像。 | +| 权限 | {% data reusables.package_registry.public-or-private-packages %} 您可以使用 {% data variables.product.prodname_dotcom %} 角色和团队来限制谁可以安装或发布每个包，因为包会继承仓库的权限。 对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | 对于每个容器映像，您可以选择其他人具有的访问权限级别。 容器映像访问的权限与组织和仓库权限不同。 | 可见性 | {% data reusables.package_registry.public-or-private-packages %} | 您可以设置每个容器映像的可见性。 私有容器映像仅对组织内被授予访问权限的人员或团队可见。 公共容器映像对任何人都可见。 | 匿名访问 | N/A| 您可以匿名访问公共容器映像。 {% else %} -| | 包注册表 | -| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 托管位置 | 您可以在一个仓库中托管多个包。 | -| 权限 | {{ site.data.reusables.package_registry.public-or-private-packages }} 您可以使用 {{ site.data.variables.product.prodname_dotcom }} 角色和团队来限制谁可以安装或发布每个包，因为包会继承仓库的权限。 对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | +| | 包注册表 | +| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 托管位置 | 您可以在一个仓库中托管多个包。 | +| 权限 | {% data reusables.package_registry.public-or-private-packages %} 您可以使用 {% data variables.product.prodname_dotcom %} 角色和团队来限制谁可以安装或发布每个包，因为包会继承仓库的权限。 对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | | 可见性 | {% data reusables.package_registry.public-or-private-packages %} {% endif %} @@ -164,12 +166,12 @@ versions: - 要从仓库下载和安装包，您的令牌必须具有 `read:packages` 作用域，并且您的用户帐户必须对该仓库具有读取权限。 - 要在 {% data variables.product.product_name %} 上删除私有包的特定版本，您的令牌必须具有 `delete:packages` 和 `repo` 作用域。 公共包无法删除。 更多信息请参阅“[删除包](/packages/publishing-and-managing-packages/deleting-a-package)”。 -| 作用域 | 描述 | 仓库权限 | -| ----------------- | ------------------------------------------------------------------------------ | --------------- | -| `read:packages` | 从 {% data variables.product.prodname_registry %} 下载和安装包 | 读取 | -| `write:packages` | 将包上传和发布到 {% data variables.product.prodname_registry %} | 写入 | -| `delete:packages` | 从 {% data variables.product.prodname_registry %} 删除私有包的特定版本 | 管理员 | -| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write, or admin | +| 作用域 | 描述 | 仓库权限 | +| ----------------- | ----------------------------------------------------------- | ------ | +| `read:packages` | 从 {% data variables.product.prodname_registry %} 下载和安装包 | 读取 | +| `write:packages` | 将包上传和发布到 {% data variables.product.prodname_registry %} | 写入 | +| `delete:packages` | 从 {% data variables.product.prodname_registry %} 删除私有包的特定版本 | 管理员 | +| `repo` | 上传和删除包（连同 `write:packages` 或 `delete:packages`） | 写入或管理员 | 创建 {% data variables.product.prodname_actions %} 工作流程时，您可以使用 `GITHUB_TOKEN` 发布和安装 {% data variables.product.prodname_registry %} 中的包，无需存储和管理个人访问令牌。 diff --git a/translations/zh-CN/content/packages/publishing-and-managing-packages/deleting-a-package.md b/translations/zh-CN/content/packages/publishing-and-managing-packages/deleting-a-package.md index 090577a118e0..9ec33a70d9bf 100644 --- a/translations/zh-CN/content/packages/publishing-and-managing-packages/deleting-a-package.md +++ b/translations/zh-CN/content/packages/publishing-and-managing-packages/deleting-a-package.md @@ -31,7 +31,7 @@ versions: {% else %} -At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages. +目前，{% data variables.product.prodname_registry %} on {% data variables.product.product_location %} 不支持删除公共包。 {% endif %} diff --git a/translations/zh-CN/content/packages/publishing-and-managing-packages/publishing-a-package.md b/translations/zh-CN/content/packages/publishing-and-managing-packages/publishing-a-package.md index 4559a4e044da..3eece7e742d7 100644 --- a/translations/zh-CN/content/packages/publishing-and-managing-packages/publishing-a-package.md +++ b/translations/zh-CN/content/packages/publishing-and-managing-packages/publishing-a-package.md @@ -22,7 +22,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} 如果软件包的新版本修复了安全漏洞，您应该在仓库中发布安全通告。 -{% 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. 更多信息请参阅“[关于 GitHub 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 +{% data variables.product.prodname_dotcom %} 审查每个发布的安全通告，并且可能使用它向受影响的仓库发送 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 GitHub 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 {% endif %} ### 发布包 diff --git a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md index 2a441679474e..3180d25cc295 100644 --- a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md @@ -27,7 +27,7 @@ versions: 在 `servers` 标记中，添加带 `id` 的子 `server` 标记，将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌。 -在 `repositories` 标记中，通过将仓库的 `id` 映射到您在包含凭据的 `server` 标记中添加的 `id` 来配置仓库。 将 {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名称，{% endif %}将 *REPOSITORY* 替换为您要向其发布包或从中安装包的仓库的名称，并将 *OWNER* 替换为拥有仓库的用户或组织帐户的名称。 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. +在 `repositories` 标记中，通过将仓库的 `id` 映射到您在包含凭据的 `server` 标记中添加的 `id` 来配置仓库。 将 {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名称，{% endif %}将 *REPOSITORY* 替换为您要向其发布包或从中安装包的仓库的名称，并将 *OWNER* 替换为拥有仓库的用户或组织帐户的名称。 由于不支持大写字母，因此，即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母，也必须对仓库所有者使用小写字母。 如果要与多个仓库交互，您可以将每个仓库添加到 `repository` 标记中独立的子 `repositories`，将每个仓库的 `id` 映射到 `servers` 标记中的凭据。 diff --git a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md index 1b5d8323211b..b66fbee98c83 100644 --- a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md @@ -78,7 +78,7 @@ versions: ### 发布包 -您可以使用 *nuget.config* 文件进行身份验证，将包发布到 {% data variables.product.prodname_registry %}。 发布时，您需要将 *csproj* 文件中的 `OWNER` 值用于您的 *nuget.config* 身份验证文件。 在 *.csproj* 文件中指定或增加版本号，然后使用 `dotnet pack` 命令创建该版本的 *.nuspec* 文件。 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. +您可以使用 *nuget.config* 文件进行身份验证，将包发布到 {% data variables.product.prodname_registry %}。 发布时，您需要将 *csproj* 文件中的 `OWNER` 值用于您的 *nuget.config* 身份验证文件。 在 *.csproj* 文件中指定或增加版本号，然后使用 `dotnet pack` 命令创建该版本的 *.nuspec* 文件。 有关创建包的更多信息，请参阅 Microsoft 文档中的“[创建和发布包](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)”。 {% data reusables.package_registry.viewing-packages %} @@ -160,7 +160,7 @@ versions: ### 安装包 -在项目中使用来自 {% data variables.product.prodname_dotcom %} 的包类似于使用来自 *nuget.org* 的包。 将包依赖项添加到 *.csproj* 文件以指定包名称和版本。 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. +在项目中使用来自 {% data variables.product.prodname_dotcom %} 的包类似于使用来自 *nuget.org* 的包。 将包依赖项添加到 *.csproj* 文件以指定包名称和版本。 有关在项目中使用 *.csproj* 文件的更多信息，请参阅 Microsoft 文档中的“[使用 NuGet 包](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)”。 {% data reusables.package_registry.authenticate-step %} diff --git a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md index 34c1fb0455a7..02e62fd6544a 100644 --- a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md @@ -30,7 +30,7 @@ versions: {% data variables.product.prodname_ghe_server %} 实例的主机名。 {% endif %} -将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *REPOSITORY* 替换为要发布的包所在仓库的名称，将 *OWNER* 替换为 {% data variables.product.prodname_dotcom %} 上拥有该仓库的用户或组织帐户的名称。 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. +将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *REPOSITORY* 替换为要发布的包所在仓库的名称，将 *OWNER* 替换为 {% data variables.product.prodname_dotcom %} 上拥有该仓库的用户或组织帐户的名称。 由于不支持大写字母，因此，即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母，也必须对仓库所有者使用小写字母。 {% note %} diff --git a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md index 50d5cecb4b04..9f326abbf399 100644 --- a/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md @@ -77,7 +77,7 @@ registry=https://npm.pkg.github.com/OWNER {% note %} -**Note:** Package names and scopes must only use lowercase letters. +**注：**包名称和作用域只能使用小写字母。 {% endnote %} @@ -85,7 +85,7 @@ registry=https://npm.pkg.github.com/OWNER 通过在 *package.json* 文件中包含 `URL` 字段，您可以将多个包发布到同一个 {% data variables.product.prodname_dotcom %} 仓库。 更多信息请参阅“[将多个包发布到同一个仓库](#publishing-multiple-packages-to-the-same-repository)”。 -您可以使用项目中的本地 *.npmrc* 文件或使用 *package.json* 中的 `publishConfig` 选项来设置项目的作用域映射。 {% data variables.product.prodname_registry %} 只支持作用域内的 npm 包。 作用域内的包具有名称格式 `@owner/name`。 作用域内的包总是以 `@` 符号开头。 You may need to update the name in your *package.json* to use the scoped name. 例如，`"name": "@codertocat/hello-world-npm"`。 +您可以使用项目中的本地 *.npmrc* 文件或使用 *package.json* 中的 `publishConfig` 选项来设置项目的作用域映射。 {% data variables.product.prodname_registry %} 只支持作用域内的 npm 包。 作用域内的包具有名称格式 `@owner/name`。 作用域内的包总是以 `@` 符号开头。 您可能需要更新 *package.json* 中的名称以使用作用域内的名称。 例如，`"name": "@codertocat/hello-world-npm"`。 {% data reusables.package_registry.viewing-packages %} @@ -143,7 +143,7 @@ registry=https://npm.pkg.github.com/OWNER ### 安装包 -通过在项目的 *package.json* 文件中将包添加为依赖项，您可以从 {% data variables.product.prodname_registry %} 安装包。 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. +通过在项目的 *package.json* 文件中将包添加为依赖项，您可以从 {% data variables.product.prodname_registry %} 安装包。 有关在项目中使用 *package.json* 的更多信息，请参阅 npm 文档中的“[使用 package.json](https://docs.npmjs.com/getting-started/using-a-package.json)”。 默认情况下，您可以从一个组织添加包。 更多信息请参阅“[从其他组织安装包](#installing-packages-from-other-organizations)”。 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 b161e3312bbd..d12d15de4006 100644 --- a/translations/zh-CN/content/rest/guides/basics-of-authentication.md +++ b/translations/zh-CN/content/rest/guides/basics-of-authentication.md @@ -48,8 +48,8 @@ end ``` 客户端 ID 和客户端密钥[来自应用程序的配置页面][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 +{% if currentVersion == "free-pro-team@latest" %} **永远_不要_**将该事项的这些值存储在 +{% data variables.product.product_name %} 中或任何其他公共的地方。{% endif %} 建议将它们存储为 [环境变量][about env vars]--我们正是这样做的。 接下来，在 _views/index.erb_ 中粘贴此内容： @@ -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]。 此标头包含用于发出请求的令牌的作用域列表。 除此之外，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 %} 的端点。 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 #### 发出经过身份验证的请求 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 a771dbf41eee..6bed206ec28e 100644 --- a/translations/zh-CN/content/rest/guides/traversing-with-pagination.md +++ b/translations/zh-CN/content/rest/guides/traversing-with-pagination.md @@ -32,7 +32,7 @@ $ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user: `-I` 参数表示我们只关注标头，而不关注实际内容。 在检查结果时，您会注意到 Link 标头中的一些信息，如下所示： - Link: ; rel="next", + 链接：; rel="next", ; rel="last" 我们来分解说明。 `rel="next"` 表示下一页是 `page=2`。 这是合理的，因为在默认情况下，所有分页查询都是从第 `1` 页开始。`rel="last"` 提供了更多信息，指示结果的最后一页是第 `34` 页。 因此，我们还有 33 页有关 `addClass` 的信息可用。 不错！ @@ -49,7 +49,7 @@ $ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user: 以下是再次出现的 Link 标头： - Link: ; rel="next", + 链接：; rel="next", ; rel="last", ; rel="first", ; rel="prev" @@ -66,7 +66,7 @@ $ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user: 请注意它对标头响应的影响： - Link: ; rel="next", + 链接：; rel="next", ; rel="last" 您可能已经猜到了，`rel="last"` 信息表明最后一页现在是第 20 页。 这是因为我们要求每页提供更多的结果相关信息。 diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md index 6ced5e101573..9b4e697d8839 100644 --- a/translations/zh-CN/content/rest/overview/libraries.md +++ b/translations/zh-CN/content/rest/overview/libraries.md @@ -11,7 +11,7 @@ versions:
Gundamcat -

Octokit comes in many flavors

+

Octokit 风格多样

使用官方的 Octokit 库，或者使用任何适用的第三方库。


Ruby → octokit.rb

@@ -48,7 +48,7 @@ Library name | Repository |---|---| **haskell-github** | [fpco/Github](https://g ### Java -Library name | Repository | More information |---|---|---| **GitHub Java API**| [org.eclipse.egit.github.core](https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core) | Is part of the [GitHub Mylyn Connector](https://github.com/eclipse/egit-github) and aims to support the entire GitHub v3 API. 可在 [Maven Central](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.eclipse.egit.github.core%22) 中构建。 **GitHub API for Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|defines an object oriented representation of the GitHub API. **JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|is based on Java7 JSON API (JSR-353), simplifies tests with a runtime GitHub stub, and covers the entire API. +Library name | Repository | More information |---|---|---| **GitHub Java API**| [org.eclipse.egit.github.core](https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core) | Is part of the [GitHub Mylyn Connector](https://github.com/eclipse/egit-github) and aims to support the entire GitHub v3 API. 可在 [Maven Central](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.eclipse.egit.github.core%22) 中构建。 **用于 Java 的 GitHub API**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|定义面向对象的 GitHub API 表示形式。 **JCabi GitHub API**|[github.jcabi.com（个人网站）](http://github.jcabi.com)|基于 Java7 JSON API (JSR-353)，简化 runtime GitHub stub 测试，涵盖整个 API。 ### JavaScript diff --git a/translations/zh-CN/content/rest/overview/openapi-description.md b/translations/zh-CN/content/rest/overview/openapi-description.md index 5c6b2dfbf5a3..cd4915fae104 100644 --- a/translations/zh-CN/content/rest/overview/openapi-description.md +++ b/translations/zh-CN/content/rest/overview/openapi-description.md @@ -14,14 +14,14 @@ versions: 您可以在开源[REST API OpenAPI 描述](https://github.com/github/rest-api-description)仓库中找到描述。 -我们以两种格式提供描述。 The bundled version works for most cases, as it includes OpenAPI components for reuse and readability. If your tooling does not support inline references to components, we also provide a fully dereferenced version. +我们以两种格式提供描述。 捆绑版本适用于大多数情况，因为它包括可重用且可读的 OpenAPI 组件。 如果您的工具不支持对组件的内联引用，我们还提供完全取消引用的版本。 -### Using the {% data variables.product.company_short %} OpenAPI description +### 使用 {% data variables.product.company_short %} OpenAPI 描述 -There are many uses for an OpenAPI description. 例如，您可以： +OpenAPI 描述有很多用途。 例如，您可以： -* Generate your own API client. -* Validate and test a {% data variables.product.company_short %} REST API integration. -* Explore and interact with the {% data variables.product.product_name %} REST API using third-party tools, such as Insomnia or Postman. +* 生成您自己的 API 客户端。 +* 验证并测试 {% data variables.product.company_short %} REST API 集成。 +* 使用第三方工具（如 Insomnia 或 Postman）探索 {% data variables.product.product_name %} REST API 并与之交互。 -For example, {% data variables.product.company_short %} uses the REST OpenAPI description to generate the {% data variables.product.product_name %} [REST API reference documentation](/rest/reference). +例如，{% data variables.product.company_short %} 使用 REST OpenAPI 描述生成 {% data variables.product.product_name %} [REST API 参考文档](/rest/reference)。 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 967998775466..ec4a6ae19e50 100644 --- a/translations/zh-CN/content/rest/overview/other-authentication-methods.md +++ b/translations/zh-CN/content/rest/overview/other-authentication-methods.md @@ -1,6 +1,6 @@ --- -title: 其他身份验证方法 -intro: 您可以在非生产环境中使用基本身份验证进行测试。 +title: Other authentication methods +intro: You can use basic authentication for testing in a non-production environment. redirect_from: - /v3/auth versions: @@ -11,9 +11,12 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -虽然 API 提供多种身份验证方法，但我们强烈建议对生产应用程序使用 [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)。 提供的其他方法旨在用于脚本或测试（即没有必要使用完整 OAuth 方法的情况）。 依赖 -{% data variables.product.product_name %} 进行身份验证的第三方应用程序不应要求或收集 {% data variables.product.product_name %} 凭据。 -它们应该使用 [OAuth web 工作流程](/apps/building-oauth-apps/authorizing-oauth-apps/)。 +While the API provides multiple methods for authentication, we strongly +recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) for production applications. The other +methods provided are intended to be used for scripts or testing (i.e., cases +where full OAuth would be overkill). Third party applications that rely on +{% data variables.product.product_name %} for authentication should not ask for or collect {% data variables.product.product_name %} credentials. +Instead, they should use the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). {% endif %} @@ -23,46 +26,63 @@ To authenticate we recommend using [OAuth](/apps/building-integrations/setting-u {% endif %} -### 基本身份验证 +### Basic Authentication -API 支持在 [RFC2617](http://www.ietf.org/rfc/rfc2617.txt) 中定义的基本身份验证，但有一些细微区别。 主要区别在于 RFC 要求使用 `401 Unauthorized` 响应来回复未经验证的请求。 在很多情况下这会暴露用户数据的存在。 对于此类请求，{% data variables.product.product_name %} API 的响应是 `404 Not Found`。 这可能导致 HTTP 库假定返回 `401 Unauthorized` 的问题。 解决方案是手动创建 `Authorization` 标头。 +The API supports Basic Authentication as defined in +[RFC2617](http://www.ietf.org/rfc/rfc2617.txt) with a few slight differences. +The main difference is that the RFC requires unauthenticated requests to be +answered with `401 Unauthorized` responses. In many places, this would disclose +the existence of user data. Instead, the {% data variables.product.product_name %} API responds with `404 Not Found`. +This may cause problems for HTTP libraries that assume a `401 Unauthorized` +response. The solution is to manually craft the `Authorization` header. -#### 通过 OAuth 和个人访问令牌 +#### Via OAuth and personal access tokens -我们建议您使用 OAuth 令牌向 GitHub API 验证。 OAuth 令牌包含[个人访问令牌][personal-access-tokens]，允许用户随时撤销访问权限。 +We recommend you use OAuth tokens to authenticate to the GitHub API. OAuth tokens include [personal access tokens][personal-access-tokens] and enable the user to revoke access at any time. ```shell $ curl -u username:token {% data variables.product.api_url_pre %}/user ``` -如果您的工具只支持基本身份验证，但您想要利用 OAuth 访问令牌的安全功能，这个方法非常有用。 +This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. -{% if enterpriseServerVersions contains currentVersion %} -#### 通过用户名和密码 +#### Via username and password -{% data reusables.apps.deprecating_password_auth %} +{% if currentVersion == "free-pro-team@latest" %} -要将基本身份验证与 {% data variables.product.product_name %} API 结合使用，只需发送与帐户关联的用户名和密码。 +{% note %} -例如，如果您通过 [cURL][curl] 访问 API，则将 `` 替换为您的 {% data variables.product.product_name %} 用户名后，以下命令将对您进行身份验证。 （cURL 将提示您输入密码。） +**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. + +For example, if you're accessing the API via [cURL][curl], the following command +would authenticate you if you replace `` with your {% data variables.product.product_name %} username. +(cURL will prompt you to enter the password.) ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -如果您启用了双重身份验证，请务必了解如何[使用双重身份验证](/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](/v3/auth/#working-with-two-factor-authentication). {% endif %} {% if currentVersion == "free-pro-team@latest" %} -#### SAML SSO 身份验证 +#### Authenticating for SAML SSO {% note %} -**注：**代表其他工具生成令牌的集成和 OAuth 应用程序将自动获得授权。 +**Note:** Integrations and OAuth applications that generate tokens on behalf of others are automatically authorized. {% endnote %} -如果您要使用 API 访问实施 [SAML SSO][saml-sso] 身份验证的组织，您需要创建个人访问令牌 (PAT) 并[授权该令牌][allowlist]访问组织。 访问 `X-GitHub-SO` 中指定的 URL 以授权令牌访问组织。 +If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a personal access token (PAT) and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization. ```shell $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test @@ -74,7 +94,7 @@ $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api } ``` -在请求可能来自多个组织的数据时（例如，[请求由用户创建的议题列表][user-issues]），`X-GitHub-SSO` 标头将指示哪些组织需要您授权个人访问令牌： +When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your personal access token: ```shell $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/user/issues @@ -82,27 +102,26 @@ $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api > X-GitHub-SSO: partial-results; organizations=21955855,20582480 ``` -`organizations` 的值是需要您授权个人访问令牌的组织列表，用逗号分隔。 +The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your personal access token. {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -### 使用双重身份验证 - -{% data reusables.apps.deprecating_password_auth %} +### Working with two-factor authentication -启用双重身份验证后，REST API 中_大多数_端点的[基本身份验证](#basic-authentication)均要求您使用个人访问令牌或 OAuth 令牌，而不是用户名和密码。 - -您可以 {% if currentVersion == "free-pro-team@latest" %}使用 [{% data variables.product.product_name %}开发者设置](https://github.com/settings/tokens/new){% endif %}来生成新的个人访问令牌，或者使用 OAuth 授权 API 中的“[创建新授权][create-access]”端点来生成新的 OAuth 令牌。 更多信息请参阅“[创建用于命令行的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)”。 然后，您将使用这些令牌向 GitHub API 验证，更多信息请参阅“[使用 OAuth 令牌进行身份验证][oauth-auth]”。 唯一需要使用用户名和密码进行身份验证的时候是创建 OAuth 令牌或使用 OAuth 授权 API 时。 +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 %}. 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)". 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 %} -#### 结合使用 OAuth 授权 API 与双重身份验证 +{% if enterpriseServerVersions contains currentVersion %} +#### Using the OAuth Authorizations API with two-factor authentication -当您调用 OAuth 授权 API 时，基本身份验证会要求您使用一次性密码 (OTP) 以及您的用户名和密码，而不是令牌。 当您尝试使用 OAuth 授权 API 进行身份验证时，服务器将响应 `401 Unauthorized` 和以下标头之一，以指示需要使用双重身份验证代码： +When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code: -`X-GitHub-OTP: required; SMS` 或 `X-GitHub-OTP: required; app`. +`X-GitHub-OTP: required; SMS` or `X-GitHub-OTP: required; app`. -此标头指示您的帐户如何接收其双重身份验证代码。 您将通过 SMS 接收 OTP 代码，或者使用 Google Authenticator 或 1Password 等应用程序，具体取决于您的帐户设置。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。 在标头中传递 OTP： +This header tells you how your account receives its two-factor authentication codes. Depending how you set up your account, you will either receive your OTP codes via SMS or you will use an application like Google Authenticator or 1Password. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." Pass the OTP in the header: ```shell $ curl --request POST \ @@ -114,10 +133,10 @@ $ curl --request POST \ ``` {% endif %} -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization [curl]: http://curl.haxx.se/ [oauth-auth]: /v3/#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 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 36628210cfb2..8dff7c69ab9b 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 @@ -76,7 +76,7 @@ $ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs ### 身份验证 -{% 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. +{% if currentVersion == "github-ae@latest" %} 我们建议通过 [web 应用程序流程](/developers/apps/authorizing-oauth-apps#web-application-flow)创建 OAuth2 令牌来向 {% data variables.product.product_name %} REST API 验证。 {% else %} 通过 {% data variables.product.product_name %} REST API 验证有两种方式。{% endif %} 需要身份验证的请求有时将返回 `404 Not Found`，而不是 `403 Forbidden`。 这是为了防止私有仓库意外泄露给未经授权的用户。 #### 基本验证 @@ -96,7 +96,7 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. {% endnote %} -阅读[关于 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. +阅读[关于 OAuth2 的更多信息](/apps/building-oauth-apps/)。 请注意，OAuth2 令牌可使用生产应用程序的 [web 应用程序流](/developers/apps/authorizing-oauth-apps#web-application-flow)来获取。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} #### OAuth2 键/密钥 @@ -135,9 +135,9 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar 在短时间内检测到多个使用无效凭据的请求后，API 将暂时拒绝该用户的所有身份验证尝试（包括使用有效凭据的尝试），并返回 `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" @@ -165,19 +165,10 @@ $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product. 您可以向根端点发出 `GET` 请求，以获取 REST API 支持的所有端点类别： ```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 %} - -{% note %} - -**注：**对于 {% data variables.product.prodname_ghe_server %}，[与所有其他端点一样](/v3/enterprise-admin/#endpoint-urls)，您需要传递用户名和密码。 - -{% endnote %} - -{% endif %} - ### GraphQL 全局节点 ID 请参阅“[使用全局节点 ID](/v4/guides/using-global-node-ids)”指南，详细了解如何通过 REST API 查找 `node_id` 以及如何在 GraphQL 操作中使用它们。 diff --git a/translations/zh-CN/content/rest/overview/troubleshooting.md b/translations/zh-CN/content/rest/overview/troubleshooting.md index 3c5d62a9dd20..95d294358bca 100644 --- a/translations/zh-CN/content/rest/overview/troubleshooting.md +++ b/translations/zh-CN/content/rest/overview/troubleshooting.md @@ -13,16 +13,53 @@ versions: 您在 API 中可能会遇到一些奇怪的问题，下面列出一些您可能会经历的问题的解决方案。 -### 为什么仓库明明存在，我却收到了 `404` 错误？ +### 现在仓库的 `404` 错误 一般来说，我们发送 `404` 错误的原因是您的客户端没有正确通过身份验证。 您可能预期在这些情况下会看到 `403 Forbidden`。 但是，由于我们不希望提供有关私有仓库的_任何_信息，因此 API 会返回 `404` 错误。 要解决问题，请确保[您正确通过身份验证](/guides/getting-started/)，[您的 OAuth 访问令牌具有所需的作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)，并且[第三方应用程序限制][oap-guide]不会阻止您访问。 -### 为什么我看不到所有的结果？ +### 并非所有结果都返回 大多数访问资源列表（_例如_，用户、议题_等_）的 API 调用都支持分页。 如果您发出了请求但收到了不完整的结果集，您可能只看到第一页。 您需要请求剩余的页面以获取更多结果。 *切勿*尝试和猜测分页 URL 的格式。 并非每个 API 调用都使用相同的结构。 您应该从随每个请求一起发送的[链接标头](/v3/#pagination)中提取分页信息。 +{% if currentVersion == "free-pro-team@latest" %} +### 基本身份验证错误 + +从 2020 年 11 月 13 日起，REST API 和 OAuth 授权 API 的用户名和密码身份验证被弃用，不再有效。 + +#### 使用 `username`/`password` 进行基本身份验证 + +如果您对 API 调用使用 `username` 和 `password`，则它们无法再进行身份验证。 例如： + +```bash +curl -u my_user:my_password https://api.github.com/user/repos +``` + +相反，在测试端点或进行本地开发时使用[个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)： + +```bash +curl -H 'Authorization: token my_access_token' https://api.github.com/user/repos +``` + +对于 OAuth 应用程序，您应该使用 [web 应用程序流程](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)生成 OAuth 令牌以用于 API 调用的标头： + +```bash +curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos +``` + +#### 调用 OAuth 授权 API + +如果要调用 [OAuth 授权 API](/enterprise-server@2.22/rest/reference/oauth-authorizations) 来管理 OAuth 应用的授权或生成访问令牌，类似于以下示例： + +```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"}' +``` + +然后您必须切换到 [web 应用程序流程](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)来生成访问令牌。 + +{% endif %} + [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md index 8e25a298322c..51afdab9d8e3 100644 --- a/translations/zh-CN/content/rest/reference/enterprise-admin.md +++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md @@ -24,7 +24,7 @@ You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints ### 端点 URL -REST API endpoints{% if enterpriseServerVersions contains currentVersion %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: +REST API 端点{% if enterpriseServerVersions contains currentVersion %}— [管理控制台](#management-console) API 端点除外—{% endif %} 是以下 URL 的前缀： ```shell http(s)://hostname/api/v3/ @@ -42,14 +42,14 @@ http(s)://hostname/ {% data variables.product.product_name %} 安装设施的 API 端点接受与 GitHub.com [相同的身份验证方法](/rest/overview/resources-in-the-rest-api#authentication)。 您可以使用 **[OAuth 令牌](/apps/building-integrations/setting-up-and-registering-oauth-apps/)**（可使用[授权 API](/rest/reference/oauth-authorizations#create-a-new-authorization) 创建）或**[基本身份验证](/rest/overview/resources-in-the-rest-api#basic-authentication)**来验证自己。 {% if enterpriseServerVersions contains currentVersion %} OAuth 令牌用于企业特定的端点时必须具有 `site_admin` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps#available-scopes)。{% endif %} -Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% if enterpriseServerVersions contains currentVersion %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. +企业管理 API 端点只有经过身份验证的 {% data variables.product.product_name %} 站点管理员可以访问{% if enterpriseServerVersions contains currentVersion %}，但[管理控制台](#management-console) API 例外，它需要[管理控制台密码](/enterprise/admin/articles/accessing-the-management-console/){% endif %}。 {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} ### 版本信息 -The current version of your enterprise is returned in the response header of every API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` You can also read the current version by calling the [meta endpoint](/rest/reference/meta/). +每个 API 的响应标头中都会返回企业的当前版本：`X-GitHub-Enterprise-Version: {{currentVersion}}.0` 您也可以通过调用[元端点](/rest/reference/meta/)来读取当前版本。 {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -140,9 +140,9 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} {% if currentVersion == "github-ae@latest" %} -## Encryption at rest +## 休息时加密 -You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)." +您可以使用休息时加密 API 来管理用于对 {% data variables.product.product_name %} 上的数据进行加密的密钥。 更多信息请参阅“[为企业配置数据加密](/admin/configuration/configuring-data-encryption-for-your-enterprise)”。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %} @@ -163,9 +163,9 @@ You can use the encryption at rest API to manage the key that encrypts your data {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -## Announcements +## 公告 -The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." +公告 API 允许您管理企业中的全局公告横幅。 更多信息请参阅“[自定义企业的用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)”。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %} @@ -177,7 +177,7 @@ The Announcements API allows you to manage the global announcement banner in you ## 全局 web 挂钩 -Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. 全局 web 挂钩可以订阅[组织](/developers/webhooks-and-events/webhook-events-and-payloads#organization)、[用户](/developers/webhooks-and-events/webhook-events-and-payloads#user)、[仓库](/developers/webhooks-and-events/webhook-events-and-payloads#repository)、[团队](/developers/webhooks-and-events/webhook-events-and-payloads#team)、[成员](/developers/webhooks-and-events/webhook-events-and-payloads#member)、[成员身份](/developers/webhooks-and-events/webhook-events-and-payloads#membership)、[复刻](/developers/webhooks-and-events/webhook-events-and-payloads#fork)和 [ping](/developers/webhooks-and-events/about-webhooks#ping-event) 事件类型。 +全局 web 挂钩安装在企业上。 您可以使用全局 web 挂钩来自动监视、响应或实施针对企业上的用户、组织、团队和仓库的规则。 全局 web 挂钩可以订阅[组织](/developers/webhooks-and-events/webhook-events-and-payloads#organization)、[用户](/developers/webhooks-and-events/webhook-events-and-payloads#user)、[仓库](/developers/webhooks-and-events/webhook-events-and-payloads#repository)、[团队](/developers/webhooks-and-events/webhook-events-and-payloads#team)、[成员](/developers/webhooks-and-events/webhook-events-and-payloads#member)、[成员身份](/developers/webhooks-and-events/webhook-events-and-payloads#membership)、[复刻](/developers/webhooks-and-events/webhook-events-and-payloads#fork)和 [ping](/developers/webhooks-and-events/about-webhooks#ping-event) 事件类型。 *此 API 只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。 要了解如何配置全局 web 挂钩，请参阅[关于全局 web 挂钩](/enterprise/admin/user-management/about-global-webhooks)。 @@ -221,7 +221,7 @@ Global webhooks are installed on your enterprise. You can use global webhooks to {% tip %} -在对管理控制台进行 API 调用时，必须明确设置端口号。 If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`. +在对管理控制台进行 API 调用时，必须明确设置端口号。 如果在企业上启用了 TLS，则端口号为 `8443`；否则，端口号为 `8080`。 如果您不想提供端口号，则需要将工具配置为自动遵循重定向。 @@ -254,7 +254,7 @@ $ curl -L 'https://api_key:your-amazing-password@hostname: {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} ## 组织 -The Organization Administration API allows you to create organizations on your enterprise. *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。 +组织管理 API 允许您在企业上创建组织。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} @@ -374,7 +374,7 @@ The Organization Administration API allows you to create organizations on your e {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} ## 用户 -The User Administration API allows you to suspend{% if enterpriseServerVersions contains currentVersion %}, unsuspend, promote, and demote{% endif %}{% if currentVersion == "github-ae@latest" %} and unsuspend{% endif %} users on your enterprise. *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `403` 响应。 +用户管理 API 允许您暂停{% if enterpriseServerVersions contains currentVersion %}、取消暂停、升级和降级{% endif %}{% if currentversion == "github-ae@latest" %} 以及取消暂停{% endif %} 企业上的用户。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `403` 响应。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} diff --git a/translations/zh-CN/content/rest/reference/gists.md b/translations/zh-CN/content/rest/reference/gists.md index 97127193a929..74f4d71acaa4 100644 --- a/translations/zh-CN/content/rest/reference/gists.md +++ b/translations/zh-CN/content/rest/reference/gists.md @@ -10,7 +10,7 @@ versions: ### 身份验证 -You can read public gists {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}and create them for anonymous users without a token.{% else %} anonymously, but you must be signed into GitHub to create gists.{% endif %} To read or write gists on a user's behalf, you need the gist OAuth scope and a token. 更多信息请参阅“[OAuth 应用程序的作用域](/developers/apps/scopes-for-oauth-apps)”。 +您可以匿名读取公开 Gist {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}并为没有令牌的匿名用户创建它们。{% else %}，但是您必须登录到 GitHub 才能创建 Gist。{% endif %} 要代表用户读取或写入 Gist，您需要 Gist OAuth 作用域和令牌。 更多信息请参阅“[OAuth 应用程序的作用域](/developers/apps/scopes-for-oauth-apps)”。 diff --git a/translations/zh-CN/content/rest/reference/interactions.md b/translations/zh-CN/content/rest/reference/interactions.md index e9ae08c8a7b8..74c5ba2ae5e1 100644 --- a/translations/zh-CN/content/rest/reference/interactions.md +++ b/translations/zh-CN/content/rest/reference/interactions.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -用户通过评论、开设议题和创建拉取请求与仓库进行交互。 交互 API 允许具有所有者或管理员权限的用户临时限制某些用户与公共仓库交互。 +用户通过评论、开设议题和创建拉取请求与仓库进行交互。 交互 API 允许具有公共仓库所有者或具有管理员访问权限的用户临时将与公共仓库的交互限于特定类型的用户。 {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -14,24 +14,42 @@ versions: ## 组织 -组织交互 API 允许组织所有者临时限制哪些用户可以在组织的公共仓库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户组的更多信息： +组织交互 API 允许组织所有者临时限制哪类用户可以在组织的公共仓库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息： * 组织中的 {% data reusables.interactions.existing-user-limit-definition %}。 * 组织中的 {% data reusables.interactions.contributor-user-limit-definition %}。 * 组织中的 {% data reusables.interactions.collaborator-user-limit-definition %}。 +在组织级别设置交互限制将覆盖为组织拥有的各个仓库设置的任何交互限制。 要为组织拥有的各个仓库设置不同的交互限制，请改用[仓库](#repository)交互端点。 + {% for operation in currentRestOperations %} {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} {% endfor %} ## 仓库 -仓库交互 API 允许具有所有者或管理员权限的用户临时限制哪些用户可以在公共存储库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户组的更多信息： +仓库交互 API 允许具有所有者或管理员权限的用户临时限制哪类用户可以在公共仓库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息： * 仓库中的 {% data reusables.interactions.existing-user-limit-definition %}。 * 仓库中的 {% data reusables.interactions.contributor-user-limit-definition %}。 * 仓库中的 {% data reusables.interactions.collaborator-user-limit-definition %}。 +如果对拥有该仓库的用户或组织启用了交互限制，单个仓库的限制就不能更改。 而应使用[用户](#user)或[组织](#organization)交互端点来更改交互限制。 + {% for operation in currentRestOperations %} {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %} {% endfor %} + +## 用户 + +用户交互 API 允许您临时限制哪类用户可以在公共仓库上发表评论、开设问题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息： + +* 与仓库交互产生的 {% data reusables.interactions.existing-user-limit-definition %}。 +* 与仓库交互产生的 {% data reusables.interactions.contributor-user-limit-definition %}。 +* 与仓库交互产生的 {% data reusables.interactions.collaborator-user-limit-definition %}。 + +在用户级别设置交互限制将覆盖为用户拥有的各个仓库设置的任何交互限制。 要为用户拥有的个别仓库设置不同的交互限制，请使用[仓库](#repository)交互端点。 + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/zh-CN/content/rest/reference/oauth-authorizations.md b/translations/zh-CN/content/rest/reference/oauth-authorizations.md index 44f399bc0789..567475c739fe 100644 --- a/translations/zh-CN/content/rest/reference/oauth-authorizations.md +++ b/translations/zh-CN/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 %} - 您可以使用此 API 来管理 OAuth 应用程序对您帐户的访问权限。 您只能使用您的用户名和密码（而不是令牌），通过[基本身份验证](/rest/overview/other-authentication-methods#basic-authentication)访问此 API。 如果您或您的用户启用了双重身份验证，请务必了解如何[使用双重身份验证](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)。 diff --git a/translations/zh-CN/content/rest/reference/orgs.md b/translations/zh-CN/content/rest/reference/orgs.md index 18afff94eadd..e1102e4e6ad6 100644 --- a/translations/zh-CN/content/rest/reference/orgs.md +++ b/translations/zh-CN/content/rest/reference/orgs.md @@ -38,7 +38,7 @@ versions: ## Web 挂钩 -组织 web 挂钩允许您在组织内发生特定事件时接收 HTTP `POST` 有效负载。 Subscribing to these events makes it possible to build integrations that react to events on {% data variables.product.product_name %}. 有关您可以订阅的操作的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 事件类型](/developers/webhooks-and-events/github-event-types)”。 +组织 web 挂钩允许您在组织内发生特定事件时接收 HTTP `POST` 有效负载。 订阅这些事件可以构建对 {% data variables.product.product_name %} 上的事件做出反应的集成。 有关您可以订阅的操作的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 事件类型](/developers/webhooks-and-events/github-event-types)”。 ### 范围和限制 diff --git a/translations/zh-CN/content/rest/reference/search.md b/translations/zh-CN/content/rest/reference/search.md index 2f3ac95f73f8..929061e2ba7a 100644 --- a/translations/zh-CN/content/rest/reference/search.md +++ b/translations/zh-CN/content/rest/reference/search.md @@ -28,16 +28,22 @@ versions: 搜索 API 中的每个端点都使用[查询参数](https://en.wikipedia.org/wiki/Query_string)对 {% data variables.product.product_name %} 进行搜索。 有关包含端点和查询参数的示例，请参阅搜索 API 中的各个端点。 -A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. 搜索查询的格式为： +查询可以包含在 {% data variables.product.product_name %} 上支持的搜索限定符的任意组合中。 搜索查询的格式为： ``` -q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N +SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N ``` 例如，如果您要搜索 `defunkt` 拥有的在自述文件中包含单词 `GitHub` 和 `Octocat` 的所有_仓库_，您可以在_搜索仓库_端点中使用以下查询： ``` -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. 例如： +```javascript +// JavaScript +const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` 有关可用限定符及其格式的完整列表和使用示例，请参阅“[在 GitHub 上搜索](/articles/searching-on-github/)”。 有关如何使用运算符匹配特定数量、日期或排除结果，请参阅“[了解搜索语法](/articles/understanding-the-search-syntax/)”。 diff --git a/translations/zh-CN/content/rest/reference/users.md b/translations/zh-CN/content/rest/reference/users.md index 38ace0846310..89e3300aee4f 100644 --- a/translations/zh-CN/content/rest/reference/users.md +++ b/translations/zh-CN/content/rest/reference/users.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -用户 API 上的许多资源提供了快捷方式，可用于获取有关当前经过身份验证的用户的信息。 If a request URL does not include a `{username}` parameter then the response will be for the logged in user (and you must pass [authentication information](/rest/overview/resources-in-the-rest-api#authentication) with your request).{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} Additional private information, such as whether a user has two-factor authentication enabled, is included when authenticated through basic auth or OAuth with the `user` scope.{% endif %} +用户 API 上的许多资源提供了快捷方式，可用于获取有关当前经过身份验证的用户的信息。 如果请求 URL 不含 `{username}` 参数，则响应将是登录用户的响应（您必须随请求传递[身份验证信息](/rest/overview/resources-in-the-rest-api#authentication)）。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} 在通过基本身份验证或作用域为 `user` 的 OAuth 进行身份验证时，将包含其他私有信息，例如用户是否启用双重身份验证。{% endif %} {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml index d77f2c999693..2428be2110fd 100644 --- a/translations/zh-CN/data/glossaries/external.yml +++ b/translations/zh-CN/data/glossaries/external.yml @@ -61,7 +61,7 @@ - term: 分支 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. + 分支是仓库的平行版本。它包含在仓库中，但不影响主要或 master 分支，可让您自由工作而不中断“即时”版本。在执行所需的更改后，可以将分支合并回 master 分支以发布更改。 - term: 分支限制 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. + 默认开发分支。只要创建 Git 仓库，就会创建一个名为 "main" 的分支，并且它会变为活动的分支。大多数情况下，这包含本地开发，但纯属惯例，而非必需。 - term: master 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`. + 许多 Git 存储库中的默认分支。默认情况下，在命令行上创建新的 Git 仓库时，将创建一个名为 "master" 的分支。许多工具现在对默认分支使用替代名称。例如，在 GitHub 上创建新仓库时，默认分支称为 "main"。 - term: 成员图 description: 显示仓库所有分叉的仓库图。 diff --git a/translations/zh-CN/data/graphql/ghae/graphql_previews.ghae.yml b/translations/zh-CN/data/graphql/ghae/graphql_previews.ghae.yml index 23ff7ab7dd59..f34be4a794c6 100644 --- a/translations/zh-CN/data/graphql/ghae/graphql_previews.ghae.yml +++ b/translations/zh-CN/data/graphql/ghae/graphql_previews.ghae.yml @@ -85,7 +85,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: 固定议题预览 description: 此预览增加了对固定议题的支持。 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 e382d3d36899..f73100b64db2 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 @@ -2,112 +2,112 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。" - reason: "`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。" + description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' + reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: AssignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。" - reason: "`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值" + description: '`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。' + reason: '`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。" - reason: "`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值" + description: '`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。' + reason: '`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。" - reason: "`Sponsorship.maintainer` 将被删除。" + description: '`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。' + reason: '`Sponsorship.maintainer` 将被删除。' date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有挂起的成员都会使用许可证 date: '2020-07-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。" + description: '`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。' reason: 仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。 date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: jdennes - location: Issue.timeline - description: "`timeline` 将被删除。使用 Issue.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: PullRequest.timeline - description: "`timeline` 将被删除。使用 PullRequest.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` 将被删除。" - reason: "`INVITEE_LOGIN` 不再是有效字段值。仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。" + description: '`INVITEE_LOGIN` 将被删除。' + reason: '`INVITEE_LOGIN` 不再是有效字段值。仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` 将被删除。改用 `Sponsorship.sponsorEntity`。" - reason: "`Sponsorship.sponsor` 将被删除。" + description: '`sponsor` 将被删除。改用 `Sponsorship.sponsorEntity`。' + reason: '`Sponsorship.sponsor` 将被删除。' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有成员都会使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有外部协作者使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有挂起的协作者使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` 将被删除。改为使用 PullRequest.isDraft。" + description: '`DRAFT` 将被删除。改为使用 PullRequest.isDraft。' reason: DRAFT 状态将从这个枚举中删除，应改用 `isDraft` date: '2021-01-01T00:00:00+00:00' criticality: 重大 diff --git a/translations/zh-CN/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml index 68c63dd55cb2..6dbd72d8f4c1 100644 --- a/translations/zh-CN/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/zh-CN/data/graphql/ghes-2.19/graphql_upcoming_changes.public-enterprise.yml @@ -2,63 +2,63 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。" - reason: "`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。" + description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' + reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: ContributionOrder.field - description: "`field` 将被删除。只支持一个顺序字段。" - reason: "`field` 将被删除。" + description: '`field` 将被删除。只支持一个顺序字段。' + reason: '`field` 将被删除。' date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Issue.timeline - description: "`timeline` 将被删除。使用 Issue.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` 将被删除。使用 PullRequest.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: AssignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: UnassignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 diff --git a/translations/zh-CN/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml index 19c09fa571de..66d125b08e44 100644 --- a/translations/zh-CN/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/zh-CN/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml @@ -2,560 +2,560 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。" - reason: "`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。" + description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' + reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: ContributionOrder.field - description: "`field` 将被删除。只支持一个顺序字段。" - reason: "`field` 将被删除。" + description: '`field` 将被删除。只支持一个顺序字段。' + reason: '`field` 将被删除。' date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Issue.timeline - description: "`timeline` 将被删除。使用 Issue.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: Organization.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: PullRequest.timeline - description: "`timeline` 将被删除。使用 PullRequest.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: AssignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。" - reason: "`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值" + description: '`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。' + reason: '`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。" - reason: "`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值" + description: '`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。' + reason: '`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: Organization.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.color - description: "`color` 将被删除。使用 `Package` 对象代替。" + description: '`color` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` 将被删除。使用 `Package` 对象代替。" + description: '`latestVersion` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.name - description: "`name` 将被删除。使用 `Package` 对象代替。" + description: '`name` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` 将被删除。使用 `Package` 对象代替。" + description: '`nameWithOwner` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` 将被删除。使用 `Package` 对象。" + description: '`packageFileByGuid` 将被删除。使用 `Package` 对象。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` 将被删除。使用 `Package` 对象。" + description: '`packageFileBySha256` 将被删除。使用 `Package` 对象。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` 将被删除。使用 `Package` 对象代替。" + description: '`packageType` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` 将被删除。使用 `Package` 对象代替。" + description: '`preReleaseVersions` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` 将被删除。使用 `Package` 对象代替。" + description: '`registryPackageType` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.repository - description: "`repository` 将被删除。使用 `Package` 对象代替。" + description: '`repository` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` 将被删除。使用 `Package` 对象代替。" + description: '`statistics` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.tags - description: "`tags` 将被删除。使用 `Package` 对象代替。" + description: '`tags` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.topics - description: "`topics` 将被删除。使用 `Package` 对象代替。" + description: '`topics` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.version - description: "`version` 将被删除。使用 `Package` 对象代替。" + description: '`version` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` 将被删除。使用 `Package` 对象代替。" + description: '`versionByPlatform` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` 将被删除。使用 `Package` 对象代替。" + description: '`versionBySha256` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versions - description: "`versions` 将被删除。使用 `Package` 对象代替。" + description: '`versions` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` 将被删除。使用 `Package` 对象代替。" + description: '`versionsByMetadatum` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` 将被删除。使用 `PackageDependency` 对象代替。" + description: '`dependencyType` 将被删除。使用 `PackageDependency` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` 将被删除。使用 `PackageDependency` 对象代替。" + description: '`name` 将被删除。使用 `PackageDependency` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` 将被删除。使用 `PackageDependency` 对象代替。" + description: '`version` 将被删除。使用 `PackageDependency` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` 将被删除。使用 `PackageFile` 对象代替。" + description: '`guid` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` 将被删除。使用 `PackageFile` 对象代替。" + description: '`md5` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` 将被删除。使用 `PackageFile` 对象代替。" + description: '`metadataUrl` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.name - description: "`name` 将被删除。使用 `PackageFile` 对象代替。" + description: '`name` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` 将被删除。使用 `PackageFile` 对象代替。" + description: '`packageVersion` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` 将被删除。使用 `PackageFile` 对象代替。" + description: '`sha1` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` 将被删除。使用 `PackageFile` 对象代替。" + description: '`sha256` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.size - description: "`size` 将被删除。使用 `PackageFile` 对象代替。" + description: '`size` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.url - description: "`url` 将被删除。使用 `PackageFile` 对象代替。" + description: '`url` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsThisMonth` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsThisWeek` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsThisYear` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsToday` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsTotalCount` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageTag.name - description: "`name` 将被删除。使用 `PackageTag` 对象代替。" + description: '`name` 将被删除。使用 `PackageTag` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageTag.version - description: "`version` 将被删除。使用 `PackageTag` 对象代替。" + description: '`version` 将被删除。使用 `PackageTag` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`dependencies` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`fileByName` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`files` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`installationCommand` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`manifest` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`platform` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`preRelease` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`readme` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`readmeHtml` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`registryPackage` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`release` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`sha256` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`size` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`statistics` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`summary` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`updatedAt` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`version` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`viewerCanEdit` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsThisMonth` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsThisWeek` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsThisYear` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsToday` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsTotalCount` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。" - reason: "`Sponsorship.maintainer` 将被删除。" + description: '`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。' + reason: '`Sponsorship.maintainer` 将被删除。' date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: antn - location: User.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 diff --git a/translations/zh-CN/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml index c5d9fe486310..e059e78ee968 100644 --- a/translations/zh-CN/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/zh-CN/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml @@ -2,568 +2,568 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。" - reason: "`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。" + description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' + reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: ContributionOrder.field - description: "`field` 将被删除。只支持一个顺序字段。" - reason: "`field` 将被删除。" + description: '`field` 将被删除。只支持一个顺序字段。' + reason: '`field` 将被删除。' date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Organization.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: RepositoryOwner.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: User.pinnedRepositories - description: "`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。" + description: '`pinnedRepositories` 将被删除。使用 ProfileOwner.pinnedites 代替。' reason: pinnedRepositories 将被删除 date: '2019-10-01T00:00:00+00:00' criticality: 重大 owner: cheshire137 - location: AssignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。" - reason: "`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值" + description: '`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。' + reason: '`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。" - reason: "`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值" + description: '`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。' + reason: '`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: Organization.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Organization.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.color - description: "`color` 将被删除。使用 `Package` 对象代替。" + description: '`color` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.latestVersion - description: "`latestVersion` 将被删除。使用 `Package` 对象代替。" + description: '`latestVersion` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.name - description: "`name` 将被删除。使用 `Package` 对象代替。" + description: '`name` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.nameWithOwner - description: "`nameWithOwner` 将被删除。使用 `Package` 对象代替。" + description: '`nameWithOwner` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.packageFileByGuid - description: "`packageFileByGuid` 将被删除。使用 `Package` 对象。" + description: '`packageFileByGuid` 将被删除。使用 `Package` 对象。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.packageFileBySha256 - description: "`packageFileBySha256` 将被删除。使用 `Package` 对象。" + description: '`packageFileBySha256` 将被删除。使用 `Package` 对象。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.packageType - description: "`packageType` 将被删除。使用 `Package` 对象代替。" + description: '`packageType` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.preReleaseVersions - description: "`preReleaseVersions` 将被删除。使用 `Package` 对象代替。" + description: '`preReleaseVersions` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.registryPackageType - description: "`registryPackageType` 将被删除。使用 `Package` 对象代替。" + description: '`registryPackageType` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.repository - description: "`repository` 将被删除。使用 `Package` 对象代替。" + description: '`repository` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.statistics - description: "`statistics` 将被删除。使用 `Package` 对象代替。" + description: '`statistics` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.tags - description: "`tags` 将被删除。使用 `Package` 对象代替。" + description: '`tags` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.topics - description: "`topics` 将被删除。使用 `Package` 对象代替。" + description: '`topics` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.version - description: "`version` 将被删除。使用 `Package` 对象代替。" + description: '`version` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versionByPlatform - description: "`versionByPlatform` 将被删除。使用 `Package` 对象代替。" + description: '`versionByPlatform` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versionBySha256 - description: "`versionBySha256` 将被删除。使用 `Package` 对象代替。" + description: '`versionBySha256` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versions - description: "`versions` 将被删除。使用 `Package` 对象代替。" + description: '`versions` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackage.versionsByMetadatum - description: "`versionsByMetadatum` 将被删除。使用 `Package` 对象代替。" + description: '`versionsByMetadatum` 将被删除。使用 `Package` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageDependency.dependencyType - description: "`dependencyType` 将被删除。使用 `PackageDependency` 对象代替。" + description: '`dependencyType` 将被删除。使用 `PackageDependency` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageDependency.name - description: "`name` 将被删除。使用 `PackageDependency` 对象代替。" + description: '`name` 将被删除。使用 `PackageDependency` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageDependency.version - description: "`version` 将被删除。使用 `PackageDependency` 对象代替。" + description: '`version` 将被删除。使用 `PackageDependency` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.guid - description: "`guid` 将被删除。使用 `PackageFile` 对象代替。" + description: '`guid` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.md5 - description: "`md5` 将被删除。使用 `PackageFile` 对象代替。" + description: '`md5` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.metadataUrl - description: "`metadataUrl` 将被删除。使用 `PackageFile` 对象代替。" + description: '`metadataUrl` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.name - description: "`name` 将被删除。使用 `PackageFile` 对象代替。" + description: '`name` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.packageVersion - description: "`packageVersion` 将被删除。使用 `PackageFile` 对象代替。" + description: '`packageVersion` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.sha1 - description: "`sha1` 将被删除。使用 `PackageFile` 对象代替。" + description: '`sha1` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.sha256 - description: "`sha256` 将被删除。使用 `PackageFile` 对象代替。" + description: '`sha256` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.size - description: "`size` 将被删除。使用 `PackageFile` 对象代替。" + description: '`size` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageFile.url - description: "`url` 将被删除。使用 `PackageFile` 对象代替。" + description: '`url` 将被删除。使用 `PackageFile` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageOwner.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageSearch.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisMonth - description: "`downloadsThisMonth` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsThisMonth` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisWeek - description: "`downloadsThisWeek` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsThisWeek` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsThisYear - description: "`downloadsThisYear` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsThisYear` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsToday - description: "`downloadsToday` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsToday` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageStatistics.downloadsTotalCount - description: "`downloadsTotalCount` 将被删除。使用 `PackageStatistics` 对象代替。" + description: '`downloadsTotalCount` 将被删除。使用 `PackageStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageTag.name - description: "`name` 将被删除。使用 `PackageTag` 对象代替。" + description: '`name` 将被删除。使用 `PackageTag` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageTag.version - description: "`version` 将被删除。使用 `PackageTag` 对象代替。" + description: '`version` 将被删除。使用 `PackageTag` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.deleted - description: "`deleted` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`deleted` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.dependencies - description: "`dependencies` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`dependencies` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.fileByName - description: "`fileByName` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`fileByName` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.files - description: "`files` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`files` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.installationCommand - description: "`installationCommand` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`installationCommand` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.manifest - description: "`manifest` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`manifest` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.platform - description: "`platform` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`platform` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.preRelease - description: "`preRelease` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`preRelease` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.readme - description: "`readme` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`readme` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.readmeHtml - description: "`readmeHtml` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`readmeHtml` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.registryPackage - description: "`registryPackage` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`registryPackage` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.release - description: "`release` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`release` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.sha256 - description: "`sha256` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`sha256` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.size - description: "`size` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`size` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.statistics - description: "`statistics` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`statistics` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.summary - description: "`summary` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`summary` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.updatedAt - description: "`updatedAt` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`updatedAt` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.version - description: "`version` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`version` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersion.viewerCanEdit - description: "`viewerCanEdit` 将被删除。使用 `PackageVersion` 对象代替。" + description: '`viewerCanEdit` 将被删除。使用 `PackageVersion` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "`downloadsThisMonth` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsThisMonth` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "`downloadsThisWeek` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsThisWeek` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "`downloadsThisYear` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsThisYear` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsToday - description: "`downloadsToday` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsToday` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "`downloadsTotalCount` 将被删除。使用 `PackageVersionStatistics` 对象代替。" + description: '`downloadsTotalCount` 将被删除。使用 `PackageVersionStatistics` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Repository.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Repository.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Sponsorship.maintainer - description: "`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。" - reason: "`Sponsorship.maintainer` 将被删除。" + description: '`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。' + reason: '`Sponsorship.maintainer` 将被删除。' date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: antn - location: User.registryPackages - description: "`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。" + description: '`registryPackages` 将被删除。使用 `PackageOwner` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: User.registryPackagesForQuery - description: "`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。" + description: '`registryPackagesForQuery` 将被删除。使用 `PackageSearch` 对象代替。' reason: 重命名 GitHub 包字段和对象。 date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: dinahshi - location: Issue.timeline - description: "`timeline` 将被删除。使用 Issue.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: PullRequest.timeline - description: "`timeline` 将被删除。使用 PullRequest.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea diff --git a/translations/zh-CN/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml index 4acc318c988b..b1b0e39037cb 100644 --- a/translations/zh-CN/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/zh-CN/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml @@ -2,71 +2,71 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。" - reason: "`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。" + description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' + reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: AssignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。" - reason: "`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值" + description: '`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。' + reason: '`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。" - reason: "`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值" + description: '`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。' + reason: '`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: Sponsorship.maintainer - description: "`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。" - reason: "`Sponsorship.maintainer` 将被删除。" + description: '`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。' + reason: '`Sponsorship.maintainer` 将被删除。' date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有挂起的成员都会使用许可证 date: '2020-07-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。" + description: '`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。' reason: 仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。 date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: jdennes - location: Issue.timeline - description: "`timeline` 将被删除。使用 Issue.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: PullRequest.timeline - description: "`timeline` 将被删除。使用 PullRequest.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea @@ -86,15 +86,15 @@ upcoming_changes: owner: oneill38 - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` 将被删除。" - reason: "`INVITEE_LOGIN` 不再是有效字段值。仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。" + description: '`INVITEE_LOGIN` 将被删除。' + reason: '`INVITEE_LOGIN` 不再是有效字段值。仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` 将被删除。改用 `Sponsorship.sponsorEntity`。" - reason: "`Sponsorship.sponsor` 将被删除。" + description: '`sponsor` 将被删除。改用 `Sponsorship.sponsorEntity`。' + reason: '`Sponsorship.sponsor` 将被删除。' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: nholden @@ -107,21 +107,21 @@ upcoming_changes: owner: oneill38 - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有成员都会使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有外部协作者使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有挂起的协作者使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 diff --git a/translations/zh-CN/data/graphql/graphql_previews.yml b/translations/zh-CN/data/graphql/graphql_previews.yml index 01f33a2798a6..1672f2aa196f 100644 --- a/translations/zh-CN/data/graphql/graphql_previews.yml +++ b/translations/zh-CN/data/graphql/graphql_previews.yml @@ -102,7 +102,7 @@ toggled_on: - Mutation.createContentAttachment owning_teams: - - '@github/ce-extensibility' + - '@github/feature-lifecycle' - title: 固定议题预览 description: 此预览增加了对固定议题的支持。 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 2444badea947..cce0d5621200 100644 --- a/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml @@ -2,119 +2,119 @@ upcoming_changes: - location: Migration.uploadUrlTemplate - description: "`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。" - reason: "`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。" + description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' + reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' date: '2019-04-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: AssignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: EnterpriseBillingInfo.availableSeats - description: "`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。" - reason: "`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值" + description: '`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。' + reason: '`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: EnterpriseBillingInfo.seats - description: "`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。" - reason: "`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值" + description: '`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。' + reason: '`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值' date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: BlakeWilliams - location: UnassignedEvent.user - description: "`user` 将被删除。使用 `assignee` 字段代替。" + description: '`user` 将被删除。使用 `assignee` 字段代替。' reason: 受理人现在可以作为人体模型。 date: '2020-01-01T00:00:00+00:00' criticality: 重大 owner: tambling - location: Query.sponsorsListing - description: "`sponsorsListing` 将被删除。使用 `Sponsorable.sponsorsListing` 代替。" - reason: "`Query.sponsorsListing` 将被删除。" + description: '`sponsorsListing` 将被删除。使用 `Sponsorable.sponsorsListing` 代替。' + reason: '`Query.sponsorsListing` 将被删除。' date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: antn - location: Sponsorship.maintainer - description: "`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。" - reason: "`Sponsorship.maintainer` 将被删除。" + description: '`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。' + reason: '`Sponsorship.maintainer` 将被删除。' date: '2020-04-01T00:00:00+00:00' criticality: 重大 owner: antn - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有挂起的成员都会使用许可证 date: '2020-07-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterpriseOwnerInfo.pendingCollaborators - description: "`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。" + description: '`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。' reason: 仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。 date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: jdennes - location: Issue.timeline - description: "`timeline` 将被删除。使用 Issue.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: PullRequest.timeline - description: "`timeline` 将被删除。使用 PullRequest.timelineItems 代替。" - reason: "`timeline` 将被删除" + description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。' + reason: '`timeline` 将被删除' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: mikesea - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "`INVITEE_LOGIN` 将被删除。" - reason: "`INVITEE_LOGIN` 不再是有效字段值。仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。" + description: '`INVITEE_LOGIN` 将被删除。' + reason: '`INVITEE_LOGIN` 不再是有效字段值。仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: jdennes - location: Sponsorship.sponsor - description: "`sponsor` 将被删除。改用 `Sponsorship.sponsorEntity`。" - reason: "`Sponsorship.sponsor` 将被删除。" + description: '`sponsor` 将被删除。改用 `Sponsorship.sponsorEntity`。' + reason: '`Sponsorship.sponsor` 将被删除。' date: '2020-10-01T00:00:00+00:00' criticality: 重大 owner: nholden - location: EnterpriseMemberEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有成员都会使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有外部协作者使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "`isUnlicensed` 将被删除。" + description: '`isUnlicensed` 将被删除。' reason: 所有挂起的协作者使用许可证 date: '2021-01-01T00:00:00+00:00' criticality: 重大 owner: BrentWheeldon - location: MergeStateStatus.DRAFT - description: "`DRAFT` 将被删除。改为使用 PullRequest.isDraft。" + description: '`DRAFT` 将被删除。改为使用 PullRequest.isDraft。' reason: DRAFT 状态将从这个枚举中删除，应改用 `isDraft` date: '2021-01-01T00:00:00+00:00' criticality: 重大 diff --git a/translations/zh-CN/data/reusables/enterprise_installation/disable-github-pages-warning.md b/translations/zh-CN/data/reusables/enterprise_installation/disable-github-pages-warning.md index ecac6ccacbf0..c03db262a489 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/disable-github-pages-warning.md +++ b/translations/zh-CN/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/)." +**Warning:** If subdomain isolation is disabled, we recommend also disabling {% data variables.product.prodname_pages %} on your enterprise. 无法将用户提供的 {% data variables.product.prodname_pages %} 内容与其余企业数据分隔。 更多信息请参阅“[为企业配置 {% data variables.product.prodname_pages %}](/enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/)”。 {% endwarning %} {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-code-scanning.md b/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-code-scanning.md index e6857e58928c..a82992ae5605 100644 --- a/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-code-scanning.md +++ b/translations/zh-CN/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. 您应谨慎安排更改时间，以尽量减少停机时间。 +**警告**：更改此设置将导致 {% 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 %} 重启。 您应谨慎安排更改时间，以尽量减少停机时间。 {% endwarning %} diff --git a/translations/zh-CN/data/reusables/feature-preview/feature-preview-setting.md b/translations/zh-CN/data/reusables/feature-preview/feature-preview-setting.md new file mode 100644 index 000000000000..0d12c5d5ab55 --- /dev/null +++ b/translations/zh-CN/data/reusables/feature-preview/feature-preview-setting.md @@ -0,0 +1 @@ +1. 在任何页面的右上角，单击您的个人资料照片，然后单击 **Feature preview（功能预览）**。 ![功能预览按钮](/assets/images/help/settings/feature-preview-button.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/gated-features/draft-prs.md b/translations/zh-CN/data/reusables/gated-features/draft-prs.md index 9c53c6d6c05e..613f2cdae522 100644 --- a/translations/zh-CN/data/reusables/gated-features/draft-prs.md +++ b/translations/zh-CN/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 %} +拉取请求草稿可用于具有组织的 {% data variables.product.prodname_free_team %} 和传统的按仓库结算方案的公共仓库，以及具有 {% 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 %} 和 {% data variables.product.prodname_ghe_cloud %} 的公共和私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md b/translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md index c03039c9e98d..881de3dfa3d3 100644 --- a/translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md +++ b/translations/zh-CN/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" %}更多信息请参阅“[关于企业帐户](/articles/about-enterprise-accounts)”。{% endif %} +企业帐户可用于 {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}、{% data variables.product.prodname_ghe_managed %}、{% endif %} 和 {% data variables.product.prodname_ghe_server %}。 {% if currentVersion == "free-pro-team@latest" %}更多信息请参阅“[关于企业帐户](/articles/about-enterprise-accounts)”。{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/internal-repos.md b/translations/zh-CN/data/reusables/gated-features/internal-repos.md index d0cff1ba1179..2664e0616b06 100644 --- a/translations/zh-CN/data/reusables/gated-features/internal-repos.md +++ b/translations/zh-CN/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+. 更多信息请参阅“GitHub's products”。 +内部仓库可用于 {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}、{% data variables.product.prodname_ghe_managed %}、{% endif %} 和 {% data variables.product.prodname_ghe_server %} 2.20+。 更多信息请参阅“GitHub's products”。 diff --git a/translations/zh-CN/data/reusables/gated-features/pages.md b/translations/zh-CN/data/reusables/gated-features/pages.md index e24925cc9877..06a1c92dfa65 100644 --- a/translations/zh-CN/data/reusables/gated-features/pages.md +++ b/translations/zh-CN/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 %} +{% data variables.product.prodname_pages %} 适用于具有 {% data variables.product.prodname_free_user %} 和组织的 {% data variables.product.prodname_free_team %} 的公共仓库，以及具有 {% 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 %} 和 {% data variables.product.prodname_ghe_server %} 的公共和私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/protected-branches.md b/translations/zh-CN/data/reusables/gated-features/protected-branches.md index a9745fcec2b6..c5b2cde05ba7 100644 --- a/translations/zh-CN/data/reusables/gated-features/protected-branches.md +++ b/translations/zh-CN/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 %} +受保护分支适用于具有 {% data variables.product.prodname_free_user %} 和组织的 {% data variables.product.prodname_free_team %} 的公共仓库，以及具有 {% 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 %} 和 {% data variables.product.prodname_ghe_server %} 的公共和私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/repository-insights.md b/translations/zh-CN/data/reusables/gated-features/repository-insights.md index 71016e9f967d..276ba4dea848 100644 --- a/translations/zh-CN/data/reusables/gated-features/repository-insights.md +++ b/translations/zh-CN/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 %} +此仓库洞察图可用于具有 {% data variables.product.prodname_free_user %} 和组织的 {% data variables.product.prodname_free_team %} 的公共仓库，以及具有 {% 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 %} 和 {% data variables.product.prodname_ghe_server %} 的公共和私有仓库。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[关于仓库图](/articles/about-repository-graphs)”和“[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)”。{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/saml-sso.md b/translations/zh-CN/data/reusables/gated-features/saml-sso.md index 51fda0fb6f28..089e659d999c 100644 --- a/translations/zh-CN/data/reusables/gated-features/saml-sso.md +++ b/translations/zh-CN/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 %}. 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 +SAML 单点登录可用于 {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} 和 {% data variables.product.prodname_ghe_managed %}{% endif %}。 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 diff --git a/translations/zh-CN/data/reusables/gated-features/secret-scanning.md b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md new file mode 100644 index 000000000000..bd279034eee8 --- /dev/null +++ b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md @@ -0,0 +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 %} diff --git a/translations/zh-CN/data/reusables/gated-features/ssh-certificate-authorities.md b/translations/zh-CN/data/reusables/gated-features/ssh-certificate-authorities.md index 4c89830bb5ae..12566421de3f 100644 --- a/translations/zh-CN/data/reusables/gated-features/ssh-certificate-authorities.md +++ b/translations/zh-CN/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+. 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 +SSH 证书机构支持可用于 {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}、{% data variables.product.prodname_ghe_managed %}、{% endif %} 和 {% data variables.product.prodname_ghe_server %} 2.19+。 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 diff --git a/translations/zh-CN/data/reusables/gated-features/wikis.md b/translations/zh-CN/data/reusables/gated-features/wikis.md index 61f560896e02..f470574be627 100644 --- a/translations/zh-CN/data/reusables/gated-features/wikis.md +++ b/translations/zh-CN/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 %} +Wikis 适用于具有 {% data variables.product.prodname_free_user %} 和组织的 {% data variables.product.prodname_free_team %} 的公共仓库，以及具有 {% 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 %} 和 {% data variables.product.prodname_ghe_server %} 的公共和私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md b/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md index 0dccf560d54f..1be33a4be685 100644 --- a/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/zh-CN/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. 您可以选择禁用 {% data variables.product.prodname_actions %} 或将其限制为私有操作，这意味着人们只能使用仓库中存在的操作。 +默认情况下，{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_actions %} 在 {% data variables.product.product_location %} 上启用后，它{% elsif currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_actions %}{% endif %} 将在所有仓库和组织上启用。 您可以选择禁用 {% data variables.product.prodname_actions %} 或将其限制为私有操作，这意味着人们只能使用仓库中存在的操作。 diff --git a/translations/zh-CN/data/reusables/github-actions/enabled-local-github-actions.md b/translations/zh-CN/data/reusables/github-actions/enabled-local-github-actions.md index 0043c8e9608d..79602c267463 100644 --- a/translations/zh-CN/data/reusables/github-actions/enabled-local-github-actions.md +++ b/translations/zh-CN/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. +当您仅启用本地操作时，工作流程只能运行位于您的仓库、组织或企业中的操作。 diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md index 1a16386dc2df..6e4aef176736 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md @@ -1,4 +1,4 @@ -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 %}. 要管理自托管运行器，您必须拥有以下权限，具体取决于添加自托管运行器的位置： +自托管运行器可位于仓库、组织或{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} 上的企业帐户设置{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.product_location %} 上的企业设置{% endif %}中。 要管理自托管运行器，您必须拥有以下权限，具体取决于添加自托管运行器的位置： - **用户仓库**：您必须是仓库所有者。 - **组织**：您必须是组织所有者。 - **组织仓库**：您必须是组织所有者或者拥有该仓库的管理员权限。 diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index da5417e252d5..371a94c67bbf 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -1,6 +1,6 @@ 1. 导航到自托管运行器注册的位置： * **在组织或仓库中**，导航到主页并单击 {% 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**: + * {% if currentVersion == "free-pro-team@latest" %}**如果使用企业帐户**：通过访问 `https://github.com/enterprises/ENTERPRISE-NAME`（将 `ENTERPRISE-NAME` 替换为您的企业帐户名称）导航到您的企业帐户。{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**如果使用企业级运行器**： 1. 在任何页面的右上角，单击 {% octicon "rocket" aria-label="The rocket ship" %}。 1. 在左边栏中，单击 **Enterprise overview（企业概览）**。 @@ -9,4 +9,4 @@ * **在组织或仓库中**：单击左边栏中的 **Actions（操作）**。 ![操作设置](/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". + * {% if currentVersion == "free-pro-team@latest" %}**如果使用企业帐户**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**如果使用企业级运行器**{% endif %}：在“{% octicon "law" aria-label="The law icon" %} Policies（政策）”下单击 **Actions（操作）**。 diff --git a/translations/zh-CN/data/reusables/github-insights/contributors-tab.md b/translations/zh-CN/data/reusables/github-insights/contributors-tab.md index 8ace3bbe6e71..60ad08fdf900 100644 --- a/translations/zh-CN/data/reusables/github-insights/contributors-tab.md +++ b/translations/zh-CN/data/reusables/github-insights/contributors-tab.md @@ -1 +1 @@ -1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Contributors**. ![贡献者选项卡](/assets/images/help/insights/contributors-tab.png) +1. 在 **{% octicon "gear" aria-label="The gear icon" %} Settings（设置）**下，单击 **Contributors（贡献者）**。 ![贡献者选项卡](/assets/images/help/insights/contributors-tab.png) diff --git a/translations/zh-CN/data/reusables/interactions/interactions-detail.md b/translations/zh-CN/data/reusables/interactions/interactions-detail.md index 299f62a79422..fafe2589be36 100644 --- a/translations/zh-CN/data/reusables/interactions/interactions-detail.md +++ b/translations/zh-CN/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -启用限制后，只有指定的 {% data variables.product.product_name %} 用户组才能参与交互。 限制在设置后 24 小时到期。 +启用限制后，只有指定的 {% data variables.product.product_name %} 用户类型才能参与交互。 限制在定义的期限后自动过期。 diff --git a/translations/zh-CN/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/zh-CN/data/reusables/large_files/can-include-lfs-objects-archives.md index 3df66e0b0308..03bb8da83e29 100644 --- a/translations/zh-CN/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/zh-CN/data/reusables/large_files/can-include-lfs-objects-archives.md @@ -1,4 +1,4 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} 您可以选择是否 -{% 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. 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 +您可以选择是否将 {% 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/data/reusables/large_files/rejected_pushes.md b/translations/zh-CN/data/reusables/large_files/rejected_pushes.md index 4d04d4d367be..9e81f90cf472 100644 --- a/translations/zh-CN/data/reusables/large_files/rejected_pushes.md +++ b/translations/zh-CN/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. +如果在企业或仓库上禁用了 {% data variables.large_files.product_name_short %}，则用户无法将 {% data variables.large_files.product_name_short %} 资产推送到 {% data variables.product.product_name %} 。 diff --git a/translations/zh-CN/data/reusables/large_files/storage_assets_location.md b/translations/zh-CN/data/reusables/large_files/storage_assets_location.md index cb76cf1bcf28..dbf1afd5a246 100644 --- a/translations/zh-CN/data/reusables/large_files/storage_assets_location.md +++ b/translations/zh-CN/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`. +默认情况下， +{% data variables.large_files.product_name_long %} 客户端在托管 Git 仓库的同一服务器上存储大型资产。 当 {% data variables.large_files.product_name_short %} 在 {% data variables.product.product_location %} 设备上启用时，大型资产将存储在 `/data/user/storage` 中的数据分区中。 {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/marketplace/downgrade-marketplace-only.md b/translations/zh-CN/data/reusables/marketplace/downgrade-marketplace-only.md index 4a49a8a348ca..461bdac9580c 100644 --- a/translations/zh-CN/data/reusables/marketplace/downgrade-marketplace-only.md +++ b/translations/zh-CN/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 %}. 如果要终止您在 {% data variables.product.prodname_dotcom %} 上的所有付费订阅，必须分别降级每个付费订阅。 +取消应用程序或将应用程序降级至免费不会影响您在 {% data variables.product.prodname_dotcom %} 上的[其他付费订阅](/articles/about-billing-on-github)。 如果要终止您在 {% data variables.product.prodname_dotcom %} 上的所有付费订阅，必须分别降级每个付费订阅。 diff --git a/translations/zh-CN/data/reusables/organizations/organizations_include.md b/translations/zh-CN/data/reusables/organizations/organizations_include.md index f74c8e35f12a..2ca103b28112 100644 --- a/translations/zh-CN/data/reusables/organizations/organizations_include.md +++ b/translations/zh-CN/data/reusables/organizations/organizations_include.md @@ -3,6 +3,6 @@ - 用于升级到 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %} 以获取额外功能的选项，包括复杂的用户身份验证和管理，以及升级的支持选项。 {% data reusables.gated-features.more-info %}{% endif %} - 无限的成员资格，以各种不同的角色授予[对组织及其数据的不同访问权限](/articles/permission-levels-for-an-organization) - 能够向成员授予[对组织仓库的一系列访问权限](/articles/repository-permission-levels-for-an-organization) -- [Nested teams that reflect your company or group's structure](/articles/about-teams) with cascading access permissions and mentions{% if currentVersion != "github-ae@latest" %} +- [反映公司或组结构的嵌套团队](/articles/about-teams)，级联了访问权限和提及{% if currentVersion != "github-ae@latest" %} - 组织所有者能够查看成员的[双重身份验证 (2FA) 状态](/articles/about-two-factor-authentication) -- The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +- 用于[要求所有组织成员使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)的选项{% endif %} diff --git a/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md b/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md index 04eb93059de1..126fa8336d51 100644 --- a/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md +++ b/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ - [添加组织成员到团队](/articles/adding-organization-members-to-a-team) - [从团队中删除组织成员](/articles/removing-organization-members-from-a-team) - [将组织成员升级为团队维护员](/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" %} +- 删除团队的仓库访问权限{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} - [管理团队的代码审查任务](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md b/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md index 925e7e44d245..57de6c3ba350 100644 --- a/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md +++ b/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 目前，{% data variables.product.prodname_github_container_registry %} 只支持 Docker 映像格式。 在测试阶段，存储和带宽是免费的。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)”。 +**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 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)." {% endnote %} diff --git a/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md new file mode 100644 index 000000000000..b0cddc8bcb84 --- /dev/null +++ b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/decide-publishing-source.md b/translations/zh-CN/data/reusables/pages/decide-publishing-source.md index 05bb66b2ac1b..0d2d6d60bfa3 100644 --- a/translations/zh-CN/data/reusables/pages/decide-publishing-source.md +++ b/translations/zh-CN/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 currentver_lt "enterprise-server@2. 3"%}如果您创建的是用户或组织网站，必须将网站的源代码存储在 `master` 分支上。{% endif %} 更多信息请参阅“[关于 {% 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.22" or currentVersion == "github-ae@latest" %}确定{% else %}如果是创建项目网站，确定{% endif %}要使用的发布源。 {% if currentver_lt "enterprise-server@2. 3"%}如果您创建的是用户或组织网站，必须将网站的源代码存储在 `master` 分支上。{% endif %} 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)”。 diff --git a/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md b/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md index a3aa30254d7f..4b6a5f54351d 100644 --- a/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md +++ b/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,3 @@ -如果站点是一个独立的项目，您可以创建新仓库来存储站点源代码。 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. +如果站点是一个独立的项目，您可以创建新仓库来存储站点源代码。 如果您的站点与现有的项目关联，您可以添加站点的源代码添加{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}到该项目仓库的默认分支或其他分支上的 `/docs` 文件夹中。{% else %}到 `gh-pages` 分支或该项目仓库 `master` 分支上的 `docs` 文件夹中。{% endif %} 例如，如果您创建站点来发布已经在 {% data variables.product.product_name %} 中的项目文档， 您可能想要将站点的源代码存储在与项目相同的仓库中。 如果要在现有仓库中创建站点，请跳至“[创建站点](#creating-your-site)”一节。 diff --git a/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md b/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md index da8638052ca7..27cc3feb0b44 100644 --- a/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ {% warning %} - **Warning**: {% 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 contains currentVersion or currentVersion == "github-ae@latest" %}如果您的站点管理员启用了公共页面，{% endif %}{% data variables.product.prodname_pages %} 站点将在互联网上公开，即使其仓库是私有的{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}或内部的{% 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)." {% endwarning %} diff --git a/translations/zh-CN/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/zh-CN/data/reusables/pull_requests/close-issues-using-keywords.md index ded65765fa33..a3b0f93e4bd8 100644 --- a/translations/zh-CN/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/zh-CN/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. 更多信息请参阅“[将拉取请求链接到议题](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)”。 +您可以将拉取请求链接到议题，以便{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} 显示正在进行修复并{% endif %} 在有人合并拉取请求时自动关闭议题。 更多信息请参阅“[将拉取请求链接到议题](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)”。 diff --git a/translations/zh-CN/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md b/translations/zh-CN/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md index cadca78570ff..058bee4daab3 100644 --- a/translations/zh-CN/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md +++ b/translations/zh-CN/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. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." +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. 更多信息请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。 diff --git a/translations/zh-CN/data/reusables/secret-scanning/beta.md b/translations/zh-CN/data/reusables/secret-scanning/beta.md index fded789f2b95..5f853efcb3eb 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/beta.md +++ b/translations/zh-CN/data/reusables/secret-scanning/beta.md @@ -1,5 +1,5 @@ {% note %} -**注：**私有仓库的 {% data variables.product.prodname_secret_scanning_caps %} 目前处于公测阶段，可能会有变动。 要申请访问测试版，[请加入等待列表](https://github.com/features/security/advanced-security/signup)。 +**注：**私有仓库的 {% data variables.product.prodname_secret_scanning_caps %} 目前处于公测阶段，可能会有变动。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md b/translations/zh-CN/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md index 8eff18be1d54..7f56903efc59 100644 --- a/translations/zh-CN/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md @@ -1 +1 @@ -与仓库中的安全漏洞警报相关的活动。 {% 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)". +与仓库中的安全漏洞警报相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[关于易受攻击的依赖项的安全警报](/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies)”。 diff --git a/translations/zh-CN/data/reusables/webhooks/secret.md b/translations/zh-CN/data/reusables/webhooks/secret.md index e7d517a91198..bc23a5a76c1b 100644 --- a/translations/zh-CN/data/reusables/webhooks/secret.md +++ b/translations/zh-CN/data/reusables/webhooks/secret.md @@ -1 +1 @@ -设置 web 挂钩密钥使您可以确保将 `POST` 请求发送到来自 {% data variables.product.product_name %} 的有效负载 URL。 When you set a secret, you'll receive the {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`X-Hub-Signature` and `X-Hub-Signature-256` headers{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature` header{% elsif currentVersion == "github-ae@latest" %}`X-Hub-Signature-256` header{% endif %} in the webhook `POST` request. 有关如何使用密钥和签名标头来保护 web 挂钩有效负载的更多信息，请参阅“[保护 web 挂钩](/webhooks/securing/)”。 +设置 web 挂钩密钥使您可以确保将 `POST` 请求发送到来自 {% data variables.product.product_name %} 的有效负载 URL。 在设置机密时，您将在 web 挂钩 `POST` 请求中收到 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`X-Hub-Signature` 和 `X-Hub-Signature-256` 标头{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature` 标头{% elsif currentVersion == "github-ae@latest" %}`X-Hub-Signature-256` 标头{% endif %}。 有关如何使用密钥和签名标头来保护 web 挂钩有效负载的更多信息，请参阅“[保护 web 挂钩](/webhooks/securing/)”。 diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index da4aed6d8195..8f1026a3ff91 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -3,10 +3,11 @@ header: github_docs: GitHub Docs contact: 联系我们 notices: - ghae_silent_launch: GitHub AE is currently under limited release. Please contact our Sales Team to find out more. + ghae_silent_launch: GitHub AE 目前是有限发行版。请联系我们的销售团队了解更多信息。 + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: 我们经常发布文档更新，此页面的翻译可能仍在进行中。有关最新信息，请访问英文文档。如果此页面上的翻译有问题，请告诉我们。 localization_in_progress: 你好，探索者！ 此页面正在积极开发或仍在翻译中。有关最新和最准确的信息，请访问我们的英文文档。 - product_in_progress: '👋你好，探索者！ 此页面正在积极开发中。有关最新和最准确的信息，请访问我们的开发者文档。' + early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' search: need_help: 需要帮助？ placeholder: 搜索主题、产品... @@ -19,7 +20,7 @@ toc: guides: 指南 whats_new: 新增内容 pages: - article_version: "文章版本：" + article_version: '文章版本：' miniToc: 本文内容 errors: oops: 哎呀！ @@ -121,4 +122,4 @@ footer: shop: 商店 product_landing: quick_start: 快速入门 - reference_guides: Reference guides + reference_guides: 参考指南 diff --git a/translations/zh-CN/data/variables/action_code_examples.yml b/translations/zh-CN/data/variables/action_code_examples.yml new file mode 100644 index 000000000000..84d3a4dfaa8b --- /dev/null +++ b/translations/zh-CN/data/variables/action_code_examples.yml @@ -0,0 +1,149 @@ +--- +- + title: Starter workflows + description: Workflow files for helping people get started with GitHub Actions + languages: TypeScript + href: actions/starter-workflows + tags: + - official + - 工作流程 +- + title: Example services + description: Example workflows using service containers + languages: JavaScript + href: actions/example-services + tags: + - service containers +- + title: Declaratively setup GitHub Labels + description: GitHub Action to declaratively setup labels across repos + languages: JavaScript + href: lannonbr/issue-label-manager-action + tags: + - issues + - labels +- + title: Declaratively sync GitHub labels + description: GitHub Action to sync GitHub labels in the declarative way + languages: 'Go, Dockerfile' + href: micnncim/action-label-syncer + tags: + - issues + - labels +- + title: Add releases to GitHub + description: Publish Github releases in an action + languages: 'Dockerfile, Shell' + href: elgohr/Github-Release-Action + tags: + - 发行版 + - publishing +- + title: Publish a docker image to Dockerhub + description: A Github Action used to build and publish Docker images + languages: 'Dockerfile, Shell' + href: elgohr/Publish-Docker-Github-Action + tags: + - docker + - publishing + - 构建 +- + title: Create an issue using content from a file + description: A GitHub action to create an issue using content from a file + languages: 'JavaScript, Python' + href: peter-evans/create-issue-from-file + tags: + - issues +- + title: Publish GitHub Releases with Assets + description: GitHub Action for creating GitHub Releases + languages: 'TypeScript, Shell, JavaScript' + href: softprops/action-gh-release + tags: + - 发行版 + - publishing +- + title: GitHub Project Automation+ + description: Automate GitHub Project cards with any webhook event. + languages: JavaScript + href: alex-page/github-project-automation-plus + tags: + - projects + - automation + - issues + - 拉取请求 +- + title: Run GitHub Actions Locally with a web interface + description: Runs GitHub Actions workflows locally (local) + languages: 'JavaScript, HTML, Dockerfile, CSS' + href: phishy/wflow + tags: + - local-development + - devops + - docker +- + title: Run your GitHub Actions locally + description: Run GitHub Actions Locally in Terminal + languages: 'Go, Shell' + href: nektos/act + tags: + - local-development + - devops + - docker +- + title: Build and Publish Android debug APK + description: Build and release debug APK from your Android project + languages: 'Shell, Dockerfile' + href: ShaunLWM/action-release-debugapk + tags: + - android + - 构建 +- + title: Generate sequential build numbers for GitHub Actions + description: GitHub action for generating sequential build numbers. + languages: JavaScript + href: einaregilsson/build-number + tags: + - 构建 + - automation +- + title: GitHub actions to push back to repository + description: Push Git changes to GitHub repository without authentication difficulties + languages: 'JavaScript, Shell' + href: ad-m/github-push-action + tags: + - publishing +- + title: Generate release notes based on your events + description: Action to auto generate a release note based on your events + languages: 'Shell, Dockerfile' + href: Decathlon/release-notes-generator-action + tags: + - 发行版 + - publishing +- + title: Create a GitHub wiki page based on the provided markdown file + description: Create a GitHub wiki page based on the provided markdown file + languages: 'Shell, Dockerfile' + href: Decathlon/wiki-page-creator-action + tags: + - wiki + - publishing +- + title: 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: + - projects + - issues + - labels +- + title: Add Label to your Pull Requests based on the author team name + description: Github action to label your pull requests based on the author name + languages: 'TypeScript, JavaScript' + href: JulienKode/team-labeler-action + tags: + - 拉取请求 + - labels diff --git a/translations/zh-CN/data/variables/contact.yml b/translations/zh-CN/data/variables/contact.yml index 6cade26cea62..ff70bf19af0d 100644 --- a/translations/zh-CN/data/variables/contact.yml +++ b/translations/zh-CN/data/variables/contact.yml @@ -10,7 +10,7 @@ contact_dmca: >- {% if currentVersion == "free-pro-team@latest" %}[版权声明表](https://github.com/contact/dmca){% endif %} contact_privacy: >- {% if currentVersion == "free-pro-team@latest" %}[隐私联系表](https://github.com/contact/privacy){% endif %} -contact_enterprise_sales: '[GitHub'' 销售团队](https://enterprise.github.com/contact)' +contact_enterprise_sales: "[GitHub' 销售团队](https://enterprise.github.com/contact)" contact_feedback_actions: '[GitHub 操作的反馈表](https://support.github.com/contact/feedback?contact[category]=actions)' #The team that provides Standard Support enterprise_support: 'GitHub Enterprise 支持' diff --git a/translations/zh-CN/data/variables/release_candidate.yml b/translations/zh-CN/data/variables/release_candidate.yml new file mode 100644 index 000000000000..ec65ef6f9445 --- /dev/null +++ b/translations/zh-CN/data/variables/release_candidate.yml @@ -0,0 +1,2 @@ +--- +version: ''